Ollie Lho <[EMAIL PROTECTED]> writes:
> Nikolai Vladychevski wrote:
> >
> > Hi again,
> >
> > now I am trying to burn to my DoC a compressed root filesystem (just
> > after the kernel image) and I want the kernel to boot this filesystem
> > decompressing it to ram. I made my ramdisk and , burned it after the
> > kernel image previously doing "rdev vmlinux /dev/mtdblock0" and "rdev -r
> > vmlinux 960 (my offset)" on it but the kernel seems to ignore it (I get
> > "I have not root and I want to scream"). I also added /dev/mtdblock0
> > major and minor data to the array in init/main.c but it is not a big
> > help. I am now hacking into the kernel and looking the internals and
> > after 2 days a question picked up in my mind.... Has anybody done this
> > before? And if so, how? I feel like I am loosing completely .....
> >
> > Thanks in advance.
> >
> > Nikolai
>
> I don't think you can do that. There was somebody working on using
> ramdisk
> but I did not hear any good new form him. The usually practice here is
> use /dev/nftla to host a CRAMfs image.
Ollie. Using a ramdisk works fine. The recipe for using a ramdisk is to
build linuxBIOS with support for booting an ELF image. Then use
mkelfImage to package the ramdisk, a kernel, and a command line into a
single ELF image.
Using the DOC directly as root instead of playing with a ramdisk
generally looks better, as it can be read/write, and you don't waste
storage. But the ramdisk case works fine.
Eric
