Rescue cd ?
by Chitlesh GOORAH
On http://fedoraproject.org/wiki/FC5Future,
I quote :
---------
Some people are working on LiveCD already. Should also be usable as
rescue media.
---------
Is the rescue mode another argument to pass to the kernel ?
because in install-boot.sh, Ive added
-----
label rescue
kernel vmlinuz
append initrd=initrd.img rescue
-----
on "rescue", it simply boots the livecd.
Does the rescue mode require another kernel?
Is there any "special" fedora based manual for creating rescue cds ?
Jasper, your name too : http://fedoraproject.org/wiki/FC5Future :)
--
http://clunixchit.blogspot.com
18 years, 1 month
yum in kickstart %post
by Brenton Rothchild
Hello everyone,
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
+if chroot:
+ 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
+if chroot:
+ 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
as well?
Thanks!
-Brenton Rothchild
18 years, 1 month
wiki Kadischi/Contributors page
by J. Hartline
Chitlesh,
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
project.
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.
Here though:
"Project Maintainer"
"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:"
"1. development/coding"
"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.
J. Hartline
18 years, 1 month
Suggestion: Optimizing LiveCD-speed
by Thijs H
Hi all,
I just noticed Accelerated Knoppix: It has a boot time under 60 seconds !
Unfortunately I'm not a developer, but if someone is looking for a way to
improve boot-speed, have a look at
http://www.alpha.co.jp/ac-knoppix/index_en.html
An other possibility for improving the speed of a Fedora LiveCD is using
copy2ram, that makes the LiveCD boot slowly, but when booting is finished it
works very fast.
- Thijs
18 years, 1 month
Re: Kadischi Xen kernels
by J. Hartline
>
>
>Chitlesh wrote:
>
>ok, can we leave this for next time?
>It would be nice to smooth the rough edges of the livecds so that we
>might have an Official livecd.
>JesseKeating will offer me the opportunity to grab FC5 before its
>release. So quicking the livecd would be good before FC5 release.
>
>
Ok. The link Rahul sent with the unresolved kernel issue, is fixed.
That is the patch I sent to the list and have checked into b.r.c.
( kadischi-nokernel.patch
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=178623 )
If there is more you are referring to just give me a list or whatnot,
and I'll see if I can provide you with
some suggestions.
Some things I think you should consider in this instance of a Fedora
Core 5 test 3 CD
is having 01umountproc.sh in Kadischi's post_install_scripts be nuked in
place of
01prelink.sh(In CVS) _or_ you can do this locally, and wait until later
to check-in prelink somewhere else than post install.
Besides that you'll need to mention what you are thinking, I don't read
minds. :-P
J. Hartline
18 years, 1 month
Kadischi - Xen kernels
by J. Hartline
Chitlesh
It seems to be that isolinux doesn't support .gz gzip compressed kernels
as Grub would.
This is easy to fix considering we use Grub and Isolinux, or just move
to using Grub altogether.
Give me some feedback so I know what would be best.
Surely there are some users on this list that would want Grub too no?
I think using Grub solely would work for the Kadischi overall.
J. Hartline
18 years, 1 month
Requested Features
by Thomas Canniot
Hello,
I grabbed some request features about Kadischi during the Kadischi Show
at FOSDEM 2006.
Here they are :
- One should be able to be warned if the media he is planning to burn
the iso image on is big enough. This can be summed up by a question in
Anaconda like: "Do you want to create a CD iso image or a DVD iso
image?" Then either Kadischi or Anaconda should warn that the size of
the .iso file will not be appropriated.
- Improve boot speed. Don't know how.
- The live CD should not be dependent from the display driver (already
working on this I presume?)
I know, this not a long list of request features, but that was what
people told me about first.
Thomas Canniot
18 years, 1 month
Kadischi Xen kernels [PATCH]
by J. Hartline
Hi.
Chitlesh brought up installing Xen kernels weren't working.
Here I've attached the kadischi-nokernel.patch that fixes this also.
The patch attached here patches against the CVS as of today (03-1-2006)
and shouldn't be applied consecutively with any other nokernel patches.
(This will be submitted to b.r.c and the previous patch obsoleted)
Chitlesh, you were also talking about users not having CVS access, or it
being blocked..
I have put together an SRPM and RPM for kadischi.
You can find them here: http://autopsy.thetabox.org/SRPMS and
http://autopsy.thetabox.org/RPMS/i386
if you want to direct users towards those, that should be sufficient,
and more reliable/productive than just a CVS tar.gz for download.
I've used Kadischi's version as sta6ted and pl4 in the release. (For
patchlevel).
If you have any patches or features you want to include in here, just
send them with an explanation
and I'll rebuild and re-upload the SRPM and RPM.
Please test this patch if you can. I've tested it here.
If you could also generate a patch for Anaconda and send to the Anaconda
devs to get kickstart working for FC5(Final)
that would be great too. If not I'll do it, just let me know.. FC5 is on
the horizon.
Thanks.
J. Hartline
18 years, 1 month
