I am trying to build a Live CD of RHEL5. I prefer to build a 5.2 Client
on i386, but so far only have the media for 5.1 Client on x86_64, so
have tried building for that (5.2 Client on i386 still downloading :) ).
I'm using F9 on x86_64 to build this.
I'm having problems though - the image builds, but upon attempting to
boot it, the grub screen appears and only contains "Boot from local
drive". Hitting return fails to get me any further. I've tried this by
running the ISO as a virtual CD in a KVM guest (in which case I get the
error "FATAL: INT18: BOOT FAILURE"), and also using livecd-iso-to-disk
to put the image onto a USB pen and attempting boot it on another system
(in which case the boot gets no further, but no error).
Has anyone seen this before? I can provide a copy of the ks file I am
using, along with a transcript of the build process. Any suggestions
here would be greatly appreciated.
I am working on a specialized console-based livecd, and want to include my custom kernel.
I have the rpm for the kernel in a local yum repository.
I include my local repository in my kickstart file, but when I run livecd-creator, it tries to pull the latest kernel from the release repository not my custom kernel.
Is there a way to tell livecd-creator to use my custom kernel?
Donald Raikes | Accessibility Specialist
Phone: +16028246213 | Fax: +15207440826 | Mobile: +15202717608
Oracle JDeveloper QA
ORACLE United States | | Tucson, Arizona
"Please consider your environmental responsibility before printing this e-mail"
I'm using a LiveCD generated by the livecd-tools. Sometimes during our testing it would be handy to view/modify the kickstart script that will be used by the live-cd installer (Anaconda) at local-disk-install-time.
In other words, we would like to be able to do the following:
1) generate a livecd
2) burn to a CD/DVD
3) boot the CD/DVD in a target machine
4) view/modify the kickstart script (e.g. tweak a few install or post-install actions)
5) launch the installer
6) install to the local hard drive
Can someone tell me where the kickstart file is stored on the livecd image?
I would like to say "Thanks" to all who have contributed to this project and any open source project.
Is it possible to encrypted the Live CD like you would a hard drive? If yes, could you point me to some documentation on it or give me an idea on how to go about doing it. I have done some reading on encrypting, but being so new at this, I not sure how to go about it. If it is not doable, please let me know.
This is to resolve RH bug #458803
imgcreate/yuminst.py | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/imgcreate/yuminst.py b/imgcreate/yuminst.py
index a7b04b6..628b0cd 100644
@@ -103,8 +103,8 @@ class LiveCDYum(yum.YumBase):
# dict so that things don't get pulled back in as a result
# of them. yes, this is ugly. conditionals should die.
for req, pkgs in self.tsInfo.conditionals.iteritems():
- if x in pkgs:
+ if x.name in pkgs:
self.tsInfo.conditionals[req] = pkgs
logging.warn("No such package %s to remove" %(pkg,))
Fedora -- Freedom² is a feature!
Spin Maintainers, may I please have your attention.
To be included in the Fedora 10 release cycle, you'll need a Feature
page in category ProposedFeature (and change that to the
ProposedFeatureF10 category when you feel the Spin Concept is ready for
actual inclusion). This page should be ready (eg. prepared) before the
The Feature Page for that spin should have a short description of the
spin concept, it's target audience, any notes you want to write down on
why it is you do foo or bar. It should also contain a link to the
kickstart, but since a mailing list is still pending, I suggest you
email it to fedora-livecd-list(a)redhat.com. The Spin SIG picks it up,
does a technical review, and sends you the OK or comments. If the Spin
SIG approves, your kickstart will be added to the GIT repository for the
appropriate branch(es). At this point, it'll be forced to use
"generic-logos", still. The Spin SIG will work with you to fit in the
kickstart into the pool, get some things right or more right, and while
you -by then at least-, should also have commit "access to the GIT
repository", the spin concept will continue it's path to the Board
for trademark approval. Make sure that before this happens, you have
some kind of strong argument in favor of the spin so they just can't say
no. It makes all our lives easier ;-) Once you're kickstart (spin
concept) has the almighty Board trademark approval stamp, we change
"generic-logos" back to "fedora-logos".
The kickstart should be built upon fedora-live-base.ks in the
spin-kickstarts repository at:
This GIT repository has several branches: master, and a very distinctive
branch for each live release of Fedora out there. Naturally, the master
branch is where development goes against rawhide, and the release
specific branches is where you have a chance to maintain your spin
concept for the duration of the lifecycle of that release.
Basing on fedora-live-base.ks may be deferred from such as with the
Electronic Lab DVD spin: it bases itself on the KDE CD spin so that
minimal overhead in duplicate configuration and scripts is accomplished.
You may do the same; as long as you make sure you tell us in your
Feature page or technical review request. And if you don't tell us in
your Feature page, I'll read it from the kickstart anyway.
For now, you are requested to start filling out your spin's Feature
page, get them to the Spin SIG (members are on ), request access to
the gitspin-kickstarts group in FAS, and start composing every two
weeks or so, to verify rawhide hasn't changed too much.
To watch commits to the spin-kickstarts GIT repository, subscribe to the
I'd love to see you all come back to me in the next week or so ;-)
Thanks in advance,
Jeroen van Meeuwen
 http://fedoraproject.org/wiki/SIGs/Spins (members, guidelines, DOs
Just a quick question, with the version that was shipped with F8
--base-on= would work just fine, I could see the squashfs mounted with
mount. The one on F9, appears to ignore this option as I can't see where
the old squashfs is mounted when I call mount like I could with F8. Is
this a bug or something that has not setup with the changes to the way
livecd-creator works with F9?