On Nov 29, 2007 11:18 PM, Kyle McDonald <KMcDonald at egenera.com> wrote: > Whatever it ends up being, it should be enduser/site extensible. Like > DHCP I should be able to create my own 'options' or key-value pairs > which I can use to store informationabout how I want a machine > installed. The mini root should have something (like dhcpinfo) that will > allow me to look up my options or keys in my begin or finish scripts, > or outside the miniroot on first (and maybe any other) boot up.
+1 This will likely also imply that Sun's DHCP server and client need to know how to deal with vendor/site options that don't fit into 255 bytes. My fuzzy memory tells me that the ISC DHCP server can pass multiple chunks of vendor/site options if the first one extends beyond 255 characters. In my environment today this leads me to do things like: ./setup_install_server <path>/Solaris_10_2007_08_sparc cd <path> ln -s Solaris_10_2007_08_sparc S10U4S ln -s S10U4S/Solaris_10/Tools/Boot S10U4S-b I then reference <path>/S10U4S and <path>/S10U4S-b as required. This same 255 byte limitation forces me to never use host names (especially FQDN) in any DHCP value. -- Mike Gerdts http://mgerdts.blogspot.com/
