How to supply an IP address in Red Hat's KickstartIgnoring DHCP, there are three ways to supply an IP address when you're using Kickstart to set up machines automatically:
The third option is undocumented but probably unlikely to break in the future, and sometimes quite handy. The Kickstart process assigns the machine IP address very early on,
before Anaconda has started and before the more sophisticated bits of
the Kickstart file are evaluated. Thus, you can't have the IP address
and suchlike generated by a From personal experience, syslinux is the only bootloader that lets you have a lot of boot entries and deal with them sensibly. LILO has a low hardcoded limit, and while Grub can theoretically deal with lots you'll have to scroll through a huge menu; with syslinux you can do things like have a generic USB key that will install any one of a hundred machines with the right IP address options just by typing its hostname. (Disclaimer: this is all how it was in Fedora Core 4 (and earlier versions); I haven't tested FC5 to see if it changed anything.) Sidebar: why not DHCP?I don't like DHCP, because it is very rare that I want a machine's IP address to be assigned based on its Ethernet address. Far more common is things like lab situations, where I want machines to be given names based on their physical location. You can do this with DHCP, but you have to be careful to maintain what is effectively a table mapping physical location to Ethernet address, and I'm not convinced you get anything for the effort. |
These are my WanderingThoughts GettingAround This is part of CSpace, and is written by ChrisSiebenmann. * * * Atom feeds are available; see the bottom of most pages. Categories: links, linux, programming, python, snark, solaris, spam, sysadmin, tech, unix, web |