You are not logged in.
Pages: 1
I have a suggestion that may simplify modifying system initialization, by using something we could call SIMs (for SysInit Modules).
A SIM could simplify system initialization by spliting file rc.sysinit into modules, which could then be enabled or disabled in rc.conf.
By having system initialization modules as separate files, it could be easier for people to improve the overall process.
I have created a feature request and attached to it the relevant files (which I'm using in my ArchLinux installation) so that you guys can have a hands-on experience. It can be found at http://bugs.archlinux.org/task/14569.
Google Buzz: http://bit.ly/elifarley-buzz
Google Reader: http://bit.ly/elifarley-reader
Bookmarks: http://delicious.com/elifarley | http://twitter.com/elifarley
Professional info: http://br.linkedin.com/in/elifarley | http://openhatch.org/people/elifarley/
Offline
doesnt this go against the KISS principle?
Offline
Some would say KISS is violated, some wouldn't.. Personally, I think it's a simple idea - but that there's a simpler one;
1. find an editor that lets you do block comments in bash scripts
2. open up rc.sysinit, and comment the lines that you don't want executed
pre: there's stuff in rc.sysinit that you don't want (RAID setup, fsck, lvm, etc. etc.).
post: you get rid of the stuff
simple
div curl F = 0
Offline
rc.sysinit is already 'split' somewhere with things like the 'network' and 'netfs' DAEMONS. Instead of 'violating' KISS and implementing a new process (aka 'SIM'), why not just extend the functionality we already have an use with DAEMONS. I know there's the obvious issue with the fact that we're not strictly speaking about daemons, but we're already doing it with the afore mentioned processes.
Failing that, I'll be the first to suggest the 'network' and 'netfs' daemon scripts become a "SIM"
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
Pages: 1