Date: Mon, 13 Jun 2011 09:20:04 +0300 From: Daniel Braniss <danny@cs.huji.ac.il> To: Doug Barton <dougb@FreeBSD.org> Cc: jhell@DataIX.net, freebsd-current@freebsd.org Subject: Re: rc.d script to load kernel modules Message-ID: <E1QW0VI-000Ohl-K4@kabab.cs.huji.ac.il> In-Reply-To: <4DF50AA1.9080607@FreeBSD.org> References: <4DF3E98B.40108@FreeBSD.org> <20110612085649.GA11503@DataIX.net> <4DF50AA1.9080607@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. my .5 danny
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1QW0VI-000Ohl-K4>