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,
> 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.
-- _________________________________________________________________________ / Werner Almesberger, ICA, EPFL, CH firstname.lastname@example.org / /_IN_N_032__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed May 31 2000 - 21:00:15 EST