[Clfs-support] lilo
Ken Moffat
zarniwhoop at ntlworld.com
Fri Apr 3 04:49:27 PDT 2009
On Fri, Apr 03, 2009 at 12:47:58AM +0000, Koornstra, Reinoud wrote:
PLEASE, STOP TOP-POSTING
> I did the following:
>
> Cp ${CLFS}/boot/clfskernel-2.6.28.8 ${CLFS}/boot/clfskernel
> Cp ${CLFS}/boot/System.map ${CLFS}/boot/map
Did you find anything in google ? I no longer recall exactly what
the map file does, but it has nothing to do with System.map.
>
> Mount --bind /proc ${CLFS}/proc
> mount --bind /dev ${CLFS}/dev
> mount --bind /sys ${CLFS}/sys
>
> Then lilo -v -b /dev/sdb -r /mnt/clfs
> Output:
>
> Lilo blablabla
> Ignoring entry 'boot'.
> Reading boot sector from /dev/sdb
> Warning: /dev/sdb is not on the first disk
> Using MENU secondary loader
> Calling map_insert_data
>
> Boot image: /boot/clfskernel
> Added clfs *
>
> Writing boot sector.
> Backup copy of boot sector in /boot/boot.0810
>
> Does this sound ok?
As I said, I'm not familiar with the details of putting lilo onto a
second disk and using that to replace the original. Certainly, it
has written a boot sector with the location of the clfs kernel onto
one of your disks, so it seems reasonable.
> So, next I should go to building the CLFS system?
> Nowhere is mentioned that I can reboot into the currently build system in ${CLFS} before going to section 9.
> I guess I couldn't even reboot because there's only console and null in ${CLFS}/dev ?
> Please advise what the best thing to do is.
> Kind Regards,
>
> Reinoud.
>
If you are taking the "boot" route, you have no choice but to
reboot. Devices other than console and null are created by udev.
ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
More information about the Clfs-support
mailing list