Re: 2.3.29: ramdisk still broken.

B. D. Elliott (bde@nwlink.com)
Tue, 30 Nov 1999 00:59:23 -0800


On Tue, Nov 30, 1999 at 08:31:46AM +0000, Tigran Aivazian wrote:
> does initrd not work with BDE's fix?
>
> Bruce Elliot's fix is on my page:
>
> http://www.ocston.org/~tigran/patches/other/bde-ramdisk-2.3.29-p1.patch

Yes, initrd does work with this fix, at least well enough to use on a
rescue/recovery floppy. Some code must be deleted in init/main.c to
avoid a compiling error (see below).

HOWEVER:

Kernels built with initrd support do not boot _without_ an initrd. The
last message is "Uncompressing the kernel" (or something close to that).
In other words, the "Linux version" message never appears. This also
happens without the fix.

========================================================================
--- linux/init/main.c.orig Sat Nov 13 01:42:22 1999
+++ linux/init/main.c Sat Nov 20 02:01:44 1999
kmem_cache_init();
sti();
calibrate_delay();
+#if 0000
#ifdef CONFIG_BLK_DEV_INITRD
// FIXME, use the bootmem.h interface.
if (initrd_start && !initrd_below_start_ok && initrd_start < memory_start) {
@@ -508,6 +510,7 @@
initrd_start = 0;
}
#endif
+#endif /* 0000 */
mem_init();
kmem_cache_sizes_init();
#ifdef CONFIG_PROC_FS
========================================================================

-
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/