On Friday 24 June 2005 23:35, Tim Warnock wrote:
> > > I wanted the ramdisk inside of the uml for performance.
> > Yes, it makes sense, and would perform better, but how do you
> > put the datas on the root_fs inside the ramfs? By copying it
> > at boot time using hostfs only.
> No im not. I was expecting the linux process to populate /dev/ram with
> the contents of the gunzipped image exactly as it would in the real
Ah, ok... I was expecting this to happen too, except that I hadn't understood
that your root_fs had been gzipped and used as initrd. And it seems that
root=/dev/ram should make it work as normal root_fs (even if I think that
trying root=/dev/ram0 is useful).
Since I've not clear what's happening here (and yes, initrd handling should
not be different from real world), here's a few ideas:
However, there are a bit of limitations in that, you're not allowed to use a
reiserfs root filesystem for this.
Also, if you use ext2 images, the blocksize when generating the filesystem
must sometimes match the one used for the ramdisk (i.e. you'll probably add
Well, in that case the only problem I can think of is that a initrd is
expected to be a bit different ... you'd need to supply a /linuxrc file
inside it. It can mount the real root and continue or boot directly the
system (I've seen both things in practice and I don't know the difference).
Also all the docs I see talk about /dev/ram0, not /dev/ram (but in the source
I see /dev/ram).
> > Are you doing that in your initrd script? Also, I think that
> > /dev/ram will
> > refer to the initrd itself (though I'm not sure).
> I'll explain what im doing. UML incorporates a very buggy driver.
> not UML's fault the driver is buggy but theres being no work done on it.
> The driver is EQL. EQL will take a whole system down if you lose two or
> more ppp slaves in one EQL schedule and theres data to be sent. So, what
> I wanted to do was use EQL inside of UML have it that if the uml process
> "kernel paniced" my script would detect and clean up and then reload the
> os again from ramdisk. No information loss because its all in ramdisk -
> designed to be volatile.
Hmm, interesting, ok. However with your design the ramdisk would be copied and
decompressed each time at UML boot, which might be undesirable (or not,
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB