From bernardino.lopez at gmail.com Tue Jul 1 14:54:05 2008 From: bernardino.lopez at gmail.com (Dino Lopez) Date: Tue, 1 Jul 2008 09:54:05 -0500 Subject: [Fedora-livecd-list] Fedora 9 Does not recognize SATA HDD in DELL Vostro 1510 Message-ID: <4209097b0807010754p4c50ec63k478fe528b7e83951@mail.gmail.com> Fedora 9 Does not recognize SATA HDD in DELL Vostro 1510 I also try to use the install DVD and for some reason the SATA HDD does not seems to be recognized. Try to research and did not found any settings in the Bios to change the HDD to make it work. Din00z. -------------- next part -------------- An HTML attachment was scrubbed... URL: From princerajhot at yahoo.co.in Wed Jul 2 05:45:48 2008 From: princerajhot at yahoo.co.in (prince raj) Date: Wed, 2 Jul 2008 11:15:48 +0530 (IST) Subject: [Fedora-livecd-list] (no subject) Message-ID: <530710.53968.qm@web94202.mail.in2.yahoo.com> Can I?have latest fedora cd as i have more interest in fedora than ubuntu ? From Chandigarh to Chennai - find friends all over India. Go to http://in.promos.yahoo.com/groups/citygroups/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From sundaram at fedoraproject.org Wed Jul 2 05:51:29 2008 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Wed, 02 Jul 2008 11:21:29 +0530 Subject: [Fedora-livecd-list] (no subject) In-Reply-To: <530710.53968.qm@web94202.mail.in2.yahoo.com> References: <530710.53968.qm@web94202.mail.in2.yahoo.com> Message-ID: <486B1761.2050608@fedoraproject.org> prince raj wrote: > Can I have latest fedora cd as i have more interest in fedora than ubuntu This is the wrong list really but you can download it from http://fedoraproject.org/en/get-fedora Rahul From sgodsell at hotmail.com Thu Jul 3 18:53:26 2008 From: sgodsell at hotmail.com (Sean Godsell) Date: Thu, 3 Jul 2008 14:53:26 -0400 Subject: [Fedora-livecd-list] Modifying the original Fedora Live CD Message-ID: Hello to everyone who is interested, How to replace the kernel on a Fedora livecd By Sean Godsell The reason I wrote this was I wanted to have a live cd with more stuff on it. I wanted more wifi, skype, and Adobe flash as well as shockwave, wine (for the games). So the first task on the list was a kernel that supported all the webcam drivers, ntfs, ndiswrapper, madwifi, and squashfs with lzma support. So I decided to go with the latest stable kernel at this time. Which is kernel 2.6.25.9 from kernel.org . I could have chosen the kernel source from fedora and built it the rpm way, but I started back in the days with slackware. So I am use to building the kernel the original way. Also this way of building works with other distros as well. And I get to control the patches that I want to apply. (I know you can edit the kernel.spec file, but I will leave that up to someone else ;-) ). I could also go into every detail of how to manipulate a kickstart file, and how to use livecd-creator, but I didn't, so stop reading then ;-). Once you have obtained the kernel source code, extracted, modified and built and tested it to your needs. Then its time to roll your own fedora livecd. To start with I obtained the original Fedora-9-i686-Live.iso file and saved it to /home/images (For the duration of this document I will be using a folder /home/images). Before we do anything else I am going to create a few mount points, using type in the following commands: mkdir /mnt/iso; mkdir /mnt/squashfs; mkdir /mnt/ext3fs; mkdir /mnt/next3fs Now we need to mount the Fedora-9-i686-Live.iso file. Type in the following command: mount -o loop /home/images/Fedora-9-i686-Live.iso /mnt/iso The next step I created a directory to put all the file into: mkdir /home/images/isoimage Next we have to copy all the files to the /home/images/isoimage directory with: cp -dpR /mnt/iso/* /home/images/isoimage So now we have extracted the fedora iso image to a directory. Next I created a directory called initrd mkdir /home/images/initrd Then I extracted the initrd0.img file using the following commands: cd /home/images/initrd cat /home/images/isoimage/isolinux/initrd0.img | gunzip - | cpio -i You should have an extracted initrd image now inside the /home/imgaes/initrd folder. Okay now comes the fun stuff. Copy the following lines to a file called copymodules in the /home/images folder. Start copying everything in between the equals symbols (======) ================== #!/bin/bash # Copy files from a modules.dep to a directory , by Sean Godsell # $1 - the modules.dep file to use # $2 - the directory of where to get the kernel modules to copy from # $3 - the directory to copy the modules into mods=`cat $1` for i in $mods; do name=`echo $i|awk '{print $1}'|awk -F / '{print $(NF)}'|awk -F : '{print $1}'` find $2 -iname $name -exec cp -dpf {} $3 \; done =================== Okay once the copymodules file is created. Next we have to create a directory for our new with the exact same name of the kernel you are going to copy from. In my case I am using 2.6.25.9. So I will create a directory in /home/images/initrd/lib/modules using the following command: mkdir /home/images/initrd/lib/modules/2.6.25.9 Next I want to use fedora livecds module files so I copied from the original /home/images/initrd/lib/modules/2.6.25-14.fc9.i686/ using the following command: cp /home/images/initrd/lib/modules/2.6.25-14.fc9.i686/module* /home/images/initrd/lib/modules/2.6.25.9/ Next I modified modules.dep and added the squashfs + lzma modules. To do this I looked at my installed 2.6.25.9 kernel from /lib/modules/2.6.25.9/modules.dep and replaced the one line with squashfs.ko: in /home/images/initrd/lib/modules/2.6.25.9/modules.dep with the following 3 lines: /lib/modules/2.6.25.9/extras/sqlzma.ko: /lib/modules/2.6.25.9/extras/unlzma.ko /lib/modules/2.6.25.9/extras/unlzma.ko: /lib/modules/2.6.25.9/extras/squashfs.ko: /lib/modules/2.6.25.9/extras/sqlzma.ko /lib/modules/2.6.25.9/extras/unlzma.ko I also edited out ALL of the /extras so you will end up with /lib/modules/2.6.25.9/unlzma.ko: . Next I did a global replace for 2.6.25-14.fc9.i686 to 2.6.25.9 . Now save the changes back to /home/images/initrd/lib/modules/2.6.25.9/modules.dep. We still don't have any modules in the folder, but that is about to change. Type in the following command: source /home/images/copymodules /home/images/initrd/lib/modules/2.6.25.9/modules.dep /lib/modules/2.6.25.9/ /home/images/initrd/lib/modules/2.6.25.9/ This should populate the /home/images/initrd/lib/modules/2.6.25.9 with all the necessary modules, including the squashfs and the lzma modules. Next we need to delete the old 2.6.25-14.fc9.i686 folder with the following command: rm -fr /home/images/initrd/lib/modules/2.6.25-14.fc9.i686 Once that is complete it is time to replace the original initrd0.img file. Type in the following commands: cd /home/images/initrd find . | cpio -H newc -o | gzip -9> /home/images/isoimage/isolinux/initrd0.img We now have replace the original initrd0.img. Next we need to replace the original kernel image with the following commnad: cp /boot/bzImage-2.6.25.9 /home/images/isoimage/isolinux/vmlinuz0 So now if we were to burn an iso image at this point it would boot up with the kernel 2.6.25.9 and mount a normal squashfs or a squashfs with lzma. But the rest of the livecd would not work. We need to replace the existing /lib/modules/2.6.25-14.fc9.i686 directory with the /lib/modules/2.6.25.9. These files reside inside the /home/images/isoimage/LiveOS/squashfs.img file. Enter in the following commands: mkdir /home/images/squashfs_image/ modprobe squashfs mount -o loop -t squashfs /home/images/isoimage/LiveOS/squashfs.img /mnt/squashfs cp -dpR /mnt/squashfs/* /home/images/squashfs_image/ umount /mnt/squashfs mount -o loop /home/images/squashfs_image/LiveOS/ext3fs.img /mnt/ext3fs rm -fr /mnt/ext3fs/lib/modules/2.6.25-14.fc9.i686 cp -dpR /lib/modules/2.6.25.9 /mnt/ext3fs/lib/modules/ Now you can put what ever you want on the ext3fs image. I put skype, wine packages and my wine enviroment with a windows version of firefox. Now some of you are probably thinking there is a firefox already on the fedora live cd. That is true. I already know this, but the only way that I know of getting shockwave to work is through wine or a VM with windows. The last option is just a little too big to get on a livecd image. So I opted to installing wine and my .wine environment. I also updated the firefox beta that was on the live image to the released version (Not to mention I updated a few more things). At this point you are ready to do 1 of 2 things. 1) you can re squash the ext3fs.img. 2) create a clean ext3fs.img and copy everything from /mnt/ext3fs/ to the clean ext3fs.img. You are probably wondering why would you copy everything from one ext3fs.img to another ext3fs.img, well the answer is quite simple. If you delete a bunch of things off the ext3fs.img, and then decide to squash it. You might get roughly the same size image after wards, even if you remove a lot of files. With ext3 file system it doesn't zero out all the files. It only removes entries, so the data is still there. So when squashing the ext3 image, if the data is still there, then it has to compress it. In other words if you transfer everything over from one image to a brand new clean image then when it comes time to compress the ext3 image, the end result can be a smaller image. If you don't care and want to just squash the ext3fs.img, then skip to the squashfs section. Okay to copy everything type in the following commands: dd if=/dev/zero of=/home/images/ext3fs.img bs=1MB count=4096 mkfs.ext3 /home/images/ext3fs.img mount -o loop /home/images/ext3fs.img /mnt/next3fs cp -dpR /mnt/ext3fs/* /mnt/next3fs/ Now to use the squashfs file system. First we most umount the ext3 file system. So type in: umount /mnt/next3fs umount /mnt/ext3fs Next replace the new image in squashfs_image/LiveOS cp -f /home/images/ext3fs.img /home/images/squashfs_image/LiveOS/ Then to compress type in (If you replaced the original command, then just remove the .lzma): mksquashfs.lzma squashfs_image/ /home/images/isoimage/LiveOS/squashfs.img This takes some time. So have a drink, hey why not have a couple of drinks ;-) Okay once that is done the final step is create an iso image with the following command: mkisofs -J -r -hide-rr-moved -hide-joliet-trans-tbl -V Fedora-9-Live-i686 -o Seans.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-info-table -boot-load-size 4 isoimage With the exact same fedora image. I was able to save almost 110 megabytes. Wow, what a savings. Not to mention saving on download time. I don't know why fedora didn't take the time to use squashfs+lzma, but it is worth it. I hope they put it in the next release. _________________________________________________________________ Express yourself with free Messenger emoticons. Get them today! http://www.freemessengeremoticons.ca/?icid=EMENCA122 From ivazqueznet at gmail.com Thu Jul 3 19:01:12 2008 From: ivazqueznet at gmail.com (Ignacio Vazquez-Abrams) Date: Thu, 03 Jul 2008 15:01:12 -0400 Subject: [Fedora-livecd-list] [PATCH] Allow the USB device to be a symlink to a device node Message-ID: <1215111672.3508.59.camel@ignacio.lan> The attached patch allows the USB device passed to livecd-iso-to-disk to be specified as a symlink, e.g., /dev/disk/by-*/*. -- Ignacio Vazquez-Abrams PLEASE don't CC me; I'm already subscribed -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Allow-the-USB-device-to-be-a-symlink-to-a-device-nod.patch Type: application/mbox Size: 665 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From sgodsell at hotmail.com Thu Jul 3 20:09:15 2008 From: sgodsell at hotmail.com (Sean Godsell) Date: Thu, 3 Jul 2008 16:09:15 -0400 Subject: [Fedora-livecd-list] Creating Squashfs + lzma kernel modules Message-ID: Hello to anyone who is interested, Building a kernel with squashfs with lzma support (July 2008) By Sean Godsell The first task on the list was a kernel that supported squashfs with lzma support. So I decided to go with the latest stable kernel at this time. Which is kernel 2.6.25.9 from kernel.org . Now each linux distribution has its way of building kernels. So I opted to building the kernel the generic way. This will also work for most distributions. And I get to control the patches that I want to apply. Once you have obtained the kernel source code, and extracted to a directory of your choice (I use /usr/src path). To extact I used the following command tar -jxf linux-2.6.25.9.tar.bz2 Next I downloaded a bunch of files from http://www.squashfs-lzma.org/ . Download all the files in the section 'Download (all needed)', except the last one which states linux kernel 2.6.24 or higher. For that one I already downloaded the kernel 2.6.25.9 from http://www.kernel.org . Also download http://sourceforge.net/tracker/download.php?group_id=63835&atid=505341&file_id=274755&aid=1912192 to fix squashfs for 2.6.25 kernels. Okay now for the fun stuff making the kernel. I always like to comple the stock kernel and get it running first, so I just take current kernel config file from the one I am running and use that as my starting point. On some systems you can find the config in the /boot directory. Some kernels might have enabled the config to be in /proc/config.gz. I am going to use the /boot/config-xxxxxx files. On my fedora system here I am going to copy one of the config files from /boot. In my case specifically /boot/config-2.6.25.6-55.fc9.i686 and copy it to the kernel source directory and rename it to .config . cp /boot/config-2.6.25.6-55.fc9.i686 /usr/src/linux-2.6.25.9/.config At this point I added some other patches to the kernel that are not related to squashfs (like ndiswrapper which requests an 8k stack size instead). I also added a few other drivers like r5u870, gspca, linux-uvc, and madwifi. None of which effect squashfs. Then I do a make menuconfig to add or remove items from the kernel. Once you made the changes in make menuconfig . The next step is to build the kernel, type in make -j 2 bzImage Notice the -j 2 is used for running 2 jobs at the same time. It helps speed up the build if you have a dual core system. If you have a quad system then change the 2 to 4. After type in: make -j 2 modules then make -j 2 modules_install If you don't want to wait for each step then type in the following: make bzImage modules modules_install Well some of you might want a leaner kernel with using the option -g0. This will definitely take some time to build the kernel and the modules. Next I built the other drivers (r5u870, gspca, uvc, ...) If you get errors then you must have changed or did something wrong. But if everything goes right then you should end up with a directory like '/lib/modules/2.6.25.9' with all the modules. Next for my architecture I copy the linux-2.6.25.9/arch/x86/boot/bzImage to /boot directory. cp /usr/src/linux-2.6.25.9/arch/x86/boot/bzImage /boot/bzImage-2.6.25.9 The next step is to create an initrd to go with our new kernel. I use the following command to create my initrd. mkinitrd --with=ehci_hcd --with=ohci_hcd --with=uhci_hcd --with=mbcache --with=jbd --with=ext3 --with=dm_mod --with=dm_mirror --with=dm_zero --with=dm_snapshot --with=crypto_blkcipher --with=dm_crypt --with=aes_generic --with=aes_i586 --with=cbc --with=sha256_generic --with=scsi_mod --with=sd_mod --with=libata --with=ahci --with=sg /boot/initrd-2.6.25.9.img 2.6.25.9 This will create a file called initrd-2.6.25.9.img in the /boot folder. If you don't know what modules to put into the initrd. Then what I do is look at the current system and see what it has currently loaded. Use the command lsmod. The last entries in the list are the first one's that get loaded at boot time. So I just include those ones (if you don't have and encrypted filesystem then you won't need crypto_blkcipher, as well as a few others). Now the last step before we test our kernel is to update the boot loader. In this case I update my /boot/grub/grub file with the following lines: title MyBuild (2.6.25.9) root (hd0,1) kernel /bzImage-2.6.25.9 ro root=/dev/VolGroup01/LogVol00 rhgb initrd /initrd-2.6.25.9.img If you don't want to see a lot of information being displayed on bootup, then add the word quiet to the end of the kernel line. Next reboot. reboot If it boots up, you are in luck ;-) Now to move on with adding the squashfs + lzma support in the kernel. Adding Squashfs + lzma support Okay the first step is to take the squashfs files that were download and put them in a directory. I put mine in /usr/src/squashfs , (I am going to assume that you are going to be in the directory /usr/src/squashfs) so I have 5 files in this directory: squashfs3.3.tar.gz lzma457.tar.bz2 sqlzma3.3-457-2.tar.bz2 squashfs-3.3-cvsfix.tar.gz squashfs-patch-2.6.25 The first one I expaned was squashfs3.3.tar.gz using the following command: tar -zxf squashfs3.3.tar.gz which will create a directory called squashfs3.3 inside the /usr/src/squashfs folder. Next I created a directory called lzma457 inside /usr/src/squashfs. Then I extracted the files from lzma457.tar.bz2 into the newly created folder called lzma457 using the following command: tar -C lzma457 -jxf lzma457.tar.bz2 Next I created a directory called patches inside the /usr/src/squashfs folder. Then I extracted the file squashfs-3.3-cvsfix.tar.gz into the patches directory using the following command: tar -C patches -zxf squashfs-3.3-cvsfix.tar.gz The last file to extract, I just extracted to /usr/src/squashfs, using the following command: tar -jxf sqlzma3.3-457-2.tar.bz2 Next I went inside the linux kernel (2.6.25.9). cd /usr/src/linux-2.6.25.9 (for fedora do) cd /usr/src/kernels/2.6.25.9-76.fc9.i686 and added the squashfs patch using the following command: patch -p1 < /usr/src/squashfs/squashfs3.3/kernel-patches/linux-2.6.24/squashfs3.3-patch then patch -p1 < /usr/src/squashfs/patches/typo_mkflags_k.patch then patch -p1 < /usr/src/squashfs/sqlzma2k-3.3.patch then patch -p1 < /usr/src/squashfs/squashfs-patch-2.6.25 The last patch you will get 2 fails but don't worry about them. If you are really concerned with them then you can look at the reject file 'fs/squashfs/inode.c.rej'. You will see that it is only two trivial things a printk and a module description. After do a make menuconfig or edit the .config yourself and make sure CONFIG_SQUASHFS=m . The option to set under menuconfig is under file systems->Miscellaneous filesystems->SquashFS 3.3 and set to M (for module) Next go to the /usr/src/squashfs/lzma457 directory and type in the following: patch -p1 < ../sqlzma1-449.patch Now go back one directory to /usr/src/squashfs and edit the Makefile and change the line LzmaVer = near the top of the file to read LzmaVer = lzma457 Then edit the line Kver = to Kver = linux-2.6.25.9 (fedora change to) Kver = 2.6.25.9-76.fc9.i686 Now save this file, and at the command prompt type in ln -s /usr/src/linux-2.6.25.9 squashfs3.3/kernel-patches/ (for fedora do) ln -s /usr/src/kernels/`uname -r` squashfs3.3/kernel-patches/ then patch -p0 < patches/typo_mkflags_u.patch then patch -p0 < sqlzma2u-3.3.patch then patch -p0 < patches/mksquashfs_bug_fixes.patch then patch -p0 < patches/code_cleanup.patch Don't worry about the mksquashfs_bug_fixes.patch reject. It is only a printf. And now to build the new mksquashfs command as well as the 3 new kernel modules. Type in the following: make If everything went well, then you should be able to copy the following files: (none fedora) mkdir /lib/modules/`uname -r`/extra cp /usr/src/linux-2.6.25.9/fs/squashfs/*.ko /lib/modules/`uname -r`/extra/ cp /usr/src/squashfs/lzma457/C/Compress/Lzma/kmod/*.ko /lib/modules/`uname -r`/extra/ cp /usr/src/squashfs/squashfs3.3/squashfs-tools/mksquashfs /sbin/mksquashfs.lzma (fedora) cp /usr/src/kernels/`uname -r`/fs/squashfs/*.ko /lib/modules/`uname -r`/extra/ cp /usr/src/squashfs/lzma457/C/Compress/Lzma/kmod/*.ko /lib/modules/`uname -r`/extra/ cp /usr/src/squashfs/squashfs3.3/squashfs-tools/mksquashfs /sbin/mksquashfs.lzma if you want to replace the existing command mksquashfs then cp /usr/src/squashfs/squashfs3.3/squashfs-tools/mksquashfs /sbin/ Next we have to fix up the kernel dependencies with the following command depmod -ae You should get no messages if everything went well. Now we can load the modules modprobe squashfs and finally if you do a lsmod | head then you should see unlzma, sqlzma, and squashfs modules. If you want to verify if the filesystem is supported then type in cat /proc/filesystems |grep squ You should see squashfs Remember always Good Luck, and have fun ;-) Sean _________________________________________________________________ Are you ready for Windows Live Messenger Beta 8.5 ? Get the latest for free today! http://entertainment.sympatico.msn.ca/WindowsLiveMessenger From rdieter at math.unl.edu Fri Jul 4 00:05:56 2008 From: rdieter at math.unl.edu (Rex Dieter) Date: Thu, 03 Jul 2008 19:05:56 -0500 Subject: [Fedora-livecd-list] Re: Modifying the original Fedora Live CD References: Message-ID: Sean Godsell wrote: > With the exact same fedora image. I was able to save almost 110 > megabytes. Wow, what a savings. no doubt. > I don't know why fedora didn't > take the time to use squashfs+lzma, but it is worth it. I hope they put > it in the next release. Most likely because it doesn't appear to be included in the upstream kernel. When/if it is, this is a no-brainer. -- Rex From sgodsell at hotmail.com Sat Jul 5 17:07:08 2008 From: sgodsell at hotmail.com (Sean Godsell) Date: Sat, 5 Jul 2008 13:07:08 -0400 Subject: [Fedora-livecd-list] Proper patch for squashfs+lzma support Message-ID: Hello everyone, Okay the last patch I was told it was just a hack, so I decided to make it much easier for everyone ;-) Now the first step is to take one of the patches that I supplied in this email. For example I am going to use squashlzma-2.6.25.9-76.fc9.patch and copy it to my rpm build environment. Next I change directory to my rpm build environment, so in my case: cd $HOME/rpmbuild (for users using the default) cd /usr/src/redhat Next download and install the kernel source. For this example I downloaded kernel-2.6.25.9-76.fc9.src.rpm and to install it use the following command: rpm -ivh kernel-2.6.25.9-76.fc9.src.rpm Next I apply the patch using the following command: patch -p0 < squashlzma-2.6.25.9-76.fc9.patch Now the last step naturally takes the longest, but it is the build step. In my case I only want to build the binary packages with a target of i686, so I typed in the following: rpmbuild -bb --target=i686 SPECS/kernel.spec Wait for a long while, and wahla, you are the proud parents of a new baby kernel package with squash+lzma support. I supplied the linux-2.6-squashfs-lzma.patch as well if you want to try and patch any other fedora kernel. Remember always Good Luck, and have fun ;-) Sean _________________________________________________________________ If you like crossword puzzles, then you'll love Flexicon, a game which combines four overlapping crossword puzzles into one! http://g.msn.ca/ca55/208 -------------- next part -------------- A non-text attachment was scrubbed... Name: squashlzma-2.6.25.9-76.fc9.patch Type: application/octet-stream Size: 53199 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: squashlzma-2.6.25-14.fc9.patch Type: application/octet-stream Size: 53149 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: linux-2.6-squashfs-lzma.patch Type: application/octet-stream Size: 49904 bytes Desc: not available URL: From katzj at redhat.com Mon Jul 7 00:24:14 2008 From: katzj at redhat.com (Jeremy Katz) Date: Sun, 06 Jul 2008 20:24:14 -0400 Subject: [Fedora-livecd-list] Re: Modifying the original Fedora Live CD In-Reply-To: References: Message-ID: <1215390254.23460.14.camel@aglarond.local> On Thu, 2008-07-03 at 19:05 -0500, Rex Dieter wrote: > Sean Godsell wrote: > > I don't know why fedora didn't > > take the time to use squashfs+lzma, but it is worth it. I hope they put > > it in the next release. > > Most likely because it doesn't appear to be included in the upstream kernel. When/if it is, > this is a no-brainer. Or even included by the upstream squashfs maintainer[1] Jeremy [1] squashfs already isn't upstream. layering more patches of non-upstreamed-ness on top is just going to make the lives of the kernel maintainers *more* painful. From katzj at fedoraproject.org Mon Jul 7 00:30:13 2008 From: katzj at fedoraproject.org (Jeremy Katz) Date: Mon, 7 Jul 2008 00:30:13 +0000 (UTC) Subject: [Fedora-livecd-list] 2 commits - tools/livecd-creator tools/livecd-iso-to-disk.sh Message-ID: <20080707003013.B02D912002F@lists.fedorahosted.org> tools/livecd-creator | 1 - tools/livecd-iso-to-disk.sh | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-) New commits: commit d1107693028ffc328e7c9c39c3e00623f61d81f9 Author: Ignacio Vazquez-Abrams Date: Wed Jul 2 18:13:34 2008 -0400 Allow the USB device to be a symlink to a device node diff --git a/tools/livecd-iso-to-disk.sh b/tools/livecd-iso-to-disk.sh index 3fd2145..b1450fe 100755 --- a/tools/livecd-iso-to-disk.sh +++ b/tools/livecd-iso-to-disk.sh @@ -266,7 +266,7 @@ while [ $# -gt 2 ]; do done ISO=$(readlink -f "$1") -USBDEV=$2 +USBDEV=$(readlink -f "$2") if [ -z "$ISO" ]; then usage commit 65affd65373212415dc4f05742b9531f0e04d4f2 Author: Jeremy Katz Date: Wed Jun 25 22:10:45 2008 -0400 We don't use the time module, so don't import it diff --git a/tools/livecd-creator b/tools/livecd-creator index a3ece16..b5da7a2 100755 --- a/tools/livecd-creator +++ b/tools/livecd-creator @@ -20,7 +20,6 @@ import os import os.path import sys -import time import optparse import logging From ranceh at gmail.com Mon Jul 7 03:00:20 2008 From: ranceh at gmail.com (Rance Hall) Date: Sun, 6 Jul 2008 23:00:20 -0400 Subject: [Fedora-livecd-list] Fedora 9 KDE Live CD Message-ID: <845c0f80807062000p51455fcal620b1637ce9efe5c@mail.gmail.com> Ive got one of those VIA based chrome9 video adapters its integrated on a MSI K9VGM-V mobo. Anyway, Anaconda autodetect magic fails and locks the system up. system-config-display locks the system up. running into text mode (runlevel 3, and running startx locks up the system. the Live CD locks up the system. passing Xdriver=vesa to the install cd fixes anaconda. but I really dont want to run the netinstall I want to run the LiveCD and install from that. how do I tell the KDE LiveCD "magic" that its "magic" doesnt work, and to use VESA instead, at least till the openchrome drivers get better? Thanks From apevec at redhat.com Mon Jul 7 08:47:21 2008 From: apevec at redhat.com (Alan Pevec) Date: Mon, 07 Jul 2008 10:47:21 +0200 Subject: [Fedora-livecd-list] Re: Modifying the original Fedora Live CD In-Reply-To: <1215390254.23460.14.camel@aglarond.local> References: <1215390254.23460.14.camel@aglarond.local> Message-ID: <4871D819.5080905@redhat.com> Jeremy Katz wrote: > On Thu, 2008-07-03 at 19:05 -0500, Rex Dieter wrote: >> Sean Godsell wrote: >>> I don't know why fedora didn't >>> take the time to use squashfs+lzma, but it is worth it. I hope they put >>> it in the next release. >> Most likely because it doesn't appear to be included in the upstream kernel. When/if it is, >> this is a no-brainer. > > Or even included by the upstream squashfs maintainer[1] > > Jeremy > > [1] squashfs already isn't upstream. layering more patches of > non-upstreamed-ness on top is just going to make the lives of the kernel > maintainers *more* painful. So the issue is how can we help squashfs first and then lzma get accepted upstream. What's the history here, did it ever get submitted and then shoot down for valid reasons? From sundaram at fedoraproject.org Mon Jul 7 09:27:03 2008 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Mon, 07 Jul 2008 14:57:03 +0530 Subject: [Fedora-livecd-list] Re: Modifying the original Fedora Live CD In-Reply-To: <4871D819.5080905@redhat.com> References: <1215390254.23460.14.camel@aglarond.local> <4871D819.5080905@redhat.com> Message-ID: <4871E167.5070107@fedoraproject.org> Alan Pevec wrote: > So the issue is how can we help squashfs first and then lzma get > accepted upstream. > What's the history here, did it ever get submitted and then shoot down > for valid reasons? Around 2007 august or so, Phillip Lougher cited several reasons for not merging this patch in this list IIRC. Might want to look up the archives. Rahul From apevec at redhat.com Mon Jul 7 10:22:53 2008 From: apevec at redhat.com (Alan Pevec) Date: Mon, 07 Jul 2008 12:22:53 +0200 Subject: [Fedora-livecd-list] Re: Modifying the original Fedora Live CD In-Reply-To: <4871E167.5070107@fedoraproject.org> References: <1215390254.23460.14.camel@aglarond.local> <4871D819.5080905@redhat.com> <4871E167.5070107@fedoraproject.org> Message-ID: <4871EE7D.9030001@redhat.com> Rahul Sundaram wrote: > Around 2007 august or so, Phillip Lougher cited several reasons for not > merging this patch in this list IIRC. Might want to look up the archives. I couldn't find squashfs/lzma upstream status in the archives of this list, but markmc pointed me to http://lkml.org/lkml/2008/6/3/485 which describes the current state for squashfs. There's also recent post about lzma in kernel http://lkml.org/lkml/2008/6/26/139 From todd655495 at yahoo.com Mon Jul 7 21:06:32 2008 From: todd655495 at yahoo.com (Todd N) Date: Mon, 7 Jul 2008 14:06:32 -0700 (PDT) Subject: [Fedora-livecd-list] Modifying ISO to include per-user files In-Reply-To: <701149.26370.qm@web54005.mail.re2.yahoo.com> Message-ID: <747405.40976.qm@web54003.mail.re2.yahoo.com> Any thoughts on my prior message? ? Also, an important thing I have noticed is that when I do NOT have persistence installed on a bootable USB drive (or when I have a bootable CD), the path to the boot media is available as /mnt/live.? However, when I include persistence on a bootable USB, there is no path to the boot media, and the path /mnt/live exists but is empty.? As I am counting on pulling several files in from the boot media (but outside the squashfs file system) into my local file system,?it is important that there be consistency in where I might find these files, whether or not persistence is installed on the boot media. ? Can the /mnt/live path be enabled on a bootable USB with persistence installed? ? Also, another possibility might be to include the external files I need in the actual persistence overlay.? Can I move files into this area?? If so I will not need to do surgery on the squashfs file system. ? Thanks much for any help that can be offered. ? Todd --- On Mon, 6/30/08, Todd N wrote: From: Todd N Subject: Re: [Fedora-livecd-list] Modifying ISO to include per-user files To: fedora-livecd-list at redhat.com Date: Monday, June 30, 2008, 1:55 PM Thanks much for the info, Jeremy.? I ran the mkisofs script as you specified below (we are on an i386 architecture) and re-burned a CD from the newly-created ISO file.? On booting, it gets to the point where it says "Booting the kernel.", hangs for a few seconds, then the following appears on the screen: ? -------------------------------------- WARNING:? Cannot find root file system! -------------------------------------- ? Create symlink /dev/root and then exit this shell to continue the boot sequence. ? bash-3.2# ? Any thoughts?? Something obvious I am missing? ? Thanks, Todd --- On Mon, 6/30/08, Jeremy Katz wrote: From: Jeremy Katz Subject: Re: [Fedora-livecd-list] Modifying ISO to include per-user files To: todd655495 at yahoo.com, fedora-livecd-list at redhat.com Date: Monday, June 30, 2008, 9:51 AM On Fri, 2008-06-27 at 09:16 -0700, Todd N wrote: > After creating a LiveCD ISO image, I'd like to be able to make CDs > that are essentially identical, but have a small set of unique > per-user files. I have tried mounting the ISO, copying its contents > to a regular directory, making my changes on the Live CD file system > (not the internal squashfs file system) and recreating the ISO using > mkisofs. However, this new ISO (when burned to a CD) refuses to boot. > Is there a way I can modify the ISO image to include my per-user files on the > /mnt/live file system for each user (and have the resulting ISO be bootable), > rather than running the whole livecd-creator process each time I want a new CD? You'll have to run mkisofs with the appropriate options for making the CD bootable on your arch. On x86, that's something like 'mkisofs -b isolinux/isolinux.bin -c isolinux/isolinux.cat -no-emul-boot -boot-info-table -boot-load-size 4 ....' Alternately, you can also use the --base-on support to build derivative images 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 katzj at fedoraproject.org Mon Jul 7 21:38:52 2008 From: katzj at fedoraproject.org (Jeremy Katz) Date: Mon, 7 Jul 2008 21:38:52 +0000 (UTC) Subject: [Fedora-livecd-list] 2 commits - imgcreate/kickstart.py imgcreate/live.py Message-ID: <20080707213852.BE39212002F@lists.fedorahosted.org> imgcreate/kickstart.py | 7 +++++++ imgcreate/live.py | 4 +++- 2 files changed, 10 insertions(+), 1 deletion(-) New commits: commit 856a05d2d69dde3df25849970fa0d6c200f03b5c Author: Jeremy Katz Date: Mon Jul 7 17:36:46 2008 -0400 plymouth should imply rhgb now as well diff --git a/imgcreate/live.py b/imgcreate/live.py index bd7f3e4..0bf50f2 100644 --- a/imgcreate/live.py +++ b/imgcreate/live.py @@ -97,6 +97,8 @@ class LiveImageCreatorBase(LoopImageCreator): r = kickstart.get_kernel_args(self.ks) if os.path.exists(self._instroot + "/usr/bin/rhgb"): r += " rhgb" + if os.path.exists(self._instroot + "/usr/bin/plymouth"): + r += " rhgb" return r def _get_mkisofs_options(self, isodir): commit 32575fd38289cb6777c2e2f9fd9ccc53b0bc8d55 Author: Jeremy Katz Date: Mon Jul 7 17:30:27 2008 -0400 Listen to bootloader --append We lost support for using 'bootloader --append=foo' to add arguments to the kernel command-line at some point. Add back support for this diff --git a/imgcreate/kickstart.py b/imgcreate/kickstart.py index 39756b2..0f797b8 100644 --- a/imgcreate/kickstart.py +++ b/imgcreate/kickstart.py @@ -444,6 +444,13 @@ def get_timeout(ks, default = None): return default return int(ks.handler.bootloader.timeout) +def get_kernel_args(ks, default = "ro liveimg quiet"): + if not hasattr(ks.handler.bootloader, "appendLine"): + return default + if ks.handler.bootloader.appendLine is None: + return default + return "%s %s" %(default, ks.handler.bootloader.appendLine) + def get_default_kernel(ks, default = None): if not hasattr(ks.handler.bootloader, "default"): return default diff --git a/imgcreate/live.py b/imgcreate/live.py index 1c54cf6..bd7f3e4 100644 --- a/imgcreate/live.py +++ b/imgcreate/live.py @@ -94,7 +94,7 @@ class LiveImageCreatorBase(LoopImageCreator): A sensible default implementation is provided. """ - r = "ro quiet liveimg" + r = kickstart.get_kernel_args(self.ks) if os.path.exists(self._instroot + "/usr/bin/rhgb"): r += " rhgb" return r From todd655495 at yahoo.com Tue Jul 8 21:45:24 2008 From: todd655495 at yahoo.com (Todd N) Date: Tue, 8 Jul 2008 14:45:24 -0700 (PDT) Subject: [Fedora-livecd-list] Issue with SELinux and /mnt/live on Fedora Live CD Message-ID: <983725.6159.qm@web54010.mail.re2.yahoo.com> Hello, ? I'm trying to use openvpn on a Fedora Live CD built using livecd-creator.? I'd like to have openvpn grab the required certificates and keys from somewhere other than /etc/openvpn - specifically a directory under /mnt/live.? However, on configuring such a VPN connection, when trying to actually connect to it, SELinux balks, returning the following error: ? SELinux is preventing openvpn (openvpn_t) "search" to ./mnt (mnt_t). ? What can I do within SELinux to allow openvpn to access an external file system?? Is there a specific policy change that I can make to allow this type of access? ? Thanks for any help that can be offered.? If you need any more information, please let me know. ? Todd -------------- next part -------------- An HTML attachment was scrubbed... URL: From DON.RAIKES at oracle.com Tue Jul 8 23:38:55 2008 From: DON.RAIKES at oracle.com (DON.RAIKES at oracle.com) Date: Tue, 8 Jul 2008 16:38:55 -0700 (PDT) Subject: [Fedora-livecd-list] using a specific kernel Message-ID: <581a79e0-27c7-43cf-885c-8f396f441363@default> Hello, I recently installed fedora 9, and have built a custom kernel for it. I now want to create a livecd using my custom kernel, but when I create the livecd based on the livecd-fedora-minimial.ks file, it picks up the latest kernel from the development repository. JHow can I force livecd-creator to pull my custom kernel? -------------- next part -------------- An HTML attachment was scrubbed... URL: From DON.RAIKES at oracle.com Wed Jul 9 01:58:30 2008 From: DON.RAIKES at oracle.com (DON.RAIKES at oracle.com) Date: Tue, 8 Jul 2008 18:58:30 -0700 (PDT) Subject: [Fedora-livecd-list] enabling login on livecd Message-ID: Hello, I am attempting to create a fedora 9 livecd based on the livecd-fedora-minimal.ks file. I understand that as is there is no login capabilities for this livecd. I have been successful in running livecd-creator and creatiing and burning the iso image. When I boot from it i get the login prompt no problem. Now my question is how do I enable logging in to the cd. I added the following lines to the .ks file: #!/bin/sh /usr/sbin/useradd -d /home/fedora fedora /usr/bin/passwd -d fedora My understanding was that this would create a fedora user with no password. I tried it on my regular fedora 9 system, and it created the user properly and I can login with no password. When I recreated the livecd, I drilled down and looked at the ext3fs.img and found that the fedora user was indeed created However, when I boot from the livecd, and put in fedora as the user, it prompts me for a password, and no matter what I enter, it won't let me log in. Is there something else I need to do to enable loggin into the livecd? -------------- next part -------------- An HTML attachment was scrubbed... URL: From larry.brigman at gmail.com Wed Jul 9 04:46:27 2008 From: larry.brigman at gmail.com (Larry Brigman) Date: Tue, 8 Jul 2008 21:46:27 -0700 Subject: [Fedora-livecd-list] making livecd for another similar distro Message-ID: Is there a way to force the program to generate an iso when pointing at a yum repository for another distro. I have tried this but get 'package not found'. I know the package is there because I had created the repository locally from the install CDs. This is for Oracle Linux 5.1. From dhuff at redhat.com Thu Jul 10 21:24:52 2008 From: dhuff at redhat.com (David Huff) Date: Thu, 10 Jul 2008 17:24:52 -0400 Subject: [Fedora-livecd-list] [PATCH] added get_partitions to kickstart.py In-Reply-To: <483C3D5E.5050901@redhat.com> References: <483C3D5E.5050901@redhat.com> Message-ID: <1215725092-29017-1-git-send-email-dhuff@redhat.com> --- imgcreate/kickstart.py | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/imgcreate/kickstart.py b/imgcreate/kickstart.py index 0f797b8..0fbefb7 100644 --- a/imgcreate/kickstart.py +++ b/imgcreate/kickstart.py @@ -495,6 +495,9 @@ def get_groups(ks, required = []): def get_excluded(ks, required = []): return ks.handler.packages.excludedList + required +def get_partitions(ks, required = []): + return ks.handler.partition.partitions + def ignore_missing(ks): return ks.handler.packages.handleMissing == ksconstants.KS_MISSING_IGNORE -- 1.5.4.1 From dhuff at redhat.com Thu Jul 10 21:26:55 2008 From: dhuff at redhat.com (David Huff) Date: Thu, 10 Jul 2008 17:26:55 -0400 Subject: [Fedora-livecd-list] [PATCH] re-factor the imgcreate/fs.py module In-Reply-To: <483C3D5E.5050901@redhat.com> References: <483C3D5E.5050901@redhat.com> Message-ID: <1215725215-29130-1-git-send-email-dhuff@redhat.com> From: Daniel P. Berrange --- imgcreate/fs.py | 328 +++++++++++++++++++++++++++++++++++++++++++++++++++++-- 1 files changed, 320 insertions(+), 8 deletions(-) diff --git a/imgcreate/fs.py b/imgcreate/fs.py index 98c0db4..5d94018 100644 --- a/imgcreate/fs.py +++ b/imgcreate/fs.py @@ -24,6 +24,7 @@ import stat import subprocess import random import string +import logging from imgcreate.errors import * @@ -86,6 +87,9 @@ class BindChrootMount: subprocess.call(["/bin/umount", self.dest]) self.mounted = False +#=============================================================================== +# LoopbackMount compatibility layer for old API +#=============================================================================== class LoopbackMount: def __init__(self, lofile, mountdir, fstype = None): self.lofile = lofile @@ -162,6 +166,9 @@ class LoopbackMount: self.mounted = True +#=============================================================================== +# SparseLoopbackMount compatibility layer for old API +#=============================================================================== class SparseLoopbackMount(LoopbackMount): def __init__(self, lofile, mountdir, size, fstype = None): LoopbackMount.__init__(self, lofile, mountdir, fstype) @@ -192,6 +199,9 @@ class SparseLoopbackMount(LoopbackMount): def create(self): self.expand(create = True) +#=============================================================================== +# SparseExtLoopbackMount compatibility layer for old API +#=============================================================================== class SparseExtLoopbackMount(SparseLoopbackMount): def __init__(self, lofile, mountdir, size, fstype, blocksize, fslabel): SparseLoopbackMount.__init__(self, lofile, mountdir, size, fstype) @@ -288,6 +298,308 @@ class SparseExtLoopbackMount(SparseLoopbackMount): self.resize(size) return minsize +#=============================================================================== +# Disk +#Most of the change here involves re-factoring the imgcreate/fs.py module. +#The SparseExtLoopbackMount, SparseLoopbackMount, LoopbackMount classes all +#have the built-in limitation that the image being produced corresponds to +#a single filesystem / loop mount. With the disk creator, the image being +#produced can be partitioned into multiple chunks, with many filesystems. +#Furthermore, not all of them require loopback mounts, as the partitions +#themselves are already visible via /dev/mapper/ +# +#So this patch separates the roles. There are now classes which deal with +#accessing / creating disks: +# +# Disk - generic base for disks +# RawDisk - a disk backed by a block device +# LoopbackDisk - a disk backed by a file +# SparseLoopbackDisk - a disk backed by a sparse file +# +#The 'create' method must make the disk visible as a block device - eg +#by calling losetup. For RawDisk, this is obviously a no-op. The 'cleanup' +#method must undo the 'create' operation. +# +#There are then classes which deal with mounting things: +# +# Mount - generic base for mounts +# DiskMount - able to mount a Disk object +# ExtDiskMount - able to format/resize ext3 filesystems when mounting +#=============================================================================== +class Disk: + def __init__(self, size, device = None): + self._device = device + self._size = size + + def create(self): + pass + + def cleanup(self): + pass + + def get_device(self): + return self._device + def set_device(self, path): + self._device = path + device = property(get_device, set_device) + + def get_size(self): + return self._size + size = property(get_size) + + +class RawDisk(Disk): + def __init__(self, size, device): + Disk.__init__(self, size, device) + + def fixed(self): + return True + + def exists(self): + return True + +class LoopbackDisk(Disk): + def __init__(self, lofile, size): + Disk.__init__(self, size) + self.lofile = lofile + + def fixed(self): + return False + + def exists(self): + return os.path.exists(self.lofile) + + def create(self): + if self.device is not None: + return + + losetupProc = subprocess.Popen(["/sbin/losetup", "-f"], + stdout=subprocess.PIPE) + losetupOutput = losetupProc.communicate()[0] + + if losetupProc.returncode: + raise MountError("Failed to allocate loop device for '%s'" % + self.lofile) + + device = losetupOutput.split()[0] + + logging.debug("Losetup add %s mapping to %s" % (device, self.lofile)) + rc = subprocess.call(["/sbin/losetup", device, self.lofile]) + if rc != 0: + raise MountError("Failed to allocate loop device for '%s'" % + self.lofile) + self.device = device + + def cleanup(self): + if self.device is None: + return + logging.debug("Losetup remove %s" % self.device) + rc = subprocess.call(["/sbin/losetup", "-d", self.device]) + self.device = None + + + +class SparseLoopbackDisk(LoopbackDisk): + def __init__(self, lofile, size): + LoopbackDisk.__init__(self, lofile, size) + + def expand(self, create = False, size = None): + flags = os.O_WRONLY + if create: + flags |= os.O_CREAT + makedirs(os.path.dirname(self.lofile)) + + if size is None: + size = self.size + + logging.debug("Extending sparse file %s to %d" % (self.lofile, size)) + fd = os.open(self.lofile, flags) + + os.lseek(fd, size, 0) + os.write(fd, '\x00') + os.close(fd) + + def truncate(self, size = None): + if size is None: + size = self.size + + logging.debug("Truncating sparse file %s to %d" % (self.lofile, size)) + fd = os.open(self.lofile, os.O_WRONLY) + os.ftruncate(fd, size) + os.close(fd) + + def create(self): + self.expand(create = True) + LoopbackDisk.create(self) + +class Mount: + def __init__(self, mountdir): + self.mountdir = mountdir + + def cleanup(self): + self.unmount() + + def mount(self): + pass + + def unmount(self): + pass + +class DiskMount(Mount): + def __init__(self, disk, mountdir, fstype = None, rmmountdir = True): + Mount.__init__(self, mountdir) + + self.disk = disk + self.fstype = fstype + self.rmmountdir = rmmountdir + + self.mounted = False + self.rmdir = False + + def cleanup(self): + Mount.cleanup(self) + self.disk.cleanup() + + def unmount(self): + if self.mounted: + logging.debug("Unmounting directory %s" % self.mountdir) + rc = subprocess.call(["/bin/umount", self.mountdir]) + if rc == 0: + self.mounted = False + + if self.rmdir and not self.mounted: + try: + os.rmdir(self.mountdir) + except OSError, e: + pass + self.rmdir = False + + + def __create(self): + self.disk.create() + + + def mount(self): + if self.mounted: + return + + if not os.path.isdir(self.mountdir): + logging.debug("Creating mount point %s" % self.mountdir) + os.makedirs(self.mountdir) + self.rmdir = self.rmmountdir + + self.__create() + + logging.debug("Mounting %s at %s" % (self.disk.device, self.mountdir)) + args = [ "/bin/mount", self.disk.device, self.mountdir ] + if self.fstype: + args.extend(["-t", self.fstype]) + + rc = subprocess.call(args) + if rc != 0: + raise MountError("Failed to mount '%s' to '%s'" % + (self.disk.device, self.mountdir)) + + self.mounted = True + +class ExtDiskMount(DiskMount): + def __init__(self, disk, mountdir, fstype, blocksize, fslabel, rmmountdir=True): + DiskMount.__init__(self, disk, mountdir, fstype, rmmountdir) + self.blocksize = blocksize + self.fslabel = fslabel + + def __format_filesystem(self): + logging.debug("Formating %s filesystem on %s" % (self.fstype, self.disk.device)) + rc = subprocess.call(["/sbin/mkfs." + self.fstype, + "-F", "-L", self.fslabel, + "-m", "1", "-b", str(self.blocksize), + self.disk.device]) + # str(self.disk.size / self.blocksize)]) + if rc != 0: + raise MountError("Error creating %s filesystem" % (self.fstype,)) + logging.debug("Tuning filesystem on %s" % self.disk.device) + subprocess.call(["/sbin/tune2fs", "-c0", "-i0", "-Odir_index", + "-ouser_xattr,acl", self.disk.device]) + + def __resize_filesystem(self, size = None): + current_size = os.stat(self.disk.lofile)[stat.ST_SIZE] + + if size is None: + size = self.size + + if size == current_size: + return + + if size > current_size: + self.expand(size) + + self.__fsck() + + resize2fs(self.disk.lofile, size) + return size + + def __create(self): + resize = False + if not self.disk.fixed() and self.disk.exists(): + resize = True + + self.disk.create() + + if resize: + self.__resize_filesystem() + else: + self.__format_filesystem() + + def mount(self): + self.__create() + DiskMount.mount(self) + + def __fsck(self): + logging.debug("Checking filesystem %s" % self.disk.lofile) + subprocess.call(["/sbin/e2fsck", "-f", "-y", self.disk.lofile]) + + def __get_size_from_filesystem(self): + def parse_field(output, field): + for line in output.split("\n"): + if line.startswith(field + ":"): + return line[len(field) + 1:].strip() + + raise KeyError("Failed to find field '%s' in output" % field) + + dev_null = os.open("/dev/null", os.O_WRONLY) + try: + out = subprocess.Popen(['/sbin/dumpe2fs', '-h', self.disk.lofile], + stdout = subprocess.PIPE, + stderr = dev_null).communicate()[0] + finally: + os.close(dev_null) + + return int(parse_field(out, "Block count")) * self.blocksize + + def __resize_to_minimal(self): + self.__fsck() + + # + # Use a binary search to find the minimal size + # we can resize the image to + # + bot = 0 + top = self.__get_size_from_filesystem() + while top != (bot + 1): + t = bot + ((top - bot) / 2) + + if not resize2fs(self.disk.lofile, t): + top = t + else: + bot = t + return top + + def resparse(self, size = None): + self.cleanup() + minsize = self.__resize_to_minimal() + self.disk.truncate(minsize) + return minsize + class DeviceMapperSnapshot(object): def __init__(self, imgloop, cowloop): self.imgloop = imgloop @@ -306,8 +618,8 @@ class DeviceMapperSnapshot(object): if self.__created: return - self.imgloop.loopsetup() - self.cowloop.loopsetup() + self.imgloop.create() + self.cowloop.create() self.__name = "imgcreate-%d-%d" % (os.getpid(), random.randint(0, 2**16)) @@ -315,8 +627,8 @@ class DeviceMapperSnapshot(object): size = os.stat(self.imgloop.lofile)[stat.ST_SIZE] table = "0 %d snapshot %s %s p 8" % (size / 512, - self.imgloop.loopdev, - self.cowloop.loopdev) + self.imgloop.device, + self.cowloop.device) args = ["/sbin/dmsetup", "create", self.__name, "--table", table] if subprocess.call(args) != 0: @@ -382,15 +694,14 @@ class DeviceMapperSnapshot(object): # 8) Create a squashfs of the COW # def create_image_minimizer(path, image, minimal_size): - imgloop = LoopbackMount(image, "None") + imgloop = LoopbackDisk(image, None) # Passing bogus size - doesn't matter - cowloop = SparseLoopbackMount(os.path.join(os.path.dirname(path), "osmin"), - None, 64L * 1024L * 1024L) + cowloop = SparseLoopbackDisk(os.path.join(os.path.dirname(path), "osmin"), + 64L * 1024L * 1024L) snapshot = DeviceMapperSnapshot(imgloop, cowloop) try: - cowloop.create() snapshot.create() resize2fs(snapshot.path, minimal_size) @@ -404,3 +715,4 @@ def create_image_minimizer(path, image, minimal_size): mksquashfs(cowloop.lofile, path) os.unlink(cowloop.lofile) + -- 1.5.4.1 From dhuff at redhat.com Thu Jul 10 21:28:06 2008 From: dhuff at redhat.com (David Huff) Date: Thu, 10 Jul 2008 17:28:06 -0400 Subject: [Fedora-livecd-list] [PATCH] added compat shims for old api In-Reply-To: <483C3D5E.5050901@redhat.com> References: <483C3D5E.5050901@redhat.com> Message-ID: <1215725286-29216-1-git-send-email-dhuff@redhat.com> --- imgcreate/fs.py | 201 +----------------------------------------------------- 1 files changed, 4 insertions(+), 197 deletions(-) diff --git a/imgcreate/fs.py b/imgcreate/fs.py index 5d94018..d8c6731 100644 --- a/imgcreate/fs.py +++ b/imgcreate/fs.py @@ -92,211 +92,21 @@ class BindChrootMount: #=============================================================================== class LoopbackMount: def __init__(self, lofile, mountdir, fstype = None): - self.lofile = lofile - self.mountdir = mountdir - self.fstype = fstype - - self.mounted = False - self.losetup = False - self.rmdir = False - self.loopdev = None - - def cleanup(self): - self.unmount() - self.lounsetup() - - def unmount(self): - if self.mounted: - rc = subprocess.call(["/bin/umount", self.mountdir]) - if rc == 0: - self.mounted = False - - if self.rmdir and not self.mounted: - try: - os.rmdir(self.mountdir) - except OSError, e: - pass - self.rmdir = False - - def lounsetup(self): - if self.losetup: - rc = subprocess.call(["/sbin/losetup", "-d", self.loopdev]) - self.losetup = False - self.loopdev = None - - def loopsetup(self): - if self.losetup: - return - - losetupProc = subprocess.Popen(["/sbin/losetup", "-f"], - stdout=subprocess.PIPE) - losetupOutput = losetupProc.communicate()[0] - - if losetupProc.returncode: - raise MountError("Failed to allocate loop device for '%s'" % - self.lofile) - - self.loopdev = losetupOutput.split()[0] - - rc = subprocess.call(["/sbin/losetup", self.loopdev, self.lofile]) - if rc != 0: - raise MountError("Failed to allocate loop device for '%s'" % - self.lofile) - - self.losetup = True - - def mount(self): - if self.mounted: - return - - self.loopsetup() - - if not os.path.isdir(self.mountdir): - os.makedirs(self.mountdir) - self.rmdir = True - - args = [ "/bin/mount", self.loopdev, self.mountdir ] - if self.fstype: - args.extend(["-t", self.fstype]) - - rc = subprocess.call(args) - if rc != 0: - raise MountError("Failed to mount '%s' to '%s'" % - (self.loopdev, self.mountdir)) - - self.mounted = True + DiskMount.__init__(LoopbackDisk(lofile,size = 0),mountdir,fstype,rmmountdir = True) #=============================================================================== # SparseLoopbackMount compatibility layer for old API #=============================================================================== class SparseLoopbackMount(LoopbackMount): def __init__(self, lofile, mountdir, size, fstype = None): - LoopbackMount.__init__(self, lofile, mountdir, fstype) - self.size = size - - def expand(self, create = False, size = None): - flags = os.O_WRONLY - if create: - flags |= os.O_CREAT - makedirs(os.path.dirname(self.lofile)) - - if size is None: - size = self.size - - fd = os.open(self.lofile, flags) - - os.lseek(fd, size, 0) - os.write(fd, '\x00') - os.close(fd) - - def truncate(self, size = None): - if size is None: - size = self.size - fd = os.open(self.lofile, os.O_WRONLY) - os.ftruncate(fd, size) - os.close(fd) - - def create(self): - self.expand(create = True) + DiskMount.__init__(SparseLoopbackDisk(lofile,size),mountdir,fstype,rmmountdir = True) #=============================================================================== # SparseExtLoopbackMount compatibility layer for old API #=============================================================================== class SparseExtLoopbackMount(SparseLoopbackMount): def __init__(self, lofile, mountdir, size, fstype, blocksize, fslabel): - SparseLoopbackMount.__init__(self, lofile, mountdir, size, fstype) - self.blocksize = blocksize - self.fslabel = fslabel - - def __format_filesystem(self): - rc = subprocess.call(["/sbin/mkfs." + self.fstype, - "-F", "-L", self.fslabel, - "-m", "1", "-b", str(self.blocksize), - self.lofile, - str(self.size / self.blocksize)]) - if rc != 0: - raise MountError("Error creating %s filesystem" % (self.fstype,)) - subprocess.call(["/sbin/tune2fs", "-c0", "-i0", "-Odir_index", - "-ouser_xattr,acl", self.lofile]) - - def create(self): - SparseLoopbackMount.create(self) - self.__format_filesystem() - - def resize(self, size = None): - current_size = os.stat(self.lofile)[stat.ST_SIZE] - - if size is None: - size = self.size - - if size == current_size: - return - - if size > current_size: - self.expand(size) - - self.__fsck() - - resize2fs(self.lofile, size) - - if size < current_size: - self.truncate(size) - return size - - def mount(self): - if not os.path.isfile(self.lofile): - self.create() - else: - self.resize() - return SparseLoopbackMount.mount(self) - - def __fsck(self): - subprocess.call(["/sbin/e2fsck", "-f", "-y", self.lofile]) - - def __get_size_from_filesystem(self): - def parse_field(output, field): - for line in output.split("\n"): - if line.startswith(field + ":"): - return line[len(field) + 1:].strip() - - raise KeyError("Failed to find field '%s' in output" % field) - - dev_null = os.open("/dev/null", os.O_WRONLY) - try: - out = subprocess.Popen(['/sbin/dumpe2fs', '-h', self.lofile], - stdout = subprocess.PIPE, - stderr = dev_null).communicate()[0] - finally: - os.close(dev_null) - - return int(parse_field(out, "Block count")) * self.blocksize - - def __resize_to_minimal(self): - self.__fsck() - - # - # Use a binary search to find the minimal size - # we can resize the image to - # - bot = 0 - top = self.__get_size_from_filesystem() - while top != (bot + 1): - t = bot + ((top - bot) / 2) - - if not resize2fs(self.lofile, t): - top = t - else: - bot = t - return top - - def resparse(self, size = None): - self.cleanup() - - minsize = self.__resize_to_minimal() - - self.truncate(minsize) - self.resize(size) - return minsize + ExtDiskMount.__init__(SparseLoopbackDisk(lofile,size), mountdir, fstype, blocksize, fslabel, rmmountdir = True) #=============================================================================== # Disk @@ -347,7 +157,6 @@ class Disk: return self._size size = property(get_size) - class RawDisk(Disk): def __init__(self, size, device): Disk.__init__(self, size, device) @@ -396,9 +205,7 @@ class LoopbackDisk(Disk): logging.debug("Losetup remove %s" % self.device) rc = subprocess.call(["/sbin/losetup", "-d", self.device]) self.device = None - - - + class SparseLoopbackDisk(LoopbackDisk): def __init__(self, lofile, size): LoopbackDisk.__init__(self, lofile, size) -- 1.5.4.1 From dhuff at redhat.com Thu Jul 10 21:30:26 2008 From: dhuff at redhat.com (David Huff) Date: Thu, 10 Jul 2008 17:30:26 -0400 Subject: [Fedora-livecd-list] [PATCH] switch internal code to use new api In-Reply-To: <483C3D5E.5050901@redhat.com> References: <483C3D5E.5050901@redhat.com> Message-ID: <1215725426-29347-1-git-send-email-dhuff@redhat.com> --- imgcreate/creator.py | 17 ++++++++++------- imgcreate/live.py | 6 +++--- 2 files changed, 13 insertions(+), 10 deletions(-) diff --git a/imgcreate/creator.py b/imgcreate/creator.py index c9ed60c..e0f6288 100644 --- a/imgcreate/creator.py +++ b/imgcreate/creator.py @@ -209,7 +209,11 @@ class ImageCreator(object): """ s = "/dev/root / %s defaults,noatime 0 0\n" %(self._fstype) - s += "devpts /dev/pts devpts gid=5,mode=620 0 0\n" + s += self._get_fstab_special() + return s + + def _get_fstab_special(self): + s = "devpts /dev/pts devpts gid=5,mode=620 0 0\n" s += "tmpfs /dev/shm tmpfs defaults 0 0\n" s += "proc /proc proc defaults 0 0\n" s += "sysfs /sys sysfs defaults 0 0\n" @@ -904,12 +908,11 @@ class LoopImageCreator(ImageCreator): self.__base_on(base_on) shutil.copyfile(base_on, self._image) - self.__instloop = SparseExtLoopbackMount(self._image, - self._instroot, - self.__image_size, - self.__fstype, - self.__blocksize, - self.fslabel) + self.__instloop = ExtDiskMount(SparseLoopbackDisk(self._image, self.__image_size), + self._instroot, + self.__fstype, + self.__blocksize, + self.fslabel) try: self.__instloop.mount() diff --git a/imgcreate/live.py b/imgcreate/live.py index 0bf50f2..1b486e2 100644 --- a/imgcreate/live.py +++ b/imgcreate/live.py @@ -131,7 +131,7 @@ class LiveImageCreatorBase(LoopImageCreator): # def __base_on(self, base_on): """helper function to extract ext3 file system from a live CD ISO""" - isoloop = LoopbackMount(base_on, self._mkdtemp()) + isoloop = Mount(LoopbackDisk(base_on), self._mkdtemp()) try: isoloop.mount() @@ -145,10 +145,10 @@ class LiveImageCreatorBase(LoopImageCreator): else: squashimg = isoloop.mountdir + "/LiveOS/squashfs.img" - squashloop = LoopbackMount(squashimg, self._mkdtemp(), "squashfs") + squashloop = Mount(LoopbackDisk(squashimg), self._mkdtemp(), "squashfs") try: - if not os.path.exists(squashloop.lofile): + if not squashloop.disk.exists(): raise CreatorError("'%s' is not a valid live CD ISO : " "squashfs.img doesn't exist" % base_on) -- 1.5.4.1 From jgranado at redhat.com Fri Jul 11 14:02:06 2008 From: jgranado at redhat.com (Joel Andres Granados) Date: Fri, 11 Jul 2008 16:02:06 +0200 Subject: [Fedora-livecd-list] Add firstaidkit to base desktop install Message-ID: <1215784927-28813-1-git-send-email-jgranado@redhat.com> This change will pull in all the current plugins currently in devel, the gui, backend and all the related documentation. It will not bring in the devel package that is used to actually make plugins. From jgranado at redhat.com Fri Jul 11 14:02:07 2008 From: jgranado at redhat.com (Joel Andres Granados) Date: Fri, 11 Jul 2008 16:02:07 +0200 Subject: [Fedora-livecd-list] [PATCH] Add firstaidkit to livecd. In-Reply-To: <1215784927-28813-1-git-send-email-jgranado@redhat.com> References: <1215784927-28813-1-git-send-email-jgranado@redhat.com> Message-ID: <1215784927-28813-2-git-send-email-jgranado@redhat.com> --- config/livecd-fedora-base-desktop.ks | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/config/livecd-fedora-base-desktop.ks b/config/livecd-fedora-base-desktop.ks index 586c958..602e9f6 100644 --- a/config/livecd-fedora-base-desktop.ks +++ b/config/livecd-fedora-base-desktop.ks @@ -21,6 +21,7 @@ repo --name=development --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist @printing kernel memtest86+ +firstaidkit-plugin-all # save some space -specspo -- 1.5.4.1 From kanarip at kanarip.com Fri Jul 11 14:40:01 2008 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Fri, 11 Jul 2008 16:40:01 +0200 Subject: [Fedora-livecd-list] Attention Spin Maintainers Message-ID: <487770C1.5020407@kanarip.com> Spin Maintainers, may I please have your attention. To be included in the Fedora 10 release cycle, you'll need a Feature page in category ProposedFeature (and change that to the ProposedFeatureF10 category when you feel the Spin Concept is ready for actual inclusion). This page should be ready (eg. prepared) before the Alpha freeze. The Feature Page for that spin should have a short description of the spin concept, it's target audience, any notes you want to write down on why it is you do foo or bar. It should also contain a link to the kickstart, but since a mailing list is still pending, I suggest you email it to fedora-livecd-list at redhat.com. The Spin SIG picks it up, does a technical review, and sends you the OK or comments. If the Spin SIG approves, your kickstart will be added to the GIT repository for the appropriate branch(es). At this point, it'll be forced to use "generic-logos", still. The Spin SIG will work with you to fit in the kickstart into the pool, get some things right or more right, and while you -by then at least-, should also have commit "access to the GIT repository"[1], the spin concept will continue it's path to the Board for trademark approval. Make sure that before this happens, you have some kind of strong argument in favor of the spin so they just can't say no. It makes all our lives easier ;-) Once you're kickstart (spin concept) has the almighty Board trademark approval stamp, we change "generic-logos" back to "fedora-logos". The kickstart should be built upon fedora-live-base.ks in the spin-kickstarts repository at: http://git.fedorahosted.org/git/?p=spin-kickstarts.git This GIT repository has several branches: master, and a very distinctive branch for each live release of Fedora out there. Naturally, the master branch is where development goes against rawhide, and the release specific branches is where you have a chance to maintain your spin concept for the duration of the lifecycle of that release. Basing on fedora-live-base.ks may be deferred from such as with the Electronic Lab DVD spin: it bases itself on the KDE CD spin so that minimal overhead in duplicate configuration and scripts is accomplished. You may do the same; as long as you make sure you tell us in your Feature page or technical review request. And if you don't tell us in your Feature page, I'll read it from the kickstart anyway. For now, you are requested to start filling out your spin's Feature page, get them to the Spin SIG (members are on [2]), request access to the gitspin-kickstarts group[1] in FAS, and start composing every two weeks or so, to verify rawhide hasn't changed too much. To watch commits to the spin-kickstarts GIT repository, subscribe to the spin-kickstarts-commits list[3] I'd love to see you all come back to me in the next week or so ;-) Thanks in advance, Kind regards, Jeroen van Meeuwen -kanarip [1] https://admin.fedoraproject.org/accounts/group/view/gitspin-kickstarts [2] http://fedoraproject.org/wiki/SIGs/Spins (members, guidelines, DOs and DONTs) [3] https://fedorahosted.org/mailman/listinfo/spin-kickstarts-commits From rdieter at math.unl.edu Fri Jul 11 15:13:28 2008 From: rdieter at math.unl.edu (Rex Dieter) Date: Fri, 11 Jul 2008 10:13:28 -0500 Subject: [Fedora-livecd-list] Re: Attention Spin Maintainers References: <487770C1.5020407@kanarip.com> Message-ID: Jeroen van Meeuwen wrote: > Spin Maintainers, may I please have your attention. > > To be included in the Fedora 10 release cycle, you'll need a Feature > page in category ProposedFeature (and change that to the > ProposedFeatureF10 category when you feel the Spin Concept is ready for > actual inclusion). This page should be ready (eg. prepared) before the > Alpha freeze. All or just new spins (ie, where to Desktop, KDE, and other existing ones fall)? -- Rex From notting at redhat.com Fri Jul 11 17:18:11 2008 From: notting at redhat.com (Bill Nottingham) Date: Fri, 11 Jul 2008 13:18:11 -0400 Subject: [Fedora-livecd-list] Re: Attention Spin Maintainers In-Reply-To: References: <487770C1.5020407@kanarip.com> Message-ID: <20080711171811.GC13166@nostromo.devel.redhat.com> Rex Dieter (rdieter at math.unl.edu) said: > Jeroen van Meeuwen wrote: > > > Spin Maintainers, may I please have your attention. > > > > To be included in the Fedora 10 release cycle, you'll need a Feature > > page in category ProposedFeature (and change that to the > > ProposedFeatureF10 category when you feel the Spin Concept is ready for > > actual inclusion). This page should be ready (eg. prepared) before the > > Alpha freeze. > > All or just new spins (ie, where to Desktop, KDE, and other existing ones > fall)? >From talking to people, this is 'all spins which are not part of the 'normal' set (i.e., Fedora install set, Desktop live, KDE live.) Bill From sundaram at fedoraproject.org Fri Jul 11 19:56:46 2008 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Sat, 12 Jul 2008 01:26:46 +0530 Subject: [Fedora-livecd-list] Re: Attention Spin Maintainers In-Reply-To: <20080711171811.GC13166@nostromo.devel.redhat.com> References: <487770C1.5020407@kanarip.com> <20080711171811.GC13166@nostromo.devel.redhat.com> Message-ID: <4877BAFE.4040109@fedoraproject.org> Bill Nottingham wrote: > Rex Dieter (rdieter at math.unl.edu) said: >> Jeroen van Meeuwen wrote: >> >>> Spin Maintainers, may I please have your attention. >>> >>> To be included in the Fedora 10 release cycle, you'll need a Feature >>> page in category ProposedFeature (and change that to the >>> ProposedFeatureF10 category when you feel the Spin Concept is ready for >>> actual inclusion). This page should be ready (eg. prepared) before the >>> Alpha freeze. >> All or just new spins (ie, where to Desktop, KDE, and other existing ones >> fall)? > >>From talking to people, this is 'all spins which are not part of the > 'normal' set (i.e., Fedora install set, Desktop live, KDE live.) Should I submit feature pages for games and xfce spin and does it have to be done for each release? I am not sure I understand the purpose. Rahul From DON.RAIKES at oracle.com Fri Jul 11 21:29:58 2008 From: DON.RAIKES at oracle.com (DON.RAIKES at oracle.com) Date: Fri, 11 Jul 2008 14:29:58 -0700 (PDT) Subject: [Fedora-livecd-list] adding local rpms Message-ID: <3769d7f9-28c5-4146-ae96-bbea887acce1@default> Hello, I am trying to create an accessible fedora livecd, and one of the problem I have is that some of the packages I want to use are not on any rpm repository at present. I have them locally on my desktop system. Short of creating a local repository (which I know isn't difficult), is there a way to simply include the rpms into the livecd creation process? -------------- next part -------------- An HTML attachment was scrubbed... URL: From DON.RAIKES at ORACLE.COM Sat Jul 12 21:19:19 2008 From: DON.RAIKES at ORACLE.COM (DON.RAIKES at ORACLE.COM) Date: Sat, 12 Jul 2008 14:19:19 -0700 (PDT) Subject: [Fedora-livecd-list] kernel panic on base-desktop Message-ID: <91075cb2-6ffd-4577-8710-8e94a9d77675@default> Hi, I have fedora 9 installed on my desktop, and I used yum to install livecd-tools. Just as a baseline before doing any changes, I tried creating a livecd based on the default livecd-fedora-base-desktop.ks that ships with the livecd-tools. $ livecd-creator -c livecd-fedora-base-desktop.ks -f mydesktop The iso was created just fine, so I used wodim to burn it to a cd. $ wodim -dao dev=0,0,0 mydesktop.iso I rebooted with the cd in the drive and the results: kernel panic! While I am not a linux newbie per ce, I am not sure where to start debugging this kind of situation. Could something be broken in rawhide causing this, or is it something I did wrong? -------------- next part -------------- An HTML attachment was scrubbed... URL: From kanarip at kanarip.com Sun Jul 13 14:20:00 2008 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Sun, 13 Jul 2008 16:20:00 +0200 Subject: [Fedora-livecd-list] Re: Attention Spin Maintainers In-Reply-To: <4877BAFE.4040109@fedoraproject.org> References: <487770C1.5020407@kanarip.com> <20080711171811.GC13166@nostromo.devel.redhat.com> <4877BAFE.4040109@fedoraproject.org> Message-ID: <487A0F10.6040906@kanarip.com> Rahul Sundaram wrote: > Bill Nottingham wrote: >> Rex Dieter (rdieter at math.unl.edu) said: >>> Jeroen van Meeuwen wrote: Snip... I just have to say this thread somewhat continued on fedora-devel instead... Sorry for the inconvenience of everyone following the thread here... If you want to read the answers to some of the questions asked, here's the archive link to this thread: https://www.redhat.com/archives/fedora-devel-list/2008-July/msg00686.html Kind regards, Jeroen van Meeuwen -kanarip From DON.RAIKES at ORACLE.COM Sun Jul 13 22:25:59 2008 From: DON.RAIKES at ORACLE.COM (DON.RAIKES at ORACLE.COM) Date: Sun, 13 Jul 2008 15:25:59 -0700 (PDT) Subject: [Fedora-livecd-list] Re: Attention Spin Maintainers In-Reply-To: <487A0F10.6040906@kanarip.com> Message-ID: <4bea518c-e863-4b76-a665-af071327b61e@default> Jareon et al, I am interested in creating a sping that is designed for accessibility (includes brltty, emacspeak, orca etc). I am having a few problems getting even the fedora-live-base.ks file to generate a working livecd. When I generate it and boot from the cd I get a ll kinds of errors mostly concerning an inability to mount the root file system and/or the proc/dev file systems. The steps I took were: $ livecd-creator -c fedora-live-base.ks -f base the base.iso was created. wodim -dao dev=0,0,0 base.iso The cd was burned without errors. reboot after teh timeout from isolinux, I get a ton of errors. Since I am blind, it is difficult for me to debug the startup process without sighted assistance, and I wish there were a way to use qemu to test the iso before burning it to a cd, but as far as I can tell qemu is not accessible :) Any suggestions would be appreciated. -----Original Message----- From: Jeroen van Meeuwen [mailto:kanarip at kanarip.com] Sent: Sunday, July 13, 2008 7:20 AM To: fedora-livecd-list at redhat.com Subject: Re: [Fedora-livecd-list] Re: Attention Spin Maintainers Rahul Sundaram wrote: > Bill Nottingham wrote: >> Rex Dieter (rdieter at math.unl.edu) said: >>> Jeroen van Meeuwen wrote: Snip... I just have to say this thread somewhat continued on fedora-devel instead... Sorry for the inconvenience of everyone following the thread here... If you want to read the answers to some of the questions asked, here's the archive link to this thread: https://www.redhat.com/archives/fedora-devel-list/2008-July/msg00686.html Kind regards, Jeroen van Meeuwen -kanarip -- Fedora-livecd-list mailing list Fedora-livecd-list at redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list From svahl at fedoraproject.org Mon Jul 14 06:31:12 2008 From: svahl at fedoraproject.org (Sebastian Vahl) Date: Mon, 14 Jul 2008 06:31:12 +0000 (UTC) Subject: [Fedora-livecd-list] config/livecd-fedora-kde.ks Message-ID: <20080714063112.A8CE512000C@lists.fedorahosted.org> config/livecd-fedora-kde.ks | 27 ++++++++++++++++----------- 1 file changed, 16 insertions(+), 11 deletions(-) New commits: commit 8846d303c335551ec6f48a9a5c2a502cb5823681 Author: Sebastian Vahl Date: Mon Jul 14 08:28:53 2008 +0200 remove koffice, kaffeine and ktorrent for space issues; make liveinst.desktop visible on desktop diff --git a/config/livecd-fedora-kde.ks b/config/livecd-fedora-kde.ks index 8cefa08..eb8c119 100644 --- a/config/livecd-fedora-kde.ks +++ b/config/livecd-fedora-kde.ks @@ -3,26 +3,26 @@ %packages @kde-desktop -# include nm-applet directly -NetworkManager-gnome - # unwanted packages from @kde-desktop # don't include these for now to fit on a cd # digikam (~11 megs), ktorrent (~3 megs), amarok (~14 megs), -# kdegames (~23 megs) +# kdegames (~31 megs), koffice-* (~51 megs), kftpgrabber (~1 megs) +# kaffeine-* (~3 megs) -amarok -digikam -kdeedu -scribus -#-ktorrent +-ktorrent #-kdegames #-kftpgrabber* - -# KDE 3 -koffice-kword -koffice-kspread -koffice-kpresenter -koffice-filters +-kaffeine* + +-koffice-* +# KDE 3 +#koffice-kword +#koffice-kspread +#koffice-kpresenter +#koffice-filters k3b filelight # twinkle (~10 megs) @@ -91,4 +91,9 @@ FavoriteURLs=/usr/share/applications/kde4/konqbrowser.desktop,/usr/share/applica MENU_EOF chown -R fedora:fedora /home/fedora/.kde/ +# show liveinst.desktop on and in menu +sed -i 's/NoDisplay=true/NoDisplay=false/' /usr/share/applications/liveinst.desktop + +EOF + %end From katzj at fedoraproject.org Mon Jul 14 17:29:53 2008 From: katzj at fedoraproject.org (Jeremy Katz) Date: Mon, 14 Jul 2008 17:29:53 +0000 (UTC) Subject: [Fedora-livecd-list] 2 commits - config/livecd-fedora-base-desktop.ks imgcreate/live.py Message-ID: <20080714172953.BB205120024@lists.fedorahosted.org> config/livecd-fedora-base-desktop.ks | 1 + imgcreate/live.py | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) New commits: commit fdac06373192bf0421860cf1fe20bbe9812cfc5a Author: Jeremy Katz Date: Fri Jul 11 12:07:33 2008 -0400 Add mptsas to module list (#454898) diff --git a/imgcreate/live.py b/imgcreate/live.py index 0bf50f2..e0bac09 100644 --- a/imgcreate/live.py +++ b/imgcreate/live.py @@ -67,7 +67,7 @@ class LiveImageCreatorBase(LoopImageCreator): self.__isodir = None - self.__modules = ["=ata", "sym53c8xx", "aic7xxx", "=usb", "=firewire", "=mmc", "=pcmcia"] + self.__modules = ["=ata", "sym53c8xx", "aic7xxx", "=usb", "=firewire", "=mmc", "=pcmcia", "mptsas"] self.__modules.extend(kickstart.get_modules(self.ks)) # commit 402a24145eb7f4d58e3809c1e594602b3a21d6a1 Author: Joel Andres Granados Date: Fri Jul 11 11:42:01 2008 -0400 Add firstaidkit to livecd This change will pull in all the current plugins currently in devel, the gui, backend and all the related documentation. It will not bring in the devel package that is used to actually make plugins. diff --git a/config/livecd-fedora-base-desktop.ks b/config/livecd-fedora-base-desktop.ks index 586c958..602e9f6 100644 --- a/config/livecd-fedora-base-desktop.ks +++ b/config/livecd-fedora-base-desktop.ks @@ -21,6 +21,7 @@ repo --name=development --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist @printing kernel memtest86+ +firstaidkit-plugin-all # save some space -specspo From michael.prisant at gmail.com Mon Jul 14 18:01:56 2008 From: michael.prisant at gmail.com (Michael Prisant) Date: Mon, 14 Jul 2008 14:01:56 -0400 Subject: [Fedora-livecd-list] livecd-iso-to-pxeboot: append line query Message-ID: <295537e50807141101q750acadasbad234ce154a442@mail.gmail.com> I sent the following query to Richard Jones author of the fedora livecd-iso-to-pxeboot regarding setup for pxeboot of live Fedora Live CD images and hoping someone on this list might advise on this question: ... I am trying to use your script as part of a project to setup diskless compute clients from a Fedora 9 server. I have already setup tftp, dhcp etc on this server and it is working for unattended kickstart installs and loading diagnostic programs to my clients on a private network. To begin I just wanted to see if I could pxeboot the live CD image. So I added the following stanza to my pxelinux.cfg/default file label live kernel fedora-releases-9-i386/vmlinuz0 append initrd=fedora-releases-9-i386/initrd0.img root=/Fedora-9-i686-Live.iso rootfstype=iso9660 rootflags=loop where I moved the vmlinuz.0 and intrd0.img files created by livecd-iso-to-pxeboot into the appropriate tftp server directories. My client first loads the initrd0.img. The client next begins to boot until it gets to the point where it needs to process the root directive. It then gives me an error message listing the ram disk block partitions. I have experimented with various directives to the "root=?" field. Even after reading your maillist thread with Jeremy Katz and others I am confused as to how to set this up. Sorry to be so clueless on this but I am not at all clear in this case what the "root=" is trying to point to or how I should set it up -- Can you advise? ... He responded by properly advising me to: You'll almost certainly be wanting to send this question over to the fedora-livecd-list: http://www.redhat.com/mailman/listinfo/fedora-livecd-list Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/ So hoping someone on the list might offer some help on setting this up. Thanks. Michael -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From katzj at redhat.com Mon Jul 14 19:16:17 2008 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 14 Jul 2008 15:16:17 -0400 Subject: [Fedora-livecd-list] adding local rpms In-Reply-To: <3769d7f9-28c5-4146-ae96-bbea887acce1@default> References: <3769d7f9-28c5-4146-ae96-bbea887acce1@default> Message-ID: <1216062977.4217.34.camel@aglarond.local> On Fri, 2008-07-11 at 14:29 -0700, DON.RAIKES at oracle.com wrote: > I am trying to create an accessible fedora livecd, and one of the > problem I have is that some of the packages I want to use are not on > any rpm repository at present. > > I have them locally on my desktop system. > > Short of creating a local repository (which I know isn't difficult), > is there a way to simply include the rpms into the livecd creation > process? Nope, the answer is to have a repository. file:/// repos are perfectly fine to use, so it's just a matter of running createrepo and then pointing to the repo on disk Jeremy From katzj at redhat.com Mon Jul 14 19:16:45 2008 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 14 Jul 2008 15:16:45 -0400 Subject: [Fedora-livecd-list] Re: Attention Spin Maintainers In-Reply-To: <4bea518c-e863-4b76-a665-af071327b61e@default> References: <4bea518c-e863-4b76-a665-af071327b61e@default> Message-ID: <1216063005.4217.35.camel@aglarond.local> On Sun, 2008-07-13 at 15:25 -0700, DON.RAIKES at ORACLE.COM wrote: > I am having a few problems getting even the fedora-live-base.ks file to generate a working livecd. > > When I generate it and boot from the cd I get a ll kinds of errors mostly concerning an inability to mount the root file system and/or the proc/dev file systems. Errors there tend to indicate either 1) Burn problems 2) Problems in the created initrd. The latter could be that you're using a distro which doesn't have the right mkinitrd bits or some other mismatch. It's hard to say without knowing what the actual errors are Jeremy From katzj at redhat.com Mon Jul 14 20:27:44 2008 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 14 Jul 2008 16:27:44 -0400 Subject: [Fedora-livecd-list] [PATCH] added get_partitions to kickstart.py In-Reply-To: <1215725092-29017-1-git-send-email-dhuff@redhat.com> References: <483C3D5E.5050901@redhat.com> <1215725092-29017-1-git-send-email-dhuff@redhat.com> Message-ID: <1216067264.4217.44.camel@aglarond.local> So, generally looking okay from the look I did. Two big little things left that I see 1) Commit messages should be more than one-liners. http://www.tpope.net/node/106 actually has a really nice description of what makes a good commit message 2) Instead of funky formatting of comments, just use the standard pydoc """ -- it'll also mean that we can extract api information and use help() if you're using the python interpreter on the command-line Jeremy From DON.RAIKES at oracle.com Mon Jul 14 23:24:27 2008 From: DON.RAIKES at oracle.com (DON.RAIKES at oracle.com) Date: Mon, 14 Jul 2008 16:24:27 -0700 (PDT) Subject: [Fedora-livecd-list] Re: Attention Spin Maintainers In-Reply-To: <1216063005.4217.35.camel@aglarond.local> Message-ID: Hi Jeremy, I just installed fedora 9 over the weekend (and again this morning had some issues with it). I am hoping hte issues I ran into yesterday were causing hte problems. I suspected the burning process originally since when I tried ot burn a dvd on my dvdrw drive wodim said it couldn't handle it at all. I'll try the base kickstart again tonight or tomorrow and see what happens now. -----Original Message----- From: Jeremy Katz [mailto:katzj at redhat.com] Sent: Monday, July 14, 2008 12:17 PM To: fedora-livecd-list at redhat.com Subject: RE: [Fedora-livecd-list] Re: Attention Spin Maintainers On Sun, 2008-07-13 at 15:25 -0700, DON.RAIKES at ORACLE.COM wrote: > I am having a few problems getting even the fedora-live-base.ks file to generate a working livecd. > > When I generate it and boot from the cd I get a ll kinds of errors mostly concerning an inability to mount the root file system and/or the proc/dev file systems. Errors there tend to indicate either 1) Burn problems 2) Problems in the created initrd. The latter could be that you're using a distro which doesn't have the right mkinitrd bits or some other mismatch. It's hard to say without knowing what the actual errors are Jeremy -- Fedora-livecd-list mailing list Fedora-livecd-list at redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list From s.w.pollux at gmail.com Tue Jul 15 05:29:30 2008 From: s.w.pollux at gmail.com (Pollux Su) Date: Tue, 15 Jul 2008 13:29:30 +0800 Subject: [Fedora-livecd-list] Failed to find group 'core':No groups available in any repository Message-ID: <780ddc050807142229k64292kba5dd42e93fdd1b4@mail.gmail.com> Hi all: I'm a newer of livecd-creater.When I am creating live cd,"Failed to find group 'core':No groups available in any repository" error message appears.Following is my steps: 1.Make a local repository: cp /media/Fedora8/Packages/* /var/www/html/yum/base/. createreop /var/www/html/yum/base 2.modified the /usr/share/livecd-tools/livecd-fedora-minimal.ks file, Just changed the repo line to: repo --name=fedora8 --baseurl=file:///var/www/html/yum/base 3.execute the command: livecd-creator --config=/usr/share/livecd-tools/livecd-fedora-minimal.ks --fslabel=Fedora8-Minial ........ Retireving file:///var/www/html/yum/base/repodata/repomd.xml... ok .... Error creating live CD: Failed to find gourp 'core' : No Groups Available in any repository Please help me. Thanks in advance! -------------- next part -------------- An HTML attachment was scrubbed... URL: From katzj at redhat.com Tue Jul 15 14:05:26 2008 From: katzj at redhat.com (Jeremy Katz) Date: Tue, 15 Jul 2008 10:05:26 -0400 Subject: [Fedora-livecd-list] Failed to find group 'core':No groups available in any repository In-Reply-To: <780ddc050807142229k64292kba5dd42e93fdd1b4@mail.gmail.com> References: <780ddc050807142229k64292kba5dd42e93fdd1b4@mail.gmail.com> Message-ID: <1216130726.4217.60.camel@aglarond.local> On Tue, 2008-07-15 at 13:29 +0800, Pollux Su wrote: > I'm a newer of livecd-creater.When I am creating live cd,"Failed > to find group 'core':No groups available in any repository" error > message appears.Following is my steps: When running createrepo, you need to use the -g flag so that the group metadata gets set up Jeremy From todd655495 at yahoo.com Tue Jul 15 15:03:37 2008 From: todd655495 at yahoo.com (Todd N) Date: Tue, 15 Jul 2008 08:03:37 -0700 (PDT) Subject: [Fedora-livecd-list] Persistence and /mnt/live Message-ID: <845467.73125.qm@web54011.mail.re2.yahoo.com> Hello, ? I have noticed?that when I do NOT have persistence installed on a bootable USB drive (or when I have a bootable CD), the path to the boot media is available as /mnt/live.? However, when I include persistence on a bootable USB, there is no path to the boot media, and the path /mnt/live exists but is empty.? (The USB was created using livecd-iso-to-disk?from a?Live CD that was created with livecd-creator.) ? As I am counting on pulling several files in from the boot media (but outside the squashfs file system) into my local file system on bootup,?it is important that there be consistency in where I might find these files, whether or not persistence is installed on the boot media. ? Can the /mnt/live path be enabled on a bootable USB with persistence installed? ? Also, another possibility might be to include the external files I need in the actual persistence overlay.? Can I move files into this area?? If so I will not need to do surgery on the squashfs file system. ? Thanks much for any help that can be offered. ? Todd -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.w.pollux at gmail.com Wed Jul 16 00:06:19 2008 From: s.w.pollux at gmail.com (Pollux Su) Date: Wed, 16 Jul 2008 08:06:19 +0800 Subject: [Fedora-livecd-list] Failed to find group 'core':No groups available in any repository In-Reply-To: <1216130726.4217.60.camel@aglarond.local> References: <780ddc050807142229k64292kba5dd42e93fdd1b4@mail.gmail.com> <1216130726.4217.60.camel@aglarond.local> Message-ID: <780ddc050807151706g267c8e1cg200c9f52708b3674@mail.gmail.com> Jeremy,Thank you very much! I have solved this problem following your suggest. Thanks again. On Tue, Jul 15, 2008 at 10:05 PM, Jeremy Katz wrote: > On Tue, 2008-07-15 at 13:29 +0800, Pollux Su wrote: > > I'm a newer of livecd-creater.When I am creating live cd,"Failed > > to find group 'core':No groups available in any repository" error > > message appears.Following is my steps: > > When running createrepo, you need to use the -g flag so that the group > metadata gets set up > > 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 katzj at fedoraproject.org Wed Jul 16 21:24:23 2008 From: katzj at fedoraproject.org (Jeremy Katz) Date: Wed, 16 Jul 2008 21:24:23 +0000 (UTC) Subject: [Fedora-livecd-list] tools/livecd-iso-to-disk.sh Message-ID: <20080716212423.14B64120039@lists.fedorahosted.org> tools/livecd-iso-to-disk.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 1a56c5c342875cd47f51318c5b11b6694b7fc78c Author: Jeremy Katz Date: Wed Jul 16 17:23:44 2008 -0400 Make the error message a little bit clearer (#455669) diff --git a/tools/livecd-iso-to-disk.sh b/tools/livecd-iso-to-disk.sh index b1450fe..48ae40b 100755 --- a/tools/livecd-iso-to-disk.sh +++ b/tools/livecd-iso-to-disk.sh @@ -307,7 +307,7 @@ fi if [ -n "$overlaysizemb" -a "$USBFS" = "vfat" ]; then if [ "$overlaysizemb" -gt 2047 ]; then - echo "Can't have an overlay greater than 2048MB on VFAT" + echo "Can't have an overlay of 2048MB or greater on VFAT" exitclean fi fi From s.w.pollux at gmail.com Thu Jul 17 00:22:28 2008 From: s.w.pollux at gmail.com (Pollux Su) Date: Thu, 17 Jul 2008 08:22:28 +0800 Subject: [Fedora-livecd-list] How to install the pxe patch and use it? Message-ID: <780ddc050807161722n28c61459uf9d1723b90d38655@mail.gmail.com> Hi,all guys: I found that there is a pxe patch for livecd-creator tool. http://www.redhat.com/archives/fedora-livecd-list/2008-February/msg00063.html But I have no idea about how to use this patch and how to build a pxe bootable livecd. Would someone like to help me! Thanks for your time. -------------- next part -------------- An HTML attachment was scrubbed... URL: From katzj at redhat.com Thu Jul 17 17:54:59 2008 From: katzj at redhat.com (Jeremy Katz) Date: Thu, 17 Jul 2008 13:54:59 -0400 Subject: [Fedora-livecd-list] How to install the pxe patch and use it? In-Reply-To: <780ddc050807161722n28c61459uf9d1723b90d38655@mail.gmail.com> References: <780ddc050807161722n28c61459uf9d1723b90d38655@mail.gmail.com> Message-ID: <1216317299.12841.57.camel@aglarond.local> On Thu, 2008-07-17 at 08:22 +0800, Pollux Su wrote: > I found that there is a pxe patch for livecd-creator tool. > http://www.redhat.com/archives/fedora-livecd-list/2008-February/msg00063.html > But I have no idea about how to use this patch and how to build a > pxe bootable livecd. Would someone like to help me! As far as I know, you just run it like you do with livecd-iso-to-disk and it shoves the squashfs into the initrd. But I've never actually used the script. Richard, Chris? Jeremy From rjones at redhat.com Thu Jul 17 17:51:19 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Thu, 17 Jul 2008 18:51:19 +0100 Subject: [Fedora-livecd-list] How to install the pxe patch and use it? In-Reply-To: <1216317299.12841.57.camel@aglarond.local> References: <780ddc050807161722n28c61459uf9d1723b90d38655@mail.gmail.com> <1216317299.12841.57.camel@aglarond.local> Message-ID: <20080717175119.GC17559@amd.home.annexia.org> On Thu, Jul 17, 2008 at 01:54:59PM -0400, Jeremy Katz wrote: > On Thu, 2008-07-17 at 08:22 +0800, Pollux Su wrote: > > I found that there is a pxe patch for livecd-creator tool. > > http://www.redhat.com/archives/fedora-livecd-list/2008-February/msg00063.html > > But I have no idea about how to use this patch and how to build a > > pxe bootable livecd. Would someone like to help me! > > As far as I know, you just run it like you do with livecd-iso-to-disk > and it shoves the squashfs into the initrd. Yup, basically that's right. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top From DON.RAIKES at ORACLE.COM Fri Jul 18 10:51:56 2008 From: DON.RAIKES at ORACLE.COM (DON.RAIKES at ORACLE.COM) Date: Fri, 18 Jul 2008 03:51:56 -0700 (PDT) Subject: [Fedora-livecd-list] custom spin kernel panic Message-ID: <9ae143b8-17ef-4e7e-9f75-c84fd0e48aea@default> Hello, I need some help. I am trying to create a custom fedora 9 spin, but when I burn the spin to cd, I keep getting kernel panic when I try to boot from the spin. The message I am getting before the panic is: unable to enumerate devices on usb port 2. Steps I have taken: 1. Install fedora 9 (sulphur) on a fresh system. 2. checked out spin-kickstart from the git repository. 3. Ran livecd-creator using just the fedora-live-base.ks and burned it to a cd. 4. Booted from this cd (got to the login prompt and was able to login as fedora). 5. Created my own kickstart file as follows: %include fedora-live-base.ks %packages brltty %end At present I have no need for a custom %post section so I didn't put one in. I ran livecd-creator using my kickstart file and the iso was created (about 3mb larger than the base iso image). I burned thsi image to disk and rebooted. After the isolinux delay, I get the keernel panic and message about enumerating the usb devices. As a blind user, I want to have an accessible livecd to use to help rescue my system if necessary, so I am very interested in getting this to work, and after a little tweaking, I am willing to add it to the repository for others to use. Any suggestions on how to fix the kernel panic would be appreciated. BTW: I have a 4-port kvm switch connected to the usb port of the computer and a 7-port usb hub going into the switch. I have the keyboard and braille display going into the hub. -------------- next part -------------- An HTML attachment was scrubbed... URL: From astrand at cendio.se Fri Jul 18 11:39:37 2008 From: astrand at cendio.se (=?UTF-8?Q?Peter_=C3=85strand?=) Date: Fri, 18 Jul 2008 13:39:37 +0200 (CEST) Subject: [Fedora-livecd-list] custom spin kernel panic In-Reply-To: <9ae143b8-17ef-4e7e-9f75-c84fd0e48aea@default> References: <9ae143b8-17ef-4e7e-9f75-c84fd0e48aea@default> Message-ID: On Fri, 18 Jul 2008, DON.RAIKES at ORACLE.COM wrote: > I need some help. I am trying to create a custom fedora 9 spin, but when > I burn the spin to cd, I keep getting kernel panic when I try to boot > from the spin. > > The message I am getting before the panic is: > > unable to enumerate devices on usb port 2. https://bugzilla.redhat.com/show_bug.cgi?id=446845 ? Regards, --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 --- Open Source Developers wanted - http://www.cendio.com/about-cendio/career From DON.RAIKES at ORACLE.COM Fri Jul 18 20:41:52 2008 From: DON.RAIKES at ORACLE.COM (DON.RAIKES at ORACLE.COM) Date: Fri, 18 Jul 2008 13:41:52 -0700 (PDT) Subject: [Fedora-livecd-list] livecd boot to console not x environment Message-ID: Hello, Now that I have a working livecd kickstart file based on fedora-live-base.ks, I want ot change things a bit so that my cd boots to the console not the x environment. I added skipx to my kickstart file but when the cd was recreated, it booted into the x environment again. I want the ability to go into x-windows if I want to, but normally, I will want to be working at the console. My kickstart file looks like this: %include fedora-live-base.ks skipx %package brltty %end -------------- next part -------------- An HTML attachment was scrubbed... URL: From DON.RAIKES at ORACLE.COM Fri Jul 18 23:24:51 2008 From: DON.RAIKES at ORACLE.COM (DON.RAIKES at ORACLE.COM) Date: Fri, 18 Jul 2008 16:24:51 -0700 (PDT) Subject: [Fedora-livecd-list] custom spin: %post section not being executed Message-ID: <04b0e859-4f82-4b1f-9143-1d56e231be2c@default> Hello, I am working on a custom spin of fedora 9. so far I can get the basic cd created. I have added several sections to my %post section of my custom kickstart file. For example: %post cat > /home/fedora/.exrc << EOF set ai ic ts=2 tw=80 EOF %end When the cd is created the /home/fedora/.exrc file does not exist. Do the scripts in my %post section preceed or follow those in the fedora-live-base.ks assuming that I have %include fedora-live-base.ks at the top of my kickstart file? Also, how can I add the fedora user to the sudoers list so it has sudo privilleges? -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.wood at datawranglers.com Sat Jul 19 00:22:09 2008 From: tim.wood at datawranglers.com (Tim Wood) Date: Fri, 18 Jul 2008 18:22:09 -0600 Subject: [Fedora-livecd-list] custom spin: %post section not being executed In-Reply-To: <04b0e859-4f82-4b1f-9143-1d56e231be2c@default> References: <04b0e859-4f82-4b1f-9143-1d56e231be2c@default> Message-ID: <488133B1.50000@datawranglers.com> Don, /home/fedora doesn't exist until boot. The standard way to add something to a user folder is to add it to /etc/skel (in post for instance). To add fedora user to sudoers, enable wheel in /etc/sudo (or /etc/sudoers ... away from my linux box) and then add fedora to the wheel group in /etc/groups Tim DON.RAIKES at ORACLE.COM wrote: > Hello, > > I am working on a custom spin of fedora 9. > so far I can get the basic cd created. > > I have added several sections to my %post section of my custom > kickstart file. > For example: > > %post > cat > /home/fedora/.exrc << EOF > set ai ic ts=2 tw=80 > EOF > %end > > When the cd is created the /home/fedora/.exrc file does not exist. > > Do the scripts in my %post section preceed or follow those in the > fedora-live-base.ks assuming that I have > %include fedora-live-base.ks > at the top of my kickstart file? > > Also, how can I add the fedora user to the sudoers list so it has sudo > privilleges? > ------------------------------------------------------------------------ > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list > -- _________________________________ Tim Wood, CLP, RHCT 719.338.7484 (tel) The Data Wranglers Web, Database & more since since 1994 www.datawranglers.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.wood at datawranglers.com Sat Jul 19 00:23:13 2008 From: tim.wood at datawranglers.com (Tim Wood) Date: Fri, 18 Jul 2008 18:23:13 -0600 Subject: [Fedora-livecd-list] livecd boot to console not x environment In-Reply-To: References: Message-ID: <488133F1.7060907@datawranglers.com> You need to change your init level (/etc/init.rd I believe ... someone correct me if I'm misberemembering) from 5 to 3. Tim DON.RAIKES at ORACLE.COM wrote: > Hello, > > Now that I have a working livecd kickstart file based on > fedora-live-base.ks, I want ot change things a bit so that my cd boots > to the console not the x environment. > I added skipx to my kickstart file but when the cd was recreated, it > booted into the x environment again. > > I want the ability to go into x-windows if I want to, but normally, I > will want to be working at the console. > > My kickstart file looks like this: > > %include fedora-live-base.ks > > skipx > > %package > brltty > %end > ------------------------------------------------------------------------ > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list > -- _________________________________ Tim Wood, CLP, RHCT 719.338.7484 (tel) The Data Wranglers Web, Database & more since since 1994 www.datawranglers.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From martin.x.long at jpmchase.com Sat Jul 19 04:37:13 2008 From: martin.x.long at jpmchase.com (martin.x.long at jpmchase.com) Date: Fri, 18 Jul 2008 21:37:13 -0700 Subject: [Fedora-livecd-list] How do I save and restore my overlay? In-Reply-To: <20080718160021.757C061A4EA@hormel.redhat.com> Message-ID: After I format and reinitialize my Live USB, do I have to let it run through all of the updates and reinstall my applications? Do we have the tools to pull all of that data off and restore it? Any help would be great. Thanks Martin ----------------------------------------- This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities. -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.w.pollux at gmail.com Sat Jul 19 06:37:25 2008 From: s.w.pollux at gmail.com (Pollux Su) Date: Sat, 19 Jul 2008 14:37:25 +0800 Subject: [Fedora-livecd-list] How to install the pxe patch and use it? In-Reply-To: <20080717175119.GC17559@amd.home.annexia.org> References: <780ddc050807161722n28c61459uf9d1723b90d38655@mail.gmail.com> <1216317299.12841.57.camel@aglarond.local> <20080717175119.GC17559@amd.home.annexia.org> Message-ID: <780ddc050807182337o1bc0b361p13519568f31dba99@mail.gmail.com> Hi Rich, How to install this patch? Where to download it? Sorry for this foolish question. Thank you! On Fri, Jul 18, 2008 at 1:51 AM, Richard W.M. Jones wrote: > On Thu, Jul 17, 2008 at 01:54:59PM -0400, Jeremy Katz wrote: > > On Thu, 2008-07-17 at 08:22 +0800, Pollux Su wrote: > > > I found that there is a pxe patch for livecd-creator tool. > > > > http://www.redhat.com/archives/fedora-livecd-list/2008-February/msg00063.html > > > But I have no idea about how to use this patch and how to build a > > > pxe bootable livecd. Would someone like to help me! > > > > As far as I know, you just run it like you do with livecd-iso-to-disk > > and it shoves the squashfs into the initrd. > > Yup, basically that's right. > > Rich. > > -- > Richard Jones, Emerging Technologies, Red Hat > http://et.redhat.com/~rjones > virt-top is 'top' for virtual > machines. Tiny program with many > powerful monitoring features, net stats, disk stats, logging, etc. > http://et.redhat.com/~rjones/virt-top > > -- > 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 kanarip at kanarip.com Sun Jul 20 15:27:06 2008 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Sun, 20 Jul 2008 17:27:06 +0200 Subject: [Fedora-livecd-list] Mailing list for Spins SIG Message-ID: <4883594A.4000309@kanarip.com> Hi there, there is a few new mailing lists for the Spin SIG: To watch commits to the spin-kickstarts GIT repository, subscribe to: https://fedorahosted.org/mailman/listinfo/spin-kickstarts-commits For general Fedora Spin SIG things, subscribe to: http://lists.fedoraproject.org/mailman/listinfo/fedora-spins Kind regards, Jeroen van Meeuwen -kanarip From apevec at redhat.com Sun Jul 20 19:36:45 2008 From: apevec at redhat.com (Alan Pevec) Date: Sun, 20 Jul 2008 21:36:45 +0200 Subject: [Fedora-livecd-list] How to install the pxe patch and use it? In-Reply-To: <780ddc050807182337o1bc0b361p13519568f31dba99@mail.gmail.com> References: <780ddc050807161722n28c61459uf9d1723b90d38655@mail.gmail.com> <1216317299.12841.57.camel@aglarond.local> <20080717175119.GC17559@amd.home.annexia.org> <780ddc050807182337o1bc0b361p13519568f31dba99@mail.gmail.com> Message-ID: <488393CD.5090405@redhat.com> Pollux Su wrote: > How to install this patch? Where to download it? Sorry for this > foolish question. Thank you! livecd-iso-to-pxeboot is included in livecd-tools-015 and higher From dmc.fedora at filteredperception.org Mon Jul 21 04:56:11 2008 From: dmc.fedora at filteredperception.org (Douglas McClendon) Date: Sun, 20 Jul 2008 21:56:11 -0700 Subject: [Fedora-livecd-list] How do I save and restore my overlay? In-Reply-To: References: Message-ID: <488416EB.4050009@filteredperception.org> martin.x.long at jpmchase.com wrote: > > After I format and reinitialize my Live USB, do I have to let it run > through all of the updates and reinstall my applications? > Do we have the tools to pull all of that data off and restore it? I'm not entirely sure what you mean. One thing that is possible is to copy the overlay file from one liveusb and put it on another. Though the format of the overlay file is inherently tied to the specific liveos it was originally with. I.e. you won't be able to copy an overlay file from an f9-x86 liveusb onto an f9-x64 or f10-x86 liveusb. Or even a customized f9-x86 liveusb that you created with livecd-creator/tools. From an engineering standpoint, of course anything is possible. One use case I see, is to use the persistence feature to add an entry to fstab, such that say, /mnt/data mounts to a ext3fs image located on a file on your liveusb. You can then add a user that has a home directory under there, and perhaps install applications under there. In this way, you could then copy that ext3fs image file to an f10 liveusb, and then only have to re-do the fstab and passwd modifications, such that everything now pretty much looks the same. If that doesn't help or answer you question, try to add more detail to your question. -dmc > Any help would be great. > > Thanks > > Martin > From DON.RAIKES at oracle.com Mon Jul 21 16:11:28 2008 From: DON.RAIKES at oracle.com (DON.RAIKES at oracle.com) Date: Mon, 21 Jul 2008 09:11:28 -0700 (PDT) Subject: [Fedora-livecd-list] custom spin: %post section not being executed In-Reply-To: <488133B1.50000@datawranglers.com> Message-ID: <3a09d460-328e-456b-b838-d277369aa65a@default> Thanks, I will fix my kickstart file and try again :) -----Original Message----- From: Tim Wood [mailto:tim.wood at datawranglers.com] Sent: Friday, July 18, 2008 5:22 PM To: fedora-livecd-list at redhat.com Subject: Re: [Fedora-livecd-list] custom spin: %post section not being executed Don, /home/fedora doesn't exist until boot. The standard way to add something to a user folder is to add it to /etc/skel (in post for instance). To add fedora user to sudoers, enable wheel in /etc/sudo (or /etc/sudoers ... away from my linux box) and then add fedora to the wheel group in /etc/groups Tim DON.RAIKES at ORACLE.COM wrote: Hello, I am working on a custom spin of fedora 9. so far I can get the basic cd created. I have added several sections to my %post section of my custom kickstart file. For example: %post cat > /home/fedora/.exrc << EOF set ai ic ts=2 tw=80 EOF %end When the cd is created the /home/fedora/.exrc file does not exist. Do the scripts in my %post section preceed or follow those in the fedora-live-base.ks assuming that I have %include fedora-live-base.ks at the top of my kickstart file? Also, how can I add the fedora user to the sudoers list so it has sudo privilleges? ---------------------------------------------------------------------------- -- Fedora-livecd-list mailing list Fedora-livecd-list at redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list -- _________________________________ Tim Wood, CLP, RHCT 719.338.7484 (tel) The Data Wranglers Web, Database & more since since 1994 www.datawranglers.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dhuff at redhat.com Mon Jul 21 21:26:54 2008 From: dhuff at redhat.com (David Huff) Date: Mon, 21 Jul 2008 17:26:54 -0400 Subject: [Fedora-livecd-list] re-factor the imgcreate/fs.py module edits In-Reply-To: <1216067264.4217.44.camel@aglarond.local> References: <1216067264.4217.44.camel@aglarond.local> Message-ID: <1216675616-20364-1-git-send-email-dhuff@redhat.com> Patch Edits included. Patches still require the patch "added get_partitions to kickstart.py." Also the later patch that changes creator.py and live.py to use new api, "switch internal code to use new api," is still applicable. I have redone the "added compat shims for old api" patch to implement all public methods in the old API. I am pretty sure this is the correct functionality that you were looking for however feedback is welcome. -D From dhuff at redhat.com Mon Jul 21 21:26:56 2008 From: dhuff at redhat.com (David Huff) Date: Mon, 21 Jul 2008 17:26:56 -0400 Subject: [Fedora-livecd-list] [PATCH] added compat shims in fs.py for old api In-Reply-To: <1216675616-20364-2-git-send-email-dhuff@redhat.com> References: <1216067264.4217.44.camel@aglarond.local> <1216675616-20364-1-git-send-email-dhuff@redhat.com> <1216675616-20364-2-git-send-email-dhuff@redhat.com> Message-ID: <1216675616-20364-3-git-send-email-dhuff@redhat.com> Compat shims switching over the old classes, LoopbackMount, SparseLoopbackMount, SparseExtLoopbackMount, types to sit on top of the new Disk and Mount classes. --- imgcreate/fs.py | 166 ++++++++---------------------------------------------- 1 files changed, 25 insertions(+), 141 deletions(-) diff --git a/imgcreate/fs.py b/imgcreate/fs.py index 16cbbba..6de99fd 100644 --- a/imgcreate/fs.py +++ b/imgcreate/fs.py @@ -88,32 +88,16 @@ class BindChrootMount: self.mounted = False class LoopbackMount: + """LoopbackMount compatibility layer for old API""" def __init__(self, lofile, mountdir, fstype = None): - self.lofile = lofile - self.mountdir = mountdir - self.fstype = fstype - - self.mounted = False + DiskMount.__init__(LoopbackDisk(lofile,size = 0),mountdir,fstype,rmmountdir = True) self.losetup = False - self.rmdir = False - self.loopdev = None - + def cleanup(self): - self.unmount() - self.lounsetup() + DiskMount.cleanup(self) def unmount(self): - if self.mounted: - rc = subprocess.call(["/bin/umount", self.mountdir]) - if rc == 0: - self.mounted = False - - if self.rmdir and not self.mounted: - try: - os.rmdir(self.mountdir) - except OSError, e: - pass - self.rmdir = False + DiskMount.unmount(self) def lounsetup(self): if self.losetup: @@ -143,152 +127,52 @@ class LoopbackMount: self.losetup = True def mount(self): - if self.mounted: - return - - self.loopsetup() - - if not os.path.isdir(self.mountdir): - os.makedirs(self.mountdir) - self.rmdir = True - - args = [ "/bin/mount", self.loopdev, self.mountdir ] - if self.fstype: - args.extend(["-t", self.fstype]) - - rc = subprocess.call(args) - if rc != 0: - raise MountError("Failed to mount '%s' to '%s'" % - (self.loopdev, self.mountdir)) - - self.mounted = True + DiskMount.mount(self) class SparseLoopbackMount(LoopbackMount): + """LoopbackMount compatibility layer for old API""" def __init__(self, lofile, mountdir, size, fstype = None): - LoopbackMount.__init__(self, lofile, mountdir, fstype) - self.size = size + DiskMount.__init__(SparseLoopbackDisk(lofile,size),mountdir,fstype,rmmountdir = True) def expand(self, create = False, size = None): - flags = os.O_WRONLY - if create: - flags |= os.O_CREAT - makedirs(os.path.dirname(self.lofile)) - - if size is None: - size = self.size - - fd = os.open(self.lofile, flags) - - os.lseek(fd, size, 0) - os.write(fd, '\x00') - os.close(fd) + SparseLoopbackDisk.expand(self, create, size) def truncate(self, size = None): - if size is None: - size = self.size - fd = os.open(self.lofile, os.O_WRONLY) - os.ftruncate(fd, size) - os.close(fd) + SparseLoopbackDisk.truncate(self, size) def create(self): - self.expand(create = True) + SparseLoopbackDisk.create(self) class SparseExtLoopbackMount(SparseLoopbackMount): + """LoopbackMount compatibility layer for old API""" def __init__(self, lofile, mountdir, size, fstype, blocksize, fslabel): - SparseLoopbackMount.__init__(self, lofile, mountdir, size, fstype) - self.blocksize = blocksize - self.fslabel = fslabel + ExtDiskMount.__init__(SparseLoopbackDisk(lofile,size), mountdir, fstype, blocksize, fslabel, rmmountdir = True) + def __format_filesystem(self): - rc = subprocess.call(["/sbin/mkfs." + self.fstype, - "-F", "-L", self.fslabel, - "-m", "1", "-b", str(self.blocksize), - self.lofile, - str(self.size / self.blocksize)]) - if rc != 0: - raise MountError("Error creating %s filesystem" % (self.fstype,)) - subprocess.call(["/sbin/tune2fs", "-c0", "-i0", "-Odir_index", - "-ouser_xattr,acl", self.lofile]) + ExtDiskMount.__format_filesystem(self) def create(self): - SparseLoopbackMount.create(self) - self.__format_filesystem() + SparseLoopbackDisk.create(self) def resize(self, size = None): - current_size = os.stat(self.lofile)[stat.ST_SIZE] - - if size is None: - size = self.size - - if size == current_size: - return - - if size > current_size: - self.expand(size) - - self.__fsck() - - resize2fs(self.lofile, size) - - if size < current_size: - self.truncate(size) - return size + ExtDiskMount.__resize_filesystem(self, size) def mount(self): - if not os.path.isfile(self.lofile): - self.create() - else: - self.resize() - return SparseLoopbackMount.mount(self) - + ExtDiskMount.mount(self) + def __fsck(self): - subprocess.call(["/sbin/e2fsck", "-f", "-y", self.lofile]) + ExtDiskMount.__fsck(self) def __get_size_from_filesystem(self): - def parse_field(output, field): - for line in output.split("\n"): - if line.startswith(field + ":"): - return line[len(field) + 1:].strip() - - raise KeyError("Failed to find field '%s' in output" % field) - - dev_null = os.open("/dev/null", os.O_WRONLY) - try: - out = subprocess.Popen(['/sbin/dumpe2fs', '-h', self.lofile], - stdout = subprocess.PIPE, - stderr = dev_null).communicate()[0] - finally: - os.close(dev_null) - - return int(parse_field(out, "Block count")) * self.blocksize - + ExtDiskMount.__get_size_from_filesystem(self) + def __resize_to_minimal(self): - self.__fsck() - - # - # Use a binary search to find the minimal size - # we can resize the image to - # - bot = 0 - top = self.__get_size_from_filesystem() - while top != (bot + 1): - t = bot + ((top - bot) / 2) - - if not resize2fs(self.lofile, t): - top = t - else: - bot = t - return top - + ExtDiskMount.__resize_to_minimal(self) + def resparse(self, size = None): - self.cleanup() + ExtDiskMount.resparse(self, size) - minsize = self.__resize_to_minimal() - - self.truncate(minsize) - self.resize(size) - return minsize - class Disk: """ With the new disk API the image being produced can be partitioned into -- 1.5.4.1 From dhuff at redhat.com Mon Jul 21 21:26:55 2008 From: dhuff at redhat.com (David Huff) Date: Mon, 21 Jul 2008 17:26:55 -0400 Subject: [Fedora-livecd-list] [PATCH] re-factor imgcreate/fs.py module In-Reply-To: <1216675616-20364-1-git-send-email-dhuff@redhat.com> References: <1216067264.4217.44.camel@aglarond.local> <1216675616-20364-1-git-send-email-dhuff@redhat.com> Message-ID: <1216675616-20364-2-git-send-email-dhuff@redhat.com> From: Daniel P. Berrange Most of the change here involves re-factoring the imgcreate/fs.py module. The SparseExtLoopbackMount, SparseLoopbackMount, LoopbackMount classes all have the built-in limitation that the image being produced corresponds to a single filesystem / loop mount. With the disk creator, the image being produced can be partitioned into multiple chunks, with many filesystems. Furthermore, not all of them require loopback mounts, as the partitions themselves are already visible via /dev/mapper/ So this patch separates the roles. There are now classes which deal with accessing / creating disks: Disk - generic base for disks RawDisk - a disk backed by a block device LoopbackDisk - a disk backed by a file SparseLoopbackDisk - a disk backed by a sparse file The 'create' method must make the disk visible as a block device - eg by calling losetup. For RawDisk, this is obviously a no-op. The 'cleanup' method must undo the 'create' operation. There are then classes which deal with mounting things: Mount - generic base for mounts DiskMount - able to mount a Disk object ExtDiskMount - able to format/resize ext3 filesystems when mounting Patch modified by David Huff Also fixed comments to use the standard pydoc """ format. --- imgcreate/fs.py | 346 +++++++++++++++++++++++++++++++++++++++++++++++++++---- 1 files changed, 322 insertions(+), 24 deletions(-) diff --git a/imgcreate/fs.py b/imgcreate/fs.py index 98c0db4..16cbbba 100644 --- a/imgcreate/fs.py +++ b/imgcreate/fs.py @@ -24,6 +24,7 @@ import stat import subprocess import random import string +import logging from imgcreate.errors import * @@ -288,6 +289,303 @@ class SparseExtLoopbackMount(SparseLoopbackMount): self.resize(size) return minsize +class Disk: + """ + With the new disk API the image being produced can be partitioned into + multiple chunks, with many filesystems. Furthermore, not all of them + require loopback mounts, as the partitions themselves are already + visible via /dev/mapper/ + + There are now classes which deal with accessing / creating disks: + + Disk - generic base for disks + RawDisk - a disk backed by a block device + LoopbackDisk - a disk backed by a file + SparseLoopbackDisk - a disk backed by a sparse file + + The 'create' method must make the disk visible as a block device - eg + by calling losetup. For RawDisk, this is obviously a no-op. The 'cleanup' + method must undo the 'create' operation. + + There are then classes which deal with mounting things: + + Mount - generic base for mounts + DiskMount - able to mount a Disk object + ExtDiskMount - able to format/resize ext3 filesystems when mounting + """ + def __init__(self, size, device = None): + self._device = device + self._size = size + + def create(self): + pass + + def cleanup(self): + pass + + def get_device(self): + return self._device + def set_device(self, path): + self._device = path + device = property(get_device, set_device) + + def get_size(self): + return self._size + size = property(get_size) + + +class RawDisk(Disk): + def __init__(self, size, device): + Disk.__init__(self, size, device) + + def fixed(self): + return True + + def exists(self): + return True + +class LoopbackDisk(Disk): + def __init__(self, lofile, size): + Disk.__init__(self, size) + self.lofile = lofile + + def fixed(self): + return False + + def exists(self): + return os.path.exists(self.lofile) + + def create(self): + if self.device is not None: + return + + losetupProc = subprocess.Popen(["/sbin/losetup", "-f"], + stdout=subprocess.PIPE) + losetupOutput = losetupProc.communicate()[0] + + if losetupProc.returncode: + raise MountError("Failed to allocate loop device for '%s'" % + self.lofile) + + device = losetupOutput.split()[0] + + logging.debug("Losetup add %s mapping to %s" % (device, self.lofile)) + rc = subprocess.call(["/sbin/losetup", device, self.lofile]) + if rc != 0: + raise MountError("Failed to allocate loop device for '%s'" % + self.lofile) + self.device = device + + def cleanup(self): + if self.device is None: + return + logging.debug("Losetup remove %s" % self.device) + rc = subprocess.call(["/sbin/losetup", "-d", self.device]) + self.device = None + + + +class SparseLoopbackDisk(LoopbackDisk): + def __init__(self, lofile, size): + LoopbackDisk.__init__(self, lofile, size) + + def expand(self, create = False, size = None): + flags = os.O_WRONLY + if create: + flags |= os.O_CREAT + makedirs(os.path.dirname(self.lofile)) + + if size is None: + size = self.size + + logging.debug("Extending sparse file %s to %d" % (self.lofile, size)) + fd = os.open(self.lofile, flags) + + os.lseek(fd, size, 0) + os.write(fd, '\x00') + os.close(fd) + + def truncate(self, size = None): + if size is None: + size = self.size + + logging.debug("Truncating sparse file %s to %d" % (self.lofile, size)) + fd = os.open(self.lofile, os.O_WRONLY) + os.ftruncate(fd, size) + os.close(fd) + + def create(self): + self.expand(create = True) + LoopbackDisk.create(self) + +class Mount: + def __init__(self, mountdir): + self.mountdir = mountdir + + def cleanup(self): + self.unmount() + + def mount(self): + pass + + def unmount(self): + pass + +class DiskMount(Mount): + def __init__(self, disk, mountdir, fstype = None, rmmountdir = True): + Mount.__init__(self, mountdir) + + self.disk = disk + self.fstype = fstype + self.rmmountdir = rmmountdir + + self.mounted = False + self.rmdir = False + + def cleanup(self): + Mount.cleanup(self) + self.disk.cleanup() + + def unmount(self): + if self.mounted: + logging.debug("Unmounting directory %s" % self.mountdir) + rc = subprocess.call(["/bin/umount", self.mountdir]) + if rc == 0: + self.mounted = False + + if self.rmdir and not self.mounted: + try: + os.rmdir(self.mountdir) + except OSError, e: + pass + self.rmdir = False + + + def __create(self): + self.disk.create() + + + def mount(self): + if self.mounted: + return + + if not os.path.isdir(self.mountdir): + logging.debug("Creating mount point %s" % self.mountdir) + os.makedirs(self.mountdir) + self.rmdir = self.rmmountdir + + self.__create() + + logging.debug("Mounting %s at %s" % (self.disk.device, self.mountdir)) + args = [ "/bin/mount", self.disk.device, self.mountdir ] + if self.fstype: + args.extend(["-t", self.fstype]) + + rc = subprocess.call(args) + if rc != 0: + raise MountError("Failed to mount '%s' to '%s'" % + (self.disk.device, self.mountdir)) + + self.mounted = True + +class ExtDiskMount(DiskMount): + def __init__(self, disk, mountdir, fstype, blocksize, fslabel, rmmountdir=True): + DiskMount.__init__(self, disk, mountdir, fstype, rmmountdir) + self.blocksize = blocksize + self.fslabel = fslabel + + def __format_filesystem(self): + logging.debug("Formating %s filesystem on %s" % (self.fstype, self.disk.device)) + rc = subprocess.call(["/sbin/mkfs." + self.fstype, + "-F", "-L", self.fslabel, + "-m", "1", "-b", str(self.blocksize), + self.disk.device]) + # str(self.disk.size / self.blocksize)]) + if rc != 0: + raise MountError("Error creating %s filesystem" % (self.fstype,)) + logging.debug("Tuning filesystem on %s" % self.disk.device) + subprocess.call(["/sbin/tune2fs", "-c0", "-i0", "-Odir_index", + "-ouser_xattr,acl", self.disk.device]) + + def __resize_filesystem(self, size = None): + current_size = os.stat(self.disk.lofile)[stat.ST_SIZE] + + if size is None: + size = self.size + + if size == current_size: + return + + if size > current_size: + self.expand(size) + + self.__fsck() + + resize2fs(self.disk.lofile, size) + return size + + def __create(self): + resize = False + if not self.disk.fixed() and self.disk.exists(): + resize = True + + self.disk.create() + + if resize: + self.__resize_filesystem() + else: + self.__format_filesystem() + + def mount(self): + self.__create() + DiskMount.mount(self) + + def __fsck(self): + logging.debug("Checking filesystem %s" % self.disk.lofile) + subprocess.call(["/sbin/e2fsck", "-f", "-y", self.disk.lofile]) + + def __get_size_from_filesystem(self): + def parse_field(output, field): + for line in output.split("\n"): + if line.startswith(field + ":"): + return line[len(field) + 1:].strip() + + raise KeyError("Failed to find field '%s' in output" % field) + + dev_null = os.open("/dev/null", os.O_WRONLY) + try: + out = subprocess.Popen(['/sbin/dumpe2fs', '-h', self.disk.lofile], + stdout = subprocess.PIPE, + stderr = dev_null).communicate()[0] + finally: + os.close(dev_null) + + return int(parse_field(out, "Block count")) * self.blocksize + + def __resize_to_minimal(self): + self.__fsck() + + # + # Use a binary search to find the minimal size + # we can resize the image to + # + bot = 0 + top = self.__get_size_from_filesystem() + while top != (bot + 1): + t = bot + ((top - bot) / 2) + + if not resize2fs(self.disk.lofile, t): + top = t + else: + bot = t + return top + + def resparse(self, size = None): + self.cleanup() + minsize = self.__resize_to_minimal() + self.disk.truncate(minsize) + return minsize + class DeviceMapperSnapshot(object): def __init__(self, imgloop, cowloop): self.imgloop = imgloop @@ -306,8 +604,8 @@ class DeviceMapperSnapshot(object): if self.__created: return - self.imgloop.loopsetup() - self.cowloop.loopsetup() + self.imgloop.create() + self.cowloop.create() self.__name = "imgcreate-%d-%d" % (os.getpid(), random.randint(0, 2**16)) @@ -315,8 +613,8 @@ class DeviceMapperSnapshot(object): size = os.stat(self.imgloop.lofile)[stat.ST_SIZE] table = "0 %d snapshot %s %s p 8" % (size / 512, - self.imgloop.loopdev, - self.cowloop.loopdev) + self.imgloop.device, + self.cowloop.device) args = ["/sbin/dmsetup", "create", self.__name, "--table", table] if subprocess.call(args) != 0: @@ -365,32 +663,31 @@ class DeviceMapperSnapshot(object): except ValueError: raise SnapshotError("Failed to parse dmsetup status: " + out) -# -# Builds a copy-on-write image which can be used to -# create a device-mapper snapshot of an image where -# the image's filesystem is as small as possible -# -# The steps taken are: -# 1) Create a sparse COW -# 2) Loopback mount the image and the COW -# 3) Create a device-mapper snapshot of the image -# using the COW -# 4) Resize the filesystem to the minimal size -# 5) Determine the amount of space used in the COW -# 6) Restroy the device-mapper snapshot -# 7) Truncate the COW, removing unused space -# 8) Create a squashfs of the COW -# def create_image_minimizer(path, image, minimal_size): - imgloop = LoopbackMount(image, "None") + """ + Builds a copy-on-write image which can be used to + create a device-mapper snapshot of an image where + the image's filesystem is as small as possible + + The steps taken are: + 1) Create a sparse COW + 2) Loopback mount the image and the COW + 3) Create a device-mapper snapshot of the image + using the COW + 4) Resize the filesystem to the minimal size + 5) Determine the amount of space used in the COW + 6) Restroy the device-mapper snapshot + 7) Truncate the COW, removing unused space + 8) Create a squashfs of the COW + """ + imgloop = LoopbackDisk(image, None) # Passing bogus size - doesn't matter - cowloop = SparseLoopbackMount(os.path.join(os.path.dirname(path), "osmin"), - None, 64L * 1024L * 1024L) + cowloop = SparseLoopbackDisk(os.path.join(os.path.dirname(path), "osmin"), + 64L * 1024L * 1024L) snapshot = DeviceMapperSnapshot(imgloop, cowloop) try: - cowloop.create() snapshot.create() resize2fs(snapshot.path, minimal_size) @@ -404,3 +701,4 @@ def create_image_minimizer(path, image, minimal_size): mksquashfs(cowloop.lofile, path) os.unlink(cowloop.lofile) + -- 1.5.4.1 From apevec at redhat.com Tue Jul 22 03:20:10 2008 From: apevec at redhat.com (Alan Pevec) Date: Tue, 22 Jul 2008 05:20:10 +0200 Subject: [Fedora-livecd-list] [PATCH] fix SelinuxConfig firewall side-effect Message-ID: <1216696810-16413-1-git-send-email-apevec@redhat.com> firewall --disabled is ignored: SelinuxConfig is running lokkit with SEL options only and --enabled (for firewall) is the default patch for livecd-tools-017.1-1.fc9 i.e. f9-branch in livecd git Signed-off-by: Alan Pevec --- imgcreate/creator.py | 3 +-- imgcreate/kickstart.py | 9 ++++++--- 2 files changed, 7 insertions(+), 5 deletions(-) diff --git a/imgcreate/creator.py b/imgcreate/creator.py index 4c22ac6..d799f0f 100644 --- a/imgcreate/creator.py +++ b/imgcreate/creator.py @@ -702,13 +702,12 @@ class ImageCreator(object): kickstart.KeyboardConfig(self._instroot).apply(ksh.keyboard) kickstart.TimezoneConfig(self._instroot).apply(ksh.timezone) kickstart.AuthConfig(self._instroot).apply(ksh.authconfig) - kickstart.FirewallConfig(self._instroot).apply(ksh.firewall) kickstart.SelinuxConfig(self._instroot).apply(ksh.selinux) + kickstart.FirewallConfig(self._instroot).apply(ksh.firewall) kickstart.RootPasswordConfig(self._instroot).apply(ksh.rootpw) kickstart.ServicesConfig(self._instroot).apply(ksh.services) kickstart.XConfig(self._instroot).apply(ksh.xconfig) kickstart.NetworkConfig(self._instroot).apply(ksh.network) - kickstart.SelinuxConfig(self._instroot).apply(ksh.selinux) self._create_bootconfig() diff --git a/imgcreate/kickstart.py b/imgcreate/kickstart.py index 2331626..8cddef0 100644 --- a/imgcreate/kickstart.py +++ b/imgcreate/kickstart.py @@ -169,12 +169,15 @@ class FirewallConfig(KickstartConfig): # # FIXME: should handle the rest of the options # - if not ksfirewall.enabled: - return if not os.path.exists(self.path("/usr/sbin/lokkit")): return + if ksfirewall.enabled: + status = "--enabled" + else: + status = "--disabled" + self.call(["/usr/sbin/lokkit", - "-f", "--quiet", "--nostart", "--enabled"]) + "-f", "--quiet", "--nostart", status]) class RootPasswordConfig(KickstartConfig): """A class to apply a kickstart root password configuration to a system.""" -- 1.5.5.1 From svahl at fedoraproject.org Tue Jul 22 07:35:15 2008 From: svahl at fedoraproject.org (Sebastian Vahl) Date: Tue, 22 Jul 2008 07:35:15 +0000 (UTC) Subject: [Fedora-livecd-list] config/livecd-fedora-kde.ks Message-ID: <20080722073515.9657B120027@lists.fedorahosted.org> config/livecd-fedora-kde.ks | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) New commits: commit 8a602fd81473a46e55e27ab21077bbc613bf8769 Author: Sebastian Vahl Date: Tue Jul 22 09:34:29 2008 +0200 save space: remove kftpgrabber, filelight, pavucontrol diff --git a/config/livecd-fedora-kde.ks b/config/livecd-fedora-kde.ks index eb8c119..97f0e00 100644 --- a/config/livecd-fedora-kde.ks +++ b/config/livecd-fedora-kde.ks @@ -14,7 +14,7 @@ -scribus -ktorrent #-kdegames -#-kftpgrabber* +-kftpgrabber* -kaffeine* -koffice-* @@ -24,13 +24,13 @@ #koffice-kpresenter #koffice-filters k3b -filelight +#filelight # twinkle (~10 megs) #twinkle # some extras fuse -pavucontrol +#pavucontrol # additional fonts @fonts From kanarip at kanarip.com Tue Jul 22 07:48:42 2008 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Tue, 22 Jul 2008 09:48:42 +0200 Subject: [Fedora-livecd-list] config/livecd-fedora-kde.ks In-Reply-To: <20080722073515.9657B120027@lists.fedorahosted.org> References: <20080722073515.9657B120027@lists.fedorahosted.org> Message-ID: <488590DA.5050301@kanarip.com> Sebastian Vahl wrote: > config/livecd-fedora-kde.ks | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > Could these changes be made in the spin-kickstarts GIT repository please? Kind regards, Jeroen van Meeuwen -kanarip From ml at deadbabylon.de Tue Jul 22 08:38:43 2008 From: ml at deadbabylon.de (Sebastian Vahl) Date: Tue, 22 Jul 2008 10:38:43 +0200 Subject: [Fedora-livecd-list] config/livecd-fedora-kde.ks In-Reply-To: <488590DA.5050301@kanarip.com> References: <20080722073515.9657B120027@lists.fedorahosted.org> <488590DA.5050301@kanarip.com> Message-ID: <200807221038.50078.ml@deadbabylon.de> Am Di 22.Juli 2008 schrieb Jeroen van Meeuwen: > Sebastian Vahl wrote: > > config/livecd-fedora-kde.ks | 6 +++--- > > 1 file changed, 3 insertions(+), 3 deletions(-) > > Could these changes be made in the spin-kickstarts GIT repository please? How do I get access to this GIT? Sorry for the question but I've not followed the discussions very closely because of short time atm. Sebastian -------------- 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 ml at deadbabylon.de Tue Jul 22 11:02:29 2008 From: ml at deadbabylon.de (Sebastian Vahl) Date: Tue, 22 Jul 2008 13:02:29 +0200 Subject: [Fedora-livecd-list] F10 Alpha: livecd-fedora-base-desktop.ks vs. fedora-live-base.ks Message-ID: <200807221302.34434.ml@deadbabylon.de> Short and simple question: Which kickstart will be the base for the alpha of the KDE live images, livecd-fedora-base-desktop.ks [1] from livecd GIT or fedora-live-base.ks [2] from spin-kickstarts GIT? The diff between them is quite huge (eg. one still has gparted and the other one already includes firstaidkit) and I don't want to rely on the wrong one. Sebastian [1] http://git.fedoraproject.org/git/?p=hosted/livecd;a=blob;f=config/livecd-fedora-base-desktop.ks;h=602e9f6f2d22f135ad9b1f87242ec62c5a07ece3;hb=402a24145eb7f4d58e3809c1e594602b3a21d6a1 [2] http://git.fedorahosted.org/git/?p=spin-kickstarts.git;a=blob;f=fedora-live-base.ks;h=d62b85e264a31180cc0d75487b6657d7cb8c2e74;hb=0c722ff3c4eebb069fcaaab6e5d83d7afb45004d -------------- 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 Jul 22 15:21:29 2008 From: katzj at redhat.com (Jeremy Katz) Date: Tue, 22 Jul 2008 11:21:29 -0400 Subject: [Fedora-livecd-list] F10 Alpha: livecd-fedora-base-desktop.ks vs. fedora-live-base.ks In-Reply-To: <200807221302.34434.ml@deadbabylon.de> References: <200807221302.34434.ml@deadbabylon.de> Message-ID: <1216740089.25951.22.camel@aglarond.local> On Tue, 2008-07-22 at 13:02 +0200, Sebastian Vahl wrote: > Short and simple question: Which kickstart will be the base for the alpha of > the KDE live images, livecd-fedora-base-desktop.ks [1] from livecd GIT or > fedora-live-base.ks [2] from spin-kickstarts GIT? > The diff between them is quite huge (eg. one still has gparted and the other > one already includes firstaidkit) and I don't want to rely on the wrong one. At the moment, the official spins are still being done with the configs from the livecd-tools git repo. Jeroen -- we need to talk about what the long-term answer is because having _3_ copies of the files[1] just isn't really scalable :-) But I'm a bit hosed schedule-wise this week, so maybe next week once the alpha is baked? Jeremy [1] livecd-tools repo, spins repo and then also in fedora-release From katzj at redhat.com Tue Jul 22 15:24:18 2008 From: katzj at redhat.com (Jeremy Katz) Date: Tue, 22 Jul 2008 11:24:18 -0400 Subject: [Fedora-livecd-list] [PATCH] fix SelinuxConfig firewall side-effect In-Reply-To: <1216696810-16413-1-git-send-email-apevec@redhat.com> References: <1216696810-16413-1-git-send-email-apevec@redhat.com> Message-ID: <1216740258.25951.23.camel@aglarond.local> On Tue, 2008-07-22 at 05:20 +0200, Alan Pevec wrote: > firewall --disabled is ignored: > SelinuxConfig is running lokkit with SEL options only > and --enabled (for firewall) is the default thanks, applied Jeremy From katzj at fedoraproject.org Tue Jul 22 15:24:45 2008 From: katzj at fedoraproject.org (Jeremy Katz) Date: Tue, 22 Jul 2008 15:24:45 +0000 (UTC) Subject: [Fedora-livecd-list] imgcreate/creator.py imgcreate/kickstart.py Message-ID: <20080722152445.F3BF4120027@lists.fedorahosted.org> imgcreate/creator.py | 3 +-- imgcreate/kickstart.py | 9 ++++++--- 2 files changed, 7 insertions(+), 5 deletions(-) New commits: commit d8c25944dde2de95a38c08fbb8e890295290ab21 Author: Alan Pevec Date: Tue Jul 22 05:20:10 2008 +0200 fix SelinuxConfig firewall side-effect firewall --disabled is ignored: SelinuxConfig is running lokkit with SEL options only and --enabled (for firewall) is the default patch for livecd-tools-017.1-1.fc9 i.e. f9-branch in livecd git Signed-off-by: Alan Pevec diff --git a/imgcreate/creator.py b/imgcreate/creator.py index c9ed60c..e61f034 100644 --- a/imgcreate/creator.py +++ b/imgcreate/creator.py @@ -703,13 +703,12 @@ class ImageCreator(object): kickstart.KeyboardConfig(self._instroot).apply(ksh.keyboard) kickstart.TimezoneConfig(self._instroot).apply(ksh.timezone) kickstart.AuthConfig(self._instroot).apply(ksh.authconfig) - kickstart.FirewallConfig(self._instroot).apply(ksh.firewall) kickstart.SelinuxConfig(self._instroot).apply(ksh.selinux) + kickstart.FirewallConfig(self._instroot).apply(ksh.firewall) kickstart.RootPasswordConfig(self._instroot).apply(ksh.rootpw) kickstart.ServicesConfig(self._instroot).apply(ksh.services) kickstart.XConfig(self._instroot).apply(ksh.xconfig) kickstart.NetworkConfig(self._instroot).apply(ksh.network) - kickstart.SelinuxConfig(self._instroot).apply(ksh.selinux) self._create_bootconfig() diff --git a/imgcreate/kickstart.py b/imgcreate/kickstart.py index 0f797b8..451b133 100644 --- a/imgcreate/kickstart.py +++ b/imgcreate/kickstart.py @@ -171,12 +171,15 @@ class FirewallConfig(KickstartConfig): # # FIXME: should handle the rest of the options # - if not ksfirewall.enabled: - return if not os.path.exists(self.path("/usr/sbin/lokkit")): return + if ksfirewall.enabled: + status = "--enabled" + else: + status = "--disabled" + self.call(["/usr/sbin/lokkit", - "-f", "--quiet", "--nostart", "--enabled"]) + "-f", "--quiet", "--nostart", status]) class RootPasswordConfig(KickstartConfig): """A class to apply a kickstart root password configuration to a system.""" From anthony_j_coco at yahoo.com Tue Jul 22 16:02:13 2008 From: anthony_j_coco at yahoo.com (Coco Computers & Consulting) Date: Tue, 22 Jul 2008 09:02:13 -0700 (PDT) Subject: [Fedora-livecd-list] local hard disk space? Message-ID: <258629.27582.qm@web52604.mail.re2.yahoo.com> When I boot with Centos 5.1 Live CD, a df command shows the root filesystem / is mounted to /dev/mapper/livecd-rw and shows a total of about 4GB with 50% available. Is this disk space from my local hard drive? How is it carved out? My local hard drive is installed with a Windows XP system. Does LiveCD simply create a 4GB file on the local hard drive for its own use? --thanks, --Tony C. Coco Computers & Consulting http://coconets.homeip.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From martin.x.long at jpmchase.com Tue Jul 22 23:56:12 2008 From: martin.x.long at jpmchase.com (martin.x.long at jpmchase.com) Date: Tue, 22 Jul 2008 16:56:12 -0700 Subject: [Fedora-livecd-list] Re: How do I save and restore my overlay? In-Reply-To: <20080722152501.499FC61AC87@hormel.redhat.com> Message-ID: Douglas McClendon If that doesn't help or answer you question, try to add more detail to >your question. Douglas - Thanks for the reply. I use the live usb tools to create my live USB stick with a 2047 MB overlay. I boot from it and let it run updates. I reboot the LiveUSB to make sure it still boots, then I shut down. I boot a system on a copy of Fedora 9 on the hard drive and plug in my Live USB so I can see the files on my USB stick. I see 2 folders: LiveOS and syslinux in the LiveOS folder I see three files: osmin.img overlay-FEDORA-3099-53F2 and squashfs.img ====== assumptions squashfs.img looks to be the size of the live iso overlay-FEDORA-3099-53F2 looks to be the size of the overlay and has overlay in the file name osmin.img is only 8k probably a boot strap, I'm not sure. ======= I'm sorry, I can't find anything on the LiveUSB file structure on the WiKi. I've signed on as a writer for the Fedore project so I'd like to write it once I figure out what it is. I was hoping that I could backup the overlay file and the syslinux folder from my completely updated LiveUSB stick and restore them to a newly built LiveUSB from my backup. > I'm not entirely sure what you mean. One thing that is possible is to > copy the overlay file from one liveusb and put it on another. Though > the format of the overlay file is inherently tied to the specific liveos > it was originally with. I.e. you won't be able to copy an overlay file > from an f9-x86 liveusb onto an f9-x64 or f10-x86 liveusb. Or even a > customized f9-x86 liveusb that you created with livecd-creator/tools. Nothing fancy - The same USB stick, built in the same way with the same iso and the same overlay size. The overlay file name changes. I've given the updated file (the overlay that was part of the LiveUSB for all of the updates) the same name as the new file that is created and left the updated file with its original name. I've overwritten just the overlay itself and the overlay and every combinarion of the osmin.img and squashfs.img files. I could never get it to boot. The boot starts but then hangs. Ideally, it would be great to specify the overlay and the syslinyx folder that goes with that overlay in the command line to build the LiveUSB. At this point I would be thrilled if I could get a set of manual steps together to have an updated system without going through the update process. I loose a day each time. > From an engineering standpoint, of course anything is possible. One > use case I see, is to use the persistence feature to add an entry to > fstab, such that say, /mnt/data mounts to a ext3fs image located on a > file on your liveusb. You can then add a user that has a home directory > under there, and perhaps install applications under there. In this way, > you could then copy that ext3fs image file to an f10 liveusb, and then > only have to re-do the fstab and passwd modifications, such that > everything now pretty much looks the same. Your suggestion of building a file structure that would transcend different releases would be awesome but alas I need to crawl before I can run. Any help would be greatly appreciated. Thanks again Martin ----------------------------------------- This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmc.fedora at filteredperception.org Wed Jul 23 00:08:34 2008 From: dmc.fedora at filteredperception.org (Douglas McClendon) Date: Tue, 22 Jul 2008 17:08:34 -0700 Subject: [Fedora-livecd-list] local hard disk space? In-Reply-To: <258629.27582.qm@web52604.mail.re2.yahoo.com> References: <258629.27582.qm@web52604.mail.re2.yahoo.com> Message-ID: <48867682.6030201@filteredperception.org> Coco Computers & Consulting wrote: > When I boot with Centos 5.1 Live CD, a df command shows the root > filesystem / is mounted to /dev/mapper/livecd-rw and shows a total of > about 4GB with 50% available. Is this disk space from my local hard > drive? How is it carved out? My local hard drive is installed with a > Windows XP system. Does LiveCD simply create a 4GB file on the local > hard drive for its own use? No, the 4G is basically imaginary. Whatever amount it starts out as used, say 2.1G, is actually compressed data on the cdrom, i.e. about 675MB. Once booted and files/blocks are written, they are written to ram (or with liveusb persistence, flash/disk). The only reason for the arbitrary 4G number, as opposed to say, 1000G, is that the formatting data of a larger filesystem would take up a little bit of extra space, even compressed. Theoretically if you had a 16GB ram system, you'd be a bit unhappy that an artificial limitation of 4GB of writable blocks is being used, when you have more ram than that to burn. Long ago I submitted a patch such that the devicemapper device would have a size greater than 4GB, but the filesystem still be formatted to 4GB. With that kind of patch, such a user of a 16GB filesystem could resize2fs the filesystem larger post boot, and not be limited. At the time however, squashfs was not as efficient as it currently is with sparse files, and such a larger device would also have resulted in more actual data space taken up on the cdrom (and also signifigantly increasing the time to author/master the livecd originally). Now however squashfs natively handles sparse files, and won't waste any actual space on even a terabyte of zeros. That was probably a longer answer than you were looking for. Executive summary- the 4G is purely imaginary and means nothing. The fedora livecd like most livecds, by default, does not touch your system disk at all. -dmc > > --thanks, > --Tony C. > > Coco Computers & Consulting > http://coconets.homeip.net > > > > ------------------------------------------------------------------------ > > -- > 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 Jul 23 00:17:27 2008 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Wed, 23 Jul 2008 02:17:27 +0200 Subject: [Fedora-livecd-list] config/livecd-fedora-kde.ks In-Reply-To: <200807221038.50078.ml@deadbabylon.de> References: <20080722073515.9657B120027@lists.fedorahosted.org> <488590DA.5050301@kanarip.com> <200807221038.50078.ml@deadbabylon.de> Message-ID: <48867897.5090902@kanarip.com> Sebastian Vahl wrote: > Am Di 22.Juli 2008 schrieb Jeroen van Meeuwen: >> Sebastian Vahl wrote: >>> config/livecd-fedora-kde.ks | 6 +++--- >>> 1 file changed, 3 insertions(+), 3 deletions(-) >> Could these changes be made in the spin-kickstarts GIT repository please? > > How do I get access to this GIT? > I see you have requested access, and so I have approved. > Sorry for the question but I've not followed the discussions very closely > because of short time atm. > We have a mailing list up and running on lists.fedoraproject.org now: http://admin.fedoraproject.org/mailman/listinfo/fedora-spins Kind regards, Jeroen van Meeuwen -kanarip From dmc.fedora at filteredperception.org Wed Jul 23 00:23:15 2008 From: dmc.fedora at filteredperception.org (Douglas McClendon) Date: Tue, 22 Jul 2008 17:23:15 -0700 Subject: [Fedora-livecd-list] local hard disk space? In-Reply-To: <48867682.6030201@filteredperception.org> References: <258629.27582.qm@web52604.mail.re2.yahoo.com> <48867682.6030201@filteredperception.org> Message-ID: <488679F3.1060400@filteredperception.org> Douglas McClendon wrote: > Coco Computers & Consulting wrote: >> When I boot with Centos 5.1 Live CD, a df command shows the root >> filesystem / is mounted to /dev/mapper/livecd-rw and shows a total of >> about 4GB with 50% available. ... Long ago I > submitted a patch such that the devicemapper device would have > a size greater than 4GB, but the filesystem still be formatted to 4GB. > With that kind of patch, such a user of a 16GB filesystem could > resize2fs the filesystem larger post boot, and not be limited. ... And I'm also pretty sure that the same thing can be accomplished without any patch anyway... (using a linear device mapper device that is the addition of the 4G sparse file, and a device mapper 'zero' device of arbitary length...) I really love device mapper. -dmc From svahl at fedoraproject.org Wed Jul 23 09:15:12 2008 From: svahl at fedoraproject.org (Sebastian Vahl) Date: Wed, 23 Jul 2008 09:15:12 +0000 (UTC) Subject: [Fedora-livecd-list] config/livecd-fedora-kde.ks Message-ID: <20080723091512.39A1D120027@lists.fedorahosted.org> config/livecd-fedora-kde.ks | 36 +++++++++++++++++++++++------------- 1 file changed, 23 insertions(+), 13 deletions(-) New commits: commit 9a7cd25471e221fb3b4ba3736ca02f155cc16b1f Author: Sebastian Vahl Date: Wed Jul 23 11:15:01 2008 +0200 re-include some packages after the split of kdebase-workspace diff --git a/config/livecd-fedora-kde.ks b/config/livecd-fedora-kde.ks index 97f0e00..2bf8887 100644 --- a/config/livecd-fedora-kde.ks +++ b/config/livecd-fedora-kde.ks @@ -1,36 +1,45 @@ %include livecd-fedora-base-desktop.ks %packages + @kde-desktop # unwanted packages from @kde-desktop # don't include these for now to fit on a cd -# digikam (~11 megs), ktorrent (~3 megs), amarok (~14 megs), -# kdegames (~31 megs), koffice-* (~51 megs), kftpgrabber (~1 megs) -# kaffeine-* (~3 megs) + +### amarok has duplicate functionality with juk (~14 megs) -amarok +### digikam has duplicate functionality with gwenview (~11 megs) -digikam +### kdeedu is too big for the live images -kdeedu +### scribus is too big for the live images -scribus +### kget has also basic torrent features (~3 megs) -ktorrent -#-kdegames --kftpgrabber* +### konqueror is also able to browse ftp shares (~1 megs) +#-kftpgrabber* +### kaffeine has duplicate functionality with dragonplayer (~3 megs) -kaffeine* +### the removal of kdegames will free ~31 megs +#-kdegames --koffice-* -# KDE 3 -#koffice-kword -#koffice-kspread -#koffice-kpresenter -#koffice-filters + +# Useful additional KDE3 applications +koffice-kword +koffice-kspread +koffice-kpresenter +koffice-filters k3b -#filelight +filelight # twinkle (~10 megs) #twinkle + # some extras fuse -#pavucontrol +pavucontrol + # additional fonts @fonts @@ -41,6 +50,7 @@ fonts-KOI8-R fonts-KOI8-R-100dpi tibetan-machine-uni-fonts + # FIXME/TODO: recheck the removals here # try to remove some packages from livecd-fedora-base-desktop.ks -gdm From ml at deadbabylon.de Wed Jul 23 09:19:21 2008 From: ml at deadbabylon.de (Sebastian Vahl) Date: Wed, 23 Jul 2008 11:19:21 +0200 Subject: [Fedora-livecd-list] config/livecd-fedora-kde.ks In-Reply-To: <48867897.5090902@kanarip.com> References: <20080722073515.9657B120027@lists.fedorahosted.org> <200807221038.50078.ml@deadbabylon.de> <48867897.5090902@kanarip.com> Message-ID: <200807231119.26570.ml@deadbabylon.de> Am Mi 23.Juli 2008 schrieb Jeroen van Meeuwen: > Sebastian Vahl wrote: > > Am Di 22.Juli 2008 schrieb Jeroen van Meeuwen: > >> Sebastian Vahl wrote: > >>> config/livecd-fedora-kde.ks | 6 +++--- > >>> 1 file changed, 3 insertions(+), 3 deletions(-) > >> > >> Could these changes be made in the spin-kickstarts GIT repository > >> please? > > > > How do I get access to this GIT? > > I see you have requested access, and so I have approved. I've found the group yesterday evening and it sounds like the right place to suscribe. Thanks for approving me. > > Sorry for the question but I've not followed the discussions very closely > > because of short time atm. > > We have a mailing list up and running on lists.fedoraproject.org now: > http://admin.fedoraproject.org/mailman/listinfo/fedora-spins Thanks. I'm already suscribed to these mailinglists. BTW: Until the status of both GITs is cleared (see Jeremy's mail from yesterday) I'll do the checkins in both so that nothing will be lost. Sebastian -------------- 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 anthony_j_coco at yahoo.com Wed Jul 23 14:16:07 2008 From: anthony_j_coco at yahoo.com (Coco Computers & Consulting) Date: Wed, 23 Jul 2008 07:16:07 -0700 (PDT) Subject: [Fedora-livecd-list] local hard disk space? In-Reply-To: <48867682.6030201@filteredperception.org> Message-ID: <32772.18091.qm@web52610.mail.re2.yahoo.com> Thanks Doug. In continuing to experiment with CentOS5.1 Live CD I have been able to cross-mount drives from other linux systems on my network, but as yet I have not found a way to mount the local hard drive. I tried (as root) to mount it via: mount -t ntfs /dev/hda1? /local because the Graphical Hardware utility recognized my primary local hard drive as /dev/hda1 and because the man page for mount says that 'ntfs' is a valid specification for filesystem type. My local hard drive is an ntfs (Windows XP) filesystem. But when I attempt this mount I get an error message saying that 'ntfs' is not a valid filesystem type. Is there any way at all to mount the local hard drive? That would make the LiveCD distribution much more valuable, I think. --thanks, --Tony C. Coco Computers & Consulting http://coconets.homeip.net --- On Tue, 7/22/08, Douglas McClendon wrote: From: Douglas McClendon Subject: Re: [Fedora-livecd-list] local hard disk space? To: fedora-livecd-list at redhat.com Date: Tuesday, July 22, 2008, 8:08 PM Coco Computers & Consulting wrote: > When I boot with Centos 5.1 Live CD, a df command shows the root > filesystem / is mounted to /dev/mapper/livecd-rw and shows a total of > about 4GB with 50% available. Is this disk space from my local hard > drive? How is it carved out? My local hard drive is installed with a > Windows XP system. Does LiveCD simply create a 4GB file on the local > hard drive for its own use? No, the 4G is basically imaginary. Whatever amount it starts out as used, say 2.1G, is actually compressed data on the cdrom, i.e. about 675MB. Once booted and files/blocks are written, they are written to ram (or with liveusb persistence, flash/disk). The only reason for the arbitrary 4G number, as opposed to say, 1000G, is that the formatting data of a larger filesystem would take up a little bit of extra space, even compressed. Theoretically if you had a 16GB ram system, you'd be a bit unhappy that an artificial limitation of 4GB of writable blocks is being used, when you have more ram than that to burn. Long ago I submitted a patch such that the devicemapper device would have a size greater than 4GB, but the filesystem still be formatted to 4GB. With that kind of patch, such a user of a 16GB filesystem could resize2fs the filesystem larger post boot, and not be limited. At the time however, squashfs was not as efficient as it currently is with sparse files, and such a larger device would also have resulted in more actual data space taken up on the cdrom (and also signifigantly increasing the time to author/master the livecd originally). Now however squashfs natively handles sparse files, and won't waste any actual space on even a terabyte of zeros. That was probably a longer answer than you were looking for. Executive summary- the 4G is purely imaginary and means nothing. The fedora livecd like most livecds, by default, does not touch your system disk at all. -dmc > > --thanks, > --Tony C. > > Coco Computers & Consulting > http://coconets.homeip.net > > > > ------------------------------------------------------------------------ > > -- > 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 DON.RAIKES at oracle.com Wed Jul 23 16:33:26 2008 From: DON.RAIKES at oracle.com (DON.RAIKES at oracle.com) Date: Wed, 23 Jul 2008 09:33:26 -0700 (PDT) Subject: [Fedora-livecd-list] local hard disk space? In-Reply-To: <32772.18091.qm@web52610.mail.re2.yahoo.com> Message-ID: <639c9607-d2df-4d26-86b7-bd451449f93f@default> Tony, You need to make sure that oyou have ntfs support on your livecd. You will need the ntfs-progs and/or ntfs-3g packages installed before you can mount using ntfs. -----Original Message----- From: Coco Computers & Consulting [mailto:anthony_j_coco at yahoo.com] Sent: Wednesday, July 23, 2008 7:16 AM To: fedora-livecd-list at redhat.com Subject: Re: [Fedora-livecd-list] local hard disk space? Thanks Doug. In continuing to experiment with CentOS5.1 Live CD I have been able to cross-mount drives from other linux systems on my network, but as yet I have not found a way to mount the local hard drive. I tried (as root) to mount it via: mount -t ntfs /dev/hda1 /local because the Graphical Hardware utility recognized my primary local hard drive as /dev/hda1 and because the man page for mount says that 'ntfs' is a valid specification for filesystem type. My local hard drive is an ntfs (Windows XP) filesystem. But when I attempt this mount I get an error message saying that 'ntfs' is not a valid filesystem type. Is there any way at all to mount the local hard drive? That would make the LiveCD distribution much more valuable, I think. --thanks, --Tony C. Coco Computers & Consulting http://coconets.homeip.net --- On Tue, 7/22/08, Douglas McClendon wrote: From: Douglas McClendon Subject: Re: [Fedora-livecd-list] local hard disk space? To: fedora-livecd-list at redhat.com Date: Tuesday, July 22, 2008, 8:08 PM Coco Computers & Consulting wrote:> When I boot with Centos 5.1 Live CD, a df command shows the root > filesystem / is mounted to /dev/mapper/livecd-rw and shows a total of > about 4GB with 50% available. Is this disk space from my local hard > drive? How is it carved out? My local hard drive is installed with a > Windows XP system. Does LiveCD simply create a 4GB file on the local > hard drive for its own use?No, the 4G is basically imaginary. Whatever amount it starts out asused, say 2.1G, is actually compressed data on the cdrom, i.e. about675MB. Once booted and files/blocks are written, they are written toram (or with liveusb persistence, flash/disk). The only reason for thearbitrary 4G number, as opposed to say, 1000G, is that the formattingdata of a larger filesystem would take up a little bit of extra space,even compressed. Theoretically if you had a 16GB ram system, you'd be abit unhappy that an artificial limitation of 4GB of writable blocks isbeing used, when you have more ram than that to burn. Long ago Isubmitted a patch such that the devicemapper device would havea size greater than 4GB, but the filesystem still be formatted to 4GB.With that kind of patch, such a user of a 16GB filesystem couldresize2fs the filesystem larger post boot, and not be limited. At thetime however, squashfs was not as efficient as it currently is withsparse files, and such a larger device would also have resulted in moreactual data space taken up on the cdrom (and also signifigantlyincreasing the time to author/master the livecd originally). Nowhowever squashfs natively handles sparse files, and won't waste anyactual space on even a terabyte of zeros.That was probably a longer answer than you were looking for. Executivesummary- the 4G is purely imaginary and means nothing. The fedoralivecd like most livecds, by default, does not touch your system disk atall.-dmc> > --thanks,> --Tony C.> > Coco Computers & Consulting> http://coconets.homeip.net> > > > ------------------------------------------------------------------------> > --> Fedora-livecd-list mailing list> Fedora-livecd-list at redhat.com> https://www.redhat.com/mailman/listinfo/fedora-livecd-list--Fedora-livecd-list mailing listFedora-livecd-list at redhat.comhttps://www.redhat.com/mailman/listinfo/fedora-livecd-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From jiesun66 at yahoo.com Wed Jul 23 18:54:31 2008 From: jiesun66 at yahoo.com (jie sun) Date: Wed, 23 Jul 2008 11:54:31 -0700 (PDT) Subject: [Fedora-livecd-list] jdk not included on iso image using revisor on fc7 In-Reply-To: <639c9607-d2df-4d26-86b7-bd451449f93f@default> Message-ID: <897173.7845.qm@web31605.mail.mud.yahoo.com> Hi, ?? I am using Revisor to create custom fc7 CD. But whenever I include either GNOME or KDE? in %packages in my kickstart file, the jdk rpm will not be included in the result iso image. If I remove both GNOME AND KDE, then jdk will be included in my iso image. ?? Anybody has any idea on how to install jdk? with either GNOME or KDE ? %package @ GNOME Desktop Environment @ KDE (K Desktop Environment ) jdk Regards, Jie -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.w.pollux at gmail.com Thu Jul 24 02:49:59 2008 From: s.w.pollux at gmail.com (Pollux Su) Date: Thu, 24 Jul 2008 10:49:59 +0800 Subject: [Fedora-livecd-list] How to install a tar file (not a rpm ) into livecd? Message-ID: <780ddc050807231949kf369746k7aa362acb6751aa5@mail.gmail.com> Hi,I have some problems when I build a livecd. Is there someone has experience in installing a tar file into livecd? Should I rebuild this tar file into a rpm? If I just want to copy some files into the livecd I have built,how to do this? unpack the osmin.img or squashfs.img? How can I do? Need help!!! Thanks for your time. Help,please! Regards Pollux Su -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.wood at datawranglers.com Thu Jul 24 03:52:42 2008 From: tim.wood at datawranglers.com (Tim Wood) Date: Wed, 23 Jul 2008 21:52:42 -0600 Subject: [Fedora-livecd-list] How to install a tar file (not a rpm ) into livecd? In-Reply-To: <780ddc050807231949kf369746k7aa362acb6751aa5@mail.gmail.com> References: <780ddc050807231949kf369746k7aa362acb6751aa5@mail.gmail.com> Message-ID: <4887FC8A.8080505@datawranglers.com> If you're trying to build a program from a tar file and install it, then your best option is going to be to go the rpm route. If you just want to copy some files over to a livecd, you can do it during post nochroot. If you do a search on the list archives, you'll find details. Tim Pollux Su wrote: > Hi,I have some problems when I build a livecd. > Is there someone has experience in installing a tar file into > livecd? Should I rebuild this tar file into a rpm? > If I just want to copy some files into the livecd I have built,how > to do this? unpack the osmin.img or squashfs.img? How can I do? > Need help!!! Thanks for your time. Help,please! > > Regards > Pollux Su > ------------------------------------------------------------------------ > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list > -- _________________________________ Tim Wood, CLP, RHCT 719.338.7484 (tel) The Data Wranglers Web, Database & more since since 1994 www.datawranglers.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.w.pollux at gmail.com Thu Jul 24 04:46:52 2008 From: s.w.pollux at gmail.com (Pollux Su) Date: Thu, 24 Jul 2008 12:46:52 +0800 Subject: [Fedora-livecd-list] How to install a tar file (not a rpm ) into livecd? In-Reply-To: <4887FC8A.8080505@datawranglers.com> References: <780ddc050807231949kf369746k7aa362acb6751aa5@mail.gmail.com> <4887FC8A.8080505@datawranglers.com> Message-ID: <780ddc050807232146u3aec4eafg2da0a4a4d6b479b0@mail.gmail.com> hi tim: Thanks for your fast reply, I've found how to copy file to livecd using the %post-nochroot and pasted here,you made my day,thanks again. in your own config/kickstart, you can add a section like the following (note, you can just add this, as there can be multiple of these %post sections) %post --nochroot mkdir $INSTALL_ROOT/usr/share/extramedia cp /home/mdickson/some.mpeg \ $INSTALL_ROOT/usr/share/extramedia/ mkdir $LIVE_ROOT/momedia cp /home/mdickson/someother.mpeg \ $LIVE_ROOT/momedia/ %end Note, the first part, will add the file to the root filesystem that is visible when you boot up the livecd/usb. And as a result will be compressed during the build process (but obviously not well, as mpeg is already compressed as much as it can). The second part (using LIVE_ROOT instead of INSTALL_ROOT), will add the file to the cdrom filesysem, uncompressed. As such, the user could for instance easily see the file if they dropped the cdrom into a windows system (on the cdrom, under the top level folder 'momedia'). On Thu, Jul 24, 2008 at 11:52 AM, Tim Wood wrote: > If you're trying to build a program from a tar file and install it, then > your best option is going to be to go the rpm route. > > If you just want to copy some files over to a livecd, you can do it during > post nochroot. If you do a search on the list archives, you'll find > details. > > Tim > > > Pollux Su wrote: > > Hi,I have some problems when I build a livecd. > Is there someone has experience in installing a tar file into livecd? > Should I rebuild this tar file into a rpm? > If I just want to copy some files into the livecd I have built,how to do > this? unpack the osmin.img or squashfs.img? How can I do? > Need help!!! Thanks for your time. Help,please! > > Regards > Pollux Su > > ------------------------------ > > -- > Fedora-livecd-list mailing listFedora-livecd-list at redhat.comhttps://www.redhat.com/mailman/listinfo/fedora-livecd-list > > > > -- > _________________________________ > Tim Wood, CLP, RHCT > 719.338.7484 (tel) > > The Data Wranglers > Web, Database & more since since 1994 > www.datawranglers.com > > > -- > 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 tim.wood at datawranglers.com Thu Jul 24 04:55:21 2008 From: tim.wood at datawranglers.com (Tim Wood) Date: Wed, 23 Jul 2008 22:55:21 -0600 Subject: [Fedora-livecd-list] How to install a tar file (not a rpm ) into livecd? In-Reply-To: <780ddc050807232146u3aec4eafg2da0a4a4d6b479b0@mail.gmail.com> References: <780ddc050807231949kf369746k7aa362acb6751aa5@mail.gmail.com> <4887FC8A.8080505@datawranglers.com> <780ddc050807232146u3aec4eafg2da0a4a4d6b479b0@mail.gmail.com> Message-ID: <48880B39.30007@datawranglers.com> Pollux Su wrote: hehehe... it looks like you found a previous post I did on this that I was too tired to redo :-) Glad to be of help. Tim > hi tim: > Thanks for your fast reply, I've found how to copy file to livecd > using the %post-nochroot and pasted here,you made my day,thanks again. > > > in your own config/kickstart, you can add a section like the following > (note, you can just add this, as there can be multiple of these %post > sections) > > %post --nochroot > > mkdir $INSTALL_ROOT/usr/share/extramedia > cp /home/mdickson/some.mpeg \ > $INSTALL_ROOT/usr/share/extramedia/ > > mkdir $LIVE_ROOT/momedia > cp /home/mdickson/someother.mpeg \ > $LIVE_ROOT/momedia/ > > %end > > Note, the first part, will add the file to the root filesystem that is > visible when you boot up the livecd/usb. And as a result will be > compressed during the build process (but obviously not well, as mpeg is > already compressed as much as it can). > > The second part (using LIVE_ROOT instead of INSTALL_ROOT), will add the > file to the cdrom filesysem, uncompressed. As such, the user could for > instance easily see the file if they dropped the cdrom into a windows > system (on the cdrom, under the top level folder 'momedia'). > > > On Thu, Jul 24, 2008 at 11:52 AM, Tim Wood > wrote: > > If you're trying to build a program from a tar file and install > it, then your best option is going to be to go the rpm route. > > If you just want to copy some files over to a livecd, you can do > it during post nochroot. If you do a search on the list archives, > you'll find details. > > Tim > > > Pollux Su wrote: >> Hi,I have some problems when I build a livecd. >> Is there someone has experience in installing a tar file into >> livecd? Should I rebuild this tar file into a rpm? >> If I just want to copy some files into the livecd I have >> built,how to do this? unpack the osmin.img or squashfs.img? How >> can I do? >> Need help!!! Thanks for your time. Help,please! >> >> Regards >> Pollux Su >> ------------------------------------------------------------------------ >> >> -- >> Fedora-livecd-list mailing list >> Fedora-livecd-list at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-livecd-list >> > > > -- > _________________________________ > Tim Wood, CLP, RHCT > 719.338.7484 (tel) > > The Data Wranglers > Web, Database & more since since 1994 > www.datawranglers.com > > > > -- > 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 > -- _________________________________ Tim Wood, CLP, RHCT 719.338.7484 (tel) The Data Wranglers Web, Database & more since since 1994 www.datawranglers.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.w.pollux at gmail.com Thu Jul 24 04:58:43 2008 From: s.w.pollux at gmail.com (Pollux Su) Date: Thu, 24 Jul 2008 12:58:43 +0800 Subject: [Fedora-livecd-list] I just wanna run firefox! Only firefor! How to write the ks file?(minimalks file). Message-ID: <780ddc050807232158j307e7ce5l40ec88358a2b1ad7@mail.gmail.com> Hi, I just wanna run firefox on livecd.Only firefox,firefox only. How to write the miiiniiiimalll ks file. Thanks you very much. -------------- next part -------------- An HTML attachment was scrubbed... URL: From svahl at fedoraproject.org Thu Jul 24 09:57:27 2008 From: svahl at fedoraproject.org (Sebastian Vahl) Date: Thu, 24 Jul 2008 09:57:27 +0000 (UTC) Subject: [Fedora-livecd-list] config/livecd-fedora-kde.ks Message-ID: <20080724095727.5A6C6120027@lists.fedorahosted.org> config/livecd-fedora-kde.ks | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 97e79bb8d464fffe14d2ca37dd4daf6de7d80c60 Author: Sebastian Vahl Date: Thu Jul 24 11:57:17 2008 +0200 fix the inclusion of amarok. It was accidentially excluded diff --git a/config/livecd-fedora-kde.ks b/config/livecd-fedora-kde.ks index 2bf8887..8d2148c 100644 --- a/config/livecd-fedora-kde.ks +++ b/config/livecd-fedora-kde.ks @@ -8,7 +8,7 @@ # don't include these for now to fit on a cd ### amarok has duplicate functionality with juk (~14 megs) --amarok +#-amarok ### digikam has duplicate functionality with gwenview (~11 megs) -digikam ### kdeedu is too big for the live images From kanarip at kanarip.com Thu Jul 24 16:36:52 2008 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Thu, 24 Jul 2008 18:36:52 +0200 Subject: [Fedora-livecd-list] F10 Alpha: livecd-fedora-base-desktop.ks vs. fedora-live-base.ks In-Reply-To: <1216740089.25951.22.camel@aglarond.local> References: <200807221302.34434.ml@deadbabylon.de> <1216740089.25951.22.camel@aglarond.local> Message-ID: <4888AFA4.1070906@kanarip.com> Jeremy Katz wrote: > On Tue, 2008-07-22 at 13:02 +0200, Sebastian Vahl wrote: >> Short and simple question: Which kickstart will be the base for the alpha of >> the KDE live images, livecd-fedora-base-desktop.ks [1] from livecd GIT or >> fedora-live-base.ks [2] from spin-kickstarts GIT? >> The diff between them is quite huge (eg. one still has gparted and the other >> one already includes firstaidkit) and I don't want to rely on the wrong one. > > At the moment, the official spins are still being done with the configs > from the livecd-tools git repo. > Ohw? Who decided that? > Jeroen -- we need to talk about what the long-term answer is because > having _3_ copies of the files[1] just isn't really scalable :-) But > I'm a bit hosed schedule-wise this week, so maybe next week once the > alpha is baked? > That depends. Someone decided the live spin kickstarts needed to be maintained in two separate repositories by making the official spins come from livecd-tools' GIT repo. When that happened, or why, I don't know. Nor do I know what objections there are to a new location, including it's new (submission/review) process. What's keeping livecd-tools, release engineering, hence "the official process" from using the kickstarts in spin-kickstarts exactly? I say two locations, because the fedora-10-gold.ks used for installation media is in pungi (and? or?) fedora-release, not in spin-kickstarts, and as such doesn't concern this discussion. FWIW, my livecd-tools GIT commit access request has been pending for ages. I was planning on letting the kickstarts have an easy transition, but I guess it's not going to happen. I feel I'm contributing a valuable effort to this process, thanks. -Jeroen From ehansen at spyrus.com Thu Jul 24 17:07:37 2008 From: ehansen at spyrus.com (Ebbe Hansen) Date: Thu, 24 Jul 2008 10:07:37 -0700 Subject: [Fedora-livecd-list] syslinux fails to create "ldlinux.sys" Message-ID: Need help to determine why "syslinux" fails to write to USB-drive. The trace below indicates that everything works fine until the very end! The call: "syslinux -d syslinux /dev/sdb1" results in error: syslinux: failed to create ldlinux.sys See below for details! Previous "livecd-iso-to-disk" worked OK - something must have changed on latest Fedora9-KDE load (downloaded on 7-18-08) or on my "setup" has changed. Is there a way to request diagnostics from the "syslinux" utility? E Hansen @ SPYRUS ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++ Log of 'livecd-iso-to-disk' session on Fedora-9-KDE (downloaded on 7-18-08): ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++ [root at fedora91a /]# bash -x livecd-iso-to-disk --reset-mbr --overlay-size-mb 1000 /usr/RedHat/Fedora-9-i686-Live-071808.iso /dev/sdb1 + export PATH=/sbin:/usr/sbin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbi n:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/root/bin + PATH=/sbin:/usr/sbin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbi n:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/root/bin ++ id -u + '[' 0 '!=' 0 ']' + '[' 5 -gt 2 ']' + case $1 in + resetmbr=1 + shift + '[' 4 -gt 2 ']' + case $1 in + overlaysizemb=1000 + shift + shift + '[' 2 -gt 2 ']' ++ readlink -f /usr/RedHat/Fedora-9-i686-Live-071808.iso + ISO=/usr/RedHat/Fedora-9-i686-Live-071808.iso + USBDEV=/dev/sdb1 + '[' -z /usr/RedHat/Fedora-9-i686-Live-071808.iso ']' + '[' '!' -b /usr/RedHat/Fedora-9-i686-Live-071808.iso -a '!' -f /usr/RedHat/Fedora-9-i686-Live-071808.iso ']' + '[' -z /dev/sdb1 -o '!' -b /dev/sdb1 ']' + '[' -z '' ']' + echo 'Verifying image...' Verifying image... + checkisomd5 --verbose /usr/RedHat/Fedora-9-i686-Live-071808.iso /usr/RedHat/Fedora-9-i686-Live-071808.iso: e9998706424174d69dda1f23f89b8953 Fragment sums: fad79bb3621cb515652cdbfabaa5cba632af35ca9b739ef3ca35b91b5819 Fragment count: 20 Checking: 100.0% The media check is complete, the result is: PASS. It is OK to use this media. + '[' 0 -ne 0 ']' + checkSyslinuxVersion + '[' '!' -x /usr/bin/syslinux ']' + syslinux + grep -qe -d + SYSLINUXPATH=syslinux + checkFilesystem /dev/sdb1 + dev=/dev/sdb1 ++ /lib/udev/vol_id -t /dev/sdb1 + USBFS=vfat + '[' vfat '!=' vfat -a vfat '!=' msdos -a vfat '!=' ext2 -a vfat '!=' ext3 ']' ++ /lib/udev/vol_id -u /dev/sdb1 + USBLABEL=D0F3-E7C8 + '[' -n D0F3-E7C8 ']' + USBLABEL=UUID=D0F3-E7C8 + checkPartActive /dev/sdb1 + dev=/dev/sdb1 + getdisk /dev/sdb1 + DEV=/dev/sdb1 ++ udevinfo -q path -n /dev/sdb1 + p=/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host4/target4:0:0/4: 0:0:0/block/sdb/sdb1 + '[' -e /sys//devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host4/target4:0:0 /4:0:0:0/block/sdb/sdb1/device ']' +++ readlink -f /sys//devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host4/target4:0:0 /4:0:0:0/block/sdb/sdb1/../ ++ basename /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host4/target4:0:0/ 4:0:0:0/block/sdb + device=sdb + '[' '!' -e /sys/block/sdb -o '!' -e /dev/sdb ']' + device=/dev/sdb + '[' /dev/sdb1 = /dev/sdb ']' ++ /sbin/fdisk -l /dev/sdb ++ grep /dev/sdb1 ++ awk '{print $2;}' + '[' '*' '!=' '*' ']' + checkMBR /dev/sdb1 + getdisk /dev/sdb1 + DEV=/dev/sdb1 ++ udevinfo -q path -n /dev/sdb1 + p=/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host4/target4:0:0/4: 0:0:0/block/sdb/sdb1 + '[' -e /sys//devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host4/target4:0:0 /4:0:0:0/block/sdb/sdb1/device ']' +++ readlink -f /sys//devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host4/target4:0:0 /4:0:0:0/block/sdb/sdb1/../ ++ basename /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host4/target4:0:0/ 4:0:0:0/block/sdb + device=sdb + '[' '!' -e /sys/block/sdb -o '!' -e /dev/sdb ']' + device=/dev/sdb ++ mktemp /tmp/bs.XXXXXX + bs=/tmp/bs.vryiWZ + dd if=/dev/sdb of=/tmp/bs.vryiWZ bs=512 count=1 ++ hexdump -n 2 /tmp/bs.vryiWZ ++ head -n 1 ++ awk '{print $2;}' + mbrword=31fa + rm -f /tmp/bs.vryiWZ + '[' 31fa = 0000 ']' + return 0 + checkMounted /dev/sdb1 + dev=/dev/sdb1 + grep -q '^/dev/sdb1 ' /proc/mounts + grep -q '^/dev/sdb1 ' /proc/swaps + '[' -n 1 ']' + resetMBR /dev/sdb1 + getdisk /dev/sdb1 + DEV=/dev/sdb1 ++ udevinfo -q path -n /dev/sdb1 + p=/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host4/target4:0:0/4: 0:0:0/block/sdb/sdb1 + '[' -e /sys//devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host4/target4:0:0 /4:0:0:0/block/sdb/sdb1/device ']' +++ readlink -f /sys//devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host4/target4:0:0 /4:0:0:0/block/sdb/sdb1/../ ++ basename /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host4/target4:0:0/ 4:0:0:0/block/sdb + device=sdb + '[' '!' -e /sys/block/sdb -o '!' -e /dev/sdb ']' + device=/dev/sdb + '[' -f /usr/lib/syslinux/mbr.bin ']' + cat /usr/lib/syslinux/mbr.bin + '[' -n 1000 -a vfat = vfat ']' + '[' 1000 -gt 2047 ']' ++ mktemp -d /media/cdtmp.XXXXXX + CDMNT=/media/cdtmp.wlBTjg + mount -o loop,ro /usr/RedHat/Fedora-9-i686-Live-071808.iso /media/cdtmp.wlBTjg ++ mktemp -d /media/usbdev.XXXXXX + USBMNT=/media/usbdev.SvMQxM + mount /dev/sdb1 /media/usbdev.SvMQxM + trap exitclean SIGINT SIGTERM + '[' -d /media/cdtmp.wlBTjg/LiveOS ']' + check=/media/cdtmp.wlBTjg/LiveOS + '[' -d /media/usbdev.SvMQxM/LiveOS ']' ++ du -s -B 1M /media/usbdev.SvMQxM/LiveOS ++ awk '{print $1;}' + tbd=1684 ++ du -s -B 1M /media/cdtmp.wlBTjg/LiveOS ++ awk '{print $1;}' + livesize=684 ++ df -B1M /dev/sdb1 ++ tail -n 1 ++ awk '{print $4;}' + free=2123 + '[' 1684 -gt 3807 ']' + '[' -d /media/usbdev.SvMQxM/LiveOS ']' + echo 'Already set up as live image. Deleting old in fifteen seconds...' Already set up as live image. Deleting old in fifteen seconds... + sleep 15 + rm -rf /media/usbdev.SvMQxM/LiveOS + echo 'Copying live image to USB stick' Copying live image to USB stick + '[' '!' -d /media/usbdev.SvMQxM/syslinux ']' + '[' '!' -d /media/usbdev.SvMQxM/LiveOS ']' + mkdir /media/usbdev.SvMQxM/LiveOS + '[' -f /media/cdtmp.wlBTjg/LiveOS/squashfs.img ']' + cp /media/cdtmp.wlBTjg/LiveOS/squashfs.img /media/usbdev.SvMQxM/LiveOS/squashfs.img + '[' -f /media/cdtmp.wlBTjg/LiveOS/osmin.img ']' + cp /media/cdtmp.wlBTjg/LiveOS/osmin.img /media/usbdev.SvMQxM/LiveOS/osmin.img + cp /media/cdtmp.wlBTjg/isolinux/boot.cat /media/cdtmp.wlBTjg/isolinux/initrd0.img /media/cdtmp.wlBTjg/isolinux/isolinux.bin /media/cdtmp.wlBTjg/isolinux/isolinux.cfg /media/cdtmp.wlBTjg/isolinux/memtest /media/cdtmp.wlBTjg/isolinux/splash.jpg /media/cdtmp.wlBTjg/isolinux/vesamenu.c32 /media/cdtmp.wlBTjg/isolinux/vmlinuz0 /media/usbdev.SvMQxM/syslinux + echo 'Updating boot config file' Updating boot config file + sed -i -e 's/CDLABEL=[^ ]*/UUID=D0F3-E7C8/' -e 's/rootfstype=[^ ]*/rootfstype=vfat/' /media/usbdev.SvMQxM/syslinux/isolinux.cfg + '[' -n 1000 ']' + echo 'Initializing persistent overlay file' Initializing persistent overlay file ++ /lib/udev/vol_id -l /dev/sdb1 ++ /lib/udev/vol_id -u /dev/sdb1 + OVERFILE=overlay-FEDORA9-D0F3-E7C8 + '[' vfat = vfat ']' + dd if=/dev/zero of=/media/usbdev.SvMQxM/LiveOS/overlay-FEDORA9-D0F3-E7C8 count=1000 bs=1M 1000+0 records in 1000+0 records out 1048576000 bytes (1.0 GB) copied, 273.886 s, 3.8 MB/s + sed -i -e 's/liveimg/liveimg overlay=UUID=D0F3-E7C8/' /media/usbdev.SvMQxM/syslinux/isolinux.cfg + sed -i -e 's/\ ro\ /\ rw\ /' /media/usbdev.SvMQxM/syslinux/isolinux.cfg + echo 'Installing boot loader' Installing boot loader + '[' vfat = vfat -o vfat = msdos ']' + mv /media/usbdev.SvMQxM/syslinux/isolinux.cfg /media/usbdev.SvMQxM/syslinux/syslinux.cfg + cleanup + '[' -d /media/cdtmp.wlBTjg ']' + umount /media/cdtmp.wlBTjg + rmdir /media/cdtmp.wlBTjg + '[' -d /media/usbdev.SvMQxM ']' + umount /media/usbdev.SvMQxM + rmdir /media/usbdev.SvMQxM + '[' -n syslinux ']' + syslinux -d syslinux /dev/sdb1 syslinux: failed to create ldlinux.sys + echo 'USB stick set up as live image!' USB stick set up as live image! [root at fedora91a /]# [root at fedora91a /]# -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmc.fedora at filteredperception.org Sat Jul 26 06:53:41 2008 From: dmc.fedora at filteredperception.org (Douglas McClendon) Date: Fri, 25 Jul 2008 23:53:41 -0700 Subject: [Fedora-livecd-list] Re: How do I save and restore my overlay? In-Reply-To: References: Message-ID: <488AC9F5.5060905@filteredperception.org> martin.x.long at jpmchase.com wrote: > > Douglas McClendon > >If that doesn't help or answer you question, try to add more detail to > >your question. > > Douglas - > > Thanks for the reply. > > I use the live usb tools to create my live USB stick with a 2047 MB > overlay. I boot from it and let it run updates. I reboot the LiveUSB to > make sure it still boots, then I shut down. I boot a system on a copy > of Fedora 9 on the hard drive and plug in my Live USB so I can see the > files on my USB stick. > > I see 2 folders: > LiveOS > and > syslinux > > in the LiveOS folder I see three files: > osmin.img > overlay-FEDORA-3099-53F2 > and > squashfs.img > > ====== > assumptions > > squashfs.img looks to be the size of the live iso > overlay-FEDORA-3099-53F2 looks to be the size of the overlay and has > overlay in the file name > osmin.img is only 8k probably a boot strap, I'm not sure. osmin.img is part of an optimization used during the install-to-disk process. Interesting long story, but should not be relevant here. > ======= > > I'm sorry, I can't find anything on the LiveUSB file structure on the > WiKi. I've signed on as a writer for the Fedore project so I'd like to > write it once I figure out what it is. Sounds like a good plan. I don't have the free time I used to when I was happily unemployed, but I'll try to help. > I was hoping that I could backup the overlay file and the syslinux > folder from my completely updated LiveUSB stick and restore them to a > newly built LiveUSB from my backup. I think this should work, but there may be some subtle wording here. What you said almost sounds like boiling down to doing a straight duplication of a LiveUSB, which AFAIK should work. To the extent that it doesn't work, we should focus on how what you are doing is different than a pure duplication. > > > I'm not entirely sure what you mean. One thing that is possible is to > > copy the overlay file from one liveusb and put it on another. Though > > the format of the overlay file is inherently tied to the specific liveos > > it was originally with. I.e. you won't be able to copy an overlay file > > from an f9-x86 liveusb onto an f9-x64 or f10-x86 liveusb. Or even a > > customized f9-x86 liveusb that you created with livecd-creator/tools. > > Nothing fancy - The same USB stick, built in the same way with the same > iso and the same overlay size. > > The overlay file name changes. I've given the updated file (the overlay > that was part of the LiveUSB for all of the updates) the same name as > the new file that is created and left the updated file with its original > name. I've overwritten just the overlay itself and the overlay and every > combinarion of the osmin.img and squashfs.img files. This sounds reasonable. Now, if this is a new LiveUSB built from the same LiveCD, the osmin.img and squashfs.img should be 100% identical. Same file sizes, same md5sums. If they aren't, mention that. > > I could never get it to boot. The boot starts but then hangs. What is the last thing you see when it hangs? > Ideally, it would be great to specify the overlay and the syslinyx > folder that goes with that overlay in the command line to build the > LiveUSB. Unfortunately the syslinux folder is hard coded and is a limitation of syslinux (actually you get 2 or 3 choices, but not an arbitrary choice). The overlay file name is part of our code, and is keyed off of the UUID of the usb disk (in this case). I can't say off the top of my head (it's been awhile) whether making the filename specifiable on the commandline is trivial or not. > > At this point I would be thrilled if I could get a set of manual steps > together to have an updated system without going through the update > process. I loose a day each time. If I find the time, I'll try to reproduce your problem. An absolute brute-force method that should work for identical sized usbsticks would be a bit for bit copy. I.e. if you set up one 4G LiveUSB and it works, you should be able to plug it in, and if it is seen as perhaps /dev/sdX and then you plug in another 4G usbstick seen as /dev/sdY, you should be able to run dd if=/dev/sdX of=/dev/sdY and get a working clone. (note, you may have the partition visible as /dev/sdX1, but use the whole device as above for the duplication). > > > From an engineering standpoint, of course anything is possible. One > > use case I see, is to use the persistence feature to add an entry to > > fstab, such that say, /mnt/data mounts to a ext3fs image located on a > > file on your liveusb. You can then add a user that has a home directory > > under there, and perhaps install applications under there. In this way, > > you could then copy that ext3fs image file to an f10 liveusb, and then > > only have to re-do the fstab and passwd modifications, such that > > everything now pretty much looks the same. > > Your suggestion of building a file structure that would transcend > different releases would be awesome but alas I need to crawl before I > can run. > > Any help would be greatly appreciated. Hope the above helps. And as mentioned, if I find the time, I'll try to reproduce your less brute-force method of copying, which sounds pretty reasonable, but clearly isn't working for some reason or another. And just post any wiki/work-in-progress and I'll be happy to provide feedback. -dmc From martin.x.long at jpmchase.com Sun Jul 27 02:20:22 2008 From: martin.x.long at jpmchase.com (martin.x.long at jpmchase.com) Date: Sat, 26 Jul 2008 19:20:22 -0700 Subject: [Fedora-livecd-list] Re: How do I save and restore my overlay? Message-ID: Douglas - Thanks again for the reply. Douglas McClendon wrote: > Message: 1 > Date: Fri, 25 Jul 2008 23:53:41 -0700 > From: Douglas McClendon > Subject: Re: [Fedora-livecd-list] Re: How do I save and restore my > overlay? > To: fedora-livecd-list at redhat.com > Message-ID: <488AC9F5.5060905 at filteredperception.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > martin.x.long at jpmchase.com wrote: > > Douglas McClendon > > > >If that doesn't help or answer you question, try to add more detail to > > >your question. > > > > Douglas - > > > > Thanks for the reply. > > > > I use the live usb tools to create my live USB stick with a 2047 MB > > overlay. I boot from it and let it run updates. I reboot the LiveUSB to > > make sure it still boots, then I shut down. I boot a system on a copy > > of Fedora 9 on the hard drive and plug in my Live USB so I can see the > > files on my USB stick. > > > > I see 2 folders: > > LiveOS > > and > > syslinux > > > > in the LiveOS folder I see three files: > > osmin.img > > overlay-FEDORA-3099-53F2 > > and > > squashfs.img > > > > ====== > > assumptions > > > > squashfs.img looks to be the size of the live iso > > overlay-FEDORA-3099-53F2 looks to be the size of the overlay and has > > overlay in the file name > > osmin.img is only 8k probably a boot strap, I'm not sure. > > osmin.img is part of an optimization used during the install-to-disk > process. Interesting long story, but should not be relevant here. > > > ======= > > > > I'm sorry, I can't find anything on the LiveUSB file structure on the > > WiKi. I've signed on as a writer for the Fedore project so I'd like to > > write it once I figure out what it is. > > Sounds like a good plan. I don't have the free time I used to when I > was happily unemployed, but I'll try to help. > > > > I was hoping that I could backup the overlay file and the syslinux > > folder from my completely updated LiveUSB stick and restore them to a > > newly built LiveUSB from my backup. > > I think this should work, but there may be some subtle wording here. > What you said almost sounds like boiling down to doing a straight > duplication of a LiveUSB, which AFAIK should work. To the extent that > it doesn't work, we should focus on how what you are doing is different > than a pure duplication. > > > > > > I'm not entirely sure what you mean. One thing that is possible is to > > > copy the overlay file from one liveusb and put it on another. Though > > > the format of the overlay file is inherently tied to the specific liveos > > > it was originally with. I.e. you won't be able to copy an overlay file > > > from an f9-x86 liveusb onto an f9-x64 or f10-x86 liveusb. Or even a > > > customized f9-x86 liveusb that you created with livecd-creator/tools. > > > > Nothing fancy - The same USB stick, built in the same way with the same > > iso and the same overlay size. > > > > The overlay file name changes. I've given the updated file (the overlay > > that was part of the LiveUSB for all of the updates) the same name as > > the new file that is created and left the updated file with its original > > name. I've overwritten just the overlay itself and the overlay and every > > combinarion of the osmin.img and squashfs.img files. > > This sounds reasonable. Now, if this is a new LiveUSB built from the > same LiveCD, the osmin.img and squashfs.img should be 100% identical. > Same file sizes, same md5sums. If they aren't, mention that. > I always build from the same .iso using a script so everything is built identically. The overlay file name does change every time though. > > > > > I could never get it to boot. The boot starts but then hangs. > > What is the last thing you see when it hangs? > ================================================= Decompressing Linux... done. Booting the kernel. sd 2:0:0:0: [sdb] Assuming drive cache: write through sd 2:0:0:0: [sdb] Assuming drive cache: write through ---------------------------------------------------------- WARNING: Cannot find root file system! ---------------------------------------------------------- Create symlink /dev/root and then exit this shell to continue the boot sequence. bash-3.2# ================================================= I can't find the symlink command anywhere in this limited recovery shell. I don't know where this little root directory is so I can move commands and scripts into it (before I back up) to help me recover or avoid banging out to this shell. > > > Ideally, it would be great to specify the overlay and the syslinyx > > folder that goes with that overlay in the command line to build the > > LiveUSB. > > Unfortunately the syslinux folder is hard coded and is a limitation of > syslinux (actually you get 2 or 3 choices, but not an arbitrary choice). > The overlay file name is part of our code, and is keyed off of the > UUID of the usb disk (in this case). I can't say off the top of my head > (it's been awhile) whether making the filename specifiable on the > commandline is trivial or not. > > > > > At this point I would be thrilled if I could get a set of manual steps > > together to have an updated system without going through the update > > process. I loose a day each time. > > If I find the time, I'll try to reproduce your problem. An absolute > brute-force method that should work for identical sized usbsticks would > be a bit for bit copy. I.e. if you set up one 4G LiveUSB and it works, > you should be able to plug it in, and if it is seen as perhaps /dev/sdX > and then you plug in another 4G usbstick seen as /dev/sdY, you should be > able to run > > dd if=/dev/sdX of=/dev/sdY I actually started with something like this only created an output file of /usr/MLONG01/usbiso. This was ok with my 1 gig stick but it was to small to install apps and run updates, so I upgraded. I could actually restore a bootable USB from that file which would work in a pinch. The problem is that I'm using a 16Gig USB stick and my back up files would be 16Gig each and take hours to create and restore. It actually takes longer than building the bootable USB and running the updates. On the plus side I can do a restore without an internet connection or interaction. Unfortunately, these files are just too big to work with. > > and get a working clone. (note, you may have the partition visible as > /dev/sdX1, but use the whole device as above for the duplication). > > > > > > From an engineering standpoint, of course anything is possible. One > > > use case I see, is to use the persistence feature to add an entry to > > > fstab, such that say, /mnt/data mounts to a ext3fs image located on a > > > file on your liveusb. You can then add a user that has a home directory > > > under there, and perhaps install applications under there. In this way, > > > you could then copy that ext3fs image file to an f10 liveusb, and then > > > only have to re-do the fstab and passwd modifications, such that > > > everything now pretty much looks the same. > > > > Your suggestion of building a file structure that would transcend > > different releases would be awesome but alas I need to crawl before I > > can run. > > > > Any help would be greatly appreciated. > > Hope the above helps. And as mentioned, if I find the time, I'll try to > reproduce your less brute-force method of copying, which sounds pretty > reasonable, but clearly isn't working for some reason or another. > > And just post any wiki/work-in-progress and I'll be happy to provide > feedback. What I know of the LiveUSB file structure is not yet WiKiworthy. Are my assumptions correct regarding squashfs.img and overlay-FEDORA-3099-53F2? > > -dmc > Thanks Again Martin ----------------------------------------- This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wtogami at redhat.com Sun Jul 27 08:03:30 2008 From: wtogami at redhat.com (Warren Togami) Date: Sun, 27 Jul 2008 04:03:30 -0400 Subject: [Fedora-livecd-list] Recursive livecd-creator problem Message-ID: <488C2BD2.6080209@redhat.com> I am trying to create a Live LTSP Server image. This is pretty much just livecd-fedora-9-desktop.ks plus the ltsp-server package added, then ltsp-build-client runs in %post. ltsp-build-client itself runs an internal instance of imagecreator to install the client chroot. The chroot has another chroot installed within it, then it is all smashed into a single image. This should be straightforward, except I ran into a problem. The chroot created by livecd-creator has a blank /etc/resolv.conf, so the inner imagecreator trying to create a chroot fails as it cannot download repo metadata. I cannot simply copy /etc/resolv.conf from the host to the first level chroot in %post since it is already running within the chroot at this point. I then tried to use both %post --nochroot and %post in the same kickstart file. It seems that %post --nochroot is ignored when you also have a %post? Are both supposed to run (in what order?), or only %post? Similarly %pre and %post in the same kickstart script, %pre seems to be ignored. Anybody have any idea how I can achieve my goal of copying /etc/resolv.conf from the host and into the chroot, before or during %post? Warren Togami wtogami at redhat.com From jvonau at shaw.ca Sun Jul 27 08:00:08 2008 From: jvonau at shaw.ca (Jerry Vonau) Date: Sun, 27 Jul 2008 03:00:08 -0500 Subject: [Fedora-livecd-list] Re: livecd-creator unmounting temp image, running daemons. Message-ID: <1217145608.25653.3.camel@S010600e029961c54.wp.shawcable.net> Martin Langhoff wrote: > On Sun, Jul 27, 2008 at 3:25 PM, Martin Langhoff > wrote: >> After a bit more investigation. the livecd-tools package in F9 >> (017.1-1.fc9) can only build F9 correctly, and the problem boils down >> to incorrect placement of the .ko files in the initrd. Here is how to >> repro with F9 vs F7. In my testing, F8 shows the same problems. > > I tracked this down to the switch from mayflower to mkinitrd, which > lead me to commit > 11dbd0bb5ba4b845e80109e990e4e780ca402218 where mayflower gets > installed and called during %post. > > So I updated my ks file as below. This still fails to build a bootable > F8 or F7, both drop to an emergency shell after failing to find root > (see below for more details). I am using git's master for these > builds. > > Current kickstart file > > --8<----8<----8<-- > lang en_US.UTF-8 > keyboard us > timezone US/Eastern > auth --useshadow --enablemd5 > selinux --disabled > firewall --disabled > part / --size 1024 > > repo --name=released > --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-8&arch=$basearch > > %packages > @core > bash > kernel > passwd > policycoreutils > chkconfig > authconfig > rootfiles > > # for live initrd > livecd-tools > # livecd bits to set up the livecd and be able to install > anaconda > #isomd5sum > > %end > > %post > # make the initrd we care about > rm -f /boot/initrd*.img > cp /etc/sysconfig/mkinitrd /etc/mayflower.conf > ver=`ls /boot/vmlinuz* |head -n 1 |sed -e 's;/boot/vmlinuz-;;'` > /usr/lib/livecd-creator/mayflower -f /boot/initrd-$ver.img $ver > rm -f /etc/mayflower.conf > %end > > %post --nochroot > # move the initrd we created to be the booted one > mv $INSTALL_ROOT/boot/initrd-*.img $LIVE_ROOT/isolinux/initrd0.img > %end > --8<----8<----8<-- > > With this ks file, the initrd is now built correctly. But during boot > with F8 I see all sorts of odd errors: > > WARNING: Bogus /etc/fstab file - cannot have /dev/root as the device for / > ... > starting udevd > creating devices > waiting for system to settle > ... > SQUASHFS error: Major/Minor mismatch, trying to mount newer 3.1 filesystem > SQUASHFS error: Please update your kernel > mount: wrong fstype ... > The squsashfs-tools/kernel module on the fc7/8 live disks is to old to mount the squashfs.img created on the newer f9 box. > Once on the shell, the dmesg output looks normal except for the > Squashfs errors, and ls /dev/ does not contain anything that looks > like a usable block device. Trying to mount /dev/loop0 gives me the > same squashfs error as before. > > hmmmm? hints? > > > > m Think you would need to include, maybe recompile, the squashfs-tools rpm from the f9. Then I think you'll need to recompile the kernel module and include it in the initrd. I can't recall when this update to squashfs occurred, but I believe it was tied to a kernel update between fedora releases 8-9. so I'm not sure if the above will even work. Jerry From jvonau at shaw.ca Sun Jul 27 16:52:34 2008 From: jvonau at shaw.ca (Jerry Vonau) Date: Sun, 27 Jul 2008 11:52:34 -0500 Subject: [Fedora-livecd-list] Re: livecd-creator unmounting temp image, running daemons. Message-ID: <1217177555.25653.40.camel@S010600e029961c54.wp.shawcable.net> Martin: Your cc to the livecd list are not appearing there, are you subscribed? Martin Langhoff wrote: > On Sun, Jul 27, 2008 at 8:45 PM, Martin Langhoff > wrote: >> Sounds complex. I will try going in the opposite direction: downgrade >> the package on F9 or pass flags to disable the new fanciness. > > Right - with the following patch to fs.py the F7 kernel won't panic > anymore, and a basic F8 will boot. The mkfs tweak is probably > unneeded, the main difference seems to come from -no-sparse: > Think the issue is going to be how the kernel modules differ from version 3.2 and 3.3 of squashfs-tools. So lets get this clear, F7 is using the 2.6.23.?? and does not boot, F8 is now booting correctly? with which kernel? > --- a/imgcreate/fs.py > +++ b/imgcreate/fs.py > @@ -38,7 +38,7 @@ def makedirs(dirname): > raise > > def mksquashfs(in_img, out_img): > - args = ["/sbin/mksquashfs", in_img, out_img] > + args = ["/sbin/mksquashfs", in_img, out_img, '-no-sparse', '-b', '131072'] > > if not sys.stdout.isatty(): > args.append("-no-progress") > @@ -200,7 +200,7 @@ class SparseExtLoopbackMount(SparseLoopbackMount): > > def __format_filesystem(self): > rc = subprocess.call(["/sbin/mkfs." + self.fstype, > - "-F", "-L", self.fslabel, > + '-I', '128', "-F", "-L", self.fslabel, > "-m", "1", "-b", str(self.blocksize), > self.lofile, > str(self.size / self.blocksize)]) > > > On F7 - my actual target ATM - the problem is not gone through. Init > is dropping me to a panic shell, and I cannot figure out how to get > something I can mount there. When I get dropped in the shell, lsmod > makes it seem like no interesting modules have been loaded. > modprobe-ing libata, cdrom and other modules works. I don't know the > major/minor numbers enough to mknod my way around here. > see above > So I suspect of the initrd, but I am unsure of what to do next. The > mayflower initrd seems to work though it does throw some (IMO) > meaningless errors - complaining about old module names that are not > relevant to the 2.6.23 kernel I have: > > Building an initramfs at /boot/initrd-2.6.23.1-21.fc7.img for kernel > 2.6.23.1-21.fc7 > FATAL: Module ide_cd not found. > FATAL: Module =ata not found. > FATAL: Module usbhid not found. > FATAL: Module ieee1394 not found. > Done; initramfs is 4.2M. > > any more hints on this track? > Think the only way you'll get this to fly is to get the source for squashfs-tools3.3 http://www.squashfs-lzma.org/dl/squashfs3.3.tar.gz and patch your 2.6.23 kernel and recompile the module and replace the module in the initrd. There is a good post on the livecd list about patching squashfs for lsma support and covers all the steps, perhaps you could adapt the steps(leave out the lzma patches). https://www.redhat.com/archives/fedora-livecd-list/2008-July/msg00007.html https://www.redhat.com/archives/fedora-livecd-list/2008-July/msg00005.html Repacking is initrd and iso are not that hard, but I have some notes around if you need them. Jerry From s.w.pollux at gmail.com Mon Jul 28 02:44:19 2008 From: s.w.pollux at gmail.com (Pollux Su) Date: Mon, 28 Jul 2008 10:44:19 +0800 Subject: [Fedora-livecd-list] Some questions from a livecd newer Message-ID: <780ddc050807271944l3470d577h4ec5c4385546f214@mail.gmail.com> Hi,all friends: I was assigned a linux livecd task,but I am not familiar with linux. I have finished a simple fedora livecd following the basic information I got from here. Now,I have to build a minimal livecd with firefox, I think I want to write ks file by myself base on kde ks file and add a firefox package. But this iso file is very large for me. How can I do? Thanks for your time? Where can I find the details of package which I have to install and remove when I build a minimal firefox livecd. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim.wood at datawranglers.com Mon Jul 28 05:25:30 2008 From: tim.wood at datawranglers.com (Tim Wood) Date: Sun, 27 Jul 2008 23:25:30 -0600 Subject: [Fedora-livecd-list] Some questions from a livecd newer In-Reply-To: <780ddc050807271944l3470d577h4ec5c4385546f214@mail.gmail.com> References: <780ddc050807271944l3470d577h4ec5c4385546f214@mail.gmail.com> Message-ID: <488D584A.2000805@datawranglers.com> Pollux, if you look through the kickstarts that are included, you'll find a minimal kickstart. Do not use that as your starting point because the login is disabled. You probably want to start with the minimal desktop. Make sure that builds for you. Then, make a copy in the same directory. Remove one or two packages you're sure you don't need. For instance, open office. Then build another ISO. If that works, duplicate your kickstart and repeat the process. When you get a kickstart that doesn't work, go back to the last one that worked and try again. The kickstart file itself is very similar to the one used for automated installs of RedHat. If you do a google search, you should be able to find RedHat's kickstart documentation (hint, make site:redhat.com part of your google search). The simplest way to find out what a package does is to pull up a terminal on a fedora system and have yum tell you. If you wanted to know what anaconda is: > yum search anaconda Tim Pollux Su wrote: > Hi,all friends: > I was assigned a linux livecd task,but I am not familiar with > linux. I have finished a simple fedora livecd following the basic > information I got from here. Now,I have to build a minimal livecd with > firefox, I think I want to write ks file by myself base on kde ks file > and add a firefox package. But this iso file is very large for me. How > can I do? > Thanks for your time? Where can I find the details of package which > I have to install and remove when I build a minimal firefox livecd. > ------------------------------------------------------------------------ > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list > -- _________________________________ Tim Wood, CLP, RHCT 719.338.7484 (tel) The Data Wranglers Web, Database & more since since 1994 www.datawranglers.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.w.pollux at gmail.com Mon Jul 28 07:54:09 2008 From: s.w.pollux at gmail.com (Pollux Su) Date: Mon, 28 Jul 2008 15:54:09 +0800 Subject: [Fedora-livecd-list] Some questions from a livecd newer In-Reply-To: <488D584A.2000805@datawranglers.com> References: <780ddc050807271944l3470d577h4ec5c4385546f214@mail.gmail.com> <488D584A.2000805@datawranglers.com> Message-ID: <780ddc050807280054y706c3144jd79f5bfa5b0fe2bb@mail.gmail.com> Hi tim: Thanks for your reply.I have build a livecd using livecd-fedora-8-base-desktop.ks file. There were more than 500 packages installed. If I adopt you approach to build the firefox livecd, it's too hard to minimize the iso file. I don't have idea to decide that which packages I need to remove or save and which services were not necessary. I just want to open a firefox browser when the system was booted. No login UI, no external service,no... just a clean desktop with a firefox browser. I thought it would be a little hard,but it seems very hard. Who can give me some suggestion?Any help will be appreciative. best regards thanks On Mon, Jul 28, 2008 at 1:25 PM, Tim Wood wrote: > Pollux, if you look through the kickstarts that are included, you'll find > a minimal kickstart. Do not use that as your starting point because the > login is disabled. You probably want to start with the minimal desktop. > Make sure that builds for you. Then, make a copy in the same directory. > Remove one or two packages you're sure you don't need. For instance, open > office. Then build another ISO. If that works, duplicate your kickstart > and repeat the process. When you get a kickstart that doesn't work, go back > to the last one that worked and try again. > > The kickstart file itself is very similar to the one used for automated > installs of RedHat. If you do a google search, you should be able to find > RedHat's kickstart documentation (hint, make site:redhat.com part of your > google search). > > The simplest way to find out what a package does is to pull up a terminal > on a fedora system and have yum tell you. If you wanted to know what > anaconda is: > > yum search anaconda > > Tim > > > Pollux Su wrote: > > Hi,all friends: > I was assigned a linux livecd task,but I am not familiar with linux. I > have finished a simple fedora livecd following the basic information I got > from here. Now,I have to build a minimal livecd with firefox, I think I want > to write ks file by myself base on kde ks file and add a firefox package. > But this iso file is very large for me. How can I do? > Thanks for your time? Where can I find the details of package which I > have to install and remove when I build a minimal firefox livecd. > > ------------------------------ > > -- > Fedora-livecd-list mailing listFedora-livecd-list at redhat.comhttps://www.redhat.com/mailman/listinfo/fedora-livecd-list > > > > -- > _________________________________ > Tim Wood, CLP, RHCT > 719.338.7484 (tel) > > The Data Wranglers > Web, Database & more since since 1994 > www.datawranglers.com > > > -- > 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 katzj at redhat.com Mon Jul 28 14:58:10 2008 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 28 Jul 2008 10:58:10 -0400 Subject: [Fedora-livecd-list] Recursive livecd-creator problem In-Reply-To: <488C2BD2.6080209@redhat.com> References: <488C2BD2.6080209@redhat.com> Message-ID: <1217257090.12821.13.camel@aglarond.local> On Sun, 2008-07-27 at 04:03 -0400, Warren Togami wrote: > The chroot created by livecd-creator has a blank /etc/resolv.conf, so > the inner imagecreator trying to create a chroot fails as it cannot > download repo metadata. > > I cannot simply copy /etc/resolv.conf from the host to the first level > chroot in %post since it is already running within the chroot at this > point. I then tried to use both %post --nochroot and %post in the same > kickstart file. > > It seems that %post --nochroot is ignored when you also have a %post? > Are both supposed to run (in what order?), or only %post? Both should run without any problems. In fact, the base livecd configs depend on this to set up things like the GPL and REAMDE on the top level of the cd. They'll run in the order that they exist within the config file for an arbitrary number of scripts -- we loop over them in imgcreate/creator.py:__run_post_scripts() > Similarly %pre and %post in the same kickstart script, %pre seems to be > ignored. %pre scripts in general are ignored right now because I'm not sure what the real use case for them is. In the installer case, it's to set up hardware. Which isn't really relevant for livecd-creator Jeremy From katzj at redhat.com Mon Jul 28 15:07:47 2008 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 28 Jul 2008 11:07:47 -0400 Subject: [Fedora-livecd-list] Re: livecd-creator unmounting temp image, running daemons. In-Reply-To: <46a038f90807271644t524c9a31s798ec84f9240dbb5@mail.gmail.com> References: <1217177555.25653.40.camel@S010600e029961c54.wp.shawcable.net> <46a038f90807271644t524c9a31s798ec84f9240dbb5@mail.gmail.com> Message-ID: <1217257667.12821.22.camel@aglarond.local> On Mon, 2008-07-28 at 11:44 +1200, Martin Langhoff wrote: > On Mon, Jul 28, 2008 at 4:52 AM, Jerry Vonau wrote: > > Your cc to the livecd list are not appearing there, are you subscribed? > > No - I thought it was an open list. I'll sub... Due to a ridiculous amount of spam, posts are limited to members only and everything else just gets dropped. Anything else is just not practical at this point for most lists :-/ Jeremy From dhuff at redhat.com Mon Jul 28 18:22:00 2008 From: dhuff at redhat.com (David Huff) Date: Mon, 28 Jul 2008 14:22:00 -0400 Subject: [Fedora-livecd-list] [PATCH] added compat shims in fs.py for old api In-Reply-To: <1217269320-10879-1-git-send-email-dhuff@redhat.com> References: <1216675616-20364-3-git-send-email-dhuff@redhat.com> <1217269320-10879-1-git-send-email-dhuff@redhat.com> Message-ID: <1217269320-10879-2-git-send-email-dhuff@redhat.com> Added a compat layer for backwards compatibility. These compat classes internally create the new Disk objects, switching the old api (LoopbackMount, SparseLoopbackMount, SparseExtLoopbackMount) types to the new Disk and Mount classes --- imgcreate/fs.py | 166 ++++++++---------------------------------------------- 1 files changed, 25 insertions(+), 141 deletions(-) diff --git a/imgcreate/fs.py b/imgcreate/fs.py index 16cbbba..933cadc 100644 --- a/imgcreate/fs.py +++ b/imgcreate/fs.py @@ -88,32 +88,16 @@ class BindChrootMount: self.mounted = False class LoopbackMount: + """LoopbackMount compatibility layer for old API""" def __init__(self, lofile, mountdir, fstype = None): - self.lofile = lofile - self.mountdir = mountdir - self.fstype = fstype - - self.mounted = False + self.diskmount = DiskMount(LoopbackDisk(lofile,size = 0),mountdir,fstype,rmmountdir = True) self.losetup = False - self.rmdir = False - self.loopdev = None - + def cleanup(self): - self.unmount() - self.lounsetup() + self.diskmount.cleanup() def unmount(self): - if self.mounted: - rc = subprocess.call(["/bin/umount", self.mountdir]) - if rc == 0: - self.mounted = False - - if self.rmdir and not self.mounted: - try: - os.rmdir(self.mountdir) - except OSError, e: - pass - self.rmdir = False + self.diskmount.unmount() def lounsetup(self): if self.losetup: @@ -143,152 +127,52 @@ class LoopbackMount: self.losetup = True def mount(self): - if self.mounted: - return - - self.loopsetup() - - if not os.path.isdir(self.mountdir): - os.makedirs(self.mountdir) - self.rmdir = True - - args = [ "/bin/mount", self.loopdev, self.mountdir ] - if self.fstype: - args.extend(["-t", self.fstype]) - - rc = subprocess.call(args) - if rc != 0: - raise MountError("Failed to mount '%s' to '%s'" % - (self.loopdev, self.mountdir)) - - self.mounted = True + self.diskmount.mount() class SparseLoopbackMount(LoopbackMount): + """SparseLoopbackMount compatibility layer for old API""" def __init__(self, lofile, mountdir, size, fstype = None): - LoopbackMount.__init__(self, lofile, mountdir, fstype) - self.size = size + self.diskmount = DiskMount(SparseLoopbackDisk(lofile,size),mountdir,fstype,rmmountdir = True) def expand(self, create = False, size = None): - flags = os.O_WRONLY - if create: - flags |= os.O_CREAT - makedirs(os.path.dirname(self.lofile)) - - if size is None: - size = self.size - - fd = os.open(self.lofile, flags) - - os.lseek(fd, size, 0) - os.write(fd, '\x00') - os.close(fd) + self.diskmount.disk.expand(create, size) def truncate(self, size = None): - if size is None: - size = self.size - fd = os.open(self.lofile, os.O_WRONLY) - os.ftruncate(fd, size) - os.close(fd) + self.diskmount.disk.truncate(size) def create(self): - self.expand(create = True) + self.diskmount.disk.create() class SparseExtLoopbackMount(SparseLoopbackMount): + """SparseExtLoopbackMount compatibility layer for old API""" def __init__(self, lofile, mountdir, size, fstype, blocksize, fslabel): - SparseLoopbackMount.__init__(self, lofile, mountdir, size, fstype) - self.blocksize = blocksize - self.fslabel = fslabel + self.diskmount = ExtDiskMount(SparseLoopbackDisk(lofile,size), mountdir, fstype, blocksize, fslabel, rmmountdir = True) + def __format_filesystem(self): - rc = subprocess.call(["/sbin/mkfs." + self.fstype, - "-F", "-L", self.fslabel, - "-m", "1", "-b", str(self.blocksize), - self.lofile, - str(self.size / self.blocksize)]) - if rc != 0: - raise MountError("Error creating %s filesystem" % (self.fstype,)) - subprocess.call(["/sbin/tune2fs", "-c0", "-i0", "-Odir_index", - "-ouser_xattr,acl", self.lofile]) + self.diskmount.__format_filesystem() def create(self): - SparseLoopbackMount.create(self) - self.__format_filesystem() + self.diskmount.disk.create() def resize(self, size = None): - current_size = os.stat(self.lofile)[stat.ST_SIZE] - - if size is None: - size = self.size - - if size == current_size: - return - - if size > current_size: - self.expand(size) - - self.__fsck() - - resize2fs(self.lofile, size) - - if size < current_size: - self.truncate(size) - return size + self.diskmount.__resize_filesystem(size) def mount(self): - if not os.path.isfile(self.lofile): - self.create() - else: - self.resize() - return SparseLoopbackMount.mount(self) - + self.diskmount.mount() + def __fsck(self): - subprocess.call(["/sbin/e2fsck", "-f", "-y", self.lofile]) + self.extdiskmount.__fsck() def __get_size_from_filesystem(self): - def parse_field(output, field): - for line in output.split("\n"): - if line.startswith(field + ":"): - return line[len(field) + 1:].strip() - - raise KeyError("Failed to find field '%s' in output" % field) - - dev_null = os.open("/dev/null", os.O_WRONLY) - try: - out = subprocess.Popen(['/sbin/dumpe2fs', '-h', self.lofile], - stdout = subprocess.PIPE, - stderr = dev_null).communicate()[0] - finally: - os.close(dev_null) - - return int(parse_field(out, "Block count")) * self.blocksize - + self.diskmount.__get_size_from_filesystem() + def __resize_to_minimal(self): - self.__fsck() - - # - # Use a binary search to find the minimal size - # we can resize the image to - # - bot = 0 - top = self.__get_size_from_filesystem() - while top != (bot + 1): - t = bot + ((top - bot) / 2) - - if not resize2fs(self.lofile, t): - top = t - else: - bot = t - return top - + self.diskmount.__resize_to_minimal() + def resparse(self, size = None): - self.cleanup() + self.diskmount.resparse(size) - minsize = self.__resize_to_minimal() - - self.truncate(minsize) - self.resize(size) - return minsize - class Disk: """ With the new disk API the image being produced can be partitioned into -- 1.5.4.1 From dhuff at redhat.com Mon Jul 28 18:21:59 2008 From: dhuff at redhat.com (David Huff) Date: Mon, 28 Jul 2008 14:21:59 -0400 Subject: [Fedora-livecd-list] [PATCH] added compat shims in fs.py for old api In-Reply-To: <1216675616-20364-3-git-send-email-dhuff@redhat.com> References: <1216675616-20364-3-git-send-email-dhuff@redhat.com> Message-ID: <1217269320-10879-1-git-send-email-dhuff@redhat.com> fixed compatibility issues as well as image resizing issues. I have tested this patch along with the other patches against the latest livecd tools with no issues. related patches needed: [PATCH] added get_partitions to kickstart.py [PATCH] re-factor imgcreate/fs.py module this one [PATCH] switch internal code to use new api From jonathan.w.miner at baesystems.com Mon Jul 28 19:34:54 2008 From: jonathan.w.miner at baesystems.com (Miner, Jonathan W (US SSA)) Date: Mon, 28 Jul 2008 15:34:54 -0400 Subject: [Fedora-livecd-list] fsck errors Message-ID: <5F14E67B470F4744925C0AE36E2E97590137D9AA@blums0006.bluelnk.net> Hi - Just started using livecd-creator (Fedora 9; livecd-tools.i386 017.1-1.fc9) and I seem to have a problem with files that I create during the %post phase not appearing on the CD. If I review the output of the livecd-creator command, I see messages similar to: | umount: /disk0/scratch/imgcreate-RK0UU5/install_root: device is busy | ioctl: LOOP_CLR_FD: Device or resource busy and | e2fsck 1.40.8 (13-Mar-2008) | Fedora-9-Gateway: recovering journal | Pass 1: Checking inodes, blocks, and sizes | Inode 18 has illegal block(s). Clear? yes | Illegal block #0 (811008) in inode 18. CLEARED. | Inode 18, i_blocks is 24, should be 16. Fix? yes | Inode 19 has illegal block(s). Clear? yes etc... I've fsck'ed a lot of drives during my career, and this does not look good. Maybe related is that after several builds my disk fills up, and the numbers from df and du don't match, suggesting that there are open files that are being deleted, and not released back into the free list: | # df -k /disk0 | Filesystem 1K-blocks Used Available Use% Mounted on | /dev/sda7 16876496 9157472 6847904 58% /disk0 | # du -sk /disk0 | 3940940 /disk0 Any ideas... is any of this normal? What can I do to debug this? From jean.rousseau at ssq.ca Mon Jul 28 19:38:59 2008 From: jean.rousseau at ssq.ca (jean.rousseau at ssq.ca) Date: Mon, 28 Jul 2008 15:38:59 -0400 Subject: [Fedora-livecd-list] Live CD ACPI Message-ID: Hi, Is it possible to put a script somewhere in the KS file who is gonna fix my live CD to always boot with ACPI=OFF If yes, can you tell me how. Regards
Ce message et tous les fichiers attach?s sont confidentiels et s'adressent exclusivement au(x) destinataire(s) indiqu?(s) ci-dessus. Si vous recevez ce message par erreur, veuillez le retourner ? l'exp?diteur et le d?truire. Tout usage, copie ou distribution non autoris?s de ce courriel sont strictement interdits.

