On Sun, 22 Apr 2001, Statux wrote:
> Two options:
>
> 1) dd if=kernel_image_filename of=/dev/fd0 bs=1440k
You also need to run rdev /dev/fd0 <root directory>
> 2) mkbootdisk --device /dev/fd0 kernel_image_filename
>
> These two options aren't the same, though. The first will put the kernel
> on a floppy in a raw sort of way. Used to boot kernel from the floppy
> instead of off the harddisk. After the kernel is loaded, the system picks
> everything up. If this is all you want, then it's a nice fast solution.
>
> The second option is much slower at boottime, but it makes a mini system
> on a floppy to get the system booted with no extras. Used for rescuing a
> system, usually. When the system boots up this way, Linux runs off the
> floppy (as opposed to the first option which only pulls the kernel off the
> floppy and boots normally).
>
> There are uses for both. Is it worth making one of each? Maybe.. maybe
> not. Always good to have a rescue disk, but on a dual boot system without
> LILO in the MBR, the first option is tastey :)
>
Your version of mkbootdisk must do things different then the version I
have, because the only differences between the first version, and a boot
disk made by mkbootdisk is the fact that it uses lilo, so you have a
chance to pass options to the kernel, and that it creates an initial RAM
disk, with any modules you need to mount the root file system. You
still are running off the hard drive, using it for the root file system.
Mikkel
--
Do not meddle in the affairs of dragons,
for you are crunchy and taste good with ketchup.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
