After 4 hours of loading a system onto a floppy, only to have it load the
600k bootfs instead of the gz'ed rootfs at 600kb, I gave up and looked at
the (2.0.28+logo) source and discovered, to my intense dismay, that no
matter how hard I tried to set ramdisk_start to 600, an initrd'ed file
system would load at offset 0. So I fixed it. And then I looked at
2.2.7, and the same feature is there.
So, here's a one line patch to enable RAMDISK_START=XXX for initrd'ed
floppy images. Am I missing something really trivial, or is this a
good candidate for wedging into the mainline kernels (patch against
2.2.9):
--- drivers/block/rd.c~ Fri Jun 4 00:21:27 1999
+++ drivers/block/rd.c Fri Jun 4 00:21:40 1999
@@ -625,7 +625,7 @@
#ifdef CONFIG_BLK_DEV_INITRD
__initfunc(void initrd_load(void))
{
- rd_load_image(MKDEV(MAJOR_NR, INITRD_MINOR),0,0);
+ rd_load_image(MKDEV(MAJOR_NR, INITRD_MINOR),rd_image_start,0);
}
#endif
____
david parsons \bi/ Imagine my pleasure at seeing the Mastodon installer
\/ instead of "can't open initial console"
-
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/