Designing a new init: configuration

[a-aa]

Erich Schubert wrote:

>Hi,
>  
>
>>I should mention that I wrote rcparser a while ago as a initng plugin,
>>proof of concept, that boots using /etc/init.d sysv scripts, it was
>>rough, but not as much as I thought it'd be.
>>    
>>
>
>The question is, do we need a system that can use such plugins - I'd
>prefer a system so small it runs on the embedded systems I'm also
>developing on.
>minit works like a charm there - without fork(). Because it's a noMMU
>platform...
>When we design a new system, I'd love to have a core with as low
>requirements as that.
>Nothing wrong with doing more on a higher level though - if we can do
>a "ln -s /usr/sbin/initrc-parser run" so to speak - fine.
>  
>
Yes, we need plugin support, it doesn't add much to the size, it allows
embeded systems to remove stuff it doesn't need, and more importantly,
it forces a ton of functions to run through the same system calls
instead of using hackish internal magic.  Forcing use of a plugin api
like system generally forces better code.  If you really want it small
you could easily do something like "static plugins", that uses defines
to allow some plugins to be statically compiled in (and still use the
plugin api).

>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
>
>_______________________________________________
>initscripts-ng-devel mailing list
>initscripts-ng-devel at lists.alioth.debian.org
>http://lists.alioth.debian.org/mailman/listinfo/initscripts-ng-devel
>
>  
>