Date: Sun, 29 Nov 1998 19:16:40 -0500 (EST) From: "John S. Dyson" <dyson@iquest.net> To: grog@lemis.com (Greg Lehey) Cc: dyson@iquest.net, wes@softweyr.com, tlambert@primenet.com, hackers@FreeBSD.ORG Subject: Re: System V init (was: Linux to be deployed in Mexican schools; Where was FreeBSD?) Message-ID: <199811300016.TAA01844@y.dyson.net> In-Reply-To: <19981130080037.A423@freebie.lemis.com> from Greg Lehey at "Nov 30, 98 08:00:37 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Greg Lehey said: > > > > Add additional packages, and see that BSD init ends up more > > and more inadequate. > > I still don't see why. We have a method to run application startup > and shutdown scripts already. Could you be more specific? > Startup your network or database with init? > > >>> 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. > > > > Also, it is all a question of C-code, > > Where? > SYSV-like init are available . > > > but a framework enables better organization. However SYSV-init is > > implemented, vendors do use it. > > I suppose there's one point there. But the only difference for > installing under FreeBSD would be the name of the startup file. > The more your system is nonstandard, the more it will be considered to be nonstandard. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811300016.TAA01844>