Peter Memishian writes: > > For SXCE, that means familiar class action and BFU updates (and a flag > > day, since you can't go back without misplacing your keys[1]), but > > most instances of the problem are likely with OpenSolaris (where NWAM > > is the default), and that has no clear mechanism for dealing with > > upgrade-related scripting. > > Assuming we allow "-" and ".", do we think many users are going to have > problems with upgrade? I'd expect most are using alphanumerics, and > spaces already don't really work (hence the bug).
The names that NWAM uses come from the ESSID and BSSID of the AP, and since the ESSID is a free-form string, and may well be "WEP-$uck$" in some locations and "%%%yo%%%" in others, I think there's a problem here, even for those who haven't yet stumbled over the space character problem. I think we've got an obligation to handle this change, or it's going to result in even _more_ anxiety and dissatisfaction with NWAM and with OpenSolaris networking in general. We've had our own problems, but we're also the scapegoat for all the problems elsewhere. -- 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]
