Hi Jan. [ ... ]
Not sure what the right answer is... I'm envisioning huge system segmented into many virtual systems, each with their own monitor. That means that the monitor would need to be supported by X or some remote window system. Does that mean xterms are best? OTOH, Keith says it's hard to go wrong with VT100. I'll leave this one to you guys, the experts :)OK. Setting the term type to a default value when the SCI tool is used standalone (after an install) seems like a good idea, since I assume that each non-global zone will likely operate on its own screen and so one cannot know how to set it up beforehand.* When running SCI tool as a standalone application, I can think about following possibilities:[a] terminal type would be configured to 'vt100'. User would be made awareof that on Summary screen.[b] terminal type setting would reflect the one configured on running system[c] terminal type would not be configured at allI slightly prefer [a], since it seems desirable approach in case SCI tool is usedto configure non-global zone.That said, why not set it to the same text-installer default values based on Sparc-monitor/X86-monitor/serial-console instead of vt100?We perhaps could do that. Looking at the algorithm (*), we would end up with 'xterm' in non-global zones. If this is acceptable, then I am fine with that approach.
Thanks,
Jack
Thank you, Jan(*) http://src.opensolaris.org/source/xref/caiman/slim_source/usr/src/cmd/text-install/svc/text-mode-menu.ksh#83
_______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
