[EMAIL PROTECTED] wrote on 07/08/2008 02:08:48 PM: > [EMAIL PROTECTED] wrote: > > 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. > > Note that I wasn't talking about custom install media, just a boot > iso. A network install and kickstart file location, like Paul says, > is definitely the way to go. A makefile in our kickstart cvs repo > makes it trivial to update and deploy both the iso and the kickstart > files when there are changes in either. Like you, at least for the > time being, dhcp is not an option, in our distributed environment. > And frankly, having done both, providing a target name and ip address > at at the 'boot:' prompt is very easy, compared to dealing with mac > addresses and dhcpd configurations, when you're wanting static > assignments anyway. > Duely noted. I haven't setup a more "automagic" method yet, we don't change the install procedure often so its not a big deal as long as its documented. Luckily this method is readily documented, except this easy static IP bit. Also I really should add it to our vcs, don't know why I hadnt.
Thanks -greg _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
