| |||||||||||||
|
| |||||||||||||
"BSD-style" init scripts,"BSD-style" init scripts,Posted Jun 28, 2004 19:10 UTC (Mon) by mattdm (subscriber, #18)In reply to: "BSD-style" init scripts, by allesfresser Parent article: A look at Slackware 10.0 It's a very nice, clean system if you ask me. In fact, doesn't sound that different from the SysV style. :)
(Log in to post comments)
"BSD-style" init scripts, Posted Jun 28, 2004 19:27 UTC (Mon) by allesfresser (subscriber, #216) [Link] I can't comment on the difference with the SysV style, as I've not had enough experience with it, but I *can* say that the Slackware scripts are (to me) a lot more readable than say, RedHat scripts. The reason I say that is because there are no utility functions to trace through, no extra stuff at all. Each script is straightforward shell script. Anyway, I like it. :-)
"BSD-style" init scripts, Posted Jul 1, 2004 4:46 UTC (Thu) by set (guest, #4788) [Link] Well, it does appear to use a sysV init daemon, but then so doesgentoo, without being traditional sysV init systems. eg. it doesnt have a series of directories, like /etc/rc0.d /etc/rc3.d filled with symlinks to the scripts in /etc/init.d with names like K05foo and S90bar, indicating the order of a set of scripts to be run when leaving and entering a new runlevel. Rather, it uses a bunch of /etc/*.conf files to determine the behaviour of the helper scripts, and a large script for each runlevel that calls the helper subsystem scripts. Which is similar to the old BSD system, but their scripts and conf files were all just in /etc/, and there is not really an idea of general runlevels, but more like security levels.
|
|
||||||||||||