split rc.sysinit

[Florin Andrei <florin sgi com>]

How about splitting rc.sysinit into multiple commands in a directory,
init.d style?
I've seen several cases when various applications (usually stuff that
wants to do low-level things) needed to somehow insert themselves in the
rc.sysinit sequence. With a monolithic rc.sysinit that's impossible
unless you hack the script using sed, perl, etc., which is ugly to say
the least.

One issue with splitting it (among many other that i'm not going to
mention) might be that the boot up time might get a bit bigger. If i'm
not mistaken, this could be avoided by creating one single actual
executable, and let it source things up from a directory, instead of
launching multiple executable scripts sequentially.

Splitting this executable might also allow for things like optionally
turning on (or NOT turning on) IEEE1394 or USB in userspace (as opposed
to using kernel parameters in the bootloader), etc.

Keyword: flexibility
Downside: complexity

-- 
Florin Andrei

"Never send a human to do a machine's job." - Agent Smith