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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm installing LFS for the second time, this time using Slackware as a host
instead of Redhat. My problem is that I can't get lilo to see any kernel
changes in my LFS partition. I had this same problem with the first LFS
install, but got around it using Grub. However, I want to understand lilo so
I'm fighting it out.
Gerard suggested this:
"If you copy the redhat lilo.conf you must copy also all of redhat's kernel images. This is explained in the book. Look in the lilo.conf file for any and each kernel and intitrd file it might use, then copy it over. Basically, when lilo in LFS complains about a missing file, just go get the file from Redhat's /boot directory.
Or, clean out LFS' version of /etc/lilo.conf so you don't need all those other files."
And David suggested this:
"You need to sync the files on the two distros. You can euther use the same /boot partition or just copy the files over. You must sync them by having the same files in both distros /boot folder or you must run lilo from the one with the new files."
I've recompiled the Kernel in LFS, and run depmod after a reboot (Slack is using 2.4.19, and my LFS uses 2.4.18). LFS has its
kernel image under /boot, and Slackware seems to keep it under /. So under /
and /boot of both distos I have copies of both kernel images.
I've tried copying outright Slackware's /boot to LFS's. Then I tried copying
LFS's own System.map to LFS's /boot. I just don't understand how lilo works.
Then man didn't give me too much insight on my problem, nor the mini howto.
Any other reading suggestions would be great.
I've run lilo in Slackware after any changes.
Here is my lilo.conf, it's been copied to the LFS partition:
# LILO configuration file
# generated by 'liloconfig'
# Start LILO global section
lba32 # Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/hda
message = /boot/boot_message.txt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# VESA framebuffer console @ 1024x768x32k
# VESA framebuffer console @ 1024x768x256
# VESA framebuffer console @ 800x600x64k
# VESA framebuffer console @ 800x600x32k
# VESA framebuffer console @ 800x600x256
# VESA framebuffer console @ 640x480x64k
# VESA framebuffer console @ 640x480x32k
# VESA framebuffer console @ 640x480x256
# End LILO global section
# Linux bootable partition config begins
image = /vmlinuz
root = /dev/hda6
label = Linux
# Linux bootable partition config ends
# end LFS
# DOS bootable partition config begins
other = /dev/hda1
label = DOS
table = /dev/hda
# DOS bootable partition config ends
Here is how my hd is mounted:
/dev/hda6 on / type ext2 (rw) 
/dev/hda5 on /boot type ext2 (rw) 
/dev/hda7 on /usr type ext2 (rw) 
/dev/hda8 on /home type ext2 (rw) 
/dev/hda1 on /mnt/vfat type vfat (rw)
/dev/fd0 on /mnt/floppy type vfat (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
none on /proc type proc (rw)
/dev/hda13 on /mnt/lfs type ext2 (rw) 
/dev/hda10 on /mnt/lfs/boot type ext2 (rw) 
/dev/hda11 on /mnt/lfs/var type ext2 (rw) 
/dev/hda12 on /mnt/lfs/usr type ext2 (rw) 
/dev/hda14 on /mnt/lfs/home type ext2 (rw) 
Just keep this in mind: whenever you change a kernel on the harddrive and you use lilo, you need to re-install lilo in the MBR (usually this is done by simply running /sbin/lilo whenever you update a kernel image or change the lilo.conf file).
Or just use Grub. Grub is a better program in my opinion and solves a lot of problems that Lilo has.