Ollie Lho writes:
> Nikolai Vladychevski wrote:
>>
>> Jeffrey Lutz writes:
>>
>> > Hi.
>> >
>> > I want to know if it is possible to have LinuxBIOS actually contain
>> >
>> > a RamDISK image so the affect would be as follows:
>> >
>> > 1) Boot linux kernel from BIOS (disk on chip). I have this working.
>> >
>> > 2) The kernel creates and extracts a RAMDISK image from the BIOS into RAM
>> > (duh. of course).
>> >
>> > 3) Mount the RamDISK as the root filesystem (/).
>> >
>> > Has anyone done this? I would think the time to boot would be small and
>> > make the system an embedded (aka set top) system.
>> >
>> > Thoughts?
>>
>> I also need exatly this stuff. I asked on the list a few months ago, Ron
>> said he will suport this soon, but I don't know where he stayd.... If
>> there's nothing yet, I will have to do it myself.... or we could do it
>> together if you want....
>>
>> I think the way we should do it is incorporate code to kernel that accesses
>> the DoC via MTD drivers (that are compiled into) and decompresses the
>> ramdisk image that resides just after the kernel on DoC into Ram and mount
>> it as root ....
>
> Why don't you use the current scheme ?? Use NFTL on the DoC as your root
> filesystem ??
>
I have just a bad feeling about it...... I will place my mini distribution
on it and some clueless user will alter some files in /etc or other stuff,
the device will not boot again.... they will call me and say "your shit
doesnt work!".... It is kind of protection, if the / partition will be
mounted as ramdisk the end users could rm -rf everything , then shut down
and turn on the device again, everything will be reestablished like new. I
just want to hide /dev/nftla from users, of course, with proper utils and
apropiate knoledge they could errase the DoC, but if they don't know how, I
will be feeling safer....
nikolai
