[PATCH] install-boot.sh support for rhgb
by Essien Essien
[seems i sent a mail without the attachement already?]
the attached install-boot.sh looks for rhgb in the livecd temp build
directory, if installed, it appends it to the kernel line.
also, i've added 'quiet' to the main kernel line but not to the 'test'
kernel line.
18 years, 3 months
FC5T2 Kernel Panic
by Chitlesh GOORAH
Hai there,
Last night I did some BAB programming just to get kadischi working.
Ive forced livecd-mkinitrd to read certain broken links.
creating iso image /tmp/FC5.iso
Warning: using transparent compression. This is a nonstandard Rock Ridge
extension. The resulting filesystem can only be transparently
read on Linux. On other operating systems you need to call
mkzftree by hand to decompress the files.
Unknown file type (unallocated) /tmp/livecd-build_no29/compressed/.. -
ignoring and continuing
My question is what is causing this :
Unknown file type (unallocated) /tmp/livecd-build_no29/compressed/..
does it have to do with the following kernel panic ?:
VFS: Mounted root (ext2 filesystem)
/bin/ash: error while loading shared libraries: libsepol.so.1
: cannot open shared object files : No such file or directory
EXT2-fs : unable to read superblock
isofs_fill_super : bread failed, dev=md11, iso_blknum=16, block=32
kernel panic - not syncing : VFS : Unable to mount root fs on unknown-block(9,1)
This reminds me about a libsepol.so.1 that Jasper mentioned before.
--
http://clunixchit.blogspot.com
18 years, 3 months
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
18 years, 3 months
Kadischi under FC5tx
by J. Hartline
Hi.
A patch submitted to the anaconda devs has made it into anaconda-10.91.14-1
which allows Kadischi to be used without patching Anaconda by users, and
without
the --livecd switch, eliminating the partitioning screens.
This of course only applies to FC5 Test platform testers.
Thanks.
J. Hartline
18 years, 3 months
Meeting times
by J. Hartline
Hi.
I am curious if we had decided on a set meeting schedule..
Have we done this?
I still propose 14:00 GMT and 20:00 GMT on Wednesdays, or
since someone mentioned that Wednesday wasn't a good day, 14:00 GMT
Wednesdays
and 20:00 Saturdays.
Had we decided?
J. Hartline
18 years, 3 months
Meeting times
by J. Hartline
Hi.
It seems like since some of us are on different sides of the worlds
perhaps we should on every Wednesday, have meeting times set at Greg's
original
proposed time, 14:00 GMT, and then again at 20:00 GMT?
What do you think? Send back a reply.
I think this would give all of us a 'Time to meet' at the least
also open up an avenue for people wanting to attend but may not make it
to one, or another.
Is this redundant, is it going to create too much out-of-sync'ness?
Surely not if both meeting notes are posted somewhere, by someone.
J. Hartline
18 years, 3 months
kadischi on 2006-02-01 rawhide
by Andy Burns
Ok, after tonight's meeting, I said I'd check the status of kadischi
with current anaconda, building a rawhide cd *on* rawhide.
I checked out kadischi from CVS
configured, built and installed it no problems as per the wiki instructions.
I have a local mirror of rawhide, on a machine called "shuttle" so
attempted to built from it as follows
# kadischi http://shuttle/fc5/x86_64 my.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)
URL http://shuttle/fc5/x86_64 contacted. OK
URL http://shuttle/fc5/x86_64/Fedora contacted. OK
URL http://shuttle/fc5/x86_64/Fedora/base contacted. OK
URL http://shuttle/fc5/x86_64/Fedora/RPMS contacted. OK
Repository seems to be OK.
Checking required packages
Looking for config file
Loadnig config file options
*** running anaconda ***
Error bad argument --livecd: unknown option
:
*** Fatal error: anaconda returned non zero (65280) exit code.
Aborting execution.
Cleaning up temporary files...
Done.
Chitlesh seemed to think that no anaconda patches were now required,
but I'm on today's version ...
# yum info anaconda
Name : anaconda
Arch : x86_64
Version: 10.91.11
Release: 1
but this is exactly the same point I got to on 2006-01-08, I saw in
changelog for anaconda about bypassing the partitioning screen, but that
seems to be only in text mode
so I applied the anaconda/flags patches
# 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
the failing hunk is the same that failed when I tried earlier, it is the
section that adds "livecd" to the option list, the array has changed
enought that patch won't apply it, so I added it by hand, I'll amend the
patch to apply cleanly and post it to bugzilla (and cvs later)
# 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).
that applied cleanly, so tried again this time in text mode
# kadischi --text http://shuttle/fc5/x86_64 my.iso
this time at least anaconda starts, gives me the betanag and country
selection screens, but still hits the partitioning screen, sorry this
isn't going to paste very well if you've not using fixed spacing, but
you get the gist.
┌────────────────────────┤ Partitioning Type ├─────────────────────────┐
│ │
│ Installation requires partitioning of your hard drive. By default, │
│ a partitioning layout is chosen which is reasonable for most users. │
│ You can either choose to use this or create your own. │
│ │
│ Remove all partitions on selected drives and create default layout. │
│ Remove linux partitions on selected drives and create default layout.│
│ Use free space on selected drives and create default layout. │
│ Create custom layout. │
│ │
│ Which drive(s) do you want to use for this installation? │
│ ↑ │
│ ▮ │
│ │
│ ┌────┐ ┌──────┐ │
│ │ OK │ │ Back │ │
│ └────┘ └──────┘ │
│ │
│ │
└──────────────────────────────────────────────────────────────────────┘
since there are no drives on the list you can't select one. so when you
continue it gets an error that you didn't select one
┌──────────────────┤ Error ├───────────────────┐
│ │
│ You need to select at least one hard drive │
│ to have Fedora Core installed onto. │
│ │
│ ┌────┐ │
│ │ OK │ │
│ └────┘ │
│ │
│ │
└──────────────────────────────────────────────┘
jasper have you got further than this? If so what version are you
working with, are you on rawhide, building a rawhide CD?
I wonder where the "rumour" that you no longer need the patch came from?
there's certianly no mention of "--livecd" in anaconda without it.
Anyway, enough for tonight ....
Andy.
18 years, 3 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
18 years, 3 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
18 years, 3 months