On Tue, 26 Jan 1999, Robert G. Brown wrote:
> So, while AGREEING that one common init style would be good, and
> while ACCEPTING that it may well be that SysV is, on the whole,
> more scalable and disciplined, I cannot help but think that there
> shouldn't be a better compromise between BSD flatfiles and SysV
> startup scripts, symlinks and config entities that are fragmented
> Can't we do better than a ratsnest of code with the file
> equivalent of goto's all over the place that no programming
> instructor would ever be pleased with in an assignment?
There could be a simple way:
/etc/init.d/scripts/ scripts for daemons/programs
/etc/init.d/system/ basic system stuff not belonging to a daemon
/etc/init.d/init.N/ symlinks to the scripts to run in each
runlevel
-->
for i in init.5/*.rc
do $i
done
<--
Then, of course, there should be a way of making sure the
scripts are run in the right order, but we can probably
do that with a rather simple kludge like a text file.
Add-on packages will almost never need to have their
script run with priority. If it needs that its fairly
complicated and system-dependant anyway...
regards,
Rik -- If a Microsoft product fails, who do you sue?
+-------------------------------------------------------------------+
| Linux memory management tour guide. [EMAIL PROTECTED] |
| Scouting Vries cubscout leader. http://www.nl.linux.org/~riel |
+-------------------------------------------------------------------+