This message and any attachments are confidential and intended solely for the above-mentioned recipient(s). If you have received this message in error, please return it to the sender and delete it from your files. Unauthorized use, copying or distribution of this e-mail is strictly prohibited.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From apevec at redhat.com  Mon Jul 28 20:00:47 2008
From: apevec at redhat.com (Alan Pevec)
Date: Mon, 28 Jul 2008 22:00:47 +0200
Subject: [Fedora-livecd-list] fsck errors
In-Reply-To: <5F14E67B470F4744925C0AE36E2E97590137D9AA@blums0006.bluelnk.net>
References: <5F14E67B470F4744925C0AE36E2E97590137D9AA@blums0006.bluelnk.net>
Message-ID: <488E256F.1000409@redhat.com>

Miner, Jonathan W (US SSA) wrote:
> If I review the output of the livecd-creator command, I see messages similar to:
> 
> | umount: /disk0/scratch/imgcreate-RK0UU5/install_root: device is busy
> | ioctl: LOOP_CLR_FD: Device or resource busy

Yeah, I've seen that too https://bugzilla.redhat.com/show_bug.cgi?id=430606#c10

I'm in the process of creating a reproducible test-case, then I'll reopen that BZ (and change summary which was just one side-effect)



From sebastian at when.com  Mon Jul 28 20:08:26 2008
From: sebastian at when.com (Sebastian Dziallas)
Date: Mon, 28 Jul 2008 22:08:26 +0200
Subject: [Fedora-livecd-list] Live CD ACPI
In-Reply-To: 
References: 
Message-ID: <488E273A.9060808@when.com>

