I wrote previously:
> 1. On departmental server running CentOS release 5.7 (Final) (32 bit)
>
> .....
>
> 'make' worked and produced an apparently usable binary.
> I could not run it as I was logged in remotely from my home machine
> running ctwm.
>
> test:
> % ./ctwm
> ./ctwm: another window manager is already running on screen 0?
> ./ctwm: unable to find any unmanaged screens
>
> My guess is that it would work if this were running on a workstation, rather
> than a headless server.
I thought I would try running ctwm on that machine remotely. So I killed my
local ctwm (on Fedora 19 PC at home), and used an xterm window to log in
remotely to the departmental server running CentOS. I launched ctwm from there
and it worked, though it took a long time to get started.
Unfortunately, I had forgotten that in my home PC .ctwmrc specified 12
workspaces (6x2) whereas the remote machine, which I don't use so much, specied
10 (5x2).
I had a lot of firefox windows in workspaces 11 and 12, when I killed ctwm
locally. So when the remote ctwm started up, I got this printed out, which at
first mystified me:
unknown workspace : Page 11
unknown workspace : Page 11
unknown workspace : Page 11
unknown workspace : Page 11
unknown workspace : Page 11
unknown workspace : Page 11
unknown workspace : Page 11
unknown workspace : Page 11
unknown workspace : Page 11
unknown workspace : Page 11
unknown workspace : Page 11
unknown workspace : Page 11
unknown workspace : Page 11
unknown workspace : Page 11
unknown workspace : Page 11
unknown workspace : Page 11
unknown workspace : Page 11
unknown workspace : Page 11
unknown workspace : Page 12
unknown workspace : Page 12
unknown workspace : Page 12
unknown workspace : Page 12
unknown workspace : Page 12
unknown workspace : Page 12
unknown workspace : Page 11
unknown workspace : Page 11
unknown workspace : Page 12
unknown workspace : Page 11
But despite that ctwm coped: it simply allocated those windows to
workspace 6, where they are perfectly usable.
So this proves that the current ctwm can be run on a different machine from the
xserver.
My broadband (cable) network connection uses VirginMedia 60Mbps download 3Mbps
upload (alas). The connection to my departmental machine goes from VM to the UK
academic network, to my university, to the department, and eventually the PC.
Anyhow, this proves that CTWM runs remotely on 32 bit CentOS
Linux 2.6.18-371.6.1.el5 #1 SMP Wed Mar 12 20:08:05 EDT 2014 i686 athlon i386
GNU/Linux
One consequence of running ctwm remotely is that using a ctwm menu item or
key-binding to launch an xterm window produces one running on the remote
machine. To launch a new local xterm I have to use an exising xterm window
that was running locally before I started the remote ctwm -- unless I use a
remote xterm to log in to my local machine and then run xterm locally!
Now returning to my normal local use of ctwm and some sanity.
Aaron
