Kadischi postinstall scripts
by J. Hartline
Hi.
I've been building some RAWHIDE ISOs with kadischi and
I notice %systemdir/proc isn't mounted by Anaconda anymore.
In kadischi's post_install_scripts we have 01umountproc.sh, which
I think is a likely candidate to be replaced with 01prelink.sh.
Does anyone have any recommendation as to why this shouldn't be, and
how we can run prelink in a more desired position?
Here is what I've put together for 01prelink.sh attached.
J. Hartline
17 years, 8 months
fc5 test 2 patch rejections
by Skunk Worx
Sigh, must be getting tired. Posted to fedora users by accident! Well
here it is:
I am trying to test kadischi against fc5 test2 and i get a patch
rejection (not too unexpected) I wonder if I should try and do it by hand?
[root@testbox kadischi]# patch -b /usr/sbin/anaconda
/usr/local/share/kadischi/patches/anaconda.patch
patching file /usr/sbin/anaconda
Hunk #1 FAILED at 400.
Hunk #2 succeeded at 510 with fuzz 2 (offset 16 lines).
Hunk #3 succeeded at 1154 (offset 22 lines).
1 out of 3 hunks FAILED -- saving rejects to file /usr/sbin/anaconda.rej
[root@testbox kadischi]# cat /usr/sbin/anaconda.rej
***************
*** 400,406 ****
try:
(args, extra) = isys.getopt(theargs, 'CGTRxtdr:fm:',
- [ 'graphical', 'text', 'test', 'debug', 'nofallback',
'method=', 'rootpath=', 'pcic=', "overhead=",
'testpath=', 'mountfs', 'traceonly', 'kickstart=',
'lang=', 'keymap=', 'kbdtype=', 'module=', 'class=',
--- 400,406 ----
try:
(args, extra) = isys.getopt(theargs, 'CGTRxtdr:fm:',
+ [ 'graphical', 'text', 'test', 'debug', 'nofallback', 'livecd',
'method=', 'rootpath=', 'pcic=', "overhead=",
'testpath=', 'mountfs', 'traceonly', 'kickstart=',
'lang=', 'keymap=', 'kbdtype=', 'module=', 'class=',
[root@testbox kadischi]# patch -b /usr/lib/anaconda/flags.py
/usr/local/share/kadischi/patches/flags.py.patch
patching file /usr/lib/anaconda/flags.py
Hunk #1 succeeded at 41 with fuzz 2 (offset 1 line).
TIA,
SW
17 years, 8 months
FC5T2: anaconda makes my screen flicker!!
by Chitlesh GOORAH
Hai there,
Ive wiped out my FC4 to install FC5T2 just to test kadischi. It's a
pity that till now I couldn't get nvidia working. Anyway,
I tried to patch anaconda, but it failed:
patch -b /usr/sbin/anaconda /usr/local/share/kadischi/patches/anaconda.patch
patching file /usr/sbin/anaconda
Hunk #1 FAILED at 400.
Hunk #2 succeeded at 510 with fuzz 2 (offset 16 lines).
Hunk #3 succeeded at 1154 (offset 22 lines).
1 out of 3 hunks FAILED -- saving rejects to file /usr/sbin/anaconda.rej
So I get my hands into the patch, and create a NEW patch. Ive attached
it in this mail.
Ive patched anaconda again. This time is was successful.
patch -b /usr/sbin/anaconda /home/chitlesh/anacondafc5t2.patch
patching file /usr/sbin/anaconda
Ive successfully patched flags.py too.
[root@goorah ~]# patch -b /usr/lib/anaconda/flags.py
/usr/local/share/kadischi/patches/flags.py.patch
patching file /usr/lib/anaconda/flags.py
But kadischi cant launch anaconda.
[root@goorah ~]# kadischi cdrom:// /tmp/fc5t2.iso
Starting kadischi...
Parsing command line arguments
Checking UID
Using buildstamp file /etc/kadischi/buildstamp.
Product path set to Fedora.
Now we are going to try to validate your repository (for now, only
http, ftp and local repositories can be checked)
Repository seems to be OK.
Checking required packages
Looking for config file
Loadnig config file options
*** running anaconda ***
Traceback (most recent call last):
File "/usr/sbin/anaconda", line 514, in ?
flags.livecd = 1
File "/usr/lib/anaconda/flags.py", line 30, in __setattr__
raise AttributeError, attr
AttributeError: livecd
*** Fatal error: anaconda returned non zero (256) exit code.
Aborting execution.
Cleaning up temporary files...
Done
Then, I patched kadischi.py with JasperHartline's kadischi-fc5tx.patch
and executed kadischi cdrom:// /tmp/fc5t2.iso again.
THIS TIME ANACONDA MADE my screen flick repetitively after detecting
my graphic card. All i needed to do is to press the power button.
after booting my FC5T2 again, I tried again. But landed with another error.
[root@goorah ~]# kadischi cdrom:// /tmp/fc5t2.iso
Starting kadischi...
Parsing command line arguments
Checking UID
Using buildstamp file /etc/kadischi/buildstamp.
Product path set to Fedora.
Now we are going to try to validate your repository (for now, only
http, ftp and local repositories can be checked)
Repository seems to be OK.
Checking required packages
Looking for config file
Loadnig config file options
*** running anaconda ***
Probing for video card: nVidia Corporation NV34 [GeForce FX Go5100]
Probing for monitor type: Unknown monitor
Starting graphical installation...
Traceback (most recent call last):
File "/usr/sbin/anaconda", line 1080, in ?
methodobj = CdromInstallMethod(method, rootPath, intf)
File "/usr/lib/anaconda/image.py", line 358, in __init__
(self.device, tree) = string.split(url, ":", 1)
ValueError: need more than 1 value to unpack
*** Fatal error: anaconda returned non zero (256) exit code.
Aborting execution.
Cleaning up temporary files...
Done.
I am in the copying process of the dvd on my drive and ill execute
kadischi afterwards. Ill keep you tuned.
by the way
[root@goorah ~]# rpm -qa | grep anaconda
anaconda-10.91.9-1
busybox-anaconda-1.01-2.1
anaconda-runtime-10.91.9-1
--
http://clunixchit.blogspot.com
17 years, 8 months
Kadischi question
by Saikat Guha
Hi,
I was looking to help test out Kadishi etc. I created a CD image (using
the CVS just now based on FC4 release); tried booting into it from
VMWare, but encountered some problems.
I am running Kadishi CVS on a FC4 x86-64, with anaconda appropriately
patched. The source image is the FC4 32-bit release version. The CD
creation process runs fine without any errors. The CD created is used to
boot up a VMWare image; said VMWare image successfully boots both 64-bit
and 32-bit FC4 rescue CD's. When booting up with the Kadischi created
CD, I run into the following problems.
1) Waiting for ISOLINUX to boot into the default image / or picking
'linux' or 'test' at that bootprompt all generate a kernel panic. It
appears that the kernel couldn't mount root.
2) Booting into 'test root=/dev/hdc' detects and mounts the ISO9660
filesystem just fine; it then successfully moves the old root to /initrd
and frees up some memory (based on debug printouts). Then it stops
producing output after printing out 'Warning: unable to open an initial
console.' Adding selinux=0 to the boot params doesn't fix this. I am
using whatever udev comes with FC4 release.
3) Booting 'vmlinuz root=/dev/hdc init=/bin/bash' gives the same
warning (about initial console) and complains that the kernel attempted
to kill init.
Am I missing something in getting it to boot?
--
Saikat
17 years, 8 months
meeting times
by J. Hartline
Hi.
There is no set meeting times for us involved with Kaidschi
though we have sheduled the next meeting at 20:00 GMT
Wednesday, February 1st 2006.
Maybe this time frame will work for you guys? ;-)
[irc.freenode.net:6667 #fedora-livecd]
Thanks!
J. Hartline
17 years, 8 months
fc5t2 some progress
by Skunk Worx
so far :
1) restored orig anaconda and flags files i patched by accident :-)
2) populated localhost web server "http://127.0.0.1/fc5" with fc5t2
Fedora/base and Fedora/RPMS below it;
3) run recommended createrepo command in /var/www/html/fc5;
4) applied recommended patch eliminating "livecd" option error;
If I try my kickstart file I get a error about "parttype, can't
continue" (I've used the "bootloader --location=none" directive in my
previous kickstart scripts) :
[root@testbox ~]# kadischi http://127.0.0.1/fc5
/cdimages/fedora-live.iso --kickstart=ks-001_fc5.cfg -C
Starting kadischi...
Parsing command line arguments
Checking UID
Using buildstamp file /etc/kadischi/buildstamp.
Product path set to Fedora.
Now we are going to try to validate your repository (for now, only http,
ftp and local repositories can be checked)
URL http://127.0.0.1/fc5 contacted. OK
URL http://127.0.0.1/fc5/Fedora contacted. OK
URL http://127.0.0.1/fc5/Fedora/base contacted. OK
URL http://127.0.0.1/fc5/Fedora/RPMS contacted. OK
Repository seems to be OK.
Checking required packages
Looking for config file
Loadnig config file options
*** running anaconda ***
Probing for video card: VIA Technologies, Inc. VT8378 [S3 UniChrome]
Integrated Video
Probing for monitor type: A91f+
In interactive step parttype, can't continue
(hangs here)
Also if I try just :
[root@testbox ~]# kadischi http://127.0.0.1/fc5 /cdimages/fedora-live.iso
...from an xterm I get a text based install, that wants to modify my
partitions on the hard drive, as I recall I used to get the full
graphical anaconda.
Comments welcome...
--
SW
17 years, 8 months
kadischi-nokernel.patch
by J. Hartline
Hi.
I sent a patch to the list earlier, but it is trash now.
The attached patch is much better, and I'm sure it can be improved though
it kills off the None kernel version.
17 years, 8 months
A Kadischi script and FC5 Question
by Matt Bird
Hi all,
Further to my earlier 'newbie' email Im progressing quite quickly with
developing 'my' live CD version. Ive written a quick Perl script that
sets the Gnome desktop image and changes the run level of the Live CD.
Im sure most of the list members here consider it old news, but
hopefully someone will benefit. The script can be found on
*http://fedoraproject.org/wiki/MattBird
*
The FC5 question relates to this sentence in the Kadischi/FAQ;
"For users trying out development(FC5tx), use:
createrepo <basedir>/<productpath>/RPMS"
Could someone confirm that this is the same method (and createrepo
software) used in Redhat Enterprise 3 (and I assume 4) as this is what
I currently use for maintaining a range of Update/Patch repositories in
the course of my day job.
Thanks
Matt
**
17 years, 8 months
some FC3 help?
by Eric White
I've seen that a couple of folks have gotten Kadischi to build with FC3
and I thought I'd gotten the kinks worked out, but I continue to see
this error message at the end of the anaconda run:
making initrd image
/tmp/livecd-build_no26/system/lib/modules/None is not a directory.
*** Fatal error: /home/ewhite/src/tools/kadischi/livecd-mkinitrd.sh
returned non zero (256) exit code. Aborting execution.
Anaconda can't find a kernel, even though there's a
kernel-2.6.9-1.667.i686.rpm in the repository. In fact there are several
flavors (i586, smp, etc.) of that kernel -- is that the problem?
Anaconda's db search is producing more than one result and reverting
back to the initialized value ("None")?
I thought it was b/c I hadn't built my customized repository correct so,
instead, pointed Kadischi at my rsync'ed FC3 directory, and used the
minimal-livecd ks script provided in the Kadischi distro, producing the
same results.
I applied the Kadischi python patched to the anaconda-10.1.0.2-1
installation that's current in the FC3 repository, and the patch process
didn't complain; i.e., I'm running on an FC3 system, trying to produce
an FC3 Kadischi LiveCD.
Any help is greatly appreciated.
Eric
17 years, 8 months
