Jack,
You have good ideas about how this might be implemented in a UI. Mostly, I like the way you can conceal details from the ordinary
user in the average installation, and still offer the detailed configuration if the user activates a control.
I think that we have come up with standard name service switch configurations to support the bulk of the supported name service
combinations, so I think we can keep this approach for the future.
Thanks for your ideas,
William
On 06/ 3/11 07:08 PM, Jack Schwartz wrote:
Hi William.
On 06/03/11 01:44, William Schumann wrote:
In order to provide more than one name service in the text installer/SCI tool, proposing modifications to the UI. Please review
and comment on this rough draft.
Change name service selection screen, (which presently allows the user to
choose only one among DNS, LDAP, NIS, or None):
offer check boxes instead of a single selection. The user will be subsequently prompted for configuration of whichever name
services were checked.
Sounds good.
Add another screen after all name service-specific prompting for the user to
enter name service sources, per nsswitch.conf(4).
UI - 1st pass - offer defaults based on the combination of name services
selected.
Allow the user to change the sources and remember them as long as the name
service selections don't change.
If the user uses F3 and goes back and changes name services, upon return to the sources screen, there is an additional message to
remind the user that it may be appropriate to alter sources.
The source screen will have two columns for database and source. e.g. for DNS,
the source screen default could be (rough example):
Name Service Database Sources
You have selected name service: DNS. Enter the name service switch database
and source information.
Database Source
---------- --------
default files
hosts files dns mdns
printer user files
[blank] [blank]
I like the idea of displaying in two columns. That said, I prefer not having
the user type the sources.
There are two things to account for in accepting an entry: that only configured sources are entered, and (if nsswitch
functionality is followed completely) what happens when a requested database entry is not found, or the source is busy or not
responding.
(For example, "nis [NOTFOUND=return] files".)
One possible solution is to provide a radio button next to each row in the source screen table, which, when clicked, brings up
another window.
In the new window is a table where each configured source can be ordered. This can be a place to assign a numeric value to each
source, or using +- keys to shift the order (a la bios setups for boot devices), or some other means.
Each source would also have a way of configuring NOTFOUND or TRYAGAIN handling. A possible implementation would be an initial
menu which has NOTFOUND and TRYAGAIN, and submenus containing "return"; "continue"; and for TRYAGAIN, "forever" and a way to
enter a numeric value. The default would be "NOTFOUND=continue".
Also, just shooting the moon here, if a source set up by these menus is later unconfigured, it would subsequently show up in these
menus as red, or grayed out, to indicate it is invalid, calling it out as requiring change.
Thanks,
Jack
...
[additional message here]
Additional messages may include:
-A default list of databases and sources are provided above. You may edit
them, or accept the defaults.
-Note: since the name service was changed, consider changing sources
accordingly.
The UI field validator for sources would permit only known sources and source
values per nsswitch.conf(4)
Thank you for your attention,
William
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
install-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/install-discuss
