[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:26:16AM +0200]:
> On 30.07.2010 04:15, Michael Biebl wrote:

> > Besides, I noticed that if no valid init is found, I get a kernel panic, but I
> > assume I should get a rescue shell.

> I guess this might be due to the following:
> # Search for valid init
> if [ -z "${init}" ] ; then
>         for init in /sbin/init /etc/init /bin/init /bin/sh; do
>                 if [ ! -x "${rootmnt}${init}" ]; then
>                         continue
>                 fi
>                 break
>         done
> fi

> Upstart stores its configuration files in /etc/init/.


> This means, the loop above exits at /etc/init, and the init
> variable is set to the /etc/init directory. Is there a good resp.
> historical reason to search for init in /etc (or /bin ftm)?

The kernel uses /sbin/init, /etc/init, /bin/init and /bin/sh
for its run_init_process().


Attachment: signature.asc
Description: Digital signature

Reply to: