On Friday 08 April 2011 19:54:08 Andrew Benton wrote: > On Fri, 8 Apr 2011 16:58:26 -0400 > > Neal Murphy <neal.p.mur...@alum.wpi.edu> wrote: > > If the specific kernel option is enabled, one can 'zcat /proc/config.gz' > > to obtain the config used to build the running kernel. > > Yes, but it's a chicken and egg situation. The first time you compile a > kernel on a new computer all you have is the generic config from the > distro you used to install LFS. It would be nice if there was a simple > script that would use lsmod, lspci, lshw, dmidecode or whatever to > probe the hardware and write a basic .config for you that would at > least have some sensible defaults and would boot. If you just took the > ubunut (or whatever) .config it would have _everything_ enabled as a > module and it would take forever to compile. A script that at least > disabled support for hardware you don't have would save a lot of time.
Ah, right. I briefly considered doing something like this to automate preparing a system for Coreboot, some years back when I last *really* wanted to dump the braindead BIOSes most Intel/AMD mboards ship with. Then I realized it was probably a lot more involved than it seemed at first glance. N -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
