Designing a new init: low level communication

Erich Schubert erich.schubert at gmail.com
Mon Aug 29 12:05:23 UTC 2005


Hi,
> But one thing I'd really like is some way of catching all output from
> init, which would probably cause a lot of overhead running through unix
> sockets? hm, maybe not, in either case it's one thing I kinda miss in
> initng, as it'd be nice to run X up as soon as possible, and show the
> boot events in X.

I'd suggest using round-robin shared memory block for that. I've
written such code before, it's really easy... (I use it for e.g.
giving data throughput averages on network interfaces, link quality
averages and such - a daemon is polling the data into SHM, then
clients can cheaply access the information.)
Dmesg uses a similar thing IIRC to access the kernel messages, so we
can maybe just patch it - think of "dmesg -i" for accessing init logs.

best regards,
Erich Schubert
--
    erich@(mucl.de|debian.org)      --      GPG Key ID: 4B3A135C    (o_
  To understand recursion you first need to understand recursion.   //\
  Wo befreundete Wege zusammenlaufen, da sieht die ganze Welt für   V_/_
        eine Stunde wie eine Heimat aus. --- Herrmann Hesse



More information about the initscripts-ng-devel mailing list