From Marc.Herbert at gmail.com Fri May 1 15:58:26 2009 From: Marc.Herbert at gmail.com (Marc.Herbert at gmail.com) Date: Fri, 01 May 2009 11:58:26 -0400 Subject: [Fedora-livecd-list] Re: F10 general question about livecd-creator and timezones References: <466775C9.5040302@verizon.net> <1181226031.5135.3.camel@localhost.localdomain> <46690AEF.2040309@verizon.net> Message-ID: Wow, Same time zone bug 2 years later, and same "tzdata-update" workaround! I love email archives :-) Skunk Worx writes: > Forrest Taylor wrote: >> On Wed, 2007-06-06 at 20:04 -0700, Skunk Worx wrote: >>> My ks scripts have the timezone set to PDT (America/Los_Angeles). >>> >>> Installation to a hard drive works as expected. PDT in startup and >>> in shells, etc. >>> >>> Creating a livecd-creator iso with the same tz setting, then >>> booting, shows A/L_A in the /etc/sysconfig/clock file, as expected. >>> >>> However the date is always EDT in the boot messages, shells, etc. >>> >>> During startup I see : >>> >>> (lvm) >>> Press I to enter interactive startup >>> Setting clock (utc) Mon Jun 4 00:12:59 EDT 2007 >>> (udev) >>> >>> I'm not clear on what is happening between lvm and udev in the >>> Linux startup sequence. >> >> It is probably using the /etc/localtime to determine the time zone. >> Replace that with /usr/share/zoneinfo/America/Los_Angeles. >> >> For the above entry, search for "Setting clock" in /etc/rc.sysinit. >> >> Forrest >> > > Yes, it's the binary file /etc/localtime. > > It appears livecd-creator doesn't trigger a code path into > "tzdata-update" (directly) or via "build-locale-archive" (indirectly) > whereas a kickstart or "normal" anaconda install does. > > For now I'm going to dynamically update it during startup with > "tzdata-update". From juszak at yahoo.com Sat May 2 03:39:02 2009 From: juszak at yahoo.com (juszak at yahoo.com) Date: Fri, 1 May 2009 20:39:02 -0700 (PDT) Subject: [Fedora-livecd-list] Can't exclude packages Message-ID: <991073.39554.qm@web38003.mail.mud.yahoo.com> I have some packages that I can't seem to exclude. I add the following lines to my kickstart file... -samba-common -samba-winbind When I build the LiveCD these packages are installed anyway. So I tried to figure out what was pulling them in. "rpm -q --whatrequires" reports that samba-common is required by samba-winbind but samba-winbind is not required by any package. S Does anybody have any ideas what i might be doing wrong? Thank You, -- cj -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From juszak at yahoo.com Sat May 2 03:47:11 2009 From: juszak at yahoo.com (juszak at yahoo.com) Date: Fri, 1 May 2009 20:47:11 -0700 (PDT) Subject: [Fedora-livecd-list] Order of package installation Message-ID: <444723.55065.qm@web38001.mail.mud.yahoo.com> I have a rpm package provided by a company that I have included in a local custom repository for inclusion on my LiveCD. When this package gets installed there is an error that "rm" can't be found and another error indicating that it is trying to use "uname". Both of these utilities are part of the binutils package that gets installed after the company provided rpm. I have contacted the company and figured out a workaround (installing the rpm in a bootup script), but I was wondering if there is anyway to manually force the order of package installations in the kickstart file. Is this possible? Thank You, -- cj -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From juszak at yahoo.com Sat May 2 04:21:32 2009 From: juszak at yahoo.com (juszak at yahoo.com) Date: Fri, 1 May 2009 21:21:32 -0700 (PDT) Subject: [Fedora-livecd-list] Applying STIGs to a LiveCD Message-ID: <114643.68454.qm@web38003.mail.mud.yahoo.com> Has anyone gone through the process of running the SRR/CSA scripts against a custom Fedora LiveCD spin (and applying the STIGS)? I help maintain a LiveCD for a project that has to be compliant with the STIGs and I'm interested in comparing notes with others that have this unique requirement. If anyone is interested in comparing notes on "stigging" LiveCDs (and related policies/procedures), please email me (juszak at yahoo.com). Thank You, -- cj -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From hobbes1069 at gmail.com Sun May 3 14:50:38 2009 From: hobbes1069 at gmail.com (Richard Shaw) Date: Sun, 3 May 2009 09:50:38 -0500 Subject: [Fedora-livecd-list] F11 Preview - No boot on EEEPC 701 Message-ID: <373c76480905030750y7560bcb0u437d52a337d92140@mail.gmail.com> I currently have F10 installed on my EEEPC 701. I'm using the exact same USB thumb drive as I used to install F10. I installed F11 Preview using the live-usb-creator gui on my F10 desktop. When I boot on the EEEPC it shows a grey screen and I see the menu box briefly before it scrolls off the screen. I re-setup my thumb drive from the F10 live CD and it boots fine. Any suggestions before I bugzilla this? Thanks, Richard -------------- next part -------------- An HTML attachment was scrubbed... URL: From Marc.Herbert at gmail.com Tue May 5 10:04:30 2009 From: Marc.Herbert at gmail.com (Marc Herbert) Date: Tue, 05 May 2009 11:04:30 +0100 Subject: [Fedora-livecd-list] enable yum logging (Re: Can't exclude packages) In-Reply-To: <991073.39554.qm@web38003.mail.mud.yahoo.com> References: <991073.39554.qm@web38003.mail.mud.yahoo.com> Message-ID: juszak at yahoo.com a ?crit : > I have some packages that I can't seem to exclude. I add the following lines to my kickstart file... > > -samba-common > -samba-winbind > > When I build the LiveCD these packages are installed anyway. So I tried to figure out what was pulling them in. "rpm -q --whatrequires" reports that samba-common is required by samba-winbind but samba-winbind is not required by any package. S > > Does anybody have any ideas what i might be doing wrong? I had a similar issue (try to exclude mkinitrd...) and found the patch below quite useful. Lowering "9" will produce even more logs. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: creator.py_yumlogging.patch URL: From katzj at fedoraproject.org Wed May 6 18:30:01 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Wed, 6 May 2009 18:30:01 +0000 (UTC) Subject: [Fedora-livecd-list] Changes to 'refs/tags/livecd-tools-020.1' Message-ID: <20090506183001.7E140120304@lists.fedorahosted.org> Changes since livecd-tools-020-7: --- 0 files changed --- From katzj at fedoraproject.org Wed May 6 18:30:01 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Wed, 6 May 2009 18:30:01 +0000 (UTC) Subject: [Fedora-livecd-list] Changes to 'refs/tags/livecd-tools-024' Message-ID: <20090506183001.A5E96120307@lists.fedorahosted.org> Changes since livecd-tools-023-10: --- 0 files changed --- From katzj at fedoraproject.org Wed May 6 18:29:59 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Wed, 6 May 2009 18:29:59 +0000 (UTC) Subject: [Fedora-livecd-list] 2 commits - config/livecd-fedora-minimal.ks imgcreate/live.py Makefile Message-ID: <20090506182959.EEF8C120285@lists.fedorahosted.org> Makefile | 2 +- config/livecd-fedora-minimal.ks | 1 + imgcreate/live.py | 4 ++-- 3 files changed, 4 insertions(+), 3 deletions(-) New commits: commit 8ddeb5380c41e9a65218bbd4e92cec8210255acf Author: Jeremy Katz Date: Wed May 6 14:02:46 2009 -0400 Bump version diff --git a/Makefile b/Makefile index c597ffc..a3b2aa9 100644 --- a/Makefile +++ b/Makefile @@ -1,5 +1,5 @@ -VERSION = 023 +VERSION = 024 INSTALL = /usr/bin/install -c INSTALL_PROGRAM = ${INSTALL} commit e0328e752e0fc5f53e8643bf02fe1aba23543ace Author: Josh Boyer Date: Tue Apr 28 21:10:35 2009 -0400 Fix ppc creation The updated patch below fixes iso creation for ppc. With this I can now build an iso to completion. diff --git a/config/livecd-fedora-minimal.ks b/config/livecd-fedora-minimal.ks index 59fced6..147f4ea 100644 --- a/config/livecd-fedora-minimal.ks +++ b/config/livecd-fedora-minimal.ks @@ -11,6 +11,7 @@ repo --name=development --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist %packages @core +anaconda-runtime bash kernel passwd diff --git a/imgcreate/live.py b/imgcreate/live.py index f91a5d2..a4914e0 100644 --- a/imgcreate/live.py +++ b/imgcreate/live.py @@ -606,7 +606,7 @@ hiddenmenu class ppcLiveImageCreator(LiveImageCreatorBase): def _get_mkisofs_options(self, isodir): - return [ "-hfs", "-nodesktop", "-part" + return [ "-hfs", "-no-desktop", "-part", "-map", isodir + "/ppc/mapping", "-hfs-bless", isodir + "/ppc/mac", "-hfs-volid", self.fslabel ] @@ -697,7 +697,7 @@ image=/ppc/ppc%(bit)s/vmlinuz f.write(cfg) f.close() - def __write_not_supported(isodir, bit): + def __write_not_supported(self, isodir, bit): makedirs(isodir + "/ppc/ppc" + bit) message = "Sorry, this LiveCD does not support your hardware" From asprakash_83 at rediffmail.com Thu May 7 05:12:33 2009 From: asprakash_83 at rediffmail.com (prakash srinivasan) Date: 7 May 2009 05:12:33 -0000 Subject: [Fedora-livecd-list] live-cd installation failed. Message-ID: <20090507051233.48347.qmail@f4mail-235-145.rediffmail.com> Hello all, I prepared a Fedora 9 based iso using the kick start start file. I tried to install my customized fedora 9. The installation started successfully and at around 90th percentage, after the post installation session, I am getting the following error message, "Error mounting device sda3 as / mount failed. This is most likely means this partition has not been formatted. Press Ok to exist the installer". After I tried to mount the sda3 partition manually. I cant mount that partition. Seems, the partition got corrupted during the installation. I cant understand, where is the problem. Did I missed any essential package while I prepared my .ks file?. Help me to install my customized fedora successfully. Regards, Prakash. -------------- next part -------------- An HTML attachment was scrubbed... URL: From xfsnowind at gmail.com Sun May 10 17:12:52 2009 From: xfsnowind at gmail.com (FENG XUE) Date: Mon, 11 May 2009 01:12:52 +0800 Subject: [Fedora-livecd-list] a problem about vmware installatioon Message-ID: i just download he fedora 11 preview and vmware 6.5, but when i installed vmware in the fedora, it always failed whatever vmware is workstation or server. the error is here: [snowind at xfsnowind yum.repos.d]$ sudo /usr/bin/vmware-config.pl Making sure services for VMware Server are stopped. Stopping VMware autostart virtual machines: Virtual machines [FAILED] Stopping VMware management services: VMware Virtual Infrastructure Web Access VMware Server Host Agent [FAILED] Stopping VMware services: VMware Authentication Daemon [ OK ] Virtual machine monitor [ OK ] None of the pre-built vmmon modules for VMware Server is suitable for your running kernel. Do you want this program to try to build the vmmon module for your system (you need to have a C compiler installed on your system)? [yes] Using compiler "/usr/bin/gcc". Use environment variable CC to override. What is the location of the directory of C header files that match your running kernel? [/lib/modules/2.6.29.2-126.fc11.i686.PAE/build/include] Extracting the sources of the vmmon module. Building the vmmon module. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config3/vmmon-only' make -C /lib/modules/2.6.29.2-126.fc11.i686.PAE/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/kernels/2.6.29.2-126.fc11.i686.PAE' CC [M] /tmp/vmware-config3/vmmon-only/linux/driver.o In file included from /tmp/vmware-config3/vmmon-only/linux/driver.c:31: /tmp/vmware-config3/vmmon-only/./include/compat_wait.h:78: error: conflicting types for ?poll_initwait? include/linux/poll.h:67: note: previous declaration of ?poll_initwait? was here In file included from /tmp/vmware-config3/vmmon-only/./include/vmware.h:38, from /tmp/vmware-config3/vmmon-only/linux/driver.c:99: /tmp/vmware-config3/vmmon-only/./include/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined In file included from /tmp/vmware-config3/vmmon-only/./common/vmx86.h:31, from /tmp/vmware-config3/vmmon-only/linux/driver.h:29, from /tmp/vmware-config3/vmmon-only/linux/driver.c:101: /tmp/vmware-config3/vmmon-only/./include/x86apic.h:97:1: warning: "APIC_BASE_MSR" redefined In file included from /usr/src/kernels/2.6.29.2-126.fc11.i686.PAE/arch/x86/include/asm/fixmap_32.h:29, from /usr/src/kernels/2.6.29.2-126.fc11.i686.PAE/arch/x86/include/asm/fixmap.h:5, from /usr/src/kernels/2.6.29.2-126.fc11.i686.PAE/arch/x86/include/asm/apic.h:8, from /usr/src/kernels/2.6.29.2-126.fc11.i686.PAE/arch/x86/include/asm/smp.h:13, from include/linux/smp.h:36, from include/linux/topology.h:33, from include/linux/mmzone.h:767, from include/linux/gfp.h:4, from include/linux/kmod.h:22, from include/linux/module.h:13, from /tmp/vmware-config3/vmmon-only/./include/compat_module.h:27, from /tmp/vmware-config3/vmmon-only/linux/driver.c:26: /usr/src/kernels/2.6.29.2-126.fc11.i686.PAE/arch/x86/include/asm/apicdef.h:132:1: warning: this is the location of the previous definition In file included from /tmp/vmware-config3/vmmon-only/./include/vcpuset.h:103, from /tmp/vmware-config3/vmmon-only/./include/modulecall.h:37, from /tmp/vmware-config3/vmmon-only/./common/vmx86.h:33, from /tmp/vmware-config3/vmmon-only/linux/driver.h:29, from /tmp/vmware-config3/vmmon-only/linux/driver.c:101: /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:329:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:333:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:401:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:407:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:506:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:595:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:684:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:773:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:775:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:860:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:862:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:945:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:947:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:1028:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:1030:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:1223:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:1227:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:1536:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:1663:7: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config3/vmmon-only/./include/vm_basic_asm.h:46, from /tmp/vmware-config3/vmmon-only/./include/rateconv.h:45, from /tmp/vmware-config3/vmmon-only/./include/modulecall.h:40, from /tmp/vmware-config3/vmmon-only/./common/vmx86.h:33, from /tmp/vmware-config3/vmmon-only/linux/driver.h:29, from /tmp/vmware-config3/vmmon-only/linux/driver.c:101: /tmp/vmware-config3/vmmon-only/./include/vm_basic_asm_x86.h:62:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_basic_asm_x86.h:177:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_basic_asm_x86.h:346:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_basic_asm_x86.h:453:7: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config3/vmmon-only/./include/vm_asm.h:43, from /tmp/vmware-config3/vmmon-only/linux/driver.c:103: /tmp/vmware-config3/vmmon-only/./include/vm_asm_x86.h:486:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_asm_x86.h:779:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_asm_x86.h:820:7: warning: "_MSC_VER" is not defined /tmp/vmware-config3/vmmon-only/./include/vm_asm_x86.h:922:7: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config3/vmmon-only/linux/driver.c:119: /tmp/vmware-config3/vmmon-only/./common/hostif.h:53:7: warning: "WINNT_DDK" is not defined /tmp/vmware-config3/vmmon-only/linux/driver.c: In function ?LinuxDriverSyncCallOnEachCPU?: /tmp/vmware-config3/vmmon-only/linux/driver.c:1423: error: too many arguments to function ?smp_call_function? /tmp/vmware-config3/vmmon-only/linux/driver.c: In function ?LinuxDriver_Ioctl?: /tmp/vmware-config3/vmmon-only/linux/driver.c:1987: error: ?struct task_struct? has no member named ?euid? /tmp/vmware-config3/vmmon-only/linux/driver.c:1987: error: ?struct task_struct? has no member named ?uid? /tmp/vmware-config3/vmmon-only/linux/driver.c:1988: error: ?struct task_struct? has no member named ?fsuid? /tmp/vmware-config3/vmmon-only/linux/driver.c:1988: error: ?struct task_struct? has no member named ?uid? /tmp/vmware-config3/vmmon-only/linux/driver.c:1989: error: ?struct task_struct? has no member named ?egid? /tmp/vmware-config3/vmmon-only/linux/driver.c:1989: error: ?struct task_struct? has no member named ?gid? /tmp/vmware-config3/vmmon-only/linux/driver.c:1990: error: ?struct task_struct? has no member named ?fsgid? /tmp/vmware-config3/vmmon-only/linux/driver.c:1990: error: ?struct task_struct? has no member named ?gid? /tmp/vmware-config3/vmmon-only/linux/driver.c:2007: error: too many arguments to function ?smp_call_function? make[2]: *** [/tmp/vmware-config3/vmmon-only/linux/driver.o] Error 1 make[1]: *** [_module_/tmp/vmware-config3/vmmon-only] Error 2 make[1]: Leaving directory `/usr/src/kernels/2.6.29.2-126.fc11.i686.PAE' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-config3/vmmon-only' Unable to build the vmmon module. For more information on how to troubleshoot module-related problems, please visit our Web site at "http://www.vmware.com/go/unsup-linux-products" and "http://www.vmware.com/go/unsup-linux-tools". Execution aborted. this is my first to send email to the fedora mail list, i just suspend somebody would receive my email, so if somebody receive it, please reply to me to give me the members in the list have received it even you also don't know how to solve this problem. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sundaram at fedoraproject.org Sun May 10 17:33:24 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Sun, 10 May 2009 23:03:24 +0530 Subject: [Fedora-livecd-list] a problem about vmware installatioon In-Reply-To: References: Message-ID: <4A070FE4.4030306@fedoraproject.org> On 05/10/2009 10:42 PM, FENG XUE wrote: > i just download he fedora 11 preview and vmware 6.5, but when i > installed vmware in the fedora, it always failed whatever vmware is > workstation or server. Please direct questions about development versions of Fedora to fedora-test list. This list is primarily about questions on the livecd-tools themselves. Rahul From jan.kratochvil at redhat.com Sun May 10 17:17:08 2009 From: jan.kratochvil at redhat.com (Jan Kratochvil) Date: Sun, 10 May 2009 19:17:08 +0200 Subject: [Fedora-livecd-list] a problem about vmware installatioon In-Reply-To: References: Message-ID: <20090510171707.GA6266@host0.dyn.jankratochvil.net> On Sun, 10 May 2009 19:12:52 +0200, FENG XUE wrote: > i just download he fedora 11 preview and vmware 6.5, but when i installed > vmware in the fedora, it always failed whatever vmware is workstation or > server. Your question is for VMware support, not for Fedora or Fedora Live CD. It is easier to use qemu-kvm (with command-line interface) or virt-manager (with GUI interface) for virtualization. Regards, Jan From dfong at dfong.com Sun May 10 22:09:42 2009 From: dfong at dfong.com (don fong) Date: Sun, 10 May 2009 15:09:42 -0700 Subject: [Fedora-livecd-list] boot livecd iso? Message-ID: <4A0750A6.7010905@dfong.com> question: how can i boot the livecd distro from a hard disk partition, hopefully with the persistent option? i have found a lot of pages describing how to do this with a USB stick, but i have not been able to find clear instructions on how to do the equivalent thing with a regular disk partition. i have the fedora livecd iso image file on my disk. i can mount it under linux. is there a way to boot the iso file directly, without wasting a CD? or to make another disk partition boot the livecd distro? thanks in advance for any help. From Marc.Herbert at gmail.com Mon May 11 09:09:23 2009 From: Marc.Herbert at gmail.com (Marc Herbert) Date: Mon, 11 May 2009 10:09:23 +0100 Subject: [Fedora-livecd-list] Re: boot livecd iso from a hard disk partition In-Reply-To: <4A0750A6.7010905@dfong.com> References: <4A0750A6.7010905@dfong.com> Message-ID: don fong a ?crit : > question: how can i boot the livecd distro from a > hard disk partition, hopefully with the persistent > option? I assume you absolutely want to boot a "real" machine. This is too bad because the easiest way from far to boot a ISO image is to use a virtual machine using VirtualBox, qemu, etc. > i have found a lot of pages > describing how to do this with a USB stick, Could you please post here the "best" URL you found? > buti have not been able to find clear instructions on > how to do the equivalent thing with a regular > disk partition. > i have the fedora livecd iso image file on my disk. > i can mount it under linux. is there a way to > boot the iso file directly, without wasting a CD? > > or to make another disk partition boot the livecd distro? Here is how I usually do this. This works with any (Linux) ISO image, not just Fedora. This assumes you already have a GRUB bootloader on the target disk. If you do not, please get one. Please note that you do not need Linux to use GRUB: http://grub4dos.sourceforge.net/wiki/index.php/Grub4dos_tutorial If you have a different bootloader than GRUB this should work "almost" the same. 1. Extract all the ISO image content to the root of somediskpartition. That is, just loopback-mount the image and copy all the content. 2. "Convert" some cherry-picked content of "isolinux/isolinux.cfg" to your GRUB configuration (in /boot/grub/menu.lst). That's all. "Converting" from the isolinux bootloader to GRUB is not as difficult as it may sound. It is basically just the matter of copy/pasting the few relevant lines and fixing the "root" parameters. For instance this works4me: title fake Fedora 10 ISO root (hd1,4) kernel /isolinux/vmlinuz0 ro liveimg root=LABEL=somediskpartition initrd /isolinux/initrd0.img As long as there are not filename clashes and enough free space you can re-use any existing partition; you do not even need to reset it and you can keep using it as before. If you are not already familiar with GRUB you will need to spend some time understanding its logic. I think such a time is never wasted and always pays back. Cheers, Marc From apevec at gmail.com Mon May 11 09:21:44 2009 From: apevec at gmail.com (Alan Pevec) Date: Mon, 11 May 2009 11:21:44 +0200 Subject: [Fedora-livecd-list] boot livecd iso? In-Reply-To: <4A0750A6.7010905@dfong.com> References: <4A0750A6.7010905@dfong.com> Message-ID: <2be7262f0905110221g4c211e9ck24806b1f6df5bf58@mail.gmail.com> On Mon, May 11, 2009 at 12:09 AM, don fong wrote: > question: how can i boot the livecd distro from a > hard disk partition, hopefully with the persistent > option? ?i have found a lot of pages > describing how to do this with a USB stick, but > i have not been able to find clear instructions on > how to do the equivalent thing with a regular > disk partition. > > i have the fedora livecd iso image file on my disk. > i can mount it under linux. ?is there a way to > boot the iso file directly, without wasting a CD? > > or to make another disk partition boot the livecd distro? You need a separate partition if your rootfs is on LVM since livecd initrd doesn't start LVM. Loop mount the ISO and copy isolinux/vmlinuz0 and isolinux/initrd0.img to /boot and LiveOS folder to / (or top-folder of the separate partition) Then add grub entry for livecd (assuming separate /boot partition and sda2 partition with /LiveOS) kernel /vmlinuz0 ro root=/dev/sda2 initrd /initrd0.img From traxtopel at gmail.com Mon May 11 15:53:42 2009 From: traxtopel at gmail.com (Williamson Grant) Date: Mon, 11 May 2009 17:53:42 +0200 Subject: [Fedora-livecd-list] livecd-tools 024-1 Message-ID: Anyone else having issues with the latest livecd-tools 024-1. Almost every custom livecd I create it fails on fsck. I worked around this, however, could it be changed so it just throws a warning and not an exception? From katzj at redhat.com Mon May 11 15:56:24 2009 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 11 May 2009 11:56:24 -0400 Subject: [Fedora-livecd-list] livecd-tools 024-1 In-Reply-To: References: Message-ID: <20090511155623.GB32112@redhat.com> On Monday, May 11 2009, Williamson Grant said: > Anyone else having issues with the latest livecd-tools 024-1. > Almost every custom livecd I create it fails on fsck. Update your e2fsprogs. If you have a perfect reproducer, esandeen would love to hear it in bug 499452 > I worked around this, however, could it be changed so it just throws a > warning and not an exception? Having it be fatal was by the explicit request of the ext4 maintainer as there really shouldn't be errors being found. And having errors found means that there are critical bugs which need fixing Jeremy From sebastian at when.com Mon May 11 16:14:10 2009 From: sebastian at when.com (Sebastian Dziallas) Date: Mon, 11 May 2009 18:14:10 +0200 Subject: [Fedora-livecd-list] livecd-tools 024-1 In-Reply-To: <20090511155623.GB32112@redhat.com> References: <20090511155623.GB32112@redhat.com> Message-ID: <4A084ED2.8040200@when.com> Jeremy Katz wrote: > On Monday, May 11 2009, Williamson Grant said: >> Anyone else having issues with the latest livecd-tools 024-1. >> Almost every custom livecd I create it fails on fsck. > > Update your e2fsprogs. If you have a perfect reproducer, esandeen would > love to hear it in bug 499452 I guess I've one. Interestingly, this occurred using ext3 file systems... I'll comment on that bug. --Sebastian >> I worked around this, however, could it be changed so it just throws a >> warning and not an exception? > > Having it be fatal was by the explicit request of the ext4 maintainer as > there really shouldn't be errors being found. And having errors found > means that there are critical bugs which need fixing > > Jeremy From traxtopel at gmail.com Mon May 11 16:27:00 2009 From: traxtopel at gmail.com (Grant Williamson) Date: Mon, 11 May 2009 18:27:00 +0200 Subject: [Fedora-livecd-list] livecd-tools 024-1 In-Reply-To: <4A084ED2.8040200@when.com> References: <20090511155623.GB32112@redhat.com> <4A084ED2.8040200@when.com> Message-ID: <4A0851D4.7080205@gmail.com> yep I see it using ext3. Sebastian Dziallas wrote: > Jeremy Katz wrote: >> On Monday, May 11 2009, Williamson Grant said: >>> Anyone else having issues with the latest livecd-tools 024-1. >>> Almost every custom livecd I create it fails on fsck. >> >> Update your e2fsprogs. If you have a perfect reproducer, esandeen would >> love to hear it in bug 499452 > > I guess I've one. Interestingly, this occurred using ext3 file > systems... I'll comment on that bug. > > --Sebastian > >>> I worked around this, however, could it be changed so it just throws a >>> warning and not an exception? >> >> Having it be fatal was by the explicit request of the ext4 maintainer as >> there really shouldn't be errors being found. And having errors found >> means that there are critical bugs which need fixing >> >> Jeremy > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list > From traxtopel at gmail.com Wed May 13 14:49:57 2009 From: traxtopel at gmail.com (Williamson Grant) Date: Wed, 13 May 2009 16:49:57 +0200 Subject: [Fedora-livecd-list] rawhide live install using usb stick problem Message-ID: Anyone tried to install a live image to disk from a usb drive. With latest F11 rawhide(20090513), the iso installs using "liveinst" with little problem from cd/dvd to disk. However when I create a usb image boot from the same machine running "liveinst". it always seems to hang at the screen after creating the partitions, i.e. does not advance. I suspect this is an anaconda issue, however this only occurs on Live from a usb stick. Any ideas, or does anyone else see this issue. From mesut.pak at nscorp.com Thu May 14 13:58:52 2009 From: mesut.pak at nscorp.com (Pak, Mesut) Date: Thu, 14 May 2009 09:58:52 -0400 Subject: [Fedora-livecd-list] proxy settings for livecd-creator Message-ID: Hi all, I have seen some posts regarding to this but no definitive answer. Could some one tell me if there is a way to set livecd-creator to use particular http proxy server and provide user authentication details? My yum.conf is alredy set up to use http proxy server. ivecd-creator --config=/opt/livecd_work/livecd-fedora-minimal.ks --fslabel=FedoraLiveCD --cache=/var/cache/live mke2fs 1.41.3 (12-Oct-2008) Filesystem label=FedoraLiveCD OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 262144 inodes, 1048576 blocks 10485 blocks (1.00%) reserved for the super user First data block=0 Maximum filesystem blocks=1073741824 32 block groups 32768 blocks per group, 32768 fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736 Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 30 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. tune2fs 1.41.3 (12-Oct-2008) Setting maximal mount count to -1 Setting interval between checks to 0 seconds filespec_eval: hash table stats: 12 elements, 12/65536 buckets used, longest chain length 1 Could not retrieve mirrorlist http://mirrors.kernel.org/fedora/development/i386/os/repodata error was [Errno 4] IOError: Error creating Live CD : Unable to download from repo : Cannot retrieve repository metadata (repomd.xml) for repository: development. Please verify its path and try again -------------- next part -------------- An HTML attachment was scrubbed... URL: From kanarip at kanarip.com Thu May 14 16:28:00 2009 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Thu, 14 May 2009 18:28:00 +0200 Subject: [Fedora-livecd-list] proxy settings for livecd-creator In-Reply-To: References: Message-ID: <4A0C4690.5090204@kanarip.com> On 05/14/2009 03:58 PM, Pak, Mesut wrote: > Hi all, > > I have seen some posts regarding to this but no definitive answer. > > Could some one tell me if there is a way to set livecd-creator to use > particular http proxy server and provide user authentication details? > > My yum.conf is alredy set up to use http proxy server. > Usually in these circumstances a: $ sudo env HTTP_PROXY=http://proxy:port livecd-creator -c /path/to/ks does the trick as urlgrabber checks (or is supposed to check) this environment variable and use it when it's available. --Jeroen From dfong at dfong.com Sat May 16 04:16:42 2009 From: dfong at dfong.com (don fong) Date: Fri, 15 May 2009 21:16:42 -0700 Subject: [Fedora-livecd-list] boot livecd iso? In-Reply-To: <2be7262f0905110221g4c211e9ck24806b1f6df5bf58@mail.gmail.com> References: <4A0750A6.7010905@dfong.com> <2be7262f0905110221g4c211e9ck24806b1f6df5bf58@mail.gmail.com> Message-ID: <4A0E3E2A.4010801@dfong.com> On 05/11/09 02:21, Alan Pevec wrote: > You need a separate partition if your rootfs is on LVM since livecd > initrd doesn't start LVM. > Loop mount the ISO and copy isolinux/vmlinuz0 and isolinux/initrd0.img > to /boot and LiveOS folder to / (or top-folder of the separate > partition) > Then add grub entry for livecd (assuming separate /boot partition and > sda2 partition with /LiveOS) > kernel /vmlinuz0 ro root=/dev/sda2 > initrd /initrd0.img Alan, thanks for your response. From dfong at dfong.com Sat May 16 04:17:00 2009 From: dfong at dfong.com (don fong) Date: Fri, 15 May 2009 21:17:00 -0700 Subject: [Fedora-livecd-list] Re: boot livecd iso from a hard disk partition In-Reply-To: References: <4A0750A6.7010905@dfong.com> Message-ID: <4A0E3E3C.4010109@dfong.com> On 05/11/09 02:09, Marc Herbert wrote: > don fong a ?crit : >> question: how can i boot the livecd distro from a >> hard disk partition, hopefully with the persistent >> option? > > I assume you absolutely want to boot a "real" machine. This is too bad > because the easiest way from far to boot a ISO image is to use a > virtual machine using VirtualBox, qemu, etc. Marc, thanks for your response. yes, this is a real machine not virtual. >> i have found a lot of pages >> describing how to do this with a USB stick, > > Could you please post here the "best" URL you found? i'm afraid i am not expert enough to judge which is best. there were so many it made my head spin. > 1. Extract all the ISO image content to the root of > somediskpartition. That is, just loopback-mount the image and copy all the > content. > > 2. "Convert" some cherry-picked content of "isolinux/isolinux.cfg" to > your GRUB configuration (in /boot/grub/menu.lst). > > That's all. i followed your directions and was able to boot the distro. now, i would like to get the persistence feature working, again to the hard disk. again, all the stuff i've found on the web is about how to do it with a USB stick, or says it can be done with a hard disk but doesn't give enough detail for my needs. any thoughts on this? From drjdes at gmail.com Sat May 16 10:33:18 2009 From: drjdes at gmail.com (joao mendes rodrigues) Date: Sat, 16 May 2009 07:33:18 -0300 Subject: [Fedora-livecd-list] cd Message-ID: <76bd3b670905160333r45b02306g12701483a53ae8fd@mail.gmail.com> Bem eu gostaria de receber um cd do sistema linux Fedora caso seja possivel. Endere?o Rua geraldo rios 305 apt202 Centro Jo?o Pinheiro MG Brasil Cep 3870000 -------------- next part -------------- An HTML attachment was scrubbed... URL: From traxtopel at gmail.com Tue May 19 11:05:44 2009 From: traxtopel at gmail.com (Williamson Grant) Date: Tue, 19 May 2009 13:05:44 +0200 Subject: [Fedora-livecd-list] livecd not building Message-ID: Did something change in rawhide in the last few days, I cannot build livecd. Sounds like something is corrupted, all packages in repo, check out fine. Is there anyway I can increase debug so I can see what is failing. After downloading my packages, always fails with. Traceback (most recent call last): File "/usr/bin/livecd-creator", line 140, in sys.exit(main()) File "/usr/bin/livecd-creator", line 123, in main creator.install() File "/usr/lib/python2.6/site-packages/imgcreate/creator.py", line 661, in install ayum.runInstall() File "/usr/lib/python2.6/site-packages/imgcreate/yuminst.py", line 181, in runInstall self.populateTs(keepold=0) File "/usr/lib/python2.6/site-packages/yum/depsolve.py", line 239, in populateTs hdr = txmbr.po.returnHeaderFromPackage() File "/usr/lib/python2.6/site-packages/yum/packages.py", line 633, in returnHeaderFromPackage hdr = rpmUtils.miscutils.hdrFromPackage(ts, rpmfile) File "/usr/lib/python2.6/site-packages/rpmUtils/miscutils.py", line 409, in hdrFromPackage raise rpmUtils.RpmUtilsError, "RPM Error opening Package" rpmUtils.RpmUtilsError: RPM Error opening Package From Marc.Herbert at gmail.com Tue May 19 15:05:03 2009 From: Marc.Herbert at gmail.com (Marc Herbert) Date: Tue, 19 May 2009 16:05:03 +0100 Subject: [Fedora-livecd-list] Re: livecd not building In-Reply-To: References: Message-ID: Williamson Grant a ?crit : > Did something change in rawhide in the last few days, I cannot build > livecd. > Sounds like something is corrupted, all packages in repo, check out > fine. > Is there anyway I can increase debug so I can see what is failing. You could try out the patch I sent 2 weeks ago ("enable yum logging"). From traxtopel at gmail.com Tue May 19 16:11:54 2009 From: traxtopel at gmail.com (Grant Williamson) Date: Tue, 19 May 2009 18:11:54 +0200 Subject: [Fedora-livecd-list] Re: livecd not building In-Reply-To: References: Message-ID: <4A12DA4A.2000307@gmail.com> Okay will do, I still have it in my trash ;) Marc Herbert wrote: > Williamson Grant a ?crit : > >> Did something change in rawhide in the last few days, I cannot build >> livecd. >> Sounds like something is corrupted, all packages in repo, check out >> fine. >> > > > >> Is there anyway I can increase debug so I can see what is failing. >> > > You could try out the patch I sent 2 weeks ago ("enable yum logging"). > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list > > From bkearney at redhat.com Tue May 19 19:18:54 2009 From: bkearney at redhat.com (Bryan Kearney) Date: Tue, 19 May 2009 15:18:54 -0400 Subject: [Fedora-livecd-list] Reconstructor Message-ID: <4A13061E.2060904@redhat.com> I am sure folks have seen this: http://reconstructor.aperantis.com What I thouhgt was interesting (besides making a pretty ui) was starting with an existing livecd iso. May speed up the process a bit in some places... dont know. -- bk From tjb at unh.edu Tue May 19 19:49:48 2009 From: tjb at unh.edu (Thomas J. Baker) Date: Tue, 19 May 2009 15:49:48 -0400 Subject: [Fedora-livecd-list] PPC LiveCD Help Message-ID: <1242762588.4259.5.camel@raptor.sr.unh.edu> I'm trying to make a live cd for a PPC machine and I want it as small as possible. I've made similar i386 images but I'm running into a problem where the ppc livecd can't be created unless the anaconda-runtime package is included ("Error creating Live CD : Unable to find boot file mapping"). The problem is that anaconda-runtime has so many dependencies that it doubles the size of the image. Any ideas or workarounds? I'm using the latest livecd-tools on Fedora 9 and at the moment, I need to stay at Fedora 9. Thanks, tjb -- ======================================================================= | Thomas Baker email: tjb at unh.edu | | Systems Programmer | | Research Computing Center voice: (603) 862-4490 | | University of New Hampshire fax: (603) 862-1761 | | 332 Morse Hall | | Durham, NH 03824 USA http://wintermute.sr.unh.edu/~tjb | ======================================================================= From traxtopel at gmail.com Wed May 20 07:13:16 2009 From: traxtopel at gmail.com (Williamson Grant) Date: Wed, 20 May 2009 09:13:16 +0200 Subject: [Fedora-livecd-list] should a livecd be ext3 or ext4 Message-ID: <897FFD61-9A35-4929-82CA-D7C932BDB2D8@gmail.com> Should a livecd be created ext3 or ext4. The reason I ask, is we tend offer the livecd's also as usb sticks, when I last tried the usb stick does not boot if the filesystem is ext4. Comments anyone? From sundaram at fedoraproject.org Wed May 20 07:23:17 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Wed, 20 May 2009 12:53:17 +0530 Subject: [Fedora-livecd-list] should a livecd be ext3 or ext4 In-Reply-To: <897FFD61-9A35-4929-82CA-D7C932BDB2D8@gmail.com> References: <897FFD61-9A35-4929-82CA-D7C932BDB2D8@gmail.com> Message-ID: <4A13AFE5.1010805@fedoraproject.org> On 05/20/2009 12:43 PM, Williamson Grant wrote: > Should a livecd be created ext3 or ext4. > > The reason I ask, is we tend offer the livecd's also as usb sticks, when > I last tried the > usb stick does not boot if the filesystem is ext4. > > Comments anyone? Fedora 11 Live CD's will use Ext4 by default but retain a small /boot partition formatted as Ext3. Since GRUB doesn't support LVM and Fedora uses LVM by default, a separate /boot is needed anyway. You can create a customized live cd with a different filesystem by using --fstype in kickstart. Rahul From traxtopel at gmail.com Wed May 20 07:41:09 2009 From: traxtopel at gmail.com (Grant Williamson) Date: Wed, 20 May 2009 09:41:09 +0200 Subject: [Fedora-livecd-list] should a livecd be ext3 or ext4 In-Reply-To: <4A13AFE5.1010805@fedoraproject.org> References: <897FFD61-9A35-4929-82CA-D7C932BDB2D8@gmail.com> <4A13AFE5.1010805@fedoraproject.org> Message-ID: <4A13B415.9090908@gmail.com> Rahul, so the liveusb-creator will work with the ext4 created livecds? Rahul Sundaram wrote: > On 05/20/2009 12:43 PM, Williamson Grant wrote: > >> Should a livecd be created ext3 or ext4. >> >> The reason I ask, is we tend offer the livecd's also as usb sticks, when >> I last tried the >> usb stick does not boot if the filesystem is ext4. >> >> Comments anyone? >> > > Fedora 11 Live CD's will use Ext4 by default but retain a small /boot > partition formatted as Ext3. Since GRUB doesn't support LVM and Fedora > uses LVM by default, a separate /boot is needed anyway. You can create a > customized live cd with a different filesystem by using --fstype in > kickstart. > > Rahul > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list > > From sundaram at fedoraproject.org Wed May 20 07:47:10 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Wed, 20 May 2009 13:17:10 +0530 Subject: [Fedora-livecd-list] should a livecd be ext3 or ext4 In-Reply-To: <4A13B415.9090908@gmail.com> References: <897FFD61-9A35-4929-82CA-D7C932BDB2D8@gmail.com> <4A13AFE5.1010805@fedoraproject.org> <4A13B415.9090908@gmail.com> Message-ID: <4A13B57E.2080201@fedoraproject.org> On 05/20/2009 01:11 PM, Grant Williamson wrote: > Rahul, > so the liveusb-creator will work with the ext4 created livecds? Yes. Rahul From kanarip at kanarip.com Wed May 20 14:28:01 2009 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Wed, 20 May 2009 16:28:01 +0200 Subject: [Fedora-livecd-list] Reconstructor In-Reply-To: <4A13061E.2060904@redhat.com> References: <4A13061E.2060904@redhat.com> Message-ID: On Tue, 19 May 2009 15:18:54 -0400, Bryan Kearney wrote: > I am sure folks have seen this: > > http://reconstructor.aperantis.com > > What I thouhgt was interesting (besides making a pretty ui) was starting > with an existing livecd iso. May speed up the process a bit in some > places... dont know. > livecd-tools (and the pretty Revisor UI) have a feature to base a compose off of another LiveCD since... like... the beginning of either of these projects... or at least since midst 2007. Kind regards, Jeroen van Meeuwen -kanarip From kanarip at kanarip.com Wed May 20 14:30:54 2009 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Wed, 20 May 2009 16:30:54 +0200 Subject: [Fedora-livecd-list] Re: livecd not building In-Reply-To: <4A12DA4A.2000307@gmail.com> References: <4A12DA4A.2000307@gmail.com> Message-ID: On Tue, 19 May 2009 18:11:54 +0200, Grant Williamson wrote: > Okay will do, I still have it in my trash ;) > If you want really, really verbose output while composing a LiveCD, try running revisor with --debug 9 supplied on the command-line. You might be able to determine what's going on using the output of revisor, fix the issue (if any) and continue composing with livecd-tools. Kind regards, Jeroen van Meeuwen -kanarip From katzj at redhat.com Wed May 20 15:16:48 2009 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 20 May 2009 11:16:48 -0400 Subject: [Fedora-livecd-list] should a livecd be ext3 or ext4 In-Reply-To: <4A13AFE5.1010805@fedoraproject.org> References: <897FFD61-9A35-4929-82CA-D7C932BDB2D8@gmail.com> <4A13AFE5.1010805@fedoraproject.org> Message-ID: <20090520151648.GB22621@redhat.com> On Wednesday, May 20 2009, Rahul Sundaram said: > On 05/20/2009 12:43 PM, Williamson Grant wrote: > > Should a livecd be created ext3 or ext4. > > > > The reason I ask, is we tend offer the livecd's also as usb sticks, when > > I last tried the > > usb stick does not boot if the filesystem is ext4. > > > > Comments anyone? > > Fedora 11 Live CD's will use Ext4 by default but retain a small /boot > partition formatted as Ext3. Since GRUB doesn't support LVM and Fedora > uses LVM by default, a separate /boot is needed anyway. You can create a > customized live cd with a different filesystem by using --fstype in > kickstart. This isn't entirely accurate. The live images themselves are entirely ext4. When you install them on a hard drive, we make an ext3 /boot and do some shuffling in anaconda. The ext4 live image is compressed inside of a squashfs which is then placed on your USB stick which should be formatted either as vfat, ext2, or ext3. I don't believe that extlinux (which we use for booting ext* USB sticks with live images on them) supports ext4 yet Jeremy From jkeating at redhat.com Wed May 20 16:53:47 2009 From: jkeating at redhat.com (Jesse Keating) Date: Wed, 20 May 2009 09:53:47 -0700 Subject: [Fedora-livecd-list] should a livecd be ext3 or ext4 In-Reply-To: <897FFD61-9A35-4929-82CA-D7C932BDB2D8@gmail.com> References: <897FFD61-9A35-4929-82CA-D7C932BDB2D8@gmail.com> Message-ID: <1242838427.3029.50.camel@localhost.localdomain> On Wed, 2009-05-20 at 09:13 +0200, Williamson Grant wrote: > > Should a livecd be created ext3 or ext4. > > The reason I ask, is we tend offer the livecd's also as usb sticks, > when I last tried the > usb stick does not boot if the filesystem is ext4. The Live Image itself is ext4. That is wrapped up in a squashfs file, and then the file and some boot loader files are placed either on a CD or on a USB device. The format of the USB device doesn't matter much, vfat, ext[2,3], etc.. so long as the bootloader can boot it. It does not have to match the filesystem that is in the squashfs image. -- Jesse Keating Fedora -- Freedom? is a feature! identi.ca: http://identi.ca/jkeating -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From traxtopel at gmail.com Wed May 20 17:03:45 2009 From: traxtopel at gmail.com (Williamson Grant) Date: Wed, 20 May 2009 19:03:45 +0200 Subject: [Fedora-livecd-list] should a livecd be ext3 or ext4 In-Reply-To: <1242838427.3029.50.camel@localhost.localdomain> References: <897FFD61-9A35-4929-82CA-D7C932BDB2D8@gmail.com> <1242838427.3029.50.camel@localhost.localdomain> Message-ID: That clears that up, I create the usb img file from the iso using my own scripts, guess that is where I got confused. On May 20, 2009, at 6:53 PM, Jesse Keating wrote: > On Wed, 2009-05-20 at 09:13 +0200, Williamson Grant wrote: >> >> Should a livecd be created ext3 or ext4. >> >> The reason I ask, is we tend offer the livecd's also as usb sticks, >> when I last tried the >> usb stick does not boot if the filesystem is ext4. > > The Live Image itself is ext4. That is wrapped up in a squashfs file, > and then the file and some boot loader files are placed either on a CD > or on a USB device. The format of the USB device doesn't matter much, > vfat, ext[2,3], etc.. so long as the bootloader can boot it. It does > not have to match the filesystem that is in the squashfs image. > > -- > Jesse Keating > Fedora -- Freedom? is a feature! > identi.ca: http://identi.ca/jkeating > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list From katzj at fedoraproject.org Wed May 27 14:29:14 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Wed, 27 May 2009 14:29:14 +0000 (UTC) Subject: [Fedora-livecd-list] Branch 'f9-branch' - 2 commits - livecd-tools.spec Makefile tools/livecd-iso-to-disk.sh Message-ID: <20090527142914.17F7B12020E@lists.fedorahosted.org> Makefile | 2 +- livecd-tools.spec | 6 +++++- tools/livecd-iso-to-disk.sh | 11 +++++++++++ 3 files changed, 17 insertions(+), 2 deletions(-) New commits: commit e3424b8e3dbceb297f34083b12a699e7084ea542 Author: Jeremy Katz Date: Wed May 27 10:11:21 2009 -0400 Bump version diff --git a/Makefile b/Makefile index c790cc2..9d67228 100644 --- a/Makefile +++ b/Makefile @@ -1,5 +1,5 @@ -VERSION = 017.2 +VERSION = 017.3 INSTALL = /usr/bin/install -c INSTALL_PROGRAM = ${INSTALL} diff --git a/livecd-tools.spec b/livecd-tools.spec index c6198c2..62224a9 100644 --- a/livecd-tools.spec +++ b/livecd-tools.spec @@ -4,7 +4,7 @@ Summary: Tools for building live CD's Name: livecd-tools -Version: 017.2 +Version: 017.3 Release: 1%{?dist} License: GPLv2 Group: System Environment/Base @@ -62,6 +62,10 @@ rm -rf $RPM_BUILD_ROOT %{python_sitelib}/imgcreate/*.pyc %changelog +* Wed May 27 2009 Jeremy Katz - 017.3-1 +- Backport livecd-iso-to-disk change to work around com32's lack of + abi guarantees (#492370, #498155) + * Fri Dec 19 2008 Jeremy Katz - 017.2-1 - Add newkey repo (#477067) - Fix --base-on even more commit 617dffce568c914200ee3ef8cad9aea85e2706bb Author: Jeremy Katz Date: Thu Apr 2 16:57:13 2009 -0400 [BACKPORT] Use our syslinux's menu com32 modules (#492370) com32 modules in syslinux don't seem to have a consistent API, so let's workaround it by copying in the menu files from our syslinux when doing livecd-iso-to-disk. This is kind of kludgey, really :/ diff --git a/tools/livecd-iso-to-disk.sh b/tools/livecd-iso-to-disk.sh index 85e097b..ccd17e6 100644 --- a/tools/livecd-iso-to-disk.sh +++ b/tools/livecd-iso-to-disk.sh @@ -297,6 +297,17 @@ if [ -n "$overlaysizemb" ]; then fi echo "Installing boot loader" +# this is a bit of a kludge, but syslinux doesn't guarantee the API for its com32 modules :/ +if [ -f $USBMNT/$SYSLINUXPATH/vesamenu.c32 -a -f /usr/share/syslinux/vesamenu.c32 ]; then + cp /usr/share/syslinux/vesamenu.c32 $USBMNT/$SYSLINUXPATH/vesamenu.c32 +elif [ -f $USBMNT/$SYSLINUXPATH/vesamenu.c32 -a -f /usr/lib/syslinux/vesamenu.c32 ]; then + cp /usr/lib/syslinux/vesamenu.c32 $USBMNT/$SYSLINUXPATH/vesamenu.c32 +elif [ -f $USBMNT/$SYSLINUXPATH/menu.c32 -a -f /usr/share/syslinux/menu.c32 ]; then + cp /usr/share/syslinux/menu.c32 $USBMNT/$SYSLINUXPATH/menu.c32 +elif [ -f $USBMNT/$SYSLINUXPATH/menu.c32 -a -f /usr/lib/syslinux/menu.c32 ]; then + cp /usr/lib/syslinux/menu.c32 $USBMNT/$SYSLINUXPATH/menu.c32 +fi + if [ "$USBFS" = "vfat" -o "$USBFS" = "msdos" ]; then # syslinux expects the config to be named syslinux.cfg # and has to run with the file system unmounted From katzj at fedoraproject.org Wed May 27 14:29:15 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Wed, 27 May 2009 14:29:15 +0000 (UTC) Subject: [Fedora-livecd-list] Changes to 'refs/tags/livecd-tools-0.17.3' Message-ID: <20090527142915.E3DB512020E@lists.fedorahosted.org> Tag 'livecd-tools-0.17.3' created by Jeremy Katz at 2009-05-27 14:11 +0000 livecd-tools-0.17.3 Changes since livecd-tools-017.1-6: --- 0 files changed --- From gayleard at eircom.net Fri May 29 10:58:22 2009 From: gayleard at eircom.net (Timothy Murphy) Date: Fri, 29 May 2009 11:58:22 +0100 Subject: [Fedora-livecd-list] Error 15 Message-ID: When I put the Fedora-10 KDE Live CD on a USB stick with livecd-iso-to-disk (which seems to go perfectly) and re-boot with the stick, I just get "Error 15" on the screen. What exactly does this mean? -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College Dublin