Richard Zidlicky wrote:
>
> this is correct and a few distributions (eg m68k) rely on that
> behaviour for installation or repair ramdisks.
Then it's easy enough for them to duplicate this kernel check in userland
at the top of /linuxrc:
mount proc proc /proc
root=`cat /proc/sys/kernel/real-root-dev`
umount /proc
[ ${root:=0} -eq 256 ] && exit 1
I have NO such luxury of a simple solution like that, with the decision set in
stone in the kernel.
> If you specify 'root=xxx' than xxx is real root that is supposed to have
> a real init and all that stuff. If that happens to be your initial ramdisk
> than there is no need to run linuxrc.
Thank you for deciding that for me.
> Why would you specify 'root=/dev/ram' if you want linuxrc to change it
> anyway? Either don't use 'root=' or set it to the value its supposed to
> have after linuxrc exits which won't be /dev/ram in normal circumstances.
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.
-
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:14 EST