On Wed, Jun 12, 2013 at 08:49:57AM +0200, thorsten wrote: > > As far as drivers, disable what you > > don't need and enable what yo do need. > > > William Harrington > > Two hints I got some time ago, which helped me a lot: > > 1: get a recent distro, boot it up, do > > dmesg > dmesg.log, > look at dmesg.log with eg. vim and look at the kernel bootmessages for > the hardware the kernel finds, in my case as example the network card: > > cat dmesg.log | grep net > > gives me: > > [ 1.268430] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [ snip good advice on how to identify the drivers ]
What you can also do, from a recent distro kernel, is 'lsmod'. Now, some distros build all manner of _security_ additions (fedora use selinux, I believe ubuntu use smack or a name like that). You can ignore those for an LFS system. But for everything else which a distro is running as a module, you probably need it. Note that this is very different from everything which a distro *builds* as a module - they try to cover all hardware and filesystems that their users might use, all you need is the hardware and filesystems that you are actually using. Also, please remember that in LFS we don't use an initrd, so everything that is needed to access the filesystems has to be built in, not as modules. That means both the filesystems themselves and the drivers for the disks (usually, libata). Things which come later, such as ethernet drivers, can be built as modules if you wish. HTH. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
