Linux Tutorial (Other Tutorial)
Xfce Documentation
This is often not difficult but at your own risk; we cannot give installation support.
To use this option, you have to have a computer with an Intel/AMD x64 processor (NOT: Apple M1, M2, or M3), sufficient main memory (8 GB) and free disk space (32 GB).This is the recommended way for using the course software.
To use this option, you need a reasonably fast Internet connection and either an X2go client or an X11 server installed on your local computer.Use this option only if you cannot use the virtual machine.
VirtualBoxDownload the appropriate VirtualBox binary and start the installation as described (MS Windows: just click on the .msi file).
After the installation, download the virtual machine stored in file
Debian12RISC.ova(about 10 GB large). Then start VirtualBox (MS Windows: menu entry "Programs/Oracle VM VirtualBox/VirtualBox") and import the virtual machine (choose "File->Import appliance", select the downloaded file, potentially adapt the configuration). Then start the virtual machine.
This virtual machine runs a 64-bit operating system for which you need a 64-bit CPU with hardware virtualization support (Intel-VT or AMD-V). While all modern computers (desktops and notebooks) have this support, it is sometimes switched off in the BIOS. If VirtualBox reports an error when starting the virtual machine, please check whether your computer has hardware virtualization support enabled (see here and here and here for more information).
If you run VirtualBox on a Windows host, a "green turtle" may appear among the icons at the bottom of the virtual machine window. This indicates that Microsoft Hyper-V is active, which considerably slows down the execution of VirtualBox. If you want VirtualBox to run at top-speed, you have to deactivate Hyper-V and any security option in Windows or in the BIOS that activates Hyper-V; this includes Windows options named like "Device Guard", "Credential Guard", "System Guard", "Memory Integrity", "Windows Defender's Core Isolation" and BIOS options named like "Secured Core" or "Memory Protection" (see here and here and here for more information).
When you start the virtual machine, a Debian GNU/Linux system with the Xfce desktop environment starts up. You may login as
User: guest(there is also a superuser account "root" with password "root" for software installations/updates; after login as "guest", you may execute "su" to switch to this account). Click on the icon "Terminal" to open a terminal shell from which you can start the course software.
Password: guest
To exchange files between your computer (the "host") and the virtual machine, some directory of your computer has to be mapped to the folder
/home/guest/hostin the home directory of user "guest". For this purpose, shutdown the virtual machine. Select in the "Settings" menu of the VirtualBox manager the "Shared Folders" tab. Press the "Add" button on the right to add a shared folder with name "host" and mount point "host" and the path of an arbitrary directory (which must be writable) on your computer (don't use the root directory C:\); also select the option "Auto-mount". Start the virtual machine again. If you write a file into the directory /home/guest/host of the virtual machine, it should appear in the configured host directory.
Don't use the shared directory for working with the software installed in the virtual machine; there are certain limitations with respect to file names etc. such that the software may not work. Use this directory only for transferring individual files from/to your host computer.
If possible, use the X2go client solution; it provides a much better user experience on low bandwidth networks than the X-Server solution.
x2goclient &and create a new session to host "qftquad1.risc.jku.at" (qftquad1-qftquad4 are available) with session type "XFCE" using your login data. You can then work with an XFCE desktop on the remote machine as if on your local machine. In particular, by selecting "Applications/Terminal Emulator", you can open a terminal window on the remote machine.
Alternatively, if you have just an X-Server running, you can type in a terminal window
ssh -Y -l username qftquad1.risc.jku.at(assuming that your account is named username). You will be asked for a password and can login to the machine "qftquad1" of the RISC environment (qftquad1-qftquad4 are available). The ssh option "-Y" allows you to start programs with GUIs and have them displayed on your computer. After typing
xterm &a terminal window (executed on the RISC machine) should pop up on your computer.
Alternatively, the free Xming software provides an X-Server together with the SSH client PuTTY. To download and install Xming, visit
Xming X Server for WindowsDownload from the section "Public releases" the executables "Xming" and "Xming-fonts" and run both for setup (complete installation, leave the default options, but have a desktop icon created for "XLaunch").
After the installation, start "XLaunch", select "Multiple windows", press "Next", Select "Start a program", press "Next", Select "Run Remote Using PuTTY (plink.exe)" and "With compression", enter "qftquad1.risc.jku.at" (qftquad1-qftquad4 are available), your username and password, press twice "Next" and then "Finish".
Now a terminal window (executed on the RISC machine) should pop up on your computer.
tcsh users (file ".tcshrc", default at RISC)(Please note that a new line must be started after the last configuration line, otherwise the command will have no effect).setenv PATH "$PATH":/zvol/formal/binbash users (file ".bashrc")export set PATH=$PATH:/zvol/formal/bin
This command puts the directory with the RISC installation of the course software into your PATH (all software is installed in directory "/zvol/formal" with the executables in subdirectory "bin"). Now logout and login again (respectively start a new terminal window) and check whether executing the command
jml --versionworks and prints some version information.
For this, enter
ps -fu usernamewhich will show a list of your processes with the corresponding process identifiers (PIDs). If you cannot close the corresponding application by normal means, enter
kill -9 PIDto terminate the process.
To finally logout from the system, logout from the remote Gnome session (if using the X2go client solution) or type
exitin the terminal window (if using the X-server solution).
Never terminate a login session by just closing the X2go window respectively the terminal window.