From kalabharath at gmail.com Sat Aug 1 16:26:04 2009 From: kalabharath at gmail.com (kala) Date: Sat, 1 Aug 2009 21:56:04 +0530 Subject: [Fedora-livecd-list] Hard disk install error for a Custom spin of Fedora 11 In-Reply-To: <7edc9ec40907301105o3b5f5268ifbe4c18c02a089ed@mail.gmail.com> References: <7edc9ec40907301105o3b5f5268ifbe4c18c02a089ed@mail.gmail.com> Message-ID: <7edc9ec40908010926l34a9002ckba4fd1752406b4f7@mail.gmail.com> Dear Friends I have created a custom live spin of fedora 11, the OS works fine while booting from USB or DVD but when it comes to hard disk installation it gives me an error which i couldnt able to solve. The first boot setup goes fine and at the end it gives me a flash of error screen ( I managed to get a screen shot of this which i am attaching as image) and then prompts me for login. when i give passwd and enter it tries to login but the login screen reappears (like cntrl+alt+backspace refreshing x server). even i couldnt login into terminal even as root which is says permission denyed. please help me solve the issue. http://opendiscovery.org.in/30-07-09_2318.jpg kala bharath -------------- next part -------------- An HTML attachment was scrubbed... URL: From zb211208 at 163.com Mon Aug 3 12:31:25 2009 From: zb211208 at 163.com (=?gbk?B?1tyx+Q==?=) Date: Mon, 3 Aug 2009 20:31:25 +0800 (CST) Subject: [Fedora-livecd-list] Hard disk install error for a Custom spin of Fedora 11 In-Reply-To: <7edc9ec40908010926l34a9002ckba4fd1752406b4f7@mail.gmail.com> References: <7edc9ec40908010926l34a9002ckba4fd1752406b4f7@mail.gmail.com> <7edc9ec40907301105o3b5f5268ifbe4c18c02a089ed@mail.gmail.com> Message-ID: <17815713.427081249302685168.JavaMail.coremail@bj163app60.163.com> hi? Sorry, I do not know this problem, In addition, I now can create livecd, but it can not boot from the hard drive, ?2009-08-02?kala ??? Dear Friends I have created a custom live spin of fedora 11, the OS works fine while booting from USB or DVD but when it comes to hard disk installation it gives me an error which i couldnt able to solve. The first boot setup goes fine and at the end it gives me a flash of error screen ( I managed to get a screen shot of this which i am attaching as image) and then prompts me for login. when i give passwd and enter it tries to login but the login screen reappears (like cntrl+alt+backspace refreshing x server). even i couldnt login into terminal even as root which is says permission denyed. please help me solve the issue. http://opendiscovery.org.in/30-07-09_2318.jpg kala bharath -------------- next part -------------- An HTML attachment was scrubbed... URL: From atodorov at redhat.com Tue Aug 4 15:57:57 2009 From: atodorov at redhat.com (Alexander Todorov) Date: Tue, 04 Aug 2009 18:57:57 +0300 Subject: [Fedora-livecd-list] Exclude docs when building livecd Message-ID: <4A785A85.3080706@redhat.com> Hi folks, on my eeepc I have the %_excludedocs rpm macro configured so that no man pages or other documentation is installed. How do I enable this when building a custom live cd? I want to save some space and man pages are not really necessary. Thanks, Alexander. From Marc.Herbert at gmail.com Tue Aug 4 16:17:29 2009 From: Marc.Herbert at gmail.com (Marc Herbert) Date: Tue, 04 Aug 2009 17:17:29 +0100 Subject: [Fedora-livecd-list] Re: Exclude docs and locales when building livecd In-Reply-To: <4A785A85.3080706@redhat.com> References: <4A785A85.3080706@redhat.com> Message-ID: Alexander Todorov a ?crit : > Hi folks, > on my eeepc I have the %_excludedocs rpm macro configured so that no man pages > or other documentation is installed. How do I enable this when building a custom > live cd? I want to save some space and man pages are not really necessary. To strip docs and locales from Fedora 10, I successfully use this: %packages --excludedocs --instLangs=en_GB.utf8:en_US.utf8 ... and this: %post localedef --list-archive | grep -v -i -E 'en_GB.utf8|en_US.utf8' | xargs localedef --delete-from-archive mv /usr/lib/locale/locale-archive /usr/lib/locale/locale-archive.tmpl /usr/sbin/build-locale-archive If the %post script looks like a hack, that's because it is. It is the least ugly solution I found to fight against the "all locales at any cost" current policy. Cheers, Marc From atodorov at redhat.com Tue Aug 4 16:39:54 2009 From: atodorov at redhat.com (Alexander Todorov) Date: Tue, 04 Aug 2009 19:39:54 +0300 Subject: [Fedora-livecd-list] Re: Exclude docs and locales when building livecd In-Reply-To: References: <4A785A85.3080706@redhat.com> Message-ID: <4A78645A.4060009@redhat.com> Marc Herbert wrote: > Alexander Todorov a ?crit : >> Hi folks, >> on my eeepc I have the %_excludedocs rpm macro configured so that no man pages >> or other documentation is installed. How do I enable this when building a custom >> live cd? I want to save some space and man pages are not really necessary. > > > To strip docs and locales from Fedora 10, I successfully use this: > > %packages --excludedocs --instLangs=en_GB.utf8:en_US.utf8 > > > ... and this: > > %post > localedef --list-archive | grep -v -i -E 'en_GB.utf8|en_US.utf8' | > xargs localedef --delete-from-archive > mv /usr/lib/locale/locale-archive /usr/lib/locale/locale-archive.tmpl > /usr/sbin/build-locale-archive > Thanks Marc, that was what I was looking for. Removing extra locales is also cool. -- Alexander. From deadbabylon at googlemail.com Thu Aug 6 13:28:03 2009 From: deadbabylon at googlemail.com (Sebastian Vahl) Date: Thu, 6 Aug 2009 15:28:03 +0200 Subject: [Fedora-livecd-list] No space left on device during image creation Message-ID: <20090806152803.78f2e1a8@netbook> I'm getting this error on my spins for x86_64 KDE live images (not for the i686 ones). Which device is meant here? On my local harddisks should be enough free space. Could this explain why the x86_64 images are ~40 megs bigger than the i686 ones? > error: /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora: import read failed(-1). > e2fsck 1.41.8 (11-July-2009) > Pass 1: Checking inodes, blocks, and sizes > Pass 2: Checking directory structure > Pass 3: Checking directory connectivity > Pass 4: Checking reference counts > Pass 5: Checking group summary information > F12-KDE-016-x86_: 88827/196608 files (0.1% non-contiguous), > 533419/786432 blocks e2image 1.41.8 (11-July-2009) > resize2fs 1.41.8 (11-July-2009) > /sbin/resize2fs: No space left on device while trying to > resize /daten/LIVECD/tmp/imgcreate-Z0Z6zr/tmp-hVegM7/ext3fs.img > Please run 'e2fsck > -fy /daten/LIVECD/tmp/imgcreate-Z0Z6zr/tmp-hVegM7/ext3fs.img' to fix > the filesystem after the aborted resize operation. Resizing the > filesystem > on /daten/LIVECD/tmp/imgcreate-Z0Z6zr/tmp-hVegM7/ext3fs.img to 532899 > (4k) blocks. e2fsck 1.41.8 (11-July-2009) Pass 1: Checking inodes, > blocks, and sizes Pass 2: Checking directory structure Pass 3: > Checking directory connectivity Pass 4: Checking reference counts > Pass 5: Checking group summary information F12-KDE-016-x86_: > 88827/196608 files (0.1% non-contiguous), 533419/786432 blocks > e2image 1.41.8 (11-July-2009) resize2fs 1.41.8 (11-July-2009) > The filesystem is already 786432 blocks long. Nothing to do! Sebastian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From atodorov at redhat.com Thu Aug 6 13:35:30 2009 From: atodorov at redhat.com (Alexander Todorov) Date: Thu, 06 Aug 2009 16:35:30 +0300 Subject: [Fedora-livecd-list] No space left on device during image creation In-Reply-To: <20090806152803.78f2e1a8@netbook> References: <20090806152803.78f2e1a8@netbook> Message-ID: <4A7ADC22.3030303@redhat.com> Sebastian Vahl ??????: > I'm getting this error on my spins for x86_64 KDE live images (not > for the i686 ones). Which device is meant here? On my local harddisks > should be enough free space. > Could this explain why the x86_64 images are ~40 megs bigger than the > i686 ones? > Try increasing the size of / in your ks.cfg. I'm not sure if livecd-tools takes this into account but I always give it a big value. -- Alexander. From deadbabylon at googlemail.com Thu Aug 6 14:46:13 2009 From: deadbabylon at googlemail.com (Sebastian Vahl) Date: Thu, 6 Aug 2009 16:46:13 +0200 Subject: [Fedora-livecd-list] No space left on device during image creation In-Reply-To: <4A7ADC22.3030303@redhat.com> References: <20090806152803.78f2e1a8@netbook> <4A7ADC22.3030303@redhat.com> Message-ID: <20090806164613.40b780ce@netbook> Am Thu, 06 Aug 2009 16:35:30 +0300 schrieb Alexander Todorov : > Sebastian Vahl ??????: > > I'm getting this error on my spins for x86_64 KDE live images (not > > for the i686 ones). Which device is meant here? On my local > > harddisks should be enough free space. > > Could this explain why the x86_64 images are ~40 megs bigger than > > the i686 ones? > > > > Try increasing the size of / in your ks.cfg. I'm not sure if > livecd-tools takes this into account but I always give it a big value. Don't work here. I've increased the size from 3072 (defined in fedora-live-base.ks) to 4096 -> same error. BTW: The spins guidelines [1] are stating this: > A Live Spin that fits on a CD should use part / 4096, which is in the > base kickstart already. But in fedora-live-base.ks from git it's still 3072. Sebastian [1] https://fedoraproject.org/wiki/Spins_Guidelines -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From smparrish at gmail.com Fri Aug 7 00:17:46 2009 From: smparrish at gmail.com (Steven M. Parrish) Date: Thu, 6 Aug 2009 20:17:46 -0400 Subject: [Fedora-livecd-list] No space left on device during image creation In-Reply-To: <20090806152803.78f2e1a8@netbook> References: <20090806152803.78f2e1a8@netbook> Message-ID: <200908062017.46489.smparrish@gmail.com> > I'm getting this error on my spins for x86_64 KDE live images (not > for the i686 ones). Which device is meant here? On my local harddisks > should be enough free space. > Could this explain why the x86_64 images are ~40 megs bigger than the > i686 ones? > > > error: /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora: import read failed(-1). > > e2fsck 1.41.8 (11-July-2009) > > Pass 1: Checking inodes, blocks, and sizes > > Pass 2: Checking directory structure > > Pass 3: Checking directory connectivity > > Pass 4: Checking reference counts > > Pass 5: Checking group summary information > > F12-KDE-016-x86_: 88827/196608 files (0.1% non-contiguous), > > 533419/786432 blocks e2image 1.41.8 (11-July-2009) > > resize2fs 1.41.8 (11-July-2009) > > /sbin/resize2fs: No space left on device while trying to > > resize /daten/LIVECD/tmp/imgcreate-Z0Z6zr/tmp-hVegM7/ext3fs.img > > Please run 'e2fsck > > -fy /daten/LIVECD/tmp/imgcreate-Z0Z6zr/tmp-hVegM7/ext3fs.img' to fix > > the filesystem after the aborted resize operation. Resizing the > > filesystem > > on /daten/LIVECD/tmp/imgcreate-Z0Z6zr/tmp-hVegM7/ext3fs.img to 532899 > > (4k) blocks. e2fsck 1.41.8 (11-July-2009) Pass 1: Checking inodes, > > blocks, and sizes Pass 2: Checking directory structure Pass 3: > > Checking directory connectivity Pass 4: Checking reference counts > > Pass 5: Checking group summary information F12-KDE-016-x86_: > > 88827/196608 files (0.1% non-contiguous), 533419/786432 blocks > > e2image 1.41.8 (11-July-2009) resize2fs 1.41.8 (11-July-2009) > > The filesystem is already 786432 blocks long. Nothing to do! > > Sebastian I was getting this error when building the OLPC releases. Turned out I was running out of space in /var/tmp where it builds the images. I have a small / with all the space in my /home. created at temporary build dir in my $HOME and used the --tmpdir= option when creating the image. Steven ===================================================== Steven M. Parrish ------------------------------------------------------------------------------------------------- gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar From deadbabylon at googlemail.com Fri Aug 7 07:00:22 2009 From: deadbabylon at googlemail.com (Sebastian Vahl) Date: Fri, 7 Aug 2009 09:00:22 +0200 Subject: [Fedora-livecd-list] No space left on device during image creation In-Reply-To: <200908062017.46489.smparrish@gmail.com> References: <20090806152803.78f2e1a8@netbook> <200908062017.46489.smparrish@gmail.com> Message-ID: <200908070900.29621.deadbabylon@googlemail.com> Am Freitag 07 August 2009 schrieb Steven M. Parrish: > I was getting this error when building the OLPC releases. Turned out I was > running out of space in /var/tmp where it builds the images. I have a > small / with all the space in my /home. created at temporary build dir in > my $HOME and used the --tmpdir= option when creating the image. Yes, I normally use "-tmpdir" to use a partition with enough free space. My / has 1G left free. But I've also tried to mount /tmp to another place and watch / during the process. Sebastian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From bronen at gmail.com Fri Aug 7 08:40:46 2009 From: bronen at gmail.com (Ronen B) Date: Fri, 7 Aug 2009 11:40:46 +0300 Subject: [Fedora-livecd-list] Iso Conversion to Live USB Message-ID: <859533090908070140n1b41160eh66d92c6a08de7638@mail.gmail.com> Hi guys, We have created a live ISO that was converted to Live USB, it seems to work fine, but we can't find any of the files that we have created in KS file (in the section of post --nochroot). the weird issue is that when booting the ISO using VirtualBox the files are available. Any suggestions? Thanks Ronen -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeevitha2006 at gmail.com Sat Aug 8 10:04:16 2009 From: jeevitha2006 at gmail.com (jeevitha) Date: Sat, 8 Aug 2009 15:04:16 +0500 Subject: [Fedora-livecd-list] Fedora10 live iso with graphical screen Message-ID: <1ff47e450908080304s5bb3d60euc5779669295c5364@mail.gmail.com> Hi, I created fedora10 livecd iso from its kickstart file. In default, Fedora 10 live iso have solar graphical booting screen. I am tring to change that to pulser graphical booting screen in fedora10 livecd iso. To set pulser grahical screen in live iso, i changed kickstart files as below 1) fedora-live-base.ks # fedora-live-base.ks # # Defines the basics for all kickstarts in the fedora-live branch # Does not include package selection (other then mandatory) # Does not include localization packages or configuration # # Does includes "default" language configuration (kickstarts including # this template can override these settings) lang en_US.UTF-8 keyboard us timezone US/Eastern auth --useshadow --enablemd5 selinux --enforcing firewall --enabled xconfig --startxonboot part / --size 3072 services --enabled=NetworkManager --disabled=network,sshd ##To use pulser plugin repo --name=MyPlugin --baseurl=file:///root/customization/plugin # To compose against the current release tree, use the following "repo" (enabled by default) repo --name=released --mirrorlist= http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-10&arch=$basearch # To include updates, use the following "repo" (enabled by default) #repo --name=updates --mirrorlist= http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f10&arch=$basearch # To compose against rawhide, use the following "repo" (disabled by default) #repo --name=rawhide --mirrorlist= http://mirrors.fedoraproject.org/mirrorlist?repo=rawhide&arch=$basearch # To compose against local trees, (edit and) use: #repo --name=f10 --baseurl= http://localrepo/fedora/releases/10/Everything/$basearch/os/ #repo --name=f10-updates --baseurl= http://localrepo/fedora/updates/10/$basearch/ %packages @base-x @base @core @fonts @admin-tools @dial-up @hardware-support @printing kernel memtest86+ plymouth-plugin-pulser #firstaidkit-plugin-all # save some space -specspo -esc -samba-client -a2ps -mpage -redhat-lsb -sox -hplip -hpijs sendmail #ssmtp -numactl -isdn4k-utils -autofs # smartcards won't really work on the livecd. -coolkey -ccid # duplicate functionality -pinfo -vorbis-tools -wget # lose the compat stuff -compat* # qlogic firmwares -ql2100-firmware -ql2200-firmware -ql23xx-firmware -ql2400-firmware # scanning takes quite a bit of space :/ -xsane -xsane-gimp -sane-backends # livecd bits to set up the livecd and be able to install anaconda isomd5sum # make sure debuginfo doesn't end up on the live image -*debuginfo %end %post ##pulser plugin setting /usr/sbin/plymouth-set-default-plugin pulser /usr/libexec/plymouth/plymouth-update-initrd # FIXME: it'd be better to get this installed from a package cat > /etc/rc.d/init.d/livesys << EOF #!/bin/bash # # live: Init script for live image # # chkconfig: 345 00 99 # description: Init script for live image. . /etc/init.d/functions if ! strstr "\`cat /proc/cmdline\`" liveimg || [ "\$1" != "start" ]; then exit 0 fi if [ -e /.liveimg-configured ] ; then configdone=1 fi exists() { which \$1 >/dev/null 2>&1 || return \$* } touch /.liveimg-configured # mount live image if [ -b \`readlink -f /dev/live\` ]; then mkdir -p /mnt/live mount -o ro /dev/live /mnt/live 2>/dev/null || mount /dev/live /mnt/live fi # enable swaps unless requested otherwise swaps=\`blkid -t TYPE=swap -o device\` if ! strstr "\`cat /proc/cmdline\`" noswap && [ -n "\$swaps" ] ; then for s in \$swaps ; do action "Enabling swap partition \$s" swapon \$s done fi if ! strstr "\`cat /proc/cmdline\`" noswap && [ -f /mnt/live/LiveOS/swap.img ] ; then action "Enabling swap file" swapon /mnt/live/LiveOS/swap.img fi mountPersistentHome() { # support label/uuid if [ "\${homedev##LABEL=}" != "\${homedev}" -o "\${homedev##UUID=}" != "\${homedev}" ]; then homedev=\`/sbin/blkid -o device -t "\$homedev"\` fi # if we're given a file rather than a blockdev, loopback it if [ "\${homedev##mtd}" != "\${homedev}" ]; then # mtd devs don't have a block device but get magic-mounted with -t jffs2 mountopts="-t jffs2" elif [ ! -b "\$homedev" ]; then loopdev=\`losetup -f\` if [ "\${homedev##/mnt/live}" != "\${homedev}" ]; then action "Remounting live store r/w" mount -o remount,rw /mnt/live fi losetup \$loopdev \$homedev homedev=\$loopdev fi # if it's encrypted, we need to unlock it if [ "\$(/lib/udev/vol_id -t \$homedev 2>/dev/null)" = "crypto_LUKS" ]; then echo echo "Setting up encrypted /home device" plymouth ask-for-password --command="cryptsetup luksOpen \$homedev EncHome" homedev=/dev/mapper/EncHome fi # and finally do the mount mount \$mountopts \$homedev /home # if we have /home under what's passed for persistent home, then # we should make that the real /home. useful for mtd device on olpc if [ -d /home/home ]; then mount --bind /home/home /home ; fi [ -x /sbin/restorecon ] && /sbin/restorecon /home if [ -d /home/liveuser ]; then USERADDARGS="-M" ; fi } findPersistentHome() { for arg in \`cat /proc/cmdline\` ; do if [ "\${arg##persistenthome=}" != "\${arg}" ]; then homedev=\${arg##persistenthome=} return fi done } if strstr "\`cat /proc/cmdline\`" persistenthome= ; then findPersistentHome elif [ -e /mnt/live/LiveOS/home.img ]; then homedev=/mnt/live/LiveOS/home.img fi # if we have a persistent /home, then we want to go ahead and mount it if ! strstr "\`cat /proc/cmdline\`" nopersistenthome && [ -n "\$homedev" ] ; then action "Mounting persistent /home" mountPersistentHome fi # make it so that we don't do writing to the overlay for things which # are just tmpdirs/caches mount -t tmpfs -o mode=0755 varcacheyum /var/cache/yum mount -t tmpfs tmp /tmp mount -t tmpfs vartmp /var/tmp [ -x /sbin/restorecon ] && /sbin/restorecon /var/cache/yum /tmp /var/tmp >/dev/null 2>&1 if [ -n "\$configdone" ]; then exit 0 fi # add fedora user with no passwd action "Adding live user" useradd \$USERADDARGS -c "Live System User" liveuser passwd -d liveuser > /dev/null # turn off firstboot for livecd boots chkconfig --level 345 firstboot off 2>/dev/null # don't start yum-updatesd for livecd boots chkconfig --level 345 yum-updatesd off 2>/dev/null # turn off mdmonitor by default chkconfig --level 345 mdmonitor off 2>/dev/null # turn off setroubleshoot on the live image to preserve resources chkconfig --level 345 setroubleshoot off 2>/dev/null # don't do packagekit checking by default gconftool-2 --direct --config-source=xml:readwrite:/etc/gconf/gconf.xml.defaults -s -t string /apps/gnome-packagekit/frequency_get_updates never >/dev/null gconftool-2 --direct --config-source=xml:readwrite:/etc/gconf/gconf.xml.defaults -s -t string /apps/gnome-packagekit/frequency_get_upgrades never >/dev/null gconftool-2 --direct --config-source=xml:readwrite:/etc/gconf/gconf.xml.defaults -s -t string /apps/gnome-packagekit/frequency_refresh_cache never >/dev/null gconftool-2 --direct --config-source=xml:readwrite:/etc/gconf/gconf.xml.defaults -s -t bool /apps/gnome-packagekit/notify_available false >/dev/null gconftool-2 --direct --config-source=xml:readwrite:/etc/gconf/gconf.xml.defaults -s -t bool /apps/gnome-packagekit/notify_distro_upgrades false >/dev/null gconftool-2 --direct --config-source=xml:readwrite:/etc/gconf/gconf.xml.defaults -s -t bool /apps/gnome-packagekit/enable_check_firmware false >/dev/null gconftool-2 --direct --config-source=xml:readwrite:/etc/gconf/gconf.xml.defaults -s -t bool /apps/gnome-packagekit/enable_check_hardware false >/dev/null gconftool-2 --direct --config-source=xml:readwrite:/etc/gconf/gconf.xml.defaults -s -t bool /apps/gnome-packagekit/enable_codec_helper false >/dev/null gconftool-2 --direct --config-source=xml:readwrite:/etc/gconf/gconf.xml.defaults -s -t bool /apps/gnome-packagekit/enable_font_helper false >/dev/null gconftool-2 --direct --config-source=xml:readwrite:/etc/gconf/gconf.xml.defaults -s -t bool /apps/gnome-packagekit/enable_mime_type_helper false >/dev/null # don't start cron/at as they tend to spawn things which are # disk intensive that are painful on a live image chkconfig --level 345 crond off 2>/dev/null chkconfig --level 345 atd off 2>/dev/null chkconfig --level 345 anacron off 2>/dev/null chkconfig --level 345 readahead_early off 2>/dev/null chkconfig --level 345 readahead_later off 2>/dev/null # Stopgap fix for RH #217966; should be fixed in HAL instead touch /media/.hal-mtab # workaround clock syncing on shutdown that we don't want (#297421) sed -i -e 's/hwclock/no-such-hwclock/g' /etc/rc.d/init.d/halt # and hack so that we eject the cd on shutdown if we're using a CD... if strstr "\`cat /proc/cmdline\`" CDLABEL= ; then cat >> /sbin/halt.local << FOE #!/bin/bash # we want to eject the cd on halt, but let's also try to avoid # io errors due to not being able to get files... cat /sbin/halt > /dev/null cat /sbin/reboot > /dev/null /usr/sbin/eject -p -m \$(readlink -f /dev/live) >/dev/null 2>&1 FOE chmod +x /sbin/halt.local fi EOF # bah, hal starts way too late cat > /etc/rc.d/init.d/livesys-late << EOF #!/bin/bash # # live: Late init script for live image # # chkconfig: 345 99 01 # description: Late init script for live image. . /etc/init.d/functions if ! strstr "\`cat /proc/cmdline\`" liveimg || [ "\$1" != "start" ] || [ -e /.liveimg-late-configured ] ; then exit 0 fi exists() { which \$1 >/dev/null 2>&1 || return \$* } touch /.liveimg-late-configured # read some variables out of /proc/cmdline for o in \`cat /proc/cmdline\` ; do case \$o in ks=*) ks="\${o#ks=}" ;; xdriver=*) xdriver="--set-driver=\${o#xdriver=}" ;; esac done # this is a bad hack to work around #460581 for the geode # purely to help move testing along for now if [ \`grep -c Geode /proc/cpuinfo\` -ne 0 ]; then cat > /etc/X11/xorg.conf <> /etc/rc.d/init.d/livesys << EOF # disable screensaver locking gconftool-2 --direct --config-source=xml:readwrite:/etc/gconf/gconf.xml.defaults -s -t bool /apps/gnome-screensaver/lock_enabled false >/dev/null # set up timed auto-login for after 60 seconds cat >> /etc/gdm/custom.conf << FOE [daemon] TimedLoginEnable=true TimedLogin=liveuser TimedLoginDelay=60 FOE EOF %end Error /usr/libexec/plymouth/plymouth-update-initrd: line 2: mkinitrd: command not found The above error occur while creating livecd iso. How to solve this error? Please help me to set pulser graphical screen as default in livecd iso. Thanks in advance, -------------- next part -------------- An HTML attachment was scrubbed... URL: From masterakee at yahoo.com Mon Aug 10 07:23:58 2009 From: masterakee at yahoo.com (Akila Nanayakkara) Date: Mon, 10 Aug 2009 00:23:58 -0700 (PDT) Subject: [Fedora-livecd-list] (no subject) Message-ID: <746758.83120.qm@web110010.mail.gq1.yahoo.com> i requested for dedora live cd or dvd. but i'm unaware of how to get it. here is my address, if you have any avalability send it to me. else give me a help to take it. thank you No 31/1A pahala imbulgoga, imbulgoda. Sri Lanka -------------- next part -------------- An HTML attachment was scrubbed... URL: From frankly3d at gmail.com Mon Aug 10 08:02:13 2009 From: frankly3d at gmail.com (Frank Murphy (Frankly3D)) Date: Mon, 10 Aug 2009 09:02:13 +0100 Subject: [Fedora-livecd-list] (no subject) In-Reply-To: <746758.83120.qm@web110010.mail.gq1.yahoo.com> References: <746758.83120.qm@web110010.mail.gq1.yahoo.com> Message-ID: <4A7FD405.3030109@gmail.com> On 10/08/09 08:23, Akila Nanayakkara wrote: > i requested for dedora live cd or dvd. but i'm unaware of how to get it. > > here is my address, if you have any avalability send it to me. else give > me a help to take it. thank you > > No 31/1A > pahala imbulgoga, > imbulgoda. > Sri Lanka > As the Freemedia is closed for maintenance August. Contact a local Fedora Ambassador: http://fedoraproject.org/wiki/Ambassadors/MembershipService/Verification#Sri_Lanka_.284.29 Regards, Frank From atodorov at redhat.com Mon Aug 10 16:01:09 2009 From: atodorov at redhat.com (Alexander Todorov) Date: Mon, 10 Aug 2009 19:01:09 +0300 Subject: [Fedora-livecd-list] LiveCD ks.cfg and livecd script Message-ID: <4A804445.1050006@redhat.com> Hi all, for my custom livecd I've used a slightly modified ks.cfg which I've taken from the web. The original ks.cfg was against F10 and includes a %post section which writes out /etc/init.d/livecd and /etc/init.d/livecd-late (IIRC) This is not the same in latest livecd-tools in F11: # cat livecd-fedora-minimal.ks lang en_US.UTF-8 keyboard us timezone US/Eastern auth --useshadow --enablemd5 selinux --enforcing firewall --disabled part / --size 2024 repo --name=development --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=rawhide&arch=$basearch %packages @core anaconda-runtime bash kernel passwd policycoreutils chkconfig authconfig rootfiles %end Can you tell me is the livecd script still required and if not what package takes care of setting up the live environment correctly. FYI: I've tried the above ks.cfg and it results in livecd which boots successfully. Regards, Alexander. From kushaldas at gmail.com Tue Aug 11 12:09:06 2009 From: kushaldas at gmail.com (Kushal Das) Date: Tue, 11 Aug 2009 17:39:06 +0530 Subject: [Fedora-livecd-list] Getting "Unable to install " error Message-ID: Hi, I am trying to work on fedora-livedvd-artstudio spin, as I added couple of new packages (like f-spot), livecd-creator is giving a strange error. I have more than 100GB of free space on /home The kickstart file can be found here [1] [root at testbox spin-kickstarts]# livecd-creator --config=fedora-livedvd-artstudio.ks --cache=cache/ --fslabel=fedora-artstudio -t /home/tmp mke2fs 1.41.4 (27-Jan-2009) Filesystem label=fedora-artstudio OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 196608 inodes, 786432 blocks 7864 blocks (1.00%) reserved for the super user First data block=0 Maximum filesystem blocks=805306368 24 block groups 32768 blocks per group, 32768 fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912 Writing inode tables: done Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 30 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. tune2fs 1.41.4 (27-Jan-2009) Setting maximal mount count to -1 Setting interval between checks to 0 seconds filespec_eval: hash table stats: 12 elements, 12/65536 buckets used, longest chain length 1 Retrieving http://mirrors.kernel.org/fedora/releases/11/Everything/i386/os/repodata/repomd.xml ...OK Retrieving http://mirror.uoregon.edu/fedora/linux/updates/11/i386/repodata/repomd.xml ...OK No such package *debuginfo to remove /usr/lib/python2.6/site-packages/imgcreate/errors.py:45: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6 return unicode(self.message) Error creating Live CD : Unable to install: [('installing package orca-2.26.3-1.fc11.i586 needs 6MB on the /home/tmp/imgcreate-aMjd0k/install_root filesystem', (9, '/home/tmp/imgcreate-aMjd0k/install_root', 6037504L)), ('installing package bug-buddy-1:2.26.0-2.fc11.i586 needs 9MB on the /home/tmp/imgcreate-aMjd0k/install_root filesystem', (9, '/home/tmp/imgcreate-aMjd0k/install_root', 8830976L)), ('installing package gvfs-gphoto2-1.2.3-9.fc11.i586 needs 9MB on the /home/tmp/imgcreate-aMjd0k/install_root filesystem', (9, '/home/tmp/imgcreate-aMjd0k/install_root', 9072640L)), ('installing package gvfs-fuse-1.2.3-9.fc11.i586 needs 9MB on the /home/tmp/imgcreate-aMjd0k/install_root filesystem', (9, '/home/tmp/imgcreate-aMjd0k/install_root', 9101312L)), ('installing package gvfs-smb-1.2.3-9.fc11.i586 needs 9MB on the /home/tmp/imgcreate-aMjd0k/install_root filesystem', (9, '/home/tmp/imgcreate-aMjd0k/install_root', 9408512L)), ('installing package gvfs-archive-1.2.3-9.fc11.i586 needs 10MB on the /home/tmp/imgcreate-aMjd0k/install_root filesystem', (9, '/home/tmp/imgcreate-aMjd0k/install_root', 9555968L)), ('installing package vino-2.26.2-1.fc11.i586 needs 12MB on the /home/tmp/imgcreate-aMjd0k/install_root filesystem', (9, '/home/tmp/imgcreate-aMjd0k/install_root', 11927552L)), ('installing package postr-0.12.3-2.fc11.noarch needs 13MB on the /home/tmp/imgcreate-aMjd0k/install_root filesystem', (9, '/home/tmp/imgcreate-aMjd0k/install_root', 12709888L)), ('installing package bluez-4.42-1.fc11.i586 needs 14MB on the /home/tmp/imgcreate-aMjd0k/install_root filesystem', (9, '/home/tmp/imgcreate-aMjd0k/install_root', 13955072L)), ('installing package pulseaudio-module-bluetooth-0.9.15-14.fc11.i586 needs 14MB on the /home/tmp/imgcreate-aMjd0k/install_root filesystem', (9, '/home/tmp/imgcreate-aMjd0k/install_root', 14168064L)), ('installing package gnome-bluetooth-2.27.5-1.fc11.i586 needs 15MB on the /home/tmp/imgcreate-aMjd0k/install_root filesystem', (9, '/home/tmp/imgcreate-aMjd0k/install_root', 15335424L)), ('installing package gnome-bluetooth-libs-2.27.5-1.fc11.i586 needs 15MB on the /home/tmp/imgcreate-aMjd0k/install_root filesystem', (9, '/home/tmp/imgcreate-aMjd0k/install_root', 15437824L))] Livecd tools version is : livecd-tools-024-1.fc11.i586 How to fix this ? [1] http://kushaldas.in/tmp/fedora-livedvd-artstudio.ks Kushal -- http://fedoraproject.org http://kushaldas.in From kalabharath at gmail.com Wed Aug 12 07:13:40 2009 From: kalabharath at gmail.com (kala) Date: Wed, 12 Aug 2009 12:43:40 +0530 Subject: [Fedora-livecd-list] Hard disk install error for a Custom spin of Fedora 11 In-Reply-To: <7edc9ec40908010926l34a9002ckba4fd1752406b4f7@mail.gmail.com> References: <7edc9ec40907301105o3b5f5268ifbe4c18c02a089ed@mail.gmail.com> <7edc9ec40908010926l34a9002ckba4fd1752406b4f7@mail.gmail.com> Message-ID: <7edc9ec40908120013n1c62a0b1h2547cddd4187ee2f@mail.gmail.com> Dear Friends I have created a custom live spin of fedora 11, the OS works fine while booting from USB or DVD but when it comes to hard disk installation it gives me an error which i couldnt able to solve. The first boot setup goes fine and at the end it gives me a flash of error screen ( I managed to get a screen shot of this which i am attaching as image) and then prompts me for login. when i give passwd and enter it tries to login but the login screen reappears (like cntrl+alt+backspace refreshing x server). even i couldnt login into terminal even as root which is says permission denyed. please help me solve the issue. http://opendiscovery.org.in/30-07-09_2318.jpg kala bharath -------------- next part -------------- An HTML attachment was scrubbed... URL: From wtogami at redhat.com Wed Aug 12 22:36:12 2009 From: wtogami at redhat.com (Warren Togami) Date: Wed, 12 Aug 2009 18:36:12 -0400 Subject: [Fedora-livecd-list] [PATCH] Handle initrd-generic dracut initrd's Message-ID: <4A8343DC.9010002@redhat.com> [PATCH] Handle initrd-generic dracut initrd's Currently dist-f12 koji repo, but not yet f12-alpha. diff --git a/imgcreate/live.py b/imgcreate/live.py index b98f7b3..c4381b2 100644 --- a/imgcreate/live.py +++ b/imgcreate/live.py @@ -361,8 +361,13 @@ class x86LiveImageCreator(LiveImageCreatorBase): shutil.copyfile(bootdir + "/vmlinuz-" + version, isodir + "/isolinux/vmlinuz" + index) - shutil.copyfile(bootdir + "/initrd-" + version + ".img", - isodir + "/isolinux/initrd" + index + ".img") + imgpath=bootdir + "/initrd-generic-" + version + ".img" + if os.path.exists(imgpath): + shutil.copyfile(imgpath, + isodir + "/isolinux/initrd" + index + ".img") + else: + shutil.copyfile(bootdir + "/initrd-" + version + ".img", + isodir + "/isolinux/initrd" + index + ".img") is_xen = False if os.path.exists(bootdir + "/xen.gz-" + version[:-3] From atodorov at redhat.com Thu Aug 13 10:46:00 2009 From: atodorov at redhat.com (Alexander Todorov) Date: Thu, 13 Aug 2009 13:46:00 +0300 Subject: [Fedora-livecd-list] Boot LiveCD over NFS Message-ID: <4A83EEE8.6060900@redhat.com> Good afternoon, I've tested Scientific Linux diskless livecd boot: http://www.livecd.ethz.ch/diskless.html It works like a charm. I found a similar page for Fedora: http://fedoraproject.org/wiki/Features/PXE-NFS_Boot_LiveCD The page says that Fedora livecd's are not capable of booting over nfs at the moment. Is anyone working on this? What is necessary to make the kernel and initrd from the livecd NFS aware? I'm willing to help implement this but not sure what needs to be done. Has anyone tried a similar configuration and wants to share how(if) they got it working? Regards, Alexander. From deadbabylon at googlemail.com Thu Aug 13 12:37:00 2009 From: deadbabylon at googlemail.com (Sebastian Vahl) Date: Thu, 13 Aug 2009 14:37:00 +0200 Subject: [Fedora-livecd-list] Big size difference in i686 and x86_64 versions of KDE live images Message-ID: <200908131437.00937.deadbabylon@googlemail.com> Hi, my KDE live images are showing a big size difference between the i686 and the x86_64 images (around 40 megs). The slighlty different package list couldn't explain this (i.e. atlas-sse (i686) vs. atlas (x86_64) is the only important difference). So I've compared the sizes of the installed packages (rpm -qa --qf "%{name} {size}\n" | sort -nr). Many packages are different in size but the kernel does have the biggest difference: i686: 78453688 x86_64: 103736431 A test spin of the GNOME images doesn't show this difference (only 2 megs). Does anybody has an explanation for this? Or can somebody try to create a x86_64 version for comparison (with livecd- creator and spins-kickstarts from git)? Sebastian [1] More package lists: https://fedoraproject.org/w/index.php?title=SebastianVahl/CurrentPackageList&oldid=118610 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From bruno at wolff.to Thu Aug 13 13:16:07 2009 From: bruno at wolff.to (Bruno Wolff III) Date: Thu, 13 Aug 2009 08:16:07 -0500 Subject: [Fedora-livecd-list] Big size difference in i686 and x86_64 versions of KDE live images In-Reply-To: <200908131437.00937.deadbabylon@googlemail.com> References: <200908131437.00937.deadbabylon@googlemail.com> Message-ID: <20090813131607.GA20407@wolff.to> On Thu, Aug 13, 2009 at 14:37:00 +0200, Sebastian Vahl wrote: > > Does anybody has an explanation for this? > Or can somebody try to create a x86_64 version for comparison (with livecd- > creator and spins-kickstarts from git)? It might be multilib related. For example if you pull in wine you will pull in i686 libraries that (sort of) duplicate libraries already pulled in for x86_64. For the games spin, I dropped wine for this reason as it put the x86_64 version of the spin over size. From deadbabylon at googlemail.com Thu Aug 13 14:10:46 2009 From: deadbabylon at googlemail.com (Sebastian Vahl) Date: Thu, 13 Aug 2009 16:10:46 +0200 Subject: [Fedora-livecd-list] Big size difference in i686 and x86_64 versions of KDE live images In-Reply-To: <20090813131607.GA20407@wolff.to> References: <200908131437.00937.deadbabylon@googlemail.com> <20090813131607.GA20407@wolff.to> Message-ID: <20090813161046.2de50a9d@netbook> Am Thu, 13 Aug 2009 08:16:07 -0500 schrieb Bruno Wolff III : > On Thu, Aug 13, 2009 at 14:37:00 +0200, > Sebastian Vahl wrote: > > > > Does anybody has an explanation for this? > > Or can somebody try to create a x86_64 version for comparison (with > > livecd- creator and spins-kickstarts from git)? > > It might be multilib related. For example if you pull in wine you > will pull in i686 libraries that (sort of) duplicate libraries > already pulled in for x86_64. For the games spin, I dropped wine for > this reason as it put the x86_64 version of the spin over size. Thanks for reminding me, I've forgotten to write this :) The x86_64 version does not contain any i?86 package. Sebastian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From maxamillion at gmail.com Thu Aug 13 14:12:17 2009 From: maxamillion at gmail.com (Adam Miller) Date: Thu, 13 Aug 2009 09:12:17 -0500 Subject: [Fedora-livecd-list] Big size difference in i686 and x86_64 versions of KDE live images In-Reply-To: <200908131437.00937.deadbabylon@googlemail.com> References: <200908131437.00937.deadbabylon@googlemail.com> Message-ID: On Thu, Aug 13, 2009 at 7:37 AM, Sebastian Vahl wrote: > x86_64 images (around 40 megs). The slighlty different package list couldn't > explain this (i.e. atlas-sse (i686) vs. atlas (x86_64) is the only important > difference). > So I've compared the sizes of the installed packages (rpm -qa --qf "%{name} > {size}\n" | sort -nr). Many packages are different in size but the kernel does > have the biggest difference: > i686: 78453688 > x86_64: 103736431 I haven't tested extensively just yet, but in a conversation with Kevin Fenzi the other day he noted that the 64-bit version of the Xfce spin was inflated by ~35MB or so because of dracut which is something we might need to adress with the dracut guys/gals/team/whatever. I don't know if the 32-bit version of the Xfce spin is also effected or not just yet, the compose I did on Monday I don't believe included dracut so I can't really say this is it for sure ... just something I thought I'd mention. -Adam -- http://maxamillion.googlepages.com --------------------------------------------------------- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments From deadbabylon at googlemail.com Thu Aug 13 18:22:08 2009 From: deadbabylon at googlemail.com (Sebastian Vahl) Date: Thu, 13 Aug 2009 20:22:08 +0200 Subject: [Fedora-livecd-list] Big size difference in i686 and x86_64 versions of KDE live images In-Reply-To: References: <200908131437.00937.deadbabylon@googlemail.com> Message-ID: <20090813202208.20ef8c89@netbook> Am Thu, 13 Aug 2009 09:12:17 -0500 schrieb Adam Miller : > On Thu, Aug 13, 2009 at 7:37 AM, Sebastian > Vahl wrote: > > > x86_64 images (around 40 megs). The slighlty different package list > > couldn't explain this (i.e. atlas-sse (i686) vs. atlas (x86_64) is > > the only important difference). > > So I've compared the sizes of the installed packages (rpm -qa --qf > > "%{name} {size}\n" | sort -nr). Many packages are different in size > > but the kernel does have the biggest difference: > > i686: 78453688 > > x86_64: 103736431 > > > I haven't tested extensively just yet, but in a conversation with > Kevin Fenzi the other day he noted that the 64-bit version of the Xfce > spin was inflated by ~35MB or so because of dracut which is something > we might need to adress with the dracut guys/gals/team/whatever. I > don't know if the 32-bit version of the Xfce spin is also effected or > not just yet, the compose I did on Monday I don't believe included > dracut so I can't really say this is it for sure ... just something I > thought I'd mention. Thanks, that was really helpful! First I've thought I've busted my build system. But it seems that I'm not the only one with this problem. But that my test spin of the gnome images seems not to be effected is a bit curious. I think I have to compare the package lists of the i686 and x86_64 version more closely. > -Adam > Sebastian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From katzj at redhat.com Thu Aug 13 21:57:36 2009 From: katzj at redhat.com (Jeremy Katz) Date: Thu, 13 Aug 2009 17:57:36 -0400 Subject: [Fedora-livecd-list] [PATCH] Handle initrd-generic dracut initrd's In-Reply-To: <4A8343DC.9010002@redhat.com> References: <4A8343DC.9010002@redhat.com> Message-ID: <20090813215736.GB519@redhat.com> On Wednesday, August 12 2009, Warren Togami said: > [PATCH] Handle initrd-generic dracut initrd's > Currently dist-f12 koji repo, but not yet f12-alpha. This doesn't apply cleanly, but also a minor style nit > diff --git a/imgcreate/live.py b/imgcreate/live.py > index b98f7b3..c4381b2 100644 > --- a/imgcreate/live.py > +++ b/imgcreate/live.py > @@ -361,8 +361,13 @@ class x86LiveImageCreator(LiveImageCreatorBase): > shutil.copyfile(bootdir + "/vmlinuz-" + version, > isodir + "/isolinux/vmlinuz" + index) > - shutil.copyfile(bootdir + "/initrd-" + version + ".img", > - isodir + "/isolinux/initrd" + index + ".img") > + imgpath=bootdir + "/initrd-generic-" + version + ".img" > + if os.path.exists(imgpath): > + shutil.copyfile(imgpath, > + isodir + "/isolinux/initrd" + index + ".img") The style in livecd-tools is to either see if a path exists and then set a variable or just use the path if it exists. eg if os.path.exists("/some/path"): myvar="/some/path" else: myvar="/some/other/path" shutil.copy(...) or if os.path.exists("/some/path"): shutil.copy("/some/path"...) else: ... Jeremy From katzj at redhat.com Thu Aug 13 21:58:22 2009 From: katzj at redhat.com (Jeremy Katz) Date: Thu, 13 Aug 2009 17:58:22 -0400 Subject: [Fedora-livecd-list] Boot LiveCD over NFS In-Reply-To: <4A83EEE8.6060900@redhat.com> References: <4A83EEE8.6060900@redhat.com> Message-ID: <20090813215821.GC519@redhat.com> On Thursday, August 13 2009, Alexander Todorov said: > I found a similar page for Fedora: > http://fedoraproject.org/wiki/Features/PXE-NFS_Boot_LiveCD > > The page says that Fedora livecd's are not capable of booting over nfs at the > moment. > > Is anyone working on this? What is necessary to make the kernel and initrd from > the livecd NFS aware? I'm willing to help implement this but not sure what needs > to be done. It basically requires a lot of initrd work. The good news is that with dracut we have a much better base for someone who wants to get it working rather than previously where the entirety of our netboot stack would have had to have been reimplemented just for live images Jeremy From katzj at fedoraproject.org Fri Aug 14 14:52:40 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Fri, 14 Aug 2009 14:52:40 +0000 (UTC) Subject: [Fedora-livecd-list] 3 commits - imgcreate/fs.py imgcreate/kickstart.py Makefile Message-ID: <20090814145240.A630C120197@lists.fedorahosted.org> Makefile | 2 +- imgcreate/fs.py | 2 +- imgcreate/kickstart.py | 12 +++++------- 3 files changed, 7 insertions(+), 9 deletions(-) New commits: commit ff31b963edb642ae210455cf38a88392feb84a9f Author: Jeremy Katz Date: Fri Aug 14 10:50:59 2009 -0400 If resize2fs fails, raise an error also (related to #517222) diff --git a/imgcreate/fs.py b/imgcreate/fs.py index 563b7a9..a9512f2 100644 --- a/imgcreate/fs.py +++ b/imgcreate/fs.py @@ -68,7 +68,7 @@ def resize2fs(fs, size = None, minimal = False): args.append("%sK" %(size / 1024,)) ret = subprocess.call(args) if ret != 0: - return ret + raise ResizeError("resize2fs returned an error (%d)! image to debug at %s" %(ret, saved_image)) if e2fsck(fs) != 0: raise ResizeError("fsck after resize returned an error! image to debug at %s" %(saved_image,)) commit b1496d9f5ee11c42ca4446eb5e4da9de025500cd Author: Jeremy Katz Date: Thu Jul 30 16:43:42 2009 -0400 Bumpv ersion diff --git a/Makefile b/Makefile index a3b2aa9..68cb635 100644 --- a/Makefile +++ b/Makefile @@ -1,5 +1,5 @@ -VERSION = 024 +VERSION = 025 INSTALL = /usr/bin/install -c INSTALL_PROGRAM = ${INSTALL} commit 8d1a422ca611e7f05da8f8f3b8e46c7d3bcb4e86 Author: Jeremy Katz Date: Mon Jul 27 09:26:58 2009 -0400 Use system-config-keyboard's bits in preference to rhpl.keyboard system-config-keyboard >= 1.3.0 has support for the keyboard pieces that used to be in rhpl. Use them if we can but fall back gracefully as people running from git could be on older releases diff --git a/imgcreate/kickstart.py b/imgcreate/kickstart.py index 83a62e4..98db856 100644 --- a/imgcreate/kickstart.py +++ b/imgcreate/kickstart.py @@ -24,7 +24,10 @@ import time import logging import urlgrabber -import rhpl.keyboard +try: + import system_config_keyboard.keyboard as keyboard +except ImportError: + import rhpl.keyboard as keyboard import pykickstart.commands as kscommands import pykickstart.constants as ksconstants @@ -132,12 +135,7 @@ class LanguageConfig(KickstartConfig): class KeyboardConfig(KickstartConfig): """A class to apply a kickstart keyboard configuration to a system.""" def apply(self, kskeyboard): - # - # FIXME: - # should this impact the X keyboard config too? - # or do we want to make X be able to do this mapping? - # - k = rhpl.keyboard.Keyboard() + k = keyboard.Keyboard() if kskeyboard.keyboard: k.set(kskeyboard.keyboard) k.write(self.instroot) From mads at kiilerich.com Fri Aug 14 22:44:55 2009 From: mads at kiilerich.com (Mads Kiilerich) Date: Sat, 15 Aug 2009 00:44:55 +0200 Subject: [Fedora-livecd-list] Custom initrd Message-ID: <4A85E8E7.7040302@kiilerich.com> I am using livecd-creator from livecd-tools-024-1.fc11.i586 and need to customize the initrd. But I have problems making it work and figuring out what is going on. I have figured out that livecd-creator through imgcreate creates a /etc/sysconfig/mkinitrd. When rpms runs mkinitrd from their %post script then it will exec mkliveinitrd and use the configured module list. AFAICS livecd-creator then picks up the initrd from /boot, and the end result after having written the iso to usb with livecd-iso-to-disk is that it ends up in /syslinux/initrd0.img. But if I overwrite the /boot/initrd* in %post like this: /sbin/mkinitrd -f /boot/initrd-$(rpm -q kernel --qf '%{version}-%{release}.%{arch}\n').img $(rpm -q kernel --qf '%{version}-%{release}.%{arch}\n') then it won't be used. What am I doing wrong? When is the initrd picked up? What is the code flow? If I make %post preserve /etc/sysconfig/mkinitrd and boots from usb and restores /etc/sysconfig/mkinitrd and runs /sbin/mkinitrd -f /mnt/live/syslinux/initrd0.img $(rpm -q kernel --qf "%{version}-%{release}.%{arch}\n") then it works as expected. /Mads From katzj at redhat.com Sat Aug 15 02:45:47 2009 From: katzj at redhat.com (Jeremy Katz) Date: Fri, 14 Aug 2009 22:45:47 -0400 Subject: [Fedora-livecd-list] Custom initrd In-Reply-To: <4A85E8E7.7040302@kiilerich.com> References: <4A85E8E7.7040302@kiilerich.com> Message-ID: <20090815024546.GB37097@redhat.com> On Saturday, August 15 2009, Mads Kiilerich said: > I have figured out that livecd-creator through imgcreate creates a > /etc/sysconfig/mkinitrd. When rpms runs mkinitrd from their %post script > then it will exec mkliveinitrd and use the configured module list. > AFAICS livecd-creator then picks up the initrd from /boot, and the end > result after having written the iso to usb with livecd-iso-to-disk is > that it ends up in /syslinux/initrd0.img. Correct > But if I overwrite the /boot/initrd* in %post like this: > /sbin/mkinitrd -f /boot/initrd-$(rpm -q kernel --qf > '%{version}-%{release}.%{arch}\n').img $(rpm -q kernel --qf > '%{version}-%{release}.%{arch}\n') > then it won't be used. > > What am I doing wrong? When is the initrd picked up? What is the code flow? %post runs after we've set up the boot loader bits. Otherwise, it %wouldn't be the last thing run. So if you want to do this, you have to do something like we did for Fedora 8 on the initial move of initramfs stuff into mkinitrd proper. See commit 11dbd0bb5ba4b845e80109e990e4e780ca402218 Also note that all of this is subject to some amount of change in Fedora 12 with the move to using dracut instead of mkinitrd Jeremy From mads at kiilerich.com Sat Aug 15 09:17:54 2009 From: mads at kiilerich.com (Mads Kiilerich) Date: Sat, 15 Aug 2009 11:17:54 +0200 Subject: [Fedora-livecd-list] Custom initrd In-Reply-To: <20090815024546.GB37097@redhat.com> References: <4A85E8E7.7040302@kiilerich.com> <20090815024546.GB37097@redhat.com> Message-ID: <4A867D42.6000104@kiilerich.com> Jeremy Katz wrote, On 08/15/2009 04:45 AM: > On Saturday, August 15 2009, Mads Kiilerich said: > >> I have figured out that livecd-creator through imgcreate creates a >> /etc/sysconfig/mkinitrd. When rpms runs mkinitrd from their %post script >> then it will exec mkliveinitrd and use the configured module list. >> AFAICS livecd-creator then picks up the initrd from /boot, and the end >> result after having written the iso to usb with livecd-iso-to-disk is >> that it ends up in /syslinux/initrd0.img. >> > Correct > > >> But if I overwrite the /boot/initrd* in %post like this: >> /sbin/mkinitrd -f /boot/initrd-$(rpm -q kernel --qf >> '%{version}-%{release}.%{arch}\n').img $(rpm -q kernel --qf >> '%{version}-%{release}.%{arch}\n') >> then it won't be used. >> >> What am I doing wrong? When is the initrd picked up? What is the code flow? >> > %post runs after we've set up the boot loader bits. Otherwise, it > %wouldn't be the last thing run. I intuitively expected %post to be the last step in the kickstart process, but to come before the "taking a snapshot of the chroot and transforming it to something bootable" part. But no one size fits all. Ok. Perhaps different %posts could make some things simpler. > So if you want to do this, you have to > do something like we did for Fedora 8 on the initial move of initramfs > stuff into mkinitrd proper. See commit > 11dbd0bb5ba4b845e80109e990e4e780ca402218 > Oh yeah. livecd-creator thinks (knows) that it is creating a CD, and thus the initrd is (has to be) in $LIVE_ROOT/isolinux/initrd0.img. So /sbin/mkinitrd -f $LIVE_ROOT/isolinux/initrd0.img $(rpm -q kernel --qf "%{version}-%{release}.%{arch}") in %post should do the trick? I will try that. I tried and was looking for $LIVE_ROOT/syslinux/initrd0.img as it can be seen on running USB sticks, but that mangling is only done later by livecd-iso-to-disk ... I have had some problems with things copied to $LIVE_ROOT in nonchrooted %post not showing up on the final system, but that might be livecd-iso-to-disk too - I will try harder. Thanks! /Mads From atodorov at redhat.com Sat Aug 15 20:39:47 2009 From: atodorov at redhat.com (Alexander Todorov) Date: Sat, 15 Aug 2009 23:39:47 +0300 Subject: [Fedora-livecd-list] Why resize back ext3fs.img to bigger size. Message-ID: <4A871D13.50002@redhat.com> Hi, in fs.py in ExtDiskMount.resparse() function we resize and truncate the image to minimum possible size (i.e. ext3 becomes 100% full) and then resize it back to the size specified in kickstart. In most cases this results in ext3fs.img which when mounted has lots of free space on it. Why is that ? It can be avoided by this simple patch: --------------------------------- imgcreate/fs.py | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/imgcreate/fs.py b/imgcreate/fs.py index 563b7a9..50ec5e7 100644 --- a/imgcreate/fs.py +++ b/imgcreate/fs.py @@ -470,7 +470,6 @@ class ExtDiskMount(DiskMount): self.cleanup() minsize = self.__resize_to_minimal() self.disk.truncate(minsize) - self.__resize_filesystem(size) return minsize class DeviceMapperSnapshot(object): From mads at kiilerich.com Sat Aug 15 23:17:41 2009 From: mads at kiilerich.com (Mads Kiilerich) Date: Sun, 16 Aug 2009 01:17:41 +0200 Subject: [Fedora-livecd-list] Why resize back ext3fs.img to bigger size. In-Reply-To: <4A871D13.50002@redhat.com> References: <4A871D13.50002@redhat.com> Message-ID: <4A874215.7030802@kiilerich.com> Alexander Todorov wrote, On 08/15/2009 10:39 PM: > Hi, > in fs.py in ExtDiskMount.resparse() function we resize and truncate the image to > minimum possible size (i.e. ext3 becomes 100% full) and then resize it back to > the size specified in kickstart. In most cases this results in ext3fs.img which > when mounted has lots of free space on it. > > > Why is that ? > Perhaps it is because unused space might contain old data which probably compresses badly. By doing it this way the extended space will be initialized with zeroes which can be compressed to (almost) nothing, and the compressed image of the specified size thus doesn't take up more space than if it had the minimal size. Why is that a problem? /Mads From katzj at redhat.com Sun Aug 16 00:10:53 2009 From: katzj at redhat.com (Jeremy Katz) Date: Sat, 15 Aug 2009 20:10:53 -0400 Subject: [Fedora-livecd-list] Why resize back ext3fs.img to bigger size. In-Reply-To: <4A874215.7030802@kiilerich.com> References: <4A871D13.50002@redhat.com> <4A874215.7030802@kiilerich.com> Message-ID: <20090816001052.GA37640@redhat.com> On Sunday, August 16 2009, Mads Kiilerich said: > Alexander Todorov wrote, On 08/15/2009 10:39 PM: >> Hi, >> in fs.py in ExtDiskMount.resparse() function we resize and truncate the image to >> minimum possible size (i.e. ext3 becomes 100% full) and then resize it back to >> the size specified in kickstart. In most cases this results in ext3fs.img which >> when mounted has lots of free space on it. >> >> Why is that ? > > Perhaps it is because unused space might contain old data which probably > compresses badly. By doing it this way the extended space will be > initialized with zeroes which can be compressed to (almost) nothing, and > the compressed image of the specified size thus doesn't take up more > space than if it had the minimal size. Correct. And by having the free space, we are able to let you write things to the filesystem when you're running the live image rather than having every write operation return -ENOSPC. We also keep around a snapshot of the minimal image so that we use the minimal image as the basis to copy over after an install from the live image (and then we resize that minimal image on the disk to the size of the partition you created) Jeremy From katzj at redhat.com Sun Aug 16 00:14:56 2009 From: katzj at redhat.com (Jeremy Katz) Date: Sat, 15 Aug 2009 20:14:56 -0400 Subject: [Fedora-livecd-list] Custom initrd In-Reply-To: <4A867D42.6000104@kiilerich.com> References: <4A85E8E7.7040302@kiilerich.com> <20090815024546.GB37097@redhat.com> <4A867D42.6000104@kiilerich.com> Message-ID: <20090816001455.GB37640@redhat.com> On Saturday, August 15 2009, Mads Kiilerich said: > Jeremy Katz wrote, On 08/15/2009 04:45 AM: >> On Saturday, August 15 2009, Mads Kiilerich said: >>> What am I doing wrong? When is the initrd picked up? What is the code flow? >>> >> %post runs after we've set up the boot loader bits. Otherwise, it >> %wouldn't be the last thing run. > > I intuitively expected %post to be the last step in the kickstart > process, but to come before the "taking a snapshot of the chroot and > transforming it to something bootable" part. But no one size fits all. > Ok. Perhaps different %posts could make some things simpler. Yep, it's unfortunate but either way makes someone unhappy :/ Being consistent and saying "last means last" helps a lot there >> So if you want to do this, you have to >> do something like we did for Fedora 8 on the initial move of initramfs >> stuff into mkinitrd proper. See commit >> 11dbd0bb5ba4b845e80109e990e4e780ca402218 > > Oh yeah. livecd-creator thinks (knows) that it is creating a CD, and > thus the initrd is (has to be) in $LIVE_ROOT/isolinux/initrd0.img. > > So > /sbin/mkinitrd -f $LIVE_ROOT/isolinux/initrd0.img $(rpm -q kernel > --qf "%{version}-%{release}.%{arch}") > in %post should do the trick? I will try that. Nope -- really, look at the commit[1]. You need the two separate %post sections as it shows you; you can't do just one > I tried and was looking for $LIVE_ROOT/syslinux/initrd0.img as it can be > seen on running USB sticks, but that mangling is only done later by > livecd-iso-to-disk ... Yep > I have had some problems with things copied to $LIVE_ROOT in nonchrooted > %post not showing up on the final system, but that might be > livecd-iso-to-disk too - I will try harder. Generally we don't copy most things from the CD to the usb stick because we don't know which things matter and then also don't know how to clean the stick, etc if you want to replace things. Other ideas welcome, but probably best implemented in liveusb-creator rather than livecd-iso-to-disk. Jeremy [1] http://git.fedorahosted.org/git/livecd?p=livecd;a=commit;h=11dbd0bb5ba4b845e80109e990e4e780ca402218 From mads at kiilerich.com Sun Aug 16 11:54:14 2009 From: mads at kiilerich.com (Mads Kiilerich) Date: Sun, 16 Aug 2009 13:54:14 +0200 Subject: [Fedora-livecd-list] Custom initrd In-Reply-To: <20090816001455.GB37640@redhat.com> References: <4A85E8E7.7040302@kiilerich.com> <20090815024546.GB37097@redhat.com> <4A867D42.6000104@kiilerich.com> <20090816001455.GB37640@redhat.com> Message-ID: <4A87F366.1060601@kiilerich.com> Jeremy Katz wrote, On 08/16/2009 02:14 AM: >>> So if you want to do this, you have to >>> do something like we did for Fedora 8 on the initial move of initramfs >>> stuff into mkinitrd proper. See commit >>> 11dbd0bb5ba4b845e80109e990e4e780ca402218 >>> >> Oh yeah. livecd-creator thinks (knows) that it is creating a CD, and >> thus the initrd is (has to be) in $LIVE_ROOT/isolinux/initrd0.img. >> >> So >> /sbin/mkinitrd -f $LIVE_ROOT/isolinux/initrd0.img $(rpm -q kernel >> --qf "%{version}-%{release}.%{arch}") >> in %post should do the trick? I will try that. >> > Nope -- really, look at the commit[1]. You need the two separate %post > sections as it shows you; you can't do just one > Ok, thanks. I'm trying to understand which parts of that commit is essential to me. So it is because LIVE_ROOT only is available in not in_chroot %post scripts? And the initrd thus has to be created in a normal chrooted %post and copied to the right location in a non-chrooted %post? Is there any particular reason why LIVE_ROOT isn't available in chroots? Couldn't the image always mounted under $INSTALL_ROOT/mnt/live? Or bind-mounted? /Mads From patrice.guay at nanotechnologies.qc.ca Sun Aug 16 16:31:58 2009 From: patrice.guay at nanotechnologies.qc.ca (Patrice Guay) Date: Sun, 16 Aug 2009 12:31:58 -0400 Subject: [Fedora-livecd-list] xen livecd creation Message-ID: <4A88347E.6020407@nanotechnologies.qc.ca> I'm trying to create a LiveCD with a xen enabled kernel (kernel-xen). I'm using livecd-tools 013 (the last compatible version with CentOS5). Creating a regular LiveCD works fine but I'm having trouble with the Xen LiveCD. The following files are created under the isolinux directory: > boot.cat > initrd0.img > isolinux.bin > isolinux.cfg > mboot.c32 > splash.jpg > vesamenu.c32 > vmlinuz0 > xen0.gz Here is the relevant content of isolinux.cfg: > default vesamenu.c32 > timeout 100 > > [...] > > label linux0 > menu label Xen LiveCD > kernel mboot.c32 > append xen0.gz --- vmlinuz0 --- initrd0.img root=CDLABEL=xen rootfstype=iso9660 ro quiet liveimg > menu default And here is the boot messages I get: > [...] > NET: Registered protocol family 17 > Using IP] No-Shortcut mod > Freeing unused kernel memory: 176k freed > Write protecting the kernel read-only data: 383k > 4gb seg fixup, process init (pid 1), cs:ip 73:00xxxxxx > 4gb seg fixup, process init (pid 1), cs:ip 73:00xxxxxx > 4gb seg fixup, process init (pid 1), cs:ip 73:00xxxxxx > [...] > 4gb seg fixup, process init (pid 1), cs:ip 73:00xxxxxx > kernel commandline: > fstab suggests root=/dev/mapper/livecd-rw > fstab suggests rootflags=defaults,noatime > fstab suggests rootfstype=ext3 > init=/sbin/init > root=/dev/mapper/livecd-rw > rootflags=defaults,noatime > rootfstype=ext3 > root_ro=0 > root_rw=0 > SCSI subsystem initialized > loop: loaded (max 16 devices) > starting udevd > creating devices > input: AT Translated Set 2 keyboard as /class/input/input0 > hdc: ATAPI 1X CD-ROM drive, 32kB Cache, UDMA(33) > Uniform CD-ROM driver Revision: 3.20 > input: ImPS/2 Generic Wheel Mouse as /class/input/input1 > waiting for system to settle > no root yet, udev rule will write symlink... > > waiting up to 60 seconds before dropping to emergency shell. > [...] > .....printk: 2869 messages suppressed. > 4gb seg fixup, process init (pid 1), cs:ip 73:009f337c > > -------------------------------------- > WARNING: Cannot find root file system! > -------------------------------------- > > Create symlink /dev/root and then exit this shell to continue > the boot sequence. > > bash: no job control in this shell > bash 3.2# Anyone has a clue about what is going wrong with this Xen LiveCD? Thanks, -- Patrice Guay From katzj at redhat.com Sun Aug 16 21:25:21 2009 From: katzj at redhat.com (Jeremy Katz) Date: Sun, 16 Aug 2009 17:25:21 -0400 Subject: [Fedora-livecd-list] Custom initrd In-Reply-To: <4A87F366.1060601@kiilerich.com> References: <4A85E8E7.7040302@kiilerich.com> <20090815024546.GB37097@redhat.com> <4A867D42.6000104@kiilerich.com> <20090816001455.GB37640@redhat.com> <4A87F366.1060601@kiilerich.com> Message-ID: <20090816212520.GA38172@redhat.com> On Sunday, August 16 2009, Mads Kiilerich said: > Jeremy Katz wrote, On 08/16/2009 02:14 AM: >>>> So if you want to do this, you have to >>>> do something like we did for Fedora 8 on the initial move of initramfs >>>> stuff into mkinitrd proper. See commit >>>> 11dbd0bb5ba4b845e80109e990e4e780ca402218 >>>> >>> Oh yeah. livecd-creator thinks (knows) that it is creating a CD, and >>> thus the initrd is (has to be) in $LIVE_ROOT/isolinux/initrd0.img. >>> >>> So >>> /sbin/mkinitrd -f $LIVE_ROOT/isolinux/initrd0.img $(rpm -q kernel >>> --qf "%{version}-%{release}.%{arch}") >>> in %post should do the trick? I will try that. >>> >> Nope -- really, look at the commit[1]. You need the two separate %post >> sections as it shows you; you can't do just one > > Ok, thanks. I'm trying to understand which parts of that commit is > essential to me. Basically all of it :) eg, when testing mkliveinitrd changes (*sigh*), I use roughly that snippet plus something which grabs my hacked up mkliveinitrd > So it is because LIVE_ROOT only is available in not in_chroot %post > scripts? And the initrd thus has to be created in a normal chrooted > %post and copied to the right location in a non-chrooted %post? Correct. > Is there any particular reason why LIVE_ROOT isn't available in chroots? > Couldn't the image always mounted under $INSTALL_ROOT/mnt/live? Or > bind-mounted? As much as possible, we try to keep the environment consistent for %post scripts so they can be transferred between real system kickstarts and live image kickstarts. Having things mounted differently like that would impact that Jeremy From katzj at redhat.com Sun Aug 16 21:27:13 2009 From: katzj at redhat.com (Jeremy Katz) Date: Sun, 16 Aug 2009 17:27:13 -0400 Subject: [Fedora-livecd-list] xen livecd creation In-Reply-To: <4A88347E.6020407@nanotechnologies.qc.ca> References: <4A88347E.6020407@nanotechnologies.qc.ca> Message-ID: <20090816212712.GB38172@redhat.com> On Sunday, August 16 2009, Patrice Guay said: > I'm trying to create a LiveCD with a xen enabled kernel (kernel-xen). > I'm using livecd-tools 013 (the last compatible version with CentOS5). > Creating a regular LiveCD works fine but I'm having trouble with the Xen > LiveCD. [snip] > Anyone has a clue about what is going wrong with this Xen LiveCD? Poke around with the shell and make sure the CD device is showing up and has the right label (/lib/udev/vol_id against the cd device) Jeremy From katzj at fedoraproject.org Mon Aug 17 14:48:59 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Mon, 17 Aug 2009 14:48:59 +0000 (UTC) Subject: [Fedora-livecd-list] 2 commits - imgcreate/fs.py imgcreate/live.py Message-ID: <20090817144859.2477312022B@lists.fedorahosted.org> imgcreate/fs.py | 3 +++ imgcreate/live.py | 5 ++++- 2 files changed, 7 insertions(+), 1 deletion(-) New commits: commit 2315f1a3cfbd38257e86b9f785f11e9a99784d67 Author: Jeremy Katz Date: Mon Aug 17 09:50:08 2009 -0400 Apparently the python traceback isn't clear enough (#517841) diff --git a/imgcreate/live.py b/imgcreate/live.py index b98f7b3..773d2c2 100644 --- a/imgcreate/live.py +++ b/imgcreate/live.py @@ -171,7 +171,10 @@ class LiveImageCreatorBase(LoopImageCreator): "LiveOS/ext3fs.img nor os.img exist" % base_on) - shutil.copyfile(os_image, self._image) + try: + shutil.copyfile(os_image, self._image) + except IOError, e + raise CreatorError("Failed to copy base live image to %s for modification: %s" %(self._image, e)) finally: squashloop.cleanup() isoloop.cleanup() commit 7a62ff24c4f1f7e46326210d0514e4b71de5772b Author: Jeremy Katz Date: Mon Aug 17 09:47:14 2009 -0400 Add a sleep to try to avoid tracebacks with snapshot removal (#506644) diff --git a/imgcreate/fs.py b/imgcreate/fs.py index a9512f2..31e5ca3 100644 --- a/imgcreate/fs.py +++ b/imgcreate/fs.py @@ -26,6 +26,7 @@ import random import string import logging import tempfile +import time from imgcreate.errors import * @@ -516,6 +517,8 @@ class DeviceMapperSnapshot(object): if not self.__created: return + # sleep to try to avoid any dm shenanigans + time.sleep(2) rc = subprocess.call(["/sbin/dmsetup", "remove", self.__name]) if not ignore_errors and rc != 0: raise SnapshotError("Could not remove snapshot device") From katzj at fedoraproject.org Mon Aug 17 14:50:57 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Mon, 17 Aug 2009 14:50:57 +0000 (UTC) Subject: [Fedora-livecd-list] imgcreate/live.py Message-ID: <20090817145057.B8A4212022B@lists.fedorahosted.org> imgcreate/live.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 832c78e2d6f54e130b845dd7d63fa457b0f513ea Author: Jeremy Katz Date: Mon Aug 17 10:50:01 2009 -0400 Fix my stupid typo. *sigh* diff --git a/imgcreate/live.py b/imgcreate/live.py index 773d2c2..f44e173 100644 --- a/imgcreate/live.py +++ b/imgcreate/live.py @@ -173,7 +173,7 @@ class LiveImageCreatorBase(LoopImageCreator): try: shutil.copyfile(os_image, self._image) - except IOError, e + except IOError, e: raise CreatorError("Failed to copy base live image to %s for modification: %s" %(self._image, e)) finally: squashloop.cleanup() From katzj at fedoraproject.org Tue Aug 18 18:10:09 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Tue, 18 Aug 2009 18:10:09 +0000 (UTC) Subject: [Fedora-livecd-list] imgcreate/live.py Message-ID: <20090818181009.4D7EA120219@lists.fedorahosted.org> imgcreate/live.py | 67 +++++++++++++++++++++++++++++++++++++++--------------- 1 file changed, 49 insertions(+), 18 deletions(-) New commits: commit c6b31fa922b322fc5b0b9f48bca3a9ff812f8bdb Author: Jeremy Katz Date: Tue Aug 18 14:07:58 2009 -0400 Support dracut based initrds With dracut, the initrd is named "initrd-generic-*.img", so support looking for that. We also end up wanting to use a different root= line which also lets the hybrid images Just Work (tm) diff --git a/imgcreate/live.py b/imgcreate/live.py index f44e173..756097b 100644 --- a/imgcreate/live.py +++ b/imgcreate/live.py @@ -364,8 +364,14 @@ class x86LiveImageCreator(LiveImageCreatorBase): shutil.copyfile(bootdir + "/vmlinuz-" + version, isodir + "/isolinux/vmlinuz" + index) - shutil.copyfile(bootdir + "/initrd-" + version + ".img", - isodir + "/isolinux/initrd" + index + ".img") + isDracut = False + if os.path.exists(bootdir + "/initrd-generic-" + version + ".img"): + shutil.copyfile(bootdir + "/initrd-generic-" + version + ".img", + isodir + "/isolinux/initrd" + index + ".img") + isDracut = True + else: + shutil.copyfile(bootdir + "/initrd-" + version + ".img", + isodir + "/isolinux/initrd" + index + ".img") is_xen = False if os.path.exists(bootdir + "/xen.gz-" + version[:-3]): @@ -373,7 +379,7 @@ class x86LiveImageCreator(LiveImageCreatorBase): isodir + "/isolinux/xen" + index + ".gz") is_xen = True - return is_xen + return (is_xen, isDracut) def __is_default_kernel(self, kernel, kernels): if len(kernels) == 1: @@ -408,18 +414,23 @@ menu hidden menu hiddenrow 5 """ % args - def __get_image_stanza(self, is_xen, **args): + def __get_image_stanza(self, is_xen, isDracut, **args): + if isDracut: + args["rootlabel"] = "live:LABEL=%(fslabel)s" % args + else: + args["rootlabel"] = "CDLABEL=%(fslabel)s" % args + if not is_xen: template = """label %(short)s menu label %(long)s kernel vmlinuz%(index)s - append initrd=initrd%(index)s.img root=CDLABEL=%(fslabel)s rootfstype=%(isofstype)s %(liveargs)s %(extra)s + append initrd=initrd%(index)s.img root=%(rootlabel)s rootfstype=%(isofstype)s %(liveargs)s %(extra)s """ else: template = """label %(short)s menu label %(long)s kernel mboot.c32 - append xen%(index)s.gz --- vmlinuz%(index)s root=CDLABEL=%(fslabel)s rootfstype=%(isofstype)s %(liveargs)s %(extra)s --- initrd%(index)s.img + append xen%(index)s.gz --- vmlinuz%(index)s root=%(rootlabel)s rootfstype=%(isofstype)s %(liveargs)s %(extra)s --- initrd%(index)s.img """ return template % args @@ -438,7 +449,9 @@ menu hiddenrow 5 index = "0" for version in versions: - is_xen = self.__copy_kernel_and_initramfs(isodir, version, index) + (is_xen, isDracut) = self.__copy_kernel_and_initramfs(isodir, version, index) + if index == "0": + self._isDracut = isDracut default = self.__is_default_kernel(kernel, kernels) @@ -449,7 +462,7 @@ menu hiddenrow 5 else: long = "Boot %s(%s)" % (self.name, kernel) - cfg += self.__get_image_stanza(is_xen, + cfg += self.__get_image_stanza(is_xen, isDracut, fslabel = self.fslabel, isofstype = "auto", liveargs = kernel_options, @@ -462,7 +475,7 @@ menu hiddenrow 5 cfg += "menu default\n" if checkisomd5: - cfg += self.__get_image_stanza(is_xen, + cfg += self.__get_image_stanza(is_xen, isDracut, fslabel = self.fslabel, isofstype = "auto", liveargs = kernel_options, @@ -540,8 +553,12 @@ hiddenmenu """ %args def __get_efi_image_stanza(self, **args): + if self._isDracut: + args["rootlabel"] = "live:LABEL=%(fslabel)s" % args + else: + args["rootlabel"] = "CDLABEL=%(fslabel)s" % args return """title %(long)s - kernel /EFI/boot/vmlinuz%(index)s root=CDLABEL=%(fslabel)s rootfstype=%(isofstype)s %(liveargs)s %(extra)s + kernel /EFI/boot/vmlinuz%(index)s root=%(rootlabel)s rootfstype=%(isofstype)s %(liveargs)s %(extra)s initrd /EFI/boot/initrd%(index)s.img """ %args @@ -649,6 +666,7 @@ class ppcLiveImageCreator(LiveImageCreatorBase): return { "32" : False, "64" : True } def __copy_kernel_and_initramfs(self, destdir, version): + isDracut = False bootdir = self._instroot + "/boot" makedirs(destdir) @@ -656,8 +674,15 @@ class ppcLiveImageCreator(LiveImageCreatorBase): shutil.copyfile(bootdir + "/vmlinuz-" + version, destdir + "/vmlinuz") - shutil.copyfile(bootdir + "/initrd-" + version + ".img", - destdir + "/initrd.img") + if os.path.exists(bootdir + "/initrd-generic-" + version + ".img"): + shutil.copyfile(bootdir + "/initrd-" + version + ".img", + destdir + "/initrd.img") + isDracut = True + else: + shutil.copyfile(bootdir + "/initrd-" + version + ".img", + destdir + "/initrd.img") + + return isDracut def __get_basic_yaboot_config(self, **args): return """ @@ -666,17 +691,21 @@ timeout=%(timeout)d """ % args def __get_image_stanza(self, **args): + if args["isDracut"]: + args["rootlabel"] = "live:LABEL=%(fslabel)s" % args + else: + args["rootlabel"] = "CDLABEL=%(fslabel)s" % args return """ image=/ppc/ppc%(bit)s/vmlinuz label=%(short)s initrd=/ppc/ppc%(bit)s/initrd.img read-only - append="root=CDLABEL=%(fslabel)s rootfstype=%(isofstype)s %(liveargs)s %(extra)s" + append="root=%(rootlabel)s rootfstype=%(isofstype)s %(liveargs)s %(extra)s" """ % args - def __write_yaboot_config(self, isodir, bit): + def __write_yaboot_config(self, isodir, bit, isDracut = False): cfg = self.__get_basic_yaboot_config(name = self.name, timeout = self._timeout * 100) @@ -688,7 +717,8 @@ image=/ppc/ppc%(bit)s/vmlinuz long = "Run from image", extra = "", bit = bit, - liveargs = kernel_options) + liveargs = kernel_options, + isDracut = isDracut) if self._has_checkisomd5(): cfg += self.__get_image_stanza(fslabel = self.fslabel, @@ -697,7 +727,8 @@ image=/ppc/ppc%(bit)s/vmlinuz long = "Verify and run from image", extra = "check", bit = bit, - liveargs = kernel_options) + liveargs = kernel_options, + isDracut = isDracut) f = open(isodir + "/ppc/ppc" + bit + "/yaboot.conf", "w") f.write(cfg) @@ -764,8 +795,8 @@ image=/ppc/ppc32/vmlinuz self.__write_not_supported(isodir, bit) continue - self.__copy_kernel_and_initramfs(isodir + "/ppc/ppc" + bit, kernel) - self.__write_yaboot_config(isodir, bit) + isDracut = self.__copy_kernel_and_initramfs(isodir + "/ppc/ppc" + bit, kernel) + self.__write_yaboot_config(isodir, bit, isDracut) makedirs(isodir + "/etc") if kernel_bits["32"] and not kernel_bits["64"]: From patrice.guay at nanotechnologies.qc.ca Wed Aug 19 00:50:43 2009 From: patrice.guay at nanotechnologies.qc.ca (Patrice Guay) Date: Tue, 18 Aug 2009 20:50:43 -0400 Subject: [Fedora-livecd-list] xen livecd creation In-Reply-To: <20090816212712.GB38172@redhat.com> References: <4A88347E.6020407@nanotechnologies.qc.ca> <20090816212712.GB38172@redhat.com> Message-ID: <4A8B4C63.3010007@nanotechnologies.qc.ca> Jeremy Katz wrote: > On Sunday, August 16 2009, Patrice Guay said: >> I'm trying to create a LiveCD with a xen enabled kernel (kernel-xen). >> I'm using livecd-tools 013 (the last compatible version with CentOS5). >> Creating a regular LiveCD works fine but I'm having trouble with the Xen >> LiveCD. > [snip] >> Anyone has a clue about what is going wrong with this Xen LiveCD? > > Poke around with the shell and make sure the CD device is showing up and > has the right label (/lib/udev/vol_id against the cd device) > I updated my livecd-tools version to 014 and applied a patch from https://bugzilla.redhat.com/show_bug.cgi?id=470564 I am now able to create a Xen LiveCD under CentOS5! -- Patrice From katzj at fedoraproject.org Wed Aug 19 20:49:44 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Wed, 19 Aug 2009 20:49:44 +0000 (UTC) Subject: [Fedora-livecd-list] imgcreate/fs.py imgcreate/live.py Message-ID: <20090819204944.05A80120261@lists.fedorahosted.org> imgcreate/fs.py | 7 +++++-- imgcreate/live.py | 5 ++--- 2 files changed, 7 insertions(+), 5 deletions(-) New commits: commit 1d215ebcf584b2bc19dece88b7f75944de2ad3f0 Author: Jeremy Katz Date: Wed Aug 19 16:47:24 2009 -0400 Use resize2fs -M (minimal) more We were keeping track of the minimal size and then passing that again. Just use resize2fs -M again for this case diff --git a/imgcreate/fs.py b/imgcreate/fs.py index 31e5ca3..b8d61db 100644 --- a/imgcreate/fs.py +++ b/imgcreate/fs.py @@ -553,7 +553,7 @@ class DeviceMapperSnapshot(object): except ValueError: raise SnapshotError("Failed to parse dmsetup status: " + out) -def create_image_minimizer(path, image, minimal_size): +def create_image_minimizer(path, image, target_size = None): """ Builds a copy-on-write image which can be used to create a device-mapper snapshot of an image where @@ -580,7 +580,10 @@ def create_image_minimizer(path, image, minimal_size): try: snapshot.create() - resize2fs(snapshot.path, minimal_size) + if target_size is not None: + resize2fs(snapshot.path, target_size) + else: + resize2fs(snapshot.path, minimal = True) cow_used = snapshot.get_cow_used() finally: diff --git a/imgcreate/live.py b/imgcreate/live.py index 756097b..528840d 100644 --- a/imgcreate/live.py +++ b/imgcreate/live.py @@ -271,11 +271,10 @@ class LiveImageCreatorBase(LoopImageCreator): try: makedirs(self.__ensure_isodir() + "/LiveOS") - minimal_size = self._resparse() + self._resparse() if not self.skip_minimize: - create_image_minimizer(self.__isodir + "/LiveOS/osmin.img", - self._image, minimal_size) + create_image_minimizer(self.__isodir + "/LiveOS/osmin.img", self._image) if self.skip_compression: shutil.move(self._image, self.__isodir + "/LiveOS/ext3fs.img") From mads at kiilerich.com Wed Aug 19 23:29:51 2009 From: mads at kiilerich.com (Mads Kiilerich) Date: Thu, 20 Aug 2009 01:29:51 +0200 Subject: [Fedora-livecd-list] Custom initrd In-Reply-To: <20090816212520.GA38172@redhat.com> References: <4A85E8E7.7040302@kiilerich.com> <20090815024546.GB37097@redhat.com> <4A867D42.6000104@kiilerich.com> <20090816001455.GB37640@redhat.com> <4A87F366.1060601@kiilerich.com> <20090816212520.GA38172@redhat.com> Message-ID: <4A8C8AEF.2090706@kiilerich.com> Jeremy Katz wrote, On 08/16/2009 11:25 PM: > On Sunday, August 16 2009, Mads Kiilerich said: > >> Jeremy Katz wrote, On 08/16/2009 02:14 AM: >> >>>>> So if you want to do this, you have to >>>>> do something like we did for Fedora 8 on the initial move of initramfs >>>>> stuff into mkinitrd proper. See commit >>>>> 11dbd0bb5ba4b845e80109e990e4e780ca402218 >>>>> >>>>> >>>> Oh yeah. livecd-creator thinks (knows) that it is creating a CD, and >>>> thus the initrd is (has to be) in $LIVE_ROOT/isolinux/initrd0.img. >>>> >>>> So >>>> /sbin/mkinitrd -f $LIVE_ROOT/isolinux/initrd0.img $(rpm -q kernel >>>> --qf "%{version}-%{release}.%{arch}") >>>> in %post should do the trick? I will try that. >>>> >>>> >>> Nope -- really, look at the commit[1]. You need the two separate %post >>> sections as it shows you; you can't do just one >>> >> Ok, thanks. I'm trying to understand which parts of that commit is >> essential to me. >> > Basically all of it :) eg, when testing mkliveinitrd changes (*sigh*), > I use roughly that snippet plus something which grabs my hacked up > mkliveinitrd > Thanks, it works fine now. But I don't see why "all of it" should be used. I am using something like a normal %post with /sbin/mkinitrd -f /initrd0.img $(rpm -q kernel --qf "%{version}-%{release}.%{arch}") and a %post --nochroot with mv $INSTALL_ROOT/initrd0.img $LIVE_ROOT/isolinux/ - with the initrd location chosen so that no "rm -f /boot/initrd*" interferes. >> Is there any particular reason why LIVE_ROOT isn't available in chroots? >> Couldn't the image always mounted under $INSTALL_ROOT/mnt/live? Or >> bind-mounted? >> > As much as possible, we try to keep the environment consistent for %post > scripts so they can be transferred between real system kickstarts and > live image kickstarts. Having things mounted differently like that > would impact that > Now I know how it works and how to work around it, so I have no problem. But in order to improve the system further and help the next newbie I will argue for some changes: Making scripts for real installation and for live building as similar as possible is a fine goal. And obviously, when live image kickstarts in some cases needs special %post scripts then it can't be reached completely. I think that an even more important goal is "%post environment is as close to runtime environment as possible". For real kickstarts "all" file systems mounted on runtime are mounted when %post is run too, so it would be consistent if the same was the case for live kickstarts. I realize that the runtime mount point for /dev/only (currently) only (?) is defined in the %post script in fedora-live-base.ks, so imgcreate wouldn't know where to mount it. Another fine goal is " '%post' and '%post --nochroot' should be as similar as possible - except for the chroot". In any case: Having the live root mounted somewhere specified by $LIVE_ROOT in all %post scripts (chroot or not) would make script contexts more consistent and make some things simpler (such as building custom initrd for F11...), and I don't see how it could have any negative impact on the goal of %post scripts being the same for real kickstart and for live image composition. /Mads From wtogami at redhat.com Thu Aug 20 22:02:37 2009 From: wtogami at redhat.com (Warren Togami) Date: Thu, 20 Aug 2009 18:02:37 -0400 Subject: [Fedora-livecd-list] resize2fs: No space left while trying to resize ... ext3fs.img Message-ID: <4A8DC7FD.4040506@redhat.com> Trying livecd-creator as of git 1d215ebcf584b2bc19dece88b7f75944de2ad3f0 with August 20th rawhide + ntfsprogs to fix the broken dep. Installing: plymouth-gdm-hooks ##################### [988/988] Removing password for user root. passwd: Success e2fsck 1.41.8 (11-July-2009) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information fedora-livec-x86: 78634/196608 files (0.1% non-contiguous), 534825/786432 blocks e2image 1.41.8 (11-July-2009) resize2fs 1.41.8 (11-July-2009) Resizing the filesystem on /opt/tmp/imgcreate-3h7N84/tmp-1Tw3yD/ext3fs.img to 534815 (4k) blocks. /sbin/resize2fs: No space left on device while trying to resize /opt/tmp/imgcreate-3h7N84/tmp-1Tw3yD/ext3fs.img Please run 'e2fsck -fy /opt/tmp/imgcreate-3h7N84/tmp-1Tw3yD/ext3fs.img' to fix the filesystem after the aborted resize operation. /usr/lib/python2.6/site-packages/imgcreate/errors.py:45: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6 return unicode(self.message) Error creating Live CD : resize2fs returned an error (1)! image to debug at /tmp/resize-image-2HbZ8I From katzj at redhat.com Fri Aug 21 15:35:34 2009 From: katzj at redhat.com (Jeremy Katz) Date: Fri, 21 Aug 2009 11:35:34 -0400 Subject: [Fedora-livecd-list] resize2fs: No space left while trying to resize ... ext3fs.img In-Reply-To: <4A8DC7FD.4040506@redhat.com> References: <4A8DC7FD.4040506@redhat.com> Message-ID: <20090821153439.GA23719@redhat.com> On Thursday, August 20 2009, Warren Togami said: > Trying livecd-creator as of git 1d215ebcf584b2bc19dece88b7f75944de2ad3f0 > with August 20th rawhide + ntfsprogs to fix the broken dep. [snip] > Resizing the filesystem on > /opt/tmp/imgcreate-3h7N84/tmp-1Tw3yD/ext3fs.img to 534815 (4k) blocks. > /sbin/resize2fs: No space left on device while trying to resize > /opt/tmp/imgcreate-3h7N84/tmp-1Tw3yD/ext3fs.img resize2fs here is saying you don't have enough space on /opt for the resize and then failing. If you _do_ have lots of disk space there, file a bug against e2fsprogs and get sandeen to look at why it's failing Jeremy From patrice.guay at nanotechnologies.qc.ca Sun Aug 23 00:01:11 2009 From: patrice.guay at nanotechnologies.qc.ca (Patrice Guay) Date: Sat, 22 Aug 2009 20:01:11 -0400 Subject: [Fedora-livecd-list] Redirecting livecd-creator output Message-ID: <4A9086C7.3010303@nanotechnologies.qc.ca> When I call livecd-creator (livecd-tools version 014 under CentOS 5) and redirect the output to a standard file, the creation process fails: # livecd-creator -c minimal.ks -f minimal > output.log mke2fs 1.39 (29-May-2006) warning: libgcc-4.1.2-44.el5: Header V3 DSA signature: NOKEY, key ID e8562897 warning: syslinux-3.36-4.2: Header V3 DSA signature: NOKEY, key ID fabea322 /sbin/scsi_id: option requires an argument -- s /sbin/scsi_id: option requires an argument -- s e2fsck 1.39 (29-May-2006) Installation target minimized to 610900K resize2fs 1.39 (29-May-2006) genMinInstDelta data length is 2208 512 byte sectors /sbin/mksquashfs: invalid option SYNTAX:/sbin/mksquashfs source1 source2 ... dest [options] [-e list of exclude dirs/files] [...] Error creating Live CD : mksquashfs exited with error (1) What could explain this behavior? -- Patrice Guay patrice.guay at nanotechnologies.qc.ca From katzj at fedoraproject.org Mon Aug 24 20:43:21 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Mon, 24 Aug 2009 20:43:21 +0000 (UTC) Subject: [Fedora-livecd-list] Makefile Message-ID: <20090824204321.A98F7120107@lists.fedorahosted.org> Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 3553dafeccf8461b966ab7d5c327d9e22e9955ad Author: Jeremy Katz Date: Mon Aug 24 16:41:52 2009 -0400 Bump version diff --git a/Makefile b/Makefile index 68cb635..f208c41 100644 --- a/Makefile +++ b/Makefile @@ -1,5 +1,5 @@ -VERSION = 025 +VERSION = 026 INSTALL = /usr/bin/install -c INSTALL_PROGRAM = ${INSTALL} From rmy at tigress.co.uk Tue Aug 25 14:55:48 2009 From: rmy at tigress.co.uk (Ron Yorston) Date: Tue, 25 Aug 2009 15:55:48 +0100 Subject: [Fedora-livecd-list] Implant md5sum Message-ID: <200908251455.n7PEtnNa001615@tiffany.internal.tigress.co.uk> I've been using the livecd-tools from the CentOS LiveCD Project, but the same issue seems to apply in Fedora. If an implantisomd5 binary can't be found a warning is printed but an attempt is made to run the binary anyway. This results in a Python traceback: isomd5sum not installed; not setting up mediacheck Traceback (most recent call last): File "/usr/bin/livecd-creator", line 133, in ? sys.exit(main()) File "/usr/bin/livecd-creator", line 123, in main creator.package() File "/usr/lib/python2.4/site-packages/imgcreate/creator.py", line 657, in package self._stage_final_image() File "/usr/lib/python2.4/site-packages/imgcreate/live.py", line 308, in _stage_final_image self.__create_iso(self.__isodir) File "/usr/lib/python2.4/site-packages/imgcreate/live.py", line 274, in __create_iso self.__implant_md5sum(iso) File "/usr/lib/python2.4/site-packages/imgcreate/live.py", line 286, in __implant_md5sum subprocess.call([implantisomd5, iso]) UnboundLocalError: local variable 'implantisomd5' referenced before assignment Sticking in a return statement makes it work: def __implant_md5sum(self, iso): """Implant an isomd5sum.""" if os.path.exists("/usr/bin/implantisomd5"): implantisomd5 = "/usr/bin/implantisomd5" elif os.path.exists("/usr/lib/anaconda-runtime/implantisomd5"): implantisomd5 = "/usr/lib/anaconda-runtime/implantisomd5" else: print >> sys.stderr, \ "isomd5sum not installed; not setting up mediacheck" return subprocess.call([implantisomd5, iso]) Ron From katzj at fedoraproject.org Tue Aug 25 15:02:07 2009 From: katzj at fedoraproject.org (Jeremy Katz) Date: Tue, 25 Aug 2009 15:02:07 +0000 (UTC) Subject: [Fedora-livecd-list] 2 commits - imgcreate/live.py tools/livecd-iso-to-disk.sh Message-ID: <20090825150207.1659F1201E3@lists.fedorahosted.org> imgcreate/live.py | 1 + tools/livecd-iso-to-disk.sh | 2 ++ 2 files changed, 3 insertions(+) New commits: commit 59aa5640bf2216d1823ce7d552ae8530d44bdabb Author: Jeremy Katz Date: Tue Aug 25 10:59:42 2009 -0400 Fix traceback when implantisomd5 isn't available (Ron Yorston) diff --git a/imgcreate/live.py b/imgcreate/live.py index 528840d..c49b358 100644 --- a/imgcreate/live.py +++ b/imgcreate/live.py @@ -264,6 +264,7 @@ class LiveImageCreatorBase(LoopImageCreator): implantisomd5 = "/usr/lib/anaconda-runtime/implantisomd5" else: logging.warn("isomd5sum not installed; not setting up mediacheck") + return subprocess.call([implantisomd5, iso]) commit 89720ad085e3996bded0e9570878e56a158232ff Author: Jeremy Katz Date: Thu Aug 20 14:13:41 2009 -0400 Sleep to avoid races (#517477) Try to sleep a little to avoid racing with system stuff poking at new filesystems diff --git a/tools/livecd-iso-to-disk.sh b/tools/livecd-iso-to-disk.sh index 0efef58..cd75153 100755 --- a/tools/livecd-iso-to-disk.sh +++ b/tools/livecd-iso-to-disk.sh @@ -28,6 +28,7 @@ usage() { } cleanup() { + sleep 2 [ -d "$CDMNT" ] && umount $CDMNT && rmdir $CDMNT [ -d "$USBMNT" ] && umount $USBMNT && rmdir $USBMNT } @@ -598,6 +599,7 @@ if [ "$homesizemb" -gt 0 ]; then done mke2fs -j /dev/mapper/EncHomeFoo tune2fs -c0 -i0 -ouser_xattr,acl /dev/mapper/EncHomeFoo + sleep 2 cryptsetup luksClose EncHomeFoo losetup -d $loop else From patrice.guay at nanotechnologies.qc.ca Thu Aug 27 12:59:06 2009 From: patrice.guay at nanotechnologies.qc.ca (Patrice Guay) Date: Thu, 27 Aug 2009 08:59:06 -0400 Subject: [Fedora-livecd-list] Redirecting livecd-creator output In-Reply-To: <4A9086C7.3010303@nanotechnologies.qc.ca> References: <4A9086C7.3010303@nanotechnologies.qc.ca> Message-ID: <4A96831A.1050100@nanotechnologies.qc.ca> Patrice Guay wrote: > When I call livecd-creator (livecd-tools version 014 under CentOS 5) and > redirect the output to a standard file, the creation process fails: > > # livecd-creator -c minimal.ks -f minimal > output.log > > mke2fs 1.39 (29-May-2006) > warning: libgcc-4.1.2-44.el5: Header V3 DSA signature: NOKEY, key ID > e8562897 > warning: syslinux-3.36-4.2: Header V3 DSA signature: NOKEY, key ID fabea322 > /sbin/scsi_id: option requires an argument -- s > /sbin/scsi_id: option requires an argument -- s > e2fsck 1.39 (29-May-2006) > Installation target minimized to 610900K > resize2fs 1.39 (29-May-2006) > genMinInstDelta data length is 2208 512 byte sectors > /sbin/mksquashfs: invalid option > > SYNTAX:/sbin/mksquashfs source1 source2 ... dest [options] [-e list of > exclude dirs/files] > [...] > Error creating Live CD : mksquashfs exited with error (1) > > > What could explain this behavior? > Marc Herbert wrote : >> Weird, I use "tee" with livecd-tools-020.1-1.fc10 and it works. >> Works for me: >> >> time nice sudo livecd-creator .... | tee build.log > > Sorry I am actually doing this: > > time nice sudo livecd-creator .... 2>&1 | tee build.log > > > That could make a difference, who knows. > > > > livecd-creator ... | tee build.log livecd-creator ... 2>&1 | tee build.log -> both methods fail the same way "livecd-creator ... > output.log" did Is there a commit somewhere between 014 and 020 fixing this issue? -- Patrice From bkearney at redhat.com Thu Aug 27 16:21:35 2009 From: bkearney at redhat.com (Bryan Kearney) Date: Thu, 27 Aug 2009 12:21:35 -0400 Subject: [Fedora-livecd-list] livecd on F11 Message-ID: <4A96B28F.90506@redhat.com> I am trying to run livecd-creator on F11. I have tried both the released package and the tips. Both are showing errors. Is the plan to release version 25 (roughly the tip) on F11? I want to understand which bug to go after. Bug in Head ============ File "/home/bkearney/code/livecd/imgcreate/live.py", line 191, in _unmount_instroot LoopImageCreator._unmount_instroot(self) File "/home/bkearney/code/livecd/imgcreate/creator.py", line 938, in _unmount_instroot self.__instloop.cleanup() File "/home/bkearney/code/livecd/imgcreate/fs.py", line 346, in cleanup Mount.cleanup(self) File "/home/bkearney/code/livecd/imgcreate/fs.py", line 325, in cleanup self.unmount() File "/home/bkearney/code/livecd/imgcreate/fs.py", line 356, in unmount raise MountError("Unable to unmount filesystem at %s" % self.mountdir) imgcreate.errors.MountError/home/bkearney/code/livecd/imgcreate/errors.py:40: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6 return str(self.message) : Unable to unmount filesystem at /tmp/imgcreate-DWSrZg/install_root umount: /tmp/imgcreate-DWSrZg/install_root: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) Exception imgcreate.errors.MountError: MountError('Unable to unmount filesystem at /tmp/imgcreate-DWSrZg/install_root',) in > ignored Bug in Released Version ======================= passwd: Success umount: /tmp/imgcreate-yYJyiT/install_root: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) ioctl: LOOP_CLR_FD: Device or resource busy Traceback (most recent call last): File "/home/bkearney/code/adk2/bin/adk", line 6, in sys.exit(app.main()) File "/home/bkearney/code/adk2/adk/adk.py", line 131, in main adk.build(cmd, appl, args) File "/home/bkearney/code/adk2/adk/adk.py", line 76, in build plugin.run(appliance, self.settings) File "/home/bkearney/code/adk2/adk/plugins/livecd.py", line 56, in run creator.configure() File "/usr/lib/python2.6/site-packages/imgcreate/creator.py", line 732, in configure self._create_bootconfig() File "/usr/lib/python2.6/site-packages/imgcreate/live.py", line 197, in _create_bootconfig self._configure_bootloader(self.__ensure_isodir()) File "/usr/lib/python2.6/site-packages/imgcreate/live.py", line 604, in _configure_bootloader self._configure_syslinux_bootloader(isodir) File "/usr/lib/python2.6/site-packages/imgcreate/live.py", line 508, in _configure_syslinux_bootloader cfg += self.__get_image_stanzas(isodir) File "/usr/lib/python2.6/site-packages/imgcreate/live.py", line 435, in __get_image_stanzas is_xen = self.__copy_kernel_and_initramfs(isodir, version, index) File "/usr/lib/python2.6/site-packages/imgcreate/live.py", line 362, in __copy_kernel_and_initramfs isodir + "/isolinux/initrd" + index + ".img") File "/usr/lib64/python2.6/shutil.py", line 52, in copyfile fsrc = open(src, 'rb') IOError: [Errno 2] No such file or directory: '/tmp/imgcreate-yYJyiT/install_root/boot/initrd-2.6.31-0.180.rc7.git4.fc12.x86_64.img'