Subject: Re: managing /usr/pkg/etc/rc.d
To: Frederick Bruckman <>
From: Greg A. Woods <>
List: netbsd-users
Date: 05/14/2003 14:08:34
[ On Wednesday, May 14, 2003 at 12:46:40 (-0500), Frederick Bruckman wrote: ]
> Subject: Re: managing /usr/pkg/etc/rc.d
> Actually, netbsd-users was supposed to be for things unrelated to
> the design of NetBSD, such as "What program can I use to do this (on
> NetBSD)?", but it hasn't really worked out that way, so whatever.

I agree!  However since the choice of design causes endless confusion
for end users it's going to be an F.A.Q. until the design is fixed.  :-)

> Hey, were you, at one time, advocating running the start-up scripts
> from ${PREFIX}/etc/rc.d? If so, what made you change your mind?

Yes, but that was long before the new pkgsrc/mk/install/* template
scripts came along.

I now definitely prefer treating RCD scripts as examples and simply
requiring the administrator to copy them into whatever place is
appropriate (along with editing /etc/rc.conf to control them).

Some folks may indeed wish to put their /usr/pkg directory on the root
filesystem and keep their RCD scripts separate in ${PREFIX}/etc/rc.d,
and yet others may wish to hack /etc/rc.local to run "rcorder" on their
${PREFIX}/etc/rc.d and separately start all their add-on packages after
their $PREFIX has been mounted.  However so long as the RCD scripts are
installed and registered in the share/examples directory, the procedures
for configuring and activating any add-on daemon remain the same for

Perhaps 'sushi' (and other add-on administration tools, such as maybe
webmin) could grow a new menu for managing packages by copying the
share/examples/rc.d scripts, and then deleting the copy upon
de-activation, and that way maybe even those whe are crying for
automated handling of the last manual steps would also be appeased.

								Greg A. Woods

+1 416 218-0098;            <>;           <>
Planix, Inc. <>; VE3TCP; Secrets of the Weird <>