--- Adam Dutko <dutko.adam(a)gmail.com> wrote:
I tested if I could eject the livecd after gnome started. I could
originally thought I'd be able to: the disc isn't restricted from
As one might imagine, this caused my machine to lockup--hard. This
probably something we should address at FUDCon, in addition to which
modules should be included on the disk, instead of statically
I haven't seen many (large) livecds that let you eject after boot.
Basically to do so, you need to migrate the data somewhere, somehow.
I did this with a mandrake-8.0 based livecd, by having the early boot
sequence search for mountable filesystems with plenty of free space,
and if so, more or less doing a dd if=/dev/cdrom of=/path/to/cachefile.
The current boot would then no longer be dependent on the cdrom drive.
Also, subsequent boots would notice the file, and use it instead of
I also outlined another mechanism to accomplish this via a 'rebootless
I imagine there are other ways of doing this as well. I think(?) that
pilgrim supports caching to ram, which is perhaps what you were
thinking of and accomplishes that, if you have _plenty_ of ram.
One last avenue which I find very interesting is keeping the meat of
the cdrom on the network, i.e. http-fuse-cloop as mentioned here...
Or ideas I've mentioned before regarding unionfs based livecds pulling
in union layers from network filesystems (nfs/gmailfs/gfs2/etc...)
So many features, so little time... :)
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.