Messages in this thread | | | Date | Fri, 13 Nov 1998 16:25:54 +0000 | From | Jamie Lokier <> | Subject | Re: e2fsck... |
| |
On Fri, Nov 13, 1998 at 01:41:12PM +0100, ralf@uni-koblenz.de wrote: > The problem is that current kernels start init, be it /{sbin,bin,etc}/init > or whatever was passed as init= argument as PID 1. But PID 1 has several > special properties like the priviledge of ignoring any signal it wants to > ignore or adopting any orphaned process. One of the nervragging funnies > with that is that that bash will ignore signals like sent from <CTRL>-C.
Oh, so _that_'s why fastboot bash can't be Ctrl-C'd. Grr, always found that annoying.
These days, wouldn't it make more sense for init's properties to be set using a capability instead of based on PID 1?
-- Jamie
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |