[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
RE: Not really a kickstart question.....
- From: "Meyers, John J" <john j meyers boeing com>
- To: <jake v2gnu com>, "Discussion list about Kickstart" <kickstart-list redhat com>
- Cc:
- Subject: RE: Not really a kickstart question.....
- Date: Wed, 23 Apr 2008 11:31:52 -0700
Hi Jake,
In the %pre section of the ks file, I run a python script that
is VERY derived from the anaconda network_text.py code. This allows the
installer to input the required network info. After which the rest of
the install is automated. I can prefill the subnet, ip to last octet,
DNS server... If you don't have fancy requirements, you should be able
to import network_text *, and call the various modules from anaconda to
provide netconfig functionality. Yeah Kickstart! And long live yum.
-----Original Message-----
From: Jake Vickers [mailto:jake v2gnu com]
Sent: Tuesday, April 22, 2008 10:04 AM
To: Discussion list about Kickstart
Subject: Not really a kickstart question.....
So we can't use netconfig in RHEL5 kickstarts anymore to set the IP
during the installation phase. I can't seem to get the setup-tool to run
on first boot (where you can config the net card, turn off SELinux,
etc.).
Am I missing something obvious, or does everyone else who has a need for
this just script it in the kickstart file?
Thanks for any suggestions.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]