On Tue, 20 Jun 2006 06:28:02 +0200, Willy Tarreau said: > Then, I think that a solution which would fit everyone's needs would be > to add a command line parameter (eg: "setsid=1") which will allow > the two lines to be executed whatever the init or shell. This way, > you want a session ? -> "init=/bin/sh setsid=1". Get 2 for the price of one: init=/bin/something_that_does_setsid_in_userspace_and_doesnt_clutter_kernel Or once you get a # prompt from /bin/sh, 'exec /bin/something_saner'. Remember - if it's trivially done in userspace, it probably shouldn't be cluttering the kernel.
Attachment:
pgpyaWpWYbbE1.pgp
Description: PGP signature
- References:
- Re: emergency or init=/bin/sh mode and terminal signals
- From: Samuel Thibault <[email protected]>
- Re: emergency or init=/bin/sh mode and terminal signals
- From: David Luyer <[email protected]>
- Re: emergency or init=/bin/sh mode and terminal signals
- From: Willy Tarreau <[email protected]>
- Re: emergency or init=/bin/sh mode and terminal signals
- Prev by Date: [patch] i386: halt the CPU on serious errors
- Next by Date: How to get kernel source release from git tree?
- Previous by thread: Re: emergency or init=/bin/sh mode and terminal signals
- Next by thread: Re: emergency or init=/bin/sh mode and terminal signals
- Index(es):
 |