From opensource at till.name Mon Dec 1 23:22:19 2008 From: opensource at till.name (Till Maas) Date: Tue, 02 Dec 2008 00:22:19 +0100 Subject: [Fedora-livecd-list] RFE: allow multi live medium In-Reply-To: <1228013861.18715.16.camel@aglarond.local> References: <200811041010.36947.opensource@till.name> <200811272251.07251.opensource@till.name> <1228013861.18715.16.camel@aglarond.local> Message-ID: <200812020022.30052.opensource@till.name> On Sun November 30 2008, Jeremy Katz wrote: > On Thu, 2008-11-27 at 22:51 +0100, Till Maas wrote: > > > 2) How do we want to namespace so that we can better support multiples > > > and have them identifiable? > > > > I guess the easiest way would be to use the name of the iso/torrent file > > for each live image, e.g.: > > > > LiveOS/F10-i686-Live > > LiveOS/F10-i686-Live-KDE > > > > or even seperate directories in the root of the filesystem. > > This could work and is definitely better than some of the other things > that have been suggested in the past. It'd require keeping some > knowledge of the original label/filename when we do the transform in > livecd-iso-to-disk/liveusb-creator. And if go this route, it probably > makes the most sense to do it in all cases and not just as a special > case. Maybe it would be also possible to use some meta information from the .iso file to make this work also in case the iso filename was not preserved. > > What I would > > really enjoy would be a generic bootloader that would recognize any iso > > image on the medium and would allow to chainboot them. I believe at least > > chainbooting iso images is possible with grub2, but I did not yet test > > it. > > Unless a lot has changed since I last looked at grub2 a few months ago, > it's in no way ready for primetime. And to be honest, I'm not entirely > convinced that it's going to be. Chainbooting the iso is an interesting > thought, though. I wonder if it could be done at all easily with the > com32 support in syslinux. > > > > 3) How do we want to handle the boot-loader pieces if we have multiple > > > OS options on the same medium? > > > > I do not yet have an answer for this. > > I don't either :) Which might put it on the critical path for > implementing Yesterday I inspected a multi live optical medium that contained several distributions. There the append keyword was used to load the several isolinux config files for each distribution from a generic one. > The open questions are important, though, as they'll impact the way the > entire path is structured. I'd rather not be in a situation of having > case statements upon case statements to support each stage in the > evolution of the way it works. The live initrd is already bad enough > there with the movement we've already had -- and this is already going > to add another case to care about. Making it possible to rename the LiveOS directory and pass it's location to initrd and probably via initrd to livesys currently seems to be enough to make it possible to create a multi live medium. I will try to create a POC usb device, soon. The implementation of live-iso-to-disk and the real location / organization of the boot loader does not really change this. Only if we can also support booting isos via grub2, probably an additional loop mount needs to be added to the initrd, but this is only wild speculation. > > Yes, it is hardcoded in the livesys initscript. Where does it come from? > > I cannot find it or any reference to it in the livecd git repository and > > it is also not owned by any package on the live medium. > > The initscript is in the kickstart config, so the spin-kickstarts repo. > Getting these pieces to work also matters for landing the initrd support Is there any other reason than lack of time to not add the livesys init script to the initscripts package? One kickstart file I opened already contained a FIXME saying, that the livesys script should be in some package and I guess it should be initscripts. Regards, Till -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 827 bytes Desc: This is a digitally signed message part. URL: From katzj at redhat.com Tue Dec 2 16:49:33 2008 From: katzj at redhat.com (Jeremy Katz) Date: Tue, 02 Dec 2008 11:49:33 -0500 Subject: [Fedora-livecd-list] RFE: allow multi live medium In-Reply-To: <200812020022.30052.opensource@till.name> References: <200811041010.36947.opensource@till.name> <200811272251.07251.opensource@till.name> <1228013861.18715.16.camel@aglarond.local> <200812020022.30052.opensource@till.name> Message-ID: <1228236573.13159.6.camel@aglarond.local> On Tue, 2008-12-02 at 00:22 +0100, Till Maas wrote: > On Sun November 30 2008, Jeremy Katz wrote: > > On Thu, 2008-11-27 at 22:51 +0100, Till Maas wrote: > > > > 2) How do we want to namespace so that we can better support multiples > > > > and have them identifiable? > > > > > > I guess the easiest way would be to use the name of the iso/torrent file > > > for each live image, e.g.: > > > > > > LiveOS/F10-i686-Live > > > LiveOS/F10-i686-Live-KDE > > > > > > or even seperate directories in the root of the filesystem. > > > > This could work and is definitely better than some of the other things > > that have been suggested in the past. It'd require keeping some > > knowledge of the original label/filename when we do the transform in > > livecd-iso-to-disk/liveusb-creator. And if go this route, it probably > > makes the most sense to do it in all cases and not just as a special > > case. > > Maybe it would be also possible to use some meta information from the .iso > file to make this work also in case the iso filename was not preserved. Yeah, the fslabel was what I really meant there > > > What I would > > > really enjoy would be a generic bootloader that would recognize any iso > > > image on the medium and would allow to chainboot them. I believe at least > > > chainbooting iso images is possible with grub2, but I did not yet test > > > it. > > > > Unless a lot has changed since I last looked at grub2 a few months ago, > > it's in no way ready for primetime. And to be honest, I'm not entirely > > convinced that it's going to be. Chainbooting the iso is an interesting > > thought, though. I wonder if it could be done at all easily with the > > com32 support in syslinux. > > > > > > 3) How do we want to handle the boot-loader pieces if we have multiple > > > > OS options on the same medium? > > > > > > I do not yet have an answer for this. > > > > I don't either :) Which might put it on the critical path for > > implementing > > Yesterday I inspected a multi live optical medium that contained several > distributions. There the append keyword was used to load the several isolinux > config files for each distribution from a generic one. Hmmm, I wonder how bad it would be to wire up a com32 module that walked the LiveOS directory and for each subdirectory in it, grabbed and appended LiveOS/fslabel/isolinux.cfg. Since that seems like a better way than having to explicitly do an append keyword for each "image" we add > > > Yes, it is hardcoded in the livesys initscript. Where does it come from? > > > I cannot find it or any reference to it in the livecd git repository and > > > it is also not owned by any package on the live medium. > > > > The initscript is in the kickstart config, so the spin-kickstarts repo. > > Getting these pieces to work also matters for landing the initrd support > > Is there any other reason than lack of time to not add the livesys init script > to the initscripts package? One kickstart file I opened already contained a > FIXME saying, that the livesys script should be in some package and I guess > it should be initscripts. There are bits and pieces that are specific to each individual spin. I guess the base bits could go into the initscripts package if notting could be talked into it Jeremy From apevec at gmail.com Sun Dec 7 21:08:01 2008 From: apevec at gmail.com (Alan Pevec) Date: Sun, 7 Dec 2008 22:08:01 +0100 Subject: [Fedora-livecd-list] [PATCH] fix device command version check Message-ID: <1228684081-14232-1-git-send-email-apevec@gmail.com> From: Alan Pevec F8_Device is a FC3_Device subclass, so isinstance was always true Signed-off-by: Alan Pevec --- imgcreate/kickstart.py | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/imgcreate/kickstart.py b/imgcreate/kickstart.py index 58171c4..253d349 100644 --- a/imgcreate/kickstart.py +++ b/imgcreate/kickstart.py @@ -450,7 +450,7 @@ def get_image_fstype(ks, default = None): def get_modules(ks): devices = [] - if isinstance(ks.handler.device, kscommands.device.FC3_Device): + if not hasattr(ks.handler.device, "deviceList"): devices.append(ks.handler.device) else: devices.extend(ks.handler.device.deviceList) -- 1.6.0.4 From katzj at fedoraproject.org Sun Dec 7 23:02:03 2008 From: katzj at fedoraproject.org (Jeremy Katz) Date: Sun, 7 Dec 2008 23:02:03 +0000 (UTC) Subject: [Fedora-livecd-list] imgcreate/kickstart.py Message-ID: <20081207230203.ADE39120313@lists.fedorahosted.org> imgcreate/kickstart.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit b98ad7391cef406967636f4fba7e3d5d2602e83f Author: Alan Pevec Date: Sun Dec 7 22:08:01 2008 +0100 fix device command version check F8_Device is a FC3_Device subclass, so isinstance was always true Signed-off-by: Alan Pevec diff --git a/imgcreate/kickstart.py b/imgcreate/kickstart.py index 58171c4..253d349 100644 --- a/imgcreate/kickstart.py +++ b/imgcreate/kickstart.py @@ -450,7 +450,7 @@ def get_image_fstype(ks, default = None): def get_modules(ks): devices = [] - if isinstance(ks.handler.device, kscommands.device.FC3_Device): + if not hasattr(ks.handler.device, "deviceList"): devices.append(ks.handler.device) else: devices.extend(ks.handler.device.deviceList) From katzj at redhat.com Sun Dec 7 23:02:19 2008 From: katzj at redhat.com (Jeremy Katz) Date: Sun, 7 Dec 2008 18:02:19 -0500 Subject: [Fedora-livecd-list] [PATCH] fix device command version check In-Reply-To: <1228684081-14232-1-git-send-email-apevec@gmail.com> References: <1228684081-14232-1-git-send-email-apevec@gmail.com> Message-ID: On Dec 7, 2008, at 4:08 PM, Alan Pevec wrote: > F8_Device is a FC3_Device subclass, so isinstance was always true Applied, thanks Jeremy From pmeyer at themeyerfarm.com Mon Dec 8 23:37:50 2008 From: pmeyer at themeyerfarm.com (Phil Meyer) Date: Mon, 08 Dec 2008 16:37:50 -0700 Subject: [Fedora-livecd-list] new dbus 1.2.6-1 breaks livecd images: Message-ID: <493DAFCE.7000405@themeyerfarm.com> Several show stoppers in builds of 64bit F10 after this round of updates, which include dbus 1.2.6-1. I get: Starting system message bus: Failed to start message bus: Error in file /etc/ dbus-1/system.d/org.gnome.CPUFreqSelector.conf, line 1, column0: no element found Several other things fail with lack of disk space, even though the messaging at kernel loading regarding "no persistant overlay: using temporary" did appear. From vnpenguin at vnoss.org Tue Dec 9 08:37:54 2008 From: vnpenguin at vnoss.org (Vnpenguin) Date: Tue, 9 Dec 2008 09:37:54 +0100 Subject: [Fedora-livecd-list] Config files for livecd-tools Message-ID: Hi all, I just installed livecd-tools package on my FC10 box. There is only /usr/share/doc/livecd-tools-020/livecd-fedora-minimal.ks Where could I found ks files for Gnome,KDE desktop ? Thanks -- http://vnoss.org From kanarip at kanarip.com Tue Dec 9 08:51:03 2008 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Tue, 09 Dec 2008 09:51:03 +0100 Subject: [Fedora-livecd-list] Config files for livecd-tools In-Reply-To: References: Message-ID: <493E3177.30805@kanarip.com> Vnpenguin wrote: > Hi all, > I just installed livecd-tools package on my FC10 box. There is only > /usr/share/doc/livecd-tools-020/livecd-fedora-minimal.ks > > Where could I found ks files for Gnome,KDE desktop ? > Please install the spin-kickstarts package. -Jeroen From vnpenguin at vnoss.org Tue Dec 9 09:07:08 2008 From: vnpenguin at vnoss.org (Vnpenguin) Date: Tue, 9 Dec 2008 10:07:08 +0100 Subject: [Fedora-livecd-list] Config files for livecd-tools In-Reply-To: <493E3177.30805@kanarip.com> References: <493E3177.30805@kanarip.com> Message-ID: On Tue, Dec 9, 2008 at 9:51 AM, Jeroen van Meeuwen wrote: > > Please install the spin-kickstarts package. > > -Jeroen > Thank you ! -- http://vnoss.org From muayyad.alsadi at ojuba.org Tue Dec 9 15:32:48 2008 From: muayyad.alsadi at ojuba.org (=?UTF-8?Q?=D9=85=D8=A4=D9=8A=D8=AF_=D8=A7=D9=84=D8=B3=D8=B9=D8=AF=D9=8A?=) Date: Tue, 09 Dec 2008 17:32:48 +0200 Subject: [Fedora-livecd-list] new dbus 1.2.6-1 breaks livecd images: In-Reply-To: <493DAFCE.7000405@themeyerfarm.com> References: <493DAFCE.7000405@themeyerfarm.com> Message-ID: <4310a6bc06b10ccb248a6ae05fcc1334@localhost> I have problems with dbus/hal but it's different Installing: fedora-screensaver-theme ##################### [981/982] Installing: gnome-screensaver ##################### [982/982] Introspect error on :1.0:/org/freedesktop/Hal/Manager: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.DBus.Introspectable" member "Introspect" error name "(unset)" destination ":1.0") /usr/sbin/setenforce: SELinux is disabled Removing password for user root. it's not fatal so I just ignore it note: I have installed some components from pending updates On Mon, 08 Dec 2008 16:37:50 -0700, Phil Meyer wrote: > > Several show stoppers in builds of 64bit F10 after this round of > updates, which include dbus 1.2.6-1. > > I get: > > Starting system message bus: Failed to start message bus: Error in > file /etc/ > dbus-1/system.d/org.gnome.CPUFreqSelector.conf, line 1, column0: no > element found > > Several other things fail with lack of disk space, even though the > messaging at kernel loading regarding "no persistant overlay: using > temporary" did appear. > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list From katzj at redhat.com Tue Dec 9 17:13:28 2008 From: katzj at redhat.com (Jeremy Katz) Date: Tue, 9 Dec 2008 12:13:28 -0500 Subject: [Fedora-livecd-list] new dbus 1.2.6-1 breaks livecd images: In-Reply-To: <493DAFCE.7000405@themeyerfarm.com> References: <493DAFCE.7000405@themeyerfarm.com> Message-ID: <334965A8-4D48-4DBD-A7B0-EE62682047C8@redhat.com> On Dec 8, 2008, at 6:37 PM, Phil Meyer wrote: > Several show stoppers in builds of 64bit F10 after this round of > updates, which include dbus 1.2.6-1. > > I get: > > Starting system message bus: Failed to start message bus: Error > in file /etc/ > dbus-1/system.d/org.gnome.CPUFreqSelector.conf, line 1, column0: no > element found The dbus update that recently got pushed has managed to tickle bugs in a lot of other apps. Fixes are in the pipeline for them Jeremy From katzj at fedoraproject.org Tue Dec 9 18:36:11 2008 From: katzj at fedoraproject.org (Jeremy Katz) Date: Tue, 9 Dec 2008 18:36:11 +0000 (UTC) Subject: [Fedora-livecd-list] imgcreate/creator.py imgcreate/live.py Message-ID: <20081209183611.42191120410@lists.fedorahosted.org> imgcreate/creator.py | 4 ++-- imgcreate/live.py | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) New commits: commit c608a60c6c419d1c71ace7dcfa26e7c1b00fa5ab Author: Jeremy Katz Date: Tue Dec 9 13:33:50 2008 -0500 Support live images using an ext4 rootfs diff --git a/imgcreate/creator.py b/imgcreate/creator.py index 519735e..5c7f13d 100644 --- a/imgcreate/creator.py +++ b/imgcreate/creator.py @@ -865,7 +865,7 @@ class LoopImageCreator(ImageCreator): def __get_fstype(self): return self.__fstype def __set_fstype(self, val): - if val != "ext2" and val != "ext3": + if val not in ("ext2", "ext3", "ext4"): raise CreatorError("Unknown _fstype '%s' supplied" % val) self.__fstype = val _fstype = property(__get_fstype, __set_fstype) @@ -874,7 +874,7 @@ class LoopImageCreator(ImageCreator): This is the filesystem type used when creating the filesystem image. Subclasses may change this if they wish to use something other ext3. - Note, only ext2 and ext3 are currently supported. + Note, only ext2, ext3, ext4 are currently supported. Note also, this attribute may only be set before calling mount(). diff --git a/imgcreate/live.py b/imgcreate/live.py index fb1f917..347d22c 100644 --- a/imgcreate/live.py +++ b/imgcreate/live.py @@ -209,7 +209,7 @@ class LiveImageCreatorBase(LoopImageCreator): f.write('LIVEOS="yes"\n') f.write('PROBE="no"\n') - f.write('MODULES+="squashfs ext3 ext2 vfat msdos "\n') + f.write('MODULES+="squashfs ext4 ext3 ext2 vfat msdos "\n') f.write('MODULES+="sr_mod sd_mod ide-cd cdrom "\n') for module in self.__modules: From lewis at codesign2.com Wed Dec 10 07:48:02 2008 From: lewis at codesign2.com (lewis at codesign2.com) Date: Tue, 9 Dec 2008 23:48:02 -0800 (PST) Subject: [Fedora-livecd-list] Config files for livecd-tools In-Reply-To: References: Message-ID: <750e928d28e42d33656535b7ae2678fe.squirrel@www.webmail.codesign2.com> Mght as well tag this on here, ArtStudio is that supposed to have a kickstart file also as a noob developer how would I add files to a kickstart file like in Debian's Live Helper Package, Im sure kickstart is just as good if not better (less files and confusion I assume) but at the moment I can't really build anything without it moaning about fitting packages in and can't find any solid documentation (can't stand that wiki page) Thanks > Hi all, > I just installed livecd-tools package on my FC10 box. There is only > /usr/share/doc/livecd-tools-020/livecd-fedora-minimal.ks > > Where could I found ks files for Gnome,KDE desktop ? > > Thanks > -- > http://vnoss.org > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list > From Tim.Einmahl at kba.de Wed Dec 10 09:04:18 2008 From: Tim.Einmahl at kba.de (Tim.Einmahl at kba.de) Date: Wed, 10 Dec 2008 10:04:18 +0100 Subject: [Fedora-livecd-list] Copy livecd to ram ? Message-ID: <267E81812CDE28418552FFE27393707104D07C63@NTEX01.kba.de> Dear all, I am using livecd-tools-013-8.i386.rpm from http://www.nanotechnologies.qc.ca/propos/linux/centos-live/$basearch/liv e to build an RHEL5.2 live-cd. I successfully created one with a jetty-application-server running an application. Now my question is, is there a way to copy the hole cd into memory and run it from there, like the copytoram from knoppix ? This would avoid accessing the cd anymore. We really need this feature, as this server is hosted in the office. Kind regards Tim From muayyad.alsadi at ojuba.org Wed Dec 10 11:33:05 2008 From: muayyad.alsadi at ojuba.org (=?UTF-8?Q?=D9=85=D8=A4=D9=8A=D8=AF_=D8=A7=D9=84=D8=B3=D8=B9=D8=AF=D9=8A?=) Date: Wed, 10 Dec 2008 13:33:05 +0200 Subject: [Fedora-livecd-list] new dbus 1.2.6-1 breaks livecd images: In-Reply-To: <334965A8-4D48-4DBD-A7B0-EE62682047C8@redhat.com> References: <493DAFCE.7000405@themeyerfarm.com> <334965A8-4D48-4DBD-A7B0-EE62682047C8@redhat.com> Message-ID: <719ff7969d1eca034420be4b6f083780@localhost> waiting... From vnpenguin at vnoss.org Wed Dec 10 12:08:19 2008 From: vnpenguin at vnoss.org (Vnpenguin) Date: Wed, 10 Dec 2008 13:08:19 +0100 Subject: [Fedora-livecd-list] livecd-tools: cache for yum ? Message-ID: Hi, Does livecd-tools uses a cache for yum ? I can't found command line option for the cache yet ? I have no local repo and I don't want download all packages for each build. Thanks, -- http://vnoss.org From kanarip at kanarip.com Wed Dec 10 12:27:19 2008 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Wed, 10 Dec 2008 13:27:19 +0100 Subject: [Fedora-livecd-list] livecd-tools: cache for yum ? In-Reply-To: References: Message-ID: <493FB5A7.4010007@kanarip.com> Vnpenguin wrote: > Hi, > Does livecd-tools uses a cache for yum ? I can't found command line > option for the cache yet ? > I have no local repo and I don't want download all packages for each build. > I think the option is "--cache /path/to/directory" Kind regards, Jeroen van Meeuwen -kanarip From vnpenguin at vnoss.org Wed Dec 10 12:52:11 2008 From: vnpenguin at vnoss.org (Vnpenguin) Date: Wed, 10 Dec 2008 13:52:11 +0100 Subject: [Fedora-livecd-list] livecd-tools: cache for yum ? In-Reply-To: <493FB5A7.4010007@kanarip.com> References: <493FB5A7.4010007@kanarip.com> Message-ID: On Wed, Dec 10, 2008 at 1:27 PM, Jeroen van Meeuwen wrote: > Vnpenguin wrote: >> >> Hi, >> Does livecd-tools uses a cache for yum ? I can't found command line >> option for the cache yet ? >> I have no local repo and I don't want download all packages for each >> build. >> > > I think the option is "--cache /path/to/directory" > Oh, my bad !!! Yes, I found it too, Thank you, -- http://vnoss.org From vnpenguin at vnoss.org Wed Dec 10 20:55:09 2008 From: vnpenguin at vnoss.org (Vnpenguin) Date: Wed, 10 Dec 2008 21:55:09 +0100 Subject: [Fedora-livecd-list] livecd-creator stops without errors :( Message-ID: Hi , I run livecd-creator on FC10 i386 box (with all updates). The first time is ok. But after that, when I added some packages into my KS file, this tool stops work without give me any error message : ======================================================================= mke2fs 1.41.3 (12-Oct-2008) Filesystem label=FC-One-LiveCD-20 OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 196608 inodes, 786432 blocks 7864 blocks (1.00%) reserved for the super user First data block=0 Maximum filesystem blocks=805306368 24 block groups 32768 blocks per group, 32768 fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912 Writing inode tables: done Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 29 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 Retrieving http://fedora.uib.no/fedora/linux/releases/10/Everything/i386/os/repodata/repomd.xml ...OK Retrieving http://ftp.cc.uoc.gr/mirrors/rpmfusion/free/fedora/releases/10/Everything/i386/os/repodata/repomd.xml ...OK Retrieving http://ftp.belnet.be/mirror/download.fedora.redhat.com/linux/updates/10/i386/repodata/repomd.xml ...OK Retrieving http://localhost/repo/repodata/repomd.xml ...OK Retrieving http://fr2.rpmfind.net/linux/rpmfusion/free/fedora/updates/10/i386/repodata/repomd.xml ...OK =============================================================================== My command line is: # livecd-creator -v -d -c myconfig.ks -f FC10test --logfile=log.txt -t /tmp --cache=/var/cache/livecd myconfig.ks is my customized KS config from XFCE desktop of FC10. So even with -d & -v options, I see nothing on screen :( Is there any way to enable more debug output ? Thanks, -- http://vnoss.org From lewis at codesign2.com Wed Dec 10 23:07:52 2008 From: lewis at codesign2.com (lewis at codesign2.com) Date: Wed, 10 Dec 2008 15:07:52 -0800 (PST) Subject: [Fedora-livecd-list] livecd-tools: cache for yum ? In-Reply-To: References: Message-ID: <91ef842db856baf342d1749db168d121.squirrel@www.webmail.codesign2.com> Ooh I know this you need create repo and rsync that way you can rsync from the internet (I have the whole of Fedora10 for x86 & 64) and createrepo on the directory google createrepo fedora and there is a tutorial on howtoforge i think it's for fedora8 but still works and works for other distro's First contrib lol > Hi, > Does livecd-tools uses a cache for yum ? I can't found command line > option for the cache yet ? > I have no local repo and I don't want download all packages for each > build. > > Thanks, > -- > http://vnoss.org > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list > From muayyad.alsadi at ojuba.org Fri Dec 12 20:38:08 2008 From: muayyad.alsadi at ojuba.org (=?UTF-8?Q?=D9=85=D8=A4=D9=8A=D8=AF_=D8=A7=D9=84=D8=B3=D8=B9=D8=AF=D9=8A?=) Date: Fri, 12 Dec 2008 22:38:08 +0200 Subject: [Fedora-livecd-list] notic this hal message while building the livecd Message-ID: hi everybody, I reported that after dbus update https://bugzilla.redhat.com/show_bug.cgi?id=476043 I always see a non-fatal message saying that there is a hal Introspect error it could be that the new dbus needs a change in hal .conf files From dhuff at redhat.com Mon Dec 15 21:49:23 2008 From: dhuff at redhat.com (David Huff) Date: Mon, 15 Dec 2008 16:49:23 -0500 Subject: [Fedora-livecd-list] [PATCH] Fix, --tmpdir relative path Message-ID: <1229377763-15921-1-git-send-email-dhuff@redhat.com> If a relative path is passed as --tmpdir it sets the build and inst root to "relative path" which then gets passes to yum as the install root and causes oddities with dependency resolution --- imgcreate/creator.py | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/imgcreate/creator.py b/imgcreate/creator.py index 5c7f13d..82db284 100644 --- a/imgcreate/creator.py +++ b/imgcreate/creator.py @@ -382,7 +382,7 @@ class ImageCreator(object): return try: - self.__builddir = tempfile.mkdtemp(dir = self.tmpdir, + self.__builddir = tempfile.mkdtemp(dir = os.path.abspath(self.tmpdir), prefix = "imgcreate-") except OSError, (err, msg): raise CreatorError("Failed create build directory in %s: %s" % -- 1.5.5.1 From katzj at redhat.com Mon Dec 15 23:26:46 2008 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 15 Dec 2008 18:26:46 -0500 Subject: [Fedora-livecd-list] [PATCH] Fix, --tmpdir relative path In-Reply-To: <1229377763-15921-1-git-send-email-dhuff@redhat.com> References: <1229377763-15921-1-git-send-email-dhuff@redhat.com> Message-ID: <1229383606.28858.25.camel@aglarond.local> On Mon, 2008-12-15 at 16:49 -0500, David Huff wrote: > If a relative path is passed as --tmpdir it sets the build and inst root to > "relative path" which then gets passes to yum as the install root and causes > oddities with dependency resolution Applied, thanks Jeremy From katzj at fedoraproject.org Tue Dec 16 02:52:48 2008 From: katzj at fedoraproject.org (Jeremy Katz) Date: Tue, 16 Dec 2008 02:52:48 +0000 (UTC) Subject: [Fedora-livecd-list] imgcreate/creator.py Message-ID: <20081216025248.9A004C024D@lists.fedorahosted.org> imgcreate/creator.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 3e40d4c418ce8a652b269d48e3794bf49c2765e7 Author: David Huff Date: Mon Dec 15 16:49:23 2008 -0500 Fix, --tmpdir relative path If a relative path is passed as --tmpdir it sets the build and inst root to "relative path" which then gets passes to yum as the install root and causes oddities with dependency resolution diff --git a/imgcreate/creator.py b/imgcreate/creator.py index 5c7f13d..82db284 100644 --- a/imgcreate/creator.py +++ b/imgcreate/creator.py @@ -382,7 +382,7 @@ class ImageCreator(object): return try: - self.__builddir = tempfile.mkdtemp(dir = self.tmpdir, + self.__builddir = tempfile.mkdtemp(dir = os.path.abspath(self.tmpdir), prefix = "imgcreate-") except OSError, (err, msg): raise CreatorError("Failed create build directory in %s: %s" % From bruno at wolff.to Tue Dec 16 03:19:21 2008 From: bruno at wolff.to (Bruno Wolff III) Date: Mon, 15 Dec 2008 21:19:21 -0600 Subject: [Fedora-livecd-list] What is supposed to pull in a display manager? Message-ID: <20081216031921.GA20039@wolff.to> I have been trying to get a games spin in shape and have been doing some testing using F10 + updates + updates-testing. I found in my tests that no display manager was getting pulled in resulting in prefdm restarting enough times to get turned off and X never came up. Adding gdm to the package list fixed this problem. (On a related note, even after this something tried to run gnome-power-manager which wasn't installed.) Should the livecd-base kickstart include gdm or is there a better fix for this issue? From sundaram at fedoraproject.org Tue Dec 16 03:27:28 2008 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Tue, 16 Dec 2008 08:57:28 +0530 Subject: [Fedora-livecd-list] What is supposed to pull in a display manager? In-Reply-To: <20081216031921.GA20039@wolff.to> References: <20081216031921.GA20039@wolff.to> Message-ID: <49472020.1030303@fedoraproject.org> Bruno Wolff III wrote: > I have been trying to get a games spin in shape and have been doing some > testing using F10 + updates + updates-testing. > I found in my tests that no display manager was getting pulled in resulting > in prefdm restarting enough times to get turned off and X never came up. > Adding gdm to the package list fixed this problem. > (On a related note, even after this something tried to run > gnome-power-manager which wasn't installed.) > > Should the livecd-base kickstart include gdm or is there a better fix > for this issue? Games kickstart file should inherit livecd desktop kickstart file instead of base. That would fix the issues. Rahul From bruno at wolff.to Tue Dec 16 03:42:06 2008 From: bruno at wolff.to (Bruno Wolff III) Date: Mon, 15 Dec 2008 21:42:06 -0600 Subject: [Fedora-livecd-list] What is supposed to pull in a display manager? In-Reply-To: <49472020.1030303@fedoraproject.org> References: <20081216031921.GA20039@wolff.to> <49472020.1030303@fedoraproject.org> Message-ID: <20081216034206.GA21636@wolff.to> On Tue, Dec 16, 2008 at 08:57:28 +0530, Rahul Sundaram wrote: > Bruno Wolff III wrote: >> I have been trying to get a games spin in shape and have been doing some >> testing using F10 + updates + updates-testing. >> I found in my tests that no display manager was getting pulled in resulting >> in prefdm restarting enough times to get turned off and X never came up. >> Adding gdm to the package list fixed this problem. >> (On a related note, even after this something tried to run >> gnome-power-manager which wasn't installed.) >> >> Should the livecd-base kickstart include gdm or is there a better fix >> for this issue? > > Games kickstart file should inherit livecd desktop kickstart file > instead of base. That would fix the issues. That seems to make sense. I'll change the games dvd kickstart to use the livecd desktop kickstart. From lewis at codesign2.com Tue Dec 16 07:47:19 2008 From: lewis at codesign2.com (lewis at codesign2.com) Date: Mon, 15 Dec 2008 23:47:19 -0800 (PST) Subject: [Fedora-livecd-list] Kickstarts Message-ID: How can I get the kickstart to configure the desktop im trying to make something for my neice with autism but i need to disable all gnome menu's and kickstart is gonna configure anything is it best to use the %post in the kickstart to do this in From bkearney at redhat.com Tue Dec 16 12:57:50 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Tue, 16 Dec 2008 07:57:50 -0500 Subject: [Fedora-livecd-list] Kickstarts In-Reply-To: References: Message-ID: <4947A5CE.6020404@redhat.com> lewis at codesign2.com wrote: > How can I get the kickstart to configure the desktop im trying to make > something for my neice with autism but i need to disable all gnome menu's > and kickstart is gonna configure anything is it best to use the %post in > the kickstart to do this in > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list If you know the command lines to perform what you want, then the %post section int he kickstart is the way to go. -- b k From bruno at wolff.to Tue Dec 16 16:09:34 2008 From: bruno at wolff.to (Bruno Wolff III) Date: Tue, 16 Dec 2008 10:09:34 -0600 Subject: [Fedora-livecd-list] Allowing livecd images large than 4GiB Message-ID: <20081216160934.GA2390@wolff.to> I have submitted a feature request (allow with a patch to implement the feature) for livecd-creator to use udf instead of iso9660 so that the images can be larger than 4GiB. This would allow full use of DVDs (the lowest maximum size for standard sized disks is 4.7GB) adding about 400MB of compressed space. This could also be used to create much larger spins for use on live usb's. I have successfully tested my patch on a spin that was over 4GiB, but still fit on a DVD. The testing wasn't that extensive, but it booted and I was able to run a couple of games without seeing a problem. I am not an expert in DVD/CD formats so there may be things I have missed. The feature request is bug 476696. From bjs at redhat.com Tue Dec 16 17:10:30 2008 From: bjs at redhat.com (Bryan J Smith) Date: Tue, 16 Dec 2008 12:10:30 -0500 Subject: [Fedora-livecd-list] Allowing livecd images large than 4GiB In-Reply-To: <20081216160934.GA2390@wolff.to> References: <20081216160934.GA2390@wolff.to> Message-ID: <1229447430.4114.21.camel@localhost.localdomain> On Tue, 2008-12-16 at 10:09 -0600, Bruno Wolff III wrote: > I have submitted a feature request (allow with a patch to implement the > feature) for livecd-creator to use udf instead of iso9660 so that the > images can be larger than 4GiB. This would allow full use of DVDs > (the lowest maximum size for standard sized disks is 4.7GB) adding about > 400MB of compressed space. This could also be used to create much larger > spins for use on live usb's. > I have successfully tested my patch on a spin that was over 4GiB, but still > fit on a DVD. The testing wasn't that extensive, but it booted and I was > able to run a couple of games without seeing a problem. > I am not an expert in DVD/CD formats so there may be things I have missed. > The feature request is bug 476696. 1) I've mastered ISO 9660 Yellow Book tracks ("data" aka ".iso files") bigger than 4GiB before with mkisofs. I have used 3rd Gen Matsushita DVD-RAM drives (the first with DVD-R) for over 6 years to record these images to DVD-R, and the LG GSA SuperMulti DVD Consortium firmware for the last 4 years. I noted this from Wikipedia ... "It is, however, possible to circumvent this limitation by using the multi-extent (fragmentation) feature of ISO 9660 Level 3. With this, files larger than 4 GiB can be split up into multiple extents (sequential series of sectors), each not exceeding the 4 GiB limit. For example, the free software such as infrarecorder and mkisofs as well as Roxio Toast are able to create ISO 9660 filesystems that use multi-extent files to store files larger than 4 GiB on appropriate media such as recordable DVDs. Empirical tests with a 4.2 GiB fragmented file on a DVD media have shown that Microsoft Windows XP supports this, while Mac OS X (as of 10.4.8) does not handle this case properly. In the case of Mac OS X, the driver appears not to support file fragmentation at all (i.e. it only supports ISO 9660 Level 2 but not Level 3). Linux supports multiple extents.[4] FreeBSD only shows and reads the last extent of a multi-extent file." 2) Does El'Torito support booting from UDF media, instead of ISO 9660 Yellow Book tracks? Or ISOLinux for that matter? If anything, it seems there is no reason not to continue utilizing ISO 9660. I see no reason that you wouldn't have ISOLinux and all of its files inside of the first 4GiB, before the Linux kernel loads with ISO 9660 Level 3 support. Heck, does ISOLinux support Level 3 as well? -- Bryan P.S. It's best to clarify DVD-R(G) as 4.35GiB and not just 4.7GB (which some people may assume is 4.7GiB, when it's only 4.35GiB). -- Bryan J Smith - Senior Consultant - Red Hat GPS SE US mailto:bjs at redhat.com +1 (407) 489-7013 (Mobile) mailto:b.j.smith at ieee.org (non-RH/ext to Blackberry) ----------------------------------------------------- For every dollar you spend on Red Hat solutions, you not only fund the leading community development re- source, but you receive the #1 IT industry leader in corporate value. http://www.redhat.com/promo/vendor/ From bjs at redhat.com Tue Dec 16 17:19:15 2008 From: bjs at redhat.com (Bryan J Smith) Date: Tue, 16 Dec 2008 12:19:15 -0500 Subject: [Fedora-livecd-list] Allowing livecd images large than 4GiB In-Reply-To: <1229447430.4114.21.camel@localhost.localdomain> References: <20081216160934.GA2390@wolff.to> <1229447430.4114.21.camel@localhost.localdomain> Message-ID: <1229447955.4114.23.camel@localhost.localdomain> On Tue, 2008-12-16 at 12:10 -0500, Bryan J Smith wrote: > 2) Does El'Torito support booting from UDF media, instead of ISO 9660 > Yellow Book tracks? Or ISOLinux for that matter? BTW, what did you test on? I could see this working on EFI systems. There are always non PC BIOS considerations. If you tested on PC BIOS, which one? Just curious. > P.S. It's best to clarify DVD-R(G) as 4.35GiB and not just 4.7GB (which > some people may assume is 4.7GiB, when it's only 4.35GiB). -- Bryan J Smith - Senior Consultant - Red Hat GPS SE US mailto:bjs at redhat.com +1 (407) 489-7013 (Mobile) mailto:b.j.smith at ieee.org (non-RH/ext to Blackberry) ----------------------------------------------------- For every dollar you spend on Red Hat solutions, you not only fund the leading community development re- source, but you receive the #1 IT industry leader in corporate value. http://www.redhat.com/promo/vendor/ From bruno at wolff.to Tue Dec 16 17:33:43 2008 From: bruno at wolff.to (Bruno Wolff III) Date: Tue, 16 Dec 2008 11:33:43 -0600 Subject: [Fedora-livecd-list] Allowing livecd images large than 4GiB In-Reply-To: <1229447955.4114.23.camel@localhost.localdomain> References: <20081216160934.GA2390@wolff.to> <1229447430.4114.21.camel@localhost.localdomain> <1229447955.4114.23.camel@localhost.localdomain> Message-ID: <20081216173343.GA10215@wolff.to> On Tue, Dec 16, 2008 at 12:19:15 -0500, Bryan J Smith wrote: > On Tue, 2008-12-16 at 12:10 -0500, Bryan J Smith wrote: > > 2) Does El'Torito support booting from UDF media, instead of ISO 9660 > > Yellow Book tracks? Or ISOLinux for that matter? > > BTW, what did you test on? > I could see this working on EFI systems. > There are always non PC BIOS considerations. > If you tested on PC BIOS, which one? > Just curious. I tested it on a dual athlon system. The last motherboard update was something on the order of 5 years ago. So I would expect things to work on a wide range of systems. My reading of the documentation was that the iso image looks like iso9660 except the file size for the isoimage is reduced and hence is inconsistent with the udf information. The documentation said that to access the file you would need to mount it with the udf or ufs drivers. My expectation is the bios never gets that far as it only needs to see the boot information. Once things are booting and linux is running I wouldn't expect problems. From bruno at wolff.to Tue Dec 16 17:35:55 2008 From: bruno at wolff.to (Bruno Wolff III) Date: Tue, 16 Dec 2008 11:35:55 -0600 Subject: [Fedora-livecd-list] Allowing livecd images large than 4GiB In-Reply-To: <1229447430.4114.21.camel@localhost.localdomain> References: <20081216160934.GA2390@wolff.to> <1229447430.4114.21.camel@localhost.localdomain> Message-ID: <20081216173555.GB10215@wolff.to> On Tue, Dec 16, 2008 at 12:10:30 -0500, Bryan J Smith wrote: > > If anything, it seems there is no reason not to continue utilizing ISO > 9660. I see no reason that you wouldn't have ISOLinux and all of its > files inside of the first 4GiB, before the Linux kernel loads with ISO > 9660 Level 3 support. Heck, does ISOLinux support Level 3 as well? Is that better supported than udf? Is it easy to use with mkisofs? Is there a way to guaranty proper placement of /boot where the bios can see it? From bjs at redhat.com Tue Dec 16 17:57:22 2008 From: bjs at redhat.com (Bryan J Smith) Date: Tue, 16 Dec 2008 12:57:22 -0500 Subject: [Fedora-livecd-list] Allowing livecd images large than 4GiB In-Reply-To: <20081216173343.GA10215@wolff.to> References: <20081216160934.GA2390@wolff.to> <1229447430.4114.21.camel@localhost.localdomain> <1229447955.4114.23.camel@localhost.localdomain> <20081216173343.GA10215@wolff.to> Message-ID: <1229450242.4114.35.camel@localhost.localdomain> On Tue, 2008-12-16 at 11:33 -0600, Bruno Wolff III wrote: > I tested it on a dual athlon system. The last motherboard update was something > on the order of 5 years ago. So I would expect things to work on a wide > range of systems. Well, then I'd say you tested it. You're sure the filesystem is UDF Plain, correct? It wasn't ISO 9660 Yellow Book (possibly as a result of UDF not being accepted as an option for some reason)? > My reading of the documentation was that the iso image looks like iso9660 > except the file size for the isoimage is reduced and hence is inconsistent > with the udf information. I've actually never dissected the ISO files I regularly create with mkisofs. But I know I've gone beyond 4.0GiB (~4.3GB) before, so they must be Level 3. We're kinda spoiled on Linux, because an .iso file != as written, but the kernel hides a lot of that in the block access. An .iso file, last time I checked, is ISO 9660 "Yellow Book" (data) track. So I'm curious if an .iso file, as well as written to optical media, is still a single track for > 4.0GiB (> ~4.3GB), or multiple Yellow Book tracks with the extent in the first. > The documentation said that to access the file > you would need to mount it with the udf or ufs drivers. My expectation > is the bios never gets that far as it only needs to see the boot information. Depends. I was under the impression that when not using PC BIOS floppy emulation, but native mode with El Torito, it uses still requires and accesses the ISO 9660 Yellow Track, which needs to have filenames limited to 31 characters. But I might be confusing ISOLinux specifics. > Once things are booting and linux is running I wouldn't expect problems. Agreed there. -- Bryan J Smith - Senior Consultant - Red Hat GPS SE US mailto:bjs at redhat.com +1 (407) 489-7013 (Mobile) mailto:b.j.smith at ieee.org (non-RH/ext to Blackberry) ----------------------------------------------------- For every dollar you spend on Red Hat solutions, you not only fund the leading community development re- source, but you receive the #1 IT industry leader in corporate value. http://www.redhat.com/promo/vendor/ From bruno at wolff.to Tue Dec 16 20:25:30 2008 From: bruno at wolff.to (Bruno Wolff III) Date: Tue, 16 Dec 2008 14:25:30 -0600 Subject: [Fedora-livecd-list] Allowing livecd images large than 4GiB In-Reply-To: <1229450242.4114.35.camel@localhost.localdomain> References: <20081216160934.GA2390@wolff.to> <1229447430.4114.21.camel@localhost.localdomain> <1229447955.4114.23.camel@localhost.localdomain> <20081216173343.GA10215@wolff.to> <1229450242.4114.35.camel@localhost.localdomain> Message-ID: <20081216202530.GA5858@wolff.to> On Tue, Dec 16, 2008 at 12:57:22 -0500, Bryan J Smith wrote: > > Well, then I'd say you tested it. You're sure the filesystem is UDF > Plain, correct? It wasn't ISO 9660 Yellow Book (possibly as a result of > UDF not being accepted as an option for some reason)? I am not sure how to tell. I changed things so the initscript was going to mount it using a fs type of udf. On the test before I changed the drivers and the fs type the mount failed. > I've actually never dissected the ISO files I regularly create with > mkisofs. But I know I've gone beyond 4.0GiB (~4.3GB) before, so they > must be Level 3. The livecd-creator process barfs in the squashfs file system is over 4 GIB compressed. The mkisofs documentation says this should happen at 2 GiB. So I am not entirely sure what gives there. > We're kinda spoiled on Linux, because an .iso file != as written, but > the kernel hides a lot of that in the block access. An .iso file, last > time I checked, is ISO 9660 "Yellow Book" (data) track. So I'm curious > if an .iso file, as well as written to optical media, is still a single > track for > 4.0GiB (> ~4.3GB), or multiple Yellow Book tracks with the > extent in the first. I suspect it was one track, but I don't know for sure. I used k3b and the burn iso dvd tool. > Depends. I was under the impression that when not using PC BIOS floppy > emulation, but native mode with El Torito, it uses still requires and > accesses the ISO 9660 Yellow Track, which needs to have filenames > limited to 31 characters. But there aren't many files visible at that level. A few things in the equivalent of /boot and the rest is the file containing the squashfs file system. From bjs at redhat.com Tue Dec 16 21:14:40 2008 From: bjs at redhat.com (Bryan J Smith) Date: Tue, 16 Dec 2008 16:14:40 -0500 Subject: [Fedora-livecd-list] Allowing livecd images large than 4GiB In-Reply-To: <20081216202530.GA5858@wolff.to> References: <20081216160934.GA2390@wolff.to> <1229447430.4114.21.camel@localhost.localdomain> <1229447955.4114.23.camel@localhost.localdomain> <20081216173343.GA10215@wolff.to> <1229450242.4114.35.camel@localhost.localdomain> <20081216202530.GA5858@wolff.to> Message-ID: <1229462080.4114.42.camel@localhost.localdomain> On Tue, 2008-12-16 at 14:25 -0600, Bruno Wolff III wrote: > The livecd-creator process barfs in the squashfs file system is over > 4 GIB compressed. Are you sure that's squashfs, or the kickstart image size? I ran into that too, but it was the image size. > The mkisofs documentation says this should happen > at 2 GiB. So I am not entirely sure what gives there. You may be correct. > I suspect it was one track, but I don't know for sure. I used k3b and the > burn iso dvd tool. k3b actually uses several tools. It can use dvd+rw-tools as well. E.g., DVD+R media is actually DVD+RW, and nothing like CD-R or DVD-R. DVD+RW Consortium (Sony/Philips) firmware also has a different focus than DVD Consortium (Matsushita/Pioneer) drives. > But there aren't many files visible at that level. A few things in the > equivalent of /boot and the rest is the file containing the squashfs > file system. But doesn't the PC BIOS' El Torito support need to read the Yellow Book track to get to them? That's what I assumed, but I could be wrong. I mean, it still has to load ISOLinux. -- Bryan J Smith - Senior Consultant - Red Hat GPS SE US mailto:bjs at redhat.com +1 (407) 489-7013 (Mobile) mailto:b.j.smith at ieee.org (non-RH/ext to Blackberry) ----------------------------------------------------- For every dollar you spend on Red Hat solutions, you not only fund the leading community development re- source, but you receive the #1 IT industry leader in corporate value. http://www.redhat.com/promo/vendor/ From katzj at redhat.com Tue Dec 16 22:49:01 2008 From: katzj at redhat.com (Jeremy Katz) Date: Tue, 16 Dec 2008 17:49:01 -0500 Subject: [Fedora-livecd-list] Allowing livecd images large than 4GiB In-Reply-To: <20081216160934.GA2390@wolff.to> References: <20081216160934.GA2390@wolff.to> Message-ID: <1229467741.5054.134.camel@erebor.bos.redhat.com> On Tue, 2008-12-16 at 10:09 -0600, Bruno Wolff III wrote: > I have submitted a feature request (allow with a patch to implement the > feature) for livecd-creator to use udf instead of iso9660 so that the > images can be larger than 4GiB. This would allow full use of DVDs > (the lowest maximum size for standard sized disks is 4.7GB) adding about > 400MB of compressed space. This could also be used to create much larger > spins for use on live usb's. I'm not against allowing udf, but we should probably use iso9660 unless the size forces us to need udf just to avoid problems on as many systems as we can. Jeremy From bruno at wolff.to Tue Dec 16 23:09:07 2008 From: bruno at wolff.to (Bruno Wolff III) Date: Tue, 16 Dec 2008 17:09:07 -0600 Subject: [Fedora-livecd-list] Allowing livecd images large than 4GiB In-Reply-To: <1229467741.5054.134.camel@erebor.bos.redhat.com> References: <20081216160934.GA2390@wolff.to> <1229467741.5054.134.camel@erebor.bos.redhat.com> Message-ID: <20081216230907.GA30207@wolff.to> On Tue, Dec 16, 2008 at 17:49:01 -0500, Jeremy Katz wrote: > On Tue, 2008-12-16 at 10:09 -0600, Bruno Wolff III wrote: > > I have submitted a feature request (allow with a patch to implement the > > feature) for livecd-creator to use udf instead of iso9660 so that the > > images can be larger than 4GiB. This would allow full use of DVDs > > (the lowest maximum size for standard sized disks is 4.7GB) adding about > > 400MB of compressed space. This could also be used to create much larger > > spins for use on live usb's. > > I'm not against allowing udf, but we should probably use iso9660 unless > the size forces us to need udf just to avoid problems on as many systems > as we can. So something that checked the size of the mksquashfs and switched automatically between the two and emitting a message about this could be acceptable? I don't really know python yet, so I may not be able to easily change my previous patch to do that, but want to check before going down that road. I think having access to teh extra space will be nice for the Games Spin as things are pretty tight right now and a few hundred MB would be nice to have. From katzj at redhat.com Tue Dec 16 23:41:57 2008 From: katzj at redhat.com (Jeremy Katz) Date: Tue, 16 Dec 2008 18:41:57 -0500 Subject: [Fedora-livecd-list] Allowing livecd images large than 4GiB In-Reply-To: <20081216230907.GA30207@wolff.to> References: <20081216160934.GA2390@wolff.to> <1229467741.5054.134.camel@erebor.bos.redhat.com> <20081216230907.GA30207@wolff.to> Message-ID: On Dec 16, 2008, at 6:09 PM, Bruno Wolff III wrote: > On Tue, Dec 16, 2008 at 17:49:01 -0500, > Jeremy Katz wrote: >> On Tue, 2008-12-16 at 10:09 -0600, Bruno Wolff III wrote: >>> I have submitted a feature request (allow with a patch to >>> implement the >>> feature) for livecd-creator to use udf instead of iso9660 so that >>> the >>> images can be larger than 4GiB. This would allow full use of DVDs >>> (the lowest maximum size for standard sized disks is 4.7GB) adding >>> about >>> 400MB of compressed space. This could also be used to create much >>> larger >>> spins for use on live usb's. >> >> I'm not against allowing udf, but we should probably use iso9660 >> unless >> the size forces us to need udf just to avoid problems on as many >> systems >> as we can. > > So something that checked the size of the mksquashfs and switched > automatically > between the two and emitting a message about this could be acceptable? > I don't really know python yet, so I may not be able to easily change > my previous patch to do that, but want to check before going down > that road. Yep, exactly what I'm thinking. And it should be a fairly straight forward matter of doing os.stat on the squashfs and then looking at the size from that Jeremy From bjs at redhat.com Wed Dec 17 15:07:19 2008 From: bjs at redhat.com (Bryan J Smith) Date: Wed, 17 Dec 2008 10:07:19 -0500 Subject: [Fedora-livecd-list] Allowing livecd images large than 4GiB In-Reply-To: <1229467741.5054.134.camel@erebor.bos.redhat.com> References: <20081216160934.GA2390@wolff.to> <1229467741.5054.134.camel@erebor.bos.redhat.com> Message-ID: <1229526439.6133.1.camel@localhost.localdomain> On Tue, 2008-12-16 at 17:49 -0500, Jeremy Katz wrote: > I'm not against allowing udf, but we should probably use iso9660 unless > the size forces us to need udf just to avoid problems on as many systems > as we can. I just wanted to note that I was analyzing from a standpoint of ignorance and assumption, and not hands-on testing with the patch. I don't anyone basing decisions on my commentary other than as a "review," but not actual testing. -- Bryan J Smith - Senior Consultant - Red Hat GPS SE US mailto:bjs at redhat.com +1 (407) 489-7013 (Mobile) mailto:b.j.smith at ieee.org (non-RH/ext to Blackberry) ----------------------------------------------------- For every dollar you spend on Red Hat solutions, you not only fund the leading community development re- source, but you receive the #1 IT industry leader in corporate value. http://www.redhat.com/promo/vendor/ From katzj at fedoraproject.org Fri Dec 19 18:45:03 2008 From: katzj at fedoraproject.org (Jeremy Katz) Date: Fri, 19 Dec 2008 18:45:03 +0000 (UTC) Subject: [Fedora-livecd-list] tools/livecd-creator Message-ID: <20081219184503.1F247C024D@lists.fedorahosted.org> tools/livecd-creator | 2 ++ 1 file changed, 2 insertions(+) New commits: commit 75193172b7636d1d274cc064b4386161a5488142 Author: Jeremy Katz Date: Fri Dec 19 13:43:55 2008 -0500 Don't allow spaces in labels (#475834) diff --git a/tools/livecd-creator b/tools/livecd-creator index 6d84e4c..719c874 100755 --- a/tools/livecd-creator +++ b/tools/livecd-creator @@ -73,6 +73,8 @@ def parse_options(args): raise Usage("Live CD ISO '%s' does not exist" %(options.base_on,)) if options.fs_label and len(options.fs_label) > imgcreate.FSLABEL_MAXLEN: raise Usage("CD labels are limited to 32 characters") + if options.fs_label and options.fs_label.find(" ") != -1: + raise Usage("CD labels cannot contain spaces.") return options From katzj at fedoraproject.org Fri Dec 19 18:57:30 2008 From: katzj at fedoraproject.org (Jeremy Katz) Date: Fri, 19 Dec 2008 18:57:30 +0000 (UTC) Subject: [Fedora-livecd-list] tools/livecd-iso-to-disk.sh Message-ID: <20081219185730.A9C8CC024D@lists.fedorahosted.org> tools/livecd-iso-to-disk.sh | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-) New commits: commit 44f4ec462d011e5dec4c67d7559538c3b8f08a0f Author: Matt Domsch Date: Fri Dec 19 13:56:09 2008 -0500 Improvements for encrypted /home setup (#475399) 1) if you're going to use an encrypted volume, it's best to pre-fill the volume with random data. Using /dev/urandom, it's fast enough. Only do this for non-sparse-file-backed encrypted home. Could arguably drop sparse-file-backed encrypted home and do this everywhere, but that would definitely be slower. 2) if any of the cryptsetup commands fail (bad password typed), keep trying. Otherwise, a typo means the whole process dies badly and you have to start from scratch. diff --git a/tools/livecd-iso-to-disk.sh b/tools/livecd-iso-to-disk.sh index 4414c4e..5371db1 100755 --- a/tools/livecd-iso-to-disk.sh +++ b/tools/livecd-iso-to-disk.sh @@ -510,19 +510,29 @@ fi if [ "$homesizemb" -gt 0 ]; then echo "Initializing persistent /home" + homesource=/dev/zero + [ -n "$cryptedhome" ] && homesource=/dev/urandom if [ "$USBFS" = "vfat" ]; then # vfat can't handle sparse files - dd if=/dev/zero of=$USBMNT/LiveOS/$HOMEFILE count=$homesizemb bs=1M + dd if=${homesource} of=$USBMNT/LiveOS/$HOMEFILE count=$homesizemb bs=1M else dd if=/dev/null of=$USBMNT/LiveOS/$HOMEFILE count=1 bs=1M seek=$homesizemb fi if [ -n "$cryptedhome" ]; then loop=$(losetup -f) losetup $loop $USBMNT/LiveOS/$HOMEFILE - echo "Encrypting persistent /home" - cryptsetup luksFormat -y -q $loop - echo "Please enter the password again to unlock the device" - cryptsetup luksOpen $loop EncHomeFoo + setupworked=1 + until [ ${setupworked} == 0 ]; do + echo "Encrypting persistent /home" + cryptsetup luksFormat -y -q $loop + setupworked=$? + done + setupworked=1 + until [ ${setupworked} == 0 ]; do + echo "Please enter the password again to unlock the device" + cryptsetup luksOpen $loop EncHomeFoo + setupworked=$? + done mke2fs -j /dev/mapper/EncHomeFoo tune2fs -c0 -i0 -ouser_xattr,acl /dev/mapper/EncHomeFoo cryptsetup luksClose EncHomeFoo From katzj at fedoraproject.org Fri Dec 19 19:02:32 2008 From: katzj at fedoraproject.org (Jeremy Katz) Date: Fri, 19 Dec 2008 19:02:32 +0000 (UTC) Subject: [Fedora-livecd-list] Branch 'f9-branch' - 2 commits - config/livecd-fedora-9-base-desktop.ks livecd-tools.spec Makefile Message-ID: <20081219190232.4DE10C024D@lists.fedorahosted.org> Makefile | 2 +- config/livecd-fedora-9-base-desktop.ks | 1 + livecd-tools.spec | 8 +++++++- 3 files changed, 9 insertions(+), 2 deletions(-) New commits: commit 1377c8d9141218ac57e335e4ab10d4862586a9f5 Author: Jeremy Katz Date: Fri Dec 19 14:01:26 2008 -0500 Bump to 0.17.2 diff --git a/Makefile b/Makefile index 5cdc7a2..c790cc2 100644 --- a/Makefile +++ b/Makefile @@ -1,5 +1,5 @@ -VERSION = 017.1 +VERSION = 017.2 INSTALL = /usr/bin/install -c INSTALL_PROGRAM = ${INSTALL} diff --git a/livecd-tools.spec b/livecd-tools.spec index c3ab86d..c6198c2 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.1 +Version: 017.2 Release: 1%{?dist} License: GPLv2 Group: System Environment/Base @@ -62,6 +62,12 @@ rm -rf $RPM_BUILD_ROOT %{python_sitelib}/imgcreate/*.pyc %changelog +* Fri Dec 19 2008 Jeremy Katz - 017.2-1 +- Add newkey repo (#477067) +- Fix --base-on even more +- Don't fail if devices exist +- Remove old rpmdb locks + * Mon Jun 16 2008 Jeremy Katz - 017.1-1 - Handle copying timezone to /etc/localtime (#445624) - livecd-iso-to-disk: Ensure disk isn't mounted before writing to it (#446472) commit db812bde356961492a6238e89f92eda62c8cf596 Author: Jeremy Katz Date: Fri Dec 19 13:59:37 2008 -0500 Add newkey repo (#477067) diff --git a/config/livecd-fedora-9-base-desktop.ks b/config/livecd-fedora-9-base-desktop.ks index 0b21d9a..3d14326 100644 --- a/config/livecd-fedora-9-base-desktop.ks +++ b/config/livecd-fedora-9-base-desktop.ks @@ -10,6 +10,7 @@ services --enabled=NetworkManager --disabled=network,sshd repo --name=released --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-9&arch=$basearch repo --name=updates --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f9&arch=$basearch +repo --name=updates.newkey --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f9.newkey&arch=$basearch %packages @base-x From christian08 at runbox.com Fri Dec 19 19:15:26 2008 From: christian08 at runbox.com (Christian) Date: Fri, 19 Dec 2008 20:15:26 +0100 Subject: [Fedora-livecd-list] Logging in as root Message-ID: <200812192015260843.002CA7D2@127.0.0.1> Hi all, I want to install FC10 from the Live CD. However I am visually impaired and rely on speech and orca needs to be running as root in order for the installation program to be accessible. When I do sudo su from the gnome-terminal the live user is not in the sudors file. Any help would be apreciated, many thanks! From hobbes1069 at gmail.com Fri Dec 19 19:23:09 2008 From: hobbes1069 at gmail.com (Richard Shaw) Date: Fri, 19 Dec 2008 13:23:09 -0600 Subject: [Fedora-livecd-list] Logging in as root In-Reply-To: <200812192015260843.002CA7D2@127.0.0.1> References: <200812192015260843.002CA7D2@127.0.0.1> Message-ID: <373c76480812191123g296e15c4yd820ded24474301d@mail.gmail.com> On Fri, Dec 19, 2008 at 1:15 PM, Christian wrote: > Hi all, > I want to install FC10 from the Live CD. > However I am visually impaired and rely on speech and orca needs to be running as root in order for the installation program to be accessible. > When I do > sudo su from the gnome-terminal the live user is not in the sudors file. > Any help would be apreciated, many thanks! You could try: su -c '' In this case it would be the actual root password. Richard From christian08 at runbox.com Fri Dec 19 19:42:34 2008 From: christian08 at runbox.com (Christian) Date: Fri, 19 Dec 2008 20:42:34 +0100 Subject: [Fedora-livecd-list] Logging in as root In-Reply-To: <373c76480812191123g296e15c4yd820ded24474301d@mail.gmail.com> References: <200812192015260843.002CA7D2@127.0.0.1> <373c76480812191123g296e15c4yd820ded24474301d@mail.gmail.com> Message-ID: <200812192042340437.00457D9C@127.0.0.1> Hi, So i can then run maybe: sudo -c orca? On 2008-12-19 at 13:23 Richard Shaw wrote: >On Fri, Dec 19, 2008 at 1:15 PM, Christian wrote: >> Hi all, >> I want to install FC10 from the Live CD. >> However I am visually impaired and rely on speech and orca needs to be >running as root in order for the installation program to be accessible. >> When I do >> sudo su from the gnome-terminal the live user is not in the sudors file. >> Any help would be apreciated, many thanks! > >You could try: > > su -c '' > >In this case it would be the actual root password. > >Richard > >-- >Fedora-livecd-list mailing list >Fedora-livecd-list at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-livecd-list From christian08 at runbox.com Fri Dec 19 21:50:09 2008 From: christian08 at runbox.com (Christian) Date: Fri, 19 Dec 2008 22:50:09 +0100 Subject: [Fedora-livecd-list] After installation Message-ID: <200812192250090000.00034A97@127.0.0.1> Hi all, OK, i finally managed to install the whole system with the help of the screen reader Orca for Gnome. When I reboot the machine I think I am supposed to logon. I type root and the root password I provided during the installtion but nothing happens. Am I placed at a logon screen? Any help would be apreciated many thanks! From jkeating at redhat.com Fri Dec 19 22:04:57 2008 From: jkeating at redhat.com (Jesse Keating) Date: Fri, 19 Dec 2008 14:04:57 -0800 Subject: [Fedora-livecd-list] After installation In-Reply-To: <200812192250090000.00034A97@127.0.0.1> References: <200812192250090000.00034A97@127.0.0.1> Message-ID: <1229724297.3861.5.camel@localhost.localdomain> On Fri, 2008-12-19 at 22:50 +0100, Christian wrote: > Hi all, > OK, i finally managed to install the whole system with the help of the screen reader Orca for Gnome. > When I reboot the machine I think I am supposed to logon. I type root and the root password I provided during the installtion but nothing happens. Am I placed at a logon screen? Any help would be apreciated many thanks! Root logins are no longer acceptable with GDM by default. -- 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 christian08 at runbox.com Fri Dec 19 22:14:50 2008 From: christian08 at runbox.com (Christian) Date: Fri, 19 Dec 2008 23:14:50 +0100 Subject: [Fedora-livecd-list] After installation In-Reply-To: <1229724297.3861.5.camel@localhost.localdomain> References: <200812192250090000.00034A97@127.0.0.1> <1229724297.3861.5.camel@localhost.localdomain> Message-ID: <200812192314500265.0019E4C8@127.0.0.1> OK, so how do i logon to the system then? I was not prompted to create a user during the installation process, but i am going to make it again since i have to check a few things here. Many thanks, Christian On 2008-12-19 at 14:04 Jesse Keating wrote: >On Fri, 2008-12-19 at 22:50 +0100, Christian wrote: >> Hi all, >> OK, i finally managed to install the whole system with the help of the >screen reader Orca for Gnome. >> When I reboot the machine I think I am supposed to logon. I type root >and the root password I provided during the installtion but nothing >happens. Am I placed at a logon screen? Any help would be apreciated many >thanks! > >Root logins are no longer acceptable with GDM by default. > >-- >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 opensource at till.name Fri Dec 19 22:24:45 2008 From: opensource at till.name (Till Maas) Date: Fri, 19 Dec 2008 23:24:45 +0100 Subject: [Fedora-livecd-list] After installation In-Reply-To: <200812192250090000.00034A97@127.0.0.1> References: <200812192250090000.00034A97@127.0.0.1> Message-ID: <200812192324.51949.opensource@till.name> On Fri December 19 2008, Christian wrote: > OK, i finally managed to install the whole system with the help of the > screen reader Orca for Gnome. When I reboot the machine I think I am > supposed to logon. I type root and the root password I provided during the > installtion but nothing happens. Am I placed at a logon screen? Any help > would be apreciated many thanks! On my system after installation, there are accessibility tools available already within gdm, but they seem to be only reachable using a mouse. There is a icon near the right, buttom corner that allows open a window, where they can be activated. On my German system, with this windows open, ALT-p activates a screen reader program according to a checkbox that get's checked then. But I did not notice any difference or sound output with this option enabled. Regards, Till From jkeating at redhat.com Fri Dec 19 22:30:59 2008 From: jkeating at redhat.com (Jesse Keating) Date: Fri, 19 Dec 2008 14:30:59 -0800 Subject: [Fedora-livecd-list] After installation In-Reply-To: <200812192314500265.0019E4C8@127.0.0.1> References: <200812192250090000.00034A97@127.0.0.1> <1229724297.3861.5.camel@localhost.localdomain> <200812192314500265.0019E4C8@127.0.0.1> Message-ID: <1229725859.3861.6.camel@localhost.localdomain> On Fri, 2008-12-19 at 23:14 +0100, Christian wrote: > > OK, so how do i logon to the system then? > I was not prompted to create a user during the installation process, > but i am going to make it again since i have to check a few things > here. firstboot prompts you to create a user, and firstboot runs the first time you boot a system post-install. -- 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 christian08 at runbox.com Fri Dec 19 22:42:54 2008 From: christian08 at runbox.com (Christian) Date: Fri, 19 Dec 2008 23:42:54 +0100 Subject: [Fedora-livecd-list] After installation In-Reply-To: <1229725859.3861.6.camel@localhost.localdomain> References: <200812192250090000.00034A97@127.0.0.1> <1229724297.3861.5.camel@localhost.localdomain> <200812192314500265.0019E4C8@127.0.0.1> <1229725859.3861.6.camel@localhost.localdomain> Message-ID: <200812192342540375.00339756@127.0.0.1> Hi, On 2008-12-19 at 14:30 Jesse Keating wrote: >On Fri, 2008-12-19 at 23:14 +0100, Christian wrote: >> >> OK, so how do i logon to the system then? >> I was not prompted to create a user during the installation process, >> but i am going to make it again since i have to check a few things >> here. > >firstboot prompts you to create a user, and firstboot runs the first >time you boot a system post-install. > >-- >Jesse Keating >Fedora -- Freedom?? is a feature! >identi.ca: http://identi.ca/jkeating > > OK, is it only the user its asking for? Can I just type the username, then press enter. Then etner a password for that user and press enter again. Then confirm the password and then press enter again? I simply pressed enter the first time i booted the new system. Best regards and thanks, Christian >-- >Fedora-livecd-list mailing list >Fedora-livecd-list at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-livecd-list From christian08 at runbox.com Fri Dec 19 22:46:24 2008 From: christian08 at runbox.com (Christian) Date: Fri, 19 Dec 2008 23:46:24 +0100 Subject: [Fedora-livecd-list] After installation In-Reply-To: <200812192324.51949.opensource@till.name> References: <200812192250090000.00034A97@127.0.0.1> <200812192324.51949.opensource@till.name> Message-ID: <200812192346240171.0036CADB@127.0.0.1> Hi, On 2008-12-19 at 23:24 Till Maas wrote: >On Fri December 19 2008, Christian wrote: > >> OK, i finally managed to install the whole system with the help of the >> screen reader Orca for Gnome. When I reboot the machine I think I am >> supposed to logon. I type root and the root password I provided during >the >> installtion but nothing happens. Am I placed at a logon screen? Any help >> would be apreciated many thanks! > >On my system after installation, there are accessibility tools available >already within gdm, but they seem to be only reachable using a mouse. >There is >a icon near the right, buttom corner that allows open a window, where they >can >be activated. On my German system, with this windows open, ALT-p activates >a >screen reader program according to a checkbox that get's checked then. But >I >did not notice any difference or sound output with this option enabled. > >Regards, >Till > > If you press alt-F2 for run a command, then type orca. That should launch the screen reader and you are prompted to set various settings and enable accessibility. Best regards, Christian >-- >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 Mon Dec 22 09:05:56 2008 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Mon, 22 Dec 2008 14:35:56 +0530 Subject: [Fedora-livecd-list] After installation In-Reply-To: <200812192342540375.00339756@127.0.0.1> References: <200812192250090000.00034A97@127.0.0.1> <1229724297.3861.5.camel@localhost.localdomain> <200812192314500265.0019E4C8@127.0.0.1> <1229725859.3861.6.camel@localhost.localdomain> <200812192342540375.00339756@127.0.0.1> Message-ID: <494F5874.70200@fedoraproject.org> Christian wrote: > OK, is it only the user its asking for? > Can I just type the username, then press enter. Then etner a password for that user and press enter again. Then confirm the password and then press enter again? > I simply pressed enter the first time i booted the new system. > Best regards and thanks, In firstboot, which is what you get the first time, you reboot, post-installation, the third screen is for creating a user. It is structured like this: Username: enter your username Full Name: your full name Password: enter the password Confirm Password: repeat the password After that press enter again to forward to the next screen for date and time and then the last one for sending your hardware profile. When you boot, GDM has a face browser which shows your full name, you can click and just enter your password or go to "other" and then enter your username , followed by your password to login. Hope that helps Rahul From christian08 at runbox.com Tue Dec 23 00:01:32 2008 From: christian08 at runbox.com (Christian) Date: Tue, 23 Dec 2008 01:01:32 +0100 Subject: [Fedora-livecd-list] After installation In-Reply-To: <494F5874.70200@fedoraproject.org> References: <200812192250090000.00034A97@127.0.0.1> <1229724297.3861.5.camel@localhost.localdomain> <200812192314500265.0019E4C8@127.0.0.1> <1229725859.3861.6.camel@localhost.localdomain> <200812192342540375.00339756@127.0.0.1> <494F5874.70200@fedoraproject.org> Message-ID: <200812230101320796.002E97BC@127.0.0.1> Hello, Many thanks for your reply. May I also skip that firstboot screen by pressing escape? May I bring up a standard console with ctrl-alt-f1 and login as root? Many thanks, Christian On 2008-12-22 at 14:35 Rahul Sundaram wrote: >Christian wrote: > >> OK, is it only the user its asking for? >> Can I just type the username, then press enter. Then etner a password >for that user and press enter again. Then confirm the password and then >press enter again? >> I simply pressed enter the first time i booted the new system. >> Best regards and thanks, > >In firstboot, which is what you get the first time, you reboot, >post-installation, the third screen is for creating a user. It is >structured like this: > >Username: enter your username >Full Name: your full name >Password: enter the password >Confirm Password: repeat the password > >After that press enter again to forward to the next screen for date and >time and then the last one for sending your hardware profile. When you >boot, GDM has a face browser which shows your full name, you can click >and just enter your password or go to "other" and then enter your >username , followed by your password to login. > >Hope that helps > >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 Tue Dec 23 00:09:03 2008 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Tue, 23 Dec 2008 05:39:03 +0530 Subject: [Fedora-livecd-list] After installation In-Reply-To: <200812230101320796.002E97BC@127.0.0.1> References: <200812192250090000.00034A97@127.0.0.1> <1229724297.3861.5.camel@localhost.localdomain> <200812192314500265.0019E4C8@127.0.0.1> <1229725859.3861.6.camel@localhost.localdomain> <200812192342540375.00339756@127.0.0.1> <494F5874.70200@fedoraproject.org> <200812230101320796.002E97BC@127.0.0.1> Message-ID: <49502C1F.8000708@fedoraproject.org> Christian wrote: > Hello, > Many thanks for your reply. > May I also skip that firstboot screen by pressing escape? > May I bring up a standard console with ctrl-alt-f1 and login as root? Ctl+alt+f2 and login as root would work. The first virtual terminal, now runs the graphical interface in Fedora 10. Rahul From brianhurren at yahoo.com Fri Dec 26 03:12:03 2008 From: brianhurren at yahoo.com (brian hurren) Date: Thu, 25 Dec 2008 19:12:03 -0800 (PST) Subject: [Fedora-livecd-list] fedora live and the international year of astronomy. Message-ID: <283413.12474.qm@web51308.mail.re2.yahoo.com> Because Fedora10 has such a strong astronomical theme and 2009 is the international year of astronomy. why don't we do a fedora-live disk with KDE and have '2009 international year of astronomy' written on the splash screen. the KDE version already has Kstars packed with it. how about including stelerium and Pyefem as well. I am already designing a cd cover and for it. I think it would go down really well with the astronomical societies. Get the world's best email - http://nz.mail.yahoo.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From kam at kamsalisbury.com Wed Dec 31 02:32:39 2008 From: kam at kamsalisbury.com (Kam Salisbury) Date: Tue, 30 Dec 2008 21:32:39 -0500 Subject: [Fedora-livecd-list] livecd-creator kickstart files Message-ID: <818ac3c70812301832l3f4f8ab8i1b52c332f37960bb@mail.gmail.com> Is there a repository of "known good" kickstarts for use with the livecd-creator tool? The examples RPM is good but still does not really have examples of different ways to build the livecd. For example, I started with the Fedora 10 desktop file and jut keep whittling away at it until I get what I want. Once I think its "finished", should I just post the .ks file to this list? -- Kam Salisbury http://kamsalisbury.com GPG key: FAF1751E -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruno at wolff.to Wed Dec 31 02:51:42 2008 From: bruno at wolff.to (Bruno Wolff III) Date: Tue, 30 Dec 2008 20:51:42 -0600 Subject: [Fedora-livecd-list] livecd-creator kickstart files In-Reply-To: <818ac3c70812301832l3f4f8ab8i1b52c332f37960bb@mail.gmail.com> References: <818ac3c70812301832l3f4f8ab8i1b52c332f37960bb@mail.gmail.com> Message-ID: <20081231025142.GA6391@wolff.to> On Tue, Dec 30, 2008 at 21:32:39 -0500, Kam Salisbury wrote: > Is there a repository of "known good" kickstarts for use with the > livecd-creator tool? The examples RPM is good but still does not really have > examples of different ways to build the livecd. The spin-kickstarts package is a good starting point. From sundaram at fedoraproject.org Wed Dec 31 05:40:56 2008 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Wed, 31 Dec 2008 11:10:56 +0530 Subject: [Fedora-livecd-list] livecd-creator kickstart files In-Reply-To: <20081231025142.GA6391@wolff.to> References: <818ac3c70812301832l3f4f8ab8i1b52c332f37960bb@mail.gmail.com> <20081231025142.GA6391@wolff.to> Message-ID: <495B05E8.2020004@fedoraproject.org> Bruno Wolff III wrote: > On Tue, Dec 30, 2008 at 21:32:39 -0500, > Kam Salisbury wrote: >> Is there a repository of "known good" kickstarts for use with the >> livecd-creator tool? The examples RPM is good but still does not really have >> examples of different ways to build the livecd. > > The spin-kickstarts package is a good starting point. > Feel free to share yours as well. It might end up being useful to more people. Rahul