The F9 version of livecd-tools usese /usr/sbin/lokkit to enable and
disable the firewall. There is a FIXME near it to suport the rest of the
options which lokkit takes. The current implementation executes this in
the chroot environment, so forces several packages to be deployed into
the image when it is built. Since I would be curious in reducing the
package set for the images which are built, I am curious if there are
plans around any of the following:
1) Remove the use of lokkit and instead directly manipulate the files
(or perhaps use augeas).
2) Look to break up system-config-firewall-tui so that lokkit is a
separate package with less dependencies.
I meant to get to this a little while ago, but then the world exploded.
Anyway, the kickstart configs for all of the various live images now
have their canonical location in the spin-kickstarts git repo
I've removed the configs from the livecd-tools repo, leaving just the
minimal test config because it's handy to have around.
Also, I'd like to do a release this week with all of the changes which
have accumulated. If you've sent a patch and I haven't applied it,
assume that I missed it and please resend. :-)
Is there a way from within livecd-creator and/or the kickstart files to
reduce the isolinux timeout on the livecd?
By default the timeout in isolinux.cfg is 100 seconds, and I would like
to reduce that to something more reasonable for my purposes.
bootloader options in the kickstart file only affect the timeout of the
boot menu after isolinux has passed control to the livecd's grub.
Any info would be greatly appreciated.
<warren> jeremy: btw, any idea why if I create a livecd while enforcing,
the resulting image when booted cannot do /bin/su?
<warren> jeremy: F9 host, F9 target image
<warren> jeremy: it seems fine if I setenforce 0 before livecd-creator
<jeremy> warren: with f9 updates? if so, I *thought* all of the selinux
userspace bits for enforcing had been pushed. but I didn't keep that
close of an eye on them. eparis would be the one to ask
Currently if I make a LiveCD of F9 + updates on a F9 host,
livecd-creator seems to succeed. But if I boot that live image, I am
unable to run /bin/su because of a denied permission. setenforce 0
prior to livecd-creator creates a working image.
Are we missing bits pushed to F9 updates that would allow enforcing to
be enabled and to create a valid LiveCD image?
I have created and installed Fedora 9 live-cd images to my usb device.
then i begin to update some packages, well the "update" appeared to go well
and while running from the usb device before during and after updates seemed
good and now the "but" part upon rebooting got this message:
Bug in initramfs /init detected. Dropping to a shell. Good Luck!
the same problem experienced with Gnome and Kde. :S
Hi! i use fedora 9 live usb, work perfect but the problem happens when i
install something :S like 100 mb of stuffs, different rpms, and then
happens 2 things or it just freezes or the next time i boot it says IO error
and drop me to a shell :S any help?
I notice that, in at least these versions (probably most versions):
that the -l (lower-case L) option is used on the call to restorecon in
kickstart.py. As far as I can see, there is no "-l" option to
restorecon, so this will never succeed. In fact, I had to remove it in
order to get a working live CD image. Is there something I'm missing here?
well, today i played a little bit with the livecd-creator tools on CentOS
5.2 and I think it is awesome. Well, at work, I have to administrate some
CentOS 5 and RHEL 5 Proxy Servers, and I have the problem, that once a
while, I have to create a new Install CD, which is a custom CentOS / RHEL CD
with a kickstart Installation on it. Right now, I have the problem, that
when I build a new CD it should use the actual Packages out of a repository
on my Server. Right now, I have to do it by hand to exchange the files like
kernel rpm or other packages to have the updated Packages inside the new CD.
After looking at livecd-creator, I search something like the mechanism for
downloading the rpms from a repository. So something like: look at my
comps.xml to see what should be installed and download it from a repo. Also
a system with a kickstart file would be ok, like: create a kickstart file
with all rpms that should be installed, download the RPMs, and do the other
stuff to prepare the installation CD. Maybe one of u guys have an Idea how
to manage that.
Thanks in advance.
Mit freundlichen Grüßen / Best regards