Date: Sun, 29 Nov 1998 18:30:19 +1030 From: Greg Lehey <grog@lemis.com> To: dyson@iquest.net Cc: wes@softweyr.com, tlambert@primenet.com, advocacy@FreeBSD.ORG Subject: Re: Linux to be deployed in Mexican schools; Where was FreeBSD? Message-ID: <19981129183019.H456@freebie.lemis.com> In-Reply-To: <199811290733.CAA35884@y.dyson.net>; from John S. Dyson on Sun, Nov 29, 1998 at 02:33:53AM -0500 References: <19981129175648.F456@freebie.lemis.com> <199811290733.CAA35884@y.dyson.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, 29 November 1998 at 2:33:53 -0500, John S. Dyson wrote: > Greg Lehey said: >> >> OK, I must be missing something, but what does System V init have that >> makes it easier to start up or shut down an application? /etc/rc*.d >> isn't the problem: that's a question of scripts, not init. >> > Init supports runmodes (good or bad -- I don't care -- if one doesn't like > it, then don't use them.) OK. The *idea* of run modes seems to make sense, and I wouldn't change the System V method on a system which had it, but how useful is it really? Consider: Run state Meaning BSD init 0 halt halt 1 single user shutdown 2 multi user, Whaat?? no network 3 multiuser (multiuser; stop single user) 4 undefined (most systems) can't see any equivalent on PCs 5 PROM monitor 6 reboot reboot Where's the important difference? > SysV init has an established set of standards for usage of > startup/shutdown files. It doesn't solve ALL problems, but moves > forward, other than just staying idle. Sure, but as I said, that's all a question of scripts. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981129183019.H456>