Date: Tue, 15 Jul 1997 11:48:03 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: nate@mt.sri.com (Nate Williams) Cc: terry@lambert.org, syssgm@dtir.qld.gov.au, freebsd-hackers@FreeBSD.ORG Subject: Re: multiple run-levels (was: Re: /etc/init.d/) Message-ID: <199707151848.LAA03861@phaeton.artisoft.com> In-Reply-To: <199707151802.MAA29930@rocky.mt.sri.com> from "Nate Williams" at Jul 15, 97 12:02:06 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > IBCS2 compatability requires that the target system support run levels > > to correctly support IBCS2 compliant installation scripts for commercial > > shrink-wrapped products designed to be run on UNIX platforms. > > I and others have run lots of 'shrink-wrapped' software, and none of > them required 'run-levels' to work, though they did require the ability > to start/stop processes (which is independent of run-levels). And you had to manually comprehend and write equivalents for the scripts that would have been installed. And the installation was not automatic, since we don't have IBCS2 compliant package management tools. Try installing the IBCS2 Lotus 1-2-3 (as one example). As far as starting or stopping servers, try installing an IBCS2 Sybase database server without installing the correct startup scripts into the rc3.d directory. > Also, you're 'docked/undocked' run-level requirement is a straw man. > All of your configuration is completely un-related to run-levels. The configuration is related to run *states*. The hardware can be *run* in several *states*, which *could* be represented by seperate run states. It is not a strawman, it is simply not the soloution you personally would choose (apparently). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199707151848.LAA03861>