How To Set Terminal Type in Solaris 10 Jumpstart?
Hi all,
I'm installing Solaris 10 via jumpstart, and I'd like to set the terminal type for the console to be vt100 by default.
I've tried setting the terminal type to vt100 in sysidcfg, with a line:
terminal=vt100
but this has no effect (and never has done).
In previous versions I just modified /etc/inittab from the finish script, but that's not relevant any more.
I know that I can set the terminal type after login with:
/usr/sbin/svccfg -s system/console-login 'setprop ttymon/terminal_type = vt100'
but I can't do this until the system has booted for the first time.
I've tried putting various bits of XML into /var/svc, but I'm now at the point where I'm just guessing - does anyone know the right way to do this, or can anyone point me in the right direction?
Thanks in advance,
Steve.
# 1
As far as I know, your approach is correct. If you don't want to modify the xml file manually, you can use chroot in the finish script.
# /usr/sbin/chroot /a /usr/sbin/svccfg -s system/console-login 'setprop ttymon/terminal_type = vt100'
Side note, to jump in cli mode, you can use the nowin switch.
ok> boot net - nowin install
# 2
> As far as I know, your approach is correct. If you don't want
> to modify the xml file manually, you can use chroot in the finish script.
Using chroot in the finish script does *not* work, and gives an error:
svccfg: Could not connect to repository server: repository server unavailable.
Modifying xml is fine, but it would be nice to do it in a way that will not get reverted next time I apply a patch cluster, so simply editing /var/svc/manifest/system/console-login.xml would (I think) be out.
Is there a more correct way of overriding the contents of a manifest?
Cheers,
Steve.
# 3
I think the following will do what you want.
svccfg -f /tmp/syscfg.cmd
where /tmp/syscfg.cmd contains the following
repository /a/etc/svc/repository.db
select system/console-login
setprop ttymon/terminal_type = vt100
quit
The chroot method doesn't work because svccfg is running with its root directory set to /a but it's trying to contact the svc.configd process running on the system to make changes. I'm not even sure if that process is running during a jumpstart install.
