Skip to main content

Lab 1: Installing Debian 12 with VirtualBox

Lab Preparation

Purpose of Lab 1

In order to save money and resources when learning to install, to manage, and to connect Linux machines to form networks, we will be using Virtual Machines for this course. In fact, we will be using two virtual machine programs:

  • Lab 1: Create a Debian 12 Host virtual machine (called debhost) in the virtual program called VirtualBox. This host will be stored on your Solid State External Drive (SSD).
  • Lab 2: Install a Virtualization program package on your Debian 12 Host virtual machine called KVM which will be used to create 3 remaining Virtual Machines (VMs) that you will use to learn about Linux system administration for the remainder of this course.

The virtualization software will allow you to create and administer 4 different virtual machines (VMs) on your computer system. labenv.png

It is ESSENTIAL to have a Solid State Drive (SSD) with a minimum storage capacity of 240 GB or 240 GB available on your own computer for you to perform the lab work and provide storage for your Debian 12 host and other VMs that you will create in Lab 2. Due to space requirements, you are NOT permitted to share this SSD drive with any other course material than our OPS245 course.

NOTE: It is feasible to use a notebook computer with sufficient hard disk capacity to perform these labs (as you would for an SSD drive). It would require that your notebook computer can connect to the Internet (including in Seneca's computer labs). You would be required to follow the same instructions for this lab (SSD).

Main Objectives

  • Correctly install the Debian 12 host VM (debhost) on your SSD using VirtualBox.
  • Note common Linux commands and record them in your lab logbook.
  • Use scripts to generate a post-install report for your Debian 12 host VM.
  • Disable Linux Kernel security enhancements to allow for more experimentation.

Minimum Required Materials

  1. Solid State Drive Minimum Size: 240GB
  2. Lab Logbook (Click Here to Download)

Linux Command Reference

Package Management

System Information

Networking

Miscellaneous

grepwcpwdlsmorefilewgetchmodvi

Matrix on-line tutorials

  • Linux Basics: /home/ops235/linux-basics
  • Using the vi Text Editor: /home/ops235/vi-tutorial
  • Shell Scripting - Part I (Scripting Basics): /home/ops235/scripting-1

Investigation 1: Create And Install Your First Virtual Machine (debhost)

In this lab, you will learn how to install your Debian 12 VM using the VirtualBox application.

Part 1: Using VirtualBox to Create a New Virtual Machine (VM)

debhost VM Details:

  • Name: debhost

  • Boot media / Installation: Debian 12 Net Installer install DVD (image file)

  • Disk space: 238GB

  • CPUs: 1 CPU, 4 cores (Do not mix and match! Always use 1 CPU, and multiples of 2 for cores.)

CautionIf you are using an external SSD drive on a Seneca Lab Computer you must FORMAT it AS exFAT.

By default, most external drives will be formatted for NTFS. NTFS-formatted drives may cause issues in this course if you are constantly moving between different Seneca Lab computers. When you plug your drive in, open My Computer, right-click on the new drive, and select Format.... If you are storing the vmdk file (VirtualBox disk image) on your own devices internal storage, this is not necessary.

Format exFAT

Confirm External SSD Device is Recognized as a Drive in Windows Explorer

It is essential that your Windows machine recognizes your SSD device with a drive letter on your Windows machine. Open up file explorer in Windows and examine the properties of your SSD Device. (Make note of its drive letter and path)

CautionEnabling Virtualisation on your Home Computer:

If you are going to complete the labs on your own laptop, or desktop computer at home, there are a few things you need to be aware of:

  • RAM Size considerations: Your Seneca Lab Workstations have 16GB of RAM. Your own computer should have also have at least that much RAM in order to function efficiently.
  • Enable Virtualisation in home computer's BIOS: Many home computers do not have Virtualisation enabled in their computer's BIOS. In your machines BIOS/UEFI: Enable the options VT-X(required) and VT-D(only if available)

The Debian Web Site

Open up https://www.debian.org/ in your browser. To get the latest copy of the Debian 12 netinstaller ISO click on the "Download" button. While you are on the site lets explore...

One of the most important skills you should graduate with is the ability to teach yourself something new. You will not always have the luxury of attending a training course to learn something new, so we must be prepared to learn independently. This often means reading official documentation. Official documentation is also one of the primary sources of information you should use when troubleshooting or configuring a system. Along with user forums and wiki's. Google searches can often produce results that are not specific to your Linux distribution or version, so they can produce inaccurate results.

Reading documentation, like any skill, requires practice. Reading man pages for example is often very confusing for new users as it hard to understand all of the terminology. However, the more time you spend reading the documentation the easier it will become.

Click on the "User Support" link. Take a look at some of the support options available. Find the links to the documentation and forums. Take a look around. Bookmark the page. (The Debian website is well known for being difficult to navigate.)

Creating the VM in VirtualBox

Before you can install your Debian Linux OS, you must first create a storage container which is a virtual machine (VM) using VirtualBox on your host computer.

If you will be completing the course work on your own computer then you should download and install VirtualBox from the VirtualBox Website If you will be completing the course work on Seneca Lab computers you will need to run VirtualBox from "MyApps"

Caution > Possible VirtualBox Installation Problem:

if you receive a warning that VirtualBox has missing dependencies for Python Core / win32api cancel the installation and follow these instructions before trying to install again.

Perform the Following Steps:

  1. Power up the computer in your Seneca lab in Windows. (or your own device)

  2. If you haven't already downloaded the Debian 12 netinstaller DVD ISO, then do so now.

  3. If you are using an external SSD drive, connect it to the computer and note the drive letter for that device.

  4. If you will be working on Seneca Lab computers, format your SSD to use exFAT, not NTFS. Open My Computer, right-click on the SSD, and select Format.... The dialog box should have the exFAT option selected. Once selected, click Start.

  5. Create a folder called: Virtual Machines on your SSD device or internal storage device. The storage device should have 240GB of usable space.

  6. Launch VirtualBox.

  7. Click the File menu, then select Preferences.

  8. Under the General tab, set the Default Machine Folder: to the correct location for Virtual Machines, enter the pathname for the newly created folder in your SSD or internal device, and click OK. VirtualBox Prefs

  9. Click on the "New" icon to create a new VM. We will just be creating a "shell" for the VM to contain our Debian 12 Linux operating system. This will allow us to configure the VM properly so it will boot-up properly in our Seneca labs.

      - Name: debhost
    - Folder: Check the location
    - ISO image: Browse to the downloaded ISO file
    - Type: Linux
    - Version: Debian (64 bit)
    - Check the box to "Skip unattended Installation"
    - Click "Next"

NOTE: Since this “virtual machine” will be supporting other virtual machines (i.e. nested VMs), it is necessary to give this host VM a higher amount of Memory, and number of processors cores. You can always change these settings later on to maximize the performance of running the “nested” VMs on your Host VM.

  1. Assign the VM 8GB of memory. (8192 MB)
  2. Assign 4 CPU's and select the box for ":Enable EFI"
  3. Click "Next"
  4. Choose "Create a virtual hard disk now"
  5. Set the size of the virtual hard disk to 240GB
  6. Click "Next"
  7. Review the settings and Click "Finish"

Before starting the VM we need to adjust a couple of settings

  1. Click on the "Settings" icon
  2. Click on the "System" tab
  3. Under "Motherboard" check "Enable EFI"
  4. Under "Processor" give your VM 4 Processors
  5. Enable Nested VT-x/AMD-v
  6. Click on the "Display" tab
  7. Increase the "Video Memory" to 128MB
  8. Click "OK"

Boot the VM and begin the installation of Debian

  1. Click on the "Start" icon
  2. When the Installer Boot Screen appears, Select "Advanced options..."
  3. Select "Expert install"

CautionPossible installer problem:

If the installer starts but it does not correctly display in the window, either with a black or grey screen...

  • Close and restart the VM
  • When the Installer Boot Screen appears, Select "Advanced Options"
  • Highlight but don't hit enter on the "Expert install" option
  • Type 'e' to edit the boot options
  • Add the boot parameter fb=false to the linux line as shown below
  • Type ctrl-x to boot grup fb option
  1. Select "Choose Language"

  2. Set your language to English and your location/locale to Canada

  3. Select "Continue" to skip additional locales

  4. Select "Configure the keyboard" and choose "American English"

  5. Select "Detect and mount installation media" and "Continue"

  6. Select "Load installer components from installation media" and "Continue"

  7. Select "Detect network hardware"

  8. Select "Configure the network" and "Yes" to Auto-configure the network

  9. Set the Hostname to be "debhost"

  10. Leave the Domain name: as blank

  11. Select "Set up users and passwords"

    The installation of Debian 12 provides 2 methods of achieving administrative access to the system.

    • If you enable the "root" account and provide it with a password then to get admin access you need to login as root or use the su command to switch to root. No other accounts will have admin access.
    • If you leave the "root" account disabled then the first regular account that you create will be able to access administrative privileges by using the sudo command. Generally the 2nd option is considered to be better, especially in environments where multiple users may need admin access to the system. You can always enable root account access after installation if you want both options available.

    Caution > WARNING: Do not login to a Graphical User Interface as the "root" account. Most Linux distributions prevent this.

  12. Choose "No" to prevent "root" from being enabled

  13. Enter your full name for the initial user account and then "Continue"

  14. Set your Username. At this point you can edit the username to be the same as your Seneca account name to make it easier to remember. (not required)

    As we progress through the course and create our other VM's we are going to use the same username with the same password on all of our VM's. This is a requirement for running the Lab Check scripts.

  15. Set a password for your account. You will need to enter it twice.

    Caution"P@ssw0rd" is NOT a secure password!

  16. Select "Configure the clock" and "Yes" to use NTP to set the clock and "Continue" to accept the NTP server.

  17. Select the "Eastern" time zone:

  18. Select "Detect disks"

  19. Select "Partition disks" and choose the "Manual" partitioning method.

CautionIt is very important that you setup disk partitioning correctly. A mistake at this point in the lab could cause problems in future labs.

  1. Select the "SCSI1" device which is the virtual disk for this VM.
  2. Choose "Yes" to create a new empty partition table on the device.
  3. Choose a "gpt" partition table
  4. Choose the "Free Space"
  5. Choose "Create a new partition"
  6. Enter a size of 500 MB and locate the partition at the beginning of the device
  7. Change the "Use as: " to "EFI System Partition" and leave the "Bootable flag: on"
  8. Choose the "Free Space"
  9. Choose "Create a new partition"
  10. Enter a size of 500 MB and locate the partition at the beginning
  11. Change the "Mount Point" to /boot and leave the remaining defaults
  12. Choose the "Free Space"
  13. Choose "Create a new partition"
  14. Enter a size of 190 GB and locate the partition at the beginning
  15. Change the "Use as: " to "physical volume for LVM" and leave the remaining defaults
  16. Choose the "Free Space"
  17. Choose "Create a new partition"
  18. Enter a size of 16 GB and locate the partition at the beginning
  19. Change the "Use as: " to "swap area" and leave the remaining defaults

The remaining storage will be configured using "Logical Volume Management (LVM)"

  1. Choose "Configure the Logical Volume Manager"
  2. Compare your settings with the image below, make sure they are correct and choose "yes" to write those changes to disk debgpt
  3. Choose "Create volume group" and set Volume group name to "vg_debhost"
  4. Select "/dev/sda3" as the new device for the volume group and then continue
  5. Choose "Create logical volume"
  6. Select "vg_debhost" for the "Volume Group"
  7. Set the Logical volume name to "lv_root"
  8. Set the Logical volume size to "30G"
  9. Choose "Create logical volume"
  10. Select "vg_debhost" for the "Volume Group"
  11. Set the Logical volume name to "lv_home"
  12. Set the Logical volume size to "40G"
  13. Choose "Create logical volume"
  14. Select "vg_debhost" for the "Volume Group"
  15. Set the Logical volume name to "lv_images"
  16. Set the Logical volume size to "100G"
  17. Choose "Finish"
  18. Choose the lv_home device deblvm1
  19. Change the "Use as: " to "Ext4 journalling filesystem"
  20. Change the "Mount point:" to "/home" and leave the remaining defaults
  21. Choose the lv_images device
  22. Change the "Use as: " to "Ext4 journalling filesystem"
  23. Change the "Mount point:" to a manual entry of "/var/lib/libvirt/images" and leave the remaining defaults
  24. Choose the lv_root device
  25. Change the "Use as: " to "Ext4 journalling filesystem"
  26. Change the "Mount point:" to "/" and leave the remaining defaults

Carefully review your partition settings before choosing "Finish partitioning and write changes to disk" Choose "Yes" to write the changes to disk debgptlvm

  1. Choose "Install the base system"
  2. Select the default kernel suggested
  3. Select "generic" drivers
  4. Choose "Configure the package manager"
  5. Choose "No" to "Scan extra installation media"
  6. Choose "Yes" to "Use a network mirror"
  7. Select "http"
  8. Select "Canada"
  9. Accept the default archive mirror or the uwaterloo.ca mirror
  10. Leave HTTP Proxy blank
  11. Choose "Yes" to "Use non-free firmware"
  12. Choose "No" to "Use non-free software"
  13. Choose "No" to "Use contrib software"
  14. Choose "No" to "Enable source repositories in APT"
  15. Leave the default "Services to use:" selections
  16. Select "Select and install software"
  17. Choose "no automatic updates" (We will update manually)
  18. Choose "no" to the package usage survey
  19. On the Software Selection screen make sure that the Debian Desktop Environment and Gnome are selected and add the "SSH Server" to the default selections tasksel
  20. Select "Install the GRUB boot loader"
  21. Choose "No" to "Force GRUB installation to the EFI removable media path"
  22. Choose "Yes" to "Update NVRAM variables"
  23. Choose "No" to "Run os-prober automatically"
  24. Select "Finish the installation"
  25. Choose "Yes" to "Is the system clock set to UTC"
  26. Choose "Continue" to reboot

When the system reboots you will be presented a graphical login screen login and enter your password

Then you will be presented with the "Welcome" application

  • "Next" for English
  • "Next" keyboard layout
  • Turn off Location services and then "Next"
  • "Skip" connecting your online accounts
  • Click "Start Using Debian GNU/Linux"

Investigation 2: Common Post-Installation Tasks

Fix Display Resolution

VirtualBox display your VM in 3 modes.

  • Windowed mode (default)
  • Full Screen Mode (Toggle with right-ctrl F)
  • Scaled mode (Toggle with right-ctrl S)

It is recommended to run VirtualBox in full screen mode. You can press right-ctrl F to toggle between windowed and full screen mode. It is recommended that you stay in full screen mode for the duration of your lab work. You should use Firefox within the VM to access the various websites for this course.

Switch to Full Screen Mode

Click on the icons in the top right corner and then the settings icon settings settings2 Then choose the "Displays" option

Choose a display resolution that looks better. Start with 1920x1440 and then experiment with different resolutions until you find your preference.

Enable the root account

During the installation process, we left the "root" account disabled. Lets now enable that account. All that is required is to set a password for the "root" account.

  • Click on "Activities" or press the "Windows Key" to search for applications.
  • Search for "terminal", right click on the terminal application and select "pin to dash"
  • Open the terminal application to gain access to the bash shell.

To change the root password we need to use elevated or administrative permissions.

Our account has been given "sudo" access which means we can run a command with root permissions simply by preceding the command with sudo

  • Type sudo passwd to run the passwd command as root. Then enter roots new password twice. (You will be required to enter your password to "unlock" sudo)

To test the account we can use the su command. su is short for "switch user" and we can use it to start a new bash shell as another user. (Default: root)

  • Type su -, you will be prompted for the root account password.
  • Type whoami to confirm the switch and then exit to return to the previous shell.
  • Type whoami
  • Type sudo whoami, We now see there are two methods of accessing root permissions:
    • Using the sudo command at the beginning of our command line to run it as root. We are prompted for our own password to unlock sudo
    • Using the su command to start a new shell as root. We are prompted for the root account password.

We will use sudo to temporarily gain root privileges in order to run a command, but still be our normal user. This method of obtaining elevated privileges has several advantages over logging in as root:

  • First, it only requires each administrator to know their own password.
  • Second, we can control exactly which commands a user is allowed to run as root (We will learn how to do this later in the course), instead of giving them access to everything.
  • Third, the system will log any command that is run using sudo, so that it can be audited later in case something goes awry.

Because it is configurable to a fine degree, and because it provides for better security logging/accountability for System Admins, the preferred method of accessing root permissions is sudo . There are some circumstances where using the actual root account may be required.

CautionKeep the root password and your regular user account password the same on all of the VM's that you create in the labs.

In order to simplify running the lab checking scripts in future labs, using the same root password for ALL machines (debhost and virtual machines). Also use the same regular username and passwords for all of your machines (debhost and virtual machines).

Do not do this in a production environment!

Changing Locked Screen-saver Power Settings

Your system automatically enables a screen-saver application which is a useful security tool to prevent unauthorized viewing of information on a terminal after a certain amount of inactivity. Turning-off the locked screen-saver for this course however is more useful.

To Disable the Locked Screen-saver, Perform the following steps:

  • Click on the power button at the top right-hand corner of the window.
  • Click the Settings icon
  • Click on Privacy
  • Click on Screen and set "Blank Screen Delay" to Never
  • Turn off "Automatic Screen Lock"

Test your internet connection

  • Open "Firefox" in debhost and test your Internet connection.
  • Add Firefox bookmarks for the course web page and schedule.
  • Add bookmarks for Blackboard and Outlook as well.

Perform a system update

The primary source of software and programs that we can install in Debian is the online "repositories".

These repositories are online databases of different available software organized into "Packages".

The repositories and packages are maintained by Debian and they are maintained separately for each release. We should check for updated packages frequently (at the beginning of each lab) as they often contain security updates and bug fixes.

To interact with the repositories and manage our software packages, we will use the apt command.

apt is the command line package management tool used by Debian and many other distributions of Linux.

To check for and install updated packages we need to use 2 separate apt commands:

  • apt update will update the local copy of the repository database
  • apt upgrade will check the database for packages that need to be updated, download them and install them along with any required dependencies.
  • To make changes to the software on the system requires root privileges, so we will need to add sudo to the beginning of the command. We can also run both commands on a single command line.
  • Type sudo apt update && sudo apt upgrade

Using && as a separator between the 2 commands will cause the 2nd command to execute only if the first command is successful.

cautionIf the update results in an updated Linux Kernel then you will want to restart the system

Safe Shutdown and Restart, and safely removing the external SSD

cautionIt is ABSOLUTELY ESSENTIAL that you do NOT remove your SSD drive during your Debian 12 session.

You are required to correctly shutdown your Debian 12 host virtual machine as you would with any operating system.

Also, you are required to use the "Safely Remove Hardware"" and "Eject Media" tool in the system tray on your Windows machine to properly disconnect your SSD device.

FAILURE TO DO THIS MAY DAMAGE YOUR HOST VM AND NOW ALLOW IT TO BOOT PROPERLY (YOU HAVE BEEN WARNED).

  • Click on the power icon in the top right corner of the display and then click on the power icon again
  • Click on Restart or Shutdown

What was installed?

An installation log file called /var/log/installer/status has been created to record the installation of your debhost machine. This file is an ASCII text file which can be viewed with the less command.

  • Type the command less /var/log/installer/status and browse the list of packages installed
  • Type the command man apt
  • Read the man page for the apt utility and figure out a command to list only the installed packages.
  • How many packages were installed?

Customizing your desktop/shell

  • Explore the Appearance tab in the Settings app to personalize your desktop.
  • Search for an App called "Tweaks" and use it to customize your Gnome Desktop
  • Read and edit your ~/.bashrc file and add an alias called update that will run the command line sudo apt update && sudo apt upgrade
  • Both nano and vi are installed by default. You could/should also install vim
    • Type sudo apt install vim

Turning off AppArmor

cautionNever disable AppArmor in the real world!!

It is highly discouraged and unsafe to disable AppArmor on a public-facing server. AppArmor is a Mandatory Access Control framework. When enabled, AppArmor confines programs according to a set of rules that specify what files a given program can access. This goes beyond the traditional protection of file system permissions and helps protect the system against both known and unknown vulnerabilities.

Some of the tasks we will be doing may require additional and tedious steps to configure AppArmor to not prevent our changes. So for the purposes of this course we will disable AppArmor. It is quite safe to do so because we are operating in a VM so our host is not visible to the public Internet.

  • Run the following commands to disable AppArmor:
    • sudo systemctl stop apparmor
    • sudo systemctl disable apparmor
  • We will learn more about these commands later

Investigation 3: Using Shell Commands to Generate System Information

It is very common for system administrators to keep records regarding their installed computer systems. For example, it is necessary to have a record of all the hardware information for each machine in order to help fix computer hardware problems, and to assist when purchasing additional consistent computer hardware.

Therefore, it makes sense to also have a record of the installed software and important system configurations as well. This can contain information regarding the Linux operating system, installed software, and network connectivity information.

Perform the Following Steps:

  1. Refer to the table below for common system information utilities and explanations for each.
  2. Run each of these commands, taking the time to understand what each command's output means.
  3. Record the output from these commands (except for the ps -ef output) in your lab logbook.

The Bash Shell Reference Guide is available to refresh your memory of last semester's ULI101.

Linux/Unix System Information Utilities

Command(s)Purpose
uname -rv, hostname, ps -efBasic Linux OS information such as kernel version, host-name of Linux server, and all processes that are running on the system after installation.
ip address show, ip route show, nslookup (at prompt, enter command: server)Obtain network connectivity confirmation including: IP ADDRESS, Netmask, routing (default gateway), and the default Domain Name Server.
date +'%A %B %d, %Y (%I:%M %p)'Get the current date and time according to the system. (If the date or time do not match your timezone, fix this in system settings for debhost!)
  1. Note that when you are done, you should have recorded the following information in your Lab Logbook:

    • Current Date (according to debhost)
    • Hostname (ie. debhost)
    • Kernel version
    • IPv4 address
    • Subnet mask
    • Broadcast address
    • Default gateway address
    • DNS address
  2. Review what you just wrote in your Lab Logbook. You should be able to understand them because you just put that content there, but what would this look like if you look at it several months from now? Make sure it's clear to future-you!

Answer Investigation 3 observations (all parts and questions) in your lab log book.

Investigation 4: Using BASH Scripting to Generate System Information Reports

You may have learned about creating and running Bash Shell Scripts in your ULI101 course. Shell scripts help Linux users and system administrators to automate repetitive tasks to become more efficient and to help them save time. We can take what we have learned from the commands above and put them into a bash script to generate information reports for your newly-installed Linux host machine.

  1. Create a new file in your ~/bin directory called myreport.bash
  2. Populate the beginning of the file with sh-bang line and block comment describing what this script does:
#!/usr/bin/bash
# Author: *** INSERT YOUR NAME ***
# Date: *** CURRENT DATE ***

# Purpose: Creates system info report
# USAGE: ./myreport.bash
  1. Add a line that will print out the heading System Report
echo 'System Report'
  1. Save your script and run it. Does it work?
  2. You'll notice that the script is currently sending its output to your terminal (STDOUT). We can just use output redirection on the command line when you run the script to send the output to ~/bin/sysreport.txt.
  3. Open your script in a text editor (like vim) again, and add the following lines below the echo statement:
# Print a heading for the date command output
date=$(date +'%A %B %d, %Y (%I:%M %p)')
echo "Report Date: $date"
  1. Save your script and run it again. Observe the output?

  2. Based on the previous investigation and output, add the extra commands for your script to also output (with appropriate headings):

    • The hostname of the machine.
    • The kernel version.
    • The IP address
    • The list of all installed packages.
  3. Run your script to make sure it works. Note that the output does not need to match investigation 3 exactly, but it should be very close.

  4. What other commands and information could we document? Perhaps a list of storage devices, partitions and mount points?

Lab 1 Sign-Off

Follow your Professors submission instructions for lab 1 on Blackboard.

Shell scripting is so essential for Linux administration that this course has created a shell script for every lab for this course that a student must download and run in order to check their work.

If you have performed the lab correctly, then you will get a series of OK messages and you can proceed with the SIGN-OFF for lab1.

On the other hand, if there were errors, then a WARNING message will appear with general suggestions that you will need to fix on your debhost VM in order to have your professor sign-off on this lab. Your lab should be correct before moving to Lab 2.

Perform the Following Steps:

  1. Make certain that your debhost VM is running, open the Bash Shell terminal.
  2. Change to the ~/bin directory.
  3. Download the checking script by issuing the following Linux command:
wget https://raw.githubusercontent.com/OPS245/debian-labs/main/lab1-check.bash
  1. Give that downloaded shell script file execute permissions (for the file owner).
  2. Run the shell script using sudo and if there are any warnings, make fixes and re-run shell script until you receive a "congratulations" message.
  3. Arrange evidence (command output) for each of these items on your screen:
  • Run the lab1-check.bash script (must have all OK messages, and the congratulations message)
  • Proof of anything else your Professor asks to see.

Practice For Quizzes, Tests, Midterm & Final Exam

  1. Define the term Virtual Machine.
  2. List the major screens (steps) in the installation of Debian 12.
  3. What key-combination is used to toggle the view of your running VM from "window-mode" to "full-screen-mode"?
  4. List the steps for updating the Debian software.
  5. What is the home directory for the user "root"?
  6. How do you determine the host name of your GNU/Linux workstation?
  7. What command can display the NIC MAC address?
  8. What command is used to get a list of running processes on your newly-installed system?
  9. Write the Linux command to download the on-line file: http://linux.server.org/package.tar.gz