$ command
Command (or generalized form), which should be executed with the rights of a normal user (e.g user)
# command
Command (or generalized form), which should be executed with the rights of the superuser (root). To acquire the superuser permissions, use the following command (the "-" is important!):
  • $ su -
"Fake" TLD (top level domain) for our practicals. Corresponding to the group: ".one", ".two", ".three", ".four", ".five", ".six", ".seven"
The position number in the course list.
For example: position=7, %n=7; position=101, %n=101
Last byte of the system's IP-address. In our case, it's your position in the course list + 16. For example: position=5, %X=21

Frequently Asked Questions

Can I work on labs at home?
Yes, but you need to complete at least one (first) lab instructions on the class machine. It is possible only during the lab session for your group.

How should I submit my work and where are my grades?
You don't need to submit anything. Each time you start you virtual machine in network it will be tested (continuously, automatically). The results of the tests or in other words Your Progress can be found on course test server (available only with p12). We are in a process of implementing automatic tests, check the final state on the test server.

Why can't I access/load the test server?
To access the test server you need to make and integrate a p12 file (details are in the beginning of the lab2) into your browser. The other restriction: you can only access it from university internal network. So you either should be in class or otherwise use a VPN (how to install it at home? see below).

Should I upload my current.vdi back to the FTP after working at home?
We would recommend to avoid that. After the setup on home machine is completed you actually don't need to upload the current.vdi back. We will evaluate your work with our Test Server, and it will test your machine each time (~ once in 2-5 minutes) you will run it in the VPN. It does not matter how you run it (from home machine or from class), you can just come to the class session with your laptop and avoid the upload/download of current.vdi file. But in this case, remember to make backups of the current.vdi on your local machine (for your own safety). However, if you do not have a laptop or because of some other reasons want to work using class machine, then you will need to upload the current.vdi back to the FTP.

Home Machine Configuration Manuals

Lab Schedule:

To monitor your progress:
Testing system web interface (accessible only from class or with VPN to UT, requires p12)

Feb 06 - Feb 12 - Lab 1

  • Introduction & Setting up the environment (VirtualBox, Network, introduction to Bash)

Feb 13 - Feb 19 - Lab 2

  • Logical Volume Management, Linux Logical Volume Manager

Feb 20 - Feb 26 - Lab 3

  • DNS and BIND basics, DNS client settings

Feb 27 - Mar 04 - Lab4

  • Catch-up, no new material.

Mar 05 - Mar 11 - Lab 5

  • Mail: MX record, Postfix, Dovecot, Spamassassin

Mar 12 - Mar 18 - Lab 6

  • CNAME, Apache, MySQL, Web mail, phpmyadmin

Mar 19 - Mar 25 - Lab 7

  • Apache status module and limited access, Apache SSL, SNI

Mar 26 - Apr 1 - Lab 8

  • CMS Install and Maintanance: Drupal

Apr 2 - Apr 8 - Lab 9

  • Catch-up, no new material

Apr 09 - Apr 15 - Lab 10

  • NFS server and client, Samba, Samba SWAT, Quota

Apr 16 - Apr 22 - Lab 11

  • Media Server: MediaTomb, CMS: WordPress

Apr 23 - Apr 29 - Lab12

  • Version Control (SVN)

Apr 30 - May 6 - Lab13 - Catch-Up

  • Time to fix your problems

May 7 - May 13 - Lab14 - Catch-Up

  • Time to fix your problems

May 14 - May 20 - Lab14 - Catch-Up

  • Time to fix your problems
  • DEADLINE at this week end (Sunday evening 23:59 your results on the test server will be locked and test server will be shut down). At this point all the tests on the test server should have "OK" (and have a timestamp of current week) to pass the practical part of the course and to be allowed for the exam (if any).

Useful Links:

To fine tune your Linux CLI skills:

Page edit