Re: [PATCH] 5 year old bug in main.c (initrd). Can this please be fixed?

From: Werner Almesberger (
Date: Thu May 25 2000 - 20:40:08 EST

Dave Cinege wrote:
> Again, one needs to jump through hoops,

"Hoops" are much more acceptable than "preclude".

>> It's "initrd is always magic" and "/linuxrc is there to do that
>> root change thing" vs. "A RAM disk root is a regular RAM disk root
>> no matter how you load it".
> Please rephrase that, since root=/dev/ram1 won't exhibit this.

Not quite sure what you mean. initrd should always end up on /dev/ram[0],
no ?

> I'd say the REMOTE CHANCE of that is NULL. Why would you have an initrd image,
> with /linuxrc, and not want to execute it?

Agreed on remote chance. Not sure about null. Examples:
 - really wicked stuff that changes behaviour depending on context
 - somebody's left a /linuxrc by accident

> For MONTHS I was trying to use /linuxrc, before I took the time to go
> through the kernel code and figure out why it wasn't working.

Sorry :-(

- Werner

 / Werner Almesberger, ICA, EPFL, CH /

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to Please read the FAQ at

This archive was generated by hypermail 2b29 : Wed May 31 2000 - 21:00:15 EST