Subject: Re: Summary: Third-party rc.d scripts
To: NetBSD Packages Technical Discussion List <>
From: Frederick Bruckman <>
List: tech-pkg
Date: 02/09/2002 15:54:28
On Fri, 8 Feb 2002, Greg A. Woods wrote:

> >      pkgsrc can be taught to stash an rc.d script somewhere safe before
> >      overwriting it (/var/backups?).
> Ah, no, pkgsrc should install the original copy of the rc.d script under
> $PREFIX/share/examples/$PKGBASE.

I now believe, the only reasonable way to handle this, is to make sure
the package scripts don't conflict with anything in the base scripts.
They should have unique names, like "pkg_named", and unique rcvars, so
you could start, say, either "named" or "pkg_named" or both, just by
twiddling the knobs in "/etc/rc.conf". This way we're free to install
them into "/etc/rc.d", maybe even include them in some future base system.

> A pkg_install (or pkg_activate, or
> similar) script/program/etc. should be added to facilitate making a
> package work on any given client system.

Interesting idea. I think it's not necessary, though: all the clients
could, instead, sync up "/etc/rc.d/", "/etc/defaults/rc.{,pkg.}conf",
and "/usr/share/sushi/system/rcconf/form" with the server. If there's
something that they then all need enabled, enable it on one, and sync
"/etc/rc.conf" with each other.