Re: define network in kickstart pre script

rhelv5-list-bounces-H+wXaHxf7aLQT0dZR+AlfA@xxxxxxxxxxxxxxxx wrote on 07/08/2008 
11:11:34 AM:

> If you provide the static networking parameters as options at the
> 'boot:' prompt, and have a 'network' line like this in your ks.cfg,
> then the system gets configured appropriately:
>
> network --bootproto=static --noipv6
>
> In my experience, the system is not configured correctly if you
> provide the network parameters in the dialog boxes.  (Don't know if
> this has changed recently, like since 5.0, but it sounds like it
> hasn't from your comments.)

Thank you!  Let me give that a try.  While that does make for a long boot
option, so did having it inside the url.  But this would be much cleaner.

> Note that if you use a custom boot.iso with custom syslinux.cfg, you
> can provide common parameters within custom targets (nameserver,
> netmask, method and ks location, possibly gateway), and only have to
> provide the ip, or possibly ip and gateway, at the 'boot:' prompt.

My big push internally right now is to try and avoid custom install media.
Previously we've had guys that basically invented a custom revisor and a
custom livecd-creator for rhel3-5.  This, while kewl, has been a big
maintenance nightmare.   Right now we just do a simple netboot iso.  If
your above suggestion doesn't work for us, then I might take this approach.

Thanks.

-Greg