From brianhurren at yahoo.com Thu Jan 1 09:26:31 2009 From: brianhurren at yahoo.com (brian hurren) Date: Thu, 1 Jan 2009 01:26:31 -0800 (PST) Subject: [Fedora-livecd-list] fedora live and astronomy Message-ID: <213594.26161.qm@web51307.mail.re2.yahoo.com> I am wanting to make a fedora live disk specifically for Astronomy - to celebrate 2009 international year of astronomy. is it o.k to do this? can I add Kstars, Celestia, Pyfem, Stelarium ect. and is it ok for the Astronomical scocieties to give it away to members or ask for a donation to help the societies? ps. can anyone think of any other packages to add? is it o.k to add a modified splash screen. (see attachment) Get the world's best email - http://nz.mail.yahoo.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: splash1.jpg Type: image/jpeg Size: 213746 bytes Desc: not available URL: From valent.turkovic at gmail.com Thu Jan 1 11:14:53 2009 From: valent.turkovic at gmail.com (Valent Turkovic) Date: Thu, 1 Jan 2009 12:14:53 +0100 Subject: [Fedora-livecd-list] How to create live dvd? (livecd-creator fail) Message-ID: <64b14b300901010314j23360497x2d1aee33697f1324@mail.gmail.com> Hi, first and foremost Happy New Year! I used to be able to create live DVD with Fedora 8 and 9 using livecd-creator tool but now I can't do it anymore with Fedora 10. I get an error that there isn't enough space to create image and livecd-creator fails. I used to do it without problem, so maybe the packages have grown or I added more packages than there is space for them. I see that /dev/loop0 is created and the size of that virtual partition is only 3GB: /dev/loop0 3.0G 602M 2.4G 21% /home/temp/imgcreate-KWfqq9/install_root I guess that when space runs out in that partition livecd-creator fails. Am I right? When I trim down my kickstart files with less packages then it passes. How I managed to make live DVD iso image of 935MB. I haven't tested what is the maximum size I can make but it is now far from that - arround 950-1000MB. Livd DVD I make previously with Fedora 8 and 9 was around 1200MB. Has livecd-creator changed the way it works? If that my previous assumptions are false please correct me and I have some follow up questions: 1. How are live DVD images supposted to be made (2GB iso size)? With livecd-creator or with some other tools? Which? 2. Is there a way to define larger size for /dev/loop0 ? (I looked into man page for livecd-creator and I see no such option) Thank you very much in advance! -- http://kernelreloaded.blog385.com/ linux, blog, anime, spirituality, windsurf, wireless registered as user #367004 with the Linux Counter, http://counter.li.org. ICQ: 2125241, Skype: valent.turkovic From valent.turkovic at gmail.com Thu Jan 1 11:18:00 2009 From: valent.turkovic at gmail.com (Valent Turkovic) Date: Thu, 1 Jan 2009 12:18:00 +0100 Subject: [Fedora-livecd-list] livecd-creator kickstart files In-Reply-To: <495B05E8.2020004@fedoraproject.org> References: <818ac3c70812301832l3f4f8ab8i1b52c332f37960bb@mail.gmail.com> <20081231025142.GA6391@wolff.to> <495B05E8.2020004@fedoraproject.org> Message-ID: <64b14b300901010318k531c881r3c41cab355bfaef0@mail.gmail.com> On Wed, Dec 31, 2008 at 6:40 AM, Rahul Sundaram wrote: > 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. Yes, please share your kickstart files! -- http://kernelreloaded.blog385.com/ linux, blog, anime, spirituality, windsurf, wireless registered as user #367004 with the Linux Counter, http://counter.li.org. ICQ: 2125241, Skype: valent.turkovic From valent.turkovic at gmail.com Thu Jan 1 11:19:22 2009 From: valent.turkovic at gmail.com (Valent Turkovic) Date: Thu, 1 Jan 2009 12:19:22 +0100 Subject: [Fedora-livecd-list] livecd-creator kickstart files In-Reply-To: <64b14b300901010318k531c881r3c41cab355bfaef0@mail.gmail.com> References: <818ac3c70812301832l3f4f8ab8i1b52c332f37960bb@mail.gmail.com> <20081231025142.GA6391@wolff.to> <495B05E8.2020004@fedoraproject.org> <64b14b300901010318k531c881r3c41cab355bfaef0@mail.gmail.com> Message-ID: <64b14b300901010319j544d49d3x758f2a3c14c4a849@mail.gmail.com> On Thu, Jan 1, 2009 at 12:18 PM, Valent Turkovic wrote: > On Wed, Dec 31, 2008 at 6:40 AM, Rahul Sundaram > wrote: >> 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. > > Yes, please share your kickstart files! > Ups, I forgot, here are mine: http://dl.getdropbox.com/u/184632/private-10-live-base.ks http://dl.getdropbox.com/u/184632/private-10-desktop-livecd.ks it is based on Omega 10 + additional Fedora and some proprietary packages I need and there are no floss alternatives :( Cheers, Valent. -- http://kernelreloaded.blog385.com/ linux, blog, anime, spirituality, windsurf, wireless registered as user #367004 with the Linux Counter, http://counter.li.org. ICQ: 2125241, Skype: valent.turkovic From valent.turkovic at gmail.com Thu Jan 1 11:31:07 2009 From: valent.turkovic at gmail.com (Valent Turkovic) Date: Thu, 1 Jan 2009 12:31:07 +0100 Subject: [Fedora-livecd-list] fedora live and the international year of astronomy. In-Reply-To: <283413.12474.qm@web51308.mail.re2.yahoo.com> References: <283413.12474.qm@web51308.mail.re2.yahoo.com> Message-ID: <64b14b300901010331x69dcd31ew736a88942a34256@mail.gmail.com> On Fri, Dec 26, 2008 at 4:12 AM, brian hurren wrote: > 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. # yum install pyefem No package pyefem available. what is the package name for Pyefem ? -- http://kernelreloaded.blog385.com/ linux, blog, anime, spirituality, windsurf, wireless registered as user #367004 with the Linux Counter, http://counter.li.org. ICQ: 2125241, Skype: valent.turkovic From fulko.hew at gmail.com Thu Jan 1 13:28:36 2009 From: fulko.hew at gmail.com (Fulko Hew) Date: Thu, 1 Jan 2009 08:28:36 -0500 Subject: [Fedora-livecd-list] fedora live and the international year of astronomy. In-Reply-To: <64b14b300901010331x69dcd31ew736a88942a34256@mail.gmail.com> References: <283413.12474.qm@web51308.mail.re2.yahoo.com> <64b14b300901010331x69dcd31ew736a88942a34256@mail.gmail.com> Message-ID: <8204a4fe0901010528g34fc1d7btdf0db6b49632794d@mail.gmail.com> On Thu, Jan 1, 2009 at 6:31 AM, Valent Turkovic wrote: > On Fri, Dec 26, 2008 at 4:12 AM, brian hurren wrote: >> 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. > > # yum install pyefem > No package pyefem available. > > what is the package name for Pyefem ? Try 'pyephem' From valent.turkovic at gmail.com Thu Jan 1 13:42:36 2009 From: valent.turkovic at gmail.com (Valent Turkovic) Date: Thu, 1 Jan 2009 14:42:36 +0100 Subject: [Fedora-livecd-list] Re: How to create live dvd? (livecd-creator fail) In-Reply-To: <64b14b300901010314j23360497x2d1aee33697f1324@mail.gmail.com> References: <64b14b300901010314j23360497x2d1aee33697f1324@mail.gmail.com> Message-ID: <64b14b300901010542u71a2879fneb857805eceacf77@mail.gmail.com> On Thu, Jan 1, 2009 at 12:14 PM, Valent Turkovic wrote: > Hi, first and foremost Happy New Year! I forgot to add these are my kickstart files I used: http://dl.getdropbox.com/u/184632/private-10-live-base.ks http://dl.getdropbox.com/u/184632/private-10-desktop-livecd.ks These work now but if you uncomment OpenOffice or some of KDE packages then it fails :( Command I used was: # cd /home # livecd-creator -c private-10-desktop-livecd.ks -f F10Private -t /home/temp/ and my /home partition has 15GB of free space. Cheers, Valent. -- http://kernelreloaded.blog385.com/ linux, blog, anime, spirituality, windsurf, wireless registered as user #367004 with the Linux Counter, http://counter.li.org. ICQ: 2125241, Skype: valent.turkovic From bruno at wolff.to Thu Jan 1 15:51:27 2009 From: bruno at wolff.to (Bruno Wolff III) Date: Thu, 1 Jan 2009 09:51:27 -0600 Subject: [Fedora-livecd-list] How to create live dvd? (livecd-creator fail) In-Reply-To: <64b14b300901010314j23360497x2d1aee33697f1324@mail.gmail.com> References: <64b14b300901010314j23360497x2d1aee33697f1324@mail.gmail.com> Message-ID: <20090101155127.GA21395@wolff.to> On Thu, Jan 01, 2009 at 12:14:53 +0100, Valent Turkovic wrote: > > I used to be able to create live DVD with Fedora 8 and 9 using > livecd-creator tool but now I can't do it anymore with Fedora 10. > > I get an error that there isn't enough space to create image and > livecd-creator fails. > > I used to do it without problem, so maybe the packages have grown or I > added more packages than there is space for them. I see that > /dev/loop0 is created and the size of that virtual partition is only > 3GB: > /dev/loop0 3.0G 602M 2.4G 21% > /home/temp/imgcreate-KWfqq9/install_root > > I guess that when space runs out in that partition livecd-creator > fails. Am I right? There are two space limits that I am aware of. One is the uncompressed file system that the build is done in and the other is the limit to the size of the compressed file system on the media. The first limit is controlled by the part command. The recommended size for DVDs is 8192, but that can end up being your limit if you are getting reasonable compression. The second limit is 4GiB and is due to a restriction of file sizes of the iso9660 format. You can get around this using udf instead. I am working on patches to livecd-creator to switch to udf when this limit is reached. They probably won't in Fedora before the alpha. But if you do go over the 4 GiB limit, you can look at bug 476696 for a patch that will unconditionally use udf. From bruno at wolff.to Thu Jan 1 16:01:42 2009 From: bruno at wolff.to (Bruno Wolff III) Date: Thu, 1 Jan 2009 10:01:42 -0600 Subject: [Fedora-livecd-list] fedora live and astronomy In-Reply-To: <213594.26161.qm@web51307.mail.re2.yahoo.com> References: <213594.26161.qm@web51307.mail.re2.yahoo.com> Message-ID: <20090101160142.GB21395@wolff.to> On Thu, Jan 01, 2009 at 01:26:31 -0800, brian hurren wrote: > I am wanting to make a fedora live disk specifically for Astronomy - to celebrate 2009 international year of astronomy. is it o.k to do this? can I add Kstars, Celestia, Pyfem, Stelarium ect. and is it ok for the Astronomical scocieties to give it away to members or ask for a donation to help the societies? > > ps. can anyone think of any other packages to add? > is it o.k to add a modified splash screen. (see attachment) Asking for money ins't a problem. You need to worry about providing source for people who are interested. You are going to need to be able to provide it on the spot for people that want it. You can't assume that you will be able to get it from Fedora for the next three years. You need to worry about trade marks. I am not sure where the guidelines on those are. Currently there is a way to replace the fedora packages with trademarks with generic stuff. There has also been talk of having a third option with remix trademarks, but I don't know where that is at right now. From valent.turkovic at gmail.com Thu Jan 1 16:28:58 2009 From: valent.turkovic at gmail.com (Valent Turkovic) Date: Thu, 1 Jan 2009 17:28:58 +0100 Subject: [Fedora-livecd-list] How to create live dvd? (livecd-creator fail) In-Reply-To: <20090101155127.GA21395@wolff.to> References: <64b14b300901010314j23360497x2d1aee33697f1324@mail.gmail.com> <20090101155127.GA21395@wolff.to> Message-ID: <64b14b300901010828i70b858a2jaea69dc3816c2b@mail.gmail.com> On Thu, Jan 1, 2009 at 4:51 PM, Bruno Wolff III wrote: > On Thu, Jan 01, 2009 at 12:14:53 +0100, > Valent Turkovic wrote: >> >> I used to be able to create live DVD with Fedora 8 and 9 using >> livecd-creator tool but now I can't do it anymore with Fedora 10. >> >> I get an error that there isn't enough space to create image and >> livecd-creator fails. >> >> I used to do it without problem, so maybe the packages have grown or I >> added more packages than there is space for them. I see that >> /dev/loop0 is created and the size of that virtual partition is only >> 3GB: >> /dev/loop0 3.0G 602M 2.4G 21% >> /home/temp/imgcreate-KWfqq9/install_root >> >> I guess that when space runs out in that partition livecd-creator >> fails. Am I right? > > There are two space limits that I am aware of. One is the uncompressed > file system that the build is done in and the other is the limit to > the size of the compressed file system on the media. > > The first limit is controlled by the part command. The recommended size > for DVDs is 8192, but that can end up being your limit if you are getting > reasonable compression. > > The second limit is 4GiB and is due to a restriction of file sizes of the > iso9660 format. You can get around this using udf instead. I am working > on patches to livecd-creator to switch to udf when this limit is reached. > They probably won't in Fedora before the alpha. But if you do go over > the 4 GiB limit, you can look at bug 476696 for a patch that will > unconditionally use udf. > But why is /dev/loop0 then only 3GB of size and not 4GB? -- http://kernelreloaded.blog385.com/ linux, blog, anime, spirituality, windsurf, wireless registered as user #367004 with the Linux Counter, http://counter.li.org. ICQ: 2125241, Skype: valent.turkovic From bruno at wolff.to Thu Jan 1 17:10:17 2009 From: bruno at wolff.to (Bruno Wolff III) Date: Thu, 1 Jan 2009 11:10:17 -0600 Subject: [Fedora-livecd-list] How to create live dvd? (livecd-creator fail) In-Reply-To: <64b14b300901010828i70b858a2jaea69dc3816c2b@mail.gmail.com> References: <64b14b300901010314j23360497x2d1aee33697f1324@mail.gmail.com> <20090101155127.GA21395@wolff.to> <64b14b300901010828i70b858a2jaea69dc3816c2b@mail.gmail.com> Message-ID: <20090101171017.GA17338@wolff.to> On Thu, Jan 01, 2009 at 17:28:58 +0100, Valent Turkovic wrote: > > > But why is /dev/loop0 then only 3GB of size and not 4GB? I am not sure. You might check what part command is being used. Different spins have different values for it embedded in their kickstart files. From valent.turkovic at gmail.com Thu Jan 1 17:59:23 2009 From: valent.turkovic at gmail.com (Valent Turkovic) Date: Thu, 1 Jan 2009 18:59:23 +0100 Subject: [Fedora-livecd-list] How to create live dvd? (livecd-creator fail) In-Reply-To: <20090101171017.GA17338@wolff.to> References: <64b14b300901010314j23360497x2d1aee33697f1324@mail.gmail.com> <20090101155127.GA21395@wolff.to> <64b14b300901010828i70b858a2jaea69dc3816c2b@mail.gmail.com> <20090101171017.GA17338@wolff.to> Message-ID: <64b14b300901010959u104f309br7274e4234f0285cd@mail.gmail.com> On Thu, Jan 1, 2009 at 6:10 PM, Bruno Wolff III wrote: > On Thu, Jan 01, 2009 at 17:28:58 +0100, > Valent Turkovic wrote: >> >> >> But why is /dev/loop0 then only 3GB of size and not 4GB? > > I am not sure. You might check what part command is being used. Different > spins have different values for it embedded in their kickstart files. > Thanks that was it! :) part / --size 3072 I wasn't aware that kickstart file is where you made this - I thought that thas was something hardcodec in livecd-creator tool :) Thank you once more! Valent. -- http://kernelreloaded.blog385.com/ linux, blog, anime, spirituality, windsurf, wireless registered as user #367004 with the Linux Counter, http://counter.li.org. ICQ: 2125241, Skype: valent.turkovic From fastiter at yahoo.fr Fri Jan 2 22:26:10 2009 From: fastiter at yahoo.fr (El Kindi REZIG) Date: Fri, 2 Jan 2009 22:26:10 +0000 (GMT) Subject: [Fedora-livecd-list] ANACONDA fails Message-ID: <939477.25000.qm@web23106.mail.ird.yahoo.com> Hello everybody, I'm making a Fedora spin, I made the live ISO, it boots fine, but when trying to install it Anaconda fails in the disk formatting stage (it's unable to mount /mnt/sysimage I guess?), here is the error message: An error occurred trying to format sda. This problem is serious and the install cannot continue. By the way, I'm using initng and not sysvinit, when I try to boot from sysvinit the installation works fine, but when trying initng it fails. Cheers -------------- next part -------------- An HTML attachment was scrubbed... URL: From kam at kamsalisbury.com Sat Jan 3 14:05:18 2009 From: kam at kamsalisbury.com (Kam Salisbury) Date: Sat, 3 Jan 2009 09:05:18 -0500 Subject: [Fedora-livecd-list] livecd-creator kickstart files In-Reply-To: <64b14b300901010318k531c881r3c41cab355bfaef0@mail.gmail.com> References: <818ac3c70812301832l3f4f8ab8i1b52c332f37960bb@mail.gmail.com> <20081231025142.GA6391@wolff.to> <495B05E8.2020004@fedoraproject.org> <64b14b300901010318k531c881r3c41cab355bfaef0@mail.gmail.com> Message-ID: <818ac3c70901030605l3e29135bie1359e135febe0d8@mail.gmail.com> On Thu, Jan 1, 2009 at 6:18 AM, Valent Turkovic wrote: > On Wed, Dec 31, 2008 at 6:40 AM, Rahul Sundaram > wrote: > > 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. > > Yes, please share your kickstart files! > > -- > http://kernelreloaded.blog385.com/ > linux, blog, anime, spirituality, windsurf, wireless > registered as user #367004 with the Linux Counter, http://counter.li.org. > ICQ: 2125241, Skype: valent.turkovic > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list > I have uploaded mine to http://alchemy.kamsalisbury.com/fedora/fedora-livecd-desktop.ks.20090103 and also linked to this file from http://fedoraproject.org/wiki/User:Kam -- Kam Salisbury http://kamsalisbury.com GPG key: FAF1751E -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike.cloaked at gmail.com Sun Jan 4 17:25:48 2009 From: mike.cloaked at gmail.com (Mike Cloaked) Date: Sun, 4 Jan 2009 09:25:48 -0800 (PST) Subject: [Fedora-livecd-list] How to create live dvd? (livecd-creator fail) Message-ID: <21241469.post@talk.nabble.com> Valent Turkovic wrote: > > > These work now but if you uncomment OpenOffice or some of KDE packages > then it fails :( > > Chances are that it needs a "lot" of /tmp disk space - maybe even up to 10GiB ? Sorry - this post was delayed so probably is irrelevant now! -- View this message in context: http://www.nabble.com/How-to-create-live-dvd--%28livecd-creator-fail%29-tp21240478p21241469.html Sent from the Fedora Livecd List mailing list archive at Nabble.com. From ftaylor at redhat.com Thu Jan 8 21:18:51 2009 From: ftaylor at redhat.com (Forrest Taylor) Date: Thu, 08 Jan 2009 16:18:51 -0500 Subject: [Fedora-livecd-list] Building CentOS5 Live CD on F10 Message-ID: <1231449531.14523.6.camel@papa> I am trying to build a CentOS 5.1 Live image on Fedora 10. It builds the image, but when I try to run it, it fails to boot with: mount: could not find filesystem '/dev/root' I was able to successfully build CentOS5.1 on another CentOS 5 machine using the repo provided by nanotechnologies.qc.ca. However, it uses the older livecd-tools-013. I rebuilt livecd-tools-020 on CentOS5, but I get the same error that I had on F10. Does anyone know what changed in the newer livecd-tools that no longer supports CentOS5? Thanks, -- Forrest Taylor Global Learning Services Project Manager III Cell: 303-913-5169 AIM: forresttaylorred Red Hat IRC: forrest -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From katzj at fedoraproject.org Thu Jan 8 21:53:36 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Thu, 8 Jan 2009 21:53:36 +0000 (UTC) Subject: [Fedora-livecd-list] 2 commits - imgcreate/live.py Message-ID: <20090108215336.8B6771204DD@lists.fedorahosted.org> imgcreate/live.py | 30 +++++++++++++++++++++++++----- 1 file changed, 25 insertions(+), 5 deletions(-) New commits: commit 73ff0151b331e60d011e7038c0485694e1d79dbb Author: Jeremy Katz Date: Thu Jan 8 16:50:43 2009 -0500 Be explicit with isofstype being iso9660 vs udf diff --git a/imgcreate/live.py b/imgcreate/live.py index 584bf72..f7e35db 100644 --- a/imgcreate/live.py +++ b/imgcreate/live.py @@ -70,6 +70,8 @@ class LiveImageCreatorBase(LoopImageCreator): self.__modules = ["=ata", "sym53c8xx", "aic7xxx", "=usb", "=firewire", "=mmc", "=pcmcia", "mptsas", "udf"] self.__modules.extend(kickstart.get_modules(self.ks)) + self.__isofstype = "iso9660" + # # Hooks for subclasses # @@ -248,6 +250,7 @@ class LiveImageCreatorBase(LoopImageCreator): {'file': os.path.join(path, name), 'size': os.stat(os.path.join(path, name)).st_size, 'fourgib': 4*1024*1024*1024}) + self.__isofstype = "udf" break args.append(isodir) @@ -404,13 +407,13 @@ menu hiddenrow 5 template = """label %(short)s menu label %(long)s kernel vmlinuz%(index)s - append initrd=initrd%(index)s.img root=CDLABEL=%(fslabel)s rootfstype=udf,iso9660 %(liveargs)s %(extra)s + append initrd=initrd%(index)s.img root=CDLABEL=%(fslabel)s rootfstype=%(isofstype) %(liveargs)s %(extra)s """ else: template = """label %(short)s menu label %(long)s kernel mboot.c32 - append xen%(index)s.gz --- vmlinuz%(index)s root=CDLABEL=%(fslabel)s rootfstype=udf,iso9660 %(liveargs)s %(extra)s --- initrd%(index)s.img + append xen%(index)s.gz --- vmlinuz%(index)s root=CDLABEL=%(fslabel)s rootfstype=%(isofstype) %(liveargs)s %(extra)s --- initrd%(index)s.img """ return template % args @@ -442,6 +445,7 @@ menu hiddenrow 5 cfg += self.__get_image_stanza(is_xen, fslabel = self.fslabel, + isofstype = self.__isofstype, liveargs = kernel_options, long = long, short = "linux" + index, @@ -454,6 +458,7 @@ menu hiddenrow 5 if checkisomd5: cfg += self.__get_image_stanza(is_xen, fslabel = self.fslabel, + isofstype = self.__isofstype, liveargs = kernel_options, long = "Verify and " + long, short = "check" + index, @@ -530,7 +535,7 @@ hiddenmenu def __get_efi_image_stanza(self, **args): return """title %(long)s - kernel /EFI/boot/vmlinuz%(index)s root=CDLABEL=%(fslabel)s rootfstype=udf,iso9660 %(liveargs)s %(extra)s + kernel /EFI/boot/vmlinuz%(index)s root=CDLABEL=%(fslabel)s rootfstype=%(isofstype) %(liveargs)s %(extra)s initrd /EFI/boot/initrd%(index)s.img """ %args @@ -547,11 +552,13 @@ hiddenmenu if os.path.exists("%s/EFI/boot/xen%d.gz" %(isodir, index)): continue cfg += self.__get_efi_image_stanza(fslabel = self.fslabel, + isofstype = self.__isofstype, liveargs = kernel_options, long = name, extra = "", index = index) if checkisomd5: cfg += self.__get_efi_image_stanza(fslabel = self.fslabel, + isofstype = self.__isofstype, liveargs = kernel_options, long = "Verify and Boot " + name, extra = "check", @@ -670,6 +677,7 @@ image=/ppc/ppc%(bit)s/vmlinuz kernel_options = self._get_kernel_options() cfg += self.__get_image_stanza(fslabel = self.fslabel, + isofstype = self.__isofstype, short = "linux", long = "Run from image", extra = "", @@ -678,6 +686,7 @@ image=/ppc/ppc%(bit)s/vmlinuz if self._has_checkisomd5(): cfg += self.__get_image_stanza(fslabel = self.fslabel, + isofstype = self.__isofstype, short = "check", long = "Verify and run from image", extra = "check", commit e4c497601f021d877e6ef0e68da99f331aed4899 Author: Bruno Wolff III Date: Thu Jan 8 16:47:10 2009 -0500 Support using UDF for large ISO spins (#476696) For ISO spins of larger than four gigabytes, we should use UDF instead of ISO9660 diff --git a/imgcreate/live.py b/imgcreate/live.py index 347d22c..584bf72 100644 --- a/imgcreate/live.py +++ b/imgcreate/live.py @@ -67,7 +67,7 @@ class LiveImageCreatorBase(LoopImageCreator): self.__isodir = None - self.__modules = ["=ata", "sym53c8xx", "aic7xxx", "=usb", "=firewire", "=mmc", "=pcmcia", "mptsas"] + self.__modules = ["=ata", "sym53c8xx", "aic7xxx", "=usb", "=firewire", "=mmc", "=pcmcia", "mptsas", "udf"] self.__modules.extend(kickstart.get_modules(self.ks)) # @@ -239,6 +239,17 @@ class LiveImageCreatorBase(LoopImageCreator): args.extend(self._get_mkisofs_options(isodir)) + # Switch to udf if any file on the image will be 4 GiB or more + for path, dirs, files in os.walk(isodir): + for name in files: + if os.stat(os.path.join(path, name)).st_size >= 4*1024*1024*1024: + args.append("-allow-limited-size") + logging.warn('%(file)s has a size of %(size)d, which is greater than or equal to %(fourgib)d, requiring a switch from iso9660 to udf.' % + {'file': os.path.join(path, name), + 'size': os.stat(os.path.join(path, name)).st_size, + 'fourgib': 4*1024*1024*1024}) + break + args.append(isodir) if subprocess.call(args) != 0: @@ -393,13 +404,13 @@ menu hiddenrow 5 template = """label %(short)s menu label %(long)s kernel vmlinuz%(index)s - append initrd=initrd%(index)s.img root=CDLABEL=%(fslabel)s rootfstype=iso9660 %(liveargs)s %(extra)s + append initrd=initrd%(index)s.img root=CDLABEL=%(fslabel)s rootfstype=udf,iso9660 %(liveargs)s %(extra)s """ else: template = """label %(short)s menu label %(long)s kernel mboot.c32 - append xen%(index)s.gz --- vmlinuz%(index)s root=CDLABEL=%(fslabel)s rootfstype=iso9660 %(liveargs)s %(extra)s --- initrd%(index)s.img + append xen%(index)s.gz --- vmlinuz%(index)s root=CDLABEL=%(fslabel)s rootfstype=udf,iso9660 %(liveargs)s %(extra)s --- initrd%(index)s.img """ return template % args @@ -519,7 +530,7 @@ hiddenmenu def __get_efi_image_stanza(self, **args): return """title %(long)s - kernel /EFI/boot/vmlinuz%(index)s root=CDLABEL=%(fslabel)s rootfstype=iso9660 %(liveargs)s %(extra)s + kernel /EFI/boot/vmlinuz%(index)s root=CDLABEL=%(fslabel)s rootfstype=udf,iso9660 %(liveargs)s %(extra)s initrd /EFI/boot/initrd%(index)s.img """ %args @@ -648,7 +659,7 @@ image=/ppc/ppc%(bit)s/vmlinuz label=%(short)s initrd=/ppc/ppc%(bit)s/initrd.img read-only - append="root=CDLABEL=%(fslabel)s rootfstype=iso9660 %(liveargs)s %(extra)s" + append="root=CDLABEL=%(fslabel)s rootfstype=udf,iso9660 %(liveargs)s %(extra)s" """ % args From jvonau at shaw.ca Fri Jan 9 03:01:59 2009 From: jvonau at shaw.ca (Jerry Vonau) Date: Thu, 08 Jan 2009 21:01:59 -0600 Subject: [Fedora-livecd-list] Building CentOS5 Live CD on F10 In-Reply-To: <1231449531.14523.6.camel@papa> References: <1231449531.14523.6.camel@papa> Message-ID: <1231470119.23666.96.camel@f9.vonau.ca> On Thu, 2009-01-08 at 16:18 -0500, Forrest Taylor wrote: > I am trying to build a CentOS 5.1 Live image on Fedora 10. It builds > the image, but when I try to run it, it fails to boot with: > mount: could not find filesystem '/dev/root' > > I was able to successfully build CentOS5.1 on another CentOS 5 machine > using the repo provided by nanotechnologies.qc.ca. However, it uses the > older livecd-tools-013. I rebuilt livecd-tools-020 on CentOS5, but I > get the same error that I had on F10. > > Does anyone know what changed in the newer livecd-tools that no longer > supports CentOS5? Yea, mayflower, the thing that builds the initrd for the livecd, was moved from livecd-tools to mkinitrd after livecd-tools-013. Jerry From ftaylor at redhat.com Fri Jan 9 14:58:09 2009 From: ftaylor at redhat.com (Forrest Taylor) Date: Fri, 09 Jan 2009 09:58:09 -0500 Subject: [Fedora-livecd-list] Building CentOS5 Live CD on F10 In-Reply-To: <1231470119.23666.96.camel@f9.vonau.ca> References: <1231449531.14523.6.camel@papa> <1231470119.23666.96.camel@f9.vonau.ca> Message-ID: <1231513089.14523.19.camel@papa> On Thu, 2009-01-08 at 21:01 -0600, Jerry Vonau wrote: > On Thu, 2009-01-08 at 16:18 -0500, Forrest Taylor wrote: > > I am trying to build a CentOS 5.1 Live image on Fedora 10. It builds > > the image, but when I try to run it, it fails to boot with: > > mount: could not find filesystem '/dev/root' > > > > I was able to successfully build CentOS5.1 on another CentOS 5 machine > > using the repo provided by nanotechnologies.qc.ca. However, it uses the > > older livecd-tools-013. I rebuilt livecd-tools-020 on CentOS5, but I > > get the same error that I had on F10. > > > > Does anyone know what changed in the newer livecd-tools that no longer > > supports CentOS5? > > Yea, mayflower, the thing that builds the initrd for the livecd, was > moved from livecd-tools to mkinitrd after livecd-tools-013. That explains why the newer livecd-tools didn't work. However, why didn't it work in F10? I.e., why can't I create a CentOS5 Live CD in Fedora 10? Thanks, -- Forrest Taylor Global Learning Services Project Manager III Cell: 303-913-5169 AIM: forresttaylorred Red Hat IRC: forrest -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From bjs at redhat.com Fri Jan 9 15:23:58 2009 From: bjs at redhat.com (Bryan J Smith) Date: Fri, 09 Jan 2009 10:23:58 -0500 Subject: [Fedora-livecd-list] Building CentOS5 Live CD on F10 In-Reply-To: <1231513089.14523.19.camel@papa> References: <1231449531.14523.6.camel@papa> <1231470119.23666.96.camel@f9.vonau.ca> <1231513089.14523.19.camel@papa> Message-ID: <1231514638.4005.15.camel@localhost.localdomain> On Fri, 2009-01-09 at 09:58 -0500, Forrest Taylor wrote: > That explains why the newer livecd-tools didn't work. However, why > didn't it work in F10? I.e., why can't I create a CentOS5 Live CD in > Fedora 10? Anaconda, PyKickstart and mkinitrd are all inter-twined. Anything after 013 fails for RHEL 5 without modification such as a newer Anaconda, PyKickstart and/or mkinitrd. I know there was some work with 015 and CentOS 5 which uses newer components. To get RHEL 5 to work for a thin client project, I "stole" the updateDiskless (mkinitrd replacement) and disklessrc (initrd init replacement) from old system-config-netboot and made some minor modifications. There are some current drivers inside of Red Hat to modify RHEL 5 mkinitrd, which Warren is working on. http://bjs-redhat.livejournal.com/681.html http://wtogami.livejournal.com/28896.html -- 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 jvonau at shaw.ca Fri Jan 9 15:47:22 2009 From: jvonau at shaw.ca (Jerry Vonau) Date: Fri, 09 Jan 2009 09:47:22 -0600 Subject: [Fedora-livecd-list] Building CentOS5 Live CD on F10 In-Reply-To: <1231513089.14523.19.camel@papa> References: <1231449531.14523.6.camel@papa> <1231470119.23666.96.camel@f9.vonau.ca> <1231513089.14523.19.camel@papa> Message-ID: <1231516042.23666.109.camel@f9.vonau.ca> On Fri, 2009-01-09 at 09:58 -0500, Forrest Taylor wrote: > On Thu, 2009-01-08 at 21:01 -0600, Jerry Vonau wrote: > > On Thu, 2009-01-08 at 16:18 -0500, Forrest Taylor wrote: > > > I am trying to build a CentOS 5.1 Live image on Fedora 10. It builds > > > the image, but when I try to run it, it fails to boot with: > > > mount: could not find filesystem '/dev/root' > > > > > > I was able to successfully build CentOS5.1 on another CentOS 5 machine > > > using the repo provided by nanotechnologies.qc.ca. However, it uses the > > > older livecd-tools-013. I rebuilt livecd-tools-020 on CentOS5, but I > > > get the same error that I had on F10. > > > > > > Does anyone know what changed in the newer livecd-tools that no longer > > > supports CentOS5? > > > > Yea, mayflower, the thing that builds the initrd for the livecd, was > > moved from livecd-tools to mkinitrd after livecd-tools-013. > > That explains why the newer livecd-tools didn't work. However, why > didn't it work in F10? I.e., why can't I create a CentOS5 Live CD in > Fedora 10? If I'm wrong someone should correct me, the livecd build process is using the mkinitrd from CentOS, mkinitrd is being run in a chroot environment, in the target image. Jerry From bjs at redhat.com Fri Jan 9 15:54:16 2009 From: bjs at redhat.com (Bryan J Smith) Date: Fri, 09 Jan 2009 10:54:16 -0500 Subject: [Fedora-livecd-list] Building CentOS5 Live CD on F10 In-Reply-To: <1231516042.23666.109.camel@f9.vonau.ca> References: <1231449531.14523.6.camel@papa> <1231470119.23666.96.camel@f9.vonau.ca> <1231513089.14523.19.camel@papa> <1231516042.23666.109.camel@f9.vonau.ca> Message-ID: <1231516456.4005.22.camel@localhost.localdomain> On Fri, 2009-01-09 at 09:47 -0600, Jerry Vonau wrote: > If I'm wrong someone should correct me, the livecd build process is > using the mkinitrd from CentOS, mkinitrd is being run in a chroot > environment, in the target image. Yes, but RHEL/CentOS 5 doesn't have various "--with-avail=" options, among other things, in its mkinitrd. Many of these are assumed to be in the Anaconda, PyKickstart and mkinitrd trinity by the newer livecd-tools. I our case, ran into this in the case of networking**. I know there are similar lack of features in RHEL/CentOS 5 mkinitrd for CD boot as well. I spend about 10 hours both weeks before and then during the LTSP Hackfest last year comparing what RHEL 5 and Fedora 9+ have in their Anaconda, PyKickstart and mkinitrd facilities. RHEL/CentOS 5 is based on much earlier Fedora releases and related components. -- Bryan **E.g., Warren Togami has more on our issue from his blog ... "Fedora's mkinitrd can use --with-avail==networking, but this is not possible on RHEL5 because there is no modules.networking group. We will likely implement something that looks at PCIID's within kernel modules and automatically pulls in matching kernel modules." -- 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 keith at onecoursesource.com Sat Jan 10 00:19:11 2009 From: keith at onecoursesource.com (Keith Wright) Date: Fri, 09 Jan 2009 16:19:11 -0800 Subject: [Fedora-livecd-list] Conference Talk on livecd-tools Message-ID: <4967E97F.4020604@onecoursesource.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Over the last year, I have built a couple of distributions for our company using livecd-tools with both Fedora 9 and 10. Now, the company I work for will be hosting the first annual Open Source Conference, and has asked me to give a presentation about "Building a Custom Distribution." The focus of my presentation will be livecd-tools. While I feel confident about what I want to discuss, it would be great to have experts on livecd-tools present. One Course Source's Open Source Conference is scheduled for January 28-29, 2009 in San Diego, California. Our conference will take place in the San Diego Ramada Inn and Conference Center. Registration begins on September 20, 2008. I want to mention a 75% off coupon code that expires on Friday, January 16th. This means that to attend the conference will cost less than $100 who use this code. This include food and drink! The coupon code is _*code99a*_. You can register at http://www.onecoursesource.com/ocs-osc.php. Even if you don't attend, you can still win prizes with our pass-it-on contest: http://www.onecoursesource.com/pass-it-on.php. Keith Wright, RHCE -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkln6X4ACgkQFJ8UAQeffyuIrACfU4v+KQao1b1jQj2st1e9ZnpK jX8AnRpmZq/8XGkyEQBL89oj8X5QDmcC =dAUK -----END PGP SIGNATURE----- From kam at kamsalisbury.com Sun Jan 11 13:31:56 2009 From: kam at kamsalisbury.com (Kam Salisbury) Date: Sun, 11 Jan 2009 08:31:56 -0500 Subject: [Fedora-livecd-list] Determin Overlay Free Space Message-ID: <818ac3c70901110531s3dd41949u1dd8d123f9d6440b@mail.gmail.com> I want to determin how much free space (or used space) the Fedora 10 Live USB install I built has. I actually run Fedora from my 16GB USB, exclusively - it never gets installed. Dropping to a shell, "df -h" give me... Filesystem Size Used Avail Use% Mounted on /dev/mapper/live-rw 3.0G 2.3G 650M 79% / tmpfs 1013M 76K 1013M 1% /dev/shm /dev/sdb1 7.5G 6.9G 584M 93% /mnt/live varcacheyum 1013M 0 1013M 0% /var/cache/yum /tmp 1013M 104K 1013M 1% /tmp vartmp 1013M 0 1013M 0% /var/tmp Since I created a 2GB overlay and the install is brand new, the output does not make sense. Well, maybe if the Fedora image is taking up some of the 2GB it makes sense. Is there a tool to see % overlay used? Health of the overlay itself? My web searches have only found ways to create the overlay via the livecd tools interface or shell command line. -- Kam Salisbury http://kamsalisbury.com GPG key: FAF1751E -------------- next part -------------- An HTML attachment was scrubbed... URL: From katzj at fedoraproject.org Mon Jan 12 16:38:41 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Mon, 12 Jan 2009 16:38:41 +0000 (UTC) Subject: [Fedora-livecd-list] imgcreate/live.py Message-ID: <20090112163841.66597120515@lists.fedorahosted.org> imgcreate/live.py | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) New commits: commit 4a670c764a1a949c866539b8a6a60e2729747acb Author: Jeremy Katz Date: Mon Jan 12 11:38:29 2009 -0500 Fix namespacing (#479550) diff --git a/imgcreate/live.py b/imgcreate/live.py index f7e35db..031b136 100644 --- a/imgcreate/live.py +++ b/imgcreate/live.py @@ -70,7 +70,7 @@ class LiveImageCreatorBase(LoopImageCreator): self.__modules = ["=ata", "sym53c8xx", "aic7xxx", "=usb", "=firewire", "=mmc", "=pcmcia", "mptsas", "udf"] self.__modules.extend(kickstart.get_modules(self.ks)) - self.__isofstype = "iso9660" + self._isofstype = "iso9660" # # Hooks for subclasses @@ -250,7 +250,7 @@ class LiveImageCreatorBase(LoopImageCreator): {'file': os.path.join(path, name), 'size': os.stat(os.path.join(path, name)).st_size, 'fourgib': 4*1024*1024*1024}) - self.__isofstype = "udf" + self._isofstype = "udf" break args.append(isodir) @@ -445,7 +445,7 @@ menu hiddenrow 5 cfg += self.__get_image_stanza(is_xen, fslabel = self.fslabel, - isofstype = self.__isofstype, + isofstype = self._isofstype, liveargs = kernel_options, long = long, short = "linux" + index, @@ -458,7 +458,7 @@ menu hiddenrow 5 if checkisomd5: cfg += self.__get_image_stanza(is_xen, fslabel = self.fslabel, - isofstype = self.__isofstype, + isofstype = self._isofstype, liveargs = kernel_options, long = "Verify and " + long, short = "check" + index, @@ -552,13 +552,13 @@ hiddenmenu if os.path.exists("%s/EFI/boot/xen%d.gz" %(isodir, index)): continue cfg += self.__get_efi_image_stanza(fslabel = self.fslabel, - isofstype = self.__isofstype, + isofstype = self._isofstype, liveargs = kernel_options, long = name, extra = "", index = index) if checkisomd5: cfg += self.__get_efi_image_stanza(fslabel = self.fslabel, - isofstype = self.__isofstype, + isofstype = self._isofstype, liveargs = kernel_options, long = "Verify and Boot " + name, extra = "check", @@ -677,7 +677,7 @@ image=/ppc/ppc%(bit)s/vmlinuz kernel_options = self._get_kernel_options() cfg += self.__get_image_stanza(fslabel = self.fslabel, - isofstype = self.__isofstype, + isofstype = self._isofstype, short = "linux", long = "Run from image", extra = "", @@ -686,7 +686,7 @@ image=/ppc/ppc%(bit)s/vmlinuz if self._has_checkisomd5(): cfg += self.__get_image_stanza(fslabel = self.fslabel, - isofstype = self.__isofstype, + isofstype = self._isofstype, short = "check", long = "Verify and run from image", extra = "check", From katzj at fedoraproject.org Mon Jan 12 16:43:59 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Mon, 12 Jan 2009 16:43:59 +0000 (UTC) Subject: [Fedora-livecd-list] imgcreate/live.py Message-ID: <20090112164359.8DFFC120515@lists.fedorahosted.org> imgcreate/live.py | 21 +++++++++------------ 1 file changed, 9 insertions(+), 12 deletions(-) New commits: commit df0d66f685bb06e9038e8ab76f549913b5b1143c Author: Jeremy Katz Date: Mon Jan 12 11:41:27 2009 -0500 And determine that we need to go to UDF earlier (#479550) diff --git a/imgcreate/live.py b/imgcreate/live.py index 031b136..a7032b0 100644 --- a/imgcreate/live.py +++ b/imgcreate/live.py @@ -240,18 +240,8 @@ class LiveImageCreatorBase(LoopImageCreator): "-o", iso] args.extend(self._get_mkisofs_options(isodir)) - - # Switch to udf if any file on the image will be 4 GiB or more - for path, dirs, files in os.walk(isodir): - for name in files: - if os.stat(os.path.join(path, name)).st_size >= 4*1024*1024*1024: - args.append("-allow-limited-size") - logging.warn('%(file)s has a size of %(size)d, which is greater than or equal to %(fourgib)d, requiring a switch from iso9660 to udf.' % - {'file': os.path.join(path, name), - 'size': os.stat(os.path.join(path, name)).st_size, - 'fourgib': 4*1024*1024*1024}) - self._isofstype = "udf" - break + if self._isofstype == "udf": + args.append("-allow-limited-size") args.append(isodir) @@ -283,6 +273,9 @@ class LiveImageCreatorBase(LoopImageCreator): if self.skip_compression: shutil.move(self._image, self.__isodir + "/LiveOS/ext3fs.img") + if os.stat(self.__isodir + "/LiveOS/ext3fs.img").st_size >= 4*1024*1024*1024: + self._isofstype = "udf" + logging.warn("Switching to UDF due to size of LiveOS/ext3fs.img") else: makedirs(os.path.join(os.path.dirname(self._image), "LiveOS")) shutil.move(self._image, @@ -290,6 +283,10 @@ class LiveImageCreatorBase(LoopImageCreator): "LiveOS", "ext3fs.img")) mksquashfs(os.path.dirname(self._image), self.__isodir + "/LiveOS/squashfs.img") + if os.stat(self.__isodir + "/LiveOS/squashfs.img").st_size >= 4*1024*1024*1024: + self._isofstype = "udf" + logging.warn("Switching to UDF due to size of LiveOS/squashfs.img") + self.__create_iso(self.__isodir) finally: From carlos at gutierrez.com Mon Jan 12 18:58:43 2009 From: carlos at gutierrez.com (Carlos M. Gutierrez) Date: Mon, 12 Jan 2009 14:58:43 -0400 (AST) 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, 10 Dec 2008, 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" In my Fedora 10 system I already have the usual yum caches at: /var/cache/yum/fedora/ /var/cache/yum/updates/ Is there a command-line switch to specify to livecd-creator to use those caches? If possible, it could save quite some bandwidth... I rsync'd the packages in /var/cache/yum/fedora/packages/ to a temporary directory in /var/tmp/livecd and then ran livecd-creator with --cache=/var/tmp/livecd but it proceeded to download all the packages needed for the CD anyway. Ideally, livecd-creator would be able to use those packages that I already have in the system... have I missed something obvious? Thanks... :-) Carlos M. Gutierrez carlos at gutierrez.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From katzj at redhat.com Mon Jan 12 19:42:58 2009 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 12 Jan 2009 14:42:58 -0500 Subject: [Fedora-livecd-list] livecd-tools: cache for yum ? In-Reply-To: References: <493FB5A7.4010007@kanarip.com> Message-ID: <3585F9EC-19AF-4DED-B3BB-F096B09954C3@redhat.com> On Jan 12, 2009, at 1:58 PM, Carlos M. Gutierrez wrote: > In my Fedora 10 system I already have the usual yum caches at: [snip] > > Is there a command-line switch to specify to livecd-creator to use > those caches? If possible, it could save quite some bandwidth... If you use --cache /var/cache/yum, it'll use them. But note that the "name" associated with repo lines in your ks.cfg will need to match the name of the repo for the regular system (ie, "fedora" and "updates" respectively) Jeremy From katzj at fedoraproject.org Mon Jan 12 20:19:25 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Mon, 12 Jan 2009 20:19:25 +0000 (UTC) Subject: [Fedora-livecd-list] 3 commits - imgcreate/yuminst.py tools/livecd-creator Message-ID: <20090112201925.E7BCC120515@lists.fedorahosted.org> imgcreate/yuminst.py | 1 + tools/livecd-creator | 4 ++-- 2 files changed, 3 insertions(+), 2 deletions(-) New commits: commit 9a6e8436eeb167981afef28a69afa2f49ca61d26 Author: Jan Kratochvil Date: Mon Jan 12 15:18:50 2009 -0500 Keep cache with --cache (#479716) Specifying --cache works if the image creation fails. It gets reused afterwards. But if we successfully create an image YUM itself deletes all the rpm files and next run of livecd-creator starts to download it all again. diff --git a/imgcreate/yuminst.py b/imgcreate/yuminst.py index 04c9b40..080034b 100644 --- a/imgcreate/yuminst.py +++ b/imgcreate/yuminst.py @@ -62,6 +62,7 @@ class LiveCDYum(yum.YumBase): conf += "plugins=0\n" conf += "reposdir=\n" conf += "failovermethod=priority\n" + conf += "keepcache=1\n" f = file(confpath, "w+") f.write(conf) commit d1e4c3eaf2500a72de33f0cc7d651ff43ba69ed4 Author: Jeremy Katz Date: Mon Jan 12 15:16:35 2009 -0500 Use absolute path for tmpdir (#479719) diff --git a/tools/livecd-creator b/tools/livecd-creator index 0390cc4..211f6ee 100755 --- a/tools/livecd-creator +++ b/tools/livecd-creator @@ -112,7 +112,7 @@ def main(): ks = imgcreate.read_kickstart(options.kscfg) creator = imgcreate.LiveImageCreator(ks, name, fs_label) - creator.tmpdir = options.tmpdir + creator.tmpdir = os.path.abspath(options.tmpdir) creator.skip_compression = options.skip_compression creator.skip_minimize = options.skip_minimize commit 1f0a0af690725290661086e5aebe73618f3117d6 Author: Jeremy Katz Date: Mon Jan 12 15:15:43 2009 -0500 Use absolute path to cachedir (#479716) diff --git a/tools/livecd-creator b/tools/livecd-creator index 719c874..0390cc4 100755 --- a/tools/livecd-creator +++ b/tools/livecd-creator @@ -117,7 +117,7 @@ def main(): creator.skip_minimize = options.skip_minimize try: - creator.mount(options.base_on, options.cachedir) + creator.mount(options.base_on, os.path.abspath(options.cachedir)) creator.install() creator.configure() if options.give_shell: From katzj at fedoraproject.org Mon Jan 12 20:27:38 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Mon, 12 Jan 2009 20:27:38 +0000 (UTC) Subject: [Fedora-livecd-list] imgcreate/live.py Message-ID: <20090112202738.54B94120515@lists.fedorahosted.org> imgcreate/live.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) New commits: commit 76d4cc51abf030b246b5d4c86264f1a66d5e68b7 Author: Jeremy Katz Date: Mon Jan 12 15:27:32 2009 -0500 Fix stpuid typo diff --git a/imgcreate/live.py b/imgcreate/live.py index a7032b0..d99659a 100644 --- a/imgcreate/live.py +++ b/imgcreate/live.py @@ -404,13 +404,13 @@ menu hiddenrow 5 template = """label %(short)s menu label %(long)s kernel vmlinuz%(index)s - append initrd=initrd%(index)s.img root=CDLABEL=%(fslabel)s rootfstype=%(isofstype) %(liveargs)s %(extra)s + append initrd=initrd%(index)s.img root=CDLABEL=%(fslabel)s rootfstype=%(isofstype)s %(liveargs)s %(extra)s """ else: template = """label %(short)s menu label %(long)s kernel mboot.c32 - append xen%(index)s.gz --- vmlinuz%(index)s root=CDLABEL=%(fslabel)s rootfstype=%(isofstype) %(liveargs)s %(extra)s --- initrd%(index)s.img + append xen%(index)s.gz --- vmlinuz%(index)s root=CDLABEL=%(fslabel)s rootfstype=%(isofstype)s %(liveargs)s %(extra)s --- initrd%(index)s.img """ return template % args @@ -532,7 +532,7 @@ hiddenmenu def __get_efi_image_stanza(self, **args): return """title %(long)s - kernel /EFI/boot/vmlinuz%(index)s root=CDLABEL=%(fslabel)s rootfstype=%(isofstype) %(liveargs)s %(extra)s + kernel /EFI/boot/vmlinuz%(index)s root=CDLABEL=%(fslabel)s rootfstype=%(isofstype)s %(liveargs)s %(extra)s initrd /EFI/boot/initrd%(index)s.img """ %args From carlos at gutierrez.com Tue Jan 13 04:54:15 2009 From: carlos at gutierrez.com (Carlos M. Gutierrez) Date: Tue, 13 Jan 2009 00:54:15 -0400 (AST) Subject: [Fedora-livecd-list] livecd-tools: cache for yum ? In-Reply-To: <3585F9EC-19AF-4DED-B3BB-F096B09954C3@redhat.com> References: <493FB5A7.4010007@kanarip.com> <3585F9EC-19AF-4DED-B3BB-F096B09954C3@redhat.com> Message-ID: On Mon, 12 Jan 2009, Jeremy Katz wrote: > If you use --cache /var/cache/yum, it'll use them. But note that the "name" > associated with repo lines in your ks.cfg will need to match the name of the > repo for the regular system (ie, "fedora" and "updates" respectively) I have no ks.cfg file in my system(s) which is not surprising since I have never used kickstart before... the closest I have is anaconda-ks.cfg in the /root directory and I do note that there is a Gnome applet to edit a kickstart file, but that one doesn't seem to have anywhere to specify repositories and their names. man kickstart didn't return anything. This is probably newbie territory, but could you or somebody point me to the kickstart documentation that covers the repositories to use and the syntax that goes into ks.cfg ... I did try running livecd-creator with --cache /var/yum/cache but the huge download started anyway... after some checking, it seems the new rpm's went into /var/cache/yum/released ... the "fedora" repository appears to be renamed somewhere to "released". Thanks... Carlos -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From sundaram at fedoraproject.org Tue Jan 13 08:55:26 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Tue, 13 Jan 2009 14:25:26 +0530 Subject: [Fedora-livecd-list] livecd-tools: cache for yum ? In-Reply-To: References: <493FB5A7.4010007@kanarip.com> <3585F9EC-19AF-4DED-B3BB-F096B09954C3@redhat.com> Message-ID: <496C56FE.3020107@fedoraproject.org> Carlos M. Gutierrez wrote: > > This is probably newbie territory, but could you or somebody point me to > the kickstart documentation that covers the repositories to use and the > syntax that goes into ks.cfg ... > > I did try running livecd-creator with --cache /var/yum/cache but the > huge download started anyway... after some checking, it seems the new > rpm's went into /var/cache/yum/released ... the "fedora" repository > appears to be renamed somewhere to "released". # yum install spin-kickstarts for getting a bunch of official kickstart files. Also refer https://fedoraproject.org/wiki/Anaconda/Kickstart The directory names in the cache folder are based on the repository id and they are not being renamed. Rahul From bruno at wolff.to Tue Jan 13 14:17:14 2009 From: bruno at wolff.to (Bruno Wolff III) Date: Tue, 13 Jan 2009 08:17:14 -0600 Subject: [Fedora-livecd-list] livecd-tools: cache for yum ? In-Reply-To: References: <493FB5A7.4010007@kanarip.com> <3585F9EC-19AF-4DED-B3BB-F096B09954C3@redhat.com> Message-ID: <20090113141714.GA30840@wolff.to> On Tue, Jan 13, 2009 at 00:54:15 -0400, "Carlos M. Gutierrez" wrote: > > This is probably newbie territory, but could you or somebody point me to > the kickstart documentation that covers the repositories to use and the > syntax that goes into ks.cfg ... If you install spin-kickstarts you'll get some samples. fedora-live-base.ks is one that has repo commands in it you can look at. (Many kickstarts include others so don't have repo commands in them.) From carlos at gutierrez.com Tue Jan 13 17:19:02 2009 From: carlos at gutierrez.com (Carlos M. Gutierrez) Date: Tue, 13 Jan 2009 13:19:02 -0400 (AST) Subject: [Fedora-livecd-list] livecd-tools: cache for yum ? [SUCCESS] In-Reply-To: <20090113141714.GA30840@wolff.to> References: <493FB5A7.4010007@kanarip.com> <3585F9EC-19AF-4DED-B3BB-F096B09954C3@redhat.com> <20090113141714.GA30840@wolff.to> Message-ID: On Tue, 13 Jan 2009, Bruno Wolff III wrote: > On Tue, Jan 13, 2009 at 00:54:15 -0400, > "Carlos M. Gutierrez" wrote: >> >> This is probably newbie territory, but could you or somebody point me to >> the kickstart documentation that covers the repositories to use and the >> syntax that goes into ks.cfg ... > > If you install spin-kickstarts you'll get some samples. fedora-live-base.ks > is one that has repo commands in it you can look at. (Many kickstarts > include others so don't have repo commands in them.) Thanks Rahul, Bruno, and Jeremy for your help... I finally achieved what I wanted which was to build a LiveCD ISO file using mostly the packages that I already had in my "fedora" and "updates" yum caches. What had me confused for a moment was that I could not find a ks.cfg file in my system but then I realized that what was meant was my *.ks file for the LiveCD... I was already using the spin-kickstarts package in my kickstart file: %include /usr/share/spin-kickstarts/fedora-livecd-desktop.ks lang en_US.UTF-8 keyboard us timezone America/Puerto_Rico To make the story short, I had to cheat a little to achieve my goal... I modified /usr/share/spin-kickstarts/fedora-live-base.ks and made the following change: repo --name=released ... to repo --name=fedora ... And then everything "just worked"... only a few new packages in "updates" were downloaded. Adding the fedora repo to my own kickstart file didn't work because the repo command doesn't substitute the repo --name=released line in the base kickstart file. In other words, you can add repos, not substitute or remove them. On reading the kickstart docs I note that there is a --cost= directive that would probably be useful to have more than one repo with the same packages... and I'll try that as I keep experimenting. Thanks! Carlos -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From keith at onecoursesource.com Tue Jan 13 18:28:42 2009 From: keith at onecoursesource.com (Keith Wright) Date: Tue, 13 Jan 2009 10:28:42 -0800 Subject: [Fedora-livecd-list] Kickstart documentation Message-ID: <496CDD5A.6020803@onecoursesource.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Here's the documentation of kickstart files that is current for RHEL 5.3: https://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.3/html/Installation_Guide/s1-kickstart2-file.html The Fedora project also has documentation available at: http://fedoraproject.org/wiki/Anaconda/Kickstart I would also normally refer you to installing anaconda, and then looking at /usr/share/doc/anaconda-11.4.1.63/kickstart-docs.txt. However, currently this file appears to be broken! Keith Wright, RHCE -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkls3VoACgkQFJ8UAQeffyuhjACeOKVpg5EWp9REuAnV9fSmSnUx 0tMAn00UP9gcrjg22zoLROZwYwVfOaL1 =DuWw -----END PGP SIGNATURE----- From kam at kamsalisbury.com Wed Jan 14 11:42:35 2009 From: kam at kamsalisbury.com (Kam Salisbury) Date: Wed, 14 Jan 2009 06:42:35 -0500 Subject: [Fedora-livecd-list] Overlay File Health? Message-ID: <818ac3c70901140342k77488edci6b1b6d4bcb466ac7@mail.gmail.com> How do I see how much space is used in the overlay file (Fedora USB)? [liveuser at localhost ~]$ df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/live-rw 3.0G 2.2G 771M 75% / tmpfs 1013M 288K 1013M 1% /dev/shm /dev/sdb1 15G 8.3G 6.8G 55% /mnt/live varcacheyum 1013M 0 1013M 0% /var/cache/yum /tmp 1013M 104K 1013M 1% /tmp vartmp 1013M 0 1013M 0% /var/tmp The above command output does not seem to reflect the 2GB overlay. Is there a way to output "just" the overlay contents? Something like 'du -hs' (du shows what /dev/mapper shows). -- Kam Salisbury http://kamsalisbury.com GPG key: FAF1751E -------------- next part -------------- An HTML attachment was scrubbed... URL: From katzj at fedoraproject.org Thu Jan 15 05:58:50 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Thu, 15 Jan 2009 05:58:50 +0000 (UTC) Subject: [Fedora-livecd-list] tools/livecd-iso-to-disk.sh Message-ID: <20090115055850.8C34B12052E@lists.fedorahosted.org> tools/livecd-iso-to-disk.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) New commits: commit 5813114b6f5e2497764593eb1b2f645d06d2fbb0 Author: Jeremy Katz Date: Thu Jan 15 00:57:44 2009 -0500 Fix for udev deprecated syntax (#480109) diff --git a/tools/livecd-iso-to-disk.sh b/tools/livecd-iso-to-disk.sh index 5371db1..fba2567 100755 --- a/tools/livecd-iso-to-disk.sh +++ b/tools/livecd-iso-to-disk.sh @@ -45,7 +45,7 @@ getdisk() { return fi - p=$(udevinfo -q path -n $DEV) + p=$(udevadm info -q path -n $DEV) if [ -e /sys/$p/device ]; then device=$(basename /sys/$p) else @@ -131,7 +131,7 @@ createGPTLayout() { size=$(echo $partinfo |cut -d : -f 2 |sed -e 's/B$//') /sbin/parted --script $device unit b mkpart '"EFI System Partition"' fat32 17408 $(($size - 17408)) set 1 boot on USBDEV=${device}1 - /sbin/udevsettle + /sbin/udevadm settle /sbin/mkdosfs -n LIVE $USBDEV USBLABEL="UUID=$(/lib/udev/vol_id -u $dev)" } From janina at rednote.net Fri Jan 16 02:17:12 2009 From: janina at rednote.net (Janina Sajka) Date: Thu, 15 Jan 2009 21:17:12 -0500 Subject: [Fedora-livecd-list] Can I do this safely? Message-ID: <20090116021712.GA7001@sonata.rednote.net> Now that I know Orca is working on Fedora's Live CD, I want to try an installation from the Live Desktop. But, I need to be absolutely certain I won't overwrite data on /dev/sdb1. Short of opening the box and removing the power or data connectors for that disc, can I rely on the installer to give me the option of where on my drives Fedora will be installed? Do I get a chance to say: "Put it at /dev/sda1?" Please pardon this rather basic question, but I have no experience of this installer and the data on /dev/sdb1 is very important to me. -- Janina Sajka, Phone: +1.202.595.7777; sip:janina at CapitalAccessibility.Com Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility janina at a11y.org Linux Foundation http://a11y.org From bruno at wolff.to Fri Jan 16 06:55:27 2009 From: bruno at wolff.to (Bruno Wolff III) Date: Fri, 16 Jan 2009 00:55:27 -0600 Subject: [Fedora-livecd-list] Can I do this safely? In-Reply-To: <20090116021712.GA7001@sonata.rednote.net> References: <20090116021712.GA7001@sonata.rednote.net> Message-ID: <20090116065527.GB21983@wolff.to> On Thu, Jan 15, 2009 at 21:17:12 -0500, Janina Sajka wrote: > Now that I know Orca is working on Fedora's Live CD, I want to try an > installation from the Live Desktop. But, I need to be absolutely certain > I won't overwrite data on /dev/sdb1. Short of opening the box and > removing the power or data connectors for that disc, can I rely on the > installer to give me the option of where on my drives Fedora will be > installed? Do I get a chance to say: "Put it at /dev/sda1?" You get a chance to layout partitions as you would when doing a normal install. It's still possible to make a mistake though, so you aren't totally protected. From katzj at fedoraproject.org Fri Jan 16 15:30:21 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Fri, 16 Jan 2009 15:30:21 +0000 (UTC) Subject: [Fedora-livecd-list] 2 commits - imgcreate/live.py tools/livecd-creator Message-ID: <20090116153021.80AEFC024D@lists.fedorahosted.org> imgcreate/live.py | 2 +- tools/livecd-creator | 4 +++- 2 files changed, 4 insertions(+), 2 deletions(-) New commits: commit ea5320abc1500552e17a95710e0fb989b001c41b Author: Jeremy Katz Date: Wed Jan 14 22:19:28 2009 -0500 Fix traceback when not specifying a cachedir diff --git a/tools/livecd-creator b/tools/livecd-creator index 211f6ee..1aab882 100755 --- a/tools/livecd-creator +++ b/tools/livecd-creator @@ -115,9 +115,11 @@ def main(): creator.tmpdir = os.path.abspath(options.tmpdir) creator.skip_compression = options.skip_compression creator.skip_minimize = options.skip_minimize + if options.cachedir: + options.cachedir = os.path.abspath(options.cachedir) try: - creator.mount(options.base_on, os.path.abspath(options.cachedir)) + creator.mount(options.base_on, options.cachedir) creator.install() creator.configure() if options.give_shell: commit 1435e38ad9dda0d5440e028a5f38fe2a3ccf8346 Author: Jeremy Katz Date: Tue Jan 13 09:23:43 2009 -0500 Use the explicit form for ppc (not sure how I missed it) - thanks to Bruno Wolf diff --git a/imgcreate/live.py b/imgcreate/live.py index d99659a..a6a9c46 100644 --- a/imgcreate/live.py +++ b/imgcreate/live.py @@ -663,7 +663,7 @@ image=/ppc/ppc%(bit)s/vmlinuz label=%(short)s initrd=/ppc/ppc%(bit)s/initrd.img read-only - append="root=CDLABEL=%(fslabel)s rootfstype=udf,iso9660 %(liveargs)s %(extra)s" + append="root=CDLABEL=%(fslabel)s rootfstype=%(isofstype)s %(liveargs)s %(extra)s" """ % args From katzj at redhat.com Fri Jan 16 21:09:08 2009 From: katzj at redhat.com (Jeremy Katz) Date: Fri, 16 Jan 2009 16:09:08 -0500 Subject: [Fedora-livecd-list] [PATCH] Using both EFI and MBR at once on Live USB images and other misc. fixes In-Reply-To: <49090E7A.7090009@diffingo.com> References: <48F7FC16.9090201@diffingo.com> <1224213914.370.85.camel@aglarond.local> <48F87E65.6040104@diffingo.com> <1224251419.13356.46.camel@aglarond.local> <48F8A696.8020601@diffingo.com> <4908E124.10603@diffingo.com> <1225327119.25818.2.camel@aglarond.local> <49090E7A.7090009@diffingo.com> Message-ID: <20090116210907.GC27731@redhat.com> On Wednesday, October 29 2008, Stewart Adam said: > On 10/29/08 8:38 PM, Jeremy Katz wrote: >> On Wed, 2008-10-29 at 18:18 -0400, Stewart Adam wrote: >>> Here's the patch that I spoke about in my last email: >>> http://downloads.diffingo.com/livecd-iso-to-disk.sh-efi.patch >> >> Cool. From a quick look, it looks okay. But given where we are in the >> Fedora 10 cycle, I'm going to hold off on applying it until after we get >> Fedora 10 out the door to avoid destabilizing things for people >> (especially as feature freeze was a month or so ago) > > No problem, that gives us some more time to work out the GPT+syslinux problems. Okay, as I come back to looking at this, the patch still looks okay and I've even given it a quick test now :-) Have you had any luck/progress on GPT+syslinux before I try to look at it some more? From maillist at diffingo.com Sat Jan 17 20:19:21 2009 From: maillist at diffingo.com (Stewart Adam) Date: Sat, 17 Jan 2009 15:19:21 -0500 Subject: [Fedora-livecd-list] [PATCH] Using both EFI and MBR at once on Live USB images and other misc. fixes In-Reply-To: <20090116210907.GC27731@redhat.com> References: <48F7FC16.9090201@diffingo.com> <1224213914.370.85.camel@aglarond.local> <48F87E65.6040104@diffingo.com> <1224251419.13356.46.camel@aglarond.local> <48F8A696.8020601@diffingo.com> <4908E124.10603@diffingo.com> <1225327119.25818.2.camel@aglarond.local> <49090E7A.7090009@diffingo.com> <20090116210907.GC27731@redhat.com> Message-ID: <49723D49.7050602@diffingo.com> On 1/16/09 4:09 PM, Jeremy Katz wrote: > On Wednesday, October 29 2008, Stewart Adam said: >> On 10/29/08 8:38 PM, Jeremy Katz wrote: >>> On Wed, 2008-10-29 at 18:18 -0400, Stewart Adam wrote: >>>> Here's the patch that I spoke about in my last email: >>>> http://downloads.diffingo.com/livecd-iso-to-disk.sh-efi.patch >>> Cool. From a quick look, it looks okay. But given where we are in the >>> Fedora 10 cycle, I'm going to hold off on applying it until after we get >>> Fedora 10 out the door to avoid destabilizing things for people >>> (especially as feature freeze was a month or so ago) >> No problem, that gives us some more time to work out the GPT+syslinux problems. > > Okay, as I come back to looking at this, the patch still looks okay and > I've even given it a quick test now :-) Have you had any luck/progress > on GPT+syslinux before I try to look at it some more? There's been some good progress - I sent a few messages to the syslinux mailing lists and hpa plans on fixing the GPT MBR in the near future, so we have that part of the problem covered. For now, I guess we can just comment out the "if" that chooses between mbr.bin or gptmbr.bin so that the USB key would be only EFI or only MBR compatible until this is resolved. The other half of the problem is that recent kernels hang when booting from EFI (bug 466954). Peter Jones was able to find out which commit broke EFI booting, but we're not sure how to fix it yet. Stewart From katzj at redhat.com Mon Jan 19 15:55:40 2009 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 19 Jan 2009 10:55:40 -0500 Subject: [Fedora-livecd-list] [PATCH] Using both EFI and MBR at once on Live USB images and other misc. fixes In-Reply-To: <49723D49.7050602@diffingo.com> References: <48F7FC16.9090201@diffingo.com> <1224213914.370.85.camel@aglarond.local> <48F87E65.6040104@diffingo.com> <1224251419.13356.46.camel@aglarond.local> <48F8A696.8020601@diffingo.com> <4908E124.10603@diffingo.com> <1225327119.25818.2.camel@aglarond.local> <49090E7A.7090009@diffingo.com> <20090116210907.GC27731@redhat.com> <49723D49.7050602@diffingo.com> Message-ID: <20090119155540.GD32152@redhat.com> On Saturday, January 17 2009, Stewart Adam said: > On 1/16/09 4:09 PM, Jeremy Katz wrote: >> On Wednesday, October 29 2008, Stewart Adam said: >>> On 10/29/08 8:38 PM, Jeremy Katz wrote: >>>> On Wed, 2008-10-29 at 18:18 -0400, Stewart Adam wrote: >>>>> Here's the patch that I spoke about in my last email: >>>>> http://downloads.diffingo.com/livecd-iso-to-disk.sh-efi.patch >>>> Cool. From a quick look, it looks okay. But given where we are in the >>>> Fedora 10 cycle, I'm going to hold off on applying it until after we get >>>> Fedora 10 out the door to avoid destabilizing things for people >>>> (especially as feature freeze was a month or so ago) >>> No problem, that gives us some more time to work out the GPT+syslinux problems. >> >> Okay, as I come back to looking at this, the patch still looks okay and >> I've even given it a quick test now :-) Have you had any luck/progress >> on GPT+syslinux before I try to look at it some more? > > There's been some good progress - I sent a few messages to the syslinux > mailing lists and hpa plans on fixing the GPT MBR in the near future, so > we have that part of the problem covered. For now, I guess we can just > comment out the "if" that chooses between mbr.bin or gptmbr.bin so that > the USB key would be only EFI or only MBR compatible until this is > resolved. Given that we didn't previously copy over an MBR for the mactel case, leaving the 'if' doesn't really seem to hurt anything. I get to EFI grub with the gptmbr.bin present and then when it's fixed, maybe things will magically just start to work. So based on that, I think I'm going to push what you had to git and then we can have it more easily testable > The other half of the problem is that recent kernels hang when booting > from EFI (bug 466954). Peter Jones was able to find out which commit > broke EFI booting, but we're not sure how to fix it yet. Yeah, I've been following Peter's sob story of debugging that. He's getting closer. I think. Jeremy From katzj at fedoraproject.org Mon Jan 19 16:16:14 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Mon, 19 Jan 2009 16:16:14 +0000 (UTC) Subject: [Fedora-livecd-list] 3 commits - imgcreate/live.py tools/livecd-iso-to-disk.sh Message-ID: <20090119161614.201A412015A@lists.fedorahosted.org> imgcreate/live.py | 12 +-- tools/livecd-iso-to-disk.sh | 169 +++++++++++++++++++++++++++++--------------- 2 files changed, 119 insertions(+), 62 deletions(-) New commits: commit 616642a5d56b8e453614f7a8845a61b033c9ac4f Author: Jeremy Katz Date: Mon Jan 19 11:14:10 2009 -0500 Use rootfstype='auto' instead of trying to discover iso9660 vs udf (#479846) diff --git a/imgcreate/live.py b/imgcreate/live.py index a6a9c46..c75cc92 100644 --- a/imgcreate/live.py +++ b/imgcreate/live.py @@ -442,7 +442,7 @@ menu hiddenrow 5 cfg += self.__get_image_stanza(is_xen, fslabel = self.fslabel, - isofstype = self._isofstype, + isofstype = "auto", liveargs = kernel_options, long = long, short = "linux" + index, @@ -455,7 +455,7 @@ menu hiddenrow 5 if checkisomd5: cfg += self.__get_image_stanza(is_xen, fslabel = self.fslabel, - isofstype = self._isofstype, + isofstype = "auto", liveargs = kernel_options, long = "Verify and " + long, short = "check" + index, @@ -549,13 +549,13 @@ hiddenmenu if os.path.exists("%s/EFI/boot/xen%d.gz" %(isodir, index)): continue cfg += self.__get_efi_image_stanza(fslabel = self.fslabel, - isofstype = self._isofstype, + isofstype = "auto", liveargs = kernel_options, long = name, extra = "", index = index) if checkisomd5: cfg += self.__get_efi_image_stanza(fslabel = self.fslabel, - isofstype = self._isofstype, + isofstype = "auto", liveargs = kernel_options, long = "Verify and Boot " + name, extra = "check", @@ -674,7 +674,7 @@ image=/ppc/ppc%(bit)s/vmlinuz kernel_options = self._get_kernel_options() cfg += self.__get_image_stanza(fslabel = self.fslabel, - isofstype = self._isofstype, + isofstype = "auto", short = "linux", long = "Run from image", extra = "", @@ -683,7 +683,7 @@ image=/ppc/ppc%(bit)s/vmlinuz if self._has_checkisomd5(): cfg += self.__get_image_stanza(fslabel = self.fslabel, - isofstype = self._isofstype, + isofstype = "auto", short = "check", long = "Verify and run from image", extra = "check", commit 08da762ce7893c79bb22772c843e492765ff15f4 Author: Jeremy Katz Date: Mon Jan 19 10:54:42 2009 -0500 Don't make an inability to find the hybrid gptmbr.bin fatal diff --git a/tools/livecd-iso-to-disk.sh b/tools/livecd-iso-to-disk.sh index 3777c21..d37a2e9 100755 --- a/tools/livecd-iso-to-disk.sh +++ b/tools/livecd-iso-to-disk.sh @@ -74,9 +74,6 @@ resetMBR() { cat /usr/lib/syslinux/gptmbr.bin > $device elif [ -f /usr/share/syslinux/gptmbr.bin ]; then cat /usr/share/syslinux/gptmbr.bin > $device - else - echo "Could not find gptmbr.bin (syslinux)" - exitclean fi else if [ -f /usr/lib/syslinux/mbr.bin ]; then commit f0ed14fce156fd97480e833440898cdc378e8f89 Author: Stweart Adam Date: Fri Jan 16 16:15:50 2009 -0500 Start to support creating/using hybrid GPT/MBR USB sticks What it changes: * Exit messages when syslinux's MBR files can't be found * Unmounts $USBDEV after creating GPT, as HAL attempts to automount * Allows for hybrid (GPT+MBR) USB keys * Adds --skipcopy to skip copying the live OS * Adds --format option to replace --mactel + --reset-mbr * --reset-mbr will now reset the MBR, GPT or not. * if --format is specified, a valid partition isn't required (only a valid device instead) Notes worth mentioning: * --format + --mactel = new GPT table, resets PMBR (GPT's Protective MBR) * --format = new MSDOS table, resets MBR * syslinux support isn't complete let, hopefully coming soon * GPT hybrid tables requires /usr/{lib,share}/syslinux/gptmbr.bin which is only in the newest syslinux (not available in the Fedora repos yet). diff --git a/tools/livecd-iso-to-disk.sh b/tools/livecd-iso-to-disk.sh index fba2567..3777c21 100755 --- a/tools/livecd-iso-to-disk.sh +++ b/tools/livecd-iso-to-disk.sh @@ -4,6 +4,7 @@ # Jeremy Katz # # overlay/persistence enhancements by Douglas McClendon +# GPT+MBR hybrid enhancements by Stewart Adam # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -22,7 +23,7 @@ export PATH=/sbin:/usr/sbin:$PATH usage() { - echo "$0 [--reset-mbr] [--noverify] [--overlay-size-mb ] [--home-size-mb ] [--unencrypted-home] " + echo "$0 [--format] [--reset-mbr] [--noverify] [--overlay-size-mb ] [--home-size-mb ] [--unencrypted-home] [--skipcopy] " exit 1 } @@ -67,12 +68,25 @@ resetMBR() { return fi getdisk $1 - if [ -f /usr/lib/syslinux/mbr.bin ]; then - cat /usr/lib/syslinux/mbr.bin > $device - elif [ -f /usr/share/syslinux/mbr.bin ]; then - cat /usr/share/syslinux/mbr.bin > $device + # if mactel, we need to use the hybrid MBR + if [ -n "$mactel" ];then + if [ -f /usr/lib/syslinux/gptmbr.bin ]; then + cat /usr/lib/syslinux/gptmbr.bin > $device + elif [ -f /usr/share/syslinux/gptmbr.bin ]; then + cat /usr/share/syslinux/gptmbr.bin > $device + else + echo "Could not find gptmbr.bin (syslinux)" + exitclean + fi else - exitclean + if [ -f /usr/lib/syslinux/mbr.bin ]; then + cat /usr/lib/syslinux/mbr.bin > $device + elif [ -f /usr/share/syslinux/mbr.bin ]; then + cat /usr/share/syslinux/mbr.bin > $device + else + echo "Could not find mbr.bin (syslinux)" + exitclean + fi fi } @@ -131,9 +145,35 @@ createGPTLayout() { size=$(echo $partinfo |cut -d : -f 2 |sed -e 's/B$//') /sbin/parted --script $device unit b mkpart '"EFI System Partition"' fat32 17408 $(($size - 17408)) set 1 boot on USBDEV=${device}1 + # Sometimes automount can be _really_ annoying. + echo "Waiting for devices to settle..." /sbin/udevadm settle + sleep 5 + umount $USBDEV &> /dev/null /sbin/mkdosfs -n LIVE $USBDEV - USBLABEL="UUID=$(/lib/udev/vol_id -u $dev)" + USBLABEL="UUID=$(/lib/udev/vol_id -u $USBDEV)" +} + +createMSDOSLayout() { + dev=$1 + getdisk $dev + + echo "WARNING: THIS WILL DESTROY ANY DATA ON $device!!!" + echo "Press Enter to continue or ctrl-c to abort" + read + + /sbin/parted --script $device mklabel msdos + partinfo=$(/sbin/parted --script -m $device "unit b print" |grep ^$device:) + size=$(echo $partinfo |cut -d : -f 2 |sed -e 's/B$//') + /sbin/parted --script $device unit b mkpart primary fat32 17408 $(($size - 17408)) set 1 boot on + USBDEV=${device}1 + # Sometimes automount can be _really_ annoying. + echo "Waiting for devices to settle..." + /sbin/udevadm settle + sleep 5 + umount $USBDEV &> /dev/null + /sbin/mkdosfs -n LIVE $USBDEV + USBLABEL="UUID=$(/lib/udev/vol_id -u $USBDEV)" } checkGPT() { @@ -142,7 +182,7 @@ checkGPT() { if [ "$(/sbin/fdisk -l $device 2>/dev/null |grep -c GPT)" -eq "0" ]; then echo "EFI boot requires a GPT partition table." - echo "This can be done manually or you can run with --reset-mbr" + echo "This can be done manually or you can run with --format" exitclean fi @@ -273,6 +313,12 @@ while [ $# -gt 2 ]; do --mactel) mactel=1 ;; + --format) + format=1 + ;; + --skipcopy) + skipcopy=1 + ;; --xo) xo=1 skipcompress=1 @@ -311,6 +357,7 @@ if [ ! -b "$ISO" -a ! -f "$ISO" ]; then usage fi +# FIXME: If --format is given, we shouldn't care and just use /dev/foo1 if [ -z "$USBDEV" -o ! -b "$USBDEV" ]; then usage fi @@ -327,17 +374,24 @@ if [ -z "$noverify" ]; then fi # do some basic sanity checks. -checkFilesystem $USBDEV checkMounted $USBDEV -if [ -z "$mactel" ]; then - checkSyslinuxVersion - checkPartActive $USBDEV - [ -n "$resetmbr" ] && resetMBR $USBDEV - checkMBR $USBDEV -elif [ -n "$mactel" ]; then - [ -n "$resetmbr" ] && createGPTLayout $USBDEV +if [ -n "$format" ];then + # checks for a valid filesystem + if [ -n "$mactel" ];then + createGPTLayout $USBDEV + else + createMSDOSLayout $USBDEV + fi +fi +checkFilesystem $USBDEV +if [ -n "$mactel" ]; then checkGPT $USBDEV fi +checkSyslinuxVersion +# Because we can't set boot flag for EFI Protective on msdos partition tables +[ -z "$mactel" ] && checkPartActive $USBDEV +[ -n "$resetmbr" ] && resetMBR $USBDEV +checkMBR $USBDEV if [ "$overlaysizemb" -gt 0 -a "$USBFS" = "vfat" ]; then @@ -406,49 +460,54 @@ if [ $(($overlaysizemb + $homesizemb + $livesize + $swapsizemb)) -gt $(($free + exitclean fi -if [ -d $USBMNT/LiveOS -a -z "$force" ]; then - echo "Already set up as live image." - if [ -z "$keephome" -a -e $USBMNT/LiveOS/$HOMEFILE ]; then - echo "WARNING: Persistent /home will be deleted!!!" - echo "Press Enter to continue or ctrl-c to abort" - read - else - echo "Deleting old OS in fifteen seconds..." - sleep 15 - - [ -e "$USBMNT/LiveOS/$HOMEFILE" -a -n "$keephome" ] && mv $USBMNT/LiveOS/$HOMEFILE $USBMNT/$HOMEFILE - fi - - rm -rf $USBMNT/LiveOS +if [ -z "$skipcopy" ];then + if [ -d $USBMNT/LiveOS -a -z "$force" ]; then + echo "Already set up as live image." + if [ -z "$keephome" -a -e $USBMNT/LiveOS/$HOMEFILE ]; then + echo "WARNING: Persistent /home will be deleted!!!" + echo "Press Enter to continue or ctrl-c to abort" + read + else + echo "Deleting old OS in fifteen seconds..." + sleep 15 + + [ -e "$USBMNT/LiveOS/$HOMEFILE" -a -n "$keephome" ] && mv $USBMNT/LiveOS/$HOMEFILE $USBMNT/$HOMEFILE + fi + + rm -rf $USBMNT/LiveOS + fi fi -echo "Copying live image to USB stick" -[ -z "$mactel" -a ! -d $USBMNT/$SYSLINUXPATH ] && mkdir -p $USBMNT/$SYSLINUXPATH +# Bootloader is always reconfigured, so keep these out of the if skipcopy stuff. +[ ! -d $USBMNT/$SYSLINUXPATH ] && mkdir -p $USBMNT/$SYSLINUXPATH [ -n "$mactel" -a ! -d $USBMNT/EFI/boot ] && mkdir -p $USBMNT/EFI/boot -[ ! -d $USBMNT/LiveOS ] && mkdir $USBMNT/LiveOS -[ -n "$keephome" -a -f "$USBMNT/$HOMEFILE" ] && mv $USBMNT/$HOMEFILE $USBMNT/LiveOS/$HOMEFILE -# cases without /LiveOS are legacy detection, remove for F10 -if [ -n "$skipcompress" -a -f $CDMNT/LiveOS/squashfs.img ]; then - mount -o loop $CDMNT/LiveOS/squashfs.img $CDMNT - cp $CDMNT/LiveOS/ext3fs.img $USBMNT/LiveOS/ext3fs.img || (umount $CDMNT ; exitclean) - umount $CDMNT -elif [ -f $CDMNT/LiveOS/squashfs.img ]; then - cp $CDMNT/LiveOS/squashfs.img $USBMNT/LiveOS/squashfs.img || exitclean -elif [ -f $CDMNT/squashfs.img ]; then - cp $CDMNT/squashfs.img $USBMNT/LiveOS/squashfs.img || exitclean -elif [ -f $CDMNT/LiveOS/ext3fs.img ]; then - cp $CDMNT/LiveOS/ext3fs.img $USBMNT/LiveOS/ext3fs.img || exitclean -elif [ -f $CDMNT/ext3fs.img ]; then - cp $CDMNT/ext3fs.img $USBMNT/LiveOS/ext3fs.img || exitclean -fi -if [ -f $CDMNT/LiveOS/osmin.img ]; then - cp $CDMNT/LiveOS/osmin.img $USBMNT/LiveOS/osmin.img || exitclean + +if [ -z "$skipcopy" ];then + echo "Copying live image to USB stick" + [ ! -d $USBMNT/LiveOS ] && mkdir $USBMNT/LiveOS + [ -n "$keephome" -a -f "$USBMNT/$HOMEFILE" ] && mv $USBMNT/$HOMEFILE $USBMNT/LiveOS/$HOMEFILE + # cases without /LiveOS are legacy detection, remove for F10 + if [ -n "$skipcompress" -a -f $CDMNT/LiveOS/squashfs.img ]; then + mount -o loop $CDMNT/LiveOS/squashfs.img $CDMNT + cp $CDMNT/LiveOS/ext3fs.img $USBMNT/LiveOS/ext3fs.img || (umount $CDMNT ; exitclean) + umount $CDMNT + elif [ -f $CDMNT/LiveOS/squashfs.img ]; then + cp $CDMNT/LiveOS/squashfs.img $USBMNT/LiveOS/squashfs.img || exitclean + elif [ -f $CDMNT/squashfs.img ]; then + cp $CDMNT/squashfs.img $USBMNT/LiveOS/squashfs.img || exitclean + elif [ -f $CDMNT/LiveOS/ext3fs.img ]; then + cp $CDMNT/LiveOS/ext3fs.img $USBMNT/LiveOS/ext3fs.img || exitclean + elif [ -f $CDMNT/ext3fs.img ]; then + cp $CDMNT/ext3fs.img $USBMNT/LiveOS/ext3fs.img || exitclean + fi + if [ -f $CDMNT/LiveOS/osmin.img ]; then + cp $CDMNT/LiveOS/osmin.img $USBMNT/LiveOS/osmin.img || exitclean + fi fi -if [ -z "$mactel" ]; then - cp $CDMNT/isolinux/* $USBMNT/$SYSLINUXPATH - BOOTCONFIG=$USBMNT/$SYSLINUXPATH/isolinux.cfg -else +cp $CDMNT/isolinux/* $USBMNT/$SYSLINUXPATH +BOOTCONFIG=$USBMNT/$SYSLINUXPATH/isolinux.cfg +if [ -n "$mactel" ];then if [ -d $CDMNT/EFI/boot ]; then cp $CDMNT/EFI/boot/* $USBMNT/EFI/boot else @@ -599,8 +658,9 @@ echo "Installing boot loader" if [ -n "$mactel" ]; then # replace the ia32 hack if [ -f "$USBMNT/EFI/boot/boot.conf" ]; then cp -f $USBMNT/EFI/boot/bootia32.conf $USBMNT/EFI/boot/boot.conf ; fi - cleanup -elif [ "$USBFS" = "vfat" -o "$USBFS" = "msdos" ]; then +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 mv $USBMNT/$SYSLINUXPATH/isolinux.cfg $USBMNT/$SYSLINUXPATH/syslinux.cfg From katzj at fedoraproject.org Mon Jan 19 16:57:43 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Mon, 19 Jan 2009 16:57:43 +0000 (UTC) Subject: [Fedora-livecd-list] livecd-tools.spec Makefile Message-ID: <20090119165743.4AB1F12015A@lists.fedorahosted.org> Makefile | 4 livecd-tools.spec | 242 ------------------------------------------------------ 2 files changed, 2 insertions(+), 244 deletions(-) New commits: commit 4125fbd5713d071cbbab076130f8e077da68cabc Author: Jeremy Katz Date: Mon Jan 19 11:26:06 2009 -0500 Bump version diff --git a/Makefile b/Makefile index 48c89d5..f5625a4 100644 --- a/Makefile +++ b/Makefile @@ -1,5 +1,5 @@ -VERSION = 020 +VERSION = 021 INSTALL = /usr/bin/install -c INSTALL_PROGRAM = ${INSTALL} @@ -42,7 +42,7 @@ uninstall: rm -rf $(DESTDIR)/usr/share/doc/livecd-tools-$(VERSION) dist : all - git-archive --format=tar --prefix=livecd-tools-$(VERSION)/ HEAD | bzip2 -9v > livecd-tools-$(VERSION).tar.bz2 + git archive --format=tar --prefix=livecd-tools-$(VERSION)/ HEAD | bzip2 -9v > livecd-tools-$(VERSION).tar.bz2 clean: rm -f *~ creator/*~ installer/*~ config/*~ docs/*.8 diff --git a/livecd-tools.spec b/livecd-tools.spec deleted file mode 100644 index 215b576..0000000 --- a/livecd-tools.spec +++ /dev/null @@ -1,242 +0,0 @@ -%{!?python_sitelib: %define python_sitelib %(%{__python} -c "import distutils.sysconfig as d; print d.get_python_lib()")} - -%define debug_package %{nil} - -Summary: Tools for building live CD's -Name: livecd-tools -Version: 020 -Release: 1%{?dist} -License: GPLv2 -Group: System Environment/Base -URL: http://git.fedoraproject.org/?p=hosted/livecd -Source0: %{name}-%{version}.tar.bz2 -BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root -Requires: util-linux -Requires: coreutils -Requires: e2fsprogs -Requires: yum >= 3.2.18 -Requires: mkisofs -Requires: squashfs-tools -Requires: pykickstart >= 0.96 -Requires: dosfstools >= 2.11-8 -Requires: isomd5sum -Requires: rhpl -Requires: python-urlgrabber -%ifarch %{ix86} x86_64 -Requires: syslinux -%endif -%ifarch ppc -Requires: yaboot -%endif -BuildRequires: python -BuildRequires: /usr/bin/pod2man - - -%description -Tools for generating live CD's on Fedora based systems including -derived distributions such as RHEL, CentOS and others. See -http://fedoraproject.org/wiki/FedoraLiveCD for more details. - -%prep -%setup -q - -%build -make - -%install -rm -rf $RPM_BUILD_ROOT -make install DESTDIR=$RPM_BUILD_ROOT - -%clean -rm -rf $RPM_BUILD_ROOT - -%files -%defattr(-,root,root,-) -%doc AUTHORS COPYING README HACKING API -%doc config/livecd-fedora-minimal.ks -%{_mandir}/man*/* -%{_bindir}/livecd-creator -%{_bindir}/livecd-iso-to-disk -%{_bindir}/livecd-iso-to-pxeboot -%{_bindir}/image-creator -%dir %{python_sitelib}/imgcreate -%{python_sitelib}/imgcreate/*.py -%{python_sitelib}/imgcreate/*.pyo -%{python_sitelib}/imgcreate/*.pyc - -%changelog -* Wed Nov 12 2008 Jeremy Katz - 020-1 -- Support setting up a swap file -- Verify integer args in livecd-iso-to-disk (#467257) -- Set up persistent /home on internal mtd0 for XO -- Default to resetting the overlay on XO -- Support copying the raw ext3fs to the usb stick instead of the squash -- Mactel fixes -- Align initrd properly on XO (#467093) -- Make initrd load addr work on newer XO firmwares -- Fix up Xen paths for Xen live images (Michael Ansel) -- Support --defaultdesktop (Orion Poplawski) - -* Fri Oct 10 2008 Jeremy Katz - 019-1 -- livecd-iso-to-disk: Various other XO fixes -- Cleanup rpmdb locks after package installation -- Fix traceback due to lazy rhpl.keyboard import -- Fix using groups with options (jkeating) -- Support persistent /home on XO's internal flash -- Fix ramdisk load addr in boot/olpc.fth for XO -- Fix up boot from SD -- Fix extracting boot parameters for pxe (apevec) -- Make rpm macro information persist into the image (bkearney) -- Support %packages --instLangs (bkearney) - -* Thu Aug 28 2008 Jeremy Katz - 018-1 -- Use logging API for debugging messages (dhuff) -- Some initial support for booting live images on an XO -- Refactoring of mount code for appliance-creator (danpb, dhuff) -- Make --base-on actually work again -- Drop the image configs; these are now in the spin-kickstarts repo -- plymouth support -- Listen to bootloader --append in config -- Add man pages (Pedro Silva) -- Support booting from Intel based Macs via EFI on USB (#450193) -- Fixes for SELinux enforcing (eparis) -- Eject the CD on shutdown (#239928) -- Allow adding extra kernel args with livecd-iso-to-disk -- Support for persistent /home (#445218) -- Copy timezone to /etc/localtime (#445624) -- Ensure that commands run by livecd-creator exist -- Mount a tmpfs for some dirs (#447127) - -* Tue May 6 2008 Bill Nottingham - 017-1 -- fix F9 final configs - -* Thu May 1 2008 Jeremy Katz - 016-1 -- Config changes all around, including F9 final configs -- Fix up the minimal image creation -- Fix odd traceback error on __del__ (#442443) -- Add late initscript and split things in half -- livecd-iso-to-disk: Check the available space on the stick (#443046) -- Fix partition size overriding (kanarip) - -* Thu Mar 6 2008 Jeremy Katz - 015-1 -- Support for using live isos with pxe booting (Richard W.M. Jones and - Chris Lalancette) -- Fixes for SELinux being disabled (Warren Togami) -- Stop using mayflower for building the initrd; mkinitrd can do it now -- Create a minimal /dev rather than using the host /dev (Warren Togami) -- Support for persistent overlays when using a USB stick (based on support - by Douglas McClendon) - -* Tue Feb 12 2008 Jeremy Katz - 014-1 -- Rework to provide a python API for use by other tools (thanks to - markmc for a lot of the legwork here) -- Fix creation of images with ext2 filesystems and no SELinux -- Don't require a yum-cache directory inside of the cachedir (#430066) -- Many config updates for rawhide -- Allow running live images from MMC/SD (#430444) -- Don't let a non-standard TMPDIR break things (Jim Meyering) - -* Mon Oct 29 2007 Jeremy Katz - 013-1 -- Lots of config updates -- Support 'device foo' to say what modules go in the initramfs -- Support multiple kernels being installed -- Allow blacklisting kernel modules on boot with blacklist=foo -- Improve bootloader configs -- Split configs off for f8 - -* Tue Sep 25 2007 Jeremy Katz - 012-1 -- Allow %%post --nochroot to work for putting files in the root of the iso -- Set environment variables for when %%post is run -- Add progress for downloads (Colin Walters) -- Add cachedir option (Colin Walters) -- Fixes for ppc/ppc64 to work again -- Clean up bootloader config a little -- Enable swaps in the default desktop config -- Ensure all configs are installed (#281911) -- Convert method line to a repo for easier config reuse (jkeating) -- Kill the modprobe FATAL warnings (#240585) -- Verify isos with iso-to-disk script -- Allow passing xdriver for setting the xdriver (#291281) -- Add turboliveinst patch (Douglas McClendon) -- Make iso-to-disk support --resetmbr (#294041) -- Clean up filesystem layout (Douglas McClendon) -- Manifest tweaks for most configs - -* Tue Aug 28 2007 Jeremy Katz - 011-1 -- Many config updates for Fedora 8 -- Support $basearch in repo line of configs; use it -- Support setting up Xen kernels and memtest86+ in the bootloader config -- Handle rhgb setup -- Improved default fs label (Colin Walters) -- Support localboot from the bootloader (#252192) -- Use hidden menu support in syslinux -- Have a base desktop config included by the other configs (Colin Walters) -- Use optparse for optino parsing -- Remove a lot of command line options; things should be specified via the - kickstart config instead -- Beginnings of PPC support (David Woodhouse) -- Clean up kernel module inclusion to take advantage of files in Fedora - kernels listing storage drivers - -* Wed Jul 25 2007 Jeremy Katz - 010-1 -- Separate out configs used for Fedora 7 -- Add patch from Douglas McClendon to make images smaller -- Add patch from Matt Domsch to work with older syslinux without vesamenu -- Add support for using mirrorlists; use them -- Let livecd-iso-to-disk work with uncompressed images (#248081) -- Raise error if SELinux requested without being enabled (#248080) -- Set service defaults on level 2 also (#246350) -- Catch some failure cases -- Allow specifying tmpdir -- Add patch from nameserver specification from Elias Hunt - -* Wed May 30 2007 Jeremy Katz - 009-1 -- miscellaneous live config changes -- fix isomd5 checking syntax error - -* Fri May 4 2007 Jeremy Katz - 008-1 -- disable screensaver with default config -- add aic7xxx and sym53c8xx drivers to default initramfs -- fixes from johnp for FC6 support in the creator -- fix iso-to-stick to work on FC6 - -* Tue Apr 24 2007 Jeremy Katz - 007-1 -- Disable prelinking by default -- Disable some things that slow down the live boot substantially -- Lots of tweaks to the default package manifests -- Allow setting the root password (Jeroen van Meeuwen) -- Allow more specific network line setting (Mark McLoughlin) -- Don't pollute the host yum cache (Mark McLoughlin) -- Add support for mediachecking - -* Wed Apr 4 2007 Jeremy Katz - 006-1 -- Many fixes to error handling from Mark McLoughlin -- Add the KDE config -- Add support for prelinking -- Fixes for installing when running from RAM or usb stick -- Add sanity checking to better ensure that USB stick is bootable - -* Thu Mar 29 2007 Jeremy Katz - 005-3 -- have to use excludearch, not exclusivearch - -* Thu Mar 29 2007 Jeremy Katz - 005-2 -- exclusivearch since it only works on x86 and x86_64 for now - -* Wed Mar 28 2007 Jeremy Katz - 005-1 -- some shell quoting fixes -- allow using UUID or LABEL for the fs label of a usb stick -- work with ext2 formated usb stick - -* Mon Mar 26 2007 Jeremy Katz - 004-1 -- add livecd-iso-to-disk for setting up the live CD iso image onto a usb - stick or similar - -* Fri Mar 23 2007 Jeremy Katz - 003-1 -- fix remaining reference to run-init - -* Thu Mar 22 2007 Jeremy Katz - 002-1 -- update for new version - -* Fri Dec 22 2006 David Zeuthen - 001-1%{?dist} -- Initial build. - From Daire.Byrne at framestore.com Mon Jan 19 17:39:36 2009 From: Daire.Byrne at framestore.com (Daire Byrne) Date: Mon, 19 Jan 2009 17:39:36 +0000 (GMT) Subject: [Fedora-livecd-list] Mac (EFI) USB booting Message-ID: <54890450.411232386776911.JavaMail.root@mailbox1> Hi, I have been trying to get Mac booting working but I am struggling to jump the first hurdle - namely having the Mac recognise the USB drive as a bootable device. I have used ALT on boot to list the bootable drives on both a Mac Mini and a PowerMac desktop machine but neither recognise a USB stick created with livecd-tools. In fact after booting from the drive MacOSX informs me that the drive isn't initialised and wants me to format it. Checking the partitions in Linux they are laid out as expected with a bootable EFI partition vfat formatted. I gave up on EFI booting and even tried a classic MBR install with rEFIt but still the USB drive is never detected. Is there another trick I'm missing here or does USB booting only work on a very small subset of Intel Mac models? The recent EFI+MBR work looks interesting but like I said I can't even get that far. Regards, Daire From katzj at redhat.com Mon Jan 19 18:19:58 2009 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 19 Jan 2009 13:19:58 -0500 Subject: [Fedora-livecd-list] Mac (EFI) USB booting In-Reply-To: <54890450.411232386776911.JavaMail.root@mailbox1> References: <54890450.411232386776911.JavaMail.root@mailbox1> Message-ID: <20090119181958.GC6090@redhat.com> On Monday, January 19 2009, Daire Byrne said: > I have been trying to get Mac booting working but I am struggling to jump the first hurdle - > namely having the Mac recognise the USB drive as a bootable device. I have used ALT on boot to > list the bootable drives on both a Mac Mini and a PowerMac desktop machine but neither > recognise a USB stick created with livecd-tools. In fact after booting from the drive MacOSX > informs me that the drive isn't initialised and wants me to format it. Checking the partitions > in Linux they are laid out as expected with a bootable EFI partition vfat formatted. PowerMacs (PPC) are an entirely different beast and there's not really been any work done on getting them booting off of USB. For the x86 based Macs, it can work, but it's definitely far from just working everywhere right now. The first question is if your machine is 32bit or 64bit EFI as we require matching x86 vs x86_64, respectively, based on that. Most of the original Core Duo stuff is 32bit EFI, the newer is 64bit. If you're using a 64bit EFI machine, right now, you're out of luck -- the kernel even in Fedora 10 was broken with 64bit EFI :( For 32bit, it _should_ work with Fedora 10. But I don't think I've actually tested it on one of the Minis, and sadly, the Apple firmware has been notoriously bad about being buggy :) > I gave up on EFI booting and even tried a classic MBR install with rEFIt but still the USB drive > is never detected. Is there another trick I'm missing here or does USB booting only work on a very > small subset of Intel Mac models? The recent EFI+MBR work looks interesting but like I said I can't > even get that far. I never managed to get rEFIt to boot off of an MBR-based USB device. Some people said they did, but I have no clue what they did to do so :) Jeremy From Daire.Byrne at framestore.com Mon Jan 19 18:43:57 2009 From: Daire.Byrne at framestore.com (Daire Byrne) Date: Mon, 19 Jan 2009 18:43:57 +0000 (GMT) Subject: [Fedora-livecd-list] Mac (EFI) USB booting In-Reply-To: <1241702395.491232390581842.JavaMail.root@mailbox1> Message-ID: <228994944.511232390637461.JavaMail.root@mailbox1> Jeremy, ----- "Jeremy Katz" wrote: > PowerMacs (PPC) are an entirely different beast and there's not > really been any work done on getting them booting off of USB. Indeed - not too bothered about them. > For the x86 based Macs, it can work, but it's definitely far from > just working everywhere right now. The first question is if your machine > is 32bit or 64bit EFI as we require matching x86 vs x86_64, > respectively, based on that. Most of the original Core Duo stuff is 32bit EFI, the > newer is 64bit. If you're using a 64bit EFI machine, right now, > you're out of luck -- the kernel even in Fedora 10 was broken with 64bit EFI > :( Yes I saw that. Like I said I'd just be happy to even get one of my Macs to recognise the USB drive as a boot device at this point! I suppose I should test on a new MacBook too for completeness. I would have thought the Mac Mini should work though as that is x86_64 and has the Core Duo 2. > I never managed to get rEFIt to boot off of an MBR-based USB device. > Some people said they did, but I have no clue what they did to do so > :) I found the same kind of confusion too - some say it can be done others say it can't. To be honest booting a MBR USB stick on Mac is still probably the best way to go because the 3D gfx for ATI/Nvidia doesn't work under EFI atm. I think I'm going to have to try booting of a CD just for the GRUB/SysLinux boot and then mount the USB stick after the kernel boots up and the initrd scripts begin. Thanks for the reply. Daire From katzj at redhat.com Mon Jan 19 18:53:58 2009 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 19 Jan 2009 13:53:58 -0500 Subject: [Fedora-livecd-list] Mac (EFI) USB booting In-Reply-To: <228994944.511232390637461.JavaMail.root@mailbox1> References: <1241702395.491232390581842.JavaMail.root@mailbox1> <228994944.511232390637461.JavaMail.root@mailbox1> Message-ID: <20090119185358.GA8602@redhat.com> On Monday, January 19 2009, Daire Byrne said: > ----- "Jeremy Katz" wrote: > > For the x86 based Macs, it can work, but it's definitely far from > > just working everywhere right now. The first question is if your machine > > is 32bit or 64bit EFI as we require matching x86 vs x86_64, > > respectively, based on that. Most of the original Core Duo stuff is 32bit EFI, the > > newer is 64bit. If you're using a 64bit EFI machine, right now, > > you're out of luck -- the kernel even in Fedora 10 was broken with 64bit EFI > > :( > > Yes I saw that. Like I said I'd just be happy to even get one of my Macs to recognise the USB drive as a boot device at this point! I suppose I should test on a new MacBook too for completeness. I would have thought the Mac Mini should work though as that is x86_64 and has the Core Duo 2. If it's a Core Duo 2, then it's _probably_ 64bit EFI -- so try with the x86_64 Fedora 10 live image and I think it should at least be able to bring up grub. > > I never managed to get rEFIt to boot off of an MBR-based USB device. > > Some people said they did, but I have no clue what they did to do so > > :) > > I found the same kind of confusion too - some say it can be done others say it can't. To be honest booting a MBR USB stick on Mac is still probably the best way to go because the 3D gfx for ATI/Nvidia doesn't work under EFI atm. I think I'm going to have to try booting of a CD just for the GRUB/SysLinux boot and then mount the USB stick after the kernel boots up and the initrd scripts begin. If you can find a way to consistently get an MBR USB stick to boot, I'd love to help improve the docs there as I agree, it would certainly be the "best" thing. One thing you can do is make a boot cd that has just the isolinux bits and then points to a USB stick for the rootfs just by changing the root= and rootfstype= arguments in isolinux.cfg. I have done that with no problems a number of times Jeremy From maillist at diffingo.com Mon Jan 19 19:36:13 2009 From: maillist at diffingo.com (Stewart Adam) Date: Mon, 19 Jan 2009 14:36:13 -0500 Subject: [Fedora-livecd-list] Mac (EFI) USB booting In-Reply-To: <20090119181958.GC6090@redhat.com> References: <54890450.411232386776911.JavaMail.root@mailbox1> <20090119181958.GC6090@redhat.com> Message-ID: <4974D62D.5000309@diffingo.com> On 1/19/09 1:19 PM, Jeremy Katz wrote: > PowerMacs (PPC) are an entirely different beast and there's not really > been any work done on getting them booting off of USB. > > For the x86 based Macs, it can work, but it's definitely far from just > working everywhere right now. The first question is if your machine is > 32bit or 64bit EFI as we require matching x86 vs x86_64, respectively, > based on that. Most of the original Core Duo stuff is 32bit EFI, the > newer is 64bit. If you're using a 64bit EFI machine, right now, you're > out of luck -- the kernel even in Fedora 10 was broken with 64bit EFI :( I didn't think of giving it a on one of the older MacBook machines - I'll do that sometime soon. It could be a bug in the 64bit firmware, but I have tried using a i386 grub EFI image and i386 kernel on my early 2008 MacBook Po, but same symptoms as booting 64bit kernels. > For 32bit, it _should_ work with Fedora 10. But I don't think I've > actually tested it on one of the Minis, and sadly, the Apple firmware > has been notoriously bad about being buggy :) Yup - the MBR USB bug seems to one of the more annoying ones :/ >> I gave up on EFI booting and even tried a classic MBR install with rEFIt but still the USB drive >> is never detected. Is there another trick I'm missing here or does USB booting only work on a very >> small subset of Intel Mac models? The recent EFI+MBR work looks interesting but like I said I can't >> even get that far. > > I never managed to get rEFIt to boot off of an MBR-based USB device. > Some people said they did, but I have no clue what they did to do so :) There was so many reports with different results... If what I read was correct, it looks like some of Apple's older firmware didn't have the USB MBR booting bug, but the newer firmware (post BootCamp 2.0 I think) does. So really, anyone that runs Software Update or buys a Mac with the new BootCamp already installed doesn't have the ability to boot from USB drives with an MBR in rEFIt... Instead, rEFIt switches and uses the internal drive's MBR. Stewart From ftaylor at redhat.com Tue Jan 20 16:14:42 2009 From: ftaylor at redhat.com (Forrest Taylor) Date: Tue, 20 Jan 2009 11:14:42 -0500 Subject: [Fedora-livecd-list] Overlay File Health? In-Reply-To: <818ac3c70901140342k77488edci6b1b6d4bcb466ac7@mail.gmail.com> References: <818ac3c70901140342k77488edci6b1b6d4bcb466ac7@mail.gmail.com> Message-ID: <1232468082.16665.3.camel@localhost.localdomain> On Wed, 2009-01-14 at 06:42 -0500, Kam Salisbury wrote: > How do I see how much space is used in the overlay file (Fedora USB)? > > [liveuser at localhost ~]$ df -h I also have a question regarding the overlay, that will probably be answered by whomever answers your question. Is the overlay ever used? The /home directory is setup using the live script, but the overlay is never setup as far as I can see. Is it meant to be used to add disk space to the root directory? Thanks, -- Forrest Taylor Global Learning Services Project Manager III Cell: 303-913-5169 AIM: forresttaylorred Red Hat IRC: forrest -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Daire.Byrne at framestore.com Wed Jan 21 17:57:38 2009 From: Daire.Byrne at framestore.com (Daire Byrne) Date: Wed, 21 Jan 2009 17:57:38 +0000 (GMT) Subject: [Fedora-livecd-list] Mac (EFI) USB booting In-Reply-To: <20090119185358.GA8602@redhat.com> Message-ID: <205022483.1631232560658230.JavaMail.root@mailbox1> ----- "Jeremy Katz" wrote: > > > I never managed to get rEFIt to boot off of an MBR-based USB device. > > > Some people said they did, but I have no clue what they did to do so > > > :) > > > > I found the same kind of confusion too - some say it can be done > > others say it can't. To be honest booting a MBR USB stick on Mac is > > still probably the best way to go because the 3D gfx for ATI/Nvidia > > doesn't work under EFI atm. I think I'm going to have to try booting > > of a CD just for the GRUB/SysLinux boot and then mount the USB stick > > after the kernel boots up and the initrd scripts begin. > > > If you can find a way to consistently get an MBR USB stick to boot, I'd > love to help improve the docs there as I agree, it would certainly be > the "best" thing. > > One thing you can do is make a boot cd that has just the isolinux > bits and then points to a USB stick for the rootfs just by changing the > root= and rootfstype= arguments in isolinux.cfg. I have done that with no > problems a number of times Just to follow up I have resorted to using a CD to do the MBR Grub boot with the kernel and initrd booting from the CD but the root squashfs filesystem mounted from the USB stick. This seems to be the most compatible way of using a USB stick on a wide variety of Macs. The EFI stuff even when it works will not do 3d acceleration. Now I just need to get a version of the intel (i810) X11 drivers to work on my Mac Mini..... Thanks for the feedback. Daire From ftaylor at redhat.com Wed Jan 21 18:56:55 2009 From: ftaylor at redhat.com (Forrest Taylor) Date: Wed, 21 Jan 2009 13:56:55 -0500 Subject: [Fedora-livecd-list] Anyone using the overlay file? Message-ID: <1232564215.28562.136.camel@papa> In the iso-to-disk script, one can add an overlay file. However, I don't see that it is being used at all--livesys does not reference it at all. It looks like the XO team passes a kernel parameter, but I haven't seen the code to actually use it. My assumption is that the overlay file would be the backend storage for an LVM snapshot. Has anyone actually used an overlay file? Any ideas on the implementation? Thanks, -- Forrest -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From katzj at redhat.com Wed Jan 21 19:00:02 2009 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 21 Jan 2009 14:00:02 -0500 Subject: [Fedora-livecd-list] Anyone using the overlay file? In-Reply-To: <1232564215.28562.136.camel@papa> References: <1232564215.28562.136.camel@papa> Message-ID: <20090121190002.GB409@redhat.com> On Wednesday, January 21 2009, Forrest Taylor said: > In the iso-to-disk script, one can add an overlay file. However, I > don't see that it is being used at all--livesys does not reference it at > all. It looks like the XO team passes a kernel parameter, but I haven't > seen the code to actually use it. > > My assumption is that the overlay file would be the backend storage for > an LVM snapshot. Has anyone actually used an overlay file? Any ideas > on the implementation? The overlay gets set up in the initramfs, so see mkliveinitrd in the mkinitrd package. Basically what happens is that instead of creating a file that's backed by RAM to use as our dm-snapshot device, we set up dm-snapshot to write to the file on the USB stick instead. Jeremy From ftaylor at redhat.com Wed Jan 21 21:57:18 2009 From: ftaylor at redhat.com (Forrest Taylor) Date: Wed, 21 Jan 2009 16:57:18 -0500 Subject: [Fedora-livecd-list] Anyone using the overlay file? In-Reply-To: <20090121190002.GB409@redhat.com> References: <1232564215.28562.136.camel@papa> <20090121190002.GB409@redhat.com> Message-ID: <1232575038.28562.147.camel@papa> On Wed, 2009-01-21 at 14:00 -0500, Jeremy Katz wrote: > On Wednesday, January 21 2009, Forrest Taylor said: > > In the iso-to-disk script, one can add an overlay file. However, I > > don't see that it is being used at all--livesys does not reference it at > > all. It looks like the XO team passes a kernel parameter, but I haven't > > seen the code to actually use it. > > > > My assumption is that the overlay file would be the backend storage for > > an LVM snapshot. Has anyone actually used an overlay file? Any ideas > > on the implementation? > > The overlay gets set up in the initramfs, so see mkliveinitrd in the > mkinitrd package. Basically what happens is that instead of creating a > file that's backed by RAM to use as our dm-snapshot device, we set up > dm-snapshot to write to the file on the USB stick instead. Thanks, Jeremy, that makes sense now. It looks like mayflower was the script that did this in RHEL5, so I'll see if I can backport it. Is there any way to see how much of the overlay is being used from within the live image? Thanks again, -- Forrest -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From katzj at redhat.com Wed Jan 21 22:10:05 2009 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 21 Jan 2009 17:10:05 -0500 Subject: [Fedora-livecd-list] Anyone using the overlay file? In-Reply-To: <1232575038.28562.147.camel@papa> References: <1232564215.28562.136.camel@papa> <20090121190002.GB409@redhat.com> <1232575038.28562.147.camel@papa> Message-ID: <20090121221004.GA12954@redhat.com> On Wednesday, January 21 2009, Forrest Taylor said: > On Wed, 2009-01-21 at 14:00 -0500, Jeremy Katz wrote: > > On Wednesday, January 21 2009, Forrest Taylor said: > > > In the iso-to-disk script, one can add an overlay file. However, I > > > don't see that it is being used at all--livesys does not reference it at > > > all. It looks like the XO team passes a kernel parameter, but I haven't > > > seen the code to actually use it. > > > > > > My assumption is that the overlay file would be the backend storage for > > > an LVM snapshot. Has anyone actually used an overlay file? Any ideas > > > on the implementation? > > > > The overlay gets set up in the initramfs, so see mkliveinitrd in the > > mkinitrd package. Basically what happens is that instead of creating a > > file that's backed by RAM to use as our dm-snapshot device, we set up > > dm-snapshot to write to the file on the USB stick instead. > > Thanks, Jeremy, that makes sense now. It looks like mayflower was the > script that did this in RHEL5, so I'll see if I can backport it. mkliveinitrd is basically mayflower renamed and moved into mkinitrd (where it should have been to begin with). > Is there any way to see how much of the overlay is being used from > within the live image? Not usefully -- you can string together some 'dm table' commands and get the number of blocks used but it requires being root and also had some oddities. My kingdom for an upstreamable unionfs :/ Jeremy From Daire.Byrne at framestore.com Thu Jan 22 09:51:30 2009 From: Daire.Byrne at framestore.com (Daire Byrne) Date: Thu, 22 Jan 2009 09:51:30 +0000 (GMT) Subject: [Fedora-livecd-list] Anyone using the overlay file? In-Reply-To: <1369332778.1861232617887517.JavaMail.root@mailbox1> Message-ID: <1665413109.1881232617890816.JavaMail.root@mailbox1> ----- "Jeremy Katz" wrote: > Not usefully -- you can string together some 'dm table' commands and > get the number of blocks used but it requires being root and also had > some oddities. > > My kingdom for an upstreamable unionfs :/ We use "aufs" to union a COW filesystem for our custom "Live" system. It does seem a little odd that many of the other distros now use a union filesystem approach to LiveCDs and NFS read-only roots but Fedora has for the time being stayed away from it. It's not like there isn't lots of custom stuff being put into fedora/redhat kernels that isn't yet upstream. In fact there was a discussion about getting UnionFS upstream recently on the kernel list.... Saying all this the dm-snapshot approach will be more efficient space wise as it works with blocks instead of whole files. Daire From herlo1 at gmail.com Thu Jan 22 10:07:34 2009 From: herlo1 at gmail.com (Clint Savage) Date: Thu, 22 Jan 2009 03:07:34 -0700 Subject: [Fedora-livecd-list] Building a Kiosk Live CD Message-ID: Hi all, I'm in the process of building a kiosk CD using xguest, but I continue to run into an issue where I can't install xguest during the building of the Live CD. It appears the reason for this is some SELinux settings it tries to make when installing the RPM. As such, the xguest rpm fails. Here's the message I get from the livecd-creator when attempting to install xguest. libsemanage.bool_read_list: could not get list of boolean names (No such file or directory). libsemanage.bool_read_list: could not read boolean list (No such file or directory). libsemanage.dbase_activedb_cache: could not cache active database (No such file or directory). libsemanage.enter_rw: could not enter read-write section (No such file or directory). Could not change boolean allow_polyinstantiation Could not change policy booleans error: %pre(xguest-1.0.6-7.fc9.noarch) scriptlet failed, exit status 255 error: install: %pre scriptlet failed (2), skipping xguest-1.0.6-7.fc9 I'm quite certain that if I were able to better understand how to adjust the SELinux values above during the build, I would be better off. But currently, I want to see if there is a recommended way of dealing with this sort of thing during the Live CD creation process. Cheers, Clint From katzj at redhat.com Thu Jan 22 14:23:45 2009 From: katzj at redhat.com (Jeremy Katz) Date: Thu, 22 Jan 2009 09:23:45 -0500 Subject: [Fedora-livecd-list] Anyone using the overlay file? In-Reply-To: <1665413109.1881232617890816.JavaMail.root@mailbox1> References: <1369332778.1861232617887517.JavaMail.root@mailbox1> <1665413109.1881232617890816.JavaMail.root@mailbox1> Message-ID: <20090122142344.GA1120@redhat.com> On Thursday, January 22 2009, Daire Byrne said: > ----- "Jeremy Katz" wrote: > > Not usefully -- you can string together some 'dm table' commands and > > get the number of blocks used but it requires being root and also had > > some oddities. > > > > My kingdom for an upstreamable unionfs :/ > > We use "aufs" to union a COW filesystem for our custom "Live" system. It does seem a little odd that many of the other distros now use a union filesystem approach to LiveCDs and NFS read-only roots but Fedora has for the time being stayed away from it. It's not like there isn't lots of custom stuff being put into fedora/redhat kernels that isn't yet upstream. In fact there was a discussion about getting UnionFS upstream recently on the kernel list.... A discussion that went nowhere fast. Just like every previous discussion of unionfs. And actually, we're _very_ resistent to adding not-upstreamed stuff into the Fedora kernels. Things that are in an appropriate staging tree? Yeah. But unionfs isn't even there > Saying all this the dm-snapshot approach will be more efficient space wise as it works with blocks instead of whole files. But since it works on blocks, you have no way at all to ever reasonably pull out your changes and apply them for a new image and a lot of other things Jeremy From Daire.Byrne at framestore.com Thu Jan 22 17:54:27 2009 From: Daire.Byrne at framestore.com (Daire Byrne) Date: Thu, 22 Jan 2009 17:54:27 +0000 (GMT) Subject: [Fedora-livecd-list] Anyone using the overlay file? In-Reply-To: <601005072.2611232640860396.JavaMail.root@mailbox1> Message-ID: <8344257.3031232646867039.JavaMail.root@mailbox1> ----- "Jeremy Katz" wrote: > > We use "aufs" to union a COW filesystem for our custom "Live" > system. It does seem a little odd that many of the other distros now > use a union filesystem approach to LiveCDs and NFS read-only roots but > Fedora has for the time being stayed away from it. It's not like there > isn't lots of custom stuff being put into fedora/redhat kernels that > isn't yet upstream. In fact there was a discussion about getting > UnionFS upstream recently on the kernel list.... > > A discussion that went nowhere fast. Just like every previous > discussion of unionfs. And actually, we're _very_ resistent to > adding not-upstreamed stuff into the Fedora kernels. Things that are in an > appropriate staging tree? Yeah. But unionfs isn't even there I have been playing around with the 2.6.28 fc10 kernel from Koji: http://koji.fedoraproject.org/koji/buildinfo?buildID=79697 It looks like it has the UnionFS patches included. Maybe it'll drop out of a final release though. Daire From apevec at redhat.com Fri Jan 23 17:53:45 2009 From: apevec at redhat.com (Alan Pevec) Date: Fri, 23 Jan 2009 18:53:45 +0100 Subject: [Fedora-livecd-list] [PATCH] localboot is available only in ISOLINUX and PXELINUX Message-ID: <1232733225-7040-1-git-send-email-apevec@redhat.com> so it should be removed from sys/extlinux.cfg to avoid error message: unknown keyword in syslinux.cfg It is masked by the menu, shows up only with custom image builds where isolinux.cfg is modified. See http://syslinux.zytor.com/wiki/index.php/SYSLINUX#LOCALBOOT_type_.5BISOLINUX.2C_PXELINUX.5D Signed-off-by: Alan Pevec --- tools/livecd-iso-to-disk.sh | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/tools/livecd-iso-to-disk.sh b/tools/livecd-iso-to-disk.sh index d37a2e9..364deb1 100755 --- a/tools/livecd-iso-to-disk.sh +++ b/tools/livecd-iso-to-disk.sh @@ -544,6 +544,9 @@ echo "Updating boot config file" # adjust label and fstype sed -i -e "s/CDLABEL=[^ ]*/$USBLABEL/" -e "s/rootfstype=[^ ]*/rootfstype=$USBFS/" $BOOTCONFIG if [ -n "$kernelargs" ]; then sed -i -e "s/liveimg/liveimg ${kernelargs}/" $BOOTCONFIG ; fi +# localboot is available only in ISOLINUX and PXELINUX +# http://syslinux.zytor.com/wiki/index.php/SYSLINUX#LOCALBOOT_type_.5BISOLINUX.2C_PXELINUX.5D +sed -i -e '/label local/d' -e '/localboot 0xffff/d' $BOOTCONFIG if [ "$overlaysizemb" -gt 0 ]; then echo "Initializing persistent overlay file" -- 1.6.0.6 From katzj at redhat.com Fri Jan 23 18:06:39 2009 From: katzj at redhat.com (Jeremy Katz) Date: Fri, 23 Jan 2009 13:06:39 -0500 Subject: [Fedora-livecd-list] [PATCH] localboot is available only in ISOLINUX and PXELINUX In-Reply-To: <1232733225-7040-1-git-send-email-apevec@redhat.com> References: <1232733225-7040-1-git-send-email-apevec@redhat.com> Message-ID: <20090123180639.GD15995@redhat.com> On Friday, January 23 2009, Alan Pevec said: > so it should be removed from sys/extlinux.cfg to avoid error message: > unknown keyword in syslinux.cfg > It is masked by the menu, shows up only with custom image builds where > isolinux.cfg is modified. > See http://syslinux.zytor.com/wiki/index.php/SYSLINUX#LOCALBOOT_type_.5BISOLINUX.2C_PXELINUX.5D It's actually supported with 3.70+ which is queued up to go into rawhide after the alpha goes out. Jeremy From maillist at diffingo.com Mon Jan 26 22:50:44 2009 From: maillist at diffingo.com (Stewart Adam) Date: Mon, 26 Jan 2009 17:50:44 -0500 Subject: [Fedora-livecd-list] [PATCH] Using both EFI and MBR at once on Live USB images and other misc. fixes In-Reply-To: <20090119155540.GD32152@redhat.com> References: <48F7FC16.9090201@diffingo.com> <1224213914.370.85.camel@aglarond.local> <48F87E65.6040104@diffingo.com> <1224251419.13356.46.camel@aglarond.local> <48F8A696.8020601@diffingo.com> <4908E124.10603@diffingo.com> <1225327119.25818.2.camel@aglarond.local> <49090E7A.7090009@diffingo.com> <20090116210907.GC27731@redhat.com> <49723D49.7050602@diffingo.com> <20090119155540.GD32152@redhat.com> Message-ID: <497E3E44.1050504@diffingo.com> On 1/19/09 10:55 AM, Jeremy Katz wrote: > On Saturday, January 17 2009, Stewart Adam said: >> There's been some good progress - I sent a few messages to the syslinux >> mailing lists and hpa plans on fixing the GPT MBR in the near future, so >> we have that part of the problem covered. For now, I guess we can just >> comment out the "if" that chooses between mbr.bin or gptmbr.bin so that >> the USB key would be only EFI or only MBR compatible until this is >> resolved. > > Given that we didn't previously copy over an MBR for the mactel case, > leaving the 'if' doesn't really seem to hurt anything. I get to EFI > grub with the gptmbr.bin present and then when it's fixed, maybe things > will magically just start to work. So based on that, I think I'm going > to push what you had to git and then we can have it more easily testable Good news - syslinux's gptmbr.bin is working fine. I was using the partition type UUID, not its unique UUID. With this correction, things work fine when booting with BIOS or EFI! I've attached a patch which re-adds the check for gptmbr.bin and if it's found, then the script will now automatically grab the partition's unique UUID and write a compatible MBR. It should work on all drives with an LBA size of 512 bytes. The patch also includes a minor fix: If --format is specified and the user has accepted the first warning by hitting , then it will automatically unmount all partitions on the device so that the parted commands don't fail. Stewart -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: livecd-iso-to-disk-efi.patch URL: From katzj at fedoraproject.org Tue Jan 27 02:52:19 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Tue, 27 Jan 2009 02:52:19 +0000 (UTC) Subject: [Fedora-livecd-list] tools/livecd-iso-to-disk.sh Message-ID: <20090127025219.935DCC024D@lists.fedorahosted.org> tools/livecd-iso-to-disk.sh | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) New commits: commit 90c15a1993e6356de4b0134bc018834a22ba6b59 Author: Stewart Adam Date: Mon Jan 26 17:50:44 2009 -0500 Using both EFI and MBR at once on Live USB images and other misc. fixes Good news - syslinux's gptmbr.bin is working fine. I was using the partition type UUID, not its unique UUID. With this correction, things work fine when booting with BIOS or EFI! I've attached a patch which re-adds the check for gptmbr.bin and if it's found, then the script will now automatically grab the partition's unique UUID and write a compatible MBR. It should work on all drives with an LBA size of 512 bytes. The patch also includes a minor fix: If --format is specified and the user has accepted the first warning by hitting , then it will automatically unmount all partitions on the device so that the parted commands don't fail. diff --git a/tools/livecd-iso-to-disk.sh b/tools/livecd-iso-to-disk.sh index d37a2e9..85dba7e 100755 --- a/tools/livecd-iso-to-disk.sh +++ b/tools/livecd-iso-to-disk.sh @@ -71,10 +71,15 @@ resetMBR() { # if mactel, we need to use the hybrid MBR if [ -n "$mactel" ];then if [ -f /usr/lib/syslinux/gptmbr.bin ]; then - cat /usr/lib/syslinux/gptmbr.bin > $device + gptmbr='/usr/lib/syslinux/gptmbr.bin' elif [ -f /usr/share/syslinux/gptmbr.bin ]; then - cat /usr/share/syslinux/gptmbr.bin > $device + gptmbr='/usr/share/syslinux/gptmbr.bin' + else + echo "Could not find gptmbr.bin (syslinux)" + exitclean fi + # our magic number is LBA-2, offset 16 - (512+512+16)/$bs + dd if=$device bs=16 skip=65 count=1 | cat $gptmbr - > $device else if [ -f /usr/lib/syslinux/mbr.bin ]; then cat /usr/lib/syslinux/mbr.bin > $device @@ -136,7 +141,7 @@ createGPTLayout() { echo "WARNING: THIS WILL DESTROY ANY DATA ON $device!!!" echo "Press Enter to continue or ctrl-c to abort" read - + umount ${device}? &> /dev/null /sbin/parted --script $device mklabel gpt partinfo=$(/sbin/parted --script -m $device "unit b print" |grep ^$device:) size=$(echo $partinfo |cut -d : -f 2 |sed -e 's/B$//') @@ -158,7 +163,7 @@ createMSDOSLayout() { echo "WARNING: THIS WILL DESTROY ANY DATA ON $device!!!" echo "Press Enter to continue or ctrl-c to abort" read - + umount ${device}? &> /dev/null /sbin/parted --script $device mklabel msdos partinfo=$(/sbin/parted --script -m $device "unit b print" |grep ^$device:) size=$(echo $partinfo |cut -d : -f 2 |sed -e 's/B$//') From katzj at redhat.com Tue Jan 27 02:52:40 2009 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 26 Jan 2009 21:52:40 -0500 Subject: [Fedora-livecd-list] [PATCH] Using both EFI and MBR at once on Live USB images and other misc. fixes In-Reply-To: <497E3E44.1050504@diffingo.com> References: <48F87E65.6040104@diffingo.com> <1224251419.13356.46.camel@aglarond.local> <48F8A696.8020601@diffingo.com> <4908E124.10603@diffingo.com> <1225327119.25818.2.camel@aglarond.local> <49090E7A.7090009@diffingo.com> <20090116210907.GC27731@redhat.com> <49723D49.7050602@diffingo.com> <20090119155540.GD32152@redhat.com> <497E3E44.1050504@diffingo.com> Message-ID: <20090127025239.GC22016@redhat.com> On Monday, January 26 2009, Stewart Adam said: > I've attached a patch which re-adds the check for gptmbr.bin and if it's > found, then the script will now automatically grab the partition's unique > UUID and write a compatible MBR. It should work on all drives with an LBA > size of 512 bytes. > > The patch also includes a minor fix: If --format is specified and the > user has accepted the first warning by hitting , then it will > automatically unmount all partitions on the device so that the parted > commands don't fail. Applied, thanks! Jeremy From maillist at diffingo.com Tue Jan 27 04:44:04 2009 From: maillist at diffingo.com (Stewart Adam) Date: Mon, 26 Jan 2009 23:44:04 -0500 Subject: [Fedora-livecd-list] [PATCH] Using both EFI and MBR at once on Live USB images and other misc. fixes In-Reply-To: <20090127025239.GC22016@redhat.com> References: <48F87E65.6040104@diffingo.com> <1224251419.13356.46.camel@aglarond.local> <48F8A696.8020601@diffingo.com> <4908E124.10603@diffingo.com> <1225327119.25818.2.camel@aglarond.local> <49090E7A.7090009@diffingo.com> <20090116210907.GC27731@redhat.com> <49723D49.7050602@diffingo.com> <20090119155540.GD32152@redhat.com> <497E3E44.1050504@diffingo.com> <20090127025239.GC22016@redhat.com> Message-ID: <497E9114.1020506@diffingo.com> On 1/26/09 9:52 PM, Jeremy Katz wrote: > > Applied, thanks! > > Jeremy Thanks for commiting it so fast! I've been testing the two configurations all night, and funnily enough the gpt+mbr setup works better than the mbr setup alone on my home machine: If I don't specify --mactel, I can boot in QEMU fine but my machine (GA-965P-S3 mobo) refuses to boot it, saying that it can't find the kernel image for "linux". There's also a small bug that I forgot to account for in the last patch - $BOOTCONFIG is overwritten if --mactel is set, so the syslinux.cfg file is left in an inconsistent state with root=CDLABEL=<...> and rootfstype=iso9660. The attached patch fixes this problem by using $BOOTCONFIG and $BOOTCONFIG_EFI. Stewart -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: livecd-two-bootconfig.patch URL: From ftaylor at redhat.com Tue Jan 27 14:21:16 2009 From: ftaylor at redhat.com (Forrest Taylor) Date: Tue, 27 Jan 2009 09:21:16 -0500 Subject: [Fedora-livecd-list] Overlay File Health? In-Reply-To: <818ac3c70901140342k77488edci6b1b6d4bcb466ac7@mail.gmail.com> References: <818ac3c70901140342k77488edci6b1b6d4bcb466ac7@mail.gmail.com> Message-ID: <1233066076.11682.3.camel@papa> On Wed, 2009-01-14 at 06:42 -0500, Kam Salisbury wrote: > How do I see how much space is used in the overlay file (Fedora USB)? > > [liveuser at localhost ~]$ df -h > Filesystem Size Used Avail Use% Mounted on > /dev/mapper/live-rw 3.0G 2.2G 771M 75% / > tmpfs 1013M 288K 1013M 1% /dev/shm > /dev/sdb1 15G 8.3G 6.8G 55% /mnt/live > varcacheyum 1013M 0 1013M 0% /var/cache/yum > /tmp 1013M 104K 1013M 1% /tmp > vartmp 1013M 0 1013M 0% /var/tmp > > The above command output does not seem to reflect the 2GB overlay. > > Is there a way to output "just" the overlay contents? Something like 'du -hs' (du shows what /dev/mapper shows). Kam, I wrote a script to check the status of the overlay (attached). I'll see if I can get it included for future use. -- Forrest Taylor Global Learning Services Project Manager III Cell: 303-913-5169 AIM: forresttaylorred Red Hat IRC: forrest -------------- next part -------------- A non-text attachment was scrubbed... Name: check_overlay_size.sh Type: application/x-shellscript Size: 600 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From maillist at diffingo.com Tue Jan 27 14:45:16 2009 From: maillist at diffingo.com (Stewart Adam) Date: Tue, 27 Jan 2009 09:45:16 -0500 Subject: [Fedora-livecd-list] Overlay File Health? In-Reply-To: <1233066076.11682.3.camel@papa> References: <818ac3c70901140342k77488edci6b1b6d4bcb466ac7@mail.gmail.com> <1233066076.11682.3.camel@papa> Message-ID: <497F1DFC.3070100@diffingo.com> On 1/27/09 9:21 AM, Forrest Taylor wrote: > On Wed, 2009-01-14 at 06:42 -0500, Kam Salisbury wrote: >> How do I see how much space is used in the overlay file (Fedora USB)? >> >> [liveuser at localhost ~]$ df -h >> Filesystem Size Used Avail Use% Mounted on >> /dev/mapper/live-rw 3.0G 2.2G 771M 75% / >> tmpfs 1013M 288K 1013M 1% /dev/shm >> /dev/sdb1 15G 8.3G 6.8G 55% /mnt/live >> varcacheyum 1013M 0 1013M 0% /var/cache/yum >> /tmp 1013M 104K 1013M 1% /tmp >> vartmp 1013M 0 1013M 0% /var/tmp >> >> The above command output does not seem to reflect the 2GB overlay. >> >> Is there a way to output "just" the overlay contents? Something like 'du -hs' (du shows what /dev/mapper shows). > > Kam, > > I wrote a script to check the status of the overlay (attached). I'll > see if I can get it included for future use. Has anyone else had the overlay become corrupted when it gets full? I had this problem too... df -h said I had a bunch of free space so I installed lots of extra packages but then I got a error message saying "read only filesystem" I after that I couldn't run "rm" or even "ls". When I rebooted from the USB key again, it complained about logical buffer errors and I had to regenerate the overlay to fix it. Stewart From ftaylor at redhat.com Tue Jan 27 15:16:39 2009 From: ftaylor at redhat.com (Forrest Taylor) Date: Tue, 27 Jan 2009 10:16:39 -0500 Subject: [Fedora-livecd-list] Overlay File Health? In-Reply-To: <497F1DFC.3070100@diffingo.com> References: <818ac3c70901140342k77488edci6b1b6d4bcb466ac7@mail.gmail.com> <1233066076.11682.3.camel@papa> <497F1DFC.3070100@diffingo.com> Message-ID: <1233069399.11682.10.camel@papa> On Tue, 2009-01-27 at 09:45 -0500, Stewart Adam wrote: > On 1/27/09 9:21 AM, Forrest Taylor wrote: > > On Wed, 2009-01-14 at 06:42 -0500, Kam Salisbury wrote: > >> How do I see how much space is used in the overlay file (Fedora USB)? > >> > >> [liveuser at localhost ~]$ df -h > >> Filesystem Size Used Avail Use% Mounted on > >> /dev/mapper/live-rw 3.0G 2.2G 771M 75% / > >> tmpfs 1013M 288K 1013M 1% /dev/shm > >> /dev/sdb1 15G 8.3G 6.8G 55% /mnt/live > >> varcacheyum 1013M 0 1013M 0% /var/cache/yum > >> /tmp 1013M 104K 1013M 1% /tmp > >> vartmp 1013M 0 1013M 0% /var/tmp > >> > >> The above command output does not seem to reflect the 2GB overlay. > >> > >> Is there a way to output "just" the overlay contents? Something like 'du -hs' (du shows what /dev/mapper shows). > > > > Kam, > > > > I wrote a script to check the status of the overlay (attached). I'll > > see if I can get it included for future use. > Has anyone else had the overlay become corrupted when it gets full? I had > this problem too... df -h said I had a bunch of free space so I installed > lots of extra packages but then I got a error message saying "read only > filesystem" I after that I couldn't run "rm" or even "ls". When I rebooted > from the USB key again, it complained about logical buffer errors and I had > to regenerate the overlay to fix it. Yeah, that is what happens when you fill up the overlay. df really isn't a valid measure of the space that you can use. You should use a larger overlay if you want to use more disk space. I've been toying with the idea of using multiple overlay files (e.g., on FAT you cannot have files larger than 2GB), but it seems more work than it is worth at this time. BTW, instead of regenerating the overlay, you can clear it out by booting the LiveUSB using the reset_overlay kernel option. -- Forrest Taylor Global Learning Services Project Manager III Cell: 303-913-5169 AIM: forresttaylorred Red Hat IRC: forrest -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kam at kamsalisbury.com Tue Jan 27 22:00:00 2009 From: kam at kamsalisbury.com (Kam) Date: Tue, 27 Jan 2009 17:00:00 -0500 Subject: [Fedora-livecd-list] Overlay File Health? Message-ID: <497f8411.8602be0a.59d4.27f6@mx.google.com> -----Original Message----- From: Stewart Adam Subj: Re: [Fedora-livecd-list] Overlay File Health? Date: Tue Jan 27, 2009 9:45 am Size: 1K To: fedora-livecd-list at redhat.com On 1/27/09 9:21 AM, Forrest Taylor wrote: > On Wed, 2009-01-14 at 06:42 -0500, Kam Salisbury wrote: >> How do I see how much space is used in the overlay file (Fedora USB)? >> >> [liveuser at localhost ~]$ df -h >> Filesystem Size Used Avail Use% Mounted on >> /dev/mapper/live-rw 3.0G 2.2G 771M 75% / >> tmpfs 1013M 288K 1013M 1% /dev/shm >> /dev/sdb1 15G 8.3G 6.8G 55% /mnt/live >> varcacheyum 1013M 0 1013M 0% /var/cache/yum >> /tmp 1013M 104K 1013M 1% /tmp >> vartmp 1013M 0 1013M 0% /var/tmp >> >> The above command output does not seem to reflect the 2GB overlay. >> >> Is there a way to output "just" the overlay contents? Something like 'du -hs' (du shows what /dev/mapper shows). > > Kam, > > I wrote a script to check the status of the overlay (attached). I'll > see if I can get it included for future use. Has anyone else had the overlay become corrupted when it gets full? I had this problem too... df -h said I had a bunch of free space so I installed lots of extra packages but then I got a error message saying "read only filesystem" I after that I couldn't run "rm" or even "ls". When I rebooted from the USB key again, it complained about logical buffer errors and I had to regenerate the overlay to fix it. Stewart -- Fedora-livecd-list mailing list Fedora-livecd-list at redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list Hi Stewart, I am hoping to understand the issue enough to build a suitable application for montoring the overall overlay health including free space. Something simple such as green, yellow, red light in a task bar applet. -- Kam http://kamsalisbury.com GPG key: FAF1751E From herlo1 at gmail.com Wed Jan 28 07:21:08 2009 From: herlo1 at gmail.com (Clint Savage) Date: Wed, 28 Jan 2009 00:21:08 -0700 Subject: [Fedora-livecd-list] Building a Kiosk Live CD In-Reply-To: <4978A6F6.90006@redhat.com> References: <4978A6F6.90006@redhat.com> Message-ID: On Thu, Jan 22, 2009 at 10:03 AM, Daniel J Walsh wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Livecd is faking out SELinux to think that the machine is enable and > implements some /selinux interfaces to cause the rpms, to think they are > successful. > > When xguest tries to modify the booleans setting using setsebool, > setsebool not only modifies the on disk policy it also attempts to > change the running kernel. The /selinux/booleans interface was not > faked out, so setsebool blows up causing xguest to not be installed. > > I have built xguest-1.0.6-8.fc10 in koji which uses semanage rather then > setsebool to change the booleans. This should write the boolean > settings to disk, and should allow xguest to be installed in a livecd. > > I am setting up an environment to test this out. > > Dan So I was able to download the koji build of xguest tonight and attempt a build of the LiveCD with xguest again, the same error appears. Any luck on your side Dan? Cheers, Clint From katzj at fedoraproject.org Fri Jan 30 23:29:37 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Fri, 30 Jan 2009 23:29:37 +0000 (UTC) Subject: [Fedora-livecd-list] imgcreate/creator.py Message-ID: <20090130232937.2092612056D@lists.fedorahosted.org> imgcreate/creator.py | 33 +++++++++++++++++++-------------- 1 file changed, 19 insertions(+), 14 deletions(-) New commits: commit f216bd2505d7de33028b229d57ca34735e86452d Author: Daniel J Walsh Date: Fri Jan 30 16:55:15 2009 -0500 Support booleans These changes to livecd-tools are needed to allow a rpm that sets booleans (xguest) to install diff --git a/imgcreate/creator.py b/imgcreate/creator.py index 82db284..498f7e6 100644 --- a/imgcreate/creator.py +++ b/imgcreate/creator.py @@ -431,6 +431,13 @@ class ImageCreator(object): os.symlink(src, self._instroot + dest) os.umask(origumask) + def __getbooleans(self): + booleans = [] + for i in selinux.security_get_boolean_names()[1]: + on = selinux.security_get_boolean_active(i) + booleans.append(("/booleans/%s" % i, "%d %d" % (on, on))) + return booleans + def __create_selinuxfs(self): # if selinux exists on the host we need to lie to the chroot if os.path.exists("/selinux/enforce"): @@ -438,18 +445,18 @@ class ImageCreator(object): # enforce=0 tells the chroot selinux is not enforcing # policyvers=999 tell the chroot to make the highest version of policy it can - files = (('/enforce', '0'), - ('/policyvers', '999')) - for (file, value) in files: + + files = [('/enforce', '0'), + ('/policyvers', '999'), + ('/commit_pending_bools', ''), + ('/mls', str(selinux.is_selinux_mls_enabled()))] + + for (file, value) in files + self.__getbooleans(): fd = os.open(selinux_dir + file, os.O_WRONLY | os.O_TRUNC | os.O_CREAT) os.write(fd, value) os.close(fd) # we steal mls from the host system for now, might be best to always set it to 1???? - files = ("/mls",) - for file in files: - shutil.copyfile("/selinux" + file, selinux_dir + file) - # make /load -> /dev/null so chroot policy loads don't hurt anything os.mknod(selinux_dir + "/load", 0666 | stat.S_IFCHR, os.makedev(1, 3)) @@ -466,13 +473,11 @@ class ImageCreator(object): def __destroy_selinuxfs(self): # if the system was running selinux clean up our lies if os.path.exists("/selinux/enforce"): - files = ('/enforce', - '/policyvers', - '/mls', - '/load') - for file in files: + for root, dirs, files in os.walk(self._instroot + "/selinux"): + if root == self._instroot + "/selinux": + continue try: - os.unlink(self._instroot + "/selinux" + file) + os.unlink(root) except OSError: pass @@ -502,7 +507,7 @@ class ImageCreator(object): self._mount_instroot(base_on) - for d in ("/dev/pts", "/etc", "/boot", "/var/log", "/var/cache/yum", "/sys", "/proc", "/selinux"): + for d in ("/dev/pts", "/etc", "/boot", "/var/log", "/var/cache/yum", "/sys", "/proc", "/selinux/booleans"): makedirs(self._instroot + d) cachesrc = cachedir or (self.__builddir + "/yum-cache")