livecd May 2007

livecd@lists.fedoraproject.org

37 participants
41 discussions

building an automatic installer with livecd-creator
by Holger Levsen 09 Jun '07

09 Jun '07

Hi, I'm trying to build an installer-cd with livecd-creator :) So I finally succeeded to build a livecd with livecd-creator under fedora7. When I boot this CD, I switch to the text-console, log in (into textmode) as root, run /etc/init.d/messagebus start /etc/init.d/haldaemon start and run the liveinst.sh script from anacondas CVS anaconda/liveinst/liveinst.sh (downloaded with curl.. for now) (I plan to put these steps into /etc/rc.d/init.d/fedora-live but for debugging it's easier to run them manually.) Then I configure anaconda manually (currently just using the defaults, which, again, I later plan to do with a kickstart file) and anaconda successfully partitions the disc and copies the system from the livecd to harddrive. But in the end the installation fails, log is attached. I would be happy if someone who is more familar with anaconda logs can tell me what went wrong... regards, Holger

3 21

Targetting other file systems besides iso
by John (J5) Palmieri 06 Jun '07

06 Jun '07

At OLPC we need to support ext3 and jffs2 builds even more so than livecd isos. Since most of the process is the same up until the final image and bootloaders we would like to add this support into the livecd tools so that all fedora projects use one toolchain. The question is how can this best be accomplished? I think passing a --variant switch (i.e. --variant=jffs2) should switch the backend to generating the correct image. This also requires template support and the ability to select templates to write out based on the variant in the %post. For instance the olpc.fth file is read in by the openfirmware. For jffs2 builds we point to the nand on the XO machines. For ext3 we point to a USB disk. Also on ext3 we write out grub entries for use with standard machines and vitalization software like qemu. What would be the best way to add this support to the livecd tools? -- John (J5) Palmieri <johnp(a)redhat.com>

5 7

Fwd: Error in livecd-creator
by John Babich 31 May '07

31 May '07

The following request was sent directly to my email account. See below for the full message. To summarize, there is an alleged bug in Live CD and I was asked to make a correction to the wiki page, http://fedoraproject.org/wiki/FedoraLiveCD/LiveCDHowTo, where I added the READ ME from v.0.3 (Apr 24 2007). Therefore, I have several questions: 1. Is this a verified bug and should I add a clarification to this page? 2. More importantly, is there a more recent version of this READ ME file? If there are any changes that need to be made, I will be glad to update the wiki page. John Babich Volunteer, Fedora Docs Project ---------- Forwarded message ---------- From: Dariusz Bednarczyk <dbednarczyk(a)autocomp.com.pl> Date: May 31, 2007 2:12 PM Subject: Error in livecd-creator To: jmbabich(a)gmail.com Hello John, Could you please add following information to the Fedora Project Wiki http://fedoraproject.org/wiki/FedoraLiveCD/LiveCDHowTo There is a bug in livecd-creator. You must change: mayflowerconf.write('MODULES+="sata_mv sata_qstor sata_sis sata_uli"\n') mayflowerconf.write('MODULES+="sata_nv sata_sil24 sata_svw sata_via"\n') into: mayflowerconf.write('MODULES+="sata_mv sata_qstor sata_sis sata_uli "\n') mayflowerconf.write('MODULES+="sata_nv sata_sil24 sata_svw sata_via "\n') Sorry for my english. -- Best regards, Dariusz Bednarczyk

2 2

creating an i386 livecd on an x86_64 system
by Bruno Postle 31 May '07

31 May '07

Just a quick question, is it practical to build an i386 livecd on an x86_64 system? -- Bruno

2 1

Problems with network setup on custom livecd
by Elias Hunt 31 May '07

31 May '07

I'm experiencing a couple problems with the network configuration on a custom livecd. In case it makes a difference we're using the -base-on argument to work off a pre-created ISO when making network customizations. This is the line in the kickstart file that we're using to setup the network: network --device eth0 --bootproto static --ip 192.168.1.5 --netmask 255.255.255.0 --gateway 192.168.1.1 --device eth1 --bootproto dhcp --nameserver 192.168.1.5,192.168.1.6,192.168.1.110,192.168.1.111 --hostname livecd-test.m2s.com The first problem we're having is that only the first nameserver is actually being put in the /etc/resolv.conf file. The second problem is that the eth0 interface showed up unconfigured, and eth1 was set to dhcp as expected. Does anyone see any blatant errors or mistakes in my syntax? Or know if this might be a known issue? Thanks. -Eli -- Elias Hunt Systems Engineer M2S, Inc. 12 Commerce Ave. W Lebanon, NH 03784 Ph: 603-298-5509 x365 Fax: 603-298-8816 hunt(a)m2s.com

