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.
I'm not too sure if this will help, but have you done a clean hard reboot since making changes? If not, power down and leave for 30 seconds, then power up.
The reason I ask is that you have CONFIG_KEXEC=y, which is used for fast rebooting with the same kernel. Whilst if the kernel changes it should reload, I'm wondering if KEXEC is rebooting to the kernel held in memory, rather than the modified kernel. It shouldn't, but strange things happen sometimes.
I've just had a look at your .config file and changed a lot of settings. Try the following after saving the included .config file:
Code:
# from your host, as root:
cp /where/you/stored/downloaded/.config /mnt/lfs/usr/src/.config
# from inside the chrooted environment:
cd /usr/src/linux-3.1
make mrproper
cp /usr/src/.config .config
make menuconfig
# no changes are needed, exit and possibly safe (the make menuconfig is a precaution step)
make
make modules_install
cp -v arch/x86/boot/bzImage /boot/vmlinuz-3.1-lfs-7.0
cp -v System.map /boot/System.map-3.1
cp -v .config /boot/config-3.1
Exit the chrooted environment and re-boot, select LFS 7.0 and keep your fingers crossed!
why it's trying to enter in runlevel 3,4 and 5.it should enter in runlevel 1 because there is no X. am i right?
Nope.
LFS starts in runlevel 3 (command mode).
runlevel 5 would start X (not done in LFS, BLFS has that part).
runlevel 1 is a safe mode where almost nothing is started (bare essentials)
runlevel 2 is like 1, but network is included
runlevel 4 isn't used in (B)LFS
runlevel 6 restarts the system
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.