jean.rousseau at ssq.ca wrote:
> Hi,
>  
> Is it possible to put a script somewhere in the KS file who is gonna fix 
> my live CD to always boot with ACPI=OFF
>  
> If yes, can you tell me how.
>  
> Regards

Hi Jean,

you could just add a line like this to your kickstart:

    bootloader --append="acpi=off" --location=mbr

I hope this helps.

Best Regards,
Sebastian Dziallas



From kanarip at kanarip.com  Mon Jul 28 20:44:55 2008
From: kanarip at kanarip.com (Jeroen van Meeuwen)
Date: Mon, 28 Jul 2008 22:44:55 +0200
Subject: [Fedora-livecd-list] [PATCH] first extend yum's exclude setting
Message-ID: <488E2FC7.7020609@kanarip.com>

First extending yum's exclude setting with packages excluded from the 
compose in the kickstart package manifest helps in group selection (see 
also #456882), since @core has a mandatory package called 
"fedora-logos". Although livecd-tools already removes the packages 
(after package and group selection) in the excluded list, I think this 
is cleaner as not even dependency resolving will know about the package 
explicitly excluded (and the package is thus not pulled in accidently, 
afterwards).

Kind regards,

Jeroen van Meeuwen
-kanarip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: first-exclude-packages.patch
Type: text/x-patch
Size: 676 bytes
Desc: not available
URL: 

From wtogami at redhat.com  Tue Jul 29 22:23:19 2008
From: wtogami at redhat.com (Warren Togami)
Date: Tue, 29 Jul 2008 18:23:19 -0400
Subject: [Fedora-livecd-list] Recursive livecd-creator problem
In-Reply-To: <1217257090.12821.13.camel@aglarond.local>
References: <488C2BD2.6080209@redhat.com>
	<1217257090.12821.13.camel@aglarond.local>
Message-ID: <488F9857.3040406@redhat.com>

Jeremy Katz wrote:
> On Sun, 2008-07-27 at 04:03 -0400, Warren Togami wrote:
>> The chroot created by livecd-creator has a blank /etc/resolv.conf, so 
>> the inner imagecreator trying to create a chroot fails as it cannot 
>> download repo metadata.
>>
>> I cannot simply copy /etc/resolv.conf from the host to the first level 
>> chroot in %post since it is already running within the chroot at this 
>> point.  I then tried to use both %post --nochroot and %post in the same 
>> kickstart file.
>>
>> It seems that %post --nochroot is ignored when you also have a %post?
>> Are both supposed to run (in what order?), or only %post?
> 
> Both should run without any problems.  In fact, the base livecd configs
> depend on this to set up things like the GPL and REAMDE on the top level
> of the cd.  They'll run in the order that they exist within the config
> file for an arbitrary number of scripts -- we loop over them in
> imgcreate/creator.py:__run_post_scripts()
> 

one.ks
two.ks includes one.ks
three.ks includes two.ks

one.ks has %post --nochroot
three.ks has %post

It seems %post --nochroot prior to %post in three.ks is ignored.  What I 
want to achieve works if I edit one.ks, but then I lose the ability to 
simply rely upon the existing defined Fedora Desktop LiveCD definitions.

Is this a bug in creator?

Warren Togami
wtogami at redhat.com



From katzj at redhat.com  Tue Jul 29 22:55:39 2008
From: katzj at redhat.com (Jeremy Katz)
Date: Tue, 29 Jul 2008 18:55:39 -0400
Subject: [Fedora-livecd-list] [PATCH] first extend yum's exclude setting
In-Reply-To: <488E2FC7.7020609@kanarip.com>
References: <488E2FC7.7020609@kanarip.com>
Message-ID: <1217372139.16534.10.camel@aglarond.local>

On Mon, 2008-07-28 at 22:44 +0200, Jeroen van Meeuwen wrote:
> First extending yum's exclude setting with packages excluded from the 
> compose in the kickstart package manifest helps in group selection (see 
> also #456882), since @core has a mandatory package called 
> "fedora-logos". Although livecd-tools already removes the packages 
> (after package and group selection) in the excluded list, I think this 
> is cleaner as not even dependency resolving will know about the package 
> explicitly excluded (and the package is thus not pulled in accidently, 
> afterwards).

The problem with this is that it's an (albeit subtle) change in what the
semantics of the kickstart config are.  The fact that you don't end up
with broken deps, even if you do something silly like -glibc, is
something that's been relatively important in the past.  And given that
you can do per-repo exclusion of packages, I don't know that switching
to - being an exclude vs a deselect is advantageous enough to outweigh
the loss wrt broken deps. 

Especially as any change here needs to be handled consistently across
all tools using kickstart files, not just livecd-creator.

Jeremy



From katzj at redhat.com  Tue Jul 29 22:57:21 2008
From: katzj at redhat.com (Jeremy Katz)
Date: Tue, 29 Jul 2008 18:57:21 -0400
Subject: [Fedora-livecd-list] Recursive livecd-creator problem
In-Reply-To: <488F9857.3040406@redhat.com>
References: <488C2BD2.6080209@redhat.com>
	<1217257090.12821.13.camel@aglarond.local>
	<488F9857.3040406@redhat.com>
Message-ID: <1217372241.16534.12.camel@aglarond.local>

On Tue, 2008-07-29 at 18:23 -0400, Warren Togami wrote:
> Jeremy Katz wrote:
> > On Sun, 2008-07-27 at 04:03 -0400, Warren Togami wrote:
> >> The chroot created by livecd-creator has a blank /etc/resolv.conf, so 
> >> the inner imagecreator trying to create a chroot fails as it cannot 
> >> download repo metadata.
> >>
> >> I cannot simply copy /etc/resolv.conf from the host to the first level 
> >> chroot in %post since it is already running within the chroot at this 
> >> point.  I then tried to use both %post --nochroot and %post in the same 
> >> kickstart file.
> >>
> >> It seems that %post --nochroot is ignored when you also have a %post?
> >> Are both supposed to run (in what order?), or only %post?
> > 
> > Both should run without any problems.  In fact, the base livecd configs
> > depend on this to set up things like the GPL and REAMDE on the top level
> > of the cd.  They'll run in the order that they exist within the config
> > file for an arbitrary number of scripts -- we loop over them in
> > imgcreate/creator.py:__run_post_scripts()
> > 
> 
> one.ks
> two.ks includes one.ks
> three.ks includes two.ks
> 
> one.ks has %post --nochroot
> three.ks has %post
> 
> It seems %post --nochroot prior to %post in three.ks is ignored.  What I 
> want to achieve works if I edit one.ks, but then I lose the ability to 
> simply rely upon the existing defined Fedora Desktop LiveCD definitions.

It should still be fine.  Again, this is directly relied upon in the
main desktop and kde live image configs.  Are you using %end to end all
of the sections of your configs?

> Is this a bug in creator?

As of yet, it doesn't look like it to me.  And with just hand-waving
about what you're doing, it's hard to say better.  You have the config
files, you have source code -- if you think it's a creator bug, add
debugging to the code and it should pop out pretty quickly.  The %post
stuff is pretty simple

Jeremy



From katzj at fedoraproject.org  Wed Jul 30 01:16:10 2008
From: katzj at fedoraproject.org (Jeremy Katz)
Date: Wed, 30 Jul 2008 01:16:10 +0000 (UTC)
Subject: [Fedora-livecd-list] tools/livecd-creator
Message-ID: <20080730011610.D28B512001F@lists.fedorahosted.org>

 tools/livecd-creator |    4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

New commits:
commit 9368a5d54d8414f882bb16f6a9d23aee50fcdf0f
Author: Jeremy Katz 
Date:   Tue Jul 29 21:15:20 2008 -0400

    Include arch as part of livecd suffix (#457163)

diff --git a/tools/livecd-creator b/tools/livecd-creator
index b5da7a2..b401190 100755
--- a/tools/livecd-creator
+++ b/tools/livecd-creator
@@ -20,6 +20,7 @@
 import os
 import os.path
 import sys
+import time
 import optparse
 import logging
 
@@ -101,7 +102,8 @@ def main():
 
         fs_label = imgcreate.build_name(options.kscfg,
                                         "livecd-",
-                                        maxlen = imgcreate.FSLABEL_MAXLEN)
+                                        maxlen = imgcreate.FSLABEL_MAXLEN,
+                                        suffix = "%s-%s" %(os.uname()[4], time.strftime("%Y%m%d%H%M")))
 
         logging.info("Using label '%s' and name '%s'" % (fs_label, name))
 




From fastiter at yahoo.fr  Wed Jul 30 04:39:04 2008
From: fastiter at yahoo.fr (El Kindi REZIG)
Date: Wed, 30 Jul 2008 06:39:04 +0200 (CEST)
Subject: [Fedora-livecd-list] installation of livecd fails
Message-ID: <401938.90066.qm@web23108.mail.ird.yahoo.com>

Hello,

I have some problems installing my live-cd onto the disk, the installation process hangs in the post installation stage, I have no idea of what went wrong, the partition is ext3 and I tried to install a livecd that I downloaded, and it was installed properly, however I can't install the livecds I'm making using livecd creator.

A lot of people face this problem, but apparently the solution isn't provided.

Best regards

       
---------------------------------
 Envoy? avec Yahoo! Mail.
Une boite mail plus intelligente. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From kanarip at kanarip.com  Wed Jul 30 08:53:48 2008
From: kanarip at kanarip.com (Jeroen van Meeuwen)
Date: Wed, 30 Jul 2008 10:53:48 +0200
Subject: [Fedora-livecd-list] [PATCH] first extend yum's exclude setting
In-Reply-To: <1217372139.16534.10.camel@aglarond.local>
References: <488E2FC7.7020609@kanarip.com>
	<1217372139.16534.10.camel@aglarond.local>
Message-ID: <48902C1C.9090404@kanarip.com>

Jeremy Katz wrote:
> On Mon, 2008-07-28 at 22:44 +0200, Jeroen van Meeuwen wrote:
>> First extending yum's exclude setting with packages excluded from the 
>> compose in the kickstart package manifest helps in group selection (see 
>> also #456882), since @core has a mandatory package called 
>> "fedora-logos". Although livecd-tools already removes the packages 
>> (after package and group selection) in the excluded list, I think this 
>> is cleaner as not even dependency resolving will know about the package 
>> explicitly excluded (and the package is thus not pulled in accidently, 
>> afterwards).
> 
> The problem with this is that it's an (albeit subtle) change in what the
> semantics of the kickstart config are.  The fact that you don't end up
> with broken deps, even if you do something silly like -glibc, is
> something that's been relatively important in the past.  And given that
> you can do per-repo exclusion of packages,

This sounds to me like moving the exclude functionality of the package 
manifest to the repo configuration directive...

  I don't know that switching
> to - being an exclude vs a deselect is advantageous enough to outweigh
> the loss wrt broken deps. 
> 

If you do something like -glibc you may have very good reasons for doing 
so. Note that -glibc and including 
customly-compiled-appliance-worthy-glibc is a very, very valid use case.

1) an explicit exclude should be excluded no matter what. Failed 
dependencies are a good indicator you have excluded the wrong package.

2) Randomly including what is explicitly indicated should be excluded 
changes the semantics of the kickstart package manifest from "a decent 
way to configure what packages should be on the system, and what 
packages should absolutely not" to a "monkey's selection of the 
available packages". If you can't reasonably, accurately predict what it 
does, it's done for.

> Especially as any change here needs to be handled consistently across
> all tools using kickstart files, not just livecd-creator.
> 

Well... actually only the tools using kickstart files that have 
exclusive dependency resolving. pungi for example has inclusive 
dependency resolving and ignores the explicit package manifest excludes 
as well, and for valid reasons as it is allowing conflicts in the 
package set because it's installation media and doesn't know what 
packages may or may not be preferred. Revisor then again allows 
exclusive dependency resolving as well and again is one of the tools on 
the list that is going to change (for the better, as I explained).

You give me a list of packages or tools that show this kind of behavour, 
please. I know anaconda is one of them, so what else?

Kind regards,

Jeroen van Meeuwen
-kanarip



From jonathan.w.miner at baesystems.com  Wed Jul 30 16:44:34 2008
From: jonathan.w.miner at baesystems.com (Miner, Jonathan W (US SSA))
Date: Wed, 30 Jul 2008 12:44:34 -0400
Subject: [Fedora-livecd-list] fsck errors
References: <5F14E67B470F4744925C0AE36E2E97590137D9AA@blums0006.bluelnk.net>
	<488E256F.1000409@redhat.com>
Message-ID: <5F14E67B470F4744925C0AE36E2E97590137D9B2@blums0006.bluelnk.net>

One work-around, based on two successful runs, is to put "sync;sync" at the end of my %post section.

It doesn't fix the device busy message, but it greatly reduced the number the errors from e2fsck... include the message that said I was a "BONEHEAD" for trying to fsck a mounted filesystem. Glad to see the author has a sense of humor! :)


-----Original Message-----
From:	fedora-livecd-list-bounces at redhat.com on behalf of Alan Pevec
Sent:	Mon 7/28/2008 4:00 PM
To:	fedora-livecd-list at redhat.com
Cc:	
Subject:	Re: [Fedora-livecd-list] fsck errors

Miner, Jonathan W (US SSA) wrote:
> If I review the output of the livecd-creator command, I see messages similar to:
> 
> | umount: /disk0/scratch/imgcreate-RK0UU5/install_root: device is busy
> | ioctl: LOOP_CLR_FD: Device or resource busy

Yeah, I've seen that too https://bugzilla.redhat.com/show_bug.cgi?id=430606#c10

I'm in the process of creating a reproducible test-case, then I'll reopen that BZ (and change summary which was just one side-effect)

--
Fedora-livecd-list mailing list
Fedora-livecd-list at redhat.com
https://www.redhat.com/mailman/listinfo/fedora-livecd-list




-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 3257 bytes
Desc: not available
URL: 

From fastiter at yahoo.fr  Wed Jul 30 19:22:26 2008
From: fastiter at yahoo.fr (El Kindi REZIG)
Date: Wed, 30 Jul 2008 21:22:26 +0200 (CEST)
Subject: [Fedora-livecd-list] installation of livecd fails
In-Reply-To: <401938.90066.qm@web23108.mail.ird.yahoo.com>
Message-ID: <284972.32768.qm@web23102.mail.ird.yahoo.com>


And here is my kickstart file.

Any hints would be appreciated.


El Kindi REZIG  a ?crit : Hello,

I have some problems installing my live-cd onto the disk, the installation process hangs in the post installation stage, I have no idea of what went wrong, the partition is ext3 and I tried to install a livecd that I downloaded, and it was installed properly, however I can't install the livecds I'm making using livecd creator.

A lot of people face this problem, but apparently the solution isn't provided.

Best regards
          

---------------------------------
  Envoy? avec Yahoo! Mail.
Une boite mail plus intelligente. --
Fedora-livecd-list mailing list
Fedora-livecd-list at redhat.com
https://www.redhat.com/mailman/listinfo/fedora-livecd-list


       
---------------------------------
 Envoy? avec Yahoo! Mail.
Une boite mail plus intelligente. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: livecd-fedora-8-xfce.ks
Type: application/octet-stream
Size: 5689 bytes
Desc: 3367647284-livecd-fedora-8-xfce.ks
URL: 

From katzj at redhat.com  Thu Jul 31 03:32:54 2008
From: katzj at redhat.com (Jeremy Katz)
Date: Wed, 30 Jul 2008 23:32:54 -0400
Subject: [Fedora-livecd-list] [PATCH] first extend yum's exclude setting
In-Reply-To: <48902C1C.9090404@kanarip.com>
References: <488E2FC7.7020609@kanarip.com>
	<1217372139.16534.10.camel@aglarond.local>
	<48902C1C.9090404@kanarip.com>
Message-ID: <1217475174.16534.116.camel@aglarond.local>

On Wed, 2008-07-30 at 10:53 +0200, Jeroen van Meeuwen wrote:
> Jeremy Katz wrote:
> > On Mon, 2008-07-28 at 22:44 +0200, Jeroen van Meeuwen wrote:
> >> First extending yum's exclude setting with packages excluded from the 
> >> compose in the kickstart package manifest helps in group selection (see 
> >> also #456882), since @core has a mandatory package called 
> >> "fedora-logos". Although livecd-tools already removes the packages 
> >> (after package and group selection) in the excluded list, I think this 
> >> is cleaner as not even dependency resolving will know about the package 
> >> explicitly excluded (and the package is thus not pulled in accidently, 
> >> afterwards).
> > 
> > The problem with this is that it's an (albeit subtle) change in what the
> > semantics of the kickstart config are.  The fact that you don't end up
> > with broken deps, even if you do something silly like -glibc, is
> > something that's been relatively important in the past.  And given that
> > you can do per-repo exclusion of packages,
> 
> This sounds to me like moving the exclude functionality of the package 
> manifest to the repo configuration directive...
> 
>   I don't know that switching
> > to - being an exclude vs a deselect is advantageous enough to outweigh
> > the loss wrt broken deps. 
> > 
> 
> If you do something like -glibc you may have very good reasons for doing 
> so. Note that -glibc and including 
> customly-compiled-appliance-worthy-glibc is a very, very valid use case.

And if you have
%packages
-glibc
customly-compiled-appliance-worthy-glibc

in your ks.cfg, then you'll get you the customly compiled one as long as
it satisfies all the deps.  If it _doesn't_, then yes, you might get
glibc pulled in

> 1) an explicit exclude should be excluded no matter what. Failed 
> dependencies are a good indicator you have excluded the wrong package.

Failed dependencies can indicate lots of things, depending on the
context.  And not all tools (anaconda being a notable case, pungi being
another afaik) will happily let you intsall/build trees with broken
deps, going for exclusion rather than deselection can lead to a
seriously hosed system

> 2) Randomly including what is explicitly indicated should be excluded 
> changes the semantics of the kickstart package manifest from "a decent 
> way to configure what packages should be on the system, and what 
> packages should absolutely not" to a "monkey's selection of the 
> available packages". If you can't reasonably, accurately predict what it 
> does, it's done for.

