RE: 2.1AS kickstart - manual network config CD/DVD install

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 14 Mar 2005, Andrew Rechenberg Lists wrote:

> > Take a look at setInstallData() in kickstart.py.  
> > self.readKickstart() gets called twice, once before %pre and 
> > once after (or at least it does so in RHEL 3).
> 
> The kickstart.py in RedHat/instimg/usr/lib/anaconda on a RHEL2.1ASU5
> disc only calls self.readKickstart() once :\  I guess I could patch my
> kickstart.py to read it twice.  I'll check that file on 3 or later and
> modify mine accordingly to see if that works :)

Stop using a distro which is a couple years old.  (:

> > > In my ks.cfg I have "network --bootproto dhcp --device 
> > eth0" and then 
> > > in the %pre section I prompt for network configuration 
> > information and 
> > > then use sed to change the "network" line, redirect the output to a 
> > > temporary file and then copy this temp file back to /tmp/ks.cfg.
> > 
> > Why not take the network setting out of your kickstart file 
> > and have anaconda prompt for it with it's own network screen?

> From what I've read in other threads, when doing a CDROM-based kickstart
> on distros before RHEL3, anaconda doesn't care if "network" is missing
> and uses DHCP automatically and doesn't prompt.  I can certainly try it
> though :)  I'll try that first since I don't have to mess with modifying
> anaconda.

If that's happening, take a look through kickstart.py for something that 
looks like 'dispatch.skipStep("network")' and comment it out (it's 
probably in setSteps()).

--Patrick.


[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux