>From a running Centos liveCD (minimal) I want to launch anaconda with a
kickstart file. Right now we build a small ISO using isolinux that
loads the kernel and points it to the kickstart file on an HTTP server
(ks=http://blah.blah.blah/ks.cfg). But I want to gather some info from
the user and test some networking connections before launching anaconda,
thus the need for the liveCD. I've got anaconda included in the livecd
and I can call it, but when I try to pass
--kickstart=http://blah.blah.blah/ks.cfg, it says 'no method specified'.
So, I added -m http:// with a path to the repos we use with our regular
installer, but while anaconda starts, it starts asking questions about
language, keyboard, etc., meaning it's not reading the kickstart file.
Note that I don't want to install the configuration that makes up the
livecd onto the hard drive; I want to use what we've defined in the
kickstart file. I thought I'd be able to use the same syntax as in the
installer ISO I currently build, but that doesn't seem to be working
(why not?) Is what I want to do feasible? Am I just not getting the
syntax right? TIA.
I've got a problem with the script "livecd-iso-to-pxe"... It creates the right files (under /tftboot directory) but I can't pxeboot a machine with this configuration.
During the pxeboot, initrd is loaded and kernel starts the execution, but it looks like it can't run (or find) the init process...
Have you ever got this problem before?
Unfortunately I haven't got any error message to show you (just kernel logs on the console during the boot... but without error... just the kernel, no messages from init script...). I'm using fedora11
Le me know if you know a solution for this problem
I would like to add "console=ttyS0" to the append line in the isolinux.cfg
file in order to capture boot messages when testing liveCDs.
I notice that the live.py script includes an $(extra) parameter. Is it
possible to add "console=ttyS0" to this $(extra) parameter? If so, where
should it be set?
Is there a better way to pass such parameters directly through the kickstart
file, such as with the "bootloader" parameter?
I am getting an error parsing a ks file with the latest version of
livecd-creator, see below. Has anyone seen any errors like this before,
or know what could be causing this error?
[david@RAWHIDE2 ovirt-node-image-devel]$ sudo livecd-creator -c
/usr/share/ovirt-node/ovirt-node-recipe.ks -d -v
Using label 'ovirt-node-r-x86_64-200910081644' and name
Traceback (most recent call last):
File "/usr/bin/livecd-creator", line 140, in <module>
File "/usr/bin/livecd-creator", line 112, in main
ks = imgcreate.read_kickstart(options.kscfg)
File "/usr/lib/python2.6/site-packages/imgcreate/kickstart.py", line
56, in read_kickstart
except IOError, (err, msg):
ValueError: need more than 1 value to unpack
[david@RAWHIDE2 ovirt-node-image-devel]$ ksvalidator
[david@RAWHIDE2 ovirt-node-image-devel]$ ksvalidator -v DEVEL
The version DEVEL is not supported by pykickstart
[david@RAWHIDE2 ovirt-node-image-devel]$ ksvalidator -v F12
[david@RAWHIDE2 ovirt-node-image-devel]$ ksvalidator -v F11
[david@RAWHIDE2 ovirt-node-image-devel]$ cat /etc/redhat-release
Fedora release 11.92 (Rawhide)
[david@RAWHIDE2 ovirt-node-image-devel]$ rpm -q livecd-tools
[david@RAWHIDE2 ovirt-node-image-devel]$ rpm -q pykickstart
[david@RAWHIDE2 ovirt-node-image-devel]$ rpm -q python
We have our development servers here where I work that are running CentOS
5.2 64-bit on them. One of our projects has a LiveCD that we build and
provide. It is currently built on a Fedora 8 PC that I have but we'd like
to move to Fedora 11 or 12.
What I'd like to do is put the Fedora 11 RPMs on our server, run
createrepo to create a repository, and use livecd-creator on that server
to build the Fedora 11 LiveCD. Is this approach possible? Are there any
"gotchas" I need to be aware of if it is possible? The LiveCD is a 32-bit
Common ARTS Software Development
Daniel J Walsh wrote:
> On 09/29/2009 03:45 PM, Jay Greguske wrote:
>> Jeremy Katz wrote:
>>> On Fri, Sep 25, 2009 at 8:59 AM, Jay Greguske <jgregusk(a)redhat.com> wrote:
>>>> Jeremy Katz wrote:
>>>>> There have been some problems more recently with the booleans stuff if
>>>>> SELinux isn't enabled. Does that all end up working correctly still?
>>>> I'll look into it. Are there any you have in mind specifically?
>>> Dan might remember better than I -- I vaguely remember that a lot of
>>> the home directory bits and also some of the xguest stuff requires
>>> working booleans
>>> - Jeremy
>> I installed xguest to a running livecd (desktop ks file) and played with
>> two booleans related to it: browser_write_xguest_data, and
>> xguest_connect_network. With the former turned off the Guest account
>> could not download files from random internet sites, and with the latter
>> it couldn't connect at all, so I'd say they were functioning as
>> expected. I'm pretty confident SELinux booleans are working correctly
>> with these changes. If you have other tests to suggest I'd be happy to
>> try them out.
>> - Jay
> How much work would it be to create a livecd with only an xguest login.
> Random Root password and no user accounts.
> So the cd could only run xguest. I know if you can boot the cd you can beat the system, but it might be a cool demo.
Should be pretty easy: you just need the right kickstart configuration
file. While things are quiet this week I'll see if I can produce that