From owner-freebsd-ports Wed Sep 20 18:59:51 1995 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA03085 for ports-outgoing; Wed, 20 Sep 1995 18:59:51 -0700 Received: from chemserv.umd.edu (chemserv.umd.edu [129.2.64.40]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA03039 ; Wed, 20 Sep 1995 18:59:42 -0700 Received: from cappuccino.eng.umd.edu (cappuccino.eng.umd.edu [129.2.98.14]) by chemserv.umd.edu (8.7.Beta.14/8.7.Beta.14) with ESMTP id VAA11404; Wed, 20 Sep 1995 21:58:44 -0400 (EDT) Received: (chuckr@localhost) by cappuccino.eng.umd.edu (8.7/8.6.4) id VAA15361; Wed, 20 Sep 1995 21:58:43 -0400 (EDT) Date: Wed, 20 Sep 1995 21:58:43 -0400 (EDT) From: Chuck Robey To: patl@asimov.volant.org cc: kelly@fsl.noaa.gov, terry@lambert.org, julian@ref.tfs.com, asami@cs.berkeley.edu, ports@freebsd.org, hackers@freebsd.org Subject: Re: ports startup scripts In-Reply-To: <9509210127.AA21284@asimov.volant.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ports@freebsd.org Precedence: bulk On Wed, 20 Sep 1995 patl@asimov.volant.org wrote: > |> I don't think that going to such a system means that we have to slavishly > |> copy their every nuance. We could easily set something like: > |> > |> 0: single user > |> 1: multiuser > |> 2: network > |> 3: user-custom > > The run levels seem have fairly standard meanings - PLEASE stick with > the level definitions as used by Solaris, HP-UX, etc. There is no > excuse for gratuituous incompatability. This seems a little cockeyed, requesting no changes in a "standard" item, that would be totally non-standard in BSD from the start anyways. Are there BSD based systems, not running init/inittab SVR type things, that use this setup? Because, if there aren't, asking for standardization is simply tying the hands of designers, for no good purpose. If I'm right, and a BSD standard to this doesn't exist, then an oppurtunity is presenting itself to use the best of what's out there. This isn't linux or SYSV, so reasons based on such systems are out of place. Am I wrong? > > |> > All those oddly named scripts, links, codes are hard to grok. More > |> > often than not, when ``such-n-such is hung,'' I have to > |> > > |> > find /etc/rc* -type f | xargs grep such-n-such > |> > > |> > just to find out the name of the script I'm supposed to use. And it > |> > turns out all it did was run ``such-n-such -d'' which I saw with the > |> > output from `ps', so it would've been faster to just kill it and > |> > restart it---which I'm leary of since what if I forgot to remove a > |> > fifo, lock file, or other such debris before doing so? > > I haven't seen how HP-UX does this; but it's pretty clean in Solaris 2.4. > The files generally have fairly clear names, and they all live in > /etc/init.d. The rc* directories only contain symlinks to the file > in init.d, and the symlinks are clearly named. > > > Once I figured out the basics, this became one of the things I really > like about Solaris as compared with SunOS4.x. > > > > > -Pat > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+-----------------------------------------------