SystemRescueCd can be accessed remotely using VNC when it is configured to run a VNC server. The tightvnc package has been compiled with the server support. It means a Vnc server can be started on SystemRescueCd so that you can graphical applications (such as GParted) from another computer (the vnc client).
It means you have the ability use the graphical environment remotely. All programs will be executed on the computer running SystemRescueCd, and the user is working on another computer. There are VNC client for most platforms (Linux, Solaris, Windows, MacOs).
To use this new feature, you can either configure and run the VNC service by
hand, or use the
vncserver=x:password option on the boot command line
(where x is the number of displays you want). The password must be between
6 and 8 characters, else the boot option is ignored.
Do not forget that your network must be configured so that you can connect to
your VNC server. You can use either the
dhdhcp option for dynamic
gateway=ipaddr/cidr for static network configuration.
If you start with
rescue64 vncserver=2:MyPaSsWd ethx=192.168.124.10 then
SystemRescueCd will configure the Ethernet interfaces with the static IP address
given and it will start the VNC server. Two VNC displays will be configured
(display 0 and display 1). Both are using the same password when you
authenticate. By default, the VNC servers listen on the port
So in that case the VNC server will listen on both
tcp/5900 (display 0)
tcp/5901 (display 1). Since you have two displays, two users can
connect to two different graphical sessions using such commands:
vncviewer 192.168.124.10:0 and
If you just want one vnc session, you just need one display. You can just use
rescue64 vncserver=1:MyPaSsWd ethx=192.168.124.10 and you will be able to
connect using a command such as