From kanarip at kanarip.com Sun Apr 1 00:02:24 2007 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Sun, 01 Apr 2007 02:02:24 +0200 Subject: [Fedora-livecd-list] Caching downloaded RPMs In-Reply-To: <003901c773b5$ac0741a0$0203a8c0@inspiron> References: <003901c773b5$ac0741a0$0203a8c0@inspiron> Message-ID: <460EF690.5070004@kanarip.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 J. Christopher Pereira Z. wrote: > Hi: > > 1) I'm building a LiveCD using a remote repository. > Everytime I restart the task, the packages are being redownloaded into > the temporal/mounted dir. > Is there any option for caching the downloaded packages? > > PS: I'm on FC6 building a FC7 live CD. > > 2) If there is no option or trick for caching, how can I download only > some packages (+ dependencies) into my local repository for building a > minimal LiveCD. > You can download the RPMs needed for the LiveCD once, and put them in a local, separate repo. Create the necessary repodata with createrepo. Kind regards, Jeroen van Meeuwen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFGDvaPKN6f2pNCvwgRAt4aAJ4h3j9oyRRUNLjV/HuQ3y4GDjWzowCdGaB3 BQVcO3DppjasDRv+r3pJK6U= =BcPh -----END PGP SIGNATURE----- From jdogalt at yahoo.com Mon Apr 2 01:08:39 2007 From: jdogalt at yahoo.com (Jane Dogalt) Date: Sun, 1 Apr 2007 18:08:39 -0700 (PDT) Subject: [Fedora-livecd-list] boot speed optomization (Qs for DZ mainly) Message-ID: <934623.50658.qm@web56905.mail.re3.yahoo.com> David, I just read the historic readahead post you referenced. I haven't really spent any effort thinking about massaging readahead into a boot speed optomization for a livecd (I'm guessing you have?). But it happens to be very similar to the 'early boot file seperation' methods I've described here relating to livecds. I have a couple questions about your 2004 post- " I've made the following observations 1. The kernel patch, linux-2.6.3-printopen.patch, wasn't really working well for me - it reported far to few files - instead I added a printk() to fs/namei.c:link_path_walk() (disclaimer: I don't know much about the kernel so there may be a better solution than this). " The method that I was planning on implementing, was to boot a livecd(-to-be) under qemu, then use file access times to construct a list of files that should be precached (same thing as readahead afaict). (And then by hand figure out files that are specific to the hardware platform, and make sure that their cousins get included in the list) What are your thoughts on this? Any quick reason why this wasn't used for readahead (I'm fairly ignorant of the internals of readahead). And do any of the reasons why it wasn't used for readahead apply to livecd optomization case? FYI- I see 2 obvious ways to do readahead in the livecd case. One, which I've outlined here before, would be to use unionfs, and seperate the filesystem images into "files that should be read ahead" and "the rest". Obviously unionfs, while it may eventually get into fedora, isn't the way to go. Its only a minor modifcation to do the same thing with devicemapper snapshots however. (i.e. you create the filesystem populating it with the files to be read-ahead, then you dm-snapshot it, and copy the rest of the files in. The resulting original fsimage(sparse ext3) along with the devicemapper snapshot device (damage/cow) image file, constitute the same effective thing as above with unionfs. Thus all your early read-ahead files, go in a single file/track on your cd/dvd, reducing seek times. Additionally, you can just read the read-ahead section into ram in one big chunk. (that would waste some ram, however with md-mirror tricks, you can work around that) Another minor question- " b. ext3 should support operations for moving blocks around; e.g. optimize around the readahead fileset - when idle the system should rearrange the files to facilitate faster booting " Has anything happened with that in the last 3 years? Sounds like a decent idea, that might be adaptable to the livecd boot optomization case. Final question: Have you had any other ideas on how livecd boot speed might be improved? -dmc/jdog ____________________________________________________________________________________ 8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie showtime shortcut. http://tools.search.yahoo.com/shortcuts/#news From jasperhartline at adelphia.net Mon Apr 2 03:03:04 2007 From: jasperhartline at adelphia.net (Jasper Hartline) Date: Sun, 01 Apr 2007 22:03:04 -0500 Subject: [Fedora-livecd-list] boot speed optomization (Qs for DZ mainly) In-Reply-To: <934623.50658.qm@web56905.mail.re3.yahoo.com> References: <934623.50658.qm@web56905.mail.re3.yahoo.com> Message-ID: <46107268.6020103@adelphia.net> Jane Dogalt wrote: > Final question: Have you had any other ideas on how livecd boot speed > might be improved? > > -dmc/jdog > I'm not sure if Pilgrim is implementing this or not, but prelinking the installed data directory before squashing it and making the ISO image is what we do with Kadischi built images. This allows the binary files and such to be pre-prelinked and thus will result in some faster booting times perhaps only a minor improvement, but is nevertheless a good idea. J. Hartline From davidz at redhat.com Mon Apr 2 04:29:26 2007 From: davidz at redhat.com (David Zeuthen) Date: Mon, 02 Apr 2007 00:29:26 -0400 Subject: [Fedora-livecd-list] [patch 06/20] Cleanup unmount() and teardown() In-Reply-To: <20070327142838.238236885@redhat.com>> References: <20070327141438.698373065@redhat.com> > <20070327142838.238236885@redhat.com>> Message-ID: <1175488166.3008.212.camel@zelda.fubar.dk> On Tue, 2007-03-27 at 15:14 +0100, Mark McLoughlin wrote: > - # TODO: need to handle when unmount fails because of lingering > - # processes that has open files > + self.bindmounts.reverse() > + for b in self.bindmounts: > + b.umount() > + Is the idea here that an exception is thrown all the way up to the user if unmount fails because some process in the chroot have open files? I guess that's fine; long term I'm hoping we can slay them somehow.. it does happens from time to time since that packages inevitably do a 'service foo restart' instead of 'service foo condrestart'... David From davidz at redhat.com Mon Apr 2 04:34:17 2007 From: davidz at redhat.com (David Zeuthen) Date: Mon, 02 Apr 2007 00:34:17 -0400 Subject: [Fedora-livecd-list] [patch 09/20] Consolidate bindmounts creation In-Reply-To: <20070327142839.124389042@redhat.com>> References: <20070327141438.698373065@redhat.com> > <20070327142839.124389042@redhat.com>> Message-ID: <1175488457.3008.215.camel@zelda.fubar.dk> On Tue, 2007-03-27 at 15:14 +0100, Mark McLoughlin wrote: > plain text document attachment (livecd-bindmounts-consolidation.patch) > No reason why the /var/cache/yum bindmount shouldn't be > created in the same loop as the rest of the bindmounts Yeah; mostly historical from when I wrote the original pilgrim code; it took me a while to figure out why we ran out of space. I guess this is fine although it's a bit weird to see /var/cache/yum along with the "special directories" that we normally bindmount to /. David From davidz at redhat.com Mon Apr 2 04:51:12 2007 From: davidz at redhat.com (David Zeuthen) Date: Mon, 02 Apr 2007 00:51:12 -0400 Subject: [Fedora-livecd-list] [patch 00/20] Fix error handling and misc. cleanups In-Reply-To: <20070327141438.698373065@redhat.com>> References: <20070327141438.698373065@redhat.com>> Message-ID: <1175489472.3008.227.camel@zelda.fubar.dk> Hey Mark, Sorry for the lag - been busy trying to get a new HAL release out, On Tue, 2007-03-27 at 15:14 +0100, Mark McLoughlin wrote: > Hi, > Apologies for spamming the list with 20 mails, but hopefully > it'll make it easier to review the patches. Yeah, it did make it easier although I'm always slighty scared when seeing a bunch of patches ;-) - would you happen to have a git repo handy that I can pull from? > The background to this is that I was suprised to see that > livecd-creator had rather poor error handling (e.g. not unmounting > stuff after certain errors, obscure error messages etc.) since > I thought that was the main reason to re-write pilgrim in python :-) > > It's understandable, though. Because Python has exceptions, > it's easy to be fooled into thinking you have error conditions > under control, but in reality, exceptions probably makes it easier > to screw up error handling. > > So, here's an attempt to fix it based on the following > guidelines: > > - don't intercept an exception if you can't do something useful > with it. Corollary: intercept an exception if you can do something > useful with it. > > - anticipate user errors or user-fixable system errors in a user > friendly manner. Corollary: allow other types of exceptions > to be passed to the toplevel. > > - i.e. there are 3 types of errors/exceptions, and 3 different > strategies for handling them: > > 1) errors which we can handle ourselves without ever telling > the user - e.g. a directory which we wish to create already > exists > > 2) user errors, or predictable system errors, which we > should do our best to help the user out with - e.g. > a busted kickstart file or running out of loop devices > > 3) pathological system errors or programmer errors, all > of which can be just allowed to propogate up to the > toplevel where an ugly traceback will be printed - > e.g creating a dir under the temporary build dir > fails or an unmount fails because we didn't close > the rpmdb > > - whatever the error, we should do our best to clean up files, > directories, mounts, etc. which we created > > - bear in mind that e.g. Ctrl-C can happen at any time > > Also, I've cleanup up various parts of the code as I > worked on the error handling. Those patches come first. This is really good stuff, thanks a bunch for working on it. I just read through all the patches and from a cursory look they look good to me; tomorrow I'm going to try and actually apply them to the code [1]. I'd also like for Jeremy to sign them off as he was the last one before you to fix up my, uh, rough bash->python conversion of the pilgrim shell script plus he's the main guy working on this stuff these days. Thanks again, Cheers, David [1] : As a practical thing would you happen to have a git repo stashed somewhere that I can pull form? From davidz at redhat.com Mon Apr 2 05:33:23 2007 From: davidz at redhat.com (David Zeuthen) Date: Mon, 02 Apr 2007 01:33:23 -0400 Subject: [Fedora-livecd-list] boot speed optomization (Qs for DZ mainly) In-Reply-To: <934623.50658.qm@web56905.mail.re3.yahoo.com> References: <934623.50658.qm@web56905.mail.re3.yahoo.com> Message-ID: <1175492003.3008.265.camel@zelda.fubar.dk> Hey, On Sun, 2007-04-01 at 18:08 -0700, Jane Dogalt wrote: > David, > > I just read the historic readahead post you referenced. I haven't > really spent any effort thinking about massaging readahead into a boot > speed optomization for a livecd (I'm guessing you have?). > > But it happens to be very similar to the 'early boot file seperation' > methods I've described here relating to livecds. Yea, there's a bunch of similarities between livecd's and real systems; typically they share at least optimizations... > I have a couple > questions about your 2004 post- > > " > I've made the following observations > > 1. The kernel patch, linux-2.6.3-printopen.patch, wasn't really working > well for me - it reported far to few files - instead I added a > printk() to fs/namei.c:link_path_walk() > (disclaimer: I don't know much about the kernel so there may be a > better solution than this). > " > > The method that I was planning on implementing, was to boot a > livecd(-to-be) under qemu, then use file access times to construct a > list of files that should be precached (same thing as readahead > afaict). > (And then by hand figure out files that are specific to the hardware > platform, and make sure that their cousins get included in the list) > > What are your thoughts on this? I think it's the right approach - I wouldn't limit it to livecd fwiw; one thing that's been discussed in various forums is to build/ship a set of SystemTap scripts along with each kernel + tweak /etc/rc.sysinit and/or the initramfs such that it recognizes an option "boot_profile" or something. The result would be that a SystemTap script would run and hook into e.g. sys_open() and record (access_time, filename). For nice UI polish, you could ship a small UI program that docks in the notification area and upon login gives you a notification +------------------------------------------------+ | Your system is being profiled. Click the "Stop | | Profiling" button to analyze the results. | | [Stop Profiling] | +------------------------------------------------+ and then you would get a nice chart a'la http://bootchart.org/images/bootchart.sortreadahead.png and also a file you can feed into readahead. > Any quick reason why this wasn't used > for readahead (I'm fairly ignorant of the internals of readahead). > > And do any of the reasons why it wasn't used for readahead apply to > livecd optomization case? I think it's simply because the readahead RPM always contained an out-of-date list of files - it's a bit hard, for example with firefox, the files move around with every release (try "rpm -ql firefox"). Plus readahead itself wasn't really that clever... >From what I gather from Karel Zak (current readahead maintainer) is that he have fixed readahead to use the directory, /etc/readahead.d, I think, that applications can drop files into. I also recall a thread where he wanted to use the audit subsystem rather than SystemTap scripts to e.g. intercept sys_open(). I guess both would work. Personally, fwiw, I think it's a dead end to have a list of files provided by packages; it needs to be generated when significant changes are made to the OS; e.g. when packages are installed/removed/updated as well as on system install time (e.g. the first time you boot into the installed OS) and, by extension, at livecd creation time. > FYI- I see 2 obvious ways to do readahead in the livecd case. One, > which I've outlined here before, would be to use unionfs, and seperate > the filesystem images into "files that should be read ahead" and "the > rest". Obviously unionfs, while it may eventually get into fedora, > isn't the way to go. Agreed. > Its only a minor modifcation to do the same thing with devicemapper > snapshots however. (i.e. you create the filesystem populating it with > the files to be read-ahead, then you dm-snapshot it, and copy the rest > of the files in. The resulting original fsimage(sparse ext3) along > with the devicemapper snapshot device (damage/cow) image file, > constitute the same effective thing as above with unionfs. > > Thus all your early read-ahead files, go in a single file/track on your > cd/dvd, reducing seek times. > > Additionally, you can just read the read-ahead section into ram in one > big chunk. (that would waste some ram, however with md-mirror tricks, > you can work around that) That's an interesting idea but notably this wouldn't help on an installed system since they way we install is dd'ing the ext3 file system. And it would be very nice to have this on the installed system as well (although over time it would deteriorate as packages are updated). Especially as it might motivate people to adopt this for mainline Fedora. Anyway, specifically for live cd, you may also get away with the hack I mentioned in my 2004 post; e.g. once you have an ext3 image + list of readahead files (that you get from profiling via qemu/kvm), just create a new ext3 image and first copy all the readahead files and then the rest. I would be happy to take a patch to livecd-tools that does exactly this. (Beware of symlinks btw! E.g. surely all files in /etc/init.d/* will be in the list but you need to create /etc/rc.d/init.d and /etc/init.d -> rc.d/init.d before copying those.) In fact, I think my recommendation would be to try the 2004 copy hack - you would probably need to hookup bootchart to get tangible results + comparisons. I found it to be very useful. It would be awesome if the presence of the bootchart RPM on the live cd system automatically gave you two extra entries in syslinux ("profile livecd" and "profile livecd [run from RAM]") along with all the fancy-schmancy UI dialogs to get the bootchart + list of readahead files. > Another minor question- > > " > b. ext3 should support operations for moving blocks around; e.g. > optimize around the readahead fileset - when idle the system should > rearrange the files to facilitate faster booting > " > > Has anything happened with that in the last 3 years? Sounds like a > decent idea, that might be adaptable to the livecd boot optomization > case. Sadly, no, not that I know of. I know Jens Axboe did some interesting work with fcache http://lkml.org/lkml/2006/5/15/46 but I don't think it applies to live cd as it duplicates a bunch of stuff. I don't think there's any way to avoid an ext3 defrag API... > Final question: Have you had any other ideas on how livecd boot speed > might be improved? Yeah. I do. But you're not going to like it :-) We simply need to do _less work_. We simply run way too many shell scripts, programs and daemons at start up. For example... there's absolutely no reason to start bluetooth daemons if you don't have BT hardware (am working with the Bluez folks on starting Bluez from HAL), there's no reason to start cups until you need to print (printer discovery needs to be in the desktop session _anyway_ / delayed until you actually need it), there's no reason to have a HP printer / scanner daemon... there's no reason to start _four_ SELinux daemons.. there's no reason to write system daemons using bloated frameworks like Python (am sure lots of people will flame me for that)... and the list goes on. Most, if not all, of this is fixable.. it's just a lot of hard work. Hope this helps, David From markmc at redhat.com Mon Apr 2 10:21:00 2007 From: markmc at redhat.com (Mark McLoughlin) Date: Mon, 02 Apr 2007 11:21:00 +0100 Subject: [Fedora-livecd-list] [patch 00/20] Fix error handling and misc. cleanups In-Reply-To: <1175489472.3008.227.camel@zelda.fubar.dk> References: <20070327141438.698373065@redhat.com> > <1175489472.3008.227.camel@zelda.fubar.dk> Message-ID: <1175509260.3430.17.camel@blaa> Hi David, On Mon, 2007-04-02 at 00:51 -0400, David Zeuthen wrote: > [1] : As a practical thing would you happen to have a git repo stashed > somewhere that I can pull form? This git business is pretty new to me, but I created a markmc branch, pushed the patches from quilt into git, ran git-update-server-info and rsync-ed .git to here: http://www.gnome.org/~markmc/livecd-markmc.git Probably a silly way of doing it, but it should suffice. Cheers, Mark. From markmc at redhat.com Mon Apr 2 10:36:25 2007 From: markmc at redhat.com (Mark McLoughlin) Date: Mon, 02 Apr 2007 11:36:25 +0100 Subject: [Fedora-livecd-list] [patch 06/20] Cleanup unmount() and teardown() In-Reply-To: <1175488166.3008.212.camel@zelda.fubar.dk> References: <20070327141438.698373065@redhat.com> > <20070327142838.238236885@redhat.com> > <1175488166.3008.212.camel@zelda.fubar.dk> Message-ID: <1175510185.3430.28.camel@blaa> On Mon, 2007-04-02 at 00:29 -0400, David Zeuthen wrote: > On Tue, 2007-03-27 at 15:14 +0100, Mark McLoughlin wrote: > > - # TODO: need to handle when unmount fails because of lingering > > - # processes that has open files > > + self.bindmounts.reverse() > > + for b in self.bindmounts: > > + b.umount() > > + > > Is the idea here that an exception is thrown all the way up to the user > if unmount fails because some process in the chroot have open files? In this case, given the choice between returning a nice error to the user and letting an exception propagate back up to the toplevel, I'd go with the latter. This is a programming error in that the tool has sucked and there's nothing the user can do to help. So, returning a nice error here might make us feel better, but doesn't help the user[1]. umount() doesn't even through an exception right now, though. It probably should. > I guess that's fine; long term I'm hoping we can slay them somehow.. it > does happens from time to time since that packages inevitably do a > 'service foo restart' instead of 'service foo condrestart'... Yep, that'd be the best way of handling it ... it's not just unmounting the bind mount that could fail because of this, though. The process could just as easily have files open in /usr. Cheers, Mark. [1] - Um, I'm not trying to lecture here btw ... I'm just trying to get my own head around what's a good error handling strategy when coding with exceptions :-) From katzj at redhat.com Mon Apr 2 14:29:25 2007 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 02 Apr 2007 10:29:25 -0400 Subject: [Fedora-livecd-list] boot speed optomization (Qs for DZ mainly) In-Reply-To: <46107268.6020103@adelphia.net> References: <934623.50658.qm@web56905.mail.re3.yahoo.com> <46107268.6020103@adelphia.net> Message-ID: <1175524165.7819.14.camel@erebor.boston.redhat.com> On Sun, 2007-04-01 at 22:03 -0500, Jasper Hartline wrote: > Jane Dogalt wrote: > > Final question: Have you had any other ideas on how livecd boot speed > > might be improved? > > > I'm not sure if Pilgrim is implementing this or not, but prelinking the > installed data directory > before squashing it and making the ISO image is what we do with Kadischi > built images. > This allows the binary files and such to be pre-prelinked and thus will > result in some faster booting times perhaps > only a minor improvement, but is nevertheless a good idea. Heh, I actually threw together the quick and dirty patch to do just this on Friday evening. Was planning on testing it today before sending it on :-) Jeremy From katzj at redhat.com Mon Apr 2 19:03:47 2007 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 2 Apr 2007 15:03:47 -0400 Subject: [Fedora-livecd-list] [PATCH] Add support for prelinking the system Message-ID: <11755406271453-git-send-email-katzj@redhat.com> prelink the system after packages are installed. This should lead to some speed-ups at runtime. Allow skipping prelink by passing --no-prelink --- creator/livecd-creator | 16 +++++++++++++++- 1 files changed, 15 insertions(+), 1 deletions(-) diff --git a/creator/livecd-creator b/creator/livecd-creator index c7232e0..84a8f67 100755 --- a/creator/livecd-creator +++ b/creator/livecd-creator @@ -601,6 +601,14 @@ class InstallationTarget: preexec_fn=self.run_in_root) return True + def prelinkSystem(self): + # prelink the system + instroot = "%s/install_root" %(self.build_dir,) + if os.path.exists("%s/usr/sbin/prelink" %(instroot,)): + subprocess.call(["/usr/sbin/prelink", "-mRavN"], + preexec_fn=self.run_in_root) + return True + def launchShell(self): print "Launching shell. Exit to continue." print "----------------------------------" @@ -737,6 +745,7 @@ def main(): base_on = None kscfg = None skip_compression = False + skip_prelink = False uncompressed_size = 3072 give_shell = False @@ -745,7 +754,7 @@ def main(): ["help", "repo=", "base-on=", "package=", "exclude-package=", "fslabel=", "config=", "skip-compression", "uncompressed-size=", - "shell"]) + "shell", "no-prelink"]) except getopt.GetoptError: usage() sys.exit(2) @@ -761,6 +770,9 @@ def main(): if o in ("-s", "--skip-compression"): skip_compression = True continue + if o in ("--no-prelink",): + skip_prelink = True + continue if o in ("-u", "--uncompressed-size"): uncompressed_size = int(a) continue @@ -842,6 +854,8 @@ def main(): sys.exit(1) target.configureSystem(ksparser) target.createInitramfs() + if not skip_prelink: + target.prelinkSystem() if ksparser.handler.selinux.selinux: target.relabelSystem() target.configureBootloader() -- 1.5.0.5 From davidz at redhat.com Mon Apr 2 19:35:39 2007 From: davidz at redhat.com (David Zeuthen) Date: Mon, 02 Apr 2007 15:35:39 -0400 Subject: [Fedora-livecd-list] [PATCH] Add support for prelinking the system In-Reply-To: <11755406271453-git-send-email-katzj@redhat.com> References: <11755406271453-git-send-email-katzj@redhat.com> Message-ID: <1175542539.2751.39.camel@zelda.fubar.dk> On Mon, 2007-04-02 at 15:03 -0400, Jeremy Katz wrote: > prelink the system after packages are installed. This should lead to some > speed-ups at runtime. Allow skipping prelink by passing --no-prelink Looks good to me but we should probably get Mark's patches in before committing it (I suppose it would require major rework). OK? David From katzj at redhat.com Mon Apr 2 19:52:18 2007 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 02 Apr 2007 15:52:18 -0400 Subject: [Fedora-livecd-list] [PATCH] Add support for prelinking the system In-Reply-To: <1175542539.2751.39.camel@zelda.fubar.dk> References: <11755406271453-git-send-email-katzj@redhat.com> <1175542539.2751.39.camel@zelda.fubar.dk> Message-ID: <1175543539.7819.33.camel@erebor.boston.redhat.com> On Mon, 2007-04-02 at 15:35 -0400, David Zeuthen wrote: > On Mon, 2007-04-02 at 15:03 -0400, Jeremy Katz wrote: > > prelink the system after packages are installed. This should lead to some > > speed-ups at runtime. Allow skipping prelink by passing --no-prelink > > Looks good to me but we should probably get Mark's patches in before > committing it (I suppose it would require major rework). OK? Yeah. And it shouldn't be too bad to adjust given that it's a pretty trivial change Jeremy From katzj at redhat.com Mon Apr 2 21:50:55 2007 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 02 Apr 2007 17:50:55 -0400 Subject: [Fedora-livecd-list] [patch 00/20] Fix error handling and misc. cleanups In-Reply-To: <1175489472.3008.227.camel@zelda.fubar.dk> References: <20070327141438.698373065@redhat.com> > <1175489472.3008.227.camel@zelda.fubar.dk> Message-ID: <1175550655.7819.44.camel@erebor.boston.redhat.com> On Mon, 2007-04-02 at 00:51 -0400, David Zeuthen wrote: > This is really good stuff, thanks a bunch for working on it. I just read > through all the patches and from a cursory look they look good to me; > tomorrow I'm going to try and actually apply them to the code [1]. > > I'd also like for Jeremy to sign them off as he was the last one before > you to fix up my, uh, rough bash->python conversion of the pilgrim shell > script plus he's the main guy working on this stuff these days. Looks good to me. I merged it all and pushed to the master. If anyone notices problems, holler. On a barely related note -- would it be interesting to set up commit spam to the list? I don't know that we have enough commits for it to be overwhelming and it could definitely be useful. Jeremy From jasperhartline at adelphia.net Mon Apr 2 23:41:55 2007 From: jasperhartline at adelphia.net (Jasper Hartline) Date: Mon, 02 Apr 2007 18:41:55 -0500 Subject: [Fedora-livecd-list] [patch 00/20] Fix error handling and misc. cleanups In-Reply-To: <1175550655.7819.44.camel@erebor.boston.redhat.com> References: <20070327141438.698373065@redhat.com> > <1175489472.3008.227.camel@zelda.fubar.dk> <1175550655.7819.44.camel@erebor.boston.redhat.com> Message-ID: <461194C3.7050901@adelphia.net> Jeremy Katz wrote: > On a barely related note -- would it be interesting to set up commit > spam to the list? I don't know that we have enough commits for it to be > overwhelming and it could definitely be useful. > > Jeremy > That would be a good idea. J. Hartline From alexm at asic.udl.cat Tue Apr 3 10:55:10 2007 From: alexm at asic.udl.cat (=?ISO-8859-1?Q?Alexandre_Magaz_Gra=E7a?=) Date: Tue, 03 Apr 2007 12:55:10 +0200 Subject: [Fedora-livecd-list] bindmounts not mounted Message-ID: <4612328E.6030005@asic.udl.cat> Hi, I've been trying to build a live cd with the last pilgrim version (git) and it seems that bindmounts doesn't get mounted. This is the output I get at the package installing stage: [...] Installing: gnome-panel ##################### [426/620] /proc is empty (not mounted ?) Installing: rpm ##################### [427/620] Installing: gnome-python2-gconf ##################### [428/620] Installing: gnome-python2-desktop ##################### [429/620] Installing: tomcat5-servlet-2.4-api ##################### [430/620] GC Warning: Couldn't read /proc/stat GC Warning: GC_get_nprocs() returned -1 dirname: missing operand [...] This patch solved the problem: diff --git a/creator/livecd-creator b/creator/livecd-creator index 9a00946..7eac113 100755 --- a/creator/livecd-creator +++ b/creator/livecd-creator @@ -409,6 +409,9 @@ class InstallationTarget: (self.build_dir + "/yum-cache", "/var/cache/yum")]: self.bindmounts.append(BindChrootMount(f, self.build_dir + "/install_root", dest)) + for b in self.bindmounts: + b.mount() + # make sure /etc/mtab is current inside install_root os.symlink("../proc/mounts", self.build_dir + "/install_root/etc/mtab") Cheers, Alex From markmc at redhat.com Tue Apr 3 11:07:02 2007 From: markmc at redhat.com (Mark McLoughlin) Date: Tue, 03 Apr 2007 12:07:02 +0100 Subject: [Fedora-livecd-list] bindmounts not mounted In-Reply-To: <4612328E.6030005@asic.udl.cat> References: <4612328E.6030005@asic.udl.cat> Message-ID: <1175598422.3402.11.camel@blaa> Hi Alexandre, On Tue, 2007-04-03 at 12:55 +0200, Alexandre Magaz Gra?a wrote: > Hi, > I've been trying to build a live cd with the last pilgrim version (git) > and it seems that bindmounts doesn't get mounted. This is the output I > get at the package installing stage: Strange I didn't see this problem in my testing but ... > > diff --git a/creator/livecd-creator b/creator/livecd-creator > index 9a00946..7eac113 100755 > --- a/creator/livecd-creator > +++ b/creator/livecd-creator > @@ -409,6 +409,9 @@ class InstallationTarget: > (self.build_dir + "/yum-cache", > "/var/cache/yum")]: > self.bindmounts.append(BindChrootMount(f, self.build_dir + > "/install_root", dest)) > > + for b in self.bindmounts: > + b.mount() > + ... you're absolutely right, we need this ... I managed to drop the actual mount() call ... Thanks, Mark. From ml at deadbabylon.de Tue Apr 3 12:16:02 2007 From: ml at deadbabylon.de (Sebastian Vahl) Date: Tue, 3 Apr 2007 14:16:02 +0200 Subject: [Fedora-livecd-list] liveinst/anaconda crashes after setting root password Message-ID: <20070403141602.0e4cf8ea@localhost.localdomain> Hi. An actual spin of kde-livecd crashes after setting root password. Log is attached. Versions: - anaconda-11.2.0.42-1 (inserted " --interface org.freedesktop.Hal.Device.Storage" manually in /usr/sbin/liveinst) - livecd-creator from git (checkout from today and patched to mount bindmounts) Wanted to post this here first before creating a bug. Am I missing something or is this really a bug that should be filled? Sebastian -------------- next part -------------- A non-text attachment was scrubbed... Name: liveinst.error Type: application/octet-stream Size: 27541 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From fedora at leemhuis.info Tue Apr 3 13:03:20 2007 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Tue, 03 Apr 2007 15:03:20 +0200 Subject: [Fedora-livecd-list] Space savings discussed on fedora-packaging-list Message-ID: <46125098.80601@leemhuis.info> Hi, below discussion from Fedora Packaging FYI, in case the space saving discussed there are of interest for you. Original thread starts at: https://www.redhat.com/archives/fedora-packaging/2007-April/msg00003.html CU thl ------- Original-Nachricht -------- Betreff: [Fedora-packaging] Hardlinking *.pyc and *.pyo Datum: Tue, 3 Apr 2007 13:42:24 +0300 Von: Ville Skytt? Antwort an: Discussion of RPM packaging standards and practices for Fedora Extras An: fedora-packaging Mailing List Hello, Related to recent space saving discussions, I came across PLD's rpm-build-macros package recently, and found that they hardlink identical *.pyc and *.pyo. In a lot of cases, they're the same, and there's some potential for saving some MB "for free", on my FC6 x86_64 box: $ /usr/sbin/hardlink -ncv /usr/lib*/python2.4 2>&1 | tail -n 1 Would save 11116544 The PLD implementation looks like this: # Hardlink binary identical .pyc and .pyo files # (idea by glen pld-linux org) %__spec_install_post_py_hardlink {\ %{!?no_install_post_py_hardlink: __spec_install_post_py_hardlink() { \ [ ! -d "$RPM_BUILD_ROOT" ] || find "$RPM_BUILD_ROOT" -name '*.pyc' | while read a; do \ b="$(echo $a|sed -e 's/.pyc$/.pyo/')"; \ if cmp -s "$a" "$b"; then \ ln -f "$a" "$b"; \ fi; \ done \ }; __spec_install_post_py_hardlink } } The use of "cmp" would require diffutils installed. Or the above could be converted to use hardlink instead (which would have to be made sure to be around) or maybe sha1sum (in coreutils, pretty much always around in buildroots). I suppose something like the above could be easily added to redhat-rpm-config or rpm, eg. embedded in brp-python-bytecompile or run after it in %__os_install_post. Worth it? Other comments? -------- Original-Nachricht -------- Return-Path: X-Original-To: rpmbuild at localhost Delivered-To: rpmbuild at localhost.thl.home Received: by truhe.thl.home (Postfix, from userid 500) id 67F1B8110; Tue, 3 Apr 2007 13:24:27 +0200 (CEST) X-Original-To: thl at localhost Delivered-To: thl at localhost.thl.home Received: from truhe.thl.home (localhost [127.0.0.1]) by truhe.thl.home (Postfix) with ESMTP id 510D280AD for ; Tue, 3 Apr 2007 13:24:27 +0200 (CEST) X-Original-To: fedora at leemhuis.info Delivered-To: web550p1 at basicbox7.server-home.net Received: from leemhuis.info [195.137.212.29] by truhe.thl.home with POP3 (fetchmail-6.3.6) for (single-drop); Tue, 03 Apr 2007 13:24:27 +0200 (CEST) Received: from hormel.redhat.com (hormel.redhat.com [209.132.177.30]) by basicbox7.server-home.net (Postfix) with ESMTP id 1B0C63741D9 for ; Tue, 3 Apr 2007 13:17:29 +0200 (CEST) Received: from listman.util.phx.redhat.com (listman.util.phx.redhat.com [10.8.4.110]) by hormel.redhat.com (Postfix) with ESMTP id B188E72E40; Tue, 3 Apr 2007 07:17:30 -0400 (EDT) Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by listman.util.phx.redhat.com (8.13.1/8.13.1) with ESMTP id l33BHSHq025579 for ; Tue, 3 Apr 2007 07:17:28 -0400 Received: from mx1.redhat.com (mx1.redhat.com [172.16.48.31]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l33BHSBL023395 for ; Tue, 3 Apr 2007 07:17:28 -0400 Received: from TZMXR01.htp-tel.de (tzmxr01.htp-tel.de [81.14.243.17]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l33BHM8I029053 for ; Tue, 3 Apr 2007 07:17:23 -0400 Received: from TZMXR01.htp-tel.de (localhost [127.0.0.1]) by TZMXR01.htp-tel.de with ESMTP id l33BHGYK029546 for ; Tue, 3 Apr 2007 13:17:16 +0200 (CEST) Received: from truhe.thl.home (a81-14-184-169.net-htp.de [81.14.184.169]) by TZMXR01.htp-tel.de with ESMTP id l33BHF0E029531 for ; Tue, 3 Apr 2007 13:17:16 +0200 (CEST) Received: from thl.ct.heise.de (localhost [127.0.0.1]) by truhe.thl.home (Postfix) with ESMTP id 70DC580AD for ; Tue, 3 Apr 2007 13:17:15 +0200 (CEST) Message-ID: <461237BB.5050700 at leemhuis.info> Date: Tue, 03 Apr 2007 13:17:15 +0200 From: Thorsten Leemhuis User-Agent: Thunderbird 2.0b2 (X11/20070308) MIME-Version: 1.0 To: Discussion of RPM packaging standards and practices for Fedora Extras Subject: Re: [Fedora-packaging] Hardlinking *.pyc and *.pyo References: <200704031342.25238.ville.skytta at iki.fi> In-Reply-To: <200704031342.25238.ville.skytta at iki.fi> X-Enigmail-Version: 0.94.3.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-RedHat-Spam-Score: 0 X-loop: fedora-packaging at redhat.com X-BeenThere: fedora-packaging at redhat.com X-Mailman-Version: 2.1.5 Precedence: junk Reply-To: Discussion of RPM packaging standards and practices for Fedora Extras List-Id: Discussion of RPM packaging standards and practices for Fedora Extras List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: fedora-packaging-bounces at redhat.com Errors-To: fedora-packaging-bounces at redhat.com X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on basicbox7.server-home.net X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=AWL autolearn=disabled version=3.0.3 X-UIDL: dg:!!WW-!!BIp"!23Y"! On 03.04.2007 12:42, Ville Skytt? wrote: > Worth it? Other comments? Hehe, sounds interesting. Did you tell the Live-CD guys about it? I'd say they will probably very interested in something like this (they could run hardlink directly for now until we decide what we want to do). CU thl -------- Original-Nachricht -------- Return-Path: X-Original-To: rpmbuild at localhost Delivered-To: rpmbuild at localhost.thl.home Received: by truhe.thl.home (Postfix, from userid 500) id DB9EB8110; Tue, 3 Apr 2007 13:54:57 +0200 (CEST) X-Original-To: thl at localhost Delivered-To: thl at localhost.thl.home Received: from truhe.thl.home (localhost [127.0.0.1]) by truhe.thl.home (Postfix) with ESMTP id C928480AD for ; Tue, 3 Apr 2007 13:54:57 +0200 (CEST) X-Original-To: fedora at leemhuis.info Delivered-To: web550p1 at basicbox7.server-home.net Received: from leemhuis.info [195.137.212.29] by truhe.thl.home with POP3 (fetchmail-6.3.6) for (single-drop); Tue, 03 Apr 2007 13:54:57 +0200 (CEST) Received: from hormel.redhat.com (hormel.redhat.com [209.132.177.30]) by basicbox7.server-home.net (Postfix) with ESMTP id 1EF8C374D37 for ; Tue, 3 Apr 2007 13:45:41 +0200 (CEST) Received: from listman.util.phx.redhat.com (listman.util.phx.redhat.com [10.8.4.110]) by hormel.redhat.com (Postfix) with ESMTP id AAF3D73009; Tue, 3 Apr 2007 07:45:42 -0400 (EDT) Received: from int-mx2.corp.redhat.com (nat-pool.util.phx.redhat.com [10.8.5.200]) by listman.util.phx.redhat.com (8.13.1/8.13.1) with ESMTP id l33Bjfnb029939 for ; Tue, 3 Apr 2007 07:45:41 -0400 Received: from mx2.redhat.com (mx2.redhat.com [10.255.15.25]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l33Bje9H030402 for ; Tue, 3 Apr 2007 07:45:40 -0400 Received: from smtp5.pp.htv.fi (smtp5.pp.htv.fi [213.243.153.39]) by mx2.redhat.com (8.13.1/8.13.1) with ESMTP id l33BjcSD019557 for ; Tue, 3 Apr 2007 07:45:39 -0400 Received: from viper.localdomain (cs181043142.pp.htv.fi [82.181.43.142]) by smtp5.pp.htv.fi (Postfix) with ESMTP id B4D425BC1E9 for ; Tue, 3 Apr 2007 14:45:37 +0300 (EEST) From: Ville Skytt? To: Discussion of RPM packaging standards and practices for Fedora Extras Subject: Re: [Fedora-packaging] Hardlinking *.pyc and *.pyo Date: Tue, 3 Apr 2007 14:45:37 +0300 User-Agent: KMail/1.9.6 References: <200704031342.25238.ville.skytta at iki.fi> <461237BB.5050700 at leemhuis.info> In-Reply-To: <461237BB.5050700 at leemhuis.info> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Message-Id: <200704031445.37318.ville.skytta at iki.fi> X-RedHat-Spam-Score: 0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by listman.util.phx.redhat.com id l33Bjfnb029939 X-loop: fedora-packaging at redhat.com X-BeenThere: fedora-packaging at redhat.com X-Mailman-Version: 2.1.5 Precedence: junk Reply-To: Discussion of RPM packaging standards and practices for Fedora Extras List-Id: Discussion of RPM packaging standards and practices for Fedora Extras List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: fedora-packaging-bounces at redhat.com Errors-To: fedora-packaging-bounces at redhat.com X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on basicbox7.server-home.net X-Spam-Level: X-Spam-Status: No, score=-0.3 required=5.0 tests=AWL autolearn=disabled version=3.0.3 X-UIDL: GSK"!`f=!!:Wi"!p1+"! On Tuesday 03 April 2007, Thorsten Leemhuis wrote: > On 03.04.2007 12:42, Ville Skytt? wrote: > > Worth it? Other comments? > > Hehe, sounds interesting. Did you tell the Live-CD guys about it? I'd > say they will probably very interested in something like this (they > could run hardlink directly for now until we decide what we want to do). Nope, just brought it up in last week's packaging meeting and now posted here. Feel free to forward. Another thing they could be interested in (again on my FC6 x86_64): $ /usr/sbin/hardlink -ncv /usr/share/doc 2>&1 | tail -n 1 Would save 6692864 (of which COPYING's share is about 3.2M) -------- Original-Nachricht -------- Return-Path: X-Original-To: rpmbuild at localhost Delivered-To: rpmbuild at localhost.thl.home Received: by truhe.thl.home (Postfix, from userid 500) id EF7088117; Tue, 3 Apr 2007 14:05:05 +0200 (CEST) X-Original-To: thl at localhost Delivered-To: thl at localhost.thl.home Received: from truhe.thl.home (localhost [127.0.0.1]) by truhe.thl.home (Postfix) with ESMTP id D99CE80DE for ; Tue, 3 Apr 2007 14:05:05 +0200 (CEST) X-Original-To: fedora at leemhuis.info Delivered-To: web550p1 at basicbox7.server-home.net Received: from leemhuis.info [195.137.212.29] by truhe.thl.home with POP3 (fetchmail-6.3.6) for (single-drop); Tue, 03 Apr 2007 14:05:05 +0200 (CEST) Received: from hormel.redhat.com (hormel.redhat.com [209.132.177.30]) by basicbox7.server-home.net (Postfix) with ESMTP id BE818374D4B for ; Tue, 3 Apr 2007 14:01:32 +0200 (CEST) Received: from listman.util.phx.redhat.com (listman.util.phx.redhat.com [10.8.4.110]) by hormel.redhat.com (Postfix) with ESMTP id 93CE072FB4; Tue, 3 Apr 2007 08:01:33 -0400 (EDT) Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by listman.util.phx.redhat.com (8.13.1/8.13.1) with ESMTP id l33C1VoW032671 for ; Tue, 3 Apr 2007 08:01:32 -0400 Received: from mx1.redhat.com (mx1.redhat.com [172.16.48.31]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l33C1UEY004042 for ; Tue, 3 Apr 2007 08:01:30 -0400 Received: from junior.physik.fu-berlin.de (IDENT:U2FsdGVkX184gQ/KwtoT7+xBQgH3zjb63w3ZGzlWGD4 at junior.physik.fu-berlin.de [130.133.35.30]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l33C1RN5026158 for ; Tue, 3 Apr 2007 08:01:27 -0400 Received: from neu-vpn.physik.fu-berlin.de ([160.45.32.209] helo=neu.nirvana) by mail2.atrpms.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.66) id 1HYhhE-0001uV-06; Tue, 03 Apr 2007 14:01:25 +0200 Received: from thimm by neu.nirvana with local (Exim 4.66) (envelope-from ) id 1HYhhC-0001x3-TQ; Tue, 03 Apr 2007 14:01:06 +0200 Date: Tue, 3 Apr 2007 14:01:06 +0200 From: Axel Thimm To: Discussion of RPM packaging standards and practices for Fedora Extras Message-ID: <20070403120106.GD29856 at neu.nirvana> References: <200704031342.25238.ville.skytta at iki.fi> MIME-Version: 1.0 In-Reply-To: <200704031342.25238.ville.skytta at iki.fi> User-Agent: Mutt/1.5.13 (2006-08-11) X-Scanned: No viruses found. X-Scan-Signature: fe522d7d72b3ce68d16a3279c0f8f490 X-RedHat-Spam-Score: 0 X-loop: fedora-packaging at redhat.com Subject: [Fedora-packaging] Re: Hardlinking *.pyc and *.pyo X-BeenThere: fedora-packaging at redhat.com X-Mailman-Version: 2.1.5 Precedence: junk Reply-To: Discussion of RPM packaging standards and practices for Fedora Extras List-Id: Discussion of RPM packaging standards and practices for Fedora Extras List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1626666452==" Sender: fedora-packaging-bounces at redhat.com Errors-To: fedora-packaging-bounces at redhat.com X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on basicbox7.server-home.net X-Spam-Level: X-Spam-Status: No, score=-0.2 required=5.0 tests=AWL autolearn=disabled version=3.0.3 X-UIDL: ff="!/9`"!@MP!!34]!! On Tue, Apr 03, 2007 at 01:42:24PM +0300, Ville Skytt? wrote: > Related to recent space saving discussions, I came across PLD's > rpm-build-macros package recently, and found that they hardlink > identical *.pyc and *.pyo. In a lot of cases, they're the same, > and there's some potential for saving some MB "for free", > on my FC6 x86_64 box: > > $ /usr/sbin/hardlink -ncv /usr/lib*/python2.4 2>&1 | tail -n 1 > Would save 11116544 I get more than twice as much on a typical FC6/x86_64 system: 27275264. That's 26 MB on 166MB total, e.g. saving 16%. # du -sc /usr/lib*/python2.4| tail -n 1 170200 total On another system I get 21MB of 144MB total, e.g about 15%. > The PLD implementation looks like this: > > # Hardlink binary identical .pyc and .pyo files > # (idea by glen pld-linux org) > %__spec_install_post_py_hardlink {\ > %{!?no_install_post_py_hardlink: __spec_install_post_py_hardlink() { \ > [ ! -d "$RPM_BUILD_ROOT" ] || find "$RPM_BUILD_ROOT" -name '*.pyc' | while read a; do \ > b="$(echo $a|sed -e 's/.pyc$/.pyo/')"; \ > if cmp -s "$a" "$b"; then \ > ln -f "$a" "$b"; \ > fi; \ > done \ > }; __spec_install_post_py_hardlink } } > > The use of "cmp" would require diffutils installed. Or the above > could be converted to use hardlink instead (which would have to be made > sure to be around) or maybe sha1sum (in coreutils, pretty much always > around in buildroots). > > I suppose something like the above could be easily added to > redhat-rpm-config or rpm, eg. embedded in brp-python-bytecompile > or run after it in %__os_install_post. brp-python-bytecompile sounds like the best spot since the pyc/pyos are created there. Maybe we should ship an improved brp-python-bytecompile in redhat-rpm-config while lobbying rpm upstream to adopt it? > Worth it? Other comments? A 15% space gain (under python) w/o any drawbacks? Always worth it. :) From wwoods at redhat.com Tue Apr 3 15:30:47 2007 From: wwoods at redhat.com (Will Woods) Date: Tue, 03 Apr 2007 11:30:47 -0400 Subject: [Fedora-livecd-list] Live USB converter script In-Reply-To: <1174941185.3161.11.camel@aglarond.local> References: <1174941185.3161.11.camel@aglarond.local> Message-ID: <1175614247.6884.138.camel@metroid.rdu.redhat.com> On Mon, 2007-03-26 at 16:33 -0400, Jeremy Katz wrote: > A better choice is to take the live CD image and copy the bits from it > to your USB stick. The result is the attached script. Run it with > arguments of the live CD iso image and the device of your USB key and it > copies over the bits of the live CD onto your USB stick and makes it > bootable. Supported filesystems for your USB stick are vfat/msdos and > ext23. Just a note - the -d flag to syslinux doesn't exist in syslinux-3.11 (i.e. doesn't work in FC6). The script should maybe check for that. Something like: if ! syslinux 2>&1 | grep -qe -d; then echo "Your syslinux is too old for this." exit 1 fi > What do people think? It seems to work from some quick testing and it's > impressive just how much faster it is going from a USB stick. The only thing keeping this from being face-meltingly awesome is the lack of persistent storage. Well, that and I can't get it to boot from my USB key: "Missing operating system" every time. Maybe it doesn't like vfat? I'll try ext3 and see what happens. -w -------------- 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 rstrode at redhat.com Tue Apr 3 15:41:25 2007 From: rstrode at redhat.com (Ray Strode) Date: Tue, 03 Apr 2007 11:41:25 -0400 Subject: [Fedora-livecd-list] Live USB converter script In-Reply-To: <1175614247.6884.138.camel@metroid.rdu.redhat.com> References: <1174941185.3161.11.camel@aglarond.local> <1175614247.6884.138.camel@metroid.rdu.redhat.com> Message-ID: <1175614885.10864.0.camel@halflap.boston.devel.redhat.com> Hi, > Well, that and I can't get it to boot from > my USB key: "Missing operating system" every time. Maybe it doesn't like > vfat? I'll try ext3 and see what happens. You might have to run fdisk on the device and make the partition bootable. --Ray From tim.wood at datawranglers.com Tue Apr 3 15:45:22 2007 From: tim.wood at datawranglers.com (Tim Wood) Date: Tue, 3 Apr 2007 09:45:22 -0600 Subject: [Fedora-livecd-list] Live USB converter script In-Reply-To: <1175614247.6884.138.camel@metroid.rdu.redhat.com> References: <1174941185.3161.11.camel@aglarond.local> <1175614247.6884.138.camel@metroid.rdu.redhat.com> Message-ID: Knoppix has a way of doing this. I've played with it... essentially the boot code looks a specific config file on each device ... putting the image with the LiveCD last. As soon as it finds one, it looks in their for the path to several things such as the home directory, network config files, menu config files, etc. Missing Operating System... grub (or is it lilo this time) sounds like its toast. FWIW... Tim Wood On Apr 3, 2007, at 9:30 AM, Will Woods wrote: > The only thing keeping this from being face-meltingly awesome is the > lack of persistent storage. Well, that and I can't get it to boot from > my USB key: "Missing operating system" every time. Maybe it doesn't > like > vfat? I'll try ext3 and see what happens. > > -w From tim.wood at datawranglers.com Tue Apr 3 15:46:24 2007 From: tim.wood at datawranglers.com (Tim Wood) Date: Tue, 3 Apr 2007 09:46:24 -0600 Subject: [Fedora-livecd-list] Try Ray's trick first In-Reply-To: <1175614885.10864.0.camel@halflap.boston.devel.redhat.com> References: <1174941185.3161.11.camel@aglarond.local> <1175614247.6884.138.camel@metroid.rdu.redhat.com> <1175614885.10864.0.camel@halflap.boston.devel.redhat.com> Message-ID: <900F2820-BC3D-4378-8B82-9EEACDD2DBDE@datawranglers.com> Stupid me... that's the usual cause. Try Ray's suggestion before mine. On Apr 3, 2007, at 9:41 AM, Ray Strode wrote: > You might have to run fdisk on the device and make the partition > bootable. From katzj at redhat.com Tue Apr 3 15:56:04 2007 From: katzj at redhat.com (Jeremy Katz) Date: Tue, 03 Apr 2007 11:56:04 -0400 Subject: [Fedora-livecd-list] Live USB converter script In-Reply-To: <1175614247.6884.138.camel@metroid.rdu.redhat.com> References: <1174941185.3161.11.camel@aglarond.local> <1175614247.6884.138.camel@metroid.rdu.redhat.com> Message-ID: <1175615764.3746.9.camel@aglarond.local> On Tue, 2007-04-03 at 11:30 -0400, Will Woods wrote: > On Mon, 2007-03-26 at 16:33 -0400, Jeremy Katz wrote: > > A better choice is to take the live CD image and copy the bits from it > > to your USB stick. The result is the attached script. Run it with > > arguments of the live CD iso image and the device of your USB key and it > > copies over the bits of the live CD onto your USB stick and makes it > > bootable. Supported filesystems for your USB stick are vfat/msdos and > > ext23. > > Just a note - the -d flag to syslinux doesn't exist in syslinux-3.11 > (i.e. doesn't work in FC6). The script should maybe check for that. > Something like: > > if ! syslinux 2>&1 | grep -qe -d; then > echo "Your syslinux is too old for this." > exit 1 > fi I don't know how common of a use case grabbing the script off of a web site/git directly instead of using the package is, though. > > What do people think? It seems to work from some quick testing and it's > > impressive just how much faster it is going from a USB stick. > > The only thing keeping this from being face-meltingly awesome is the > lack of persistent storage. Well, that and I can't get it to boot from > my USB key: "Missing operating system" every time. Maybe it doesn't like > vfat? I'll try ext3 and see what happens. vfat should be fine. Making sure the partition is bootable is definitely needed. I filed a bug about that yesterday so that I don't forget to add something to at least try to check. Jeremy From wwoods at redhat.com Tue Apr 3 16:03:30 2007 From: wwoods at redhat.com (Will Woods) Date: Tue, 03 Apr 2007 12:03:30 -0400 Subject: [Fedora-livecd-list] Live USB converter script In-Reply-To: <1175614885.10864.0.camel@halflap.boston.devel.redhat.com> References: <1174941185.3161.11.camel@aglarond.local> <1175614247.6884.138.camel@metroid.rdu.redhat.com> <1175614885.10864.0.camel@halflap.boston.devel.redhat.com> Message-ID: <1175616210.6884.145.camel@metroid.rdu.redhat.com> On Tue, 2007-04-03 at 11:41 -0400, Ray Strode wrote: > You might have to run fdisk on the device and make the partition > bootable. I used gparted, and it said the partition was marked bootable. fdisk confirmed that, but it said the partition boundaries were odd. So I repartitioned with fdisk, and now I get: "Boot error" Which is, at least, a different failure message. Maybe I just have a sketchy key. -w -------------- 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 Tue Apr 3 16:27:22 2007 From: katzj at redhat.com (Jeremy Katz) Date: Tue, 03 Apr 2007 12:27:22 -0400 Subject: [Fedora-livecd-list] bindmounts not mounted In-Reply-To: <1175598422.3402.11.camel@blaa> References: <4612328E.6030005@asic.udl.cat> <1175598422.3402.11.camel@blaa> Message-ID: <1175617642.3746.11.camel@aglarond.local> On Tue, 2007-04-03 at 12:07 +0100, Mark McLoughlin wrote: > On Tue, 2007-04-03 at 12:55 +0200, Alexandre Magaz Gra?a wrote: > > Hi, > > I've been trying to build a live cd with the last pilgrim version (git) > > and it seems that bindmounts doesn't get mounted. This is the output I > > get at the package installing stage: > > Strange I didn't see this problem in my testing but ... And I didn't either. Pushed the fix Thanks, Jeremy From fedora at leemhuis.info Tue Apr 3 16:29:57 2007 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Tue, 03 Apr 2007 18:29:57 +0200 Subject: [Fedora-livecd-list] Live USB converter script In-Reply-To: <1175616210.6884.145.camel@metroid.rdu.redhat.com> References: <1174941185.3161.11.camel@aglarond.local> <1175614247.6884.138.camel@metroid.rdu.redhat.com> <1175614885.10864.0.camel@halflap.boston.devel.redhat.com> <1175616210.6884.145.camel@metroid.rdu.redhat.com> Message-ID: <46128105.6050300@leemhuis.info> Will Woods schrieb: > On Tue, 2007-04-03 at 11:41 -0400, Ray Strode wrote: > >> You might have to run fdisk on the device and make the partition >> bootable. > I used gparted, and it said the partition was marked bootable. fdisk > confirmed that, but it said the partition boundaries were odd. So I > repartitioned with fdisk, and now I get: "Boot error" > > Which is, at least, a different failure message. > > Maybe I just have a sketchy key. Do you have a proper MBR on the stick that jumps to the bootsector of the active partition (that where syslinux is installed as far as I can see from this discussion)? CU thl From katzj at redhat.com Tue Apr 3 17:16:11 2007 From: katzj at redhat.com (Jeremy Katz) Date: Tue, 03 Apr 2007 13:16:11 -0400 Subject: [Fedora-livecd-list] liveinst/anaconda crashes after setting root password In-Reply-To: <20070403141602.0e4cf8ea@localhost.localdomain> References: <20070403141602.0e4cf8ea@localhost.localdomain> Message-ID: <1175620571.3746.15.camel@aglarond.local> On Tue, 2007-04-03 at 14:16 +0200, Sebastian Vahl wrote: > Wanted to post this here first before creating a bug. Am I missing > something or is this really a bug that should be filled? We fixed this yesterday, but then just never got around to building anaconda. Sorry about that :/ Jeremy From katzj at redhat.com Tue Apr 3 17:16:46 2007 From: katzj at redhat.com (Jeremy Katz) Date: Tue, 03 Apr 2007 13:16:46 -0400 Subject: [Fedora-livecd-list] Space savings discussed on fedora-packaging-list In-Reply-To: <46125098.80601@leemhuis.info> References: <46125098.80601@leemhuis.info> Message-ID: <1175620606.3746.17.camel@aglarond.local> On Tue, 2007-04-03 at 15:03 +0200, Thorsten Leemhuis wrote: > below discussion from Fedora Packaging FYI, in case the space saving > discussed there are of interest for you. While I think this is interesting, instead of adding hacks in the livecd-creator, I think I'd rather get the changes just in the packages. It's a bit more maintainable that way, even if it means that we can't take advantage of it until F8 Jeremy From katzj at redhat.com Tue Apr 3 17:20:25 2007 From: katzj at redhat.com (Jeremy Katz) Date: Tue, 03 Apr 2007 13:20:25 -0400 Subject: [Fedora-livecd-list] Live USB converter script In-Reply-To: <46128105.6050300@leemhuis.info> References: <1174941185.3161.11.camel@aglarond.local> <1175614247.6884.138.camel@metroid.rdu.redhat.com> <1175614885.10864.0.camel@halflap.boston.devel.redhat.com> <1175616210.6884.145.camel@metroid.rdu.redhat.com> <46128105.6050300@leemhuis.info> Message-ID: <1175620825.3746.21.camel@aglarond.local> On Tue, 2007-04-03 at 18:29 +0200, Thorsten Leemhuis wrote: > Will Woods schrieb: > > On Tue, 2007-04-03 at 11:41 -0400, Ray Strode wrote: > >> You might have to run fdisk on the device and make the partition > >> bootable. > > I used gparted, and it said the partition was marked bootable. fdisk > > confirmed that, but it said the partition boundaries were odd. So I > > repartitioned with fdisk, and now I get: "Boot error" > > > > Which is, at least, a different failure message. > > > > Maybe I just have a sketchy key. > > Do you have a proper MBR on the stick that jumps to the bootsector of > the active partition (that where syslinux is installed as far as I can > see from this discussion)? It did. I think this a sketchy BIOS. Will was going to try a BIOS update now. FWIW, a good way to check if the USB key is bootable is to install qemu adn then run: qemu -hda /path/to/usb/stick -m 256 -std-vga If that comes up to the boot screen, then the stick _should_ be bootable modulo BIOS problems. It's a nice, quick and easy way to ensure some basic sanity Jeremy From ml at deadbabylon.de Tue Apr 3 18:34:21 2007 From: ml at deadbabylon.de (Sebastian Vahl) Date: Tue, 3 Apr 2007 20:34:21 +0200 Subject: [Fedora-livecd-list] liveinst/anaconda crashes after setting root password In-Reply-To: <1175620571.3746.15.camel@aglarond.local> References: <20070403141602.0e4cf8ea@localhost.localdomain> <1175620571.3746.15.camel@aglarond.local> Message-ID: <20070403203421.57d58a10@localhost.localdomain> Am Tue, 03 Apr 2007 13:16:11 -0400 schrieb Jeremy Katz : > On Tue, 2007-04-03 at 14:16 +0200, Sebastian Vahl wrote: > > Wanted to post this here first before creating a bug. Am I missing > > something or is this really a bug that should be filled? > > We fixed this yesterday, but then just never got around to building > anaconda. Sorry about that :/ Ah, ok. When it is fixed it's good enough. :) Sebastian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From lmacken at redhat.com Tue Apr 3 20:11:24 2007 From: lmacken at redhat.com (Luke Macken) Date: Tue, 3 Apr 2007 16:11:24 -0400 Subject: [Fedora-livecd-list] Live USB converter script In-Reply-To: <1175620825.3746.21.camel@aglarond.local> References: <1174941185.3161.11.camel@aglarond.local> <1175614247.6884.138.camel@metroid.rdu.redhat.com> <1175614885.10864.0.camel@halflap.boston.devel.redhat.com> <1175616210.6884.145.camel@metroid.rdu.redhat.com> <46128105.6050300@leemhuis.info> <1175620825.3746.21.camel@aglarond.local> Message-ID: <20070403201124.GB29144@tomservo.rh.rit.edu> On Tue, Apr 03, 2007 at 01:20:25PM -0400, Jeremy Katz wrote: > On Tue, 2007-04-03 at 18:29 +0200, Thorsten Leemhuis wrote: > > Will Woods schrieb: > > > On Tue, 2007-04-03 at 11:41 -0400, Ray Strode wrote: > > >> You might have to run fdisk on the device and make the partition > > >> bootable. > > > I used gparted, and it said the partition was marked bootable. fdisk > > > confirmed that, but it said the partition boundaries were odd. So I > > > repartitioned with fdisk, and now I get: "Boot error" > > > > > > Which is, at least, a different failure message. > > > > > > Maybe I just have a sketchy key. > > > > Do you have a proper MBR on the stick that jumps to the bootsector of > > the active partition (that where syslinux is installed as far as I can > > see from this discussion)? > > It did. I think this a sketchy BIOS. Will was going to try a BIOS > update now. > > FWIW, a good way to check if the USB key is bootable is to install qemu > adn then run: > qemu -hda /path/to/usb/stick -m 256 -std-vga > > If that comes up to the boot screen, then the stick _should_ be bootable > modulo BIOS problems. It's a nice, quick and easy way to ensure some > basic sanity I am able to run the livecd on my USB stick using qemu, but I get the 'Boot error' message when trying to boot straight up with my T43. I just tried to update my bios and such, but that completely failed and told me to contact my support :( luke From fedora at leemhuis.info Wed Apr 4 05:09:23 2007 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Wed, 04 Apr 2007 07:09:23 +0200 Subject: [Fedora-livecd-list] Live USB converter script In-Reply-To: <20070403201124.GB29144@tomservo.rh.rit.edu> References: <1174941185.3161.11.camel@aglarond.local> <1175614247.6884.138.camel@metroid.rdu.redhat.com> <1175614885.10864.0.camel@halflap.boston.devel.redhat.com> <1175616210.6884.145.camel@metroid.rdu.redhat.com> <46128105.6050300@leemhuis.info> <1175620825.3746.21.camel@aglarond.local> <20070403201124.GB29144@tomservo.rh.rit.edu> Message-ID: <46133303.8000708@leemhuis.info> On 03.04.2007 22:11, Luke Macken wrote: > On Tue, Apr 03, 2007 at 01:20:25PM -0400, Jeremy Katz wrote: >> On Tue, 2007-04-03 at 18:29 +0200, Thorsten Leemhuis wrote: >>> Will Woods schrieb: >>>> On Tue, 2007-04-03 at 11:41 -0400, Ray Strode wrote: >>>>> You might have to run fdisk on the device and make the partition >>>>> bootable. >>>> I used gparted, and it said the partition was marked bootable. fdisk >>>> confirmed that, but it said the partition boundaries were odd. So I >>>> repartitioned with fdisk, and now I get: "Boot error" >>>> Which is, at least, a different failure message. >>>> Maybe I just have a sketchy key. >>> Do you have a proper MBR on the stick that jumps to the bootsector of >>> the active partition (that where syslinux is installed as far as I can >>> see from this discussion)? >> It did. I think this a sketchy BIOS. Will was going to try a BIOS >> update now. >> FWIW, a good way to check if the USB key is bootable is to install qemu >> adn then run: >> qemu -hda /path/to/usb/stick -m 256 -std-vga >> If that comes up to the boot screen, then the stick _should_ be bootable >> modulo BIOS problems. It's a nice, quick and easy way to ensure some >> basic sanity > I am able to run the livecd on my USB stick using qemu, but I get the > 'Boot error' message when trying to boot straight up with my T43. I > just tried to update my bios and such, but that completely failed and > told me to contact my support :( Another wild guess from someone that didn't try the live-USB stuff yet: There are some systems around that boot only with a superfloppy-like Stick (e.g. one without MBR and thus without partition table -- e.g. where one big "partition" that holds all the data) while others run only if the stick has an MBR on it. CU thl From ml at deadbabylon.de Wed Apr 4 13:29:30 2007 From: ml at deadbabylon.de (Sebastian Vahl) Date: Wed, 4 Apr 2007 15:29:30 +0200 Subject: [Fedora-livecd-list] liveinst/anaconda crashes after setting root password In-Reply-To: <1175620571.3746.15.camel@aglarond.local> References: <20070403141602.0e4cf8ea@localhost.localdomain> <1175620571.3746.15.camel@aglarond.local> Message-ID: <20070404152930.5016e410@localhost.localdomain> Am Tue, 03 Apr 2007 13:16:11 -0400 schrieb Jeremy Katz : > On Tue, 2007-04-03 at 14:16 +0200, Sebastian Vahl wrote: > > Wanted to post this here first before creating a bug. Am I missing > > something or is this really a bug that should be filled? > > We fixed this yesterday, but then just never got around to building > anaconda. Sorry about that :/ > anaconda is working again (anaconda-11.2.0.44-1). And even the installation is bootable again! (#234728). Thanks! Sebastian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From jasperhartline at adelphia.net Wed Apr 4 14:16:33 2007 From: jasperhartline at adelphia.net (Jasper Hartline) Date: Wed, 04 Apr 2007 09:16:33 -0500 Subject: [Fedora-livecd-list] Kadischi: USB CDROM drives Message-ID: <4613B341.3030509@adelphia.net> Hello. I have just committed some changes to Kadischi's CVS tree which should rectify the issue with Kadischi built LiveCD media not booting properly on USB CDROM drives. I am asking that the people who are using Kadischi test the latest CVS tree and verify this works on your USB CDROM drives. If you encounter early bootstrap propblems and any kernel panics please report the errors if any and send to the list. This fix has been put off for quite some time for the fact I did not have a USB CDROM drive lying around to test with. It should be all good now, please test it and report your results. J. Hartline From katzj at redhat.com Wed Apr 4 15:25:10 2007 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 4 Apr 2007 11:25:10 -0400 Subject: [Fedora-livecd-list] [PATCH] Generalization for different ways of booting the live image Message-ID: <11757003102716-git-send-email-katzj@redhat.com> * Move to /dev/live instead of /dev/livecd to work with live USB sticks as well as live CDs. * Create /dev/live-osimg and /dev/live-squashed symlinks so that we can find the real os image block device more easily from the running live image * Copy squashfs.img when going from RAM to avoid #234881 --- creator/livecd-creator | 4 +- creator/mayflower | 77 ++++++++++++++++++++++++++++-------------------- 2 files changed, 47 insertions(+), 34 deletions(-) diff --git a/creator/livecd-creator b/creator/livecd-creator index fcf7cc3..5f5c91b 100755 --- a/creator/livecd-creator +++ b/creator/livecd-creator @@ -674,12 +674,12 @@ menu color hotkey 0 #ffffffff #ff000000 label linux menu label %(label)s kernel vmlinuz - append initrd=initrd.img ro quiet root=CDLABEL=%(label)s rootfstype=iso9660 livecd + append initrd=initrd.img ro quiet root=CDLABEL=%(label)s rootfstype=iso9660 liveimg label runfromram menu label %(label)s from RAM kernel vmlinuz - append initrd=initrd.img ro quiet root=CDLABEL=%(label)s rootfstype=iso9660 livecd livecd_ram + append initrd=initrd.img ro quiet root=CDLABEL=%(label)s rootfstype=iso9660 liveimg live_ram """ %{"label": self.fs_label, "background" : have_background} cfgf = open("%s/out/isolinux/isolinux.cfg" %(self.build_dir,), "w") diff --git a/creator/mayflower b/creator/mayflower index 212c672..f483e1e 100755 --- a/creator/mayflower +++ b/creator/mayflower @@ -234,8 +234,8 @@ rootfstype="" quiet=0 shell=0 eshell=0 -livecd_ram=0 -livecd_locale="" +live_ram=0 +live_locale="" # Parse kernel commandline options # @@ -259,11 +259,11 @@ for o in \`cat /proc/cmdline\` ; do eshell) eshell=1 ;; - livecd_ram) - livecd_ram=1 + live_ram) + live_ram=1 ;; - livecd_locale=*) - livecd_locale=\${o#livecd_locale=} + live_locale=*) + live_locale=\${o#live_locale=} ;; esac done @@ -536,19 +536,19 @@ else fi # live cd helper function -do_livecd_from_loop121() { +do_live_from_loop121() { # create a sparse file for the overlay dd if=/dev/null of=/overlay bs=1024 count=1 seek=$((512*1024)) 2> /dev/null losetup /dev/loop119 /overlay # set up the snapshot - echo 0 \`blockdev --getsize /dev/loop121\` snapshot /dev/loop121 /dev/loop119 p 8 | dmsetup create livecd-rw + echo 0 \`blockdev --getsize /dev/loop121\` snapshot /dev/loop121 /dev/loop119 p 8 | dmsetup create live-rw # set up new /dev/root symlink rm -f /dev/root - ln -s /dev/mapper/livecd-rw /dev/root + ln -s /dev/mapper/live-rw /dev/root - mount -n -t ext3 /dev/mapper/livecd-rw /sysroot + mount -n -t ext3 /dev/mapper/live-rw /sysroot # here you can modify the rw ext3 fs for testing if you don't want to # respin the entire rootfs (which takes ages). Example # @@ -557,24 +557,36 @@ do_livecd_from_loop121() { # We also use it to dynamically set the system locale from the boot # menu on live cd's. # - if [ "\$livecd_locale" != "" ] ; then - echo "LANG=\$livecd_locale" > /sysroot/etc/sysconfig/i18n + if [ "\$live_locale" != "" ] ; then + echo "LANG=\$live_locale" > /sysroot/etc/sysconfig/i18n fi - # create rule so udev creates /dev/livecd symlink on real rootfs - if [ "\$livecd_ram" == "1" ] ; then - echo "KERNEL==\"loop118\", SYMLINK+=\"livecd\"" >> /sysroot/etc/udev/rules.d/50-udev.rules - else - echo "KERNEL==\"hd[a-z]\", BUS==\"ide\", SYSFS{removable}==\"1\", ATTRS{media}==\"cdrom\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$CDLABEL\", SYMLINK+=\"livecd\"" >> /sysroot/etc/udev/rules.d/50-udev.rules - echo "KERNEL==\"sr[0-9]\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$CDLABEL\", SYMLINK+=\"livecd\"" >> /sysroot/etc/udev/rules.d/50-udev.rules - echo "KERNEL==\"scd[0-9]\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$CDLABEL\", SYMLINK+=\"livecd\"" >> /sysroot/etc/udev/rules.d/50-udev.rules - echo "KERNEL==\"pcd[0-9]\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$CDLABEL\", SYMLINK+=\"livecd\"" >> /sysroot/etc/udev/rules.d/50-udev.rules + # create rule so udev creates /dev/live symlink on real rootfs + if [ -n "\$CDLABEL" ]; then + echo "KERNEL==\"hd[a-z]\", BUS==\"ide\", SYSFS{removable}==\"1\", ATTRS{media}==\"cdrom\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$CDLABEL\", SYMLINK+=\"live\"" >> /sysroot/etc/udev/rules.d/50-udev.rules + echo "KERNEL==\"sr[0-9]\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$CDLABEL\", SYMLINK+=\"live\"" >> /sysroot/etc/udev/rules.d/50-udev.rules + echo "KERNEL==\"scd[0-9]\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$CDLABEL\", SYMLINK+=\"live\"" >> /sysroot/etc/udev/rules.d/50-udev.rules + echo "KERNEL==\"pcd[0-9]\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$CDLABEL\", SYMLINK+=\"live\"" >> /sysroot/etc/udev/rules.d/50-udev.rules + elif [ -n "\$LABEL" ]; then + echo "KERNEL==\"hd[a-z]\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$LABEL\", SYMLINK+=\"live\"" >> /sysroot/etc/udev/rules.d/50-udev.rules + echo "KERNEL==\"hd[a-z][0-9]*\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$LABEL\", SYMLINK+=\"live\"" >> /sysroot/etc/udev/rules.d/50-udev.rules + echo "KERNEL==\"sd[a-z]\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$LABEL\", SYMLINK+=\"live\"" >> /sysroot/etc/udev/rules.d/50-udev.rules + echo "KERNEL==\"sd[a-z][0-9]*\", PROGRAM=\"/lib/udev/vol_id -l %N\", RESULT==\"\$LABEL\", SYMLINK+=\"live\"" >> /sysroot/etc/udev/rules.d/50-udev.rules + elif [ -n "\$UUID" ]; then + echo "KERNEL==\"hd[a-z]\", PROGRAM=\"/lib/udev/vol_id -u %N\", RESULT==\"\$UUID\", SYMLINK+=\"live\"" >> /sysroot/etc/udev/rules.d/50-udev.rules + echo "KERNEL==\"hd[a-z][0-9]*\", PROGRAM=\"/lib/udev/vol_id -u %N\", RESULT==\"\$UUID\", SYMLINK+=\"live\"" >> /sysroot/etc/udev/rules.d/50-udev.rules + echo "KERNEL==\"sd[a-z]\", PROGRAM=\"/lib/udev/vol_id -u %N\", RESULT==\"\$UUID\", SYMLINK+=\"live\"" >> /sysroot/etc/udev/rules.d/50-udev.rules + echo "KERNEL==\"sd[a-z][0-9]*\", PROGRAM=\"/lib/udev/vol_id -u %N\", RESULT==\"\$UUID\", SYMLINK+=\"live\"" >> /sysroot/etc/udev/rules.d/50-udev.rules fi + # add rules for /dev/live-squashed and /dev/live-osimg + echo "KERNEL==\"loop120\" SYMLINK+=\"live-squashed\"" >> /sysroot/etc/udev/rules.d/50-udev.rules + echo "KERNEL==\"loop121\" SYMLINK+=\"live-osimg\"" >> /sysroot/etc/udev/rules.d/50-udev.rules + mount -n -o ro,remount /sysroot } -# we might have an uncompressed embedded ext3 to use as rootfs (uncompressed livecd) +# we might have an uncompressed embedded ext3 to use as rootfs (uncompressed live) # if [ -e /sysroot/LiveOS/ext3fs.img ]; then EXT3FS="/sysroot/LiveOS/ext3fs.img" @@ -599,10 +611,10 @@ if [ -n "\$EXT3FS" ] ; then losetup /dev/loop121 \$EXT3FS umount -l /sysroot - do_livecd_from_loop121 + do_live_from_loop121 fi -# we might have an embedded ext3 on squashfs to use as rootfs (compressed livecd) +# we might have an embedded ext3 on squashfs to use as rootfs (compressed live) # if [ -e /sysroot/LiveOS/squashfs.img ]; then SQUASHED="/sysroot/LiveOS/squashfs.img" @@ -625,15 +637,14 @@ if [ -n "\$SQUASHED" ] ; then modprobe loop max_loop=128 modprobe dm_snapshot - if [ "\$livecd_ram" == "1" ] ; then - echo "Copying livecd to RAM..." - echo "(this may take a few minutes. CD will be ejected upon completion.)" - dd if=/dev/root of=/livecd.iso bs=512 2> /dev/null + if [ "\$live_ram" == "1" ] ; then + echo "Copying live image to RAM..." + echo "(this may take a few minutes)" + dd if=\$SQUASHED of=/squashed.img bs=512 2> /dev/null umount -n /sysroot - echo "Done copying livecd to RAM." + echo "Done copying live image to RAM." eject -p /dev/root - losetup /dev/loop118 /livecd.iso - mount -n -t iso9660 /dev/loop118 /sysroot + SQUASHED="/squashed.img" fi losetup /dev/loop120 \$SQUASHED @@ -643,9 +654,11 @@ if [ -n "\$SQUASHED" ] ; then losetup /dev/loop121 /squashfs/os.img umount -l /squashfs - umount -l /sysroot + if [ "\$live_ram" == "0" ] ; then + umount -l /sysroot + fi - do_livecd_from_loop121 + do_live_from_loop121 fi if [ "\$eshell" == "1" ] ; then -- 1.5.0.6 From mspevack at redhat.com Wed Apr 4 15:46:07 2007 From: mspevack at redhat.com (Max Spevack) Date: Wed, 4 Apr 2007 11:46:07 -0400 (EDT) Subject: [Fedora-livecd-list] Test3 LiveCD QA issues Message-ID: I just spent about 90 minutes going through Test3, starting with the Gnome LiveCD and working my way through installation, firstboot, and login. I tried to relive my days as a QA engineer and adopt the mindset of a user who isn't deeply technical, and as a user who becomes uncomfortable at anything that doesn't seem to "just work" the way it's expected to. I have a number of suggestions and straight bugs. I don't have the time to open bugzillas for all of these. Most of this is LiveCD stuff, but some of it is general QA. Will -- I'm going to leave it up to you to file Bugzillas, etc. as appropriate. --Max ====================== Booting the LiveCD, grub gives you two options: Fedora-7-Test3-Live-i386 Fedora-7-Test3-Live-i386 from RAM This is confusing -- should I choose default or no? What's the difference between the two? I think users will be confused. ====================== The default user name at the Live CD's gdm -- this is a simple change s/Fedora live CD/Fedora/ then if it's a LiveUSB or LiveDVD, the user name doesn't look odd ====================== First impressions of the LiveCD desktop We want it to be uncluttered, and to show off the coolest stuff in the most obvious way. To that end: - do we need the SCIM module in the top right? - do we need the Desktop search module in the top right? What about the default applications at the top of the GNOME panel? - now: evolution, web browser Why not also add some useful/common apps: - instant messenger - the gimp - abiword ====================== Firefox - We need a default homepage for Firefox that isn't just the generic firefox page. - We need to update the default bookmarks for Firefox in F7. There's actually a wiki page where we're working on the list. http://fedoraproject.org/wiki/Releases/7/Bookmarks ====================== I tried every single application under "Applications", "Places", and "System". It was a disappointing experience. Has anyone else done this, both for the liveCD and/or for the actual installed distro? - abiword crashes on startup - "calendar" in the office section is actually Evolution and it crashes when you close it - "email" in the top launcher is also Evolution, and it too crashes (obviously) when you close it. - "tasks" in the office section -- same thing - so shouldn't it just have one more generalized name? - "Other->Theme Installer" doesn't do anything, and should be removed - CD Player takes a long time to boot, and then locks/crashes - "Places->Network" crashes when you close it and takes down the whole gnome panel, which restarts - "System->Administration->Logical Volume Manager" gives "unknown error" on startup. - "System->About Fedora" can't load properly due to missing about-fedora.xml ====================== Trying out the installer The "restart" button at the end of the anaconda/install window didn't work, and I had to manually restart the machine from Gnome's system menu. After rebooting..... "License Information" in Firstboot - Can we make the text box smaller, to better fit the text that is in it? - Either the "Forward" button should say "Understood, please proceed" or the place in the grey where it says "Understood, please proceed" should simply be gone. It looks dumb. "Hardware Profile" screen in Firstboot. Let's clean up the text. It's quite wordy, and contains incorrect capitalizations. "Smolt is a hardware profiler for the Fedora Project. Submitting your profile helps focus our efforts on pupular hardware and platforms. All submissions are anonymous." The last part "Sending your profile will enable a monthly update" -- I assume that means that if you send your profile *now* it will send an updated version of it every month. Is that right? Can the user disable that easily? I forgot to look, but we must make sure that the default choice is "do not send". From jkeating at redhat.com Wed Apr 4 15:57:57 2007 From: jkeating at redhat.com (Jesse Keating) Date: Wed, 4 Apr 2007 11:57:57 -0400 Subject: [Fedora-livecd-list] Test3 LiveCD QA issues In-Reply-To: References: Message-ID: <200704041157.57446.jkeating@redhat.com> On Wednesday 04 April 2007 11:46:07 Max Spevack wrote: > ====================== > > First impressions of the LiveCD desktop > > We want it to be uncluttered, and to show off the coolest stuff in the > most obvious way. ?To that end: > ????????- do we need the SCIM module in the top right? > ????????- do we need the Desktop search module in the top right? > > What about the default applications at the top of the GNOME panel? > ????????- now: evolution, web browser > > Why not also add some useful/common apps: > ? ? ?- instant messenger > ? ? ?- the gimp > ? ? ?- abiword We want the Live desktop to be the same as the installed Desktop. Therefor these types of thoughts need to go to the general desktop. We really really want the environment on Live to be as close if not the same as the installed system. > ====================== > > Firefox > > - We need a default homepage for Firefox that isn't just the generic > firefox page. The very first time you launch FF you get their screen, I don't know if there is a way around it. > - We need to update the default bookmarks for Firefox in F7. ?There's > actually a wiki page where we're working on the list. > ????????http://fedoraproject.org/wiki/Releases/7/Bookmarks There was a bug in FF that it wasn't loading the bookmarks right, I do believe that has been fixed in rawhide. It should show the release notes by default. -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From wwoods at redhat.com Wed Apr 4 16:08:18 2007 From: wwoods at redhat.com (Will Woods) Date: Wed, 04 Apr 2007 12:08:18 -0400 Subject: [Fedora-livecd-list] Test3 LiveCD QA issues In-Reply-To: References: Message-ID: <1175702898.6884.161.camel@metroid.rdu.redhat.com> On Wed, 2007-04-04 at 11:46 -0400, Max Spevack wrote: > Will -- I'm going to leave it up to you to file Bugzillas, etc. as > appropriate. Here's a quick once-over of the stuff you mentioned. I'll look at the rest in more detail, but here's what I know off the top of my head: > First impressions of the LiveCD desktop > > We want it to be uncluttered, and to show off the coolest stuff in the > most obvious way. To that end: > - do we need the SCIM module in the top right? > - do we need the Desktop search module in the top right? For that matter - shouldn't we pre-populate the image with index data if we're going to include Beagle? > - We need a default homepage for Firefox that isn't just the generic > firefox page. IIRC this is coming (as with the "Welcome to Fedora Core 6!" page) soon. Although I'm not sure if we have/want a LiveCD specific one. > I tried every single application under "Applications", "Places", and > "System". It was a disappointing experience. Has anyone else done this, > both for the liveCD and/or for the actual installed distro? > > - abiword crashes on startup Yep. https://bugzilla.redhat.com/234765 Added to the LiveCD tracker: https://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=Fedora7LiveCD > - "System->About Fedora" can't load properly due to missing > about-fedora.xml Again, I believe this is coming along with the bookmarks and Firefox start page.. Actually I thought we had a placeholder there now. Did it get dropped from the LiveCD? > Trying out the installer > > The "restart" button at the end of the anaconda/install window didn't > work, and I had to manually restart the machine from Gnome's system menu. That's a known bug: https://bugzilla.redhat.com/225168 It's on the F7 LiveCD tracker. > > "Smolt is a hardware profiler for the Fedora Project. Submitting your > profile helps focus our efforts on pupular hardware and platforms. All > submissions are anonymous." [...] > I forgot to look, but we must make sure that the default choice is "do not > send". It is. -w -------------- 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 mspevack at redhat.com Wed Apr 4 16:20:59 2007 From: mspevack at redhat.com (Max Spevack) Date: Wed, 4 Apr 2007 12:20:59 -0400 (EDT) Subject: [Fedora-livecd-list] Test3 LiveCD QA issues In-Reply-To: References: Message-ID: On Wed, 4 Apr 2007, Max Spevack wrote: > I just spent about 90 minutes going through Test3, starting with the > Gnome LiveCD and working my way through installation, firstboot, and > login. I tried to relive my days as a QA engineer and adopt the mindset > of a user who isn't deeply technical, and as a user who becomes > uncomfortable at anything that doesn't seem to "just work" the way it's > expected to. > > I have a number of suggestions and straight bugs. I don't have the time > to open bugzillas for all of these. I forgot to say, however, that overall the LiveCD is very impressive. But the difference between impressive and blows-you-away-awesome is the small stuff, and that is the spirit in which I wrote my email. --Max -- Max Spevack + http://fedoraproject.org/wiki/MaxSpevack + gpg key -- http://spevack.org/max.asc + fingerprint -- CD52 5E72 369B B00D 9E9A 773E 2FDB CB46 5A17 CF21 From davidz at redhat.com Wed Apr 4 16:47:44 2007 From: davidz at redhat.com (David Zeuthen) Date: Wed, 04 Apr 2007 12:47:44 -0400 Subject: [Fedora-livecd-list] Test3 LiveCD QA issues In-Reply-To: References: Message-ID: <1175705264.2741.11.camel@zelda.fubar.dk> On Wed, 2007-04-04 at 11:46 -0400, Max Spevack wrote: > ====================== > > Booting the LiveCD, grub gives you two options: > > Fedora-7-Test3-Live-i386 > Fedora-7-Test3-Live-i386 from RAM > > This is confusing -- should I choose default or no? What's the difference > between the two? I think users will be confused. The FC6 live cd said "(run from RAM - requires 1GB+)" instead of "from RAM" which may be less confusing to at least English speaking users.. > ====================== > > The default user name at the Live CD's gdm -- this is a simple change > > s/Fedora live CD/Fedora/ > > then if it's a LiveUSB or LiveDVD, the user name doesn't look odd Sounds good to me... > ====================== > > First impressions of the LiveCD desktop Note that mostly all of your comments below also apply to the default desktop install.. best is to just fix the problems there. So I'm adding fedora-desktop-list to get out the desktop people to read this. For reference, the original mail was here https://www.redhat.com/archives/fedora-livecd-list/2007-April/msg00036.html I basically agree with most of your points; some specific comments below... > We want it to be uncluttered, and to show off the coolest stuff in the > most obvious way. To that end: > - do we need the SCIM module in the top right? It would be nice if SCIM didn't show an icon for certain locales that use latin1, e.g. English, Danish, German, Dutch etc. So this should be fixed in SCIM itself... we shouldn't do a quick one-off for the live CD; we need to fix SCIM and keep including it by default... Keep in mind that the live CD may be used by people who don't speak/read/understand a word of English. > - do we need the Desktop search module in the top right? No, it should go IMO. Not Live CD specific. > > What about the default applications at the top of the GNOME panel? > - now: evolution, web browser Not Live CD specific. Agree it needs work... personally I think the web browser icon is butt ugly; it should show Firefox as that's the default browse... btw, it's even worse; a default desktop install we show icons for three OO applications. Do we really think that OO.o is the first thing people do? (I mean, this setup might be fine for "RHEL Desktop" but I'd wager any day of the week, and twice on Sundays, that it isn't true for Fedora) > - "Other->Theme Installer" doesn't do anything, and should be > removed Fixed already in Rawhide AFAIK. You missed my favorite pet peeve about the default desktop install. We show two trash cans, one in lower panel and one on the desktop. Do we _really_ want people to call us the trash distro? :-) David From katzj at redhat.com Wed Apr 4 14:11:44 2007 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 04 Apr 2007 10:11:44 -0400 Subject: [Fedora-livecd-list] liveinst/anaconda crashes after setting root password In-Reply-To: <20070404152930.5016e410@localhost.localdomain> References: <20070403141602.0e4cf8ea@localhost.localdomain> <1175620571.3746.15.camel@aglarond.local> <20070404152930.5016e410@localhost.localdomain> Message-ID: <1175695904.3099.1.camel@aglarond.local> On Wed, 2007-04-04 at 15:29 +0200, Sebastian Vahl wrote: > Am Tue, 03 Apr 2007 13:16:11 -0400 schrieb Jeremy Katz : > > On Tue, 2007-04-03 at 14:16 +0200, Sebastian Vahl wrote: > > > Wanted to post this here first before creating a bug. Am I missing > > > something or is this really a bug that should be filled? > > > > We fixed this yesterday, but then just never got around to building > > anaconda. Sorry about that :/ > > > anaconda is working again (anaconda-11.2.0.44-1). And even the > installation is bootable again! (#234728). Thanks! Great -- thanks for testing. And the "fix" for 234728 is currently just a hack... hopefully I'll get more to the bottom of it today, but I didn't want to leave things broken for testers in the interim Jeremy From katzj at redhat.com Wed Apr 4 17:27:23 2007 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 04 Apr 2007 13:27:23 -0400 Subject: [Fedora-livecd-list] Test3 LiveCD QA issues In-Reply-To: <1175702898.6884.161.camel@metroid.rdu.redhat.com> References: <1175702898.6884.161.camel@metroid.rdu.redhat.com> Message-ID: <1175707643.3099.5.camel@aglarond.local> On Wed, 2007-04-04 at 12:08 -0400, Will Woods wrote: > On Wed, 2007-04-04 at 11:46 -0400, Max Spevack wrote: > > First impressions of the LiveCD desktop > > > > We want it to be uncluttered, and to show off the coolest stuff in the > > most obvious way. To that end: > > - do we need the SCIM module in the top right? > > - do we need the Desktop search module in the top right? > > For that matter - shouldn't we pre-populate the image with index data if > we're going to include Beagle? If there were an easy way to do so, it'd be worth considering but the data is per-user I believe. And the user is actually created at boot time. > > - We need a default homepage for Firefox that isn't just the generic > > firefox page. > > IIRC this is coming (as with the "Welcome to Fedora Core 6!" page) soon. > Although I'm not sure if we have/want a LiveCD specific one. Personally, I'd prefer to keep them the same. Which means we should include a little bit that's about the live CD in the default page probably. > > - "System->About Fedora" can't load properly due to missing > > about-fedora.xml > > Again, I believe this is coming along with the bookmarks and Firefox > start page.. Actually I thought we had a placeholder there now. Did it > get dropped from the LiveCD? For test3, we had to nuke /usr/share/docs so we'd fit on the CD which would have broken this. We've managed to make some other package tweaks to avoid having to do this in The Future (tm) Jeremy From jkeating at redhat.com Wed Apr 4 17:31:46 2007 From: jkeating at redhat.com (Jesse Keating) Date: Wed, 4 Apr 2007 13:31:46 -0400 Subject: [Fedora-livecd-list] Test3 LiveCD QA issues In-Reply-To: References: <1175705264.2741.11.camel@zelda.fubar.dk> Message-ID: <200704041331.50123.jkeating@redhat.com> On Wednesday 04 April 2007 13:14:31 dragoran dragoran wrote: > which is not true for x86_64 it does not even work with 2gb (oom) This was a bug in how this was done from DVD which should be fixed now, so that the comment should still apply. -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From katzj at redhat.com Wed Apr 4 17:30:26 2007 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 04 Apr 2007 13:30:26 -0400 Subject: [Fedora-livecd-list] Test3 LiveCD QA issues In-Reply-To: <1175705264.2741.11.camel@zelda.fubar.dk> References: <1175705264.2741.11.camel@zelda.fubar.dk> Message-ID: <1175707826.3099.9.camel@aglarond.local> On Wed, 2007-04-04 at 12:47 -0400, David Zeuthen wrote: > On Wed, 2007-04-04 at 11:46 -0400, Max Spevack wrote: > > ====================== > > > > Booting the LiveCD, grub gives you two options: > > > > Fedora-7-Test3-Live-i386 > > Fedora-7-Test3-Live-i386 from RAM > > > > This is confusing -- should I choose default or no? What's the difference > > between the two? I think users will be confused. > > The FC6 live cd said "(run from RAM - requires 1GB+)" instead of "from > RAM" which may be less confusing to at least English speaking users.. At the same time, it's long and if you have a long enough fslabel (which we likely do), then you run out of space and only get part of the text displayed. While the run from RAM option is nice, I'm still not entirely sold on it for the reasons Max was confused. > > ====================== > > > > The default user name at the Live CD's gdm -- this is a simple change > > > > s/Fedora live CD/Fedora/ > > > > then if it's a LiveUSB or LiveDVD, the user name doesn't look odd > > Sounds good to me... I actually have pending changing it to "Fedora Live" instead of just Fedora. And actually changing the rest of the "livecd" type references to be just live or live image. Jeremy From zrchrn at gmail.com Wed Apr 4 17:37:17 2007 From: zrchrn at gmail.com (Ahm ed) Date: Wed, 4 Apr 2007 13:37:17 -0400 Subject: [Fedora-livecd-list] Question- Has the booting problem been fixed? Message-ID: The Problem: Booting the Fedora 7 live cd fails with an error about not being able to mount the root filesystem. There are examples of users problems here: http://forums.fedoraforum.org/showthread.php?t=151292&page=2&pp=15 I have on numerous occasions heard/read there were fixes but still have not seen any. Is this a known problem, with a known fix coming? Anyone know? -Ed From mspevack at redhat.com Wed Apr 4 17:48:44 2007 From: mspevack at redhat.com (Max Spevack) Date: Wed, 4 Apr 2007 13:48:44 -0400 (EDT) Subject: [Fedora-livecd-list] Test3 LiveCD QA issues In-Reply-To: <1175707826.3099.9.camel@aglarond.local> References: <1175705264.2741.11.camel@zelda.fubar.dk> <1175707826.3099.9.camel@aglarond.local> Message-ID: On Wed, 4 Apr 2007, Jeremy Katz wrote: >>> The default user name at the Live CD's gdm -- this is a simple change >>> >>> s/Fedora live CD/Fedora/ >>> >>> then if it's a LiveUSB or LiveDVD, the user name doesn't look odd >> >> Sounds good to me... > > I actually have pending changing it to "Fedora Live" instead of just > Fedora. And actually changing the rest of the "livecd" type references > to be just live or live image. works4me --Max From katzj at redhat.com Wed Apr 4 17:52:41 2007 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 04 Apr 2007 13:52:41 -0400 Subject: [Fedora-livecd-list] Question- Has the booting problem been fixed? In-Reply-To: References: Message-ID: <1175709162.3099.15.camel@aglarond.local> On Wed, 2007-04-04 at 13:37 -0400, Ahm ed wrote: > The Problem: > Booting the Fedora 7 live cd fails with an error about not being able > to mount the root filesystem. > > There are examples of users problems here: > > http://forums.fedoraforum.org/showthread.php?t=151292&page=2&pp=15 > > I have on numerous occasions heard/read there were fixes but still > have not seen any. Is this a known problem, with a known fix coming? > Anyone know? With test1, there were some pata drivers which weren't included as well as one of the main sata drivers being just entirely busted. Especially with test3, though, I don't know of any specific cases where there should be problems. If people are having problems, we need to have bugs filed with the specific details of their hardware (and one per person, instead of 5 people piling into the same bug with different hardware) to try to track down the problem. Jeremy From rdieter at math.unl.edu Wed Apr 4 18:09:34 2007 From: rdieter at math.unl.edu (Rex Dieter) Date: Wed, 04 Apr 2007 13:09:34 -0500 Subject: [Fedora-livecd-list] git write access, who to poke? Message-ID: Now that the kde livecd configs are in the livecd git repo, who can I poke to get write access? I'd like to be able use that as the authoritative copy used for development purposes. (I'll have to learn to use git too, but that's my problem). -- Rex From sundaram at fedoraproject.org Wed Apr 4 17:59:58 2007 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Wed, 04 Apr 2007 23:29:58 +0530 Subject: [Fedora-livecd-list] Test3 LiveCD QA issues In-Reply-To: <1175709293.17528.2.camel@rousalka.dyndns.org> References: <1175705264.2741.11.camel@zelda.fubar.dk> <1175709293.17528.2.camel@rousalka.dyndns.org> Message-ID: <4613E79E.7000904@fedoraproject.org> Nicolas Mailhot wrote: > Le mercredi 04 avril 2007 ? 12:47 -0400, David Zeuthen a ?crit : > >> You missed my favorite pet peeve about the default desktop install. We >> show two trash cans, one in lower panel and one on the desktop. Do we >> _really_ want people to call us the trash distro? :-) > > What do you complain about ? This is the desktop that removed quick > terminal access, (and a few months later it tops in mugshot's stats) > > The Fedora desktop moves in mysterious ways I think you have pointed out that mugshot reference enough times by now. The nautilus extension to have the terminal in the context menu is installed by default which I am not sure is intentional. Rahul From davidz at redhat.com Wed Apr 4 19:24:42 2007 From: davidz at redhat.com (David Zeuthen) Date: Wed, 04 Apr 2007 15:24:42 -0400 Subject: [Fedora-livecd-list] Test3 LiveCD QA issues In-Reply-To: <1175709293.17528.2.camel@rousalka.dyndns.org> References: <1175705264.2741.11.camel@zelda.fubar.dk> <1175709293.17528.2.camel@rousalka.dyndns.org> Message-ID: <1175714682.2741.19.camel@zelda.fubar.dk> On Wed, 2007-04-04 at 19:54 +0200, Nicolas Mailhot wrote: > Le mercredi 04 avril 2007 ? 12:47 -0400, David Zeuthen a ?crit : > > > You missed my favorite pet peeve about the default desktop install. We > > show two trash cans, one in lower panel and one on the desktop. Do we > > _really_ want people to call us the trash distro? :-) > > What do you complain about ? This is the desktop that removed quick > terminal access, (and a few months later it tops in mugshot's stats) > > The Fedora desktop moves in mysterious ways For the record, nautilus-open-terminal was in the FC6 live cd (reason: "For the adult in you") [1] so at least I share your point of view. I don't know why it disappeared from the Fedora 7 live cd. When the merger is complete it should probably be pulled in by one of the default @desktop groups. (Btw, in the future please rather file a bug so nautilus-open-terminal can go into the default set instead of... snide remarks. Thanks for your continued interested in the Fedora desktop project.) David [1] : http://www.mail-archive.com/fedora-announce-list at redhat.com/msg01172.html From mspevack at redhat.com Wed Apr 4 19:44:30 2007 From: mspevack at redhat.com (Max Spevack) Date: Wed, 4 Apr 2007 15:44:30 -0400 (EDT) Subject: [Fedora-livecd-list] Test3 LiveCD QA issues In-Reply-To: <1175714682.2741.19.camel@zelda.fubar.dk> References: <1175705264.2741.11.camel@zelda.fubar.dk> <1175709293.17528.2.camel@rousalka.dyndns.org> <1175714682.2741.19.camel@zelda.fubar.dk> Message-ID: On Wed, 4 Apr 2007, David Zeuthen wrote: > For the record, nautilus-open-terminal was in the FC6 live cd (reason: > "For the adult in you") [1] so at least I share your point of view. I > don't know why it disappeared from the Fedora 7 live cd. When the merger > is complete it should probably be pulled in by one of the default > @desktop groups. > > (Btw, in the future please rather file a bug so nautilus-open-terminal > can go into the default set instead of... snide remarks. Thanks for your > continued interested in the Fedora desktop project.) If I had final say over the Fedora package manifest (and in a roundabout way I suppose I do), nautilus-open-terminal would be included by default on the GNOME LiveCD and in Fedora Prime/Everything. And gnome-terminal would be in the top panel on the desktop. :-) --Max From gmureddu at prodigy.net.mx Wed Apr 4 21:32:06 2007 From: gmureddu at prodigy.net.mx (Gian Paolo Mureddu) Date: Wed, 04 Apr 2007 16:32:06 -0500 Subject: [Fedora-livecd-list] Fedora 7 Test3 LiveCD feedback Message-ID: <46141956.5080902@prodigy.net.mx> I'm not sure if this is the right place to provide feedback on the LiveCD for the Test versions of Fedora 7... If this is not, then please point me in the right direction. I recently tried the latest LiveCD on a factory build HP Pavillion machine (I'm not sure about the model, sorry), and found a few problems. Fortunately enough I had no problems booting up the LiveCD, however here are my observations: * Proper keyboard map is not loaded when changing the language for the session. Maybe this is the most offending "problem" of the ones I found. I tested the LiveCD in English and Spanish (Mexico). When I switched to Spanish, I expected the keymap to be changed to that of Spanish Latin American, instead the default keymap was kept (US English). This is easily solvable by changing the map with the keyboard applet in GNOME. * Even though apparently everything seems to be working right for the graphics hardware on this machine, trying to enable Desktop Effects resulted in X restarting. The chip in question is an S3 Pro Savage DDR whose DRI drivers do have support for 32-bpp rendering. I did not go much further into checking whether or not AIGLX was enabled or not, etc... Not that this feature is a must, and certainly not on such hardware, but it would have been nice to test its performance with this hardware. * I know all about the reasons behind leaving OOo out of the LiveCD spins, but AbiWord simply is not enough for .doc documents (while Gnumeric is more than capable of opening a plethora of .xls files). AbiWord crashed several times trying to open a rather simple .doc document, when I get the chance I'll file the proper bug report. * Compared to other Live media distributions out there, Fedora feels a bit more "sluggish"... By this I mean that it apparently takes more time reading data off the CD/DVD media than other distributions like Knoppix. Not that this is a problem as such, but rather it takes a bit longer to boot and start the session... On the other hand, Fedora LiveCDs have about the best hardware detection and setup I've seen yet in a LiveCD. I'll file bug reports for the Desktop Effects and keyboard map issues in bugzilla as soon as I can (if not others have already filed them), all in all this test release is a very solid one, and it was rather nice to see it in action. All the good news follow: * I was able to instantly browse the Windows network I have setup at home and it did so without any problems (as expected as there are two other Fedora linux boxes on this network, the master file server [FC5] and my personal workstation [FC6], so not only was the Windows network visible and "browseable", but also some *nix services [like sftp]) * For this computer in particular the performance in the desktop interactivity is far superior to its native OS (WinXP Home). Browsing the large collection of family photographs on the file server was a snap, and the rendering speed and pan speed of the images when viewed at full size (2048/1536) was pretty fast. By comparison, using the Windows' image viewer panning the images when viewed in full size is painfully slow, plus no double filtering for zooms ;) * Configuring the network was a snap! The machine is set for DHCP, so it was automagically setup, however when to manually configure it, it was also very easy to do, especially since now the network applet is there by defaul, which means that opening and changing the connection's properties is very, very simple to do and easy. My father was rather impressed. * Removable media support, as always is superb. Tested the multi card reader on the machine only for consistency and completeness... Not problems in this area either, and it is rather nice to see the devices still there in the computer:/// view, even when the partitions have been unmounted, just like its been standard in GNOME since a few releases ago. * Printing is now REALLY simple. Actually it has been ever since FC6 (which allowed you to change some printing options like paper, printing quality etc, right from the print menu on most applications, rather than having to define several printers for the same hardware for different quality settings). A bit OT, but is it possible to get commercial ppd files to be used with CUPS and Gutenprint? * Firefox2 addition was a pleasant surprise... Though would it be possible to make the spell checker work with aspell as well?, so that it would also scan for errors in spelling for other languages, especially useful for HDD installations. In the current state it only works if you type in English, which means that any other language other than English will be red highlighted (kind of annoying, and I know, I know, it can be disabled... Consider this an RFE, though I'm afraid this depends on Mozilla rather than Fedora). From luya_tfz at thefinalzone.com Wed Apr 4 21:48:36 2007 From: luya_tfz at thefinalzone.com (Luya Tshimbalanga) Date: Wed, 4 Apr 2007 17:48:36 -0400 Subject: [Fedora-livecd-list] LiveCD not ejecting when shutting down/restart In-Reply-To: References: <1175705264.2741.11.camel@zelda.fubar.dk> <1175709293.17528.2.camel@rousalka.dyndns.org> <1175714682.2741.19.camel@zelda.fubar.dk> Message-ID: <1175723316.46141d349be59@ssl.mecca.ca> One of annoying problem is the inability for the liveCD to unmount and eject itself when shutting down or restarting. The issues is true for a LiveCD but I think it might apply for LiveUSB as well. Can anyone solve that issue? -- Luya Tshimbalanga Fedora Project contributor http://www.fedoraproject.org/wiki/LuyaTshimbalanga From jasperhartline at adelphia.net Thu Apr 5 18:48:03 2007 From: jasperhartline at adelphia.net (Jasper Hartline) Date: Thu, 05 Apr 2007 13:48:03 -0500 Subject: [Fedora-livecd-list] LiveCD not ejecting when shutting down/restart In-Reply-To: <1175723316.46141d349be59@ssl.mecca.ca> References: <1175705264.2741.11.camel@zelda.fubar.dk> <1175709293.17528.2.camel@rousalka.dyndns.org> <1175714682.2741.19.camel@zelda.fubar.dk> <1175723316.46141d349be59@ssl.mecca.ca> Message-ID: <46154463.1080800@adelphia.net> Luya Tshimbalanga wrote: > One of annoying problem is the inability for the liveCD to unmount and eject > itself when shutting down or restarting. The issues is true for a LiveCD but I > think it might apply for LiveUSB as well. Can anyone solve that issue? > > LiveUSB devices do not require ejections. If you take a look at Kadischi's eject_live_cd.c you will see we use the same code as find_live_cd.c to locate and eject the CDROM or DVDROM device from readonly-halt which is part of Kadischi also. Perhaps this would be something to integrate within Pilgrim? It works splendid. J. Hartline From tjboring at gmail.com Fri Apr 6 00:01:01 2007 From: tjboring at gmail.com (Tim Boring) Date: Thu, 5 Apr 2007 17:01:01 -0700 Subject: [Fedora-livecd-list] livecd-creator command doesn't appear to be creating vmlinuz Message-ID: <207b80240704051701s60c4c586h7faec33d1214941d@mail.gmail.com> i'm trying to build a livecd using the livecd-creator tool on FC6 but am having some issues. the command completes with an exit code of 0 but the resulting ISO doesn't include the kernel in the boot directory. here are a couple lines from the output of livecd-creator that seem to point to an issue with the chroot environment: Installed: bash.i386 0:3.1-16.1 grub.i386 0:0.97-13 Dependency Installed: basesystem.noarch 0:8.0-5.1.1 diffutils.i386 0: 2.8.1-15.2.2 fedora-logos.noarch 0:6.0.6-1.fc6 filesystem.i386 0:2.4.0-1 glibc.i686 0:2.5-3 glibc-common.i386 0:2.5-3 info.i386 0:4.8-11.1 libgcc.i386 0:4.1.1-30 libtermcap.i386 0:2.0.8-46.1 mktemp.i386 3:1.5-23.2.2 ncurses.i386 0:5.5-24.20060715 setup.noarch 0:2.5.55-1 termcap.noarch 1: 5.5-1.20060701.1 tzdata.noarch 0:2006m-2.fc6 zlib.i386 0:1.2.3-3 Unknown option or parameter "gconfd-root" /sbin/mayflower [--help] example: /sbin/mayflower /boot/myinitramfs.img `uname -r` /usr/sbin/chroot: cannot run command `/sbin/fixfiles': No such file or directory /bin/cp: cannot stat `/var/tmp/livecd-creator/build-tmpe4dAud/install_root/boot/vmlinuz*': No such file or directory /bin/mv: cannot stat `/var/tmp/livecd-creator/build-tmpe4dAud/install_root/boot/livecd- initramfs.img': No such file or directory but i'm not really sure how to proceed from this point. before running the command i added /sbin to root's path and i also verified that /sbin/fixfiles exists...so that looks ok in the normal environment. i guess i'm not sure why it wouldn't work in the chroot environment. any ideas or suggestions are appreciated. thanks, tim thanks, tim -------------- next part -------------- An HTML attachment was scrubbed... URL: From raywelton at yahoo.com Fri Apr 6 20:05:53 2007 From: raywelton at yahoo.com (ray welton) Date: Fri, 06 Apr 2007 13:05:53 -0700 Subject: [Fedora-livecd-list] livecd-creator command doesn't appear to be creating vmlinuz In-Reply-To: <207b80240704051701s60c4c586h7faec33d1214941d@mail.gmail.com> References: <207b80240704051701s60c4c586h7faec33d1214941d@mail.gmail.com> Message-ID: <1175889953.15069.43.camel@lab-rh1> Hi TIM, Well I'm new at this and had the same/similar problem. I copied all of the contents of the Fedora-Livecd I downloaded and burned to a cd to the /usr/tmp/livecd-creator' directory squashfs.img /boot/ /sysroot/ Before building the image you need to.. First get Super User 'su -' then set SELinux '/usr/sbin/setenforce 0' also insure you are in the directory where you want the ISO file to be saved. I'm still working at figuring out the commands and configuration but the above way did get me started with a boot-able ISO img. Some body else will probably give you better incite but I hope this may help. Ray On Thu, 2007-04-05 at 17:01 -0700, Tim Boring wrote: > i'm trying to build a livecd using the livecd-creator tool on FC6 but > am having some issues. the command completes with an exit code of 0 > but the resulting ISO doesn't include the kernel in the boot > directory. here are a couple lines from the output of livecd-creator > that seem to point to an issue with the chroot environment: > > Installed: bash.i386 0:3.1-16.1 grub.i386 0:0.97-13 > Dependency Installed: basesystem.noarch 0:8.0-5.1.1 diffutils.i386 > 0:2.8.1-15.2.2 fedora-logos.noarch 0:6.0.6-1.fc6 filesystem.i386 > 0:2.4.0-1 glibc.i686 0:2.5-3 glibc-common.i386 0:2.5-3 info.i386 > 0:4.8-11.1 libgcc.i386 0:4.1.1-30 libtermcap.i386 0:2.0.8-46.1 > mktemp.i386 3:1.5-23.2.2 ncurses.i386 0:5.5-24.20060715 setup.noarch > 0:2.5.55-1 termcap.noarch 1:5.5-1.20060701.1 tzdata.noarch > 0:2006m-2.fc6 zlib.i386 0:1.2.3-3 > Unknown option or parameter "gconfd-root" > > /sbin/mayflower [--help] > > example: /sbin/mayflower /boot/myinitramfs.img `uname -r` > /usr/sbin/chroot: cannot run command `/sbin/fixfiles': No such file or > directory > /bin/cp: cannot stat > `/var/tmp/livecd-creator/build-tmpe4dAud/install_root/boot/vmlinuz*': > No such file or directory > /bin/mv: cannot stat > `/var/tmp/livecd-creator/build-tmpe4dAud/install_root/boot/livecd- > initramfs.img': No such file or directory > > but i'm not really sure how to proceed from this point. before > running the command i added /sbin to root's path and i also verified > that /sbin/fixfiles exists...so that looks ok in the normal > environment. i guess i'm not sure why it wouldn't work in the chroot > environment. any ideas or suggestions are appreciated. > > thanks, > tim > > thanks, > tim > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list From lesliek at ozemail.com.au Mon Apr 9 07:02:45 2007 From: lesliek at ozemail.com.au (lesliek at ozemail.com.au) Date: Mon, 09 Apr 2007 15:02:45 +0800 Subject: [Fedora-livecd-list] "Build a Fedora Live CD" instructions Message-ID: <32872.1176102165@ozemail.com.au> An HTML attachment was scrubbed... URL: From tjboring at gmail.com Mon Apr 9 07:10:18 2007 From: tjboring at gmail.com (Tim Boring) Date: Mon, 9 Apr 2007 00:10:18 -0700 Subject: [Fedora-livecd-list] "Build a Fedora Live CD" instructions In-Reply-To: <32872.1176102165@ozemail.com.au> References: <32872.1176102165@ozemail.com.au> Message-ID: <207b80240704090010n48329713y44b4d34327ac2cc@mail.gmail.com> try setting up root's path like so: PATH=/sbin:$PATH that should fix it. i encountered the same problem and it was because root's path didn't include '/sbin'...not sure why, but that's a different issue. On 4/9/07, lesliek at ozemail.com.au wrote: > > I'm using Fedora Core 6. > > I followed exactly the above instructions in an attempt to create a > minimal Live CD. > > They failed for me. > > The output of the relevant command shows 74 packages being installed, > bash, grub and kernel plus 71 dependencies. > > The output then continues: > > "Building an initramfs at /boot/livecd-initramfs.img for kernel > 2.6.18-1.2798.fc6 > FATAL: Module usbhid not found. > FATAL: Module sata_ulisata_nv not found. > FATAL: Module sata_viasata_promise not found. > cp: cannot stat `/usr/sbin/eject': No such file or directory > cp: cannot stat `/usr/bin/tree': No such file or directory > Done; initramfs is 2.8M. > > /usr/sbin/chroot: cannot run command `/sbin/fixfiles': No such file or > directory > sh: mksquashfs: command not found" > > How should I edit the command string given in the document to create the > minimal live cd? > > Thanks for reading, > > Leslie > > > ____ > Visit http://stumblng.tumblr.com > An Australian lawyer's tumblelog about things you might otherwise have > missed > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lesliek at ozemail.com.au Mon Apr 9 09:14:59 2007 From: lesliek at ozemail.com.au (Leslie Katz) Date: Mon, 09 Apr 2007 19:14:59 +1000 Subject: [Fedora-livecd-list] "Build a Fedora Live CD" instructions In-Reply-To: <207b80240704090010n48329713y44b4d34327ac2cc@mail.gmail.com> References: <32872.1176102165@ozemail.com.au> <207b80240704090010n48329713y44b4d34327ac2cc@mail.gmail.com> Message-ID: <461A0413.6090202@ozemail.com.au> Thanks very much for your reply Tim. I thought I could add /sbin to root's path permanently by editing root's .bash_profile file, but, although the file took the change, that didn't lead to /sbin showing up in root's path on a reboot. So I added /sbin to root's path temporarily before running the livecd-creator again. When I did that, I got all the errors I set out in my first post, except for the last one, "sh: mksquashfs: command not found". That had obviously been the crucial one, since I also got an .iso the second time. When I booted from it, all worked up to the stage where I was asked to log in. I knew nothing of any username or password, so I just pressed Enter. However, that didn't work. I infer that there's no way to get beyond the log in stage with the minimal cd. I'll now try to follow the next lot of instructions in the document. Thanks again for your help, Leslie Tim Boring wrote: > try setting up root's path like so: > > PATH=/sbin:$PATH > > that should fix it. i encountered the same problem and it was because > root's path didn't include '/sbin'...not sure why, but that's a > different issue. > -- Visit http://stumblng.tumblr.com An Australian lawyers' tumblelog about things you might otherwise have missed From katzj at redhat.com Mon Apr 9 14:44:25 2007 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 09 Apr 2007 10:44:25 -0400 Subject: [Fedora-livecd-list] livecd-creator command doesn't appear to be creating vmlinuz In-Reply-To: <207b80240704051701s60c4c586h7faec33d1214941d@mail.gmail.com> References: <207b80240704051701s60c4c586h7faec33d1214941d@mail.gmail.com> Message-ID: <1176129866.31918.6.camel@erebor.boston.redhat.com> On Thu, 2007-04-05 at 17:01 -0700, Tim Boring wrote: > i'm trying to build a livecd using the livecd-creator tool on FC6 but > am having some issues. the command completes with an exit code of 0 > but the resulting ISO doesn't include the kernel in the boot > directory. here are a couple lines from the output of livecd-creator > that seem to point to an issue with the chroot environment: Which version of the livecd creator? Jeremy From ps3udov3ctor at gmail.com Mon Apr 9 16:40:17 2007 From: ps3udov3ctor at gmail.com (pseudo vector) Date: Mon, 9 Apr 2007 10:40:17 -0600 Subject: [Fedora-livecd-list] how to set root password? Message-ID: <13233df20704090940j1b166057p28ab425eb8fdffef@mail.gmail.com> Hi, I'm trying to use livecd-creator to make a "permanent" system that sits outside of a firewall (i.e. it's assigned a non-dhcp ip address, runs ssh for users that need to get into our internal network). I can not get root login to work though. I have the following lines in my livecd-conf file: # update user info echo 'root:$1$ncO9QrXs$.f63DbXQniCX41Pb8gMD1' | chpasswd -e passwd -S root useradd -c "SNOOPY User Account" -m -n \ -p '$1$2OOvrGlY$M3tBJfc9gfKvThcmqnOgo1' snoopy pwconv When I boot the livecd though root logins fail with: login: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=tty1 ruser= rhost= user=root login: FAILED LOGIN 1 FROM (null) FOR root, Authentication failure The snoopy user account works fine though (and I can't su to root from that account). I've verified by looking at the livecd image that the password is set properly in /etc/passwd and /etc/shadow. /etc/securetty is also ok. How does one go about getting root logins on the livecd? Thanks in advance for any replys. From tjboring at gmail.com Mon Apr 9 17:16:06 2007 From: tjboring at gmail.com (Tim Boring) Date: Mon, 9 Apr 2007 10:16:06 -0700 Subject: [Fedora-livecd-list] "Build a Fedora Live CD" instructions In-Reply-To: <461A0413.6090202@ozemail.com.au> References: <32872.1176102165@ozemail.com.au> <207b80240704090010n48329713y44b4d34327ac2cc@mail.gmail.com> <461A0413.6090202@ozemail.com.au> Message-ID: <207b80240704091016l305dbce4v93c163152c1b9336@mail.gmail.com> On 4/9/07, Leslie Katz wrote: > > Thanks very much for your reply Tim. > > I thought I could add /sbin to root's path permanently by editing root's > .bash_profile file, but, although the file took the change, that didn't > lead to /sbin showing up in root's path on a reboot. So I added /sbin to > root's path temporarily before running the livecd-creator again. if you want to add /sbin to root's path permanently, you need to add it to root's .bashrc, not .bash_profile. that'll take care of it so /sbin is there after a reboot. > When I booted from it, all worked up to the stage where I was asked to > log in. I knew nothing of any username or password, so I just pressed > Enter. However, that didn't work. you couldn't log in because the livecd-creator command doesn't set a root password and doesn't create a normal user. you'll have to do that yourself. i think i saw that in the docs somewhere. hope that helps, tim Tim Boring wrote: > > try setting up root's path like so: > > > > PATH=/sbin:$PATH > > > > that should fix it. i encountered the same problem and it was because > > root's path didn't include '/sbin'...not sure why, but that's a > > different issue. > > > -- > Visit http://stumblng.tumblr.com > An Australian lawyers' tumblelog about things you might otherwise have > missed > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tjboring at gmail.com Mon Apr 9 17:16:56 2007 From: tjboring at gmail.com (Tim Boring) Date: Mon, 9 Apr 2007 10:16:56 -0700 Subject: [Fedora-livecd-list] livecd-creator command doesn't appear to be creating vmlinuz In-Reply-To: <1176129866.31918.6.camel@erebor.boston.redhat.com> References: <207b80240704051701s60c4c586h7faec33d1214941d@mail.gmail.com> <1176129866.31918.6.camel@erebor.boston.redhat.com> Message-ID: <207b80240704091016t1c9f8a5cu8b593be5324d48a0@mail.gmail.com> disregard...i found the problem. i foobar'd the command! :-( On 4/9/07, Jeremy Katz wrote: > > On Thu, 2007-04-05 at 17:01 -0700, Tim Boring wrote: > > i'm trying to build a livecd using the livecd-creator tool on FC6 but > > am having some issues. the command completes with an exit code of 0 > > but the resulting ISO doesn't include the kernel in the boot > > directory. here are a couple lines from the output of livecd-creator > > that seem to point to an issue with the chroot environment: > > Which version of the livecd creator? > > Jeremy > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian.cain at gmail.com Mon Apr 9 18:42:48 2007 From: brian.cain at gmail.com (Brian Cain) Date: Mon, 9 Apr 2007 13:42:48 -0500 Subject: [Fedora-livecd-list] how to set root password? In-Reply-To: <13233df20704090940j1b166057p28ab425eb8fdffef@mail.gmail.com> References: <13233df20704090940j1b166057p28ab425eb8fdffef@mail.gmail.com> Message-ID: <17e3a31c0704091142ib56b2fxaadcbc9fad5c3dbe@mail.gmail.com> On 4/9/07, pseudo vector wrote: > Hi, > > I'm trying to use livecd-creator to make a "permanent" system that > sits outside of a firewall (i.e. it's assigned a non-dhcp ip address, > runs ssh for users that need to get into our internal network). > > I can not get root login to work though. I have the following lines in > my livecd-conf file: > > # update user info > echo 'root:$1$ncO9QrXs$.f63DbXQniCX41Pb8gMD1' | chpasswd -e > passwd -S root > useradd -c "SNOOPY User Account" -m -n \ > -p '$1$2OOvrGlY$M3tBJfc9gfKvThcmqnOgo1' snoopy > pwconv > > When I boot the livecd though root logins fail with: > login: pam_unix(login:auth): authentication failure; logname=LOGIN > uid=0 euid=0 tty=tty1 ruser= rhost= user=root > > login: FAILED LOGIN 1 FROM (null) FOR root, Authentication failure > > The snoopy user account works fine though (and I can't su to root from > that account). That error message looks like a generic authentication failure, but if you're sure you're typing in the password correctly, I would check the manpage for sshd_config. "PermitRootLogin" is one of the options whose value may need to change. > I've verified by looking at the livecd image that the password is set > properly in /etc/passwd and /etc/shadow. /etc/securetty is also ok. > > How does one go about getting root logins on the livecd? As an alternative, I would recommend adding this to your livecd init script instead: echo "snoopy ALL=(ALL) ALL" >> /etc/sudoers -- -Brian From ps3udov3ctor at gmail.com Mon Apr 9 19:09:13 2007 From: ps3udov3ctor at gmail.com (pseudo vector) Date: Mon, 9 Apr 2007 13:09:13 -0600 Subject: [Fedora-livecd-list] how to set root password? In-Reply-To: <17e3a31c0704091142ib56b2fxaadcbc9fad5c3dbe@mail.gmail.com> References: <13233df20704090940j1b166057p28ab425eb8fdffef@mail.gmail.com> <17e3a31c0704091142ib56b2fxaadcbc9fad5c3dbe@mail.gmail.com> Message-ID: <13233df20704091209p54c8e483r68b5b19369c13c37@mail.gmail.com> On 4/9/07, Brian Cain wrote: > That error message looks like a generic authentication failure, but if > you're sure you're typing in the password correctly, I would check the > manpage for sshd_config. "PermitRootLogin" is one of the options > whose value may need to change. I'm trying to log in from the terminal (tty1), not through ssh. /etc/securetty is set to allow root logins from tty1. > As an alternative, I would recommend adding this to your livecd init > script instead: > > echo "snoopy ALL=(ALL) ALL" >> /etc/sudoers When the system is finally setup I don't want snoopy to be able to gain root access. I only mention that I can't su from the only other usable account as perhaps a hint to anyone that may know what is causing root to not to be able to login. From brian.cain at gmail.com Mon Apr 9 23:03:47 2007 From: brian.cain at gmail.com (Brian Cain) Date: Mon, 9 Apr 2007 18:03:47 -0500 Subject: [Fedora-livecd-list] how to set root password? In-Reply-To: <13233df20704091209p54c8e483r68b5b19369c13c37@mail.gmail.com> References: <13233df20704090940j1b166057p28ab425eb8fdffef@mail.gmail.com> <17e3a31c0704091142ib56b2fxaadcbc9fad5c3dbe@mail.gmail.com> <13233df20704091209p54c8e483r68b5b19369c13c37@mail.gmail.com> Message-ID: <17e3a31c0704091603x1a4f1bdcvd2d51e33d22241c1@mail.gmail.com> On 4/9/07, pseudo vector wrote: > On 4/9/07, Brian Cain wrote: > > That error message looks like a generic authentication failure, but if > > you're sure you're typing in the password correctly, I would check the > > manpage for sshd_config. "PermitRootLogin" is one of the options > > whose value may need to change. > > I'm trying to log in from the terminal (tty1), not through ssh. > /etc/securetty is set to allow root logins from tty1. Oh, I guess I didn't read closely enough. Have you executed the lines you're using in a shell on a fc6 system and verified that it works? I can't help thinking that chpasswd is mucking things up. Can you try and see if you can login if you echo a password to the passwd command? Even if you're nervous about a plaintext login on the livecd media, it's still worthwhile to execute for debugging's sake. By "set properly", you mean that the contents of /etc/shadow matches what you have in your shell script? -- -Brian From lesliek at ozemail.com.au Tue Apr 10 09:09:26 2007 From: lesliek at ozemail.com.au (Leslie Katz) Date: Tue, 10 Apr 2007 19:09:26 +1000 Subject: [Fedora-livecd-list] "Build a Fedora Live CD" instructions In-Reply-To: <207b80240704091016l305dbce4v93c163152c1b9336@mail.gmail.com> References: <32872.1176102165@ozemail.com.au> <207b80240704090010n48329713y44b4d34327ac2cc@mail.gmail.com> <461A0413.6090202@ozemail.com.au> <207b80240704091016l305dbce4v93c163152c1b9336@mail.gmail.com> Message-ID: <461B5446.8030002@ozemail.com.au> Tim Boring wrote: > > > if you want to add /sbin to root's path permanently, you need to add > it to root's .bashrc, not .bash_profile. that'll take care of it so > /sbin is there after a reboot. Thanks, Tim. I'll try that instead. I'm guessing now that what I tried didn't work because I didn't log in as root after editing .bash_profile. I logged in as myself and then switched to root in a terminal. > > > > you couldn't log in because the livecd-creator command doesn't set a > root password and doesn't create a normal user. you'll have to do > that yourself. i think i saw that in the docs somewhere. Well, I'm working from two documents, the document from the IBM site and a README that I got from the wiki. I think an understanding on the point is coming to me, though slowly. I'll need more time for experimenting, which I don't have right now, but I wanted to reply to you as soon as I could to thank you for your further help. Best wishes, Leslie From ps3udov3ctor at gmail.com Tue Apr 10 17:38:54 2007 From: ps3udov3ctor at gmail.com (pseudo vector) Date: Tue, 10 Apr 2007 11:38:54 -0600 Subject: [Fedora-livecd-list] how to set root password? In-Reply-To: <17e3a31c0704091603x1a4f1bdcvd2d51e33d22241c1@mail.gmail.com> References: <13233df20704090940j1b166057p28ab425eb8fdffef@mail.gmail.com> <17e3a31c0704091142ib56b2fxaadcbc9fad5c3dbe@mail.gmail.com> <13233df20704091209p54c8e483r68b5b19369c13c37@mail.gmail.com> <17e3a31c0704091603x1a4f1bdcvd2d51e33d22241c1@mail.gmail.com> Message-ID: <13233df20704101038y57be3f69va2172a93ecd1925f@mail.gmail.com> On 4/9/07, Brian Cain wrote: > Oh, I guess I didn't read closely enough. Have you executed the lines > you're using in a shell on a fc6 system and verified that it works? I > can't help thinking that chpasswd is mucking things up. Can you try > and see if you can login if you echo a password to the passwd command? > Even if you're nervous about a plaintext login on the livecd media, > it's still worthwhile to execute for debugging's sake. > By "set properly", you mean that the contents of /etc/shadow matches > what you have in your shell script? Oh man, am I stupid. No I didn't try on an existing system, so sure was I that I had done everything right. I just did it though and found sure enough that the same encrypted pw doesn't work on another fc6 system. The problem? I use a shell script to encrypt the passwords. The password I'm trying to use has a $ in it. The shell expanded that $ and the subsequent text as a variable, since it didn't exist it expanded to 0, and encrypted that string instead of the one I intended. If I replace that part of the password string with a 0, voila, I can log in. Total PICNIC error. Sorry to waste your time and the resources of the mailing list. Thanks for your help. From Brian.Cain at ge.com Tue Apr 10 17:51:55 2007 From: Brian.Cain at ge.com (Cain, Brian (GE Healthcare)) Date: Tue, 10 Apr 2007 13:51:55 -0400 Subject: [Fedora-livecd-list] how to set root password? In-Reply-To: <13233df20704101038y57be3f69va2172a93ecd1925f@mail.gmail.com> References: <13233df20704090940j1b166057p28ab425eb8fdffef@mail.gmail.com><17e3a31c0704091142ib56b2fxaadcbc9fad5c3dbe@mail.gmail.com><13233df20704091209p54c8e483r68b5b19369c13c37@mail.gmail.com><17e3a31c0704091603x1a4f1bdcvd2d51e33d22241c1@mail.gmail.com> <13233df20704101038y57be3f69va2172a93ecd1925f@mail.gmail.com> Message-ID: <2376B63A5AF8564F8A2A2D76BC6DB03302D8D0F4@CINMLVEM11.e2k.ad.ge.com> > -----Original Message----- > From: fedora-livecd-list-bounces at redhat.com > [mailto:fedora-livecd-list-bounces at redhat.com] On Behalf Of > pseudo vector ... > Oh man, am I stupid. No I didn't try on an existing system, so sure > was I that I had done everything right. I just did it though and found > sure enough that the same encrypted pw doesn't work on another fc6 > system. The problem? I use a shell script to encrypt the passwords. > The password I'm trying to use has a $ in it. The shell expanded that > $ and the subsequent text as a variable, since it didn't exist it BTW, for bash scripts, you can avoid this problem by quoting your here doc delimiter. If it's quoted, bash will not do variable expansion. Copy/paste these into a bash shell and see for yourself. cat <<'EOF' test $one $two $three EOF cat < Hey, I'm not sure if this is the right place to suggest this, but I think Gnome Partition Manager should be one of the default packages on the livecd spins. Although that would require ntfs-3g, it makes dual-booting Fedora (and hd tweaks) tons easier. Just thought I'd give my two cents... -Blayde From ml at deadbabylon.de Tue Apr 10 20:25:48 2007 From: ml at deadbabylon.de (Sebastian Vahl) Date: Tue, 10 Apr 2007 22:25:48 +0200 Subject: [Fedora-livecd-list] Suggestion: Submenu in isolinux for locales Message-ID: <20070410222548.4dcbba74@localhost.localdomain> Hi. Don't know if this is possible with isolinux: It would be much easier for non-english users if they could choose their language at the bootmenu. I know that they could attach eg. "live_locale=de_DE.UTF-8". But a menu or submenu for non-experienced users would be the best, I think. Sebastian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From katzj at redhat.com Tue Apr 10 20:54:24 2007 From: katzj at redhat.com (Jeremy Katz) Date: Tue, 10 Apr 2007 16:54:24 -0400 Subject: [Fedora-livecd-list] Suggestion: Submenu in isolinux for locales In-Reply-To: <20070410222548.4dcbba74@localhost.localdomain> References: <20070410222548.4dcbba74@localhost.localdomain> Message-ID: <1176238464.3025.35.camel@aglarond.local> On Tue, 2007-04-10 at 22:25 +0200, Sebastian Vahl wrote: > Don't know if this is possible with isolinux: It would be much easier > for non-english users if they could choose their language at the > bootmenu. I know that they could attach eg. "live_locale=de_DE.UTF-8". > But a menu or submenu for non-experienced users would be the best, I > think. The problem is that doing this in the bootloader is really not at all ideal. You don't have any ability to have a11y and bootloaders suck to hack on. This is why the GNOME live CD goes to gdm instead of just doing automatic login now. With the facebrowser, you can select the user and you can also select the language pretty easily Jeremy From gmureddu at prodigy.net.mx Tue Apr 10 22:29:16 2007 From: gmureddu at prodigy.net.mx (Gian Paolo Mureddu) Date: Tue, 10 Apr 2007 17:29:16 -0500 Subject: [Fedora-livecd-list] Suggestion: Submenu in isolinux for locales In-Reply-To: <1176238464.3025.35.camel@aglarond.local> References: <20070410222548.4dcbba74@localhost.localdomain> <1176238464.3025.35.camel@aglarond.local> Message-ID: <461C0FBC.4080101@prodigy.net.mx> Jeremy Katz escribi?: > On Tue, 2007-04-10 at 22:25 +0200, Sebastian Vahl wrote: > >> Don't know if this is possible with isolinux: It would be much easier >> for non-english users if they could choose their language at the >> bootmenu. I know that they could attach eg. "live_locale=de_DE.UTF-8". >> But a menu or submenu for non-experienced users would be the best, I >> think. >> > > The problem is that doing this in the bootloader is really not at all > ideal. You don't have any ability to have a11y and bootloaders suck to > hack on. > > This is why the GNOME live CD goes to gdm instead of just doing > automatic login now. With the facebrowser, you can select the user and > you can also select the language pretty easily > > Jeremy > > That's nice and all, but still it'd be best to be able to set the default system language from the get go... Maybe something a la Knoppix for this would be helpful? What I mean is that the default (en_us) locale keyboard will stick no matter if you login via GDM with another language. Maybe the easiest way would be to change the keyboard map to that of the locale when logging into the fedora session in the LiveCD, or skip GDM altogether and do it with boot parameters (only a page for the boot loader explaining the options to be passed would be required) so it'd be something like boot: linux lang=ES_mx or something similar. From zrchrn at gmail.com Wed Apr 11 02:53:56 2007 From: zrchrn at gmail.com (Ahm ed) Date: Tue, 10 Apr 2007 22:53:56 -0400 Subject: [Fedora-livecd-list] Booting Test Live-cds fails Message-ID: Hello, I have tried ALL the Test live-cds (from 1 to 3) And on everyone the cds have failed to boot up. Apparently something to do with either no /dev/root or modprobe not finding something. I am told this is related to the new PATA implementation in the Linux kernel. This is not a fedora specific bug. However I would have expected their to be a fix for this in fedora. Especially this long after the bug manifested itself. Has there been any work on this lately? How far has it gotten? At this rate Fedora has essentially become useless on my comp. as I cannot even boot to install it. The only way I know how is to install a minimal fc6 and upgrade. Which still doesn't fix the problem as I am force to stick to FC6 kernels. Any news? From markmc at redhat.com Wed Apr 11 13:41:10 2007 From: markmc at redhat.com (Mark McLoughlin) Date: Wed, 11 Apr 2007 14:41:10 +0100 Subject: [Fedora-livecd-list] [PATCH] livecd-creator : implement kickstart "network" command Message-ID: <1176298870.15779.1.camel@blaa> Hey, Here's a patch which takes a stab at implementing kickstart's network command in livecd-creator. Cheers, Mark. -------------- next part -------------- A non-text attachment was scrubbed... Name: livecd-kickstart-network-config.patch Type: text/x-patch Size: 5803 bytes Desc: not available URL: From markmc at redhat.com Wed Apr 11 15:55:38 2007 From: markmc at redhat.com (Mark McLoughlin) Date: Wed, 11 Apr 2007 16:55:38 +0100 Subject: [Fedora-livecd-list] [PATCH] livecd-creator : implement kickstart "network" command In-Reply-To: <1176298870.15779.1.camel@blaa> References: <1176298870.15779.1.camel@blaa> Message-ID: <1176306938.20305.0.camel@blaa> On Wed, 2007-04-11 at 14:41 +0100, Mark McLoughlin wrote: > + def writeNetworkConfig(self, instroot, netwrok): ^^ Watch out for this typo if applying - I forgot to refresh the patch with this fixed before sending it. Cheers, Mark. From katzj at redhat.com Wed Apr 11 17:08:07 2007 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 11 Apr 2007 13:08:07 -0400 Subject: [Fedora-livecd-list] Booting Test Live-cds fails In-Reply-To: References: Message-ID: <1176311287.13648.5.camel@aglarond.local> On Tue, 2007-04-10 at 22:53 -0400, Ahm ed wrote: > I have tried ALL the Test live-cds (from 1 to 3) And on everyone the > cds have failed to boot up. Apparently something to do with either no > /dev/root or modprobe not finding something. I am told this is related > to the new PATA implementation in the Linux kernel. This is not a > fedora specific bug. However I would have expected their to be a fix > for this in fedora. Especially this long after the bug manifested > itself. Has there been any work on this lately? How far has it gotten? > At this rate Fedora has essentially become useless on my comp. as I > cannot even boot to install it. The only way I know how is to install > a minimal fc6 and upgrade. Which still doesn't fix the problem as I am > force to stick to FC6 kernels. Any news? Have you filed a bug including the details of your hardware? Otherwise, it's really hard to be able to figure out exactly what's broken. Jeremy From katzj at redhat.com Wed Apr 11 17:15:52 2007 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 11 Apr 2007 13:15:52 -0400 Subject: [Fedora-livecd-list] [PATCH] livecd-creator : implement kickstart "network" command In-Reply-To: <1176298870.15779.1.camel@blaa> References: <1176298870.15779.1.camel@blaa> Message-ID: <1176311752.13648.10.camel@aglarond.local> On Wed, 2007-04-11 at 14:41 +0100, Mark McLoughlin wrote: > Here's a patch which takes a stab at implementing kickstart's network > command in livecd-creator. This ends up changing the behavior, though, in the case that you don't have a network line at all (which is pretty reasonable to do, especially if you're setting up for NetworkManager). Also, if you have multiple network lines and the first specifies the hostname, then it gets overriden by later ones. Jeremy From markmc at redhat.com Wed Apr 11 17:29:12 2007 From: markmc at redhat.com (Mark McLoughlin) Date: Wed, 11 Apr 2007 18:29:12 +0100 Subject: [Fedora-livecd-list] [PATCH] livecd-creator : implement kickstart "network" command In-Reply-To: <1176311752.13648.10.camel@aglarond.local> References: <1176298870.15779.1.camel@blaa> <1176311752.13648.10.camel@aglarond.local> Message-ID: <1176312552.20921.3.camel@blaa> On Wed, 2007-04-11 at 13:15 -0400, Jeremy Katz wrote: > On Wed, 2007-04-11 at 14:41 +0100, Mark McLoughlin wrote: > > Here's a patch which takes a stab at implementing kickstart's network > > command in livecd-creator. > > This ends up changing the behavior, though, in the case that you don't > have a network line at all (which is pretty reasonable to do, especially > if you're setting up for NetworkManager). Also, if you have multiple > network lines and the first specifies the hostname, then it gets > overriden by later ones. So, what you're basically saying is that writeNetworkConfig(), writeNetworkHosts() and writeNetworkResolv() should not be called per network line, but rather at the end either with values collected from the network lines in aggregate, or default values where there are no network lines? That makes sense, I'll take another look at anaconda's logic for this ... Cheers, Mark. From katzj at redhat.com Wed Apr 11 17:34:07 2007 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 11 Apr 2007 13:34:07 -0400 Subject: [Fedora-livecd-list] [PATCH] livecd-creator : implement kickstart "network" command In-Reply-To: <1176312552.20921.3.camel@blaa> References: <1176298870.15779.1.camel@blaa> <1176311752.13648.10.camel@aglarond.local> <1176312552.20921.3.camel@blaa> Message-ID: <1176312847.13648.23.camel@aglarond.local> On Wed, 2007-04-11 at 18:29 +0100, Mark McLoughlin wrote: > On Wed, 2007-04-11 at 13:15 -0400, Jeremy Katz wrote: > > On Wed, 2007-04-11 at 14:41 +0100, Mark McLoughlin wrote: > > > Here's a patch which takes a stab at implementing kickstart's network > > > command in livecd-creator. > > > > This ends up changing the behavior, though, in the case that you don't > > have a network line at all (which is pretty reasonable to do, especially > > if you're setting up for NetworkManager). Also, if you have multiple > > network lines and the first specifies the hostname, then it gets > > overriden by later ones. > > So, what you're basically saying is that writeNetworkConfig(), > writeNetworkHosts() and writeNetworkResolv() should not be called per > network line, but rather at the end either with values collected from > the network lines in aggregate, or default values where there are no > network lines? Yep. And written that way it makes a whole lot more sense than what I wrote :-) Jeremy From zrchrn at gmail.com Thu Apr 12 21:28:33 2007 From: zrchrn at gmail.com (Ahm ed) Date: Thu, 12 Apr 2007 17:28:33 -0400 Subject: [Fedora-livecd-list] Booting Test Live-cds fails Message-ID: >On Tue, 2007-04-10 at 22:53 -0400, Ahm ed wrote: >> I have tried ALL the Test live-cds (from 1 to 3) And on everyone the >> cds have failed to boot up. Apparently something to do with either no >> /dev/root or modprobe not finding something. I am told this is related >> to the new PATA implementation in the Linux kernel. This is not a >> fedora specific bug. However I would have expected their to be a fix >> for this in fedora. Especially this long after the bug manifested >> itself. Has there been any work on this lately? How far has it gotten? >> At this rate Fedora has essentially become useless on my comp. as I >> cannot even boot to install it. The only way I know how is to install >> a minimal fc6 and upgrade. Which still doesn't fix the problem as I am >> force to stick to FC6 kernels. Any news? >Have you filed a bug including the details of your hardware? Otherwise, >it's really hard to be able to figure out exactly what's broken. >Jeremy No, I have not. Because on checking this bug tracker https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=Fedora7LiveCD and many of the problems stated here are essentially the same thing that I was facing. I was told the no /dev/root problem is now "fixed". But it appears that it has not been. Or that it was fixed yet there was another problem that came in. I believe it has something to do with the issues addressed here. http://kernelslacker.livejournal.com/72836.html From sundaram at fedoraproject.org Fri Apr 13 09:28:17 2007 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Fri, 13 Apr 2007 14:58:17 +0530 Subject: [Fedora-livecd-list] Booting Test Live-cds fails In-Reply-To: References: Message-ID: <461F4D31.4080606@fedoraproject.org> Ahm ed wrote: > > No, I have not. Because on checking this bug tracker > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=Fedora7LiveCD > and many of the problems stated here are essentially the same thing > that I was facing. That is not very useful. A tracker bug is a list of other bugs. Not a place to report bugs directly and piling unrelated ones makes it very inefficient. If you want the issue to be fixed you need to file a *separate bug report*. > I was told the no /dev/root problem is now "fixed". But it appears > that it has not been. This is hardware specific apparently so what is fixed for others might not be for you. You need to file a bug report with your hardware information. Rahul From markmc at redhat.com Fri Apr 13 09:52:09 2007 From: markmc at redhat.com (Mark McLoughlin) Date: Fri, 13 Apr 2007 10:52:09 +0100 Subject: [Fedora-livecd-list] [PATCH] livecd-creator : implement kickstart "network" command In-Reply-To: <1176312552.20921.3.camel@blaa> References: <1176298870.15779.1.camel@blaa> <1176311752.13648.10.camel@aglarond.local> <1176312552.20921.3.camel@blaa> Message-ID: <1176457930.8399.0.camel@blaa> On Wed, 2007-04-11 at 18:29 +0100, Mark McLoughlin wrote: > On Wed, 2007-04-11 at 13:15 -0400, Jeremy Katz wrote: > > On Wed, 2007-04-11 at 14:41 +0100, Mark McLoughlin wrote: > > > Here's a patch which takes a stab at implementing kickstart's network > > > command in livecd-creator. > > > > This ends up changing the behavior, though, in the case that you don't > > have a network line at all (which is pretty reasonable to do, especially > > if you're setting up for NetworkManager). Also, if you have multiple > > network lines and the first specifies the hostname, then it gets > > overriden by later ones. > > So, what you're basically saying is that writeNetworkConfig(), > writeNetworkHosts() and writeNetworkResolv() should not be called per > network line, but rather at the end either with values collected from > the network lines in aggregate, or default values where there are no > network lines? This should do it, I think ... Cheers, Mark. -------------- next part -------------- A non-text attachment was scrubbed... Name: livecd-kickstart-network-config.patch Type: text/x-patch Size: 6522 bytes Desc: not available URL: From markmc at redhat.com Fri Apr 13 17:13:20 2007 From: markmc at redhat.com (Mark McLoughlin) Date: Fri, 13 Apr 2007 18:13:20 +0100 Subject: [Fedora-livecd-list] Fix yum to not look at host config Message-ID: <1176484400.10507.13.camel@blaa> Hey, So, I've been seeing two symptoms which suggested that yum was looking at the hosts config/cache, when clearly the code is trying it's best not to: 1) If a repo in the host's config was broken, it would die in doConfigSetup() - e.g. if the host which the repo is on couldn't be contacted 2) The livecd repos were clearly being at least partly cached outside the install root - e.g. because /var/cache/yum/a-dev gets created. Attached is a patch which fixes this, I think. It writes out its own yum.conf so that the host's repos never get initialised and uses the installroot config item which seems to do a better job of restricting yum to the install root. Oh, another side effect is that you can now use a repo called fedora-development :-) There's one fly in the ointment, though - now that we're properly caching in the install root, we hit a bug whereby we can't tell yum to close these caches before we unmount. See: https://bugzilla.redhat.com/236409 The second patch I've attached is a pretty brute force workaround for this. Cheers, Mark. -------------- next part -------------- A non-text attachment was scrubbed... Name: livecd-yum-config.patch Type: text/x-patch Size: 2383 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: livecd-close-fds.patch Type: text/x-patch Size: 894 bytes Desc: not available URL: From kanarip at kanarip.com Sun Apr 15 10:28:28 2007 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Sun, 15 Apr 2007 12:28:28 +0200 Subject: [Fedora-livecd-list] [Patch] setting root password Message-ID: <4621FE4C.5080701@kanarip.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is an attempt to fix being able to set the root password from kickstart. Kind regards, Jeroen van Meeuwen - -kanarip -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFGIf5LKN6f2pNCvwgRAv6OAJwJSR12vJFpLjj/N4CSPVPc91NXxACgyRIa nJEiIvWIjQbukKThHBc6le4= =1ef2 -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: livecd-rootpassword.patch Type: text/x-patch Size: 1434 bytes Desc: not available URL: From jdogalt at yahoo.com Mon Apr 16 00:34:04 2007 From: jdogalt at yahoo.com (Jane Dogalt) Date: Sun, 15 Apr 2007 17:34:04 -0700 (PDT) Subject: [Fedora-livecd-list] [SCRIPT] simple tool for finding large removable packages Message-ID: <787547.74627.qm@web56914.mail.re3.yahoo.com> I don't know if this will help anyone, but here is a script I wrote/use to help me find which packages I might want to remove from a livecd spin. Basically it reverse sorts the installed packages by size, and gives you the package info, as well as which/how-many packages depend on it (and their size). I.e. from an example run on a system, here is the first few lines of output- (and the thing it tells me immediately is that gimp-help is huge, nothing depends on it, and it's probably the first candidate for removal. Of course, what I'd like it to also tell me is that gimp-help has something to do with an image manipulation program, but the rpm desc is a little deficient in that regard IMO) ======================================================================== (203.48MB) openoffice.org-core is NOT removable ------------------------------------------------------------------------ number of packages that are dependent: 7 biggest deps are openoffice.org-calc(14.81MB) openoffice.org-writer(5.78MB) openoffice.org-impress(4.28MB) ------------------------------------------------------------------------ package description: openoffice.org-core-2.0.2-5.12.2 core libraries and support files for openoffice.org ======================================================================== ======================================================================== (64.05MB) gimp-help is removable ------------------------------------------------------------------------ package description: gimp-help-2-0.1.0.10.0.fc5.1 The GIMP User Manual is a newly written User Manual for the GIMP. ======================================================================== ======================================================================== (61.25MB) glibc-common is NOT removable ------------------------------------------------------------------------ number of packages that are dependent: 2 biggest deps are glibc(11.66MB) redhat-lsb(.02MB) ------------------------------------------------------------------------ package description: glibc-common-2.4-8 ... ... and so on... (consider the script GPL) __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -------------- next part -------------- A non-text attachment was scrubbed... Name: sysinfo Type: application/octet-stream Size: 3342 bytes Desc: 4147804775-sysinfo URL: From kanarip at kanarip.com Sun Apr 15 12:25:33 2007 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Sun, 15 Apr 2007 14:25:33 +0200 Subject: [Fedora-livecd-list] [Patch] setting root password In-Reply-To: <4621FE4C.5080701@kanarip.com> References: <4621FE4C.5080701@kanarip.com> Message-ID: <462219BD.1080202@kanarip.com> Jeroen van Meeuwen wrote: > This is an attempt to fix being able to set the root password from > kickstart. > My bad, I used kshandler.rootpw.rootpw instead of kshandler.rootpw.password. Kind regards, Jeroen van Meeuwen -kanarip -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: livecd-rootpassword.patch URL: From katzj at redhat.com Mon Apr 16 14:40:23 2007 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 16 Apr 2007 10:40:23 -0400 Subject: [Fedora-livecd-list] [Patch] setting root password In-Reply-To: <4621FE4C.5080701@kanarip.com> References: <4621FE4C.5080701@kanarip.com> Message-ID: <1176734423.13833.26.camel@aglarond.local> On Sun, 2007-04-15 at 12:28 +0200, Jeroen van Meeuwen wrote: > This is an attempt to fix being able to set the root password from > kickstart. This changes the behavior, though. A blank password isn't the same as setting the passwd to empty with -d. So you need to check for a lack of a root pass and still set it with -d. Also, instead of essentially running sed on /etc/shadow for the case of a crypted password, you can use usermod -p. Or it could use libuser like anaconda currently does, but that's probably overkill. Jeremy From katzj at redhat.com Mon Apr 16 14:41:34 2007 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 16 Apr 2007 10:41:34 -0400 Subject: [Fedora-livecd-list] [SCRIPT] simple tool for finding large removable packages In-Reply-To: <787547.74627.qm@web56914.mail.re3.yahoo.com> References: <787547.74627.qm@web56914.mail.re3.yahoo.com> Message-ID: <1176734494.13833.28.camel@aglarond.local> On Sun, 2007-04-15 at 17:34 -0700, Jane Dogalt wrote: > I don't know if this will help anyone, but here is a script I wrote/use > to help me find which packages I might want to remove from a livecd > spin. Cool. We should really have a place for people to be able to find useful little scripts like this easily. Jeremy From kanarip at kanarip.com Mon Apr 16 15:25:31 2007 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Mon, 16 Apr 2007 17:25:31 +0200 Subject: [Fedora-livecd-list] [Patch] setting root password In-Reply-To: <1176734423.13833.26.camel@aglarond.local> References: <4621FE4C.5080701@kanarip.com> <1176734423.13833.26.camel@aglarond.local> Message-ID: <4623956B.5070404@kanarip.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jeremy Katz wrote: > On Sun, 2007-04-15 at 12:28 +0200, Jeroen van Meeuwen wrote: >> This is an attempt to fix being able to set the root password from >> kickstart. > > This changes the behavior, though. A blank password isn't the same as > setting the passwd to empty with -d. So you need to check for a lack of > a root pass and still set it with -d. > > Also, instead of essentially running sed on /etc/shadow for the case of > a crypted password, you can use usermod -p. Or it could use libuser > like anaconda currently does, but that's probably overkill. > > Jeremy > Good point. Improvements attached. Kind regards, Jeroen van Meeuwen - -kanarip -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGI5VrKN6f2pNCvwgRAjExAKCtuSlRrmVHyLjOkodp0k58tkbMiQCcCD6W wBC8dBcoqCOE73yISXDwJW4= =5YmH -----END PGP SIGNATURE----- -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: livecd-rootpassword.patch URL: From kanarip at kanarip.com Mon Apr 16 15:31:46 2007 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Mon, 16 Apr 2007 17:31:46 +0200 Subject: [Fedora-livecd-list] [Patch] specify custom directories Message-ID: <462396E2.2000305@kanarip.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Attached is a patch to customize the build_dir, yum cachedir and yum installroot. Hope you find it usefull. Kind regards, Jeroen van Meeuwen - -kanarip -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGI5biKN6f2pNCvwgRAs0fAJ9yOMmYVobrSejxMG+KbwVDKzC6OgCgkqTw HpfvOja4CKtUfA1psUWfM+s= =ibd4 -----END PGP SIGNATURE----- -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: livecd-directories.patch URL: From jdogalt at yahoo.com Mon Apr 16 16:39:10 2007 From: jdogalt at yahoo.com (Jane Dogalt) Date: Mon, 16 Apr 2007 09:39:10 -0700 (PDT) Subject: [Fedora-livecd-list] [SCRIPT] simple tool for finding large removable packages In-Reply-To: <1176734494.13833.28.camel@aglarond.local> Message-ID: <508288.42628.qm@web56904.mail.re3.yahoo.com> --- Jeremy Katz wrote: > On Sun, 2007-04-15 at 17:34 -0700, Jane Dogalt wrote: > > I don't know if this will help anyone, but here is a script I > wrote/use > > to help me find which packages I might want to remove from a livecd > > spin. > > Cool. We should really have a place for people to be able to find > useful little scripts like this easily. I know there is the wiki where I'm guessing some old stuff is still collected from the kadischi days. But this didn't seem long enough or polished enough to be worth the bother. I figure if it's truly useful enough, someone will rewrite it nicely in python for me :) -dmc/jdog __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From katzj at redhat.com Mon Apr 16 20:05:23 2007 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 16 Apr 2007 16:05:23 -0400 Subject: [Fedora-livecd-list] [PATCH] livecd-creator : implement kickstart "network" command In-Reply-To: <1176457930.8399.0.camel@blaa> References: <1176298870.15779.1.camel@blaa> <1176311752.13648.10.camel@aglarond.local> <1176312552.20921.3.camel@blaa> <1176457930.8399.0.camel@blaa> Message-ID: <1176753923.5811.11.camel@aglarond.local> On Fri, 2007-04-13 at 10:52 +0100, Mark McLoughlin wrote: > On Wed, 2007-04-11 at 18:29 +0100, Mark McLoughlin wrote: > > On Wed, 2007-04-11 at 13:15 -0400, Jeremy Katz wrote: > > > On Wed, 2007-04-11 at 14:41 +0100, Mark McLoughlin wrote: > > > > Here's a patch which takes a stab at implementing kickstart's network > > > > command in livecd-creator. > > > > > > This ends up changing the behavior, though, in the case that you don't > > > have a network line at all (which is pretty reasonable to do, especially > > > if you're setting up for NetworkManager). Also, if you have multiple > > > network lines and the first specifies the hostname, then it gets > > > overriden by later ones. > > > > So, what you're basically saying is that writeNetworkConfig(), > > writeNetworkHosts() and writeNetworkResolv() should not be called per > > network line, but rather at the end either with values collected from > > the network lines in aggregate, or default values where there are no > > network lines? > > This should do it, I think ... Looks good. Committed with the tiny fix of using /etc/hosts instead of /etc/sysconfig hosts. Jeremy From katzj at redhat.com Mon Apr 16 20:41:32 2007 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 16 Apr 2007 16:41:32 -0400 Subject: [Fedora-livecd-list] [Patch] setting root password In-Reply-To: <4623956B.5070404@kanarip.com> References: <4621FE4C.5080701@kanarip.com> <1176734423.13833.26.camel@aglarond.local> <4623956B.5070404@kanarip.com> Message-ID: <1176756092.5811.14.camel@aglarond.local> On Mon, 2007-04-16 at 17:25 +0200, Jeroen van Meeuwen wrote: > Jeremy Katz wrote: > > On Sun, 2007-04-15 at 12:28 +0200, Jeroen van Meeuwen wrote: > >> This is an attempt to fix being able to set the root password from > >> kickstart. > > > > This changes the behavior, though. A blank password isn't the same as > > setting the passwd to empty with -d. So you need to check for a lack of > > a root pass and still set it with -d. > > > > Also, instead of essentially running sed on /etc/shadow for the case of > > a crypted password, you can use usermod -p. Or it could use libuser > > like anaconda currently does, but that's probably overkill. > > Good point. Improvements attached. Looks good and applied. Thanks. Jeremy From katzj at redhat.com Mon Apr 16 20:54:46 2007 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 16 Apr 2007 16:54:46 -0400 Subject: [Fedora-livecd-list] [Patch] specify custom directories In-Reply-To: <462396E2.2000305@kanarip.com> References: <462396E2.2000305@kanarip.com> Message-ID: <1176756886.5811.20.camel@aglarond.local> On Mon, 2007-04-16 at 17:31 +0200, Jeroen van Meeuwen wrote: > Attached is a patch to customize the build_dir, yum cachedir and yum > installroot. build dir and cachedir make sense to me[1], but what's the value in setting install_root explicitly? And as it stands, you're not even using the value since there are lots of other places where we expect that the install root is builddir/install_root. Jeremy [1] builddir to point to some form of shared storage or just somewhere with more space than /var/tmp. And the yum cache so that if you have things previously downloaded and cached, you can then take advantage of them From katzj at redhat.com Mon Apr 16 21:25:03 2007 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 16 Apr 2007 17:25:03 -0400 Subject: [Fedora-livecd-list] Fix yum to not look at host config In-Reply-To: <1176484400.10507.13.camel@blaa> References: <1176484400.10507.13.camel@blaa> Message-ID: <1176758703.5811.23.camel@aglarond.local> On Fri, 2007-04-13 at 18:13 +0100, Mark McLoughlin wrote: > So, I've been seeing two symptoms which suggested that yum was looking > at the hosts config/cache, when clearly the code is trying it's best not > to: [snip] > Attached is a patch which fixes this, I think. It writes out its own > yum.conf so that the host's repos never get initialised and uses the > installroot config item which seems to do a better job of restricting > yum to the install root. Looks pretty good. I need to finish up the generic changes so that you can just define a yum config object without having to do the file parsing I think, but this is good for now :) > There's one fly in the ointment, though - now that we're properly > caching in the install root, we hit a bug whereby we can't tell yum to > close these caches before we unmount. See: > https://bugzilla.redhat.com/236409 > The second patch I've attached is a pretty brute force workaround for > this. Ugly, but it'll work for the moment. And we'll get something like that added into upstream yum and can then switch over to using that for here. Committed Jeremy From ml at deadbabylon.de Tue Apr 17 08:51:51 2007 From: ml at deadbabylon.de (Sebastian Vahl) Date: Tue, 17 Apr 2007 10:51:51 +0200 Subject: [Fedora-livecd-list] Suggestion: Define temporary directory Message-ID: <200704171052.08661.ml@deadbabylon.de> Hi. Since livecd-creator is using variable temporary directories under /var/tmp/livecd-creator-* it is not possible anymore to use a link to another partition. But especially when creating dvds I do not have enough free space in /var/tmp. So it would be nice to have an option to define the temporary directory that should be used. Or am I missing something here? Sebastian -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From ml at deadbabylon.de Tue Apr 17 10:39:10 2007 From: ml at deadbabylon.de (Sebastian Vahl) Date: Tue, 17 Apr 2007 12:39:10 +0200 Subject: [Fedora-livecd-list] Suggestion: Submenu in isolinux for locales In-Reply-To: <1176238464.3025.35.camel@aglarond.local> References: <20070410222548.4dcbba74@localhost.localdomain> <1176238464.3025.35.camel@aglarond.local> Message-ID: <200704171239.16767.ml@deadbabylon.de> Am Di 10.April 2007 schrieb Jeremy Katz: > On Tue, 2007-04-10 at 22:25 +0200, Sebastian Vahl wrote: > > Don't know if this is possible with isolinux: It would be much easier > > for non-english users if they could choose their language at the > > bootmenu. I know that they could attach eg. "live_locale=de_DE.UTF-8". > > But a menu or submenu for non-experienced users would be the best, I > > think. > > The problem is that doing this in the bootloader is really not at all > ideal. You don't have any ability to have a11y and bootloaders suck to > hack on. > > This is why the GNOME live CD goes to gdm instead of just doing > automatic login now. With the facebrowser, you can select the user and > you can also select the language pretty easily That works for gdm. But sadly kdm do not have such an option. I think I must rethink this. Sebastian -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From rdieter at math.unl.edu Tue Apr 17 11:19:37 2007 From: rdieter at math.unl.edu (Rex Dieter) Date: Tue, 17 Apr 2007 06:19:37 -0500 Subject: [Fedora-livecd-list] Re: Suggestion: Submenu in isolinux for locales In-Reply-To: <200704171239.16767.ml@deadbabylon.de> References: <20070410222548.4dcbba74@localhost.localdomain> <1176238464.3025.35.camel@aglarond.local> <200704171239.16767.ml@deadbabylon.de> Message-ID: Sebastian Vahl wrote: > Am Di 10.April 2007 schrieb Jeremy Katz: >> This is why the GNOME live CD goes to gdm instead of just doing >> automatic login now. With the facebrowser, you can select the user and >> you can also select the language pretty easily > That works for gdm. But sadly kdm do not have such an option. > I think I must rethink this. Or (heaven-forbid) consider installing/using gdm. :) -- Rex From katzj at redhat.com Tue Apr 17 14:46:58 2007 From: katzj at redhat.com (Jeremy Katz) Date: Tue, 17 Apr 2007 10:46:58 -0400 Subject: [Fedora-livecd-list] Suggestion: Define temporary directory In-Reply-To: <200704171052.08661.ml@deadbabylon.de> References: <200704171052.08661.ml@deadbabylon.de> Message-ID: <1176821218.22139.5.camel@aglarond.local> On Tue, 2007-04-17 at 10:51 +0200, Sebastian Vahl wrote: > Since livecd-creator is using variable temporary directories > under /var/tmp/livecd-creator-* it is not possible anymore to use a link to > another partition. But especially when creating dvds I do not have enough > free space in /var/tmp. > So it would be nice to have an option to define the temporary directory that > should be used. That's one thing that kanarip's patch yesterday was addressing Jeremy From ml at deadbabylon.de Tue Apr 17 19:02:15 2007 From: ml at deadbabylon.de (Sebastian Vahl) Date: Tue, 17 Apr 2007 21:02:15 +0200 Subject: [Fedora-livecd-list] Suggestion: Define temporary directory In-Reply-To: <1176821218.22139.5.camel@aglarond.local> References: <200704171052.08661.ml@deadbabylon.de> <1176821218.22139.5.camel@aglarond.local> Message-ID: <20070417210215.3e264594@localhost.localdomain> Am Tue, 17 Apr 2007 10:46:58 -0400 schrieb Jeremy Katz : > On Tue, 2007-04-17 at 10:51 +0200, Sebastian Vahl wrote: > > Since livecd-creator is using variable temporary directories > > under /var/tmp/livecd-creator-* it is not possible anymore to use a > > link to another partition. But especially when creating dvds I do > > not have enough free space in /var/tmp. > > So it would be nice to have an option to define the temporary > > directory that should be used. > > That's one thing that kanarip's patch yesterday was addressing Ok. Thanks. Sebastian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From shankuo at gmail.com Wed Apr 18 07:57:46 2007 From: shankuo at gmail.com (SK Lim) Date: Wed, 18 Apr 2007 15:57:46 +0800 Subject: [Fedora-livecd-list] FATAL:Modules pata_xxxx Not Found Message-ID: <76553df40704180057o66db4911l2c1003c77b8af76f@mail.gmail.com> Using FC 6 (2.6.18-1.2798.fc6), fedore-livecd-6.91-2.noarch.rpm, fedora-lived-gnome-6.91.2.noarch.rpm, fedora-livecd-desktop-6.91-2.noarch.rpm and live-cd livecd-tools-001-3.fc7.i38 to create barebone live-cd from instructions on this web http://fedoraproject.org/wiki/FedoraLiveCD/LiveCDHowTo I get the following messages :- warning: device-mapper-1.02.07-3: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2 Installed: bash.i386 0:3.1-16.1 grub.i386 0:0.97-13 kernel.i686 0: 2.6.18-1.2798.fc6 Dependency Installed: MAKEDEV.i386 0:3.23-1.2 SysVinit.i386 0:2.86-14 audit-libs.i386 0:1.2.8-1.fc6 basesystem.noarch 0:8.0-5.1.1 bzip2-libs.i3860: 1.0.3-3 chkconfig.i386 0:1.3.30-1 coreutils.i386 0:5.97-11 cpio.i386 0: 2.6-19 cracklib.i386 0:2.8.9-3.1 cracklib-dicts.i386 0:2.8.9-3.1 db4.i386 0: 4.3.29-9.fc6 device-mapper.i386 0:1.02.07-3 diffutils.i386 0:2.8.1-15.2.2 dmraid.i386 0:1.0.0.rc13-1.fc6 e2fsprogs.i386 0:1.39-7 e2fsprogs-libs.i3860: 1.39-7 ethtool.i386 0:3-1.2.2 fedora-logos.noarch 0:6.0.6-1.fc6 fedora-release.noarch 0:6-4 fedora-release-notes.noarch 0:6-3 filesystem.i386 0:2.4.0-1 findutils.i386 1:4.2.27-4.1 gawk.i386 0:3.1.5-11 gdbm.i386 0:1.8.0-26.2.1 glib2.i386 0:2.12.3-2.fc6 glibc.i686 0:2.5-3 glibc-common.i386 0:2.5-3 grep.i386 0:2.5.1-54.1 gzip.i386 0:1.3.5-9 info.i386 0:4.8-11.1 initscripts.i386 0:8.45.3-1 iproute.i386 0:2.6.16-6.fc6 iputils.i386 0:20020927-41.fc6 kpartx.i386 0:0.4.7-5 krb5-libs.i386 0:1.5-7 less.i386 0:394-4.1 libacl.i386 0:2.2.39-1.1 libattr.i386 0:2.4.32-1.1 libcap.i386 0:1.10-25 libgcc.i386 0:4.1.1-30 libselinux.i386 0:1.30.29-2 libsepol.i386 0:1.12.27-1 libstdc++.i386 0:4.1.1-30 libtermcap.i386 0: 2.0.8-46.1 lvm2.i386 0:2.02.06-4 mcstrans.i386 0:0.1.8-3 mingetty.i386 0: 1.07-5.2.2 mkinitrd.i386 0:5.1.19-1 mktemp.i386 3:1.5-23.2.2 module-init-tools.i386 0:3.3-0.pre1.4.17 nash.i386 0:5.1.19-1 ncurses.i3860: 5.5-24.20060715 net-tools.i386 0:1.60-73 openssl.i686 0:0.9.8b-8 pam.i386 0: 0.99.6.2-3.fc6 pcre.i386 0:6.6-1.1 popt.i386 0:1.10.2-32 procps.i386 0: 3.2.7-8 psmisc.i386 0:22.2-5 python.i386 0:2.4.3-18.fc6 readline.i386 0: 5.1-1.1 sed.i386 0:4.1.5-5.fc6 setup.noarch 0:2.5.55-1 shadow-utils.i386 2: 4.0.17-5 sysklogd.i386 0:1.4.1-39.2 tar.i386 2:1.15.1-19 termcap.noarch 1: 5.5-1.20060701.1 tzdata.noarch 0:2006m-2.fc6 udev.i386 0:095-14 util-linux.i386 0:2.13-0.44.fc6 zlib.i386 0:1.2.3-3 Building an initramfs at /boot/livecd-initramfs.img for kernel 2.6.18-1.2798.fc6 FATAL: Module usbhid not found. FATAL: Module ata_generic not found. FATAL: Module pata_ali not found. FATAL: Module pata_amd not found. FATAL: Module pata_artop not found. FATAL: Module pata_atiixp not found. FATAL: Module pata_cmd64x not found. FATAL: Module pata_cs5520 not found. FATAL: Module pata_cs5530 not found. FATAL: Module pata_cs5535 not found. FATAL: Module pata_cypress not found. FATAL: Module pata_efar not found. FATAL: Module pata_hpt366 not found. FATAL: Module pata_hpt37x not found. FATAL: Module pata_hpt3x2n not found. FATAL: Module pata_hpt3x3 not found. FATAL: Module pata_isapnp not found. FATAL: Module pata_it821x not found. FATAL: Module pata_jmicron not found. FATAL: Module pata_marvell not found. FATAL: Module pata_mpiix not found. FATAL: Module pata_netcell not found. FATAL: Module pata_ns87410 not found. FATAL: Module pata_oldpiix not found. FATAL: Module pata_optidma not found. FATAL: Module pata_opti not found. FATAL: Module pata_pcmcia not found. FATAL: Module pata_pdc2027x not found. FATAL: Module pata_pdc202xx_old not found. FATAL: Module pata_qdi not found. FATAL: Module pata_serverworks not found. FATAL: Module pata_sil680 not found. FATAL: Module pata_sis not found. FATAL: Module pata_sl82c105 not found. FATAL: Module pata_triflex not found. FATAL: Module pata_via not found. cp: cannot stat `/usr/sbin/eject': No such file or directory cp: cannot stat `/usr/bin/tree': No such file or directory Done; initramfs is 2.9M. Error during installation... [root at livecd ~]# What are the module pata_xxx not found and where do I get these modules? -------------- next part -------------- An HTML attachment was scrubbed... URL: From vladimir.shebordaev at gmail.com Wed Apr 18 09:53:02 2007 From: vladimir.shebordaev at gmail.com (Vladimir Shebordaev) Date: Wed, 18 Apr 2007 13:53:02 +0400 Subject: [Fedora-livecd-list] FATAL:Modules pata_xxxx Not Found In-Reply-To: <76553df40704180057o66db4911l2c1003c77b8af76f@mail.gmail.com> References: <76553df40704180057o66db4911l2c1003c77b8af76f@mail.gmail.com> Message-ID: <4625EA7E.2030707@gmail.com> Hi! Basically, those modules are to be installed on initrd. You have tried rather outdated David's scripts. Please try the latest ones from FC7 Extras development (source) repo. Jeremy is working hard to make the things better for all of us. You will sure have to manually edit a kickstart script to make the exact list of the modules you need before your root filesystem is mounted. In the hope it helps. Regards, Vladimir SK Lim ?????: > Using FC 6 (2.6.18-1.2798.fc6), > fedore-livecd-6.91-2.noarch.rpm,fedora-lived-gnome-6.91.2.noarch.rpm, > fedora-livecd-desktop-6.91-2.noarch.rpm and live-cd > livecd-tools-001-3.fc7.i38 to create barebone live-cd from instructions > on this web > http://fedoraproject.org/wiki/FedoraLiveCD/LiveCDHowTo > > I get the following messages :- > > warning: device-mapper-1.02.07-3: Header V3 DSA signature: NOKEY, key ID > 4f2a6fd2 > > Installed: bash.i386 0:3.1-16.1 grub.i386 0:0.97-13 kernel.i686 > 0:2.6.18-1.2798.fc6 > Dependency Installed: MAKEDEV.i386 0:3.23-1.2 SysVinit.i386 0:2.86-14 > audit-libs.i386 0:1.2.8-1.fc6 basesystem.noarch 0:8.0-5.1.1 > bzip2-libs.i386 0:1.0.3-3 chkconfig.i386 0:1.3.30-1 coreutils.i386 > 0:5.97-11 cpio.i386 0:2.6-19 cracklib.i386 0:2.8.9-3.1 > cracklib-dicts.i386 0:2.8.9-3.1 db4.i386 0:4.3.29-9.fc6 > device-mapper.i386 0:1.02.07-3 diffutils.i386 0:2.8.1-15.2.2 dmraid.i386 > 0:1.0.0.rc13-1.fc6 e2fsprogs.i386 0:1.39-7 e2fsprogs-libs.i386 0:1.39-7 > ethtool.i386 0:3-1.2.2 fedora-logos.noarch 0:6.0.6-1.fc6 > fedora-release.noarch 0:6-4 fedora-release-notes.noarch 0:6-3 > filesystem.i386 0:2.4.0-1 findutils.i386 1:4.2.27-4.1 gawk.i386 > 0:3.1.5-11 gdbm.i386 0:1.8.0-26.2.1 glib2.i386 0:2.12.3-2.fc6 glibc.i686 > 0:2.5-3 glibc-common.i386 0:2.5-3 grep.i386 0:2.5.1-54.1 gzip.i386 > 0:1.3.5-9 info.i386 0:4.8-11.1 initscripts.i386 0:8.45.3-1 iproute.i386 > 0:2.6.16-6.fc6 iputils.i386 0:20020927-41.fc6 kpartx.i386 0:0.4.7-5 > krb5-libs.i386 0:1.5-7 less.i386 0:394-4.1 libacl.i386 0:2.2.39-1.1 > libattr.i386 0:2.4.32-1.1 libcap.i386 0:1.10-25 libgcc.i386 0: 4.1.1-30 > libselinux.i386 0:1.30.29-2 libsepol.i386 0:1.12.27-1 libstdc++.i386 > 0:4.1.1-30 libtermcap.i386 0:2.0.8-46.1 lvm2.i386 0:2.02.06-4 > mcstrans.i386 0:0.1.8-3 mingetty.i386 0:1.07-5.2.2 mkinitrd.i386 > 0:5.1.19-1 mktemp.i386 3:1.5-23.2.2 module-init-tools.i386 > 0:3.3-0.pre1.4.17 nash.i386 0:5.1.19-1 ncurses.i386 0:5.5-24.20060715 > net-tools.i386 0:1.60-73 openssl.i686 0:0.9.8b-8 pam.i386 > 0:0.99.6.2-3.fc6 pcre.i386 0:6.6-1.1 popt.i386 0:1.10.2-32 procps.i386 > 0:3.2.7-8 psmisc.i386 0:22.2-5 python.i386 0:2.4.3-18.fc6 readline.i386 > 0:5.1-1.1 sed.i386 0:4.1.5-5.fc6 setup.noarch 0:2.5.55-1 > shadow-utils.i386 2:4.0.17-5 sysklogd.i386 0:1.4.1-39.2 tar.i386 > 2:1.15.1-19 termcap.noarch 1:5.5-1.20060701.1 tzdata.noarch > 0:2006m-2.fc6 udev.i386 0:095-14 util-linux.i386 0:2.13-0.44.fc6 > zlib.i386 0:1.2.3-3 > Building an initramfs at /boot/livecd-initramfs.img for kernel > 2.6.18-1.2798.fc6 > FATAL: Module usbhid not found. > FATAL: Module ata_generic not found. > FATAL: Module pata_ali not found. > FATAL: Module pata_amd not found. > FATAL: Module pata_artop not found. > FATAL: Module pata_atiixp not found. > FATAL: Module pata_cmd64x not found. > FATAL: Module pata_cs5520 not found. > FATAL: Module pata_cs5530 not found. > FATAL: Module pata_cs5535 not found. > FATAL: Module pata_cypress not found. > FATAL: Module pata_efar not found. > FATAL: Module pata_hpt366 not found. > FATAL: Module pata_hpt37x not found. > FATAL: Module pata_hpt3x2n not found. > FATAL: Module pata_hpt3x3 not found. > FATAL: Module pata_isapnp not found. > FATAL: Module pata_it821x not found. > FATAL: Module pata_jmicron not found. > FATAL: Module pata_marvell not found. > FATAL: Module pata_mpiix not found. > FATAL: Module pata_netcell not found. > FATAL: Module pata_ns87410 not found. > FATAL: Module pata_oldpiix not found. > FATAL: Module pata_optidma not found. > FATAL: Module pata_opti not found. > FATAL: Module pata_pcmcia not found. > FATAL: Module pata_pdc2027x not found. > FATAL: Module pata_pdc202xx_old not found. > FATAL: Module pata_qdi not found. > FATAL: Module pata_serverworks not found. > FATAL: Module pata_sil680 not found. > FATAL: Module pata_sis not found. > FATAL: Module pata_sl82c105 not found. > FATAL: Module pata_triflex not found. > FATAL: Module pata_via not found. > cp: cannot stat `/usr/sbin/eject': No such file or directory > cp: cannot stat `/usr/bin/tree': No such file or directory > Done; initramfs is 2.9M. > > Error during installation... > [root at livecd ~]# > > What are the module pata_xxx not found and where do I get these modules? > > > > ------------------------------------------------------------------------ > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list From kanarip at kanarip.com Wed Apr 18 12:48:10 2007 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Wed, 18 Apr 2007 14:48:10 +0200 Subject: [Fedora-livecd-list] [Patch] specify custom directories In-Reply-To: <1176756886.5811.20.camel@aglarond.local> References: <462396E2.2000305@kanarip.com> <1176756886.5811.20.camel@aglarond.local> Message-ID: <4626138A.9030007@kanarip.com> Jeremy Katz wrote: > On Mon, 2007-04-16 at 17:31 +0200, Jeroen van Meeuwen wrote: >> Attached is a patch to customize the build_dir, yum cachedir and yum >> installroot. > > build dir and cachedir make sense to me[1], but what's the value in > setting install_root explicitly? And as it stands, you're not even > using the value since there are lots of other places where we expect > that the install root is builddir/install_root. > That is why the yum_installroot passed is actually being symlinked from builddir/install_root. line ~34 in the patch. This allows a yum object already initialized to keep the installroot yet "install into builddir/install_root". Kind regards, Jeroen van Meeuwen -kanarip From katzj at redhat.com Wed Apr 18 13:36:35 2007 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 18 Apr 2007 09:36:35 -0400 Subject: [Fedora-livecd-list] [Patch] specify custom directories In-Reply-To: <4626138A.9030007@kanarip.com> References: <462396E2.2000305@kanarip.com> <1176756886.5811.20.camel@aglarond.local> <4626138A.9030007@kanarip.com> Message-ID: <1176903395.15165.4.camel@aglarond.local> On Wed, 2007-04-18 at 14:48 +0200, Jeroen van Meeuwen wrote: > Jeremy Katz wrote: > > On Mon, 2007-04-16 at 17:31 +0200, Jeroen van Meeuwen wrote: > >> Attached is a patch to customize the build_dir, yum cachedir and yum > >> installroot. > > > > build dir and cachedir make sense to me[1], but what's the value in > > setting install_root explicitly? And as it stands, you're not even > > using the value since there are lots of other places where we expect > > that the install root is builddir/install_root. > > That is why the yum_installroot passed is actually being symlinked from > builddir/install_root. line ~34 in the patch. This allows a yum object > already initialized to keep the installroot yet "install into > builddir/install_root". But why do you actually need that? The install_root is where the file system image gets mounted and so if you already have things in a directory, that's not going to help. Jeremy From kanarip at kanarip.com Wed Apr 18 13:50:39 2007 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Wed, 18 Apr 2007 15:50:39 +0200 Subject: [Fedora-livecd-list] [Patch] specify custom directories In-Reply-To: <1176903395.15165.4.camel@aglarond.local> References: <462396E2.2000305@kanarip.com> <1176756886.5811.20.camel@aglarond.local> <4626138A.9030007@kanarip.com> <1176903395.15165.4.camel@aglarond.local> Message-ID: <4626222F.9080703@kanarip.com> Jeremy Katz wrote: > On Wed, 2007-04-18 at 14:48 +0200, Jeroen van Meeuwen wrote: >> Jeremy Katz wrote: >>> On Mon, 2007-04-16 at 17:31 +0200, Jeroen van Meeuwen wrote: >>>> Attached is a patch to customize the build_dir, yum cachedir and yum >>>> installroot. >>> build dir and cachedir make sense to me[1], but what's the value in >>> setting install_root explicitly? And as it stands, you're not even >>> using the value since there are lots of other places where we expect >>> that the install root is builddir/install_root. >> That is why the yum_installroot passed is actually being symlinked from >> builddir/install_root. line ~34 in the patch. This allows a yum object >> already initialized to keep the installroot yet "install into >> builddir/install_root". > > But why do you actually need that? The install_root is where the file > system image gets mounted and so if you already have things in a > directory, that's not going to help. > I do not already have things in a directory (well actually, I do, but I don't care about them being trashed), I have an object pointing to a directory and I cannot change that without destroying and recreating the object. The patch is doing what I need, and afaics is not disruptive to livecd-creator's way of doing things, right? Kind regards, Jeroen van Meeuwen -kanarip From katzj at redhat.com Wed Apr 18 13:59:10 2007 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 18 Apr 2007 09:59:10 -0400 Subject: [Fedora-livecd-list] [Patch] specify custom directories In-Reply-To: <4626222F.9080703@kanarip.com> References: <462396E2.2000305@kanarip.com> <1176756886.5811.20.camel@aglarond.local> <4626138A.9030007@kanarip.com> <1176903395.15165.4.camel@aglarond.local> <4626222F.9080703@kanarip.com> Message-ID: <1176904750.15165.13.camel@aglarond.local> On Wed, 2007-04-18 at 15:50 +0200, Jeroen van Meeuwen wrote: > Jeremy Katz wrote: > > On Wed, 2007-04-18 at 14:48 +0200, Jeroen van Meeuwen wrote: > >> Jeremy Katz wrote: > >>> On Mon, 2007-04-16 at 17:31 +0200, Jeroen van Meeuwen wrote: > >>>> Attached is a patch to customize the build_dir, yum cachedir and yum > >>>> installroot. > >>> build dir and cachedir make sense to me[1], but what's the value in > >>> setting install_root explicitly? And as it stands, you're not even > >>> using the value since there are lots of other places where we expect > >>> that the install root is builddir/install_root. > >> That is why the yum_installroot passed is actually being symlinked from > >> builddir/install_root. line ~34 in the patch. This allows a yum object > >> already initialized to keep the installroot yet "install into > >> builddir/install_root". > > > > But why do you actually need that? The install_root is where the file > > system image gets mounted and so if you already have things in a > > directory, that's not going to help. > > > > I do not already have things in a directory (well actually, I do, but I > don't care about them being trashed), I have an object pointing to a > directory and I cannot change that without destroying and recreating the > object. But what are you trying to do? You just keep talking about objects and implementation details, not about the actual task you're trying to do. What magic is going on that it's so important that this be kept in sync? > The patch is doing what I need, and afaics is not disruptive to > livecd-creator's way of doing things, right? It could have some ... interesting effects across error handling and adds an entirely new class of things there to check for and ensure keep working. Jeremy From kanarip at kanarip.com Wed Apr 18 14:44:03 2007 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Wed, 18 Apr 2007 16:44:03 +0200 Subject: [Fedora-livecd-list] [Patch] specify custom directories In-Reply-To: <1176904750.15165.13.camel@aglarond.local> References: <462396E2.2000305@kanarip.com> <1176756886.5811.20.camel@aglarond.local> <4626138A.9030007@kanarip.com> <1176903395.15165.4.camel@aglarond.local> <4626222F.9080703@kanarip.com> <1176904750.15165.13.camel@aglarond.local> Message-ID: <46262EB3.3060409@kanarip.com> Jeremy Katz wrote: > On Wed, 2007-04-18 at 15:50 +0200, Jeroen van Meeuwen wrote: >> Jeremy Katz wrote: >>> On Wed, 2007-04-18 at 14:48 +0200, Jeroen van Meeuwen wrote: >>>> Jeremy Katz wrote: >>>>> On Mon, 2007-04-16 at 17:31 +0200, Jeroen van Meeuwen wrote: >>>>>> Attached is a patch to customize the build_dir, yum cachedir and yum >>>>>> installroot. >>>>> build dir and cachedir make sense to me[1], but what's the value in >>>>> setting install_root explicitly? And as it stands, you're not even >>>>> using the value since there are lots of other places where we expect >>>>> that the install root is builddir/install_root. >>>> That is why the yum_installroot passed is actually being symlinked from >>>> builddir/install_root. line ~34 in the patch. This allows a yum object >>>> already initialized to keep the installroot yet "install into >>>> builddir/install_root". >>> But why do you actually need that? The install_root is where the file >>> system image gets mounted and so if you already have things in a >>> directory, that's not going to help. >>> >> I do not already have things in a directory (well actually, I do, but I >> don't care about them being trashed), I have an object pointing to a >> directory and I cannot change that without destroying and recreating the >> object. > > But what are you trying to do? You just keep talking about objects and > implementation details, not about the actual task you're trying to do. > What magic is going on that it's so important that this be kept in sync? > As said before, the already existent yum object points at another directory then builddir/install_root and the goal of specifying another install root then builddir/install_root is to be able to preserve the yum object as-is. Bigger picture however is, I'm really trying to allow us to get into livecd-creator what we need for Revisor to be able to exec(). Kind regards, Jeroen van Meeuwen -kanarip From sundaram at fedoraproject.org Wed Apr 18 18:31:11 2007 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Thu, 19 Apr 2007 00:01:11 +0530 Subject: [Fedora-livecd-list] Suggestion for LiveCd Spins In-Reply-To: <5c8fc9850704101206k117c8070h3cb61d2c9b19b757@mail.gmail.com> References: <5c8fc9850704101206k117c8070h3cb61d2c9b19b757@mail.gmail.com> Message-ID: <462663EF.8050600@fedoraproject.org> Blayde wrote: > Hey, > I'm not sure if this is the right place to suggest this, but I think > Gnome Partition Manager should be one of the default packages on the > livecd spins. Although that would require ntfs-3g, it makes > dual-booting Fedora (and hd tweaks) tons easier. Just thought I'd give > my two cents... Jeremy, can you confirm that ntfs-3g and gparted is installed by default in the GNOME live cd? I know it is going to be there in the KDE live cd for test 4. Rahul From kanarip at kanarip.com Wed Apr 18 18:33:05 2007 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Wed, 18 Apr 2007 20:33:05 +0200 Subject: [Fedora-livecd-list] [Patch] specify custom directories In-Reply-To: <4626138A.9030007@kanarip.com> References: <462396E2.2000305@kanarip.com> <1176756886.5811.20.camel@aglarond.local> <4626138A.9030007@kanarip.com> Message-ID: <46266461.2050503@kanarip.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jeroen van Meeuwen wrote: > Jeremy Katz wrote: >> On Mon, 2007-04-16 at 17:31 +0200, Jeroen van Meeuwen wrote: >>> Attached is a patch to customize the build_dir, yum cachedir and yum >>> installroot. >> >> build dir and cachedir make sense to me[1], but what's the value in >> setting install_root explicitly? And as it stands, you're not even >> using the value since there are lots of other places where we expect >> that the install root is builddir/install_root. >> > In an attempt to move forward on this, I'll try and keep in pace with what you tell me. Correct me if I'm wrong, but I understand your view is to either: - - specify the install_root separately and use it all over the script, or - - not allow to modify it at all and basically let the builddir setting specify where the (subdir) install_root is exactly The first of which I'm thinking has the most flexibility. If I was to propose a patch doing exactly that, is there anything else you want me to keep in mind? Kind regards, Jeroen van Meeuwen - -kanarip -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFGJmRhKN6f2pNCvwgRAkk7AKDWy/jee+OoGx+PxbBaRonkw8k6bACfSBa9 ZRsCNSglW68u6BxiyqZUa7o= =1mf8 -----END PGP SIGNATURE----- From sundaram at fedoraproject.org Wed Apr 18 22:49:51 2007 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Thu, 19 Apr 2007 04:19:51 +0530 Subject: [Fedora-livecd-list] Suggestion for LiveCd Spins In-Reply-To: <462663EF.8050600@fedoraproject.org> References: <5c8fc9850704101206k117c8070h3cb61d2c9b19b757@mail.gmail.com> <462663EF.8050600@fedoraproject.org> Message-ID: <4626A08F.7060907@fedoraproject.org> Rahul Sundaram wrote: > Blayde wrote: >> Hey, >> I'm not sure if this is the right place to suggest this, but I think >> Gnome Partition Manager should be one of the default packages on the >> livecd spins. Although that would require ntfs-3g, it makes >> dual-booting Fedora (and hd tweaks) tons easier. Just thought I'd give >> my two cents... > > Jeremy, can you confirm that ntfs-3g and gparted is installed by default > in the GNOME live cd? I know it is going to be there in the KDE live cd > for test 4. > (Replying to myself) Well they are now. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234082 Rahul From katzj at redhat.com Thu Apr 19 16:43:23 2007 From: katzj at redhat.com (Jeremy Katz) Date: Thu, 19 Apr 2007 12:43:23 -0400 Subject: [Fedora-livecd-list] [PATCH] add support for mediachecking the live CD. Message-ID: <11770010033724-git-send-email-katzj@redhat.com> Add support for doing a mediacheck on the live CD. This implants a checksum into the application data area of the iso9660 image using the tools in anaconda and then also checks using tools from anaconda. --- creator/livecd-creator | 7 +++++++ creator/mayflower | 15 +++++++++++++++ 2 files changed, 22 insertions(+), 0 deletions(-) diff --git a/creator/livecd-creator b/creator/livecd-creator index d9707c3..7117043 100755 --- a/creator/livecd-creator +++ b/creator/livecd-creator @@ -877,6 +877,13 @@ label runfromram "-boot-info-table", "-J", "-r", "-hide-rr-moved", "-V", "%s" %(self.fs_label,), "%s/out" %(self.build_dir)]) + # implant an isomd5sum + if os.path.exists("/usr/lib/anaconda-runtime/implantisomd5"): + subprocess.call(["/usr/lib/anaconda-runtime/implantisomd5", + "%s.iso" %(self.fs_label,)]) + else: + print >> sys.stderr, "anaconda-runtime not installed; not setting up mediacheck" + def createSquashFS(self): """create compressed squashfs file system""" if not self.skip_compression: diff --git a/creator/mayflower b/creator/mayflower index f483e1e..ed8c731 100755 --- a/creator/mayflower +++ b/creator/mayflower @@ -170,6 +170,8 @@ cp /bin/grep bin cp /bin/dmesg bin cp /sbin/lsmod sbin +# if we have the iso checker, we want it +[ -x /usr/lib/anaconda-runtime/checkisomd5 ] && cp /usr/lib/anaconda-runtime/checkisomd5 bin # Copy all required shared libs for i in bin/* sbin/* lib/udev/*; do @@ -235,6 +237,7 @@ quiet=0 shell=0 eshell=0 live_ram=0 +check_iso=0 live_locale="" # Parse kernel commandline options @@ -265,6 +268,9 @@ for o in \`cat /proc/cmdline\` ; do live_locale=*) live_locale=\${o#live_locale=} ;; + check) + check_iso=1 + ;; esac done @@ -489,6 +495,15 @@ if [ "\$root" != "mtd0" ] ; then fi +if [ "x\$check_iso" == "x1" -a -x /bin/checkisomd5 -a "x\$rootfstype" == "xiso9660" ]; then + /bin/checkisomd5 --verbose /dev/root + if [ \$? <= 0 ]; then + echo "Are you SURE you want to continue?" + echo "Press Enter to continue or ctrl-alt-del to reboot." + read + fi +fi + if [ "x\$root_ro" == "x1" ] ; then if [ -z \$rootflags ] ; then rootflags="ro" -- 1.5.0.6 From jasperhartline at adelphia.net Sat Apr 21 01:13:12 2007 From: jasperhartline at adelphia.net (Jasper Hartline) Date: Fri, 20 Apr 2007 20:13:12 -0500 Subject: [Fedora-livecd-list] Kadischi: Kadischi package (Chitlesh) Message-ID: <46296528.6010704@adelphia.net> Hello. Chitlesh Goorah, if you could work with me on orphaning the Kadischi package so I can take over the package and the bugzilla section on Kadischi I would appreciate it. I have a new package review in bugzilla right now, and as I understand it I need to contact you to have you orphan the package. Thanks. J. Hartline From xunilarodef at gmail.com Sat Apr 21 06:39:50 2007 From: xunilarodef at gmail.com (Nelson Strother) Date: Sat, 21 Apr 2007 02:39:50 -0400 Subject: [Fedora-livecd-list] partial draft of a LiveOS_README.txt In-Reply-To: <771ef40c0704202313t64f36d2by64b69595811f1db3@mail.gmail.com> References: <771ef40c0704202313t64f36d2by64b69595811f1db3@mail.gmail.com> Message-ID: <771ef40c0704202339o1d4972fdqf539ab50bdce65f2@mail.gmail.com> In the mists of time (on March 26th): https://www.redhat.com/archives/fedora-livecd-list/2007-March/msg00216.html David Zeuthen and Jeremy Katz wrote: >> ... and include a >> README file in that sub directory that explains to the user that this >> USB stick is bootable including what kind of computers it can boot on. >> For example, the README file could mention some FAQ's about older >> computers that can't boot off USB. Perhaps call it README.txt to make >> lives easier on Windows users? > > LiveOS is far better; good call. A README also sounds like a good idea. > Anyone want to volunteer to write one? :-) As the April 26 release date for F7 Test4 approaches, we have an initial partial draft of a LiveOS_README.txt at: http://fedoraproject.org/wiki/FedoraLiveCD/LiveOS_README Please help to complete and improve upon this. Cheers, Nelson From jasperhartline at adelphia.net Sun Apr 22 01:40:43 2007 From: jasperhartline at adelphia.net (Jasper Hartline) Date: Sat, 21 Apr 2007 20:40:43 -0500 Subject: [Fedora-livecd-list] Kadischi package maintainer cannot be found Message-ID: <462ABD1B.6090104@adelphia.net> Hi. I've made several attempts via IRC, in channel #fedora-livecd on irc.freenode.net IRC server to contact Chitlesh Goorah to continue the process of taking over the Kadischi package in Extras. He did not respond to me on IRC, and is not responding to me via email to the fedora-livecd-list at redhat.com either. What should I do to claim responsibility of this package if the maintainer cannot be reached and is not currently making updates to the package? J. Hartline From tjboring at gmail.com Sun Apr 22 03:16:39 2007 From: tjboring at gmail.com (Tim Boring) Date: Sat, 21 Apr 2007 20:16:39 -0700 Subject: [Fedora-livecd-list] Problem creating livecd from a custom config Message-ID: <207b80240704212016x286fc3c6gb4459e69c4899da1@mail.gmail.com> hi! i'm trying to build a custom livecd from a config file using the instructions here http://www-128.ibm.com/developerworks/linux/library/l-fedora-livecd/index.html so i've followed the format of the config file and then created my rpm...these steps appear to complete without any problems. the problem i'm having is when i run the livecd-creator command. here's the command i'm using: ' livecd-creator --repo=livecd,file:///usr/local/fc6/repo --package= mylivecd-0.1-3.i386.rpm --fslabel=LiveCD-1.2' and here's the output/error i'm getting: /bin/cp: cannot create regular file `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/sbin/mayflower': No such file or directory /bin/cp: cannot create regular file `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/sbin/run-init': No such file or directory /usr/sbin/chroot: cannot run command `/sbin/mayflower': No such file or directory /usr/sbin/chroot: cannot run command `/sbin/fixfiles': No such file or directory /bin/cp: cannot stat `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/boot/vmlinuz*': No such file or directory /bin/mv: cannot stat `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/boot/livecd- initramfs.img': No such file or directory /bin/cp: cannot stat `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/usr/share/grub/i386-redhat/stage2_eltorito': No such file or directory /bin/cp: cannot stat `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/boot/grub/splash.xpm.gz': No such file or directory Creating little endian 3.0 filesystem on ../out/squashfs.img, block size 65536. Little endian filesystem, data block size 65536, compressed data, compressed metadata, compressed fragments Filesystem size 4072.30 Kbytes (3.98 Mbytes) 0.13% of uncompressed filesystem size (3145920.81 Kbytes) Inode table size 1303 bytes (1.27 Kbytes) 0.66% of uncompressed inode table size (196758 bytes) Directory table size 43 bytes (0.04 Kbytes) 100.00% of uncompressed directory table size (43 bytes) Number of duplicate files found 0 Number of inodes 3 Number of files 1 Number of fragments 0 Number of symbolic links 0 Number of device nodes 0 Number of fifo nodes 0 Number of socket nodes 0 Number of directories 2 Number of uids 1 root (0) Number of gids 0 INFO: UTF-8 character encoding detected by locale settings. Assuming UTF-8 encoded filenames on source filesystem, use -input-charset to override. /usr/bin/mkisofs: Uh oh, I cant find the boot image 'boot/grub/stage2_eltorito' ! it seems like the issue may be with the environment and the mayflower executable not being in $PATH, but i added this line 'export PATH=/sbin:$PATH' to my config file and rebuilt my rpm. i've also made sure that i have /sbin in root's path prior to running the livecd-creator command. really all i'm wanting to do is to set up the root user with a password and according to the docs this is the only way i've found. is there any simpler way to do it? or does anyone know what might be causing the error above? any help is appreciated. thanks, tim -------------- next part -------------- An HTML attachment was scrubbed... URL: From vladimir.shebordaev at gmail.com Sun Apr 22 06:12:13 2007 From: vladimir.shebordaev at gmail.com (Vladimir Shebordaev) Date: Sun, 22 Apr 2007 10:12:13 +0400 Subject: [Fedora-livecd-list] Problem creating livecd from a custom config In-Reply-To: <207b80240704212016x286fc3c6gb4459e69c4899da1@mail.gmail.com> References: <207b80240704212016x286fc3c6gb4459e69c4899da1@mail.gmail.com> Message-ID: <462AFCBD.6000606@gmail.com> Tim, you have tried rather outdated David's livecd tools. Please checkout the ones from FC7 Extras development (source) tree. Jeremy is working hard to make our lives easier. If you are running FC6 or earlier you will probably need to manually backport "livecd" anaconda install method if you need it. The backport is quite straightforward. Also you will obviously need to upgrade pykickstart package to the version 0.96... I fear to bore you, but it must be working. In the hope it helps. Regards, Vladimir Tim Boring ?????: > hi! i'm trying to build a custom livecd from a config file using the > instructions here > http://www-128.ibm.com/developerworks/linux/library/l-fedora-livecd/index.html > > > so i've followed the format of the config file and then created my > rpm...these steps appear to complete without any problems. > > the problem i'm having is when i run the livecd-creator command. here's > the command i'm using: > > ' livecd-creator --repo=livecd,file:///usr/local/fc6/repo > --package=mylivecd-0.1-3.i386.rpm --fslabel=LiveCD-1.2' > > and here's the output/error i'm getting: > > /bin/cp: cannot create regular file > `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/sbin/mayflower': > No such file or directory > /bin/cp: cannot create regular file > `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/sbin/run-init': No > such file or directory > /usr/sbin/chroot: cannot run command `/sbin/mayflower': No such file or > directory > /usr/sbin/chroot: cannot run command `/sbin/fixfiles': No such file or > directory > /bin/cp: cannot stat > `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/boot/vmlinuz*': No > such file or directory > /bin/mv: cannot stat > `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/boot/livecd-initramfs.img': > No such file or directory > /bin/cp: cannot stat > `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/usr/share/grub/i386-redhat/stage2_eltorito': > No such file or directory > /bin/cp: cannot stat > `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/boot/grub/splash.xpm.gz': > No such file or directory > Creating little endian 3.0 filesystem on ../out/squashfs.img, block size > 65536. > > Little endian filesystem, data block size 65536, compressed data, > compressed metadata, compressed fragments > Filesystem size 4072.30 Kbytes (3.98 Mbytes) > 0.13% of uncompressed filesystem size (3145920.81 Kbytes) > Inode table size 1303 bytes (1.27 Kbytes) > 0.66% of uncompressed inode table size (196758 bytes) > Directory table size 43 bytes (0.04 Kbytes) > 100.00% of uncompressed directory table size (43 bytes) > Number of duplicate files found 0 > Number of inodes 3 > Number of files 1 > Number of fragments 0 > Number of symbolic links 0 > Number of device nodes 0 > Number of fifo nodes 0 > Number of socket nodes 0 > Number of directories 2 > Number of uids 1 > root (0) > Number of gids 0 > INFO: UTF-8 character encoding detected by locale settings. > Assuming UTF-8 encoded filenames on source filesystem, > use -input-charset to override. > /usr/bin/mkisofs: Uh oh, I cant find the boot image > 'boot/grub/stage2_eltorito' ! > > it seems like the issue may be with the environment and the mayflower > executable not being in $PATH, but i added this line > > 'export PATH=/sbin:$PATH' > > to my config file and rebuilt my rpm. i've also made sure that i have > /sbin in root's path prior to running the livecd-creator command. > > really all i'm wanting to do is to set up the root user with a password > and according to the docs this is the only way i've found. is there any > simpler way to do it? or does anyone know what might be causing the > error above? any help is appreciated. > > thanks, > tim > > > ------------------------------------------------------------------------ > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list From jasperhartline at adelphia.net Sun Apr 22 15:57:57 2007 From: jasperhartline at adelphia.net (Jasper Hartline) Date: Sun, 22 Apr 2007 10:57:57 -0500 Subject: [Fedora-livecd-list] Kadischi: LiveCD to HDD installer works Message-ID: <462B8605.4050007@adelphia.net> Hi. After many many days of wrestling with Anaconda and other complications in running the Fedora Core installer from a LiveCD environment, which is not exactly like Anaconda's normal operating environment exactly, I am glad to announce that Kadischi built LiveCD or LiveDVD media can be used to install Fedora Core to your system. Details will be posted to the wiki at http://fedoraproject.org/wiki/Kadischi shortly in how to create the disc which is able to install to the HDD. Basically, it consists of adding the latest Kadischi CVS as an RPM to your package set in your repository, and modifying comps.xml. Making sure to select Kadischi during the LiveCD or LiveDVD build phase. After the LiveCD or LiveDVD is finished and once bootstrapped on a PC.. you simply invoke kadischi with a network repository location to start the install. This only will work with machines with a network connection. This method shadows Pilgrim in some ways, but mostly not due to the fact Kadischi uses the familiar Anaconda installer, rather than any other method. I will continue to make some changes to Kadischi CVS to round out some loose ends and add such things like a LiveCD to HDD installer launcher if Gnome or KDE has been installed, among other changes.. but Kadischi from CVS today should be able to be put in a package repository to create LiveCD or LiveDVD media which is installable. Thanks. J. Hartline From tjboring at gmail.com Sun Apr 22 17:38:13 2007 From: tjboring at gmail.com (Tim Boring) Date: Sun, 22 Apr 2007 10:38:13 -0700 Subject: [Fedora-livecd-list] Problem creating livecd from a custom config In-Reply-To: <462AFCBD.6000606@gmail.com> References: <207b80240704212016x286fc3c6gb4459e69c4899da1@mail.gmail.com> <462AFCBD.6000606@gmail.com> Message-ID: <207b80240704221038uf416e88u625204b6fba8502a@mail.gmail.com> hi, vladimir! thanks for the note. do you know if there is an ISO available for FC7? i tried installing/upgrading the packages you recommended and it quickly got into dependency hell. so, since i have a test machine to work on i was just going to wipe it clean and install FC7 and start over. thanks, tim On 4/21/07, Vladimir Shebordaev wrote: > > Tim, > > you have tried rather outdated David's livecd tools. > > Please checkout the ones from FC7 Extras development (source) > tree. Jeremy is working hard to make our lives easier. > > If you are running FC6 or earlier you will probably need to > manually backport "livecd" anaconda install method if you need > it. The backport is quite straightforward. Also you will > obviously need to upgrade pykickstart package to the version > 0.96... I fear to bore you, but it must be working. > > In the hope it helps. > > Regards, > Vladimir > > Tim Boring ?????: > > hi! i'm trying to build a custom livecd from a config file using the > > instructions here > > > http://www-128.ibm.com/developerworks/linux/library/l-fedora-livecd/index.html > > < > http://www-128.ibm.com/developerworks/linux/library/l-fedora-livecd/index.html > > > > > > so i've followed the format of the config file and then created my > > rpm...these steps appear to complete without any problems. > > > > the problem i'm having is when i run the livecd-creator command. here's > > the command i'm using: > > > > ' livecd-creator --repo=livecd,file:///usr/local/fc6/repo > > --package=mylivecd-0.1-3.i386.rpm --fslabel=LiveCD-1.2' > > > > and here's the output/error i'm getting: > > > > /bin/cp: cannot create regular file > > `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/sbin/mayflower': > > No such file or directory > > /bin/cp: cannot create regular file > > `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/sbin/run-init': No > > such file or directory > > /usr/sbin/chroot: cannot run command `/sbin/mayflower': No such file or > > directory > > /usr/sbin/chroot: cannot run command `/sbin/fixfiles': No such file or > > directory > > /bin/cp: cannot stat > > `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/boot/vmlinuz*': No > > such file or directory > > /bin/mv: cannot stat > > `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/boot/livecd- > initramfs.img': > > No such file or directory > > /bin/cp: cannot stat > > > `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/usr/share/grub/i386-redhat/stage2_eltorito': > > No such file or directory > > /bin/cp: cannot stat > > > `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/boot/grub/splash.xpm.gz': > > No such file or directory > > Creating little endian 3.0 filesystem on ../out/squashfs.img, block size > > 65536. > > > > Little endian filesystem, data block size 65536, compressed data, > > compressed metadata, compressed fragments > > Filesystem size 4072.30 Kbytes (3.98 Mbytes) > > 0.13% of uncompressed filesystem size (3145920.81 Kbytes) > > Inode table size 1303 bytes (1.27 Kbytes) > > 0.66% of uncompressed inode table size (196758 bytes) > > Directory table size 43 bytes (0.04 Kbytes) > > 100.00% of uncompressed directory table size (43 bytes) > > Number of duplicate files found 0 > > Number of inodes 3 > > Number of files 1 > > Number of fragments 0 > > Number of symbolic links 0 > > Number of device nodes 0 > > Number of fifo nodes 0 > > Number of socket nodes 0 > > Number of directories 2 > > Number of uids 1 > > root (0) > > Number of gids 0 > > INFO: UTF-8 character encoding detected by locale settings. > > Assuming UTF-8 encoded filenames on source filesystem, > > use -input-charset to override. > > /usr/bin/mkisofs: Uh oh, I cant find the boot image > > 'boot/grub/stage2_eltorito' ! > > > > it seems like the issue may be with the environment and the mayflower > > executable not being in $PATH, but i added this line > > > > 'export PATH=/sbin:$PATH' > > > > to my config file and rebuilt my rpm. i've also made sure that i have > > /sbin in root's path prior to running the livecd-creator command. > > > > really all i'm wanting to do is to set up the root user with a password > > and according to the docs this is the only way i've found. is there any > > simpler way to do it? or does anyone know what might be causing the > > error above? any help is appreciated. > > > > thanks, > > tim > > > > > > ------------------------------------------------------------------------ > > > > -- > > Fedora-livecd-list mailing list > > Fedora-livecd-list at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-livecd-list > > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From vladimir.shebordaev at gmail.com Sun Apr 22 18:25:45 2007 From: vladimir.shebordaev at gmail.com (Vladimir Shebordaev) Date: Sun, 22 Apr 2007 22:25:45 +0400 Subject: [Fedora-livecd-list] Problem creating livecd from a custom config In-Reply-To: <207b80240704221038uf416e88u625204b6fba8502a@mail.gmail.com> References: <207b80240704212016x286fc3c6gb4459e69c4899da1@mail.gmail.com> <462AFCBD.6000606@gmail.com> <207b80240704221038uf416e88u625204b6fba8502a@mail.gmail.com> Message-ID: <462BA8A9.9000102@gmail.com> Well, Tim, I meant rather a backport to your current Fedora version. Anaconda does depend on around 2 dozen packages, so I tried to incorporate recent changes from livecd-tools-006 fc7 rpm back to my FC6 a few weeks ago. Everything was almost fine but faulty yum install root setup broke my host. Afaik, it has been fixed a week ago. But I doubt those changes have been also made to FC7 LiveCD. The most recent fc7-test3-6.92 livecd made lots of people scream. You can also try it. It is available, e.g. from . You will have an option for i386 or x86_64. If you managed to boot from the image installed to your hard disk you will have a chance to update and try fc7 development rpms from or whatever architecture you prefer. livecd-tools are "noarch". In the hope it helps. Regards, Vladimir Tim Boring ?????: > hi, vladimir! thanks for the note. do you know if there is an ISO > available for FC7? i tried installing/upgrading the packages you > recommended and it quickly got into dependency hell. so, since i have a > test machine to work on i was just going to wipe it clean and install > FC7 and start over. > > thanks, > tim > > On 4/21/07, *Vladimir Shebordaev* > wrote: > > Tim, > > you have tried rather outdated David's livecd tools. > > Please checkout the ones from FC7 Extras development (source) > tree. Jeremy is working hard to make our lives easier. > > If you are running FC6 or earlier you will probably need to > manually backport "livecd" anaconda install method if you need > it. The backport is quite straightforward. Also you will > obviously need to upgrade pykickstart package to the version > 0.96... I fear to bore you, but it must be working. > > In the hope it helps. > > Regards, > Vladimir > > Tim Boring ?????: > > hi! i'm trying to build a custom livecd from a config file using the > > instructions here > > > http://www-128.ibm.com/developerworks/linux/library/l-fedora-livecd/index.html > > < > http://www-128.ibm.com/developerworks/linux/library/l-fedora-livecd/index.html> > > > > so i've followed the format of the config file and then created my > > rpm...these steps appear to complete without any problems. > > > > the problem i'm having is when i run the livecd-creator > command. here's > > the command i'm using: > > > > ' livecd-creator --repo=livecd, file:///usr/local/fc6/repo > > --package=mylivecd-0.1-3.i386.rpm --fslabel=LiveCD-1.2' > > > > and here's the output/error i'm getting: > > > > /bin/cp: cannot create regular file > > > `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/sbin/mayflower': > > No such file or directory > > /bin/cp: cannot create regular file > > > `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/sbin/run-init': No > > such file or directory > > /usr/sbin/chroot: cannot run command `/sbin/mayflower': No such > file or > > directory > > /usr/sbin/chroot: cannot run command `/sbin/fixfiles': No such > file or > > directory > > /bin/cp: cannot stat > > > `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/boot/vmlinuz*': > No > > such file or directory > > /bin/mv: cannot stat > > > `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/boot/livecd-initramfs.img': > > No such file or directory > > /bin/cp: cannot stat > > > `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/usr/share/grub/i386-redhat/stage2_eltorito': > > No such file or directory > > /bin/cp: cannot stat > > > `/var/tmp/livecd-creator/build-tmp-d5CrT/install_root/boot/grub/splash.xpm.gz': > > > No such file or directory > > Creating little endian 3.0 filesystem on ../out/squashfs.img, > block size > > 65536. > > > > Little endian filesystem, data block size 65536, compressed data, > > compressed metadata, compressed fragments > > Filesystem size 4072.30 Kbytes (3.98 Mbytes) > > 0.13% of uncompressed filesystem size (3145920.81 Kbytes) > > Inode table size 1303 bytes (1.27 Kbytes) > > 0.66% of uncompressed inode table size (196758 bytes) > > Directory table size 43 bytes (0.04 Kbytes) > > 100.00% of uncompressed directory table size (43 bytes) > > Number of duplicate files found 0 > > Number of inodes 3 > > Number of files 1 > > Number of fragments 0 > > Number of symbolic links 0 > > Number of device nodes 0 > > Number of fifo nodes 0 > > Number of socket nodes 0 > > Number of directories 2 > > Number of uids 1 > > root (0) > > Number of gids 0 > > INFO: UTF-8 character encoding detected by locale settings. > > Assuming UTF-8 encoded filenames on source filesystem, > > use -input-charset to override. > > /usr/bin/mkisofs: Uh oh, I cant find the boot image > > 'boot/grub/stage2_eltorito' ! > > > > it seems like the issue may be with the environment and the mayflower > > executable not being in $PATH, but i added this line > > > > 'export PATH=/sbin:$PATH' > > > > to my config file and rebuilt my rpm. i've also made sure that i > have > > /sbin in root's path prior to running the livecd-creator command. > > > > really all i'm wanting to do is to set up the root user with a > password > > and according to the docs this is the only way i've found. is > there any > > simpler way to do it? or does anyone know what might be causing the > > error above? any help is appreciated. > > > > thanks, > > tim > > > > > > > ------------------------------------------------------------------------ > > > > -- > > Fedora-livecd-list mailing list > > Fedora-livecd-list at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-livecd-list > > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list > > > > ------------------------------------------------------------------------ > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list From mclasen at redhat.com Mon Apr 23 03:54:30 2007 From: mclasen at redhat.com (Matthias Clasen) Date: Sun, 22 Apr 2007 23:54:30 -0400 Subject: [Fedora-livecd-list] Learning why packages are getting installed Message-ID: <1177300470.3597.9.camel@localhost.localdomain> This weekend I spent some time trying to get a better understanding of why some packages are included on the live cd. At first I tried to generate a full dependency graph for the package set on the live cd, but the graph visualization tools I tried couldn't handle a graph of this size gracefully. Therefore I took a slightly different approach and wrote a small tool called "why", that when given a package name, produces a partial dependency graph showing how the given package is pulled in by "leaf" packages. The tool and some example graphs can be found here: http://people.redhat.com/mclasen/livecd (the green node is the package thats investigated, the red nodes are the leaf packages) I couldn't get myself to learn how to convince librpm to give me the dependency graph, thus the tool reads it from a text file named alldeps. The above location has the alldeps file that I generated for the test4 live cd. Hope this is useful for somebody, Matthias From jmbabich at gmail.com Mon Apr 23 05:53:37 2007 From: jmbabich at gmail.com (John Babich) Date: Mon, 23 Apr 2007 08:53:37 +0300 Subject: [Fedora-livecd-list] Learning why packages are getting installed In-Reply-To: <1177300470.3597.9.camel@localhost.localdomain> References: <1177300470.3597.9.camel@localhost.localdomain> Message-ID: <9d2c731f0704222253j745f54b4g741e66b6e9b6091@mail.gmail.com> Matthias: Thanks for the utility. I certainly have can use something like this. John Babich Volunteer, Fedora Docs Project From chitlesh at fedoraproject.org Mon Apr 23 11:30:41 2007 From: chitlesh at fedoraproject.org (Chitlesh GOORAH) Date: Mon, 23 Apr 2007 13:30:41 +0200 Subject: [Fedora-livecd-list] Kadischi: Kadischi package (Chitlesh) In-Reply-To: <46296528.6010704@adelphia.net> References: <46296528.6010704@adelphia.net> Message-ID: <13dbfe4f0704230430q405a7658y7052269e4c590f83@mail.gmail.com> On 4/21/07, Jasper Hartline wrote: > Hello. > > Chitlesh Goorah, if you could work with me on orphaning the Kadischi > package so I can take over the package and the bugzilla section on Kadischi > I would appreciate it. > > I have a new package review in bugzilla right now, and as I understand it > I need to contact you to have you orphan the package. Sorry, I was offline last week. Done: Ownership change was requested: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=237402 chitlesh -- http://clunixchit.blogspot.com From chitlesh at fedoraproject.org Mon Apr 23 11:30:00 2007 From: chitlesh at fedoraproject.org (Chitlesh GOORAH) Date: Mon, 23 Apr 2007 13:30:00 +0200 Subject: [Fedora-livecd-list] Re: Kadischi package maintainer cannot be found In-Reply-To: <462ABD1B.6090104@adelphia.net> References: <462ABD1B.6090104@adelphia.net> Message-ID: <13dbfe4f0704230430n1da8eac0yb4d6d2bf74efafaa@mail.gmail.com> On 4/22/07, Jasper Hartline wrote: > Hi. > > I've made several attempts via IRC, in channel #fedora-livecd > on irc.freenode.net IRC server to contact Chitlesh Goorah to > continue the process of taking over the Kadischi package in Extras. > > He did not respond to me on IRC, and is not responding to me via email > to the fedora-livecd-list at redhat.com either. What should I do to claim > responsibility of this package if the maintainer cannot be reached > and is not currently making updates to the package? Sorry, I was offline last week. Ownership change was requested: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=237402 regards, Chitlesh -- http://clunixchit.blogspot.com From johnp at redhat.com Tue Apr 24 18:53:57 2007 From: johnp at redhat.com (John (J5) Palmieri) Date: Tue, 24 Apr 2007 14:53:57 -0400 Subject: [Fedora-livecd-list] Support for custom configuration using python templates Message-ID: <1177440837.3387.28.camel@localhost.localdomain> This is the first in a bunch of OLPC needs I will be writing about on the list. It is super simple for me to hack up solutions that work for us but I would like to find a common solution that benefits all Fedora based projects. One of the things we need to for OLPC from the LiveCD creator is the ability to output configuration files from a template. We do this currently in Pilgrim and can do this in the LiveCD tools via the %post as shell scripts. This is pretty unwieldy and tends to be error prone with typos and missing character escapes causing sometimes hard to debug problems. A simple idea is to have standard template mechanism such as using pythons string substitutions. For example take the file /etc/issue. In shell we do this: cat < $INSTALL_ROOT/etc/issue OLPC build $BUILD (stream $STREAM; variant $VARIANT) Kernel \r on an \m EOF It would be nice to have a template file which read something like: OLPC build %(build) (stream %(stream); variant %(variant)) Kernel \r on an \m and simply passed in a hash with substitutions from the livecd tools. Python templates or whatever templates is not really the issue here. What is the issue is defining a standard template format to use, defining how the tool finds the templates and defining how substitutions are specified. Any suggestions? I am willing to do the code myself but in the lack of any interest I'm going to end up creating a one off solution, so mucho input is desired. -- John (J5) Palmieri From johnp at redhat.com Tue Apr 24 19:01:58 2007 From: johnp at redhat.com (John (J5) Palmieri) Date: Tue, 24 Apr 2007 15:01:58 -0400 Subject: [Fedora-livecd-list] Inheritance Message-ID: <1177441318.3387.37.camel@localhost.localdomain> In the pilgrim tool it is fairly easy to inherit from "stream" files and just expand a base image into a newer image. This means I can create a base description for an image, with all the required rpms and %post processing and then define another image description which adds more rpms and does more post processing. We can even override hooks and files in the child description. For instance our liveCD SDK has added gnome packages but does not download the ondisk html library to save space. This allows me to make changes to the base image which is automatically reflected in the livecd image builds. The real reason we need this is for country builds. I know that the livecd tools already have the ability to take an iso and add to it but I also need the ability to do a build from scratch. First can the current kickstart file format handle this and second how can we support this if it does not? -- John (J5) Palmieri From johnp at redhat.com Tue Apr 24 19:10:49 2007 From: johnp at redhat.com (John (J5) Palmieri) Date: Tue, 24 Apr 2007 15:10:49 -0400 Subject: [Fedora-livecd-list] Targetting other file systems besides iso Message-ID: <1177441849.3387.47.camel@localhost.localdomain> At OLPC we need to support ext3 and jffs2 builds even more so than livecd isos. Since most of the process is the same up until the final image and bootloaders we would like to add this support into the livecd tools so that all fedora projects use one toolchain. The question is how can this best be accomplished? I think passing a --variant switch (i.e. --variant=jffs2) should switch the backend to generating the correct image. This also requires template support and the ability to select templates to write out based on the variant in the %post. For instance the olpc.fth file is read in by the openfirmware. For jffs2 builds we point to the nand on the XO machines. For ext3 we point to a USB disk. Also on ext3 we write out grub entries for use with standard machines and vitalization software like qemu. What would be the best way to add this support to the livecd tools? -- John (J5) Palmieri From jdogalt at yahoo.com Wed Apr 25 01:23:02 2007 From: jdogalt at yahoo.com (Jane Dogalt) Date: Tue, 24 Apr 2007 18:23:02 -0700 (PDT) Subject: [Fedora-livecd-list] Targetting other file systems besides iso In-Reply-To: <1177441849.3387.47.camel@localhost.localdomain> Message-ID: <76509.22416.qm@web56908.mail.re3.yahoo.com> --- "John (J5) Palmieri" wrote: > At OLPC we need to support ext3 and jffs2 builds even more so than > livecd isos. Since most of the process is the same up until the > final > image and bootloaders we would like to add this support into the > livecd > tools so that all fedora projects use one toolchain. The question is > how can this best be accomplished? > > I think passing a --variant switch (i.e. --variant=jffs2) should > switch > the backend to generating the correct image. This also requires > template support and the ability to select templates to write out > based > on the variant in the %post. For instance the olpc.fth file is read > in > by the openfirmware. For jffs2 builds we point to the nand on the XO > machines. For ext3 we point to a USB disk. Also on ext3 we write > out > grub entries for use with standard machines and vitalization software > like qemu. > > What would be the best way to add this support to the livecd tools? This isn't really an answer to your question, but I would like to affirm the usefulness of what you described. I.e. creating a clear demarcation between the system installation frontend, and the system target type mogrification backend. While I've never been a huge fan of the read-only root kadischi/stateless style system, I admit it may be the right choice in some situations. And in general I think there are several other interesting system target type backends one could have. I.e. I think if things get modularized the way you described, it would be gracefully doable to merge the kadischi code into the tool as another alternate backend. And likewise, one could have a standard knoppix style unionfs backend (I think the scientific-linux folks use this style on their centos derived livecd). Not to mention the nearly half dozen 'out there' ideas I've posted on this list over the years. Likewise, I can see several possibly useful variants on the frontend as well. I.e. the kadischi anaconda --rootpath. Or my preferred method of installing inside qemu so as not to require root privs (at the expense of speed) I realize of course there are rational arguments to avoid having too many choices. On the other hand, lots of choices can be a good thing, in that the most useful among them will see the most development and evolution. Of course my overambitious 'one ring to rule them all' goal is to even support other distributions such as debian/ubuntu/centos/whatever in the frontend options as well. But yeah... What you said sounds excellent. $0.02... -dmc/jdog __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From davidz at redhat.com Wed Apr 25 16:58:12 2007 From: davidz at redhat.com (David Zeuthen) Date: Wed, 25 Apr 2007 12:58:12 -0400 Subject: [Fedora-livecd-list] Support for custom configuration using python templates In-Reply-To: <1177440837.3387.28.camel@localhost.localdomain> References: <1177440837.3387.28.camel@localhost.localdomain> Message-ID: <1177520292.2769.16.camel@zelda.fubar.dk> Hi, On Tue, 2007-04-24 at 14:53 -0400, John (J5) Palmieri wrote: > Any suggestions? I am willing to do the code myself but in the lack > of any interest I'm going to end up creating a one off solution, so > mucho input is desired. I think munging configuration files might be outside the scope of the livecd-tools project; sure, granted it's something people want to do but often it's used as a hack; for example on my system $ rpm -qf /etc/issue fedora-release-6.93-1 so I think what you *could* do instead is to have olpc-release or similar on OLPC provide that file (would be based on fedora-release). Of course, since /etc/issue is marked as %config(noreplace) in the fedora-release it's still sane for you to edit it in %post. I guess it all depends on the configuration file in question. So I think my point of view right now is that it's good enough to do this in %post for most cases; I mean, if downstreams (like OLPC) need to change a ton of configuration files/defaults perhaps there is something broken with the apps you try to include? Perhaps you can come up with concrete examples of what configuration files / defaults you need to edit /change? I think that would be useful. Thanks. David From davidz at redhat.com Wed Apr 25 17:41:10 2007 From: davidz at redhat.com (David Zeuthen) Date: Wed, 25 Apr 2007 13:41:10 -0400 Subject: [Fedora-livecd-list] Targetting other file systems besides iso In-Reply-To: <1177441849.3387.47.camel@localhost.localdomain> References: <1177441849.3387.47.camel@localhost.localdomain> Message-ID: <1177522870.2769.30.camel@zelda.fubar.dk> On Tue, 2007-04-24 at 15:10 -0400, John (J5) Palmieri wrote: > At OLPC we need to support ext3 and jffs2 builds even more so than > livecd isos. Since most of the process is the same up until the final > image and bootloaders we would like to add this support into the livecd > tools so that all fedora projects use one toolchain. The question is > how can this best be accomplished? > > I think passing a --variant switch (i.e. --variant=jffs2) should switch > the backend to generating the correct image. I think adding an option --target=[livecd| disk_msdos_ext3| disk_msdos_ext3_separate_boot| ext3| jffs2] with this help text (for --help) --target Choose target mode; defaults to livecd livecd: A compressed livecd ISO with the root file system disk_msdos_ext3 : An image with a MSDOS partitioning table, a single ext3 data partition and a bootloader for IBM PC hardware disk_msdos_ext3_separate_boot : Like disk_msdos_ext3 only that /boot is on a separate partition. ext3 : A single ext3 partition jffs2 : A jffs2 file system is what we want. Perhaps disk_msdos_ext3_separate_boot can be achieved by a separate option just like we have --skip-compression for --target=livecd. Thoughts? > This also requires > template support and the ability to select templates to write out based > on the variant in the %post. For instance the olpc.fth file is read in > by the openfirmware. For jffs2 builds we point to the nand on the XO > machines. For ext3 we point to a USB disk. Also on ext3 we write out > grub entries for use with standard machines and vitalization software > like qemu. The olpc.fth business is probably not something we need to teach the livecd tools about at all; e.g. it's simply just something you do in % post depending on the target. This raises the question of how do we pass "options" like --target to kickstart so you can do different things depending. An environment variable. Jeremy? David From markmc at redhat.com Thu Apr 26 09:22:21 2007 From: markmc at redhat.com (Mark McLoughlin) Date: Thu, 26 Apr 2007 10:22:21 +0100 Subject: [Fedora-livecd-list] Targetting other file systems besides iso In-Reply-To: <1177522870.2769.30.camel@zelda.fubar.dk> References: <1177441849.3387.47.camel@localhost.localdomain> <1177522870.2769.30.camel@zelda.fubar.dk> Message-ID: <1177579341.3487.31.camel@blaa> On Wed, 2007-04-25 at 13:41 -0400, David Zeuthen wrote: > On Tue, 2007-04-24 at 15:10 -0400, John (J5) Palmieri wrote: > > At OLPC we need to support ext3 and jffs2 builds even more so than > > livecd isos. Since most of the process is the same up until the final > > image and bootloaders we would like to add this support into the livecd > > tools so that all fedora projects use one toolchain. The question is > > how can this best be accomplished? > > > > I think passing a --variant switch (i.e. --variant=jffs2) should switch > > the backend to generating the correct image. > > I think adding an option > > --target=[livecd| > disk_msdos_ext3| > disk_msdos_ext3_separate_boot| > ext3| > jffs2] > > with this help text (for --help) > > --target Choose target mode; defaults to livecd > livecd: A compressed livecd ISO with the root file system > disk_msdos_ext3 : An image with a MSDOS partitioning > table, a single ext3 data partition and > a bootloader for IBM PC hardware > disk_msdos_ext3_separate_boot : Like disk_msdos_ext3 only > that /boot is on a separate partition. > ext3 : A single ext3 partition > jffs2 : A jffs2 file system > > is what we want. Perhaps disk_msdos_ext3_separate_boot can be achieved > by a separate option just like we have --skip-compression for > --target=livecd. Thoughts? I've a few of patches to do something similar, except I've been using livecd-creator to build xen system images for the likes of image based deployment (e.g. stateless) or this virtual appliances notion. See the attached patches - the first makes LiveCDTarget be a sub-class of InstallationTarget, the second adds --target and the last adds RawTarget which I've been playing with. Cheers, Mark. -------------- next part -------------- A non-text attachment was scrubbed... Name: livecd-refactor-target.patch Type: text/x-patch Size: 10179 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: livecd-target-type.patch Type: text/x-patch Size: 3172 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: livecd-raw-target.patch Type: text/x-patch Size: 5075 bytes Desc: not available URL: From markmc at redhat.com Thu Apr 26 09:29:21 2007 From: markmc at redhat.com (Mark McLoughlin) Date: Thu, 26 Apr 2007 10:29:21 +0100 Subject: [Fedora-livecd-list] Support for custom configuration using python templates In-Reply-To: <1177440837.3387.28.camel@localhost.localdomain> References: <1177440837.3387.28.camel@localhost.localdomain> Message-ID: <1177579762.3487.36.camel@blaa> On Tue, 2007-04-24 at 14:53 -0400, John (J5) Palmieri wrote: > One of the things we need to for OLPC from the LiveCD creator is the > ability to output configuration files from a template. One thing I've been meaning to do for a while, based on David Lutterkort's suggestion, is to try using puppet[1] from the livecd-creator ... i.e. run puppet from %post with a manifest that would change whatever configuration files you need. One reason puppet might be nice is that it does inheritance, templating etc. Dunno, I'm not convinced yet, but it's worth trying. Cheers, Mark. [1] - http://reductivelabs.com/projects/puppet/ From johnp at redhat.com Thu Apr 26 20:51:56 2007 From: johnp at redhat.com (John (J5) Palmieri) Date: Thu, 26 Apr 2007 16:51:56 -0400 Subject: [Fedora-livecd-list] Support for custom configuration using python templates In-Reply-To: <1177520292.2769.16.camel@zelda.fubar.dk> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> Message-ID: <1177620716.3404.50.camel@localhost.localdomain> On Wed, 2007-04-25 at 12:58 -0400, David Zeuthen wrote: > Hi, > > On Tue, 2007-04-24 at 14:53 -0400, John (J5) Palmieri wrote: > > Any suggestions? I am willing to do the code myself but in the lack > > of any interest I'm going to end up creating a one off solution, so > > mucho input is desired. > > I think munging configuration files might be outside the scope of the > livecd-tools project; sure, granted it's something people want to do but > often it's used as a hack; for example on my system > > $ rpm -qf /etc/issue > fedora-release-6.93-1 And I'm going to package that up for every daily release? And what about countries? Too heavy and engineered for an image based distribution. > so I think what you *could* do instead is to have olpc-release or > similar on OLPC provide that file (would be based on fedora-release). Of > course, since /etc/issue is marked as %config(noreplace) in the > fedora-release it's still sane for you to edit it in %post. I guess it > all depends on the configuration file in question. > > So I think my point of view right now is that it's good enough to do > this in %post for most cases; I mean, if downstreams (like OLPC) need to > change a ton of configuration files/defaults perhaps there is something > broken with the apps you try to include? No just that apps can be configured for different purposes. For instance gedit can be made into a development environment but requires me to write out a bunch of gconf files. We have Sabyon for a reason. It basically does what I want to do in the case of gconf and some other settings. It is a dump of configuration files. > Perhaps you can come up with concrete examples of what configuration > files / defaults you need to edit /change? I think that would be useful. > Thanks. /etc/sysconfig/modules/olpc-1.modules for the module lists to load /etc/rwtab for stateless tmpfs mounted stuff /etc/asound.state to put the correct default sound levels /etc/modprobe.d/olpc.conf.dist so we get the correct module parameters /boot/olpc_build for build info that the bootloader uses /etc/issue for build info the user can read /etc/securetty for adding the serial console /etc/inittab for removing unneeded memory waisting VT's /usr/share/fonts/dejavu-lgc/fonts.dir for mapping legacy fonts /usr/share/fonts/dejavu-lgc/fonts.scale same as above /usr/share/fonts/dejavu-lgc/fonts.alias same /etc/X11/xorg.conf and its variants for booting on any device and getting the correct xorg config file with the correct keyboard laysouts /home/olpc/.xinitrc for launching sugar /boot/grub/grub.conf for the occasional qemu boot /etc/init.d/olpc-configure init script for boot time configuration /usr/share/X11/xkb/symbols/* for keyboard configuration that is not yet upstream (note that these must be added to an already existing file) /boot/olpc.fth - for booting from openfirmware Note that we can't move a lot of these to an RPM because RPM conflict rules would prevent them from being installed. Some files need input such as BUILD number and some files change so rapidly during the testing phase that taking the time to build an rpm and place it in the right spot and rebuild the repo would be a unneeded bottleneck. -- John (J5) Palmieri From mclasen at redhat.com Fri Apr 27 01:40:44 2007 From: mclasen at redhat.com (Matthias Clasen) Date: Thu, 26 Apr 2007 21:40:44 -0400 Subject: [Fedora-livecd-list] Re: Learning why packages are getting installed Message-ID: <1177638044.30677.5.camel@localhost.localdomain> I forgot to mention that my program can also dump strong components (ie dependency cycles). Here are the results: ConsoleKit-libs <-> MAKEDEV <-> SysVinit <-> coreutils <-> dbus <-> device-mapper <-> device-mapper-libs <-> e2fsprogs <-> e2fsprogs-libs <-> initscripts <-> krb5-libs <-> libselinux <-> libxml2-python <-> logrotate <-> mcstrans <-> module-init-tools <-> net-tools <-> openssl <-> pam <-> psmisc <-> python <-> python-libs <-> shadow-utils <-> sysklogd <-> udev <-> util-linux aspell <-> aspell-en chkfontpath <-> xorg-x11-xfs fast-user-switch-applet <-> gnome-panel fedora-logos <-> redhat-artwork festival <-> festvox-slt-arctic-hts firstboot <-> system-config-keyboard gnome-python2 <-> gnome-python2-bonobo <-> gnome-python2-gnomevfs hal <-> hal-info mono-web <-> mono-winforms perl <-> perl-devel rpm <-> rpm-libs xorg-x11-drv-evdev <-> xorg-x11-drv-keyboard <-> xorg-x11-drv-mouse <-> xorg-x11-drv-vesa <-> xorg-x11-drv-void <-> xorg-x11-server-Xorg yp-tools <-> ypbind While most are small and easy to explain, there are a few horrible ones, like the one involving ConsoleKit-libs From davidz at redhat.com Fri Apr 27 01:44:27 2007 From: davidz at redhat.com (David Zeuthen) Date: Thu, 26 Apr 2007 21:44:27 -0400 Subject: [Fedora-livecd-list] Support for custom configuration using python templates In-Reply-To: <1177620716.3404.50.camel@localhost.localdomain> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> Message-ID: <1177638267.2986.20.camel@zelda.fubar.dk> On Thu, 2007-04-26 at 16:51 -0400, John (J5) Palmieri wrote: > > I think munging configuration files might be outside the scope of the > > livecd-tools project; sure, granted it's something people want to do but > > often it's used as a hack; for example on my system > > > > $ rpm -qf /etc/issue > > fedora-release-6.93-1 > > And I'm going to package that up for every daily release? And what > about countries? Too heavy and engineered for an image based > distribution. [...] > > so I think what you *could* do instead is to have olpc-release or > > similar on OLPC provide that file (would be based on fedora-release). Of > > course, since /etc/issue is marked as %config(noreplace) in the > > fedora-release it's still sane for you to edit it in %post. I guess it > > all depends on the configuration file in question. I think I said that both approaches works. Just make sure all files being changed are tagged with %config(noreplace) if you care about RPM upgrade paths (which you probably don't need to for OLPC but it's nice nonetheless if someone wants to pick this up for hardware that can cope with yum/rpm etc.). > > So I think my point of view right now is that it's good enough to do > > this in %post for most cases; I mean, if downstreams (like OLPC) need to > > change a ton of configuration files/defaults perhaps there is something > > broken with the apps you try to include? > > No just that apps can be configured for different purposes. For > instance gedit can be made into a development environment but requires > me to write out a bunch of gconf files. We have Sabyon for a reason. > It basically does what I want to do in the case of gconf and some other > settings. It is a dump of configuration files. Sure, or you can use gconftool-2 or Puppet as Mark mentioned or basically anything that gets the job done. My point really was that I don't think configuration file munging belongs in livecd-tools proper. Do you think that's wrong? > > Perhaps you can come up with concrete examples of what configuration > > files / defaults you need to edit /change? I think that would be useful. > > Thanks. > > /etc/sysconfig/modules/olpc-1.modules for the module lists to load > /etc/rwtab for stateless tmpfs mounted stuff > /etc/asound.state to put the correct default sound levels > /etc/modprobe.d/olpc.conf.dist so we get the correct module parameters > /boot/olpc_build for build info that the bootloader uses > /etc/issue for build info the user can read > /etc/securetty for adding the serial console > /etc/inittab for removing unneeded memory waisting VT's > /usr/share/fonts/dejavu-lgc/fonts.dir for mapping legacy fonts > /usr/share/fonts/dejavu-lgc/fonts.scale same as above > /usr/share/fonts/dejavu-lgc/fonts.alias same > /etc/X11/xorg.conf and its variants for booting on any device and > getting the correct xorg config file with the correct keyboard laysouts > /home/olpc/.xinitrc for launching sugar > /boot/grub/grub.conf for the occasional qemu boot > /etc/init.d/olpc-configure init script for boot time configuration > /usr/share/X11/xkb/symbols/* for keyboard configuration that is not yet > upstream (note that these must be added to an already existing file) > /boot/olpc.fth - for booting from openfirmware > > Note that we can't move a lot of these to an RPM because RPM conflict > rules would prevent them from being installed. Some files need input > such as BUILD number and some files change so rapidly during the testing > phase that taking the time to build an rpm and place it in the right > spot and rebuild the repo would be a unneeded bottleneck. So perhaps one maintainable way for you is to have a single script (packaged up in a OLPC specific RPM) that does all the munging and your %post simple invokes this? That script would know about per-country things and what kind of "image" (e.g. jffs2, livecd, disk_ext3 etc.) you're building by having the %post pass it as options? Wouldn't that work? Of course, the question I raised in an earlier mail of how we pass items to the %post script in the Kickstart file still stands. Jeremy? Perhaps just setting environment variables works out of the box. I'd be surprised if this is not the case. Also, external variables used by higher level constructs that does batch builds in a structured way (e.g. pilgrim-autobuild) needs to pass (OLPC-specific) variables too such as BUILD_NUMBER, TARGET_COUNTRY etc. to %post. I think the way I'd like this to work is that such variables are transparently passed by livecd-tools and then the %post takes care of it. Perhaps it would look like this %post olpc-configure-system --image-type $LIVECD_TOOLS_IMAGE_TYPE \ --olpc-build-number $OLPC_IMAGE_NUMBER \ --olpc-target $OLPC_TARGET_COUNTRY Would that work for you? David From stevejberry at gmail.com Fri Apr 27 15:59:28 2007 From: stevejberry at gmail.com (Steve Berry) Date: Fri, 27 Apr 2007 11:59:28 -0400 Subject: [Fedora-livecd-list] SSH defualt on livecd bootup In-Reply-To: <1177638267.2986.20.camel@zelda.fubar.dk> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> Message-ID: <46321DE0.8030703@gmail.com> I noticed I can't ssh telnet into a livecd - I'm guessing this was disabled for security reasons. can someone tell me why exactly? I would have loved to boot an old box with f7-test4 i386 and telneted over, configured vncserver to allow me to control it from remote. then install it from the cd to the harddrive and reboot it without hooking a monitor up to it. From johnp at redhat.com Fri Apr 27 17:27:54 2007 From: johnp at redhat.com (John (J5) Palmieri) Date: Fri, 27 Apr 2007 13:27:54 -0400 Subject: [Fedora-livecd-list] SSH defualt on livecd bootup In-Reply-To: <46321DE0.8030703@gmail.com> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> <46321DE0.8030703@gmail.com> Message-ID: <1177694874.3486.37.camel@localhost.localdomain> On Fri, 2007-04-27 at 11:59 -0400, Steve Berry wrote: > I noticed I can't ssh telnet into a livecd - I'm guessing this was > disabled for security reasons. > > can someone tell me why exactly? > > I would have loved to boot an old box with f7-test4 i386 and telneted > over, configured vncserver to allow me to control it from remote. then > install it from the cd to the harddrive and reboot it without hooking a > monitor up to it. Most likely the root password is not set which automatically disables ssh for security reasons. -- John (J5) Palmieri From johnp at redhat.com Fri Apr 27 17:45:11 2007 From: johnp at redhat.com (John (J5) Palmieri) Date: Fri, 27 Apr 2007 13:45:11 -0400 Subject: [Fedora-livecd-list] Support for custom configuration using python templates In-Reply-To: <1177638267.2986.20.camel@zelda.fubar.dk> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> Message-ID: <1177695911.3486.53.camel@localhost.localdomain> On Thu, 2007-04-26 at 21:44 -0400, David Zeuthen wrote: > On Thu, 2007-04-26 at 16:51 -0400, John (J5) Palmieri wrote: > > > I think munging configuration files might be outside the scope of the > > > livecd-tools project; sure, granted it's something people want to do but > > > often it's used as a hack; for example on my system > > > > > > $ rpm -qf /etc/issue > > > fedora-release-6.93-1 > > > > And I'm going to package that up for every daily release? And what > > about countries? Too heavy and engineered for an image based > > distribution. > > [...] > > > > so I think what you *could* do instead is to have olpc-release or > > > similar on OLPC provide that file (would be based on fedora-release). Of > > > course, since /etc/issue is marked as %config(noreplace) in the > > > fedora-release it's still sane for you to edit it in %post. I guess it > > > all depends on the configuration file in question. > > I think I said that both approaches works. Just make sure all files > being changed are tagged with %config(noreplace) if you care about RPM > upgrade paths (which you probably don't need to for OLPC but it's nice > nonetheless if someone wants to pick this up for hardware that can cope > with yum/rpm etc.). > > > > So I think my point of view right now is that it's good enough to do > > > this in %post for most cases; I mean, if downstreams (like OLPC) need to > > > change a ton of configuration files/defaults perhaps there is something > > > broken with the apps you try to include? > > > > No just that apps can be configured for different purposes. For > > instance gedit can be made into a development environment but requires > > me to write out a bunch of gconf files. We have Sabyon for a reason. > > It basically does what I want to do in the case of gconf and some other > > settings. It is a dump of configuration files. > > Sure, or you can use gconftool-2 or Puppet as Mark mentioned or > basically anything that gets the job done. My point really was that I > don't think configuration file munging belongs in livecd-tools proper. > Do you think that's wrong? > > > > Perhaps you can come up with concrete examples of what configuration > > > files / defaults you need to edit /change? I think that would be useful. > > > Thanks. > > > > /etc/sysconfig/modules/olpc-1.modules for the module lists to load > > /etc/rwtab for stateless tmpfs mounted stuff > > /etc/asound.state to put the correct default sound levels > > /etc/modprobe.d/olpc.conf.dist so we get the correct module parameters > > /boot/olpc_build for build info that the bootloader uses > > /etc/issue for build info the user can read > > /etc/securetty for adding the serial console > > /etc/inittab for removing unneeded memory waisting VT's > > /usr/share/fonts/dejavu-lgc/fonts.dir for mapping legacy fonts > > /usr/share/fonts/dejavu-lgc/fonts.scale same as above > > /usr/share/fonts/dejavu-lgc/fonts.alias same > > /etc/X11/xorg.conf and its variants for booting on any device and > > getting the correct xorg config file with the correct keyboard laysouts > > /home/olpc/.xinitrc for launching sugar > > /boot/grub/grub.conf for the occasional qemu boot > > /etc/init.d/olpc-configure init script for boot time configuration > > /usr/share/X11/xkb/symbols/* for keyboard configuration that is not yet > > upstream (note that these must be added to an already existing file) > > /boot/olpc.fth - for booting from openfirmware > > > > Note that we can't move a lot of these to an RPM because RPM conflict > > rules would prevent them from being installed. Some files need input > > such as BUILD number and some files change so rapidly during the testing > > phase that taking the time to build an rpm and place it in the right > > spot and rebuild the repo would be a unneeded bottleneck. > > So perhaps one maintainable way for you is to have a single script > (packaged up in a OLPC specific RPM) that does all the munging and your > %post simple invokes this? That script would know about per-country > things and what kind of "image" (e.g. jffs2, livecd, disk_ext3 etc.) > you're building by having the %post pass it as options? Wouldn't that > work? > > Of course, the question I raised in an earlier mail of how we pass items > to the %post script in the Kickstart file still stands. Jeremy? Perhaps > just setting environment variables works out of the box. I'd be > surprised if this is not the case. > > Also, external variables used by higher level constructs that does batch > builds in a structured way (e.g. pilgrim-autobuild) needs to pass > (OLPC-specific) variables too such as BUILD_NUMBER, TARGET_COUNTRY etc. > to %post. I think the way I'd like this to work is that such variables > are transparently passed by livecd-tools and then the %post takes care > of it. Perhaps it would look like this > > %post > olpc-configure-system --image-type $LIVECD_TOOLS_IMAGE_TYPE \ > --olpc-build-number $OLPC_IMAGE_NUMBER \ > --olpc-target $OLPC_TARGET_COUNTRY > > Would that work for you? In some ways it does but then again it isn't a standard solution but just a workaround. It still means no quick turnaround for testing but that is all a failing of our build system. %post to me is a workaround all together. I would really have liked this to be more declarative, then tools could be written which had context to what is going on instead of this RPM black box. A couple of things are already declarative in ks such as turning on and off default init scripts. I would have liked to have had more intelligent systems. For instance with the RPM method inheritance is at the whim of how the post in the RPM is written. For the most part people will get it right but there is also the issue that I can't optimize either. If it was declarative a tool could say this file is going to be overwritten by a later declaration so there is no need to write it out. I guess I am in a camp which believes we need to get away from the flexibility of scripting around deficiencies in our higher level tools and instead make the tools more robust and able to handle the corner cases. From davidz at redhat.com Fri Apr 27 18:37:27 2007 From: davidz at redhat.com (David Zeuthen) Date: Fri, 27 Apr 2007 14:37:27 -0400 Subject: [Fedora-livecd-list] SSH defualt on livecd bootup In-Reply-To: <46321DE0.8030703@gmail.com> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> <46321DE0.8030703@gmail.com> Message-ID: <1177699047.2773.1.camel@zelda.fubar.dk> On Fri, 2007-04-27 at 11:59 -0400, Steve Berry wrote: > I noticed I can't ssh telnet into a livecd - I'm guessing this was > disabled for security reasons. > > can someone tell me why exactly? > > I would have loved to boot an old box with f7-test4 i386 and telneted > over, configured vncserver to allow me to control it from remote. then > install it from the cd to the harddrive and reboot it without hooking a > monitor up to it. Mostly that ssh server key generation takes ages thus slowing down the already slow boot process. Also, the passwords are all blank. David From johnp at redhat.com Fri Apr 27 18:44:29 2007 From: johnp at redhat.com (John (J5) Palmieri) Date: Fri, 27 Apr 2007 14:44:29 -0400 Subject: [Fedora-livecd-list] Support for custom configuration using python templates In-Reply-To: <1177695911.3486.53.camel@localhost.localdomain> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> <1177695911.3486.53.camel@localhost.localdomain> Message-ID: <1177699469.3486.56.camel@localhost.localdomain> On Fri, 2007-04-27 at 13:45 -0400, John (J5) Palmieri wrote: > On Thu, 2007-04-26 at 21:44 -0400, David Zeuthen wrote: > > On Thu, 2007-04-26 at 16:51 -0400, John (J5) Palmieri wrote: > > > > I think munging configuration files might be outside the scope of the > > > > livecd-tools project; sure, granted it's something people want to do but > > > > often it's used as a hack; for example on my system > > > > > > > > $ rpm -qf /etc/issue > > > > fedora-release-6.93-1 > > > > > > And I'm going to package that up for every daily release? And what > > > about countries? Too heavy and engineered for an image based > > > distribution. > > > > [...] > > > > > > so I think what you *could* do instead is to have olpc-release or > > > > similar on OLPC provide that file (would be based on fedora-release). Of > > > > course, since /etc/issue is marked as %config(noreplace) in the > > > > fedora-release it's still sane for you to edit it in %post. I guess it > > > > all depends on the configuration file in question. > > > > I think I said that both approaches works. Just make sure all files > > being changed are tagged with %config(noreplace) if you care about RPM > > upgrade paths (which you probably don't need to for OLPC but it's nice > > nonetheless if someone wants to pick this up for hardware that can cope > > with yum/rpm etc.). > > > > > > So I think my point of view right now is that it's good enough to do > > > > this in %post for most cases; I mean, if downstreams (like OLPC) need to > > > > change a ton of configuration files/defaults perhaps there is something > > > > broken with the apps you try to include? > > > > > > No just that apps can be configured for different purposes. For > > > instance gedit can be made into a development environment but requires > > > me to write out a bunch of gconf files. We have Sabyon for a reason. > > > It basically does what I want to do in the case of gconf and some other > > > settings. It is a dump of configuration files. > > > > Sure, or you can use gconftool-2 or Puppet as Mark mentioned or > > basically anything that gets the job done. My point really was that I > > don't think configuration file munging belongs in livecd-tools proper. > > Do you think that's wrong? > > > > > > Perhaps you can come up with concrete examples of what configuration > > > > files / defaults you need to edit /change? I think that would be useful. > > > > Thanks. > > > > > > /etc/sysconfig/modules/olpc-1.modules for the module lists to load > > > /etc/rwtab for stateless tmpfs mounted stuff > > > /etc/asound.state to put the correct default sound levels > > > /etc/modprobe.d/olpc.conf.dist so we get the correct module parameters > > > /boot/olpc_build for build info that the bootloader uses > > > /etc/issue for build info the user can read > > > /etc/securetty for adding the serial console > > > /etc/inittab for removing unneeded memory waisting VT's > > > /usr/share/fonts/dejavu-lgc/fonts.dir for mapping legacy fonts > > > /usr/share/fonts/dejavu-lgc/fonts.scale same as above > > > /usr/share/fonts/dejavu-lgc/fonts.alias same > > > /etc/X11/xorg.conf and its variants for booting on any device and > > > getting the correct xorg config file with the correct keyboard laysouts > > > /home/olpc/.xinitrc for launching sugar > > > /boot/grub/grub.conf for the occasional qemu boot > > > /etc/init.d/olpc-configure init script for boot time configuration > > > /usr/share/X11/xkb/symbols/* for keyboard configuration that is not yet > > > upstream (note that these must be added to an already existing file) > > > /boot/olpc.fth - for booting from openfirmware > > > > > > Note that we can't move a lot of these to an RPM because RPM conflict > > > rules would prevent them from being installed. Some files need input > > > such as BUILD number and some files change so rapidly during the testing > > > phase that taking the time to build an rpm and place it in the right > > > spot and rebuild the repo would be a unneeded bottleneck. > > > > So perhaps one maintainable way for you is to have a single script > > (packaged up in a OLPC specific RPM) that does all the munging and your > > %post simple invokes this? That script would know about per-country > > things and what kind of "image" (e.g. jffs2, livecd, disk_ext3 etc.) > > you're building by having the %post pass it as options? Wouldn't that > > work? > > > > Of course, the question I raised in an earlier mail of how we pass items > > to the %post script in the Kickstart file still stands. Jeremy? Perhaps > > just setting environment variables works out of the box. I'd be > > surprised if this is not the case. > > > > Also, external variables used by higher level constructs that does batch > > builds in a structured way (e.g. pilgrim-autobuild) needs to pass > > (OLPC-specific) variables too such as BUILD_NUMBER, TARGET_COUNTRY etc. > > to %post. I think the way I'd like this to work is that such variables > > are transparently passed by livecd-tools and then the %post takes care > > of it. Perhaps it would look like this > > > > %post > > olpc-configure-system --image-type $LIVECD_TOOLS_IMAGE_TYPE \ > > --olpc-build-number $OLPC_IMAGE_NUMBER \ > > --olpc-target $OLPC_TARGET_COUNTRY > > > > Would that work for you? > > In some ways it does but then again it isn't a standard solution but > just a workaround. It still means no quick turnaround for testing but > that is all a failing of our build system. > > %post to me is a workaround all together. I would really have liked > this to be more declarative, then tools could be written which had > context to what is going on instead of this RPM black box. A couple of > things are already declarative in ks such as turning on and off default > init scripts. I would have liked to have had more intelligent systems. > For instance with the RPM method inheritance is at the whim of how the > post in the RPM is written. For the most part people will get it right > but there is also the issue that I can't optimize either. If it was > declarative a tool could say this file is going to be overwritten by a > later declaration so there is no need to write it out. > > I guess I am in a camp which believes we need to get away from the > flexibility of scripting around deficiencies in our higher level tools > and instead make the tools more robust and able to handle the corner > cases. > Actually the RPM idea still has some flaws. It leaves junk config templates laying around. Even if you delete them on systems where we want the ability to rpm upgrade they will get the new templates. Not ideal. -- John (J5) Palmieri From davidz at redhat.com Fri Apr 27 18:43:44 2007 From: davidz at redhat.com (David Zeuthen) Date: Fri, 27 Apr 2007 14:43:44 -0400 Subject: [Fedora-livecd-list] Support for custom configuration using python templates In-Reply-To: <1177695911.3486.53.camel@localhost.localdomain> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> <1177695911.3486.53.camel@localhost.localdomain> Message-ID: <1177699424.2773.5.camel@zelda.fubar.dk> On Fri, 2007-04-27 at 13:45 -0400, John (J5) Palmieri wrote: > > %post > > olpc-configure-system --image-type $LIVECD_TOOLS_IMAGE_TYPE \ > > --olpc-build-number $OLPC_IMAGE_NUMBER \ > > --olpc-target $OLPC_TARGET_COUNTRY > > > > Would that work for you? > > In some ways it does but then again it isn't a standard solution but > just a workaround. It still means no quick turnaround for testing but > that is all a failing of our build system. > > %post to me is a workaround all together. I would really have liked > this to be more declarative, then tools could be written which had > context to what is going on instead of this RPM black box. A couple of > things are already declarative in ks such as turning on and off default > init scripts. I would have liked to have had more intelligent systems. > For instance with the RPM method inheritance is at the whim of how the > post in the RPM is written. For the most part people will get it right > but there is also the issue that I can't optimize either. If it was > declarative a tool could say this file is going to be overwritten by a > later declaration so there is no need to write it out. > > I guess I am in a camp which believes we need to get away from the > flexibility of scripting around deficiencies in our higher level tools > and instead make the tools more robust and able to handle the corner > cases. Yeah, it's not that I disagree with that; it's just the way some things work in the distro are not really optimized for custom distros just yet. Note that this is not something specific to livecd-tools; you want these features to apply to normal spins and other installation methods as well. I believe both Bill and Mark did a lot of thinking on this topic and Bill even went as far as to propose it for Fedora 7 http://fedoraproject.org/wiki/Releases/FeatureCustomDistro but that feature didn't make it in. Definitely worth thinking more about... David From jasperhartline at adelphia.net Fri Apr 27 19:00:38 2007 From: jasperhartline at adelphia.net (Jasper Hartline) Date: Fri, 27 Apr 2007 14:00:38 -0500 Subject: [Fedora-livecd-list] SSH defualt on livecd bootup In-Reply-To: <1177699047.2773.1.camel@zelda.fubar.dk> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> <46321DE0.8030703@gmail.com> <1177699047.2773.1.camel@zelda.fubar.dk> Message-ID: <46324856.3090305@adelphia.net> David Zeuthen wrote: > > Mostly that ssh server key generation takes ages thus slowing down the > already slow boot process. Also, the passwords are all blank. > > David > I think the slow boot process is due to the Ext3 filesystem you have decided to use. Also, the SSH key generation doesn't take more than 6 seconds on a dual PII at 300MHz, less than 2 seconds on a Intel Celeron at 2.6GHz. That isn't exactly "ages". I would contribute it to the filesystem you have decided to use. J. Hartline From davidz at redhat.com Fri Apr 27 19:16:01 2007 From: davidz at redhat.com (David Zeuthen) Date: Fri, 27 Apr 2007 15:16:01 -0400 Subject: [Fedora-livecd-list] SSH defualt on livecd bootup In-Reply-To: <46324856.3090305@adelphia.net> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> <46321DE0.8030703@gmail.com> <1177699047.2773.1.camel@zelda.fubar.dk> <46324856.3090305@adelphia.net> Message-ID: <1177701361.2773.14.camel@zelda.fubar.dk> On Fri, 2007-04-27 at 14:00 -0500, Jasper Hartline wrote: > David Zeuthen wrote: > > > > Mostly that ssh server key generation takes ages thus slowing down the > > already slow boot process. Also, the passwords are all blank. > > > > David > > > I think the slow boot process is due to the Ext3 filesystem you have > decided to use. I hate to repeat myself, but here we go. Using ext3 is a very conscious decision: 1) it support very quick live cd installs; just dd the data instead of doing an RPM transaction that requires you to carry at least twice the amount of data. 2) ext3 actually supports xattrs so SELinux just works out of the box. This is pretty important from a "let's market Fedora" point of view. 3) it's the standard file system used by Fedora > Also, the SSH key generation doesn't take more than 6 seconds on a dual > PII at 300MHz, less than 2 > seconds on a Intel Celeron at 2.6GHz. That isn't exactly "ages". I seem to remember it's a lot more but whatever. Even if this was fast it wouldn't make sense for generic live CD's to include this feature as the passwords would still be empty. Custom live cd's is another matter of course. Btw, the key generation process is CPU-bound so it's a bit hard for me to understand why you blame the file system since that's mostly IO performance. I also don't think it's useful for you to make unsubstantiated claims about ext3's performance or the lack of. Do you numbers to back your statements up? Because if you have I'd love to see them so I can pass them on to our ext3 developers. Thanks! David From katzj at redhat.com Fri Apr 27 19:32:26 2007 From: katzj at redhat.com (Jeremy Katz) Date: Fri, 27 Apr 2007 15:32:26 -0400 Subject: [Fedora-livecd-list] SSH defualt on livecd bootup In-Reply-To: <1177701361.2773.14.camel@zelda.fubar.dk> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> <46321DE0.8030703@gmail.com> <1177699047.2773.1.camel@zelda.fubar.dk> <46324856.3090305@adelphia.net> <1177701361.2773.14.camel@zelda.fubar.dk> Message-ID: <1177702346.6286.0.camel@erebor.boston.redhat.com> On Fri, 2007-04-27 at 15:16 -0400, David Zeuthen wrote: > I seem to remember it's a lot more but whatever. Even if this was fast > it wouldn't make sense for generic live CD's to include this feature as > the passwords would still be empty. Custom live cd's is another matter > of course. And as it currently stands, it's easy to set the root pass with livecd-creator and _not_ disable sshd if that's what you want to do. Jeremy From katzj at redhat.com Fri Apr 27 19:52:06 2007 From: katzj at redhat.com (Jeremy Katz) Date: Fri, 27 Apr 2007 15:52:06 -0400 Subject: [Fedora-livecd-list] Support for custom configuration using python templates In-Reply-To: <1177695911.3486.53.camel@localhost.localdomain> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> <1177695911.3486.53.camel@localhost.localdomain> Message-ID: <1177703526.6286.13.camel@erebor.boston.redhat.com> On Fri, 2007-04-27 at 13:45 -0400, John (J5) Palmieri wrote: > %post to me is a workaround all together. I would really have liked > this to be more declarative, then tools could be written which had > context to what is going on instead of this RPM black box. A couple of > things are already declarative in ks such as turning on and off default > init scripts. The problem is that arbitrary substitutions within files really isn't declarative. Adding things that are (like services, etc) doesn't tend to be hard or that controversial. But when you get to the degree of what you're wanting, you really want a config management system like puppet, cfengine, etc. And I think that the _eventual_ answer is that we'll standardize on something like that as The Config Management Solution at which point a stronger integration into the config will make plenty of sense. But you don't really want to have integration with cfengine and puppet and ... -- instead, we need to get to where we can make an educated decision and stick with it. Jeremy From jasperhartline at adelphia.net Fri Apr 27 19:41:52 2007 From: jasperhartline at adelphia.net (Jasper Hartline) Date: Fri, 27 Apr 2007 14:41:52 -0500 Subject: [Fedora-livecd-list] SSH defualt on livecd bootup In-Reply-To: <1177702346.6286.0.camel@erebor.boston.redhat.com> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> <46321DE0.8030703@gmail.com> <1177699047.2773.1.camel@zelda.fubar.dk> <46324856.3090305@adelphia.net> <1177701361.2773.14.camel@zelda.fubar.dk> <1177702346.6286.0.camel@erebor.boston.redhat.com> Message-ID: <46325200.4070105@adelphia.net> Jeremy Katz wrote: > On Fri, 2007-04-27 at 15:16 -0400, David Zeuthen wrote: > >> I seem to remember it's a lot more but whatever. Even if this was fast >> it wouldn't make sense for generic live CD's to include this feature as >> the passwords would still be empty. Custom live cd's is another matter >> of course. >> > > And as it currently stands, it's easy to set the root pass with > livecd-creator and _not_ disable sshd if that's what you want to do. > > Absolutely. This is the value of having the tools which are used to master a LiveCD available to the public as Open Source Software. From jasperhartline at adelphia.net Fri Apr 27 19:40:56 2007 From: jasperhartline at adelphia.net (Jasper Hartline) Date: Fri, 27 Apr 2007 14:40:56 -0500 Subject: [Fedora-livecd-list] SSH defualt on livecd bootup In-Reply-To: <1177701361.2773.14.camel@zelda.fubar.dk> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> <46321DE0.8030703@gmail.com> <1177699047.2773.1.camel@zelda.fubar.dk> <46324856.3090305@adelphia.net> <1177701361.2773.14.camel@zelda.fubar.dk> Message-ID: <463251C8.90902@adelphia.net> David Zeuthen wrote: > On Fri, 2007-04-27 at 14:00 -0500, Jasper Hartline wrote: > >> David Zeuthen wrote: >> >>> Mostly that ssh server key generation takes ages thus slowing down the >>> already slow boot process. Also, the passwords are all blank. >>> >>> David >>> >>> >> I think the slow boot process is due to the Ext3 filesystem you have >> decided to use. >> > > I hate to repeat myself, but here we go. Using ext3 is a very conscious > decision: > I'm not arguing why you chose Ext3, I'm saying the slow boot process is probably due to Ext3. >> Btw, the key generation process is CPU-bound so it's a bit hard for me >> to understand why you blame the file system since that's mostly IO >> performance. I also don't think it's useful for you to make >> unsubstantiated claims about ext3's performance or the lack of. Do you >> numbers to back your statements up? Because if you have I'd love to see >> them so I can pass them on to our ext3 developers. Thanks! >> >> I never said the SSH key generation was due to Ext3, I said the boot process you describe is probably due to Ext3. Learn how to read, when you do come back with a valid retort. J. Hartline From katzj at redhat.com Fri Apr 27 19:56:53 2007 From: katzj at redhat.com (Jeremy Katz) Date: Fri, 27 Apr 2007 15:56:53 -0400 Subject: [Fedora-livecd-list] Inheritance In-Reply-To: <1177441318.3387.37.camel@localhost.localdomain> References: <1177441318.3387.37.camel@localhost.localdomain> Message-ID: <1177703813.6286.20.camel@erebor.boston.redhat.com> On Tue, 2007-04-24 at 15:01 -0400, John (J5) Palmieri wrote: > In the pilgrim tool it is fairly easy to inherit from "stream" files and > just expand a base image into a newer image. This means I can create a > base description for an image, with all the required rpms and %post > processing and then define another image description which adds more > rpms and does more post processing. We can even override hooks and > files in the child description. For instance our liveCD SDK has added > gnome packages but does not download the ondisk html library to save > space. This allows me to make changes to the base image which is > automatically reflected in the livecd image builds. > > The real reason we need this is for country builds. I know that the > livecd tools already have the ability to take an iso and add to it but I > also need the ability to do a build from scratch. First can the current > kickstart file format handle this and second how can we support this if > it does not? So there's the answer we have now, and then there's the longer term answer that's been discussed a tiny bit. The now answer is that you use %include and with that can do a substantial amount of what you're looking for. Basically, you could have your base config and then a country build could be %include /path/to/base.cfg lang fr_FR.UTF-8 (or something like that). And that should[1] work to let you get at least some simple inheritance. For more complex needs, we've talked a little in the past (where we is mostly clumens and I, but a few others also at various points) on ways to get a better concept of inheritance with the kickstart configs. The idea being that you parse one config, then the next, then the next. Mostly what's needed there is just a little work in pykickstart to ensure that doing a second parse pass doesn't blow up the world plus defining the syntax of how you say "inherit from foo" Jeremy From tchung at fedoraproject.org Fri Apr 27 19:57:56 2007 From: tchung at fedoraproject.org (Thomas Chung) Date: Fri, 27 Apr 2007 12:57:56 -0700 Subject: [Fedora-livecd-list] SSH defualt on livecd bootup In-Reply-To: <463251C8.90902@adelphia.net> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> <46321DE0.8030703@gmail.com> <1177699047.2773.1.camel@zelda.fubar.dk> <46324856.3090305@adelphia.net> <1177701361.2773.14.camel@zelda.fubar.dk> <463251C8.90902@adelphia.net> Message-ID: <369bce3b0704271257i7ca19b46n9b6c8634dfdad9a6@mail.gmail.com> On 4/27/07, Jasper Hartline wrote: > Learn how to read, when you do come back with a valid retort. Jasper, that was not necessary. :( Regards, -- Thomas Chung http://fedoraproject.org/wiki/ThomasChung From johnp at redhat.com Fri Apr 27 20:02:25 2007 From: johnp at redhat.com (John (J5) Palmieri) Date: Fri, 27 Apr 2007 16:02:25 -0400 Subject: [Fedora-livecd-list] Inheritance In-Reply-To: <1177703813.6286.20.camel@erebor.boston.redhat.com> References: <1177441318.3387.37.camel@localhost.localdomain> <1177703813.6286.20.camel@erebor.boston.redhat.com> Message-ID: <1177704145.3486.58.camel@localhost.localdomain> On Fri, 2007-04-27 at 15:56 -0400, Jeremy Katz wrote: > On Tue, 2007-04-24 at 15:01 -0400, John (J5) Palmieri wrote: > > In the pilgrim tool it is fairly easy to inherit from "stream" files and > > just expand a base image into a newer image. This means I can create a > > base description for an image, with all the required rpms and %post > > processing and then define another image description which adds more > > rpms and does more post processing. We can even override hooks and > > files in the child description. For instance our liveCD SDK has added > > gnome packages but does not download the ondisk html library to save > > space. This allows me to make changes to the base image which is > > automatically reflected in the livecd image builds. > > > > The real reason we need this is for country builds. I know that the > > livecd tools already have the ability to take an iso and add to it but I > > also need the ability to do a build from scratch. First can the current > > kickstart file format handle this and second how can we support this if > > it does not? > > So there's the answer we have now, and then there's the longer term > answer that's been discussed a tiny bit. > > The now answer is that you use %include and with that can do a > substantial amount of what you're looking for. Basically, you could > have your base config and then a country build could be > %include /path/to/base.cfg > lang fr_FR.UTF-8 > (or something like that). And that should[1] work to let you get at > least some simple inheritance. > > For more complex needs, we've talked a little in the past (where we is > mostly clumens and I, but a few others also at various points) on ways > to get a better concept of inheritance with the kickstart configs. The > idea being that you parse one config, then the next, then the next. > Mostly what's needed there is just a little work in pykickstart to > ensure that doing a second parse pass doesn't blow up the world plus > defining the syntax of how you say "inherit from foo" > > Jeremy Does this also pick up post scripts and run them in the right order? -- John (J5) Palmieri From katzj at redhat.com Fri Apr 27 20:04:53 2007 From: katzj at redhat.com (Jeremy Katz) Date: Fri, 27 Apr 2007 16:04:53 -0400 Subject: [Fedora-livecd-list] Targetting other file systems besides iso In-Reply-To: <1177522870.2769.30.camel@zelda.fubar.dk> References: <1177441849.3387.47.camel@localhost.localdomain> <1177522870.2769.30.camel@zelda.fubar.dk> Message-ID: <1177704293.6286.25.camel@erebor.boston.redhat.com> On Wed, 2007-04-25 at 13:41 -0400, David Zeuthen wrote: > On Tue, 2007-04-24 at 15:10 -0400, John (J5) Palmieri wrote: > > At OLPC we need to support ext3 and jffs2 builds even more so than > > livecd isos. Since most of the process is the same up until the final > > image and bootloaders we would like to add this support into the livecd > > tools so that all fedora projects use one toolchain. The question is > > how can this best be accomplished? > > > > I think passing a --variant switch (i.e. --variant=jffs2) should switch > > the backend to generating the correct image. > > I think adding an option > > --target=[livecd| > disk_msdos_ext3| > disk_msdos_ext3_separate_boot| > ext3| > jffs2] > > with this help text (for --help) But when we start getting to this degree of complication, I really start to wonder why we're reimplementing all of this stuff as opposed to instead moving in the direction of being able to generate all of these different things with anaconda. While anaconda isn't entirely there right now to be able to do this easily, if we're serious about wanting to generically generate images of a lot of different formats, then it's not *that* much work to get there. Yeah, it's more code and it's more of a learning curve to work on, but that's not necessarily a reason to move away. Jeremy From katzj at redhat.com Fri Apr 27 20:05:36 2007 From: katzj at redhat.com (Jeremy Katz) Date: Fri, 27 Apr 2007 16:05:36 -0400 Subject: [Fedora-livecd-list] Inheritance In-Reply-To: <1177704145.3486.58.camel@localhost.localdomain> References: <1177441318.3387.37.camel@localhost.localdomain> <1177703813.6286.20.camel@erebor.boston.redhat.com> <1177704145.3486.58.camel@localhost.localdomain> Message-ID: <1177704336.6286.27.camel@erebor.boston.redhat.com> On Fri, 2007-04-27 at 16:02 -0400, John (J5) Palmieri wrote: > On Fri, 2007-04-27 at 15:56 -0400, Jeremy Katz wrote: > > On Tue, 2007-04-24 at 15:01 -0400, John (J5) Palmieri wrote: > > > In the pilgrim tool it is fairly easy to inherit from "stream" files and > > > just expand a base image into a newer image. This means I can create a > > > base description for an image, with all the required rpms and %post > > > processing and then define another image description which adds more > > > rpms and does more post processing. We can even override hooks and > > > files in the child description. For instance our liveCD SDK has added > > > gnome packages but does not download the ondisk html library to save > > > space. This allows me to make changes to the base image which is > > > automatically reflected in the livecd image builds. > > > > > > The real reason we need this is for country builds. I know that the > > > livecd tools already have the ability to take an iso and add to it but I > > > also need the ability to do a build from scratch. First can the current > > > kickstart file format handle this and second how can we support this if > > > it does not? > > > > So there's the answer we have now, and then there's the longer term > > answer that's been discussed a tiny bit. > > > > The now answer is that you use %include and with that can do a > > substantial amount of what you're looking for. Basically, you could > > have your base config and then a country build could be > > %include /path/to/base.cfg > > lang fr_FR.UTF-8 > > (or something like that). And that should[1] work to let you get at > > least some simple inheritance. > > > > For more complex needs, we've talked a little in the past (where we is > > mostly clumens and I, but a few others also at various points) on ways > > to get a better concept of inheritance with the kickstart configs. The > > idea being that you parse one config, then the next, then the next. > > Mostly what's needed there is just a little work in pykickstart to > > ensure that doing a second parse pass doesn't blow up the world plus > > defining the syntax of how you say "inherit from foo" > > Does this also pick up post scripts and run them in the right order? I think the former does, but am not 100% sure without trying. The more complex and not done part definitely should when the code is written :-) Jeremy From jasperhartline at adelphia.net Fri Apr 27 20:08:35 2007 From: jasperhartline at adelphia.net (Jasper Hartline) Date: Fri, 27 Apr 2007 15:08:35 -0500 Subject: [Fedora-livecd-list] SSH defualt on livecd bootup In-Reply-To: <369bce3b0704271257i7ca19b46n9b6c8634dfdad9a6@mail.gmail.com> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> <46321DE0.8030703@gmail.com> <1177699047.2773.1.camel@zelda.fubar.dk> <46324856.3090305@adelphia.net> <1177701361.2773.14.camel@zelda.fubar.dk> <463251C8.90902@adelphia.net> <369bce3b0704271257i7ca19b46n9b6c8634dfdad9a6@mail.gmail.com> Message-ID: <46325843.70109@adelphia.net> Thomas Chung wrote: > On 4/27/07, Jasper Hartline wrote: >> Learn how to read, when you do come back with a valid retort. > > Jasper, that was not necessary. :( > Regards, Niether was his assumption I was talking about the SSH key generation being slow due to Ext3. Nowhere in my statement did I say "The SSH key generation is slow due to Ext3". He also said my claims were unsubstantiated, again going on an assumption of what I said which I never had. It's plain to see he is not a native English speaker. J. Hartline From davidz at redhat.com Fri Apr 27 20:33:34 2007 From: davidz at redhat.com (David Zeuthen) Date: Fri, 27 Apr 2007 16:33:34 -0400 Subject: [Fedora-livecd-list] SSH defualt on livecd bootup In-Reply-To: <46325843.70109@adelphia.net> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> <46321DE0.8030703@gmail.com> <1177699047.2773.1.camel@zelda.fubar.dk> <46324856.3090305@adelphia.net> <1177701361.2773.14.camel@zelda.fubar.dk> <463251C8.90902@adelphia.net> <369bce3b0704271257i7ca19b46n9b6c8634dfdad9a6@mail.gmail.com> <46325843.70109@adelphia.net> Message-ID: <1177706014.2773.37.camel@zelda.fubar.dk> On Fri, 2007-04-27 at 15:08 -0500, Jasper Hartline wrote: > He also said my claims were unsubstantiated, again going on an > assumption of what I said which I never had. Not at all. I asked you to clarify "I think the slow boot process is due to the Ext3 filesystem you have decided to use." because I don't think you really know what you're talking about. I'm still waiting for that clarification. > It's plain to see he is not a native English speaker. Would you rather I replied in Danish? Would that make you feel better? Anyway, Jasper, I know enough English to know that it's rude to talk about people present in the third person. I'm here. I've got a name. Refer to me as David, not as "he". Thanks. Your mail and whole line or arguing just makes me sad. It's so obvious, even to non-native English speakers such as myself, that you're just trolling obviously because I'm the person that ate your lunch by making Kadishci mostly irrelevant with pilgrim/livecd-tools. Well sorry about that Jasper. But that doesn't really justify you starting a witch-hunt against non-native English speakers. David From johnp at redhat.com Fri Apr 27 20:36:46 2007 From: johnp at redhat.com (John (J5) Palmieri) Date: Fri, 27 Apr 2007 16:36:46 -0400 Subject: [Fedora-livecd-list] SSH defualt on livecd bootup In-Reply-To: <46325843.70109@adelphia.net> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> <46321DE0.8030703@gmail.com> <1177699047.2773.1.camel@zelda.fubar.dk> <46324856.3090305@adelphia.net> <1177701361.2773.14.camel@zelda.fubar.dk> <463251C8.90902@adelphia.net> <369bce3b0704271257i7ca19b46n9b6c8634dfdad9a6@mail.gmail.com> <46325843.70109@adelphia.net> Message-ID: <1177706206.3486.68.camel@localhost.localdomain> On Fri, 2007-04-27 at 15:08 -0500, Jasper Hartline wrote: > Thomas Chung wrote: > > On 4/27/07, Jasper Hartline wrote: > >> Learn how to read, when you do come back with a valid retort. > > > > Jasper, that was not necessary. :( > > Regards, > Niether was his assumption I was talking about the SSH key generation > being slow due to Ext3. > Nowhere in my statement did I say "The SSH key generation is slow due to > Ext3". > > He also said my claims were unsubstantiated, again going on an > assumption of what I said which I never had. > It's plain to see he is not a native English speaker. Woh, calm down here. I think the issue is the context of the tread was ssh. Moving it to issues with ext3 is a whole other topic and your post was easy to misinterpret as saying ext3 was the reason ssh is slow. Language being language, missing a comma by the reader or author here or there can least to misinterpretations. Lets not get a simple misunderstanding to become an invitation to personal attacks. -- John (J5) Palmieri From johnp at redhat.com Fri Apr 27 20:52:49 2007 From: johnp at redhat.com (John (J5) Palmieri) Date: Fri, 27 Apr 2007 16:52:49 -0400 Subject: [Fedora-livecd-list] Targetting other file systems besides iso In-Reply-To: <1177704293.6286.25.camel@erebor.boston.redhat.com> References: <1177441849.3387.47.camel@localhost.localdomain> <1177522870.2769.30.camel@zelda.fubar.dk> <1177704293.6286.25.camel@erebor.boston.redhat.com> Message-ID: <1177707169.3486.76.camel@localhost.localdomain> On Fri, 2007-04-27 at 16:04 -0400, Jeremy Katz wrote: > On Wed, 2007-04-25 at 13:41 -0400, David Zeuthen wrote: > > On Tue, 2007-04-24 at 15:10 -0400, John (J5) Palmieri wrote: > > > At OLPC we need to support ext3 and jffs2 builds even more so than > > > livecd isos. Since most of the process is the same up until the final > > > image and bootloaders we would like to add this support into the livecd > > > tools so that all fedora projects use one toolchain. The question is > > > how can this best be accomplished? > > > > > > I think passing a --variant switch (i.e. --variant=jffs2) should switch > > > the backend to generating the correct image. > > > > I think adding an option > > > > --target=[livecd| > > disk_msdos_ext3| > > disk_msdos_ext3_separate_boot| > > ext3| > > jffs2] > > > > with this help text (for --help) > > But when we start getting to this degree of complication, I really start > to wonder why we're reimplementing all of this stuff as opposed to > instead moving in the direction of being able to generate all of these > different things with anaconda. While anaconda isn't entirely there > right now to be able to do this easily, if we're serious about wanting > to generically generate images of a lot of different formats, then it's > not *that* much work to get there. Yeah, it's more code and it's more > of a learning curve to work on, but that's not necessarily a reason to > move away. I'm 100% with you here. Though the nice thing with livecd is that it is easy for someone to jump into. I would love one installer tool to rule them all and spend time shaping up fedora packages so that no matter what target you choose it all just works. -- John (J5) Palmieri From jasperhartline at adelphia.net Fri Apr 27 20:46:07 2007 From: jasperhartline at adelphia.net (Jasper Hartline) Date: Fri, 27 Apr 2007 15:46:07 -0500 Subject: [Fedora-livecd-list] SSH defualt on livecd bootup In-Reply-To: <1177706014.2773.37.camel@zelda.fubar.dk> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> <46321DE0.8030703@gmail.com> <1177699047.2773.1.camel@zelda.fubar.dk> <46324856.3090305@adelphia.net> <1177701361.2773.14.camel@zelda.fubar.dk> <463251C8.90902@adelphia.net> <369bce3b0704271257i7ca19b46n9b6c8634dfdad9a6@mail.gmail.com> <46325843.70109@adelphia.net> <1177706014.2773.37.camel@zelda.fubar.dk> Message-ID: <4632610F.3010305@adelphia.net> David Zeuthen wrote: > On Fri, 2007-04-27 at 15:08 -0500, Jasper Hartline wrote: > >> He also said my claims were unsubstantiated, again going on an >> assumption of what I said which I never had. >> > > Not at all. I asked you to clarify "I think the slow boot process is due > to the Ext3 filesystem you have decided to use." because I don't think > you really know what you're talking about. I'm still waiting for that > clarification. > > SquashFS is much faster than the uncompressed Ext3 which Pilgrim and livecd-tools uses. >> It's plain to see he is not a native English speaker. >> > > Would you rather I replied in Danish? Would that make you feel better? > Anyway, Jasper, I know enough English to know that it's rude to talk > about people present in the third person. I'm here. I've got a name. > Refer to me as David, not as "he". Thanks. > I was replying to someone who was commenting on my comment to you, I wasn't talking to you. Again, you are far from knowing enough English to know this obviously. > Your mail and whole line or arguing just makes me sad. It's so obvious, > even to non-native English speakers such as myself, that you're just > trolling obviously because I'm the person that ate your lunch by making > Kadishci mostly irrelevant with pilgrim/livecd-tools. Well sorry about > that Jasper. But that doesn't really justify you starting a witch-hunt > against non-native English speakers. > You were the one who made the assumption I was talking about SSH keys generation being slow due to Ext3. Let me clarify: You state starting SSHD would not be good for the already slow boot process. I stated, the boot process is probably slow due to Ext3. I also added that SSH key generation on a dual PII at 300MHz takes a mere 6 seconds or less and that on an Intel Celeron at 2.6GHz took maybe 2 seconds. Now you're going to try to sit here and cover up the fact you are far from an English major, and that you did not make a mistake assuming what you did, and try to sidetrack your flaws in personality claiming I'm on a witch hunt because of some software? Explain. J. Hartline From davidz at redhat.com Fri Apr 27 21:38:43 2007 From: davidz at redhat.com (David Zeuthen) Date: Fri, 27 Apr 2007 17:38:43 -0400 Subject: [Fedora-livecd-list] SSH defualt on livecd bootup In-Reply-To: <4632610F.3010305@adelphia.net> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> <46321DE0.8030703@gmail.com> <1177699047.2773.1.camel@zelda.fubar.dk> <46324856.3090305@adelphia.net> <1177701361.2773.14.camel@zelda.fubar.dk> <463251C8.90902@adelphia.net> <369bce3b0704271257i7ca19b46n9b6c8634dfdad9a6@mail.gmail.com> <46325843.70109@adelphia.net> <1177706014.2773.37.camel@zelda.fubar.dk> <4632610F.3010305@adelphia.net> Message-ID: <1177709923.2773.44.camel@zelda.fubar.dk> On Fri, 2007-04-27 at 15:46 -0500, Jasper Hartline wrote: > Explain. Jasper, for det f?rste skylder jeg ikke dig nogen forklaring. For det andet har jeg bedre ting at bruge min tid p?. Held og lykke, du har _virkelig_ brug for det. David From jasperhartline at adelphia.net Fri Apr 27 21:44:11 2007 From: jasperhartline at adelphia.net (Jasper Hartline) Date: Fri, 27 Apr 2007 16:44:11 -0500 Subject: [Fedora-livecd-list] SSH defualt on livecd bootup In-Reply-To: <1177709923.2773.44.camel@zelda.fubar.dk> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> <46321DE0.8030703@gmail.com> <1177699047.2773.1.camel@zelda.fubar.dk> <46324856.3090305@adelphia.net> <1177701361.2773.14.camel@zelda.fubar.dk> <463251C8.90902@adelphia.net> <369bce3b0704271257i7ca19b46n9b6c8634dfdad9a6@mail.gmail.com> <46325843.70109@adelphia.net> <1177706014.2773.37.camel@zelda.fubar.dk> <4632610F.3010305@adelphia.net> <1177709923.2773.44.camel@zelda.fubar.dk> Message-ID: <46326EAB.2020902@adelphia.net> David Zeuthen wrote: > On Fri, 2007-04-27 at 15:46 -0500, Jasper Hartline wrote: > >> Explain. >> > > Jasper, for det f?rste skylder jeg ikke dig nogen forklaring. For det > andet har jeg bedre ting at bruge min tid p?. Held og lykke, du har > _virkelig_ brug for det. > You sure felt like explaining why you chose Ext3, when I was not debating WHY you chose Ext3, but merely suggested it is probably what makes the boot process slow. So are you just confused, or are you seriously going to try to win such an argument stating opinions as facts you cannot prove? J. Hartline From sundaram at fedoraproject.org Fri Apr 27 21:54:22 2007 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Sat, 28 Apr 2007 03:24:22 +0530 Subject: [Fedora-livecd-list] SSH defualt on livecd bootup In-Reply-To: <46326EAB.2020902@adelphia.net> References: <1177440837.3387.28.camel@localhost.localdomain> <1177520292.2769.16.camel@zelda.fubar.dk> <1177620716.3404.50.camel@localhost.localdomain> <1177638267.2986.20.camel@zelda.fubar.dk> <46321DE0.8030703@gmail.com> <1177699047.2773.1.camel@zelda.fubar.dk> <46324856.3090305@adelphia.net> <1177701361.2773.14.camel@zelda.fubar.dk> <463251C8.90902@adelphia.net> <369bce3b0704271257i7ca19b46n9b6c8634dfdad9a6@mail.gmail.com> <46325843.70109@adelphia.net> <1177706014.2773.37.camel@zelda.fubar.dk> <4632610F.3010305@adelphia.net> <1177709923.2773.44.camel@zelda.fubar.dk> <46326EAB.2020902@adelphia.net> Message-ID: <4632710E.1050407@fedoraproject.org> Jasper Hartline wrote: > David Zeuthen wrote: >> On Fri, 2007-04-27 at 15:46 -0500, Jasper Hartline wrote: >> >>> Explain. >>> >> >> Jasper, for det f?rste skylder jeg ikke dig nogen forklaring. For det >> andet har jeg bedre ting at bruge min tid p?. Held og lykke, du har >> _virkelig_ brug for det. >> > You sure felt like explaining why you chose Ext3, when I was not > debating WHY you chose > Ext3, but merely suggested it is probably what makes the boot process slow. > > So are you just confused, or are you seriously going to try to win such > an argument > stating opinions as facts you cannot prove? Jasper, your original message was confusing to me too. Your comparison on SSH key generation times vs cpu speed atleast implied that you thought the process was cpu bound. This is not something related to whether someone speaks English as their native language or not. At any rate this conversation is going nowhere useful. Just drop it and move on folks. Rahul From sundaram at fedoraproject.org Sat Apr 28 01:05:11 2007 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Sat, 28 Apr 2007 06:35:11 +0530 Subject: [Fedora-livecd-list] Fedora 7 Test 4 GNOME based i386 Live CD report Message-ID: <46329DC7.9010500@fedoraproject.org> Hi Just installed the F7 T4 GNOME based i386 live cd and here are some of my observations after playing with it for a day. * You do not need to accept the EULA anymore. It just has a pointer to the wiki link instead of including the text. * Smolt integration UI is good and works well. Noticed that it said it would update the profile automatically on a monthly basis. My test system profile is http://smolt.fedoraproject.org/show?UUID=492900d9-5ee0-441c-9792-fc2ecc86aa5d * Look and feel is good. Flying high theme with Mist based icon set. * Firefox and Evolution are the default panel applications but seem to be using the old Blue Curve icons. * Network manager (nm-applet) is enabled by default * Blog, stock ticker, bittorrent and gparted applications installed by default * fast user switcher applet is on the panel by default and shows up on the lock screen. too. * Multiple locales and input methods available by default * Abiword does not crash on startup anymore. gnumeric is also available but we are missing a small presentation program to complete this sort of mini office suite. * Beagle is installed by default and replaces gnome-search-tool on the UI like the previous release. Might be better to keep these entries separate. * gThumb and GIMP are available by default but not f-spot. * Pigdin has replaced Gaim. Has new icons and a better interface. * Wodim has replaced cdrecord. cdrecord is a symlink to wodim and works as expected. * New application, system-config-selinux is available under administration. Looks pretty comprehensive. SELinux boolean configuration has been removed from system-config-securitylevel and is now available in this tool. Title says "system-config-selinux.py" instead of just "system-config-selinux" which is a minor wart in the UI. * Places and /home/ is filled by default folders for documents, video etc. Might look less cluttered if those default folder were under a common parent. /home//personal/ for example. * Preferences menu is organized into multiple categories now. The central control panel that GNOME includes is disabled by default (upstream inherited) but can be enabled using alacarte. Menu editor is a entry now in the preferences menu. * Yum is faster. Pirut and Pup UI does not appear to hang anymore. * About Fedora menu entry uses old wordings and says Fedora people instead of Planet Fedora as we have agreed upon now for consistency. * nautilus-open-terminal extension was not installed by default unlike previous live cd releases. * SCIM input icon doesnt show up on the system tray unlike the previous test release. Default is showing on demand but setting it to show always does not make it show up on the system tray. * nautilus has crashed more than once during login including the previous test releases with some vague bonobo error which I did not note down. Anyone else seeing this? * Turning on desktop effects immediately makes it crash Xorg * shutdown entry showed up twice as first and last entries in the system menu just once. Rest later, Rahul From mclasen at redhat.com Sat Apr 28 01:24:06 2007 From: mclasen at redhat.com (Matthias Clasen) Date: Fri, 27 Apr 2007 21:24:06 -0400 Subject: [Fedora-livecd-list] Re: Fedora 7 Test 4 GNOME based i386 Live CD report In-Reply-To: <46329DC7.9010500@fedoraproject.org> References: <46329DC7.9010500@fedoraproject.org> Message-ID: <1177723446.3656.6.camel@localhost.localdomain> On Sat, 2007-04-28 at 06:35 +0530, Rahul Sundaram wrote: > Hi > > Just installed the F7 T4 GNOME based i386 live cd and here are some of > my observations after playing with it for a day. > * Beagle is installed by default and replaces gnome-search-tool on the > UI like the previous release. Might be better to keep these entries > separate. No. Offering several different search tools in the menu is a bad idea. Medium-term, we're hoping to see a unified frontend for the various indexers. > * New application, system-config-selinux is available under > administration. Looks pretty comprehensive. SELinux boolean > configuration has been removed from system-config-securitylevel and is > now available in this tool. Title says "system-config-selinux.py" > instead of just "system-config-selinux" which is a minor wart in the UI. The bigger wart is that the menu entry for system-config-securitylevel still says "Firewall and SELinux" even though SELinux was removed... > * nautilus-open-terminal extension was not installed by default unlike > previous live cd releases. This live cd is just following the comps defaults here. The FC6 live cd was following David Z.s personal preferences... > * SCIM input icon doesnt show up on the system tray unlike the previous > test release. Default is showing on demand but setting it to show always > does not make it show up on the system tray. You should get it by default if you are logging in in a CJK locale. For other locales, use the "input method" capplet to turn it on. > * nautilus has crashed more than once during login including the > previous test releases with some vague bonobo error which I did not note > down. Anyone else seeing this? File a bug ? > * Turning on desktop effects immediately makes it crash Xorg Dito. > * shutdown entry showed up twice as first and last entries in the system > menu just once. > I have seen this once before, but then it repaired itself. Please file panel bug for this, too. Matthias From sundaram at redhat.com Sat Apr 28 02:31:16 2007 From: sundaram at redhat.com (Rahul Sundaram) Date: Sat, 28 Apr 2007 08:01:16 +0530 Subject: [Fedora-livecd-list] Re: Fedora 7 Test 4 GNOME based i386 Live CD report In-Reply-To: <1177723446.3656.6.camel@localhost.localdomain> References: <46329DC7.9010500@fedoraproject.org> <1177723446.3656.6.camel@localhost.localdomain> Message-ID: <4632B1F4.8060503@redhat.com> Matthias Clasen wrote: > On Sat, 2007-04-28 at 06:35 +0530, Rahul Sundaram wrote: > >> * Beagle is installed by default and replaces gnome-search-tool on the >> UI like the previous release. Might be better to keep these entries >> separate. > > No. Offering several different search tools in the menu is a bad idea. > Medium-term, we're hoping to see a unified frontend for the various > indexers. I understand the long term view but there are two short term rather prominent issues 1) Beagle sucks up CPU 2) With the default settings searching there gets no results. I still think Beagle should either not by installed by default because of relative immaturity or atleast by separate from the gnome-search-tool in the UI so that I can keep using it without having to uninstall beagle to get the UI option back. Tomboy is pretty useful though it is not visible in the user interface. I think we can place it in the panel by default along with Abiword in the GNOME based live images atleast. The prime spin still has Firefox, Evolution and three openoffice.org applications which makes sense for RHEL but not for Fedora. I would prefer something more home user oriented for Fedora. Forgot to mention that ntfs-3g is installed by default which is pretty good. I am not sure that's the case for the prime spin but since it uses the same comps.xml I hope that's the case. Someone please confirm this. >> * New application, system-config-selinux is available under >> administration. Looks pretty comprehensive. SELinux boolean >> configuration has been removed from system-config-securitylevel and is >> now available in this tool. Title says "system-config-selinux.py" >> instead of just "system-config-selinux" which is a minor wart in the UI. > > The bigger wart is that the menu entry for system-config-securitylevel > still says "Firewall and SELinux" even though SELinux was removed... You can still toggle between enable/disable/permissive modes so I am not sure that's a wart. If we remove it completely which might be better since the menu entry needs to be fixed. You have already reported this in https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234155. system-config-selinux is not available as a bugzilla component so I am adding some comments to the above bug report. Running a console helper enabled application that requires root access to do something makes the root password prompt a modal dialog box. This is not a change in behavior but it seems useful to make it a dialog box that can be attended to later. >> * nautilus-open-terminal extension was not installed by default unlike >> previous live cd releases. > > This live cd is just following the comps defaults here. The FC6 live cd > was following David Z.s personal preferences... RHEL 5 has this extension installed by default if that matters. Mugshot stats show the gnome terminal as one of the top three popular applications being used and this extension is pretty small so it might be useful to make it available by default. >> * SCIM input icon doesnt show up on the system tray unlike the previous >> test release. Default is showing on demand but setting it to show always >> does not make it show up on the system tray. > > You should get it by default if you are logging in in a CJK locale. For > other locales, use the "input method" capplet to turn it on. I am in the default English locale and I had to select custom input method and choose scim (which was the only option) instead of the system wide configuration (scim) setting which was enabled by default. If both of these were using the scim methods why would choosing one of them make a difference here? If scim is the only "custom" input method available should that option even be enabled? Relogging and left click on the hardly visible light grey icon does nothing. I couldn't figure out how to enable Tamil as a alternative input method while logging into the English locale. The SCIM setup UI does not seem to be following GNOME HIG. All of this user interface details seems to be a mess that could use a cleanup. Some of this was discussed in https://www.redhat.com/archives/fedora-maintainers/2007-April/msg00376.html >> * nautilus has crashed more than once during login including the >> previous test releases with some vague bonobo error which I did not note >> down. Anyone else seeing this? > > File a bug ? https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=238227 >> * Turning on desktop effects immediately makes it crash Xorg > > Dito. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=206501 This was reported long back in Fedora Core 6. I have added some comments. Someone confirm whether this is VMWare specific. I am running the image using it. >> * shutdown entry showed up twice as first and last entries in the system >> menu just once. >> > I have seen this once before, but then it repaired itself. Please file > panel bug for this, too. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=238228. I was able to reproduce this now and a screenshot has been attached. Thanks Matthias. Rahul From mclasen at redhat.com Sat Apr 28 11:26:04 2007 From: mclasen at redhat.com (Matthias Clasen) Date: Sat, 28 Apr 2007 07:26:04 -0400 Subject: [Fedora-livecd-list] Re: Fedora 7 Test 4 GNOME based i386 Live CD report In-Reply-To: <4632B1F4.8060503@redhat.com> References: <46329DC7.9010500@fedoraproject.org> <1177723446.3656.6.camel@localhost.localdomain> <4632B1F4.8060503@redhat.com> Message-ID: <1177759564.3656.15.camel@localhost.localdomain> On Sat, 2007-04-28 at 08:01 +0530, Rahul Sundaram wrote: > >> * Beagle is installed by default and replaces gnome-search-tool on the > >> UI like the previous release. Might be better to keep these entries > >> separate. > > > > No. Offering several different search tools in the menu is a bad idea. > > Medium-term, we're hoping to see a unified frontend for the various > > indexers. > > I understand the long term view but there are two short term rather > prominent issues > > 1) Beagle sucks up CPU > 2) With the default settings searching there gets no results. > > I still think Beagle should either not by installed by default because > of relative immaturity or atleast by separate from the gnome-search-tool > in the UI so that I can keep using it without having to uninstall beagle > to get the UI option back Removing beagle or installing tracker instead is certainly something we can discuss for F8. > Tomboy is pretty useful though it is not visible in the user interface. > I think we can place it in the panel by default along with Abiword in > the GNOME based live images atleast. That too. > The prime spin still has Firefox, Evolution and three openoffice.org > applications which makes sense for RHEL but not for Fedora. I would > prefer something more home user oriented for Fedora. Why on earth do you think firefox, evolution and OOo don't make sense for Fedora users ? The only reason OOo is not on the livecd is space. > >> * SCIM input icon doesnt show up on the system tray unlike the previous > >> test release. Default is showing on demand but setting it to show always > >> does not make it show up on the system tray. > > > > You should get it by default if you are logging in in a CJK locale. For > > other locales, use the "input method" capplet to turn it on. > > I am in the default English locale and I had to select custom input > method and choose scim (which was the only option) instead of the system > wide configuration (scim) setting which was enabled by default. If both > of these were using the scim methods why would choosing one of them make > a difference here? If scim is the only "custom" input method available > should that option even be enabled? Relogging and left click on the > hardly visible light grey icon does nothing. I couldn't figure out how > to enable Tamil as a alternative input method while logging into the > English locale. The SCIM setup UI does not seem to be following GNOME > HIG. All of this user interface details seems to be a mess that could > use a cleanup. The input method capplet needs some revision, Warren posted about that some time ago. I hope he looks after getting that done for F7. Matthias From stevejberry at gmail.com Sat Apr 28 13:43:07 2007 From: stevejberry at gmail.com (Steve Berry) Date: Sat, 28 Apr 2007 09:43:07 -0400 Subject: [Fedora-livecd-list] Fedora 7 Test 4 GNOME based i386 Live CD - install to HD option + ssh In-Reply-To: <1177759564.3656.15.camel@localhost.localdomain> References: <46329DC7.9010500@fedoraproject.org> <1177723446.3656.6.camel@localhost.localdomain> <4632B1F4.8060503@redhat.com> <1177759564.3656.15.camel@localhost.localdomain> Message-ID: <46334F6B.5090002@gmail.com> I booted the livecd, and used it for like 5 hours with no problems, except i did notice if you logout and try to mess with the preferences for the greeter/user login it'll simply flip out. wasn't sure why. but if you click on things, the screen refreshes, and doesnt reload properly, it does this a number of times. I had to simply reboot. so whatever happened I'm not sure. after I came back I decided to wipe the hard drive and put the livecd image on it using the installer tool, - awesome process. very simple. The ONLY thing i noticed was SSH is disabled .. and personally. this made things slightly difficult to get this box up and running. if ssh was available. I could have : booted the box with the cd, logged in via ssh, fired up vncserver, came back to my desktop and connected... setup the hd install from remote, and rebooted. at that point, rebooted when required, then pull the cd out, ssh back in, do the same thing and do the rest of the configuration. all headless. if security was an issue. having direct access to the cdrom wouldn't matter. I can tear the box apart with a chainsaw for that matter. so security IS not a concern root access is flat out available to any computer on my network with a simple reboot of the computer from a button push and a livecd drop in. Please . turn ssh on by defualt. the livecd users of the world will benefit from it. OR .. at least turn it on once it goes HD install. this way at least we can shell into the box and do some configuration without hauling cables around to eyeball what's going on.. This inst a rant about SSH being disabled .. I just wanted to make sure people DO actually care that ssh is disabled. From jkeating at redhat.com Sat Apr 28 21:10:36 2007 From: jkeating at redhat.com (Jesse Keating) Date: Sat, 28 Apr 2007 14:10:36 -0700 Subject: [Fedora-livecd-list] Fedora 7 Test 4 GNOME based i386 Live CD - install to HD option + ssh In-Reply-To: <46334F6B.5090002@gmail.com> References: <46329DC7.9010500@fedoraproject.org> <1177759564.3656.15.camel@localhost.localdomain> <46334F6B.5090002@gmail.com> Message-ID: <200704281410.36508.jkeating@redhat.com> On Saturday 28 April 2007 06:43:07 Steve Berry wrote: > if security was an issue. having direct access to the cdrom wouldn't > matter. I can tear the box apart with a chainsaw for that matter. so > security IS not a concern > root access is flat out available to any computer on my network with a > simple reboot of the computer from a button push and a livecd drop in. > > Please . turn ssh on by defualt. the livecd users of the world will > benefit from it. OR .. at least turn it on once it goes HD install. > this way at least we can shell into the box and do some configuration > without hauling cables around to eyeball what's going on.. YOU have physical access to the box. Fred down the road who has network access to the same space that your Live box is on does _not_ have physical access, yet with ssh on could have root level access to your running environment. -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From sundaram at fedoraproject.org Sun Apr 29 01:09:10 2007 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Sun, 29 Apr 2007 06:39:10 +0530 Subject: [Fedora-livecd-list] Re: Fedora 7 Test 4 GNOME based i386 Live CD report In-Reply-To: <1177759564.3656.15.camel@localhost.localdomain> References: <46329DC7.9010500@fedoraproject.org> <1177723446.3656.6.camel@localhost.localdomain> <4632B1F4.8060503@redhat.com> <1177759564.3656.15.camel@localhost.localdomain> Message-ID: <4633F036.5060400@fedoraproject.org> Matthias Clasen wrote: >> The prime spin still has Firefox, Evolution and three openoffice.org >> applications which makes sense for RHEL but not for Fedora. I would >> prefer something more home user oriented for Fedora. > > Why on earth do you think firefox, evolution and OOo don't make sense > for Fedora users ? The only reason OOo is not on the livecd is space. I didn't say it does not make sense. Only that there are other applications more frequently compared to OO.o presentation or spreadsheet programs. You can look at mugshot stats at http://mugshot.org/applications for some idea. Firefox, Evolution, Openoffice.org writer, Gaim and Gnome terminal or Rhythmbox would be more appropriate IMO. Rahul From sundaram at fedoraproject.org Sun Apr 29 01:09:54 2007 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Sun, 29 Apr 2007 06:39:54 +0530 Subject: [Fedora-livecd-list] Fedora 7 Test 4 GNOME based i386 Live CD - install to HD option + ssh In-Reply-To: <46334F6B.5090002@gmail.com> References: <46329DC7.9010500@fedoraproject.org> <1177723446.3656.6.camel@localhost.localdomain> <4632B1F4.8060503@redhat.com> <1177759564.3656.15.camel@localhost.localdomain> <46334F6B.5090002@gmail.com> Message-ID: <4633F062.10704@fedoraproject.org> Steve Berry wrote: > I booted the livecd, and used it for like 5 hours with no problems, > except i did notice if you logout and try to mess with the preferences > for the greeter/user login > it'll simply flip out. wasn't sure why. but if you click on things, the > screen refreshes, and doesnt reload properly, it does this a number of > times. > > I had to simply reboot. so whatever happened I'm not sure. File a bug report. Rahul From stevejberry at gmail.com Sun Apr 29 10:22:25 2007 From: stevejberry at gmail.com (Steve Berry) Date: Sun, 29 Apr 2007 06:22:25 -0400 Subject: [Fedora-livecd-list] Fedora 7 Test 4 GNOME based i386 Live CD - install to HD option + ssh In-Reply-To: <200704281410.36508.jkeating@redhat.com> References: <46329DC7.9010500@fedoraproject.org> <1177759564.3656.15.camel@localhost.localdomain> <46334F6B.5090002@gmail.com> <200704281410.36508.jkeating@redhat.com> Message-ID: <463471E1.4020506@gmail.com> Jesse Keating wrote: > On Saturday 28 April 2007 06:43:07 Steve Berry wrote: > >> if security was an issue. having direct access to the cdrom wouldn't >> matter. I can tear the box apart with a chainsaw for that matter. so >> security IS not a concern >> root access is flat out available to any computer on my network with a >> simple reboot of the computer from a button push and a livecd drop in. >> >> Please . turn ssh on by defualt. the livecd users of the world will >> benefit from it. OR .. at least turn it on once it goes HD install. >> this way at least we can shell into the box and do some configuration >> without hauling cables around to eyeball what's going on.. >> > > YOU have physical access to the box. Fred down the road who has network > access to the same space that your Live box is on does _not_ have physical > access, yet with ssh on could have root level access to your running > environment. > > For matters of taste, *I* would prefer SSH enabled by default, the overall public may perfer it. I really don't know. but if no one KNEW, and it was implied ssh was enabled by defualt. it would make more sense to enable it on defualt. But since it's not, I suppose disabling it *due to root not having a password *(for ease of use) is a pretty good idea.. I had to think about it a bit, but I tend to agree. In lieu of ssh disabled, it's not impossible to spin off a personal livecd with root passworded (custom) and ssh enabled. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jasperhartline at adelphia.net Sun Apr 29 10:57:06 2007 From: jasperhartline at adelphia.net (Jasper Hartline) Date: Sun, 29 Apr 2007 05:57:06 -0500 Subject: [Fedora-livecd-list] Fedora 7 Test 4 GNOME based i386 Live CD - install to HD option + ssh In-Reply-To: <463471E1.4020506@gmail.com> References: <46329DC7.9010500@fedoraproject.org> <1177759564.3656.15.camel@localhost.localdomain> <46334F6B.5090002@gmail.com> <200704281410.36508.jkeating@redhat.com> <463471E1.4020506@gmail.com> Message-ID: <46347A02.5060802@adelphia.net> Steve Berry wrote: > For matters of taste, *I* would prefer SSH enabled by default, the > overall public may perfer it. I really don't know. but if no one > KNEW, and it was implied > ssh was enabled by defualt. it would make more sense to enable it on > defualt. > > But since it's not, I suppose disabling it *due to root not having a > password *(for ease of use) is a pretty good idea.. > > I had to think about it a bit, but I tend to agree. > > In lieu of ssh disabled, it's not impossible to spin off a personal > livecd with root passworded (custom) and ssh enabled. > If you cannot figure out a way to buid your own LiveCD with SSHD enabled with livecd-tools at this stage, you might consider looking into Kadischi. It provides a services menu after the initial installation process of the soon-to-be rootfs which allows you to configure the services you want started, login accounts you would like to create, and enables you to toggle and configure the firewall to your needs before the ISO is created. You can get it from here: http://fedoraproject.org/wiki/Kadischi Though, from what I've been told, and I know it should be possible to easily hack in these features you actually can enable SSHd and add openssh-server and openssh-clients as packages. J. Hartline From dwmw2 at infradead.org Sun Apr 29 13:31:57 2007 From: dwmw2 at infradead.org (David Woodhouse) Date: Sun, 29 Apr 2007 14:31:57 +0100 Subject: [Fedora-livecd-list] PowerPC support. Message-ID: <1177853517.3085.29.camel@pmac.infradead.org> At http://git.infradead.org/?p=users/dwmw2/livecd-ppc.git (git://git.infradead.org/~dwmw2/livecd-ppc.git) there's a set of patches which first introduces a little abstraction for the arch-specific configureBootloader() and createIso() functions, then implements the PPC version. 1. Allow mayflower path to be specified, to run from git tree 2, Remove syslinux from package lists; add it dynamically instead. 3. Move x86-specific functions (createIso, configureBootloader) into subclass 4. Only create isolinux/ directory in x86-specific configureBootloader() 5. Add PowerPC support, add pata_mpc52xx module to mayflower.conf The full patch is as follows... diff --git a/config/livecd-fedora-desktop.ks b/config/livecd-fedora-desktop.ks index 1ee6fba..780e201 100644 --- a/config/livecd-fedora-desktop.ks +++ b/config/livecd-fedora-desktop.ks @@ -23,7 +23,6 @@ services --enabled=NetworkManager,dhcdbd --disabled=network,sshd @dial-up @hardware-support @printing -syslinux kernel scim* diff --git a/config/livecd-fedora-kde.ks b/config/livecd-fedora-kde.ks index 20413b1..9aeceed 100644 --- a/config/livecd-fedora-kde.ks +++ b/config/livecd-fedora-kde.ks @@ -23,7 +23,6 @@ kernel dejavu-lgc-fonts setroubleshoot smolt -syslinux system-config-display xorg-x11-drivers diff --git a/config/livecd-fedora-minimal.ks b/config/livecd-fedora-minimal.ks index e8065b6..db52912 100644 --- a/config/livecd-fedora-minimal.ks +++ b/config/livecd-fedora-minimal.ks @@ -17,7 +17,6 @@ repo --name=a-extras-dev --baseurl=http://download.fedora.redhat.com/pub/fedora/ %packages bash kernel -syslinux passwd policycoreutils chkconfig diff --git a/config/livedvd-fedora-kde.ks b/config/livedvd-fedora-kde.ks index 1ed2f57..71aa122 100644 --- a/config/livedvd-fedora-kde.ks +++ b/config/livedvd-fedora-kde.ks @@ -23,7 +23,6 @@ kernel dejavu-lgc-fonts setroubleshoot smolt -syslinux system-config-display xorg-x11-drivers diff --git a/creator/livecd-creator b/creator/livecd-creator index a526b07..755e659 100755 --- a/creator/livecd-creator +++ b/creator/livecd-creator @@ -27,6 +27,8 @@ import traceback import subprocess import shutil import yum +import rpmUtils.arch +import rhpl import pykickstart.parser import pykickstart.version @@ -277,6 +279,178 @@ class LiveCDYum(yum.YumBase): cb.filelog = False return self.runTransaction(cb) +class InstallationArchPPC: + def __init__(self): + # For now we need anaconda-runtime, for bits like ofboot.b and mapping files. + # We could generate those ourselves though... + self.bootldr_package = ("yaboot","anaconda-runtime") + + def createIso(self, target): + """write out the live CD ISO""" + subprocess.call(["/usr/bin/mkisofs", "-o", "%s.iso" %(target.fs_label,), + "-hfs", "-hfs-bless", "%s/out/ppc/mac" %(target.build_dir), + "-hfs-volid", "%s" %(target.fs_label,), "-part", + "-map", "/usr/lib/anaconda-runtime/boot/mapping", + "-J", "-r", "-hide-rr-moved", "-no-desktop", + "-V", "%s" %(target.fs_label,), "%s/out" %(target.build_dir)]) + + def configureBootloader(self, target): + """configure the boot loader""" + + # Copy yaboot and ofboot.b in to mac directory + os.makedirs(target.build_dir + "/out/ppc/mac") + shutil.copyfile("%s/install_root/usr/lib/anaconda-runtime/boot/ofboot.b" %(target.build_dir), + "%s/out/ppc/mac/ofboot.b" %(target.build_dir,)) + shutil.copyfile("%s/install_root/usr/lib/yaboot/yaboot" %(target.build_dir), + "%s/out/ppc/mac/yaboot" %(target.build_dir,)) + + # Copy yaboot and ofboot.b in to mac directory + os.makedirs(target.build_dir + "/out/ppc/chrp") + shutil.copyfile("%s/install_root/usr/lib/anaconda-runtime/boot/bootinfo.txt" %(target.build_dir), + "%s/out/ppc/bootinfo.txt" %(target.build_dir,)) + shutil.copyfile("%s/install_root/usr/lib/yaboot/yaboot" %(target.build_dir), + "%s/out/ppc/chrp/yaboot" %(target.build_dir,)) + subprocess.call(["/usr/sbin/addnote", "%s/out/ppc/chrp/yaboot" %(target.build_dir,)]) + + os.makedirs(target.build_dir + "/out/ppc/ppc32") + shutil.copyfile("%s/install_root/boot/vmlinuz-%s" + %(target.build_dir, target.get_kernel_version()), + "%s/out/ppc/ppc32/vmlinuz" %(target.build_dir,)) + shutil.copyfile("%s/install_root/boot/livecd-initramfs.img" + %(target.build_dir,), + "%s/out/ppc/ppc32/initrd.img" %(target.build_dir,)) + os.unlink("%s/install_root/boot/livecd-initramfs.img" + %(target.build_dir,)) + + os.makedirs(target.build_dir + "/out/ppc/ppc64") + # FIXME: Need 64-bit kernel and initrd + + cfg32 = """ +init-message = "Welcome to the Fedora %(label)s LiveCD" +timeout=6000 + +""" %{"label": target.fs_label} + + stanzas = [("linux", "Run from image", ""), + ("runfromram", "Run from RAM - requires 1 GiB+", "live_ram")] + if os.path.exists("%s/install_root/usr/lib/anaconda-runtime/checkisomd5" %(target.build_dir,)): + stanzas.append( ("check", "Verify and run from image", "check") ) + + for (short, long, extra) in stanzas: + cfg32 += """ + +image=/ppc/ppc32/vmlinuz + label=%(short)s + initrd=/ppc/ppc32/initrd.img + read-only + append="ro quiet root=CDLABEL=%(label)s rootfstype=iso9660 %(extra)s" +""" %{"label": target.fs_label, + "short": short, "long": long, "extra": extra} + + cfgf = open("%s/out/ppc/ppc32/yaboot.conf" %(target.build_dir,), "w") + cfgf.write(cfg32) + cfgf.close() + os.makedirs(target.build_dir + "/out/etc") + cfgf = open("%s/out/etc/yaboot.conf" %(target.build_dir,), "w") + cfgf.write(cfg32) + cfgf.close() + + # FIXME. Obviously + cfg64 = """ +init-message = "Sorry, this LiveCD only supports 32-bit hardware" +""" + cfgf = open("%s/out/ppc/ppc64/yaboot.conf" %(target.build_dir,), "w") + cfgf.write(cfg64) + cfgf.close() + + # TODO: enable external entitity to partipate in adding boot entries + # build 'netboot' images with kernel+initrd, like mk-images.ppc + +class InstallationArchX86: + def __init__(self): + self.bootldr_package = ("syslinux",) + + def createIso(self, target): + """write out the live CD ISO""" + subprocess.call(["/usr/bin/mkisofs", "-o", "%s.iso" %(target.fs_label,), + "-b", "isolinux/isolinux.bin", + "-c", "isolinux/boot.cat", + "-no-emul-boot", "-boot-load-size", "4", + "-boot-info-table", "-J", "-r", "-hide-rr-moved", + "-V", "%s" %(target.fs_label,), "%s/out" %(target.build_dir)]) + + def configureBootloader(self, target): + """configure the boot loader""" + + # set up boot loader + # + # TODO: + # - fix for archs not using grub + # - fix for non-i386 + # - error handling + # + os.makedirs(target.build_dir + "/out/isolinux") + + shutil.copyfile("%s/install_root/boot/vmlinuz-%s" + %(target.build_dir, target.get_kernel_version()), + "%s/out/isolinux/vmlinuz" %(target.build_dir,)) + + shutil.copyfile("%s/install_root/boot/livecd-initramfs.img" + %(target.build_dir,), + "%s/out/isolinux/initrd.img" %(target.build_dir,)) + os.unlink("%s/install_root/boot/livecd-initramfs.img" + %(target.build_dir,)) + + for p in ["isolinux.bin", "vesamenu.c32"]: + path = "%s/install_root/usr/lib/syslinux/%s" % (target.build_dir, p) + + if not os.path.isfile(path): + raise InstallationError("syslinux not installed : %s not found" % path) + + shutil.copy(path, "%s/out/isolinux/%s" % (target.build_dir, p)) + + if os.path.exists("%s/install_root/usr/lib/anaconda-runtime/syslinux-vesa-splash.jpg" %(target.build_dir,)): + shutil.copy("%s/install_root/usr/lib/anaconda-runtime/syslinux-vesa-splash.jpg" %(target.build_dir,), + "%s/out/isolinux/splash.jpg" %(target.build_dir,)) + have_background = "menu background splash.jpg" + else: + have_background = "" + + cfg = """ +default vesamenu.c32 +timeout 600 + +%(background)s +menu title Welcome to %(label)s! +menu color border 0 #ffffffff #00000000 +menu color sel 0 #ffffffff #ff000000 +menu color title 0 #ffffffff #00000000 +menu color tabmsg 0 #ffffffff #00000000 +menu color unsel 0 #ffffffff #00000000 +menu color hotsel 0 #ff000000 #ffffffff +menu color hotkey 0 #ffffffff #ff000000 +""" %{"label": target.fs_label, "background" : have_background} + + stanzas = [("linux", "Run from image", ""), + ("runfromram", "Run from RAM - requires 1 GiB+", "live_ram")] + if os.path.exists("%s/install_root/usr/lib/anaconda-runtime/checkisomd5" %(target.build_dir,)): + stanzas.append( ("check", "Verify and run from image", "check") ) + + for (short, long, extra) in stanzas: + cfg += """label %(short)s + menu label %(long)s + kernel vmlinuz + append initrd=initrd.img ro quiet root=CDLABEL=%(label)s rootfstype=iso9660 liveimg %(extra)s +""" %{"label": target.fs_label, "background" : have_background, + "short": short, "long": long, "extra": extra} + + cfgf = open("%s/out/isolinux/isolinux.cfg" %(target.build_dir,), "w") + cfgf.write(cfg) + cfgf.close() + + # TODO: enable external entitity to partipate in adding boot entries + + class InstallationTarget: def __init__(self, repos, packages, epackages, groups, fs_label, skip_compression, skip_prelink): self.ayum = None @@ -293,6 +467,14 @@ class InstallationTarget: self.bindmounts = [] self.ksparser = None + myarch = rhpl.getArch() + if myarch == "i386" or myarch == "x86_64": + self.arch = InstallationArchX86() + elif myarch == "ppc": + self.arch = InstallationArchPPC() + else: + raise InstallationError("Do not know how to build LiveCD for arch '%s'" % (myarch,)) + def parse(self, kscfg): ksversion = pykickstart.version.makeVersion() self.ksparser = pykickstart.parser.KickstartParser(ksversion) @@ -377,7 +559,6 @@ class InstallationTarget: except OSError, (err, msg): raise InstallationError("Failed create build directory in /var/tmp: %s" % msg) - os.makedirs(self.build_dir + "/out/isolinux") os.makedirs(self.build_dir + "/out/sysroot") os.makedirs(self.build_dir + "/data/sysroot") os.makedirs(self.build_dir + "/install_root") @@ -748,12 +929,12 @@ class InstallationTarget: return kernels[0] - def createInitramfs(self): + def createInitramfs(self, mayflower_path): # Create initramfs - if not os.path.isfile("/usr/lib/livecd-creator/mayflower"): + if not os.path.isfile(mayflower_path): raise InstallationError("livecd-creator not correctly installed : "+ - "/usr/lib/livecd-creator/mayflower not found") - shutil.copy("/usr/lib/livecd-creator/mayflower", + mayflower_path+" not found") + shutil.copy(mayflower_path, "%s/install_root/sbin/mayflower" %(self.build_dir,)) # modules needed for booting (this is butt ugly and we need to retrieve this from elsewhere, e.g. the kernel) mayflowerconf = open(self.build_dir + "/install_root/etc/mayflower.conf", "w") @@ -761,7 +942,7 @@ class InstallationTarget: mayflowerconf.write('MODULES+="sata_mv sata_qstor sata_sis sata_uli "\n') mayflowerconf.write('MODULES+="sata_nv sata_sil24 sata_svw sata_via "\n') mayflowerconf.write('MODULES+="sata_promise sata_sil sata_sx4 sata_vsc "\n') - mayflowerconf.write('MODULES+="ata_generic pata_ali pata_amd pata_artop pata_atiixp pata_cmd64x pata_cs5520 pata_cs5530 pata_cs5535 pata_cypress pata_efar pata_hpt366 pata_hpt37x pata_hpt3x2n pata_hpt3x3 pata_isapnp pata_it821x pata_jmicron pata_marvell pata_mpiix pata_netcell pata_ns87410 pata_oldpiix pata_optidma pata_opti pata_pcmcia pata_pdc2027x pata_pdc202xx_old pata_qdi pata_serverworks pata_sil680 pata_sis pata_sl82c105 pata_triflex pata_via pdc_adma "\n') + mayflowerconf.write('MODULES+="ata_generic pata_ali pata_amd pata_artop pata_atiixp pata_cmd64x pata_cs5520 pata_cs5530 pata_cs5535 pata_cypress pata_efar pata_hpt366 pata_hpt37x pata_hpt3x2n pata_hpt3x3 pata_isapnp pata_it821x pata_jmicron pata_marvell pata_mpiix pata_netcell pata_ns87410 pata_oldpiix pata_optidma pata_opti pata_pcmcia pata_pdc2027x pata_pdc202xx_old pata_qdi pata_serverworks pata_sil680 pata_sis pata_sl82c105 pata_triflex pata_via pdc_adma pata_mpc52xx "\n') mayflowerconf.close() subprocess.call(["/sbin/mayflower", "-f", "/boot/livecd-initramfs.img", @@ -789,76 +970,8 @@ class InstallationTarget: def launchShell(self): subprocess.call(["/bin/bash"], preexec_fn=self.run_in_root) - def configureBootloader(self): - """configure the boot loader""" - - # set up boot loader - # - # TODO: - # - fix for archs not using grub - # - fix for non-i386 - # - error handling - # - shutil.copyfile("%s/install_root/boot/vmlinuz-%s" - %(self.build_dir, self.get_kernel_version()), - "%s/out/isolinux/vmlinuz" %(self.build_dir,)) - - shutil.copyfile("%s/install_root/boot/livecd-initramfs.img" - %(self.build_dir,), - "%s/out/isolinux/initrd.img" %(self.build_dir,)) - os.unlink("%s/install_root/boot/livecd-initramfs.img" - %(self.build_dir,)) - - for p in ["isolinux.bin", "vesamenu.c32"]: - path = "%s/install_root/usr/lib/syslinux/%s" % (self.build_dir, p) - - if not os.path.isfile(path): - raise InstallationError("syslinux not installed : %s not found" % path) - - shutil.copy(path, "%s/out/isolinux/%s" % (self.build_dir, p)) - - if os.path.exists("%s/install_root/usr/lib/anaconda-runtime/syslinux-vesa-splash.jpg" %(self.build_dir,)): - shutil.copy("%s/install_root/usr/lib/anaconda-runtime/syslinux-vesa-splash.jpg" %(self.build_dir,), - "%s/out/isolinux/splash.jpg" %(self.build_dir,)) - have_background = "menu background splash.jpg" - else: - have_background = "" - - cfg = """ -default vesamenu.c32 -timeout 600 - -%(background)s -menu title Welcome to %(label)s! -menu color border 0 #ffffffff #00000000 -menu color sel 0 #ffffffff #ff000000 -menu color title 0 #ffffffff #00000000 -menu color tabmsg 0 #ffffffff #00000000 -menu color unsel 0 #ffffffff #00000000 -menu color hotsel 0 #ff000000 #ffffffff -menu color hotkey 0 #ffffffff #ff000000 -""" %{"label": self.fs_label, "background" : have_background} - - stanzas = [("linux", "Run from image", ""), - ("runfromram", "Run from RAM - requires 1 GB+", "live_ram")] - if os.path.exists("%s/install_root/usr/lib/anaconda-runtime/checkisomd5" %(self.build_dir,)): - stanzas.append( ("check", "Verify and run from image", "check") ) - - for (short, long, extra) in stanzas: - cfg += """label %(short)s - menu label %(long)s - kernel vmlinuz - append initrd=initrd.img ro quiet root=CDLABEL=%(label)s rootfstype=iso9660 liveimg %(extra)s -""" %{"label": self.fs_label, "background" : have_background, - "short": short, "long": long, "extra": extra} - - cfgf = open("%s/out/isolinux/isolinux.cfg" %(self.build_dir,), "w") - cfgf.write(cfg) - cfgf.close() - # TODO: enable external entitity to partipate in adding boot entries - - def install(self): + def install(self, mayflower_path): for (name, url) in self.repos: self.ayum.addRepository(name, url) @@ -868,24 +981,8 @@ menu color hotkey 0 #ffffffff #ff000000 self.relabelSystem() if not self.skip_prelink: self.prelinkSystem() - self.createInitramfs() - self.configureBootloader() - - def createIso(self): - """write out the live CD ISO""" - subprocess.call(["/usr/bin/mkisofs", "-o", "%s.iso" %(self.fs_label,), - "-b", "isolinux/isolinux.bin", - "-c", "isolinux/boot.cat", - "-no-emul-boot", "-boot-load-size", "4", - "-boot-info-table", "-J", "-r", "-hide-rr-moved", - "-V", "%s" %(self.fs_label,), "%s/out" %(self.build_dir)]) - - # implant an isomd5sum - if os.path.exists("/usr/lib/anaconda-runtime/implantisomd5"): - subprocess.call(["/usr/lib/anaconda-runtime/implantisomd5", - "%s.iso" %(self.fs_label,)]) - else: - print >> sys.stderr, "anaconda-runtime not installed; not setting up mediacheck" + self.createInitramfs(mayflower_path) + self.arch.configureBootloader(self) def createSquashFS(self): """create compressed squashfs file system""" @@ -901,7 +998,14 @@ menu color hotkey 0 #ffffffff #ff000000 def package(self): self.createSquashFS() - self.createIso() + self.arch.createIso(self) + # implant an isomd5sum + if os.path.exists("/usr/lib/anaconda-runtime/implantisomd5"): + subprocess.call(["/usr/lib/anaconda-runtime/implantisomd5", + "%s.iso" %(self.fs_label,)]) + else: + print >> sys.stderr, "anaconda-runtime not installed; not setting up mediacheck" + def usage(out): print >> out, """ @@ -911,9 +1015,9 @@ usage: livecd-creator [--help] [--package=] [--package= ...] [--exclude-package=] [--exclude-package= ...] [--base-on=] - [--fslabel=