Practical activity

Presentation & objectives

The aim of this activity is to help you discover how your computer works, and what are the main physical elements inside it.

Also, you will learn to manipulate the terminal to navigate in your file system, and run commands.

Activity contents

You may already know the insides of your own computer, nevertheless you might not know how to get them from a Command Line Interface (CLI). In this activity, we will try to map all your system components using only the terminal. We will then verify all the information using the Graphical User Interface.

If you want you can edit a text file on your computer to write down the command lines’ output or use a good old-fashioned pen&paper.

1 — What is your Operating System ?

The first thing you need to know in order to continue this activity is what is your Operating System. For this first question we will not get into the detail, we only need to know the OS family : Linux, Windows or macOS.

2 — Using the command line

The second step is launching the Terminal application of your operating system. This application may differ from one OS to another (hence the first easy question).

3 — Discover your own computer

Now that you have opened the Terminal application of you specific OS we are going to learn a little bit about your computer.

Hardware components

In this exercise we are going to try to retrieve the list of the most important hardware components of your computer. In particular, we are going to learn about the components of the von Neumann architecture that we have introduced during the lecture.

wmic cpu get name

Get-CimInstance -ClassName Win32_Processor

lscpu

system_profiler SPHardwareDataType

• What is your CPU vendor ?
• What is the frequency of your CPU ?
• Optional : Did you get the number of cores available ? (you may have to search for an additional parameters)

wmic memorychip get devicelocator, manufacturer, partnumber, serialnumber, capacity, speed, memorytype, formfactor

Get-CimInstance -ClassName Win32_PhysicalMemory

Get-CimInstance -ClassName Win32_PhysicalMemory | Select-Object devicelocator, manufacturer, partnumber, serialnumber, capacity, speed, memorytype, formfactor

lshw -short -C memory

system-profiler SPMemoryDataType

• How much physical memory do you have on your computer ?
• What is the frequency of the Chip(s) ?

wmic diskdrive get model,serialNumber,size,mediaType

Get-CimInstance -ClassName Win32_DiskDrive

Get-CimInstance -ClassName Win32_DiskDrive | Select-Object model,serialNumber,size,mediaType

lsblk

hdparm -I /dev/sda

system_profiler SPStorageDataType

• How many storage drives are installed in your computer ?
• What is the total size of your drive(s) ?
• Do you have Hard Disk Drive(s) or Solid State Drive(s) ?
• Optional : how many partitions are present and what is a partition ?

wmic Path Win32_PNPEntity get Description,DeviceId

Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match '^USB' }

lsusb

lspci

system_profiler SPUSBDataType

brew install usbutils

• What are the current USB devices connected to your computer if any ?
• Can you get your graphic card information ?

Operating System

In this exercise we are going to learn about the features of your Operating System that we have introduced during the lecture.

ver

Get-ComputerInfo OsName,OsVersion,OsBuildNumber,OsHardwareAbstractionLayer,WindowsVersion

uname -a

uname -a

• What is the specific version of your operating system ?
• Did you manage to get the kernel version ?

tasklist

Get-Process

ps

ps

• Is there a way to make the output more readable ? (think of the more command)
• Are all the processes listed ?

whoami

whoami

whoami

wmic os get TotalVisibleMemorySize,FreePhysicalMemory

Get-CimInstance -Class Win32_OperatingSystem | Select-Object FreePhysicalMemory

chkdsk

Get-CimInstance -Class Win32_LogicalDisk | 
  Select-Object -Property DeviceID, Name, @{ 
    label='FreeSpace' 
    expression={($_.FreeSpace/1GB).ToString('F2')} 
  }

free

df

vm_stat

df

The command line allows you to do many more tasks that we will not cover here. However, you may have noticed that some terminal commands are simpler than the others depending on the operating system, especially the Linux ones. That can be explained by the need to interact with these OSes with a command line more often (to administer a server for example). That is why, even if you are not currently running a Linux machine, we greatly encourage you to learn and practice with Linux commands for the IMT Atlantique computer science curriculum.

4 — Using the graphical interface for validation

Now that we have obtained much of the hardware and operating system information using the CLI we are going to verify all of them using the GUI.

The hardware components

Most of the modern OS have a single point of entry to get all the hardware components of your PC, including its CPU, drives, peripherals …

• Verify that all the previous information you gathered about your computer are the same as the one presented in the GUI.
• Optional: feel free to explore and discover other information about your hardware : your network adapters, graphic card, …

Software components

• Are the running processes the same that you found with the CLI ?
• Launch a simple application (such as a text editor), can you see it in the list of processes ?
• Optional: try to kill this process (be careful to select the previous process and not another one)

5 — Keep your system and applications up to date

As we have seen, your computer is running a lot of different processes either applications that you are using or services that perform various tasks in the background. There is a specific type of applications that we have not covered for the moment which are malicious software.

Malicious software, or malware, are designed to harm, exploit, or otherwise compromise a computer system or network. The primary purposes of malware include stealing sensitive information (e.g., passwords, financial data), disrupting operations (e.g., causing system crashes, deleting files), gaining unauthorized access to systems, and using compromised devices for illegal activities (e.g., sending spam, launching attacks on other systems).

They can come from various sources: applications downloaded from an untrusted sources (think of pirated games), a fraudulent link, or a macro inside a Word document received by mail for example. Here we give a list of some security best practice you should follow in order to keep your computer relatively safe (unfortunately it can never be 100% secured).

To go further

TODO add simple scripts

To go beyond

TODO WSL

• name.

  Short description.