linux-os (Dick Johnson), le Wed 21 Jun 2006 07:53:12 -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 :
> >> I don't think this is the correct behavior. 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. If you want
> >> a controlling terminal from your emergency shell, please exec /bin/login.
> >
> > Ok, but people don't know that: they're given a shell, and wonder why on
> > hell ^C doesn't work...
> >
> > Samuel
>
> Attached is a simple program called shell.
I already know how to write this.
The problem is not for _me_, it is for all these people that use
init=/bin/sh, and wonder why ^C doesn't work. Finding documentation on
such issue is not easy, so they'll most probably _not_ find out that
they need to use /sbin/sulogin, /bin/login, or even dig the linux-kernel
archives for your program. That's why I'm raising the issue at the
kernel level.
Samuel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
