I'm using Kadischi with rawhide and find it incredibly useful.
However, I wanted to run yum in the %post section of a kickstart
script I use. I ran into a problem where yum attempts to check
the current architecture of its environment by checking
/proc/cpuinfo. (For the curious, this was to support installing
XFce4 from extras-development).
Like several other generic chroot'd problems/solutions with kickstarts,
I added these before running anaconda in kadischi.py:
+# set up chroot environment if necessary
+ flc_log ('setting up chroot environment from host to build')
+ os.makedirs (normalize_path([sysdir, 'proc']))
+ os.makedirs (normalize_path([sysdir, 'sys']))
+ run ("mount --bind /proc %s" % (normalize_path([sysdir, 'proc'])), builddir)
+ run ("mount --bind /sys %s" % (normalize_path([sysdir, 'sys'])), builddir)
and immediately after running anaconda in kadischi.py:
+# tear down chroot environment if necessary
+ flc_log ('tearing down chroot environment')
+ run ("umount %s" % (normalize_path([sysdir, 'proc'])), builddir)
+ run ("umount %s" % (normalize_path([sysdir, 'sys'])), builddir)
I also added a command-line argument to (--chroot) to control these.
I wanted to add this to kadischi so I didn't have to find a way
to run the %post with "--nochroot" and find a way to propagate the
/tmp/livecd-build_noX/ path into the kickstart somewhere... Of course
this means you'd have to build the ISO on the same architecture that
you're targeting the ISO installation...
I wondered if anyone else had this problem and a better solution?
Or would anyone find a patch useful? This was my first time
doing anything in Python, too, so who knows if it's a good way
to implement this type of solution... ;)
I also added a "--nocompress" option to skip the whole mkzftree phase,
since most of the ISOs I generate are below CD-sizes before compression;
I run the ISOs in QEMU from a USB keychain, so speed was becoming an
issue with the compressed images... Would anyone find this useful
Can we try to less-complicate the Kadischi/Contributors page on the wiki.
It looks a bit strange, I think when users are visiting the wiki they'll
click Contributors and expect to see the current contributors of the
If you have a look: http://fedoraproject.org/wiki/Kadischi/Contributors
" The following table lists the Kadischi contributors."
"The objective of this table is to prepare ground for the next maintainer."
This is a bit strange, the user clicked the link I think they were
already expecting a list of contributors, not an explanation of what is
on the Contributors page.
Also.. if you read the second sentence, it really makes little sense.
The table's objective is toi list the contributors, not prepare ground
for a maintainer.
The On Vacation and Mailing List and Archives links, those look great.
"There is no maintainer for the moment. Darko Ilic was the previous
maintainer of this project."
This information is in the Kadischi/FAQ so it is redundant. We should
place it on one or another page.
It should exist on the FAQ, or on the Contributors page, but not
neccessarily both, unless there is a reason I am not aware of.
This block here should go to the FAQ:
"How can I help"
"There are 3 sub categories of the Kadischi Project:"
"2. making documentation /wiki maintaining / translation"
"3. testers/bugs/bugs triage"
Though listing "categories" I think should be changed to "You can help
in a few of different ways:" for example
with Procedures as a category under that FAQ.
Surely this will help organize that wiki page a bit better.
I got mail from Berry Linux developer. Given the limited Japanese
I know, I got some suggestions. Here is the mail:
hayo gozaimasu Luya Tshimbalanga san,
> I am currently one Fedora user contributing on Kadischi project
> (http://www.fedoraproject.org/wiki/kadischi) as you have heard before.
Yes, I heard before.
> Could you see what went wrong with this ouput and what suggestion do you
I'm sorry I'm not good at English.
And I don't know python well and what he, one of Kadischi contributor, expects.
So precise advice may not be possible, sorry.
I think squashfs is READ-ONLY filesystem.
So if he'd like to install these files,
initrd.img, vmlinuz and isolinux.cfg,
to squashfs file, please install it BEFORE mksquashfs command.
But case of Berry Linux, it doesn't need initrd.img, vmlinuz and isolinux.cfg files in squashfs file.
But Berry Linux needs these files for boot.img file.
# make initrd image
flc_log ('making initrd image')
run ("%s %s %s" % (normalize_path([bindir, 'livecd-mkinitrd.sh']), sysdir, kernel_version), builddir)
# compress the tree
flc_log ('compressing the tree (order a pizza `cause this will take a while)')
# A squashed READ-ONLY filesystem for Linux
run ("mksquashfs %s %s" % (sysdir, squasharchive), builddir)
by Yuichiro Nakada
Get your free email from [protocol]://mail.jp.popstarmail.org
Our ambassador ThomasCanniot will present for the first time in public
a Fedora Live CD build by Kadischi.
Any livecd made by Kadischi when boots does not show any with respect
Ive created a page with my screenshots and texts which I propose to
integrate in within the livecd.
have a look
suggestions are welcome.
Ive already did the neccessary.
if the text can be enhanced somehow, do post something to the list.
by the way in a 800x600 resolution, we can not add much info per page.
Why only 5 F-keys?
I found it kewl to add only 5 F-keys.
5 F-keys 5 FC Versions.
concerning a splash.lss, I failed to make a proper one. if you look at
the right hand top corner of the first screenshot you will see a
broken blue spot. This is my broken splash.lss
if anyone wants to create one for Fedora, do send it to me. Ill add
it. Of course if its related to the Fedora Core 5 theme.
Maybe the FedoraArtwork department can help me with it.
The last screenshot is a 1024x768 resolution (16 bit) screen.
Are there any plans to run a LiveCD entirely from RAM with Kadischi?
Something like run entirely from ramdisk instead of selectively
transferring some dirs to the tmpfs mount?
I tried to find something on the wiki, and this list's archives, but
im trying to integrate mksquashfs, i think Finalzone too :)
but the main difficulty is that I can't integrate these files
cp $sysdir/boot/isolinux/initrd.img $csysdir/boot/isolinux/initrd.img
cp $sysdir/boot/vmlinuz-$kernel $csysdir/boot/isolinux/vmlinuz
cp /usr/lib/syslinux/isolinux.bin $csysdir/boot/isolinux/
cat > $csysdir/boot/isolinux/isolinux.cfg <<_EOF_
to the Read-Only squashfs since in kadischi.py in comments it's said :::
install boot & conf files in compressed tree (they shoudn`t be compressed)
Ive attached my kadischi.py on which im working on. maybe Finalzone /
JasperHartline may come up with a solution :)
One thing I noticed is %s variable does not use .sqsh extension.
I think we shoould find a way to define that.
I use the following tutorial
> ----- Original Message -----
> From: fedora-livecd-list-request(a)redhat.com
> To: fedora-livecd-list(a)redhat.com
> Subject: Fedora-livecd-list Digest, Vol 10, Issue 17
> Date: Tue, 21 Feb 2006 12:00:15 -0500 (EST)
> Send Fedora-livecd-list mailing list submissions to
> To subscribe or unsubscribe via the World Wide Web, visit
> or, via email, send a message with subject or body 'help' to
> You can reach the person managing the list at
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Fedora-livecd-list digest..."
> Today's Topics:
> 1. integrate squashfs: help! (Chitlesh GOORAH)
> Message: 1
> Date: Tue, 21 Feb 2006 17:32:23 +0100
> From: "Chitlesh GOORAH" <chitlesh(a)fedoraproject.org>
> Subject: [Fedora-livecd-list] integrate squashfs: help!
> To: fedora-livecd-list(a)redhat.com
> Content-Type: text/plain; charset="iso-8859-1"
> Hai there,
> im trying to integrate mksquashfs, i think Finalzone too :)
> but the main difficulty is that I can't integrate these files
> cp $sysdir/boot/isolinux/initrd.img $csysdir/boot/isolinux/initrd.img
> cp $sysdir/boot/vmlinuz-$kernel $csysdir/boot/isolinux/vmlinuz
> cp /usr/lib/syslinux/isolinux.bin $csysdir/boot/isolinux/
> cat > $csysdir/boot/isolinux/isolinux.cfg <<_EOF_
> to the Read-Only squashfs since in kadischi.py in comments it's said :::
> install boot & conf files in compressed tree (they shoudn`t be compressed)
> Ive attached my kadischi.py on which im working on. maybe Finalzone /
> JasperHartline may come up with a solution :)