On Sun, Jun 24, 2012 at 8:13 PM, Bob Cochran <bcochran13(a)verizon.net> wrote:
Hi!
I just used cobbler to install Fedora 17 x86_64 on my laptop, and it worked
quite nicely! I copied the sample.ks kickstart provided by cobbler to
sample1.ks file and modified that to comment out the skipx line thinking
this would get me a graphical install:
# skipx
My laptop booted pxelinux.0, but then I got error messages from dracut such
as this:
dracut Warning: no suitable images
dracut Warning: unable to process initqueue
After some thinking and research about this I realized that the profile I
added named "Fedora-17-x86_64" was not pointing at a kickstart file, so I
edited it:
cobbler profile edit name=Fedora-17-x86_64
--kickstart=/var/lib/cobbler/kickstarts/sample1.ks
Then I tried another installation attempt. This stopped abruptly with the
error message:
The following error was found while parsing the kickstart configuration
file:
Section %pre does not end with %end
Yes, this needs to be fixed. It used to be optional but appears to be
required now. It's just good practice to have it anyway.
So I added %end to the end of the %pre, %packages and %post.
This got me a successful and basic non-gui installation. I was able to
reboot, login as the root user, and do a yum update.
The "text" option is in the default kernel opts in
/etc/cobbler/settings - remove that and you should get a GUI.
I have some questions. I want this laptop computer to start
interface
'wlan0' (the wireless card) most of the time and connect to ssid
'hygrophila' if possible. If it is plugged in to a wired connection,
interface eth0, then it should prefer that instead, and I want to assign it
a static ip address. How do I do this? Do I pass a network string through
the cobbler system I have defined for this laptop?
Or, should I be passing system-specific settings through "snippets"?
Doing everything but the SSID should be supported out of the box with
cobbler. For the SSID part, I'd edit the network snippets (pre and
post) to read the SSID from ksmeta and set it that way.
Evidently, I am going to need to edit sample1.ks a few times and then
do a
fresh install on the laptop after each round of editing the kickstart, until
I get it correct. I assume that if I change the "system" entry
netboot-enabled=false to netboot-enabled=true, this will let me try out a
fresh install and see if I got it right.
Yep.
Likewise, if I want to set the hostname of the laptop, I should be
doing
this through the system entry, rather than through the kickstart.
Yep.