People have been using kickstart in this fashion for a long, long, long
time without it being "done for".  But I appreciate the hyperbole.

> > Especially as any change here needs to be handled consistently across
> > all tools using kickstart files, not just livecd-creator.
>
> Well... actually only the tools using kickstart files that have 
> exclusive dependency resolving. pungi for example has inclusive 
> dependency resolving and ignores the explicit package manifest excludes 
> as well, and for valid reasons as it is allowing conflicts in the 
> package set because it's installation media and doesn't know what 
> packages may or may not be preferred. Revisor then again allows 
> exclusive dependency resolving as well and again is one of the tools on 
> the list that is going to change (for the better, as I explained).
> 
> You give me a list of packages or tools that show this kind of behavour, 
> please. I know anaconda is one of them, so what else?

anaconda, pungi, livecd-creator, snake... that's off the top of my head.
But the bigger thing to change is people's *perception*.  If you're used
to one thing, changing those semantics is very dangerous and it's
something that we've been very very very careful to avoid doing with the
kickstart file format.  To the point of introducing entirely new syntax
in cases where there could be confusion.

Hence, why I say it's not clear to me why you wouldn't in this case just
do excludes at the repo level since that provides the same level of
functionality but without any of the fuzziness around changing the
semantics of the existing syntax

Jeremy



