So an unconfigured system doesn't behave properly, and you have to hard
code it? Is an ON bug filed against that problem?
liane
On 9/19/11 1:08 AM, Jan Damborsky wrote:
Hi Seth,
that code is run on unconfigured system as part of configuration process
and tries to determine terminal type usable on that system. That value then
ends up in appropriate smf property of console-login service at the end
of configuration process.
Thank you,
Jan
On 09/16/11 19:29, Seth Goldberg wrote:
Hi,
I thought we were storing the terminal type for physical console in
SMF now as a property of the console service-- wouldn't it be better
to look at that property instead of hard coding sun-color?
--S
On Sep 16, 2011, at 6:17 AM, Jan Damborsky<[email protected]>
wrote:
LGTM, William.
Thank you for taking care of that,
Jan
On 09/16/11 13:57, William Schumann wrote:
https://cr.opensolaris.org/action/browse/caiman/wmsch/7090443/webrev/
Applied Jan's patch. Tested with zone in 173 - terminal type vt100
appeared in summary (sun-color previously appeared).
Tested with fsh-weakfish (x86) sysconfig create-profile - also comes
up vt100; this fix changes the default terminal type for x86 global
zone as well as non-global zones from sun-color to vt100.
Modified test_system_info.py for manual testing. Passed.
Thanks,
William
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
