The first task you must complete to configure Boot@Boot is to configure VNC support so that the SunPCi III cards have an X server available that is guaranteed to be running and accepting connections when the cards boot. If you want to use another X server to display your SunPCi consoles, and the X server is guaranteed to be available for connections at all times, you can choose not to use VNC support. See “Using an X Server Other Than Xvnc” on page 127.
To configure VNC support, you must first add VNC support to the file /etc/Master.ini by using the following command:
#/opt/SUNWspci3/bin/sunpcidadm -a VNC
This adds the necessary configuration information that the daemon needs to start the Xvnc server.
Note – The sunpcidadm command is case insensitive when referring to VNC or to cards, so that the commands sunpcidadm
When you initially add the VNC configuration information to the file /etc/Master.ini, VNC is configured as disabled by default. This is so that you can customize the configuration information before Xvnc starts.
For example, if you want to run VNC and the SunPCi sessions under an account other than the root account, you can modify the user ID, group ID, and home directory for the user. Note that if you change the user name for VNC, the vncviewer application will expect you to type the password for that username when connecting to the Xvnc server, rather than the root password.
In this way, you can give administrators for the SunPCi cards full access to them without having to give them the root password to the machine in which they are installed. If the accounts you specify are not NIS or NIS+ accounts but rather local accounts, the accounts must have read access to the /etc/shadow password file.
Chapter 11 Using SunPCi III Software 121
