Date: Wed, 18 Nov 1998 10:45:15 -0800 (PST) From: Doug White <dwhite@resnet.uoregon.edu> To: Ben Hutchinson <benhutch@xfiles.org.uk> Cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, freebsd-current@FreeBSD.ORG Subject: Re: /etc/rc.d, and changes to /etc/rc? Message-ID: <Pine.BSF.4.03.9811181039050.27173-100000@resnet.uoregon.edu> In-Reply-To: <19981118014446.C15587@xfiles.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 18 Nov 1998, Ben Hutchinson wrote: > In which case how about implementing something a little more sysv-ish for > only ports? > > Ie, a rough idea: > > /usr/local/etc/rcS.d for startup scripts I strongly oppose this; rc.d already exists and is standardized in several releases. Such a change would be gratuitous. > /usr/local/etc/rcK.d for shutdown scripts rc.shutdown.d would be a self-documenting name. rcK.d doesn't mean anything to me. (K=kill?? I don't come from a Solaris background.) > Would this provide sufficient granularity? It would save people from hacking /etc/rc.shutdown (like rc.d saves hacking /etc/rc.local). Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.03.9811181039050.27173-100000>