I have a PXE boot environment set up for installing Fedora/RHEL. Has
anyone looked at making the LiveCD loadable from the network? If not,
are there any pointers that might help?
Chris Adams <cmadams(a)hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
I'm putting together a feature enhancement patch for livecd-tools, that
will basically just allow multiple instances of --config on the command
line, and then build something that is the same as if one --config
option was used on a kickstart file that is the appended contents of the
multiple specified kickstarts.
This came about because I was considering the biggest differences
between the VirOS livecd generation tool I'm working on for myself, and
livecd-creator. non-root was the top thing, but the 2nd biggest thing
was just my whole dna/virus/gene/trait metaphor. I.e. building livecds
with a mix and match collection of traits, from a library of preexisting
And then I realized that just implementing the above, brings that type
of methodology to livecd-creator. Yes, of course you can do this
manually with cat appending or kickstart including. But I think the
implementation is so simple, and the functionality useful enough, that
its worth doing.
The next thing after that, which would be a bit tougher, is the idea of
passing variables to the kickstart files. Maybe already the post
scripts can pull in environment variables (haven't tried it), but I
think it'd be better if you could specify some variables/define-macros
on the command-line, and more or less have them sed-replaced in the
To give an idea of kind of where I'm aiming, something like this-
The result would be that instead of the current user that gets
autologged in being named 'fedora', it would be named 'guest'.
Anyway, the define bit may be tricky, but I'll try to get together a
simple patch for the multiple kickstarts in the next couple days.
As the subject line says- comments requested.
Running livecd-creator is apparently wiping out /dev on my F8 machine.
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
I'm currently working on my livecd generator, and making it compatible
with the kickstart format that livecd-tools expects.
My method involves a traditional anaconda network install going under qemu.
So here is what I noticed when I tried feeding a flattened version of
The main problem, is that no install method is specified. For now, I'm
just going to do a little parsing, taking the first repo line, and
converting it into
With a manual wget and selection of a random mirror if mirrorlist is
I'm thinking that livecd-tools might be better off requiring the install
method syntax anyway, and basically setting down the idea that the
kickstarts that it accepts, should be usable as generic kickstarts for
installation in the traditional way.
Other than that, the only other thing I think I noticed was that it
failed to go completely automated due to lack of specified root password
entry. Again, I'd suggest explicitly requiring that entry.
If the only issue is who will actually make the modifications, I am of
course willing to do that work. But I won't go ahead unless it's agreed
it is the right thing to do.
Chris Negus, who authored on book on Linux live cd's that covered
Kadischi now has a very comprehensive article on Fedora livecd-creator.
Check it out.
"The Fedora project has added a powerful tool to its Linux distribution
to build your own live CD. With a single livecd-creator command and a
kickstart file listing the software you want, you can create a desktop,
gaming, or Web server to run live on most PCs. This article gives
details of how to do that."
On Saturday 19 January 2008 2:04 pm, Tim Wood wrote:
> So, dcw would do this:
> %post -nochroot
> cp /etc/resolv.conf > /$INSTALL_ROOT/etc/resolv.conf
Do not use the / before $INSTALL_ROOT. The above example would then be:
cp /etc/resolv.conf > $INSTALL_ROOT/etc/resolv.conf
> Jeremy Katz wrote:
> > On Sat, 2008-01-19 at 13:39 -0600, dcw wrote:
> >> Using livecd-creator (ver. 13-4) I have made a livecd with a recompiled
> >> kernel and it boots and works. I am now at the point of copying some
> >> configuration files from the hard drive to the livecd using the
> >> livecd-creator program.
> > [snip]
> >> I have not been able to determine what 'somewhere' should be.
> > /mnt/sysimage is only relevant for anaconda installs -- creating live
> > images on a real system, we can't guarantee that /mnt/sysimage exists or
> > is being used for this purpose. Thus, you can instead use
> > $INSTALL_ROOT. Which iirc, I also added to anaconda in F8
> > Jeremy
> > --
> > Fedora-livecd-list mailing list
> > Fedora-livecd-list(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-livecd-list
RD Woodyard, Inc.
on Saturday 19 January 2008 2:15 pm, Douglas McClendon wrote:
> dcw wrote:
> > Using livecd-creator (ver. 13-4) I have made a livecd with a recompiled
> > kernel and it boots and works. I am now at the point of copying some
> > configuration files from the hard drive to the livecd using the
> > livecd-creator program.
> > The following method works:
> > %post
> > echo "nameserver 10.10.2.99" > /etc/resolv.conf
> > but I would like to use:
> > %post -nochroot
> > cp /etc/resolv.conf > /somewhere/etc/resolv.conf
> > I have not been able to determine what 'somewhere' should be.
> > I have never programed in python but I have looked through the
> > livecd-creator program and made several 'best' guesses but I have not
> > found anything that works. I have also searched the internet and I have
> > found nothing that addresses this.
> > The documentation on
> > http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/sysadmin-guid
> >e/s1-kickstart2-postinstallconfig.html says to:
> > %post --nochroot
> > cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf
> > /mnt/sysimage does not exist.
> > Any help will be greatly appreciated,
> Yeah, documentation is lacking right now. I see that Tim and Jeremy
> answered this while I was pasting this mail together, but since this
> response adds a bit more, I'll go ahead and send it.
> Here is the same help I just gave Mike Dickson a couple days ago-
> 1) to add some arbitrary file (300M mpeg) to the resulting LiveCD ISO
> in your own config/kickstart, you can add a section like the following
> (note, you can just add this, as there can be multiple of these %post
Thanks for your quick response. Knowing that there can be multiple %post
sections will be useful.
> %post --nochroot
> mkdir $INSTALL_ROOT/usr/share/extramedia
> cp /home/mdickson/some.mpeg \
> mkdir $LIVE_ROOT/momedia
> cp /home/mdickson/someother.mpeg \
$LIVE_ROOT is also good to know.
> Note, the first part, will add the file to the root filesystem that is
> visible when you boot up the livecd/usb. And as a result will be
> compressed during the build process (but obviously not well, as mpeg is
> already compressed as much as it can).
> The second part (using LIVE_ROOT instead of INSTALL_ROOT), will add the
> file to the cdrom filesysem, uncompressed. As such, the user could for
> instance easily see the file if they dropped the cdrom into a windows
> system (on the cdrom, under the top level folder 'momedia').
> Fedora-livecd-list mailing list
RD Woodyard, Inc.