To access the cluster remotely, you have to use ssh (it doesn't accept
telnet requests). The domain name is linuxlab.csic.umd.edu
. So it will be something like:
ssh -l <your username> linuxlab.csic.umd.edu
$ setenv PATH /usr/local/bochs-2.0.2/bin:$PATH
If your shell is bash, add them with
$ export PATH=/usr/local/bochs-2.0.2/bin:$PATH
Now you can download and compile the kernel
/usr/local/bochs-2.0.2on the linuxlab cluster. If you are working on one of the workstations in the linuxlab room, just go to your project's build directory and run bochs.
$ bochs
(Make sure you run
it from that directory so that it can find the
.bochsrc file which is given to you, and tells bochs what to
do.)
If you are working remotely, e.g. from your WAM/Glue account, first download the fonts file, and uncompress/untar it in your account. then do:
xset fp+ <the font directory in your account>For example, if you have saved the files in the directory ~/fonts, and your user name in WAM is bob, do
xset fp+ ~bob/fonts
After this, do
xhost +and then you must be able to run bochs from your linuxlab account , and have the output on your WAM/Glue X session.
Note: you have to do these two steps every time you logon to your account. Also, the second step is sort of dangerous, because it enables clients from any host to connect to your X session!
xset fp+ <path>do the following if you're working from a WAM workstation: (Again, these have to be done from your WAM account, and the text in bold must be entered as is.)
xfs -config bochs.xfs -port 7777 &
xset +fp tcp/127.0.0.1:7777
xset fp rehash