end of day one

This commit is contained in:
waldek 2022-02-18 14:25:50 +01:00
parent 599c418d97
commit 3cd63a682c
1 changed files with 30 additions and 1 deletions

View File

@ -157,16 +157,31 @@ waldek@hellodebian:~$
![htop](../assets/VirtualBox_debian_18_02_2022_13_18_25.png) ![htop](../assets/VirtualBox_debian_18_02_2022_13_18_25.png)
![htop](../assets/VirtualBox_debian_18_02_2022_13_18_51.png) ![htop](../assets/VirtualBox_debian_18_02_2022_13_18_51.png)
The *menu bar* at the bottom shows you can press **F10** to quit.
This does not work because of a shortcut of gnome-terminal!
You can deactivate this shortcut in the preferences though.
But pressing **q** also exits the program.
![htop bug with gnome-terminal](../assets/VirtualBox_debian_18_02_2022_13_19_35.png) ![htop bug with gnome-terminal](../assets/VirtualBox_debian_18_02_2022_13_19_35.png)
### Adding a secondary desktop environment ### Adding a secondary desktop environment
During the initial installation we where offered a choice of desktop environments to install.
This menu was an actual program called `tasksel` we can run again to add different ones!
As it's a program that can heavily modify the system, we need administrator privileges.
```bash
waldek@hellodebian:~$ sudo tasksel
[sudo] password for waldek:
```
![tasksel](../assets/VirtualBox_debian_18_02_2022_13_21_33.png) ![tasksel](../assets/VirtualBox_debian_18_02_2022_13_21_33.png)
![tasksel](../assets/VirtualBox_debian_18_02_2022_13_22_33.png) ![tasksel](../assets/VirtualBox_debian_18_02_2022_13_22_33.png)
![tasksel](../assets/VirtualBox_debian_18_02_2022_13_22_47.png) ![tasksel](../assets/VirtualBox_debian_18_02_2022_13_22_47.png)
![tasksel](../assets/VirtualBox_debian_18_02_2022_13_23_57.png) ![tasksel](../assets/VirtualBox_debian_18_02_2022_13_23_57.png)
### Changing the runlevel ## Changing the runlevel
The **first** process started by the kernel can be discover by `htop` and is `/usr/sbin/init`. The **first** process started by the kernel can be discover by `htop` and is `/usr/sbin/init`.
This is rather vague but we can find out a *bit* more about this program via `ls` which we'll get into more detail later. This is rather vague but we can find out a *bit* more about this program via `ls` which we'll get into more detail later.
@ -206,9 +221,17 @@ Created symlink /etc/systemd/system/default.target → /lib/systemd/system/multi
waldek@hellodebian:~$ sudo reboot now waldek@hellodebian:~$ sudo reboot now
``` ```
After the reboot you'll be confronted with the following screen.
Don't stress, your machine is not broken!
It's just running in a more *minimal* mode.
You can log in just as with the graphical login window but you'll only have a command line to interact with the machine.
A quick look at `htop` tells us not a lot of stuff is running, just the bare minimum.
![minimal runlevel](../assets/VirtualBox_debian_18_02_2022_13_40_00.png) ![minimal runlevel](../assets/VirtualBox_debian_18_02_2022_13_40_00.png)
![minimal runlevel](../assets/VirtualBox_debian_18_02_2022_13_40_11.png) ![minimal runlevel](../assets/VirtualBox_debian_18_02_2022_13_40_11.png)
To *undo* this change and regain the graphical interface again you can run the following commands.
```bash ```bash
waldek@hellodebian:~$ sudo systemctl set-default graphical.target waldek@hellodebian:~$ sudo systemctl set-default graphical.target
[sudo] password for waldek: [sudo] password for waldek:
@ -217,4 +240,10 @@ Created symlink /etc/systemd/system/default.target → /lib/systemd/system/graph
waldek@hellodebian:~$ sudo reboot now waldek@hellodebian:~$ sudo reboot now
``` ```
## Exercise
Please create a second virtual machine and install a **minimal** Debian.
Minimal means **no graphical environment**.
I advise you to **not** set a root password.
Once this machine is up and running, install a few programs.
The only one we saw up until now is `htop` but maybe try out `bmon`, `elinks` and/or `ranger`.