> |> 1) Boot the system in Linux using the bootdisk.
> |> 2) Mount the DOS partition (this should be within 1024 cylinders
i.e.
> |> 3) Move the /boot to /dos/boot : cp -a /boot /dos ; rm -r /boot
> |> 4) Create a symlink for LILO to find at boot: ln -s /dos/boot /boot
> |> 5) Move kernel (i.e. /vmlinuz) to /boot/vmlinuz: mv /vmlinuz /boot
> |> 6) Edit /etc/lilo.conf to change /vmlinuz to /boot/vmlinuz
> |
>
>
> How the /dos/boot directory will be available before kernel boots up.
> A small correction here.
> Boot in to dos partition and run loadlin.
>
well if the vmlinuz is in /boot of the linux partition, how will it be
available
before loading kernel and mounting /boot ?
so, the file system specifics AFIK is needed only when lilo is updating the
boot sector.
The proceedure of bootstrapping is more or less as follows
the bios reads 512 bytes of boot code, and executes this, which
contains only a loader for lilo transient program, which in turn
provides ui and gets user choice and executes more programs,
but these programs, like kernel, or boot time options cannot
be fit into the boot sector (it will hold only 512 bytes). Hence
it has to be loaded off the harddisk directly, and since the logic
provides that no file system specific has been loaded at the time of
starting kernel, I assume that lilo just transfers execution to the start
portion of the kernel, which contains the code to load and run the whole
kernel.
I hope this provides an explanation for putting kernel any where.
----------------------------------------------
The mailing list archives are available at
http://lists.linux-india.org/cgi-bin/wilma/linux-india-help
