> > > Anywhere that a kernel image exists, an initrd image can exist.
> >
> > Except for very low memory diskless machines.
> >
> > sizeof(rs support + initrd support + ramdisk size) > sizeof(kernel_bootp)
^^ rd, of course
>
> Exactly my point. For me to make such a disk that I currently make, I
> basically:
>
> make oldconfig
> make zImage modules
> kmodinst <dir for modules> This is a small sh script I wrote from the
> modules_install target in the Makefile
> cp System.map /<dir>/boot/System.map-<kver>
> cp arch/i386/boot/zImage /<dir>/boot/vmlinuz-<kver>
> change to that boot dir
> rdev <kernel> /dev/nfs
> rootflags <kernel> 0
>
> foreach floppy I want to create, I cp <kernel> /dev/fd0
>
> With initrd support? Putting kernel on there would require (on a new
> floppy, above is a non issue).
It is not true. If you use zImage (kernel < 500kB) you should have >700kB
for compressed ramdisk on the same disketque (unless you use 360k/720k
floppies). It is enough.
> mkfs /dev/fd0
> mount it
> cp <file list> /floppy
> cp <kernel> /floppy
> lilo -C /floppy
You still do not need lilo. You can put ramdisk parameters directly into
kernel using rdev.
However I can't imagine ramdisk loading and starting on a machine with only
4MB RAM (eg. 386SX). Question is: mark such hardware as obsolete or keep
Linux hardware requirement as low as possible ...
Regards
Andrzej
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:25 EST