3 7

firstboot & X login invisible fonts from KDE LiveCD hd install
by David Kewley 28 May '07

28 May '07

Long story short, I installed the Fedora 7 RC2 KDE LiveCD image to my hard drive. Booting from the hard drive for the first time, firstboot comes up 800x600, with menu, button, and paragraph fonts about 3 pixels high -- totally unreadable. All the graphics and screen layout elements look normal size, much, much bigger than the text. The initial login screen comes up 1920x1080 (because it's hooked up to my HD TV via VGA), but the text is again tiny compared to the graphics and layout. It seems to be around 5 pixels high in this case. I don't see any other reports about this in fedora-livecd, fedora-devel, fedora-test, nor Bugzilla. Is it worth putting into Bugzilla, or should I somehow contact members of the KDE SIG (how?), or what? By the way, fedora-livecd-list is not listed on http://www.redhat.com/mailman/listinfo/ -- is that deliberate? Thanks, David P.S. Learned a bunch of other stuff along the way, because this is my first experience with a few technologies: * Fedora 7 (last used FC5 until this weekend) * Fedora LiveCD * making a LiveCD image boot from a Compact Flash card * using a Via Epia EN12000EG low-power Mini-ITX motherboard (idle in runlevel 5, with dual-hd RAID 1: 16W power :) * installing the LiveCD image to the hard drive * tuning the case fan speed through software

1 0

Yet More Anaconda & Kadischi
by dex 24 May '07

24 May '07

I've now gotten anaconda going with kickstart using the command-line: anaconda --kickstart=/home/dexter/mini-ks-cfg.ks --nodmraid --nompath \ --method=http://mirror.atrpms.net/fedoracore/development/i386/os \ --rootpath=/tmp/kadischi.oluQuu The anaconda so called ninjas are obviously way to busy to notice! I struggle on. ...dex

1 0

small error after media check (/init)
by Sebastian Vahl 23 May '07

23 May '07

Hi. I've noticed a small error after testing some cds with the bootoption "Verify and run from image": Right after the check is passed, this line is shown: /init line 310 = No such file or directory I've not noticed any problems because of that. So it just might be a small thing. I will open a bug for it later the day. This only as a quick notice. Sebastian

2 2

force installation of RPMs
by Heiko Andresen 23 May '07

23 May '07

I'm struggling around with a (hopefully) small problem. I've setup a Fedora Core 6 system and followed the instructions http://www-128.ibm.com/developerworks/linux/library/l-fedora-livecd/ to build a LiveCD with livecd-creator, which works perfectly ! My problem now is that I have to integrate an RPM which has to be installed with "rpm -i --nodeps". How do I manage this ? Is there a way to force this in the pkgadd) section of the configuration file ? regards, -- Heiko Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser

3 3

quick questions
by Elias Hunt 22 May '07

22 May '07

I searched the archive and was unable to find an answer to either question. Feel free to redirect me if there is already info on either of these. Is there a way to adjust the livecd boot delay? Currently it's set to 60 seconds which is a long time for our application, we'd like it around 5 or 10 seconds, but I've been unable to determine where that comes from in the CD image, nor if there is a kickstart value to set it easily at creation time. Second, I'm sure someone else has seen "Buffer I/O error on device sr0, logical block xxxxxx" errors. I've burned over 20 different ISOs now at varying burn speeds and they all have one block that generates errors during boot. Each burn is a different block id, but they all error about 8 times, and then continue booting. It doesn't seem to be causing problems, but I'm concerned that something in the livecd-creator process isn't doing what is expected and may give us trouble down the road. Any help or thoughts on either of those are greatly appreciated. -Eli -- Elias Hunt Systems Engineer M2S, Inc. 12 Commerce Ave. W Lebanon, NH 03784 Ph: 603-298-5509 x365 Fax: 603-298-8816 hunt(a)m2s.com

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

livecd May 2007