In article <200005261223.OAA08365@faui02b.informatik.uni-erlangen.de>,
Richard Zidlicky <Richard.Zidlicky@stud.informatik.uni-erlangen.de> wrote:
>> The idea is /dev/ram0 is not a usable root. It may not even have init.
>> /linuxrc provides a userland means to perform actions before init.
>> This is the typical mode of opertion of thin clients, thin servers, or other
>> embedded devices.
>
>do you need some sort of preinit= kernel parameter or what? Make a patch for that,
>without breaking initial ramdisks
Dave is pointing out (correctly in some peoples opinion) that initial ramdisks
are currently broken and he would like to fix them.
One of the problems we have is that there is no concise definition as to what
the initial ramdisk support SHOULD do (and how it interacts with other popular
kernel options).
Nor is there a concise definition as to what initial ramdisk support actually
does (and how it interacts with other popular kernel options). The current
documentation file is four years old and does not completely document the
current behaviour.
We do have a lot of opinions flying about as to what people think it does or
should do. Perhaps both sides could write some documentation to support
their points of view. Then we could discuss whether changing current behaviour
is a good idea or bad.
--
__O
Fireplug - a Lineo company _-\<,_
PGP Fingerprint: 28 E2 A0 15 99 62 9A 00 (_)/ (_) 88 EC A3 EE 2D 1C 15 68
Stuart Lynne <sl@fireplug.net> www.fireplug.net 604-461-7532
-
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 May 31 2000 - 21:00:16 EST