Subject: Re: rc.d network vs NETWORK
To: Luke Mewburn <>
From: Tracy J. Di Marco White <>
List: current-users
Date: 04/20/2001 08:41:16
}On Fri, Apr 20, 2001 at 08:40:55AM +0200, Tom Ivar Helbekkmo wrote:
}> Speaking of rc.d and rcorder: should there, perhaps, be an rc.conf
}> variable one could set to make /etc/rc and /etc/rc.shutdown include
}> /usr/pkg/etc/rc.d/* and/or /usr/local/etc/rc.d/* automatically?
}This assumes that /usr/pkg and /usr/local is available at boot time
}(i.e, on the / filesystem). If you add them later into the dependency
}tree, they may not get started at the correct time.
}The issue of how to support how a package install adds its own rc.d
}startup script and configuration to the system has not yet been
}resolved (there's been a fair bit of debate on this issue). I believe
}the current suggested practice is to copy /usr/pkg/etc/rc.d/foo ->
}/etc/rc.d, and add an entry to /etc/rc.conf or /etc/rc.conf.d/foo.
}At least, this is what I do.

My solution was to create /etc/local, and touch everything in /etc
and /etc/rc.d as little as possible.  I changed /etc/rc like so:
#files=`rcorder -s nostart /etc/rc.d/*`
files=`rcorder -s nostart /etc/rc.d/* /etc/local/rc.d/*`
(and I must say it was interesting watching how rcorder orders things
just depending on which order those two directories are in.)

This lets me wipe out /etc/rc.d when I update and just make install
in /usr/src/etc/rc.d so I don't leave old files lying around.
I also put local changes to the things that live in /etc/defaults
in /etc/local, so I have an /etc/local/rc.conf referenced from

Tracy J. Di Marco White
Project Vincent Systems Manager