Mike Meyer wrote:
> Yes, that's correct. And yes, not all is bad in SysV. In particular,
> having a directory where you can find scripts to stop (and restart)
> subsystems is very nice. I think the multiple levels (rc?.d) is a bit
> of overkill. Either the system is up (meaning everything is turned
> on), or it's down, and the sysadmin who brought it down can start the
> subsystems s/he needs. Having a single init.d to look in for those
> things helps in that process.

The multiple levels are there to deal with changes in state. In BSD, for
instance, we have single user/multi-user. A number of other variations
can exist, both in heavy duty servers where you might want to bring
certain services down for upgrade and then back up, and "desktop"
machines, such as notebooks where you can be stand-alone, docked into
different networks (eg. home/work).

Thing is, SysV does it in a very ugly way, and not flexible enough

This has been talked to death. Look at these:


and my favorite substitute proposal:


Daniel C. Sobral                        (8-DCS)

                <jkh> _DES: The Book of Bruce has only one sentence in it, and it says
"the actual directives of my cult are left as an exercise for the
reader. Good luck."
                <EE> jkh: does it really include the 'good luck' part?
                <jkh> EE: OK, I made that part up.
                <jkh> EE: I figured it should sound a bit more cheery than how Bruce
initially dictated it to me.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to