Re: rc.d script to load kernel modules

> On 6/12/11 11:20 PM, Daniel Braniss wrote:
> >> On 6/12/2011 1:56 AM, Jason Hellenthal wrote:
> >>
> >>> Cutting modules out of the kernel in general does help speed up booting
> >>> but loading those same modules later in the boot process will just lead
> >>> you back to the same boot time.
> >> Loading modules via loader.conf is many times slower than doing it from
> >> disk after the system is partially booted. (As in, 2-3 seconds per
> >> module vs. nearly instantaneous for all 6.)
> >>
> >> I didn't offer my list as an example of what to do, I offered it as a
> >> syntax example. I would of course expect people to use appropriate
> >> discretion to load things in loader.conf that are necessary for boot.
> >> (Of course, the fact that people can easily get this wrong is a strike
> >> against the technique.)
> >>
> >> There is no point in having an _enable for this script because if the
> >> kld_list is empty, nothing happens.
> >>
> > Doug's solution is what we have been using for a very long time!
> >
> > the loader.conf solution is not practical when it's shared among many
> > hosts -like here where most of the hosts are dataless-, so, moving the not
> > essential ones to rc.conf was the obvious solution.
> 
> what would be REALLY cool would be the ability to make loader.conf 
> have some sort of conditional
> clauses..
> 
> e.g. if MAC== 01:02:03:04:05:06
>            blah
in case of diskless, this is solved by having a private (per host/per network/etc)
rc.conf.

in case you use dhcp/pxeboot, you can concatenate several rc.confs to get
one tailored.

danny