David Murphy wrote:
> One additional feature I'd copy from JumpStart is centralising the
> config files. For those not familiar with JumpStart, ther's a rules
> file that is basically a table of identifiers against configuration
> profiles,. Identifiers can be things like IP address, ethernet
> address, architecture, size of the root disk, etc. etc. It's nicer
> 'cos you don't need to have a different boot procedure for different
> types of install client, i.e. you'd have just the one boot floppy on a
> typical PC, or execute just the one network boot command on machines
> that can boot off the net.
with kickstart the id can just be your ethernet address, but kickstart
can go fetch your ks.cfg file from an nfs server. the dhcp server needs
to specify a "filename" attribute and a "next-server" attribute for the
ethernet card. that seems slightly more difficult then just running a
script to make the floppy (since you'll need a floppy anyway).
with solaris the boxes had the smarts to boot off the net, so editing a
bootp config file and /etc/ethers was fine. but since you have to make
a floppy anyway for intel boxes...
kevin at suberic.net "we were goin' for breakfast. in canada. we
fork()'ed on 37058400 made a deal: if she'd stop hookin', i'd stop
meatspace place: home shootin' people. maybe we were aiming high."
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!