Re: rc improvements (wanted?)

On Sat, Jul 19, 2008 at 08:22:05PM +0200, mouss wrote:
> Bernd Walter wrote:
> >On Sat, Jul 19, 2008 at 05:03:53PM +0200, Miroslav Lachman wrote:
> >>Bernd Walter wrote:
> >>
> >>[...]
> >>
> >>>Speaking about small systems, where startup time is more a problem than
> >>>on 08/15 desktop and server systems.
> >>>What I would love to see is that scripts like moused, ypserv, lpt, etc
> >>>are not started if the services are disabled.
> >>>So far each script is started, sucks in routines plus rc.conf then
> >>>possibly does nothing reasonable after wasting some seconds boottime.
> >>>Of course I can remove the scripts, but you'll never know if you need
> >>>one of them at a later time and having the right set of scripts can
> >>>become tricky.
> >>And what about just chmod unneeded scripts to become not executable / 
> >>readable instead of removing?
> >>(I like the current "one directory" layout instead of some linuxism with 
> >>many directories and symlinks)
> >
> >This and all the ideas about using enable/disable directories or
> >softlinks share a major problem:
> >They requires configuring outside of rc.conf, which is not what I want.
> >Of course I can do:
> >mkdir /etc/rc.d/disabled ; mv /etc/rc.d/moused /etc/rc.d/disabled
> >But then I would loose the ability to configure everything with rc.conf.
> >A tool, which parses rc.conf and automatically relocates might be an
> >option, but it would be better if it can be done without.
> >
> 
> 
> how about a cache mechanism: rcorder/rc would use a previously 
> determined order unless something changed in rc.conf or rc.d.
> 
> this way you don't need to determine which scripts need to run and in 
> which order every time the system boots. this also removes the need for 
> an "active.d" directory.

Sounds good, but I think the problem is that rc.conf is a script and
that some people do smart rc.conf settings e.g. by loader settings
to allow their notebooks to boot differently.
That of course also invalidaes my idea with the tool above.

-- 
B.Walter <bernd_at_bwct.de> http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.