From wtogami at redhat.com  Thu Jul 31 04:04:55 2008
From: wtogami at redhat.com (Warren Togami)
Date: Thu, 31 Jul 2008 00:04:55 -0400
Subject: [Fedora-livecd-list] livecd-creator problem during enforcing
Message-ID: <489139E7.8060201@redhat.com>

Hi Eric,

 jeremy: btw, any idea why if I create a livecd while enforcing, 
the resulting image when booted cannot do /bin/su?
Permission denied
 jeremy: F9 host, F9 target image
 jeremy: it seems fine if I setenforce 0 before livecd-creator
 warren: with f9 updates?  if so, I *thought* all of the selinux 
userspace bits for enforcing had been pushed.  but I didn't keep that 
close of an eye on them.  eparis would be the one to ask

Currently if I make a LiveCD of F9 + updates on a F9 host, 
livecd-creator seems to succeed.  But if I boot that live image, I am 
unable to run /bin/su because of a denied permission.  setenforce 0 
prior to livecd-creator creates a working image.

Are we missing bits pushed to F9 updates that would allow enforcing to 
be enabled and to create a valid LiveCD image?

Warren Togami
wtogami at redhat.com



From wtogami at redhat.com  Thu Jul 31 04:59:20 2008
From: wtogami at redhat.com (Warren Togami)
Date: Thu, 31 Jul 2008 00:59:20 -0400
Subject: [Fedora-livecd-list] Re: livecd-creator problem during enforcing
In-Reply-To: <1217478693.2902.78.camel@localhost.localdomain>
References: <489139E7.8060201@redhat.com>
	<1217478693.2902.78.camel@localhost.localdomain>
