Yeah, eject is apparently looking in /block/sys to check for the 'removable_media'
flag for the specified device... and it's assuming the device name isn't a
symlink.
-Mike
---
Michael D Labriola
21 Rip Van Winkle Cir
Warwick, RI 02886
401-316-9844
-----Original Message-----
From: Jeremy Katz <katzj(a)redhat.com>
Date: Mon, 16 Jun 2008 13:53:43
To:fedora-livecd-list@redhat.com
Subject: Re: [Fedora-livecd-list] Boot to RAM
On Mon, 2008-06-16 at 16:20 +0000, mdlabriola(a)yahoo.com wrote:
Does the current Fedora Live CD support loading the rootfs to RAM? I
thought I remembered that as a boot option in some of the earlier releases (Fedora 6?).
The code is still there. It's not exercised much, though. We removed
it from the menus as it can be pretty confusing to do reliably (how much
RAM is "enough")
I googled a bit and found reference to a 'live_ram' command
line arg and tried adding that and booting, but I get the following error:
Yep, that's the trick
Done copying live image to RAM.
eject: did not find a device /dev/root in /sys/block/
Sounds like a bug in eject -- it should follow the link and then do the eject
Jeremy
--
Fedora-livecd-list mailing list
Fedora-livecd-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-livecd-list