If we get an error when installing packages after yum has set up file
logging, the unmount (and then losetup -d) can fail. This makes it so
that we don't set up the yum file logger; it doesn't really buy us
anything and closing it in the error case is nearly impossible with the
way python's logging API works. Also, don't create a directory that
we're never using.
Iam a RedHat/Fedora old-timer and wish to thank the Fedora team for the
official Live CD *gift* (ya, the zod wallpaper made that explicit;).
With a gamut of live CDs around, this one helps me feel at home again.
I have been looking for Live USB efforts off fedora and came across these:
and some notes at wish-list page inside official liveCD site (but
However since my requirement was slightly different*, i ended up creating
a GUI install script based on tweaked initramdisk etc while retaining
core/rootfs packaging power of a fedora LiveCD(-creator etc).
In essence its just a liveCD to liveUSB install script in a package.
I put it here for now:
- It lets users experience the liveCD first; then by using this
package the liveCD
experience can be installed on USB stick.
- Re-uses Fedora's mature init ramdisk/udev capability which help in optimized
wait time for USB detection during mounting USB root.
- It depends on robust livecd-creator etc tools to customize/base most of core
contents including rootfs packaging.
- Allows developers to customize the live USB to specific requirement by
simply tweaking-in sections of install script.
I'd be glad to take comments/feedback.
Disclaimer: It has been tested by just 1 (rather two) "eye-balls".
There could be untested scenario lurking. Use it with own discretion.
Did you check how much space left on the partition that containts
On 3/6/07, Sebastian Vahl <ml(a)deadbabylon.de> wrote:
> I've got just a short question: Is creating of a live dvd possible with
> the current version of livecd-creator (001-3)?
> A few minutes ago I've tried to create one. The size of the packages to
> be downloaded was 1.0 Gb. Then yum fails with an transaction error.
> There should not be enough free space on the filesystem.
> Fedora-livecd-list mailing list
Mohd Izhar Firdaus Bin Ismail
天野晃 「あまの ひかる」
Universiti Teknologi PETRONAS
ICT 2nd Year 1st Semester
A few weeks ago, I was looking for a tool to build bootable and easily
customized DVD's for archiving media and other gigabyte sized items.
>From some of the recent list postings, a few other people appear to
have similar goals. Adding the following 3 switches to a version of
livecd-creator provided a fully automated solution that I've been very
--install-root - Where the build root will be (a hardcoded /var/tmp
didn't work for my setups)
--append-files - takes multiple path args for user data to be added
in the mkisofs process
--script - post install script that fires after the build tree is
complete; passes --install-root
The post install script allowed the implementation of simple build
inheritance by applying (cp -a) successive overlay trees to the build
root. These trees are mirrors of the root filesystem, but only contain
files and directories to be added... so if a /home directory (or
symlink) were placed in the root of an overlay tree, it would be
copied to the build root automatically during the postinstall. A
script is optionally run in chroot following each overlay in order to
install additional packages or make "class" specific configuration
changes. The overlay trees contain the scripts so their sequential
appearance in the build root is automatic.
I already had a collection of scripts and "build classes" from another
project and adding the --script hook allowed me to leverage them. I
was going to add another switch that would force a shell after the
build, but found that the --script automation resolved the post
install customization issue completely.
The hacks and changes I made to the older code are incompatible with
the current version, so these switches are offered as a suggestion
rather then a patch. Although the old code is working well for me,
perhaps others could benefit from this added flexibility in a future
BTW, the livecd-creator code was easy to work with and the overall
package does an amazing job... thanks much! :)
I'm sorry to re-post about this but I thought it might be possible
that somebody might have some new insights.
I'm working on a project where I want to customize the content of the
home directory - i.e. put some media files in to it. The project I'm
working on is to create a DVD for promoting Free Culture (i.e. Free
Software, Creative Commons, Public Domain etc): as part of it I plan
to include a live cd on the disc and I would love to use Fedora for
this. As it stands I think I'll probably end up using Knoppix because
there's a very straight forward method to stick some files on to the
desktop - any help would be hugely appreciated!
I brought this question up at fudcon, and it relates a bit to this
yum patch, and a bit to your kickstart patch. Really its a bit more
like 2 questions.
1) Do you forsee the system installation code within anaconda and
livecd creator merging at any point, or staying divergent? Phrased
another way, do you ever see something like anaconda --rootpath
replacing the installer code in livecd-creator? (or just generally
coming to a point where there is a single code path to install
generated system images)
2) Where do the spin differentiation / configurations exist in relation
to pungi, and how do you see these relating to _livecd_ spin
differentiation/configurations (which I visualize currently as
differing kickstart files).
I suppose one issue that would clarify both of these, would be the
theoretical possibility of something like the current livecd installer
replacing the traditional anaconda install mechanism. Were that to
happen, then it seems like the spin differentiation / configuration for
the major spins, would just be different kickstart files. Do you see
things going in this direction, or some other direction?
8:00? 8:25? 8:40? Find a flick in no time
with the Yahoo! Search movie showtime shortcut.
I've just one note and one question:
1. live-cdreator should fail if "--fslabel" contains more than 32
characters. If this is the case mkisofs will fail creating the iso.
2. Are there plans to allow a different temporary directory
than /vat/tmp/livecd-creator? On my installation I normally do not have
2-2,5 GB free space in /var/tmp but a lot of free space on different