Re: RFC: Alternate patch to have true new-style rc.d scripts in ports(without touching localpkg)

> > - Why cannot /usr/local/etc/rc.d be used with rcorder if /etc/rc.d/local
> > is okay?
> 
> What if a startup script need to do something BEFORE /usr is mounted? My
> case in point is Tobias Roth's profile.sh script. Since this is a script
> only with no programs in /usr/local, the only way to put it into a port
> is to allow it into the root filesystem in some place where it can be
> run before any filesystem is mounted. (It is dependent on ly on fsck.)

Good point. In my opinion, this is a sufficiently special requirement
that it should have a special solution - no need to change the existing
/usr/local/etc/rc.d mechanism. Though I can see how others would see it
differently.

I can live with /etc/local/etc/rc.d or /etc/rc.d/local however - it's
just not something I would prefer. Also, having a separate "local"
directory somewhere under /etc for startup would make it easy for
mergemaster to ignore it.

If /etc/local/etc/rc.d or /etc/rc.d/local is chosen it would be really
nice if rcorder could also look at /usr/local/etc/rc.d, for those of us
who prefer to keep things out of /etc.

Steinar Haug, Nethelp consulting, sthaug_at_nethelp.no