> Now, if only zones were configurable through the > jumpstart mechanism. And, if only WANboot worked > with the jumpstart filesystem layout, instead of > everything having to be in a single flat directory. > Then it would be really nice, and I wouldn't have my > engineering team scrambling to try and figure out > how to do truly remote builds and writing extra > tools to do zone configuration.
I'm not sure what you mean by "if only WANboot worked with the JumpStart filesystem layout". JumpStart does work with WANboot. But why do you even need WANboot? This is more indicative of an architectural problem than a technical problem. Why didn't your engineering team write a spec for a Solaris IPSec crypto router/firewall? Then you wouldn't need WANboot because everything would be going over the VPN. And, if you configure a DHCP server for JumpStart, you don't need WANboot either because DHCP can span networks via another DHCP relay server. The bonus is that JumpStart then supports PXE in addition to installing SPARC based systems. Much more scalable than WANboot. This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
