501056 – sys-kernel/genkernel-next-35 should pass init=$variable (systemd)

Bug 501056 - sys-kernel/genkernel-next-35 should pass init=$variable (systemd)

Summary: sys-kernel/genkernel-next-35 should pass init=$variable (systemd)

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Fabio Erculiani (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2014-02-12 10:50 UTC by Arnaud Desgranges
Modified:	2015-04-10 12:04 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
emerge --info (emerge.info,5.54 KB, text/plain) 2014-02-12 10:52 UTC, Arnaud Desgranges	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Arnaud Desgranges 2014-02-12 10:50:39 UTC

When i pass init=/usr/lib/systemd/systemd in grub kernel command line,like this :

title Gentoo Linux
root (hd0,0)
kernel  /vmlinuz root=/dev/sda2 init=/usr/lib/systemd/systemd
initrd  /initrd

It boots in openrc
It is also said in the wiki : http://wiki.gentoo.org/wiki/Talk:Systemd :
genkernel-next

There are problems with stable genkernel-next-35: kernel use init system from /sbin/init instead of /usr/lib/systemd/systemd
Grub2 config is right:
GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd"
Updating to unstable genkernel-next-47 fix this problem

I confirm this problem.
with unstable genkernel-next it is solved

Reproducible: Always

Steps to Reproduce:
1. emerge stable genkernel-next
2. boot in systemd init failed
3.
Actual Results:  
boot in openrc

Expected Results:  
boot in systemd

Comment 1 Arnaud Desgranges 2014-02-12 10:52:40 UTC

Created attachment 370202 [details]
emerge --info

Comment 2 Pacho Ramos gentoo-dev

2015-04-10 12:04:01 UTC

55 version (current stable) should have this fixed