Who’s this guy?
Short? — Arch and Gentoo
In more detail? Something like this:
It’s 2026, and I still show up to work convinced that a computer network
can be fixed with a good sense of humour and two metres of RJ-45 cable.
And you know what? It usually works. Accidentally, but it works.
By training I’m an engineer, by profession an academic teacher, and by practice someone who has spent many years trying to convince computers, networks, and users to cooperate with each other just a little more than they’re naturally inclined to.
I was born on Earth, which — as it later turned out — was the first in a series of unexpected life decisions. The second was developing an interest in Linux back when normal people were configuring networks on Amigas or with Windows 3.11, crying in rhythm to floppy disk drives.
I didn’t cry.
I compiled the kernel from scratch.
Voluntarily.
This says something about my character — note for students 😉😉😉
Over the years I earned a Doctor of Habilitation degree in engineering and technical sciences from the AGH University of Science and Technology in Kraków — an institution historically associated with digging things out of the ground, but in practice producing engineers capable of fixing things they didn’t break themselves.
I specialise in detecting traces of cybercrime in networks, building and administering computer networks based on Gentoo and Arch Linux, server architecture, virtualisation, and the broadly understood discipline known as “make it work.”
My approach to technical problems can be described as “calm, systematic, and (for unknown reasons) effective.” Some people treat this as an ability of obscure origin, mainly because most of these things I do using Gentoo and Arch Linux.
I also build and maintain servers, laboratories, network environments, educational platforms, cloud services, and other constructions that work best when no one remembers they exist. That’s the paradox of this field — if I did everything right, most people won’t have the faintest idea that I did anything at all.
Apart from teaching and administering things, I also administer students. They’re harder to configure than servers, but at least they don’t require a restart. Officially, at least 😉.
I’m also the creator of AGHos — my own Linux distribution based on Arch,
built specifically for my student courses.
Because why use a ready-made system when you can build your own?
AGHos configures itself, can boot over the network, and generally behaves
more predictably than most first-year students.
Sometimes even fifth-year ones ;)
So if you landed here looking for someone who knows Linux, computer networks, servers, cybersecurity, or someone who voluntarily compiles things that absolutely don’t need compiling — you’ve come to the right place.
If you’re looking for a reasonable hobby, I’m afraid I can’t help. 😉
If that doesn’t help — call Gołek.
If Gołek can’t help — buy new hardware.”
— The Unwritten Law of the Server Room, WIMiC AGH
Areas of Expertise
Courses Taught
- LSystems Use & Specialist Software — the academic version of “check if your disk is still alive.”
- LabNetwork Laboratory — where cables are patient, and students — only sometimes.
- LabOperating Systems — learning to respect Linux through trial, error, and more trial.
- ProjTeam Project — where students discover that “works on my machine” is not a system architecture.
L = lecture | Lab = laboratory | Proj = project
About This Page (and the Server)
The lab server you’re reading this on provides students with virtual environments for their coursework. Each student has their own QEMU machine, their own resources, and — more importantly — their own space to make mistakes without harming others. It’s a thoughtful architecture. Absolutely nobody appreciates it. At least not until something breaks and it turns out isolation saved the day.