svn commit: r225201 - in head/sys: amd64/conf i386/conf

[Garrett Cooper]

On Sat, Aug 27, 2011 at 2:21 PM, Slawa Olhovchenkov <slw at zxy.spb.ru> wrote:
> On Sat, Aug 27, 2011 at 02:09:36PM -0700, Garrett Cooper wrote:
>
>> >> > What drivers in GENERIC don't need to boot from disk or network?
>> >> > sound only?
>> >>
>> >> man rc.conf, search for kld_list.
>> >
>> > Sorry for bad english.
>> > What drivers (from current GENERIC) don't need for network or disk
>> > boot and can be moved to kld_list?
>> >
>> > I see only sound and agp.
>>
>>     The answer varies based on your deployment mechanism and
>> requirements. For example: some modules like the kqemu, nvidia,
>> vboxdrv, etc, etc don't need to be loaded until later on in the boot
>> process. That being said, if I'm netbooting I don't need to load
>> storage drivers and the like until later on (unless I want to do some
>> sort of mountroot manipulation, need to have a working kernel dumpable
>> device at boot, etc).
>> -Garrett
>
> No-no-no.
> GENERIC placed on instalation CD/DVD and updated by freebsd-update.
> So GENERIC (and modules loaded in /boot/loader.conf from instalation
> image and in default install) must be enought to install in widest
> environment.

    This method is for customizers more than generalists today. but
should potentially be extended to generalists tomorrow (this method is
similar to what I would refer to as "pimp my PC").

> If drivers moved from GENERIC to /boot/loader.conf it allow preserve
> wide range of installation environment and give light way to reduce
> count of loaded devices (by edit /boot/loader.conf).

    /boot/loader.conf is empty by default. GENERIC for the most part
is a complete, monolithic kernel. I'm not sure what the issue is here,
because this is for more advanced usage (i.e. you do linux_load="YES"
in /boot/loader.conf, etc).
Thanks,
-Garrett