From owner-freebsd-current Wed Nov 18 10:46:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18088 for freebsd-current-outgoing; Wed, 18 Nov 1998 10:46:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18075 for ; Wed, 18 Nov 1998 10:46:35 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id KAA06273; Wed, 18 Nov 1998 10:45:16 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 18 Nov 1998 10:45:15 -0800 (PST) From: Doug White To: Ben Hutchinson cc: Garrett Wollman , freebsd-current@FreeBSD.ORG Subject: Re: /etc/rc.d, and changes to /etc/rc? In-Reply-To: <19981118014446.C15587@xfiles.org.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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