LWP and UWP
There are a number of important details about these systems that you should be aware of.
- The home directory of the LWP is NOT the same as that of the UWP.
Data has to be explicitly transferred between the systems, which is a bit inconvient.
However, the X-drive that you know from the UWP is available at /mnt/<account-name>
So you could use that to communicate between Linux and Windows.
- Local disk space on our servers
Apart from your home directory on the LWP, which is maintained by the CIT, there also is
a local disk on our fwn-servers. Use it if you use the file system intensively.
Local disk is usually faster than the networked disk of the home directory.
The local disk space resides at /local.
We will create a subdirectory there for you if you want to use it, just ask.
But realize that no backup will be made for this local disk.
If you really need a backup, you can copy the files to you home directory, on Linux or Windows.
Also be aware to not completely fill the local disk.
You can check the usage of all disks with the command 'df', and check usage of a particular directory with 'du -s directory'.
- Administration on the LWP
You can get administration rights on an LWP, it works with a mechanism call sudo and you have to ask the CIT to give it to you.
Note that you do not have these rights on our 4 server machines.
A virtual version of the UWP can also be accessed via a webpage using http://uwp.rug.nl.
This currently is the most convenient way to access a UWP from Linux or Mac.
With Windows or the Mac there is only one user interface, but in Linux there are many to choose from, both graphical and command line oriented.
When behind a computer that runs Linux you usually use a graphical interface.
On the login-screen you can select the user interface you want to use, with names such as XFCE, Gnome, Openbox, Unity or KDE.
When you start a terminal program, usually called "Terminal" or "Konsole", you can use the command line interface.
You actually are interacting with a program usually called "the shell".
The shell program that we use is called "bash", short for "Bourne again shell".
Using the command line interface
A command consists of one or more words, where the first is the actual command and the rest are its parameters.
Parameters beginning with a hyphen (-) are called options.
Here a few important commands, with some options, with a short description.
There is of course much to much to explain here.
See the manual page of bash or the Internet for more documentation.
List file in the current working directory. Initially you are in your home directory: /home/your-account-name
- ls -l mydir
List file(s in directory) mydir with time, permission and size information.
- cd /tmp
Change working directory to /tmp. Returns to you home directory when used without a parameter.
Print Working Directory, shows the current working directory.
- man ls
Online manual, called manual page, for the command ls (as an example). Be sure to always shorty look at the manual page of each command the first time you use it.
- echo Your home directory is $HOME
Type all the parameters of echo to the screen. $HOME is a so called environment variable and contains the value of your home directory.
Shows all environment variables. Especially note the variable PATH that shows the list of directories that are searched for commands when you are issuing one.
- more myfile
Type the contents of file myfile to the screen. Only works for textfiles.
- nano myfile
Start the simple tekst editor called nano to edit the file myfile. This editor is simple but always available also when you have no graphical user interface. Usually when you have a GUI, you maybe use gedit.
- sh myfile
Execute the text file myfile as a program, usually called a (shell) script.
- ssh email@example.com
Login to the machine fwn03.housing.rug.nl using p123456 as the account name, using the Secure SHell.
Last modified: Thu Jan 8 15:51:00 CET 2015