Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Can someone walk me through configuring the kernel in chapter 8.3, or does it need to be specially configured at all? This is my first time doing this and I got this far, and really don't want to screw up in the last chapter.
Last edited by computerfreak97; 12-29-2010 at 08:44 PM.
Nope, this is not possible. Since we do not know your hardware configuration this is the one chapter in LFS where you are basically on your own. But here is a useful hint: http://www.linuxfromscratch.org/hint...figuration.txt
I compiled my first kernel for LFS by simply using a config-file from another Linux distro that was installed on the same computer. So I just copied it over to the build directory and used 'make ... oldconfig' instead of menuconfig.
Later I switched to 'make defconfig' which was also fine in a VM.
BTW, what host are you using? Real computer or VM? If real, is there any other distro installed on it?
Well, then defconfig is a good choice. I do recall that one time support was compiled for ext3 filesystem but not ext2. But I do not remember if this happened when I used defconfig or if I simply misconfigured. On my VM (VirtualBox) I also needed to compile the module 'pcnet32' to get the network card working. Not sure if this will also be an issue on your VM.
I suggest you just go with defconfig and see what happens when you try to boot.
However, as a Gentoo user (in Gentoo, manual configuration during install can also be done), I must warn you that the filesystem will not be compiled in by default. You'll have to make sure to compile it in (not as a module, unless LFS uses a ramdisk (if it doesn't mention one, then it doesn't use one)).
I also have a computer where it will still fail to mount the root filesystem, as a necessary chipset driver (Nvidia chipset) is not included in "make defconfig" (but this does not appear to be the norm).
Just a note: an issue with the filesystem will report an error message along the lines of "VFS: not syncing".
No, that is not necessary. Worst thing that can happen is that the menu's will look weird, but all the text will be readable and accessible (I never use the LANG option myself).
A few general pointers:
- Although it would be nice to have a working/bootable kernel the first time around, this is not needed. You can always re-enter the chrooted environment and rebuild the kernel again (redo the steps in chapter 8.3.1, except the installation of the Docs).
- You mention working on a macbook: Do include the apple specific option that are present in the kernel (and not the macintosh options). From the top of my head (but there could be more) they can be found here:
-- Device -> USB
-- Device -> Graphics -> Backlight
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.