Just for the fun, I would like to offer a free service for next few
days on experiment.
Basically this is a customized and personalized LiveCD On-Demand for your need.
You tell me what you want on the CD and I'll *try* to build it in 24 hours.
It will be based on the official Fedora 6 LiveCD + your own selection
It will also include the most current updates from Fedora 6 Updates Repository.
The package must come from Fedora 6 Core or Extras Repositories.
Sorry, NO priority package on this experiment please. :)
Any one interested in?
ps. I'll even ship it for free if you're located in US.
When try to build a customized livecd, I see there are error messages
about "sata" & "usbhid" modules.
In script "livecd-creator", there is :
# Create initramfs
# modules needed for booting (this is butt ugly and we need to
retrieve this from elsewhere, e.g. the kernel)
mayflowerconf = open(self.build_dir +
mayflowerconf.write('MODULES+="cdrom ide-cd ahci loop
dm_snapshot squashfs ext3 ehci_hcd uhci_hcd ohci_hcd usb_storage
sd_mod sr_mod usbhid ata_piix "\n')
mayflowerconf.write('MODULES+="sata_mv sata_qstor sata_sis sata_uli"\n')
mayflowerconf.write('MODULES+="sata_nv sata_sil24 sata_svw sata_via"\n')
mayflowerconf.write('MODULES+="sata_promise sata_sil sata_sx4
I have to add a space at the end of two lines:
mayflowerconf.write('MODULES+="sata_mv sata_qstor sata_sis
mayflowerconf.write('MODULES+="sata_nv sata_sil24 sata_svw
and all errors related to "sata" modules disapear. But there is still
error message about "usbhid" module. I don't know how to fix that.
Maybe because of missing of this module in kernel (I use
In spite of this error message about "usbhid" module, the cd works well :)
I installed to my sata hard disk using the alpha installer using the
"whole disk" option on /dev/sda. After installation the system boots and
works fine but when I see the /dev/sda2 partition info it shows as 3GB
in size with 70% usage (i.e. through gnome or du). When I look at the
physical drive through Gparted I see the partition as the correct size
of 190 GB.
Am I missing something here?
David Zeuthen and the Live CD Team:
I think it would help promote the Fedora Live CD efforts if there was
a HOWTO (based on the README) which could be easily referenced
and updated as needed in the Fedora Project wiki.
In order to do this, I converted the README for the Live CD Tools into
a formatted wiki entry under my sandbox,
I would like to move it to
I am willing to track changes in the Live CD process and update the wiki
accordingly. Please let me know if you agree and I will link the HOWTO
under the FedoraLiveCD entry and take responsibility to keep it up-to-date.
Volunteer, Fedora Docs Project
See inline comments..
On 1/14/07, Thomas Chung <tchung(a)fedoraproject.org> wrote:
> On 1/14/07, Amir Sela <amirse(a)gmail.com> wrote:
> > Hmm, I managed to create my own custom CD's, thanks.
> > My question was a theoretical one. I simply don't understand why
> > 10- and 20- do their configuration in different ways. 10- just does
> > a bunch of things in the post) script itself, while 20- creates
> > /etc/init.d/livecd and puts all the stuff in there, and then deletes it? :S
> > Thanks,
> > -Amir
> It's my understanding from README that 10-fedora-livecd-base.conf
> just puts a basic packages and configuration to build a minimum
> install. 20-fedora-livecd-gnome.conf put additional packages and more
> gnome-specific configurations on top of the base. So yes
> fedora-livecd-gnome rpm *requires* fedora-livecd (-base) rpm package
Hmm, I've read that README, and I've read the 10- and 20- files themselves.
I never really asked anything about package dependenceis. It's pretty
obvious from the readme that 20 is an addition to 10, and as such requires
it. It's the hierarchical nature that the livecd-creator developer wanted to
create (Which is quite elegant and cool). Nevertheless, I really don't have a
a problem with package depenedencies.
> during the LiveCD build process. It seems /etc/init.d/livecd is a
> temporary init script to perform various configuration during LiveCD
> build process and removes itself when it's completed to clean up.
Yes, I didn't ask about how it does things. That is obvious from reading the
script itself. I'm asking *why*. Because if one were to tell me that
/etc/init.d/livecd is created in 20 in order to configure the livecd when
it actually boots, I would say '"oh, ok. makes sense". But that doesn't
go well with the fact it gets deleted in the post) segment in 20. Not to
mention the fact that it really doesn't run in the post) segment per-se.
It just gets created using a "here document" clause. So when does
it actually run is what interests me, and why it's implemented like
this. I guess we'll just wait for someone else to explain it :)
> I hope I answered your questions otherwise we might have to wait for
> David who's currently on trip to LCA (linux.conf.au)
Not really, sorry. :)
We'll just wait for David. It's not that critical. I'm already working
livecd-creator. It just bugs me I don't understand that part.
Thanks a lot for the prompt replies!
>  http://gitweb.freedesktop.org/?p=users/david/livecd-tools.git;a=blob;hb=H...
>  https://www.redhat.com/archives/fedora-livecd-list/2007-January/msg00064....
> Thomas Chung
I've been trying to figure out the way livecd-creator works, and generally
it's going well, other than one thing. The way I understood it, the post)
segment runs to configure the livecd once it's created. That makes sense
to me and I plan to implement it myself. This is how it works in
10-fedora-livecd-base.conf. But why does 20-fedora-livecd-gnome.conf has
this elaborate scheme of creating /etc/init.d/livecd inside the livecd, and
then deleting it? I assume this runs somehow, but first of all I don't see how
it runs (init.d scripts, AFAIK, run when you actually boot the system, and since
it gets deleted in the next sections and removed from /etc/rc?.d, why would it
run?). Second, even if it does run (which it obviously does), why implement it
like that and not like 10-fedora-livecd-base.conf script?
I hope I'm making some sense... To make it short and sweet - it looks like
there's an implementation difference between 10 and 20 and I don't see why,
or how it works in 20..
Any explanations would be great.
Thanks a lot,
Ok. Here is a link to the patch I will submit tomorrow after my testing is
finished: http://littlehat.homelinux.org:8000/livecd-creator . (I will
submit the diff from git to the mailing list when my testing is finished.)
As I indicate on my site this version does the following...
"I've added a flag to livecd-creator that you can use to dictate where to
build your livecd. Of course this will not eliminate the actual iso being
generated in your present working directory. If you do not specify the
--build-dir flag when you call livecd-creator it will use the old default of
using /var/tmp/livecd-creator. The main improvement, beyond the addition of
the --build-dir flag is the space check. This new version of livecd-creator
will verify you have at least three gigabytes of free space before
continuing. If you don't it will quit and ask you to add more space, or
specify a different directory."
So far my test of building a livecd with the modified script worked fine.
I'm now in the midst of testing both permutations: 1) specifying a build-dir
(this is the 2nd run -- my first successful I used this) and 2) not
specifying. I've verified that if I have less than 3000M in the target
directory, it fails nicely and reminds the user to add space. I will post
logs on my site as well when I get the chance.
David, I know you objected to the addition of a build-dir flag, but I
figured it fit well with your feature request and added it in. If you don't
want it in there, I will remove it and simply submit the space check.
Please let me know.
I will start hacking on other pieces tomorrow. Unfortunately school starts
Monday so my hacking time will be limited, but I want to get a few more
things ironed out in the code (specifically things you've mentioned inline).
Excellant work. I got this working on my friends computer (loaded to
ram) now I am installing on mine. I managed to mess up my fc6 install
so this is fantastic. There are somethings missing here and there
(option to install grub in a different location etc.) I assume this
will be delt with later also the gui, I assume is expected. I might be
able to help with that, so if you need anything. I think I might (if I
don't get bogged down by life and school) go ahead and make a mock up
and show it to you guys, I know you guys are busy and may appriciate
the help (unless you have your own idea and want to do it a specific
way). In any case enjoy your trip and thanx again to all involved!
Has the install to hard disk option/script (rpm) been released yet for
FC6 Live? I'd love to install FC6 on my AMD64 system (MSI K8T Neo2)
which is hampered by the sata_promise problem on the FC6 release DVD so
I can't install from there. The FC6 Live CD works like a charm however
as the kernel and sata_promise driver has been updated.
Some minor fixes follow, mostly text tweaking and a bit of Makefile cleanup.
BTW, usually the SPEC files (why not include it here?) I've seen handle the
installing of documentation and so, so this shouldn't be done in the
HACKING | 1 -
Makefile | 14 ++++--
README | 96 ++++++++++++++++++++++--------------------
creator/Makefile | 19 ++++++++
installer/Makefile | 8 ++++
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de Informatica Fono: +56 32 2654431
Universidad Tecnica Federico Santa Maria +56 32 2654239
Casilla 110-V, Valparaiso, Chile Fax: +56 32 2797513