With this podcast I start a little experiment:Can technology be explained by words only?
Let's try this out ...
In this fourth episode of “Get To Know Your Linux-System” we wanna examine the network capabilities of the system you are currently on.
And to be honest - this lesson is a tough one - if you aren’t the guy who configures networks every day.
Therefore I try to keep it as simple as possible …
What will you learn?
- examine the configuration the network-interfaces
- which ports are open?
- … and which processes are listening
- is there a local firewall in place?
In this third step of “Get To Know Your Linux-System”, we wanna examine the diskspace a system uses.
And disk space - this is the number one resource if it comes to unplanned outages.
Let me talk in this lesson about
- how to get insights into the used disk-space
… and as much important like this …
- how to examine where - in which directories and by which files - all the disk space is consumed.
In this second step of “Get To Know Your Linux-System” you will learn more about the CPU- and memory-load of your system.
What you will get
- We will have a look at the processes a system is currently busy with
- You will see, how much memory a system has installed and how it is used
- You will get the insight, if your system, is slowed down because of a memory-overload.
… and incidentally, I will show you, how you can pause a process and reactivate it later on.
If you want to get to know your Linux-system - use as a starting-point the command “with the probably most useful information per keystroke” 🙂
This command gives you a great first impression about the system you’re on.
Additionally you will learn
- about the time of your system and how to find out the timezone it is configured with
- how to find out, if your system is currently overloaded or not
- how to find out, if there are currently other users working on the system.
Here is another question that often comes up by my students and clients:
” … how can I solve the problem with these special-characters? The shell always gets me wrong …”
The fast and simple answer to this is: You have to quote!
… and you have to to it the right way.
But let’s start from the beginning …