[Fedora-livecd-list] LiveCD Issues

[Jeremy Katz]

On Thu, 2007-09-20 at 09:34 -0400, asmith11 at cox.net wrote:
> 1) Installing to Live Image vs. Installing to System
> 
> Is there a good way (or best practice) in my kickstart %post section
> to determine whether I am installing to a live image vs. installing to
> a system (or said differently whether the installation is happening
> via the GUI installer vs. the livecd-creator?  We have certain
> operations we'd like to perform (format some large partitions, etc.)
> that don't really make sense for the live image but we would like
> installed on the real target system as part of a "real"
> installation.  

Hrmm -- there's nothing at the moment.  But I can definitely see it
making some sense.  And being able to differentiate for pungi as well.
It would be easy enough to set an environment variable if that would
help.  I guess you could also key off of the existence
of /root/anaconda-ks.cfg for it being an anaconda install, but that's
definitely into heuristics territory

> 2) Redhat Enterprise 5 Problem
> 
> We've been able to successfully bundle RHEL5 as a live image.  Things
> are generally working pretty well.  We have been using LiveCD Tools
> 008 and 009 up till now.  When we tried to upgrade to LiveCD tools 011
> the images we created would no longer boot (in QEMU or via CD/DVD if
> burned to a disk).  The error we see at boot is the one where it says
> that "/dev/root" is missing and that we should create the link and
> then exit the shell.  This has normally been working fine.  Is this a
> problem with a missing kernel module?  Any ideas on how to fix this?

Yeah, if you look in livecd-creator, you'll see that we now write out
things like "=ata" as the modules to use.  Which won't work for RHEL5 as
it doesn't have the file to do that mapping.  At the same time, I really
don't want to have to keep around the list of all of the pata/sata
modules and have to keep updating it as the list changes over time :-/.
Open to suggestions, though.

Jeremy