Boot on a new LFS system

Philippe Lefèvre ph.lefevre at wanadoo.fr
Wed Jul 4 09:31:08 PDT 2001


I do not unterstand something in the boot process !!

Somebody can help ??

Following the LFS book intel version 2.4.4 dated january 23rd, 2001. all

programs were well compiled.

I created this new LFS system on a separate /dev/sdc disk in order to
use it as my future boot disk. (so, it should become /dev/sda if all
goes well)

My config is:   /dev/sda = system disk  (Redhat 7, kernel 2.2.17 + LVM )
scsi ID = 0
                        /dev/sda1   *         1         9     18104
83  Linux
                        /dev/sda2            10      1019   2035150
5  Extended
                        /dev/sda5            10       986   1968624
83  Linux
                        /dev/sda6           987      1019     66464
82  Linux swap

                /dev/sdb = LVM data disk (scsi ID = 1)
                        /dev/sdb1             1      1016   4188937
8e  Linux LVM

                /dev/sdc = LFS linux disk (scsi ID = 3)
                        /dev/sdc1   *         1        10     21669
83  Linux
                        /dev/sdc2            11      1014   2178680
5  Extended
                        /dev/sdc5            11       482   1024209
83  Linux
                        /dev/sdc6           483       966   1050249
83  Linux
                        /dev/sdc7           967      1014    104129
82  Linux swap

I did mount:
        -t ext2 /dev/sdc5 /LFS
        -t proc /proc /LFS/proc
        -t ext2 /dev/sdc1 /LFS/boot
then chroot:
        /usr/sbin/chroot /LFS /usr/bin/env -i HOME=/root TERM=$TERM
/bin/bash --login

then ran lilo:
        lilo -C /etc/lilo.conf -b /dev/sdc1

lilo.conf on my LFS disk:
        image=/boot/bzImage-2.4.4-LVM
        label=LFS
        root=/dev/sda5
        read-only

lilo.conf on my "normal" system:
 boot=/dev/sda
 map=/boot/map
 install=/boot/boot.b
 prompt
 timeout=50
 message=/boot/message
 linear
 default=2217L

 image=/boot/bzImage-2.2.17-LVM
  label=2217L
  initrd=/boot/initrd-2.2.16-22.img
  read-only
  root=/dev/sda5

 image=/boot/bzImage-2.2.17
  label=2217
  initrd=/boot/initrd-2.2.16-22.img
  read-only
  root=/dev/sda5

 image=/boot/vmlinuz-2.2.16-22
  label=2216
  initrd=/boot/initrd-2.2.16-22.img
  read-only
  root=/dev/sda5

Then, I physically remove my disks sda and sdb and putting my sdc disk
as my new
sda (scsi id = 0).

Rebooting on that disk, the boot process then print the RedHat banner
with one
option to boot: LINUX and boot with a kernel which should have been
removed
from that system.

What did I do as wrong ? How is it possible that the boot process can
find the
redhat 7.0 banner and a kernel 2.2.16 which I removed before.
Notice that I have no linux label in both lilo.conf

Do you have any idea on what happen ???

Thank you in advance for any help,
Rgds,
PhiL



-- 
Unsubscribe: send email to lfs-discuss-request at linuxfromscratch.org
and put unsubscribe in the subject header of the message



More information about the lfs-dev mailing list