Re: emergency or init=/bin/sh mode and terminal signals

[Samuel Thibault <samuel.thibault@ens-lyon.org>]

linux-os (Dick Johnson), le Tue 20 Jun 2006 07:26:39 -0400, a écrit :
> 
> On Mon, 19 Jun 2006, Samuel Thibault wrote:
> 
> > linux-os (Dick Johnson), le Mon 19 Jun 2006 07:37:02 -0400, a écrit :
> >> You can't allow some terminal input to affect init. It has been the
> >> de facto standard in Unix, that the only time one should have a
> >> controlling terminal is after somebody logs in and owns something to
> >> control.
> >
> > Ok. The following still makes sense, doesn't it? (i.e. set a session for
> > the emergency shell)
> >
> > --- linux-2.6.17-orig/init/main.c	2006-06-18 19:22:40.000000000 +0200
> > +++ linux-2.6.17-perso/init/main.c	2006-06-20 00:07:07.000000000 +0200
> > @@ -729,6 +729,11 @@
> > 	run_init_process("/sbin/init");
> > 	run_init_process("/etc/init");
> > 	run_init_process("/bin/init");
> > +
> > +	/* Set a session for the shell.  */
> > +	sys_setsid();
> > +	sys_ioctl(0, TIOCSCTTY, 1);
> > +
> > 	run_init_process("/bin/sh");
> >
> > 	panic("No init found.  Try passing init= option to kernel.");
> >
> 
> Well this makes 'sense' however, you should not modify the kernel
> for this,

Why not? /bin/sh is not supposed to start a session, so in this case it
should be up to the kernel to start it.

Samuel