http://defect.opensolaris.org/bz/show_bug.cgi?id=11864
Summary: nwamcfg is too case-sensitive
Classification: Development
Product: nwam
Version: RC1
Platform: ANY/Generic
OS/Version: All
Status: NEW
Severity: minor
Priority: P4
Component: CLI
AssignedTo: nwam-dev at opensolaris.org
ReportedBy: renee.danson at sun.com
QAContact: nwam-dev at opensolaris.org
--- Comment #0 from Renee Danson Sommerfeld <renee.danson at sun.com>
2009-10-10 02:03:33 UTC ---
Feedback from a beta user:
* From an ease-of-use perspective, the case-sensitivity of objects
such as locations and NCPs, coupled with the use of capital
letters by default (e.g. the "User" NCP and the "NoNet"
location) makes life frustrating with nwamcfg. Given the
intended audience, I think we'd be much better off with a system
that preserves case but is not sensitive to it. For instance, a
user could create a "SWAN" location and it would show up as
"SWAN", but the user could select "swan" to get to it. The user
would not be able to create another profile named "Swan" "swan"
or any other variant that differs only with respect to case.
* A related issue: various NWAM objects like NCPs should not be
case sensitive. That is, both "select ncp" and "select NCP"
should work in nwamcfg. As it is, NWAM lists objects with
headings like "NCPs:" but then refuses to accept "NCP" as an
object type, which makes things more frustrating than necessary.
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
