[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#590744: Fails to boot if /sbin/init is a symlink

* Michael Biebl <biebl@debian.org> [Fri Jul 30, 2010 at 04:15:44AM +0200]:
> On 30.07.2010 03:57, Michael Prokop wrote:

> >> Does not work. For one, I guess this check
> >> if [ ! -x "${rootmnt}${init}" ] || [ ! -x "${rootmnt}${initsymlinktarget}" ] ;

> >> should be using &&.

> >> Even after fixing that, we run into the same problem, later again, at:

> >> # No init on rootmount
> >> if [ ! -x "${rootmnt}${init}" ]; then
> >>         panic "No init found. Try passing init= bootarg."
> >> fi

> > You have to drop the old "No init on rootmount" stuff of course, so
> > just replace the "No init on rootmount" part with above code.

> I also noticed, that initsymlinktarget is set (ie. we run and expensive chroot
> call), even if I pass init=/bin/systemd on the kernel command line.

No, initsymlinktarget is set to $init, but evaluated only if
${rootmnt}${init} is a symlink.

Can you please give the following snapshot version a try:


(sha1sum and gpg-signed sha1sum in the same directory) and report
back whether this works for all the situations you expect to work?


Attachment: signature.asc
Description: Digital signature

Reply to: