I noticed that the following part of the big here-document
in creator/mayflower was not backslash-escaped (along with the
following two lines):
cat > init <<EOF
if [ -f /etc/fstab ] ; then
root=$(cat /etc/fstab | while read d m f o r; do if [ "$m" == "/" ] ; then echo $d; fi; done)
So it would end up generating hard-coded bits like this:
if [ -f /etc/fstab ] ; then
[dm_mulipath came from an earlier loop where $m iterated
through module names]
At first I just fixed that by backslash-quoting things,
but then I realized that nothing in that entire here document
required expansion, so I've attached a better patch.
The patch looks big, but it's largely mechanical:
It uses <<'EOF' rather than <<EOF, which saves you the readability
and maintenance hassle of backslash-escaping all of the "$" and "`"
in the "init" here-doc.
Just thought I should should mention... That I've finally put most of the
stuff I've been working on forever online.
This is absolutely a broken work-in-progress release, and not yet the drop in
functional replacement for livecd-tools that it will become (soon...).
The interesting things it has (but again, in no way even a respectable
development release), are-
* a livecd generation mechanism that runs without root privileges, utilizing
* a tool 'smirfgen' which is like mayflower, but much more flexible
* a live.init which is like the one embedded in mayflower, but much more
* a tool qfakeroot, which is in the spirit of fakeroot, but can do even more
stuff, such as trivially convert a tarball into an ext3 filesystem image,
without root priveleges.
Again, I don't expect this to be useful for anyone. But since I've alluded to
it about half a million times over the past couple years on this list, I
figured I'd mention the code availability.
In the near future, perhaps before I clean it up to work as a drop in
(no-root-privs-required) replacement for livecd-tools, I will try to release a
version that can at least trivially modify the official f8-livecd iso image to
support liveusb-persistence (again, without requireing root privs, via the
coolness that is qfakeroot(&smirfgen).
For now, perhaps the most interesting thing to look over, would be how I
rewrote the init (tools/ZyX-Live-OS/live.init). And then perhaps look at how I
abstracted what mayflower does, into smirfgen, and the
tools/ZyX-Live-OS/smirfgen.cfg. And then after that, realize that how those
things make qfakeroot possible. And then imagine how qfakeroot could be used
to remove all root-priv requirements from the entire fedora recompile process.
P.S.- for the love of democracy, help get Cheney impeached. I'd gladly trade a
life in paradise for one of poverty if it meant that future generations would
not inherit a world where Bill Clinton *WAS* impeached, and Dick Cheney
Be a better pen pal.
Text or chat with friends inside Yahoo! Mail. See how. http://overview.mail.yahoo.com/
I created a Fedora Core 8 live CD using the
livecd-creator tool successfully. It boots up fine
from a USB pen drive and is able to install to hard
drive. But there is a problem with the size of "/"
partition (dev/sda2) on the hard disk. The commands df
and fdisk report different size.
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 4.0G 2.7G 1.3G 68% /
/dev/sda5 26G 209M 24G 1% /var
tmpfs 252M 12K 252M 1% /dev/shm
fdisk /dev/sda -l
Disk /dev/sda: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0005e0df
Device Boot Start End Blocks Id
/dev/sda1 * 1 25 200781 83
/dev/sda2 26 1299 10233405 83
/dev/sda3 1300 1430 1052257+ 82
Linux swap / Solaris
/dev/sda4 1431 4865 27591637+ 5
/dev/sda5 1431 4865 27591606 83
I noticed that the layout of my "/" paritition is same
as /dev/mapper/livecd-rw on the live image. Looks like
liveinst created a wrong partition table somehow when
dumping the image to my hard disk. I have not seen
this problem before on FC 7. Is this likely a bug with
liveinst or livecd-creator? Or I just messed
I created the FC8 live cd on a FC7 system. Because I
only have 1.9 GB free space after installation, I do
not have enough space to create a live CD from the new
FC8 system. So during the installation, I created a
custom layout that puts /var onto /dev/hda5 (a 24G
partition). I thought that would give livecd tool
enough temp space to work with. But I got an error
Error creating Live CD : Unable to install:
[('installing package glibc-common-2.7-2 needs 33MB on
33722368L)), ('installing package
gnome-backgrounds-2.20.0-1.fc8 needs 34MB on the
35389440L)), ('installing package
rt73usb-firmware-1.8-4 needs 34MB on the
35401728L)), ('installing package words-3.0-12.fc7
needs 39MB on the
system-config-keyboard-1.2.11-3.fc8 needs 1806MB on
1893142528L)), ('installing package
anaconda-126.96.36.199-2 needs 1823MB on the
1910513664L)), ('installing package
system-config-boot-0.2.17-1.fc8 needs 1823MB on the
Failed to build the live image!!!
Some of those size are nonsense to me, e.g.,
system-config-boot-0.2.17-1.fc8 needs 1823MB???
Can anyone explain what went wrong? Any help would be
appreciated. Thank you.
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
On the main Fedora list there is a post saying that a minimum install CD
set is 3 - would it be possible to boot from CD1 and finish the install
from a Live CD tree on another drive?
Pricom Pty Limited (ACN 003 252 275 ABN 91 003 252 275)
GPO Box 3411
Sydney NSW 2001
Sorry to ask directly to you, but I asked some questions
to the Fedora Project group, with no succesfull answer.
My name is Thiago Santana and I doing a derivative of
Fedora LiveCD for a Point of Sale application.
I need to understand a little bit of the Ramdrive
conceptual framework used by you in 'Fedora 7 LiveCD'.
There is a file system mounted on the root directory
("/"). How the system is it able to distinguish the
programs previously recorded on the CD image from files
and programs created by me?
If I understand correctly, some files are stored in RAM,
but I didn't get how the file system manages the
available storage space. I want to know how to calculate
the RAM space I need for my files.
Furthermore, it appears to be that when I open some file
from the image for editing, the full contents of the
file is copied to RAM. Is that the case? If it is so,
what happens if I open a great number of files?
I will be waiting for your response.
Thank advance your information.
My best regards,