Linux Remote Desktop Display

One very annoying thing about Linux’s Remote Desktop (rdesktop) command is that you rarely can get a good screen size when remotely connecting to a Windows machine. It’s either too long and you have to always scroll, or worse yet, you are looking at an 800×600 view of your remote desktop.

Fortunately, the Linux crew has thought of a consistent way to get around this issue. You can tell rdesktop to run in full-screen mode initially. This is a terrific way to automatically get a desktop that fits your monitor’s screen size from the get go. To run in full-screen mode, run the following command –>

>rdesktop -f MyMachine

That’s it! You will have a screen that is fully sized to your monitor. One other thing – To break out of full screen mode, press Ctrl-Alt-Enter. Press Ctrl-Alt-Enter again to return to full-screen mode once again.

Starting a user’s VNC server automatically on Linux

On some Linux systems, it can be advantageous for users to have a way to login to a console. Unfortunately, if they do not have physical access to the machine, there needs to be a way to do it remotely. Fortunately on Linux, there is Virtual Network Computing (VNC). VNC can be set up as a server and I will outline the steps necessary to complete this task.

First, ensure that vncserver is installed on your system. For Red Hat systems type:

>yum list vnc-server

If you see the following message:

Loaded plugins: rhnplugin
Error: No matching Packages to list

You will  need to install vncserver. Using Yum again:

>yum -y install vnc-server

We can now begin configuring VNC. We are going to do this for two users, root and myuser. Each user will access their virtual desktop from separate Internet Protocol ports. Vtxinst will use port 5801 and root will use port 5802.

We first need to edit /etc/sysconfig/vncservers. On line that has

# VNCSERVERS=”2:myusername”

Change it to

VNCSERVERS=”1:myuser 2:root”

Save the file. Now we need to prime VNC to setup its supporting files correctly. Login first as root, then myuser and issue the following command:


You will be prompted for a password if this is the first time this user has started VNC. Then run the following command to stop vncserver:

>vncserver -kill :1

Next let’s edit the user’s ~/.vnc/xstartup so that we use the gnome desktop instead of X windows. In the user’s directory, edit the file ~/.vnc/xstartup and uncomment the following 2 lines by removing the # so that the two lines look like the following:

exec /etc/X11/xinit/xinitrc

Finally, enable vncserver on startup with the following command:

>chkconfig –levels 35 vncserver on

Now, next time you reboot, VNC server will start automatically. If you don’t want to reboot, then run:

>service vncserver start

And VNC server will now be running!

Linux log error – Could not receive trustdoms : xxx Time(s)

When using Samba with Linux, Red Hat Enterprise Linux attempts to connect to a Windows server that acts as the domain controller. This is called a trustdom; as Linux is attempting to build a trust relationship with a Windows Domain Controller. You will see the following message in your log:

——————— samba Begin ————————

**Unmatched Entries**

nsswitch/winbindd_util.c:trustdom_recv(243) Could not receive trustdoms : 288 Time(s)

———————- samba End ————————-

To stop this error message, you need to stop the winbind service. To do this, run the following commands:

chkconfig winbind off
service winbind stop

This will ensure that upon reboot, the service does not start. And the second command ensures that the service is stopped immediately.

Check your log tomorrow to ensure that you are no longer receiving this message.

How to mount a Windows share in Linux

Here is an example of how to connect to a Windows share from Linux:

>mkdir -p /mnt/winShare
>mount -t cifs //192 over at this website.168.x.x/e$ /mnt/winShare -o username=Administrator

First put in the connection information in Linux style notation //IP/ShareName. The share can be a root directory, like the e$ above, or it can be any other defined share on the server.

Windows Vista how to boot up without network

For security, sometimes you do not want your computer to automatically start up allowing network connections. In Windows Vista there is a way to ensure that when your machine reboots, network connections will not be enabled. They will only be enabled once you log in the first time.

To do this, go to Control Panel -> Administrative Tools -> Services.

Then change the Network Connections service to Manual.

This will prevent Windows Vista from establishing or allowing any network connections until the first time you log in.

How to copy Subversion repositories to another server

  1. Ensure you have a working Subversion installation with Apache installed on your system.
  2. On the source machine, dump each repository:
    > svnadmin dump /path/to/repository > repository-name.dmp
  3. Copy repository-name.dmp to the target server.
  4. Load the repository into the new server:
    > cd /path/to/new-repository
    > svnadmin create repository-name
    > svnadmin load repository-name < repository-name.dmp
  5. Reassign apache permissions:
    > chown -R apache.apache repository-name
  6. You are now ready to begin using your repository on the new server!