> No, that was never the case. > We *did* ship a "Developer Edition" that had NWAM enabled by default, but it had nothing to do with the DHCP selection. That > wasn't SXCE, and instead was the forerunner of the OpenSolaris distribution. It was the first test of the new installer.
> (Yes, this forking has been confusing ...) Oh well, I must have just been luck getting the 'first test of the new installer'. BTW, what is the purpose now of making SXCE Nevada releases still if Indiana (2008.05 / 2008.11) aka OpenSolaris seems to be the default/preferred(?) offering now? I must admit to being a little confused :) 2008/11/24 James Carlson <[EMAIL PROTECTED]> > Simon Breden writes: > > That's interesting, because from memory (it was some months ago), > previous > > SXCE (nevada) installers easily allowed me to select DHCP and the host > name, > > and then NWAM was installed for me and everything worked straight out of > the > > box (could use internet from firefox immediately). With the latest SXCE > > (nevada b101), you can see what happened for me... > > No, that was never the case. > > We *did* ship a "Developer Edition" that had NWAM enabled by default, > but it had nothing to do with the DHCP selection. That wasn't SXCE, > and instead was the forerunner of the OpenSolaris distribution. It > was the first test of the new installer. > > (Yes, this forking has been confusing ...) > > > Never mind, system is working now, so that's all that matters. Again, > thanks > > for your help. > > Good to hear. > > -- > James Carlson, Solaris Networking <[EMAIL PROTECTED]> > Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 > MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 >
_______________________________________________ networking-discuss mailing list [email protected]
