Date: Sat, 23 Sep 1995 22:13:16 -0500 From: peter@taronga.com (Peter da Silva) To: hackers@freebsd.org Subject: Re: ports startup scripts Message-ID: <199509240313.WAA01237@bonkers.taronga.com> In-Reply-To: <Pine.3.89.9509232038.B7901-0100000@kryten.atinc.com> References: <199509230139.UAA03748@bonkers.taronga.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <Pine.3.89.9509232038.B7901-0100000@kryten.atinc.com>, Jonathan M. Bresler <jmb@kryten.Atinc.COM> wrote: > each rc?.d is a separate directory, with possibly distinct files. If you don't have the files with the same "service" name linked to each other, you have a messed up installation. That's no worse than having bootleg stuff in /etc/rc instead of /etc/rc.local. > with the K* and S* files in different directories, one for each >run level, ascertaining the differences is needlessly harder. There are no differences unless you're using a broken editor. Add a check for that to /etc/daily. > consider instead a file that lists which scripts to run for each >'run level or the term of the day we are using' and the order of >execution. now if both level A and level B need script Sfoo, there is >only one Sfoo. no symlinks required. no hard links required. it is >immediately obvious what is differnct and what is the same among the run >levels. And you have to trust 150 packages to edit this file without clobbering it. And you have to trust 100,000 system administrators to do the same. Getting them to "mv KXXfoo .KXXfoo" is easier. We have ... novice ... system admins at work. The number of botched systems went way down when we copied the run-level stuff from System V to our Xenix boxes. DEC thought the same thing... that's one of the things they picked up from System V for Digital UNIX... and they have been gratifyingly conservative about that. I'm not that averse to having a unified directory, but each component should have its own startup and config file. Like I said in my original response, just having /etc/rc.d with S and K scripts run by /etc/rc and shutdown would be a massive improvement. Run levels are *also* useful. Something like /etc/default to hold all the random *.conf files (/etc/conf.d?) would tidy up /etc no end too...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509240313.WAA01237>