Message-ID: <489146A8.6090708@redhat.com>

Eric Paris wrote:
>> Are we missing bits pushed to F9 updates that would allow enforcing to 
>> be enabled and to create a valid LiveCD image?
> 
> can you send me your kickstart file and I'll figure it out?
> 
> -Eric
> 

This image is a bit unique.  Please follow these directions exactly or 
it will likely fail due to the livecd-creator within another 
livecd-creator and the need to keep the cache away from the final image.

1) Put these three files into the same directory.
2) mkdir /tmp/cache
3) cd /tmp
4) setarch i386 livecd-creator --cache=/tmp/cache -c 
/path/to/live-ltsp-server.ks

Warren Togami
wtogami at redhat.com
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: livecd-fedora-9-base-desktop.ks
URL: 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: livecd-fedora-9-desktop.ks
URL: 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: live-ltsp-server.ks
URL: 

From kanarip at kanarip.com  Thu Jul 31 10:06:18 2008
From: kanarip at kanarip.com (Jeroen van Meeuwen)
Date: Thu, 31 Jul 2008 12:06:18 +0200
Subject: [Fedora-livecd-list] [PATCH] first extend yum's exclude setting
In-Reply-To: <1217475174.16534.116.camel@aglarond.local>
References: <488E2FC7.7020609@kanarip.com>	<1217372139.16534.10.camel@aglarond.local>	<48902C1C.9090404@kanarip.com>
	<1217475174.16534.116.camel@aglarond.local>
Message-ID: <48918E9A.6090109@kanarip.com>


Jeremy,

my final answer is on planet.fp.o right now.

-Jeroen