Hvad hvis fjernarbejde kunne være lige så sikkert som med bigtech – uden at betale bigtech?

Mens andre virksomheder låser sig fast i dyre, lukkede platforme (Entra, Zscaler, Cisco, Citrix …), findes der en anden vej: en komplet, gennemtestet arkitektur bygget på 100 % open source – med SUSE Linux som fundament og moderne zero trust-principper som sikkerhedsmotor.

I denne referencearkitektur viser jeg, hvordan I kan:

• 🔐 Erstatte VPN-boksen med WireGuard-mesh – kryptering og portscans simpelthen afvist
• 🪪 Fjerne phishing-truslen med FIDO2-nøgler, TOTP og Keycloak-SSO
• 💻 Få Styr på hver eneste bærbar automatisk med Salt og Uyuni – ingen patch, ingen adgang
• 🇪🇺 Opnå digital suverænitet – kontrol over al trafik og ingen trafik, data eller logs i udenlandske skyer

Alt sammen med kode, I selv kan læse, ændre og eje. Ingen vendor lock-in. Ingen per-seat-regninger. Ingen lukkede døre.

👉 Læs hele arkitekturen, diagrammet og implementeringsplanen: *Sikker fjernadgang med åben kildekode – en SUSE-baseret referencearkitektur *

Sikkerhed handler ikke om, hvem der har bygget låsen, men om hvem der har nøglen. Den skal være din !

Systemd på openSUSE Linux – Komplet Guide

Baséret på videoen "The Linux Lighthouse" – en guide til systemd på openSUSE Linux, fra grundlæggende kommandoer til avanceret tilpasning.

Hvad er systemd?

Systemd er Linux' system- og service-manager, som initialiserer og administrerer systemprocesser, efter kernen er indlæst. Den erstatter det gamle SysV-init-system. Systemd er kendt for paralleliseret opstart og on-demand-aktivering af dæmoner, hvilket gør den hurtigere og mere effektiv.

Systemd's vigtigste funktioner:

• Paralleliseret opstart af tjenester
• Socket- og D-Bus-aktivering for on-demand-tjenester
• cgroup-baseret proces-sporing
• Oprettelse af snapshots og systemgendannelse
• Fleksibel afhængighedsstyring

Tjenestestyring med systemctl

Det primære værktøj til at administrere systemd er systemctl. Her er de grundlæggende kommandoer, du får brug for hele tiden (eksemplerne bruger sshd – SSH-tjenesten til sikker fjernlogin).

Oversigt over aktive enheder

systemctl list-units

Viser alle aktuelt aktive enheder med deres status og beskrivelser.

Start og stop af en tjeneste

# Start en tjeneste
sudo systemctl start sshd

# Stop en tjeneste
sudo systemctl stop sshd

Tjek status

systemctl status sshd

Giver detaljeret information om tjenestens aktuelle tilstand, inklusive fejl.

Genstart og genindlæs

# Genstart en tjeneste
sudo systemctl restart sshd

# Genindlæs konfiguration uden afbrydelse
sudo systemctl reload sshd

Start automatisk ved boot (enable/disable)

# Start automatisk ved boot
sudo systemctl enable sshd

# Undgå start ved boot
sudo systemctl disable sshd

# Tjek om tjenesten er enabled
systemctl is-enabled sshd

Targets

I systemd erstatter targets det gamle runlevel-koncept med mere fleksible opstartssekvenser.

Vis og sæt default target

# Vis nuværende default target
systemctl get-default

# Sæt nyt default target (kræver sudo)
sudo systemctl set-default graphical.target   # eller multi-user.target / rescue.target

Efter en reboot starter systemet i det target, du lige har sat.

Skift target med det samme

sudo systemctl isolate multi-user.target

Skifter straks systemet til det valgte target (f.eks. multi-user eller rescue).

Enheder (units) og egne unit-filer

Systemd-enheder defineres af unit-filer, som ligger i:

• /usr/lib/systemd/system – standard-enheder
• /etc/systemd/system – egne/tilpassede konfigurationer

Sådan opretter du en tilpasset unit-fil (eksempel med sshd.service):

# 1. Kopiér en standard-unit-fil til /etc/systemd/system
sudo cp /usr/lib/systemd/system/sshd.service /etc/systemd/system

# 2. Redigér filen efter behov

# 3. Genindlæs systemd
sudo systemctl daemon-reload

# 4. Start/enable din tilpassede tjeneste
sudo systemctl start sshd

Oversigt og fejlfinding

Vis alle indlæste unit-filer

systemctl list-unit-files --type=service

Vis kun feilede tjenester

systemctl --failed

Analysér opstartstider

# Tjenester sorteret efter opstartstid
systemd-analyze blame

# Grafisk rapport som PNG
systemd-analyze plot > startup.png

blame viser tjenester sorteret efter opstartstid; plot genererer et PNG-diagram med en visuel opdeling af opstartstiderne.

Snapshots – et forbehold

Den officielle openSUSE-reference- og administrationsguide beskriver systemd-snapshots: sudo systemctl snapshot <navn>.snapshot, som gemmer systemets aktuelle tilstand og muliggør nem gendannelse (oprettelse, sletning, liste og isolate).

Bemærk: Denne funktionalitet virker ikke i praksis. systemctl snapshot og systemctl list-snapshots findes ikke længere – sandsynligvis er funktionen fjernet fra systemd til fordel for Snapper. Funksjonen er dog stadig omtalt i den officielle manual. Videens skaber efterlyser information, hvis nogen kender nærmere detaljer.

Timer-units (jobscheduling)

Systemd-timer-units bruges til jobplanlægning ligesom cron, men med flere fordele:

• Jobs kan afhænge af andre systemd-tjenester
• Timers håndteres som almindelige systemd-tjenester via systemctl
• Timers kan være real-time (kalenderbaserede) eller monotonic (relative)
• Timers logges i systemd-journalen, hvilket gør overvågning og fejlfinding lettere

Opret en service-fil

Opret filen /etc/systemd/system/mytask.service (navnet skal slutte på .service):

[Unit]
Description=My scheduled task

[Service]
ExecStart=/usr/local/bin/mytask.sh

Opret en timer-fil

Opret filen /etc/systemd/system/mytask.timer:

[Unit]
Description=Run my task every hour

[Timer]
OnCalendar=hourly
Persistent=true

[Install]
WantedBy=timers.target

Aktivér og start timeren

sudo systemctl enable mytask.timer
sudo systemctl start mytask.timer

# Tjek at timeren er aktiv
systemctl list-timers

Tip: Hvis timeren fejler med "bad unit file setting", så tjek statussen med systemctl status mytask.timer – ofte er det en tastefejl i unit-filen (f.eks. en forkert nøgle).

Temp-files (tmpfiles.d)

Systemd understøtter regelmæssig oprydning i midlertidige mapper via tmpfiles.d, som læser sin konfiguration fra (i prioriteret rækkefølge):

1. /etc/tmpfiles.d – egne indstillinger (overtrumfer de andre)
2. /run/tmpfiles.d
3. /usr/lib/tmpfiles.d – pakkenes standardkonfiguration

Konfigurationsformatet er én linje pr. post: type, path, action samt evt. mode, ownership, age og argument-felter.

Eksempel: automatisk oprydning i /tmp

Opret filen /etc/tmpfiles.d/cleanup.conf:

sudo vi /etc/tmpfiles.d/cleanup.conf

Med følgende indhold (sletter filer ældre end 10 dage i /tmp):

d /tmp 1777 root root 10d

Tjek derefter timeren, der håndterer oprydningen:

systemctl status systemd-tmpfiles-clean.timer

Tip: Der findes mange parameterkombinationer til forskellige use cases – læs manualen (man tmpfiles.d) for en fuld forklaring.

Logstyring med journalctl

journalctl giver adgang til at forespørge logbeskeder:

# Vis alle logs for en bestemt tjeneste
sudo journalctl -u sshd

# Følg logs i real time
sudo journalctl -u sshd -f

# Begræns antal viste linjer
sudo journalctl -n 50

-f er praktisk til realtids-overvågning (f.eks. mens du logger ind via SSH på en anden maskine) – afslut med Ctrl+C.

Opsummering

Denne guide har dækket:

• Grundlæggende systemctl-kommandoer (start, stop, status, genstart, genindlæs, enable/disable)
• Targets og hvordan du skifter mellem dem
• Oprettelse af egne unit-filer
• Fejlfinding og opstartsanalyse (--failed, systemd-analyze)
• Timer-units som cron-alternativ
• Oprydning af midlertidige filer med tmpfiles.d
• Loganalyse med journalctl

Af LivingLinux - https://www.youtube.com/@LivingLinux - https://bsky.app/profile/livinglinux.bsky.social

https://www.youtube.com/watch?v=8SNym6Pea-o

https://invidious.nerdvpn.de/?v=8SNym6Pea-o

Opensuse hardware page : https://en.opensuse.org/Portal:Hardware

openSUSE announced that you can start testing an image on the Raspberry Pi 5. Not everything is working, but it's probably usable for server tasks and you can start a desktop environment. 3D acceleration is not fully implemented, so I'm not doing my usual tests.

https://news.opensuse.org/2025/11/04/raspberrypi5-opensuse/

https://en.opensuse.org/HCL:Raspberry_Pi5

Default user is root and password is linux.

Make sure you have a recent installation of the Raspberry Pi firmware (I have 2025.04).

You can use YaST to create a new user, so you don't have to login as root. And you can use YaST to install additional software.

I look forward to a new image with 3D support.

00:00 Intro 00:12 openSUSE Announcement 01:04 System Information 01:46 Boot Issue (Fixed) 02:10 Images 02:30 Known Issues 02:54 YaST2 (Setup Tool) 04:54 vkCube 05:25 Future of YaST2 06:34 Closing Thoughts

If this video was helpful, please like, comment and subscribe!

(pæn) transcript : (fixed med mistral)

Kapitel 1: Intro Welcome to my channel Living Linux. In this video, I want to have a quick look at Open Soua on the Raspberry Pi 5.

Kapitel 2: openSUSE Announcement So, you can see that early November, they announced that they support the Raspberry Pi 5 and it took them quite some time to get it booting. And it looks like that they are upstreaming their changes to Uboot. Now, there's still a lot of work to be done, but I'm creating uh this video on a Raspberry Pi 5, or at least you see the desktop running on a Raspberry Pi 5. There are still a lot of things missing, but of course, they're working hard on it. And it might be that you have to update your EPROM. And yeah, I can show you that I have the firmware from April.

Kapitel 3: System Information So that one is good enough to get started with Open Soua. And yeah, here you see unfortunately at the moment graphics is software rendering and I'm more of a desktop person not really a server person. So that means that my uh use cases will be limited for the time being. Good thing is is that it has kernel 6.17.8.

Kapitel 4: Boot Issue (Fixed) Now there was an issue that booting uh could hang. Um but it looks like that that one has been fixed. So here is let's just say the main page for open sus on the Raspberry Pi 5.

Kapitel 5: Images So you can download different images and it's if you want to have a desktop image uh better skip KDE for now because it seems it has a graphic problem at the moment. You have to boot from micro SD. No other option.

Kapitel 6: Known Issues No support for I2S, ADC, I2C. Well, some more things. 3D acceleration not fully supported, but as you can see, you are able to get a working desktop.

Kapitel 7: YaST2 (Setup Tool) Now, one of the things that I've heard uh a lot of complaints about is that with Linux, people say that you have to use the terminal. Now, uh yeah, the default login is root with this password. And the only thing I did on the command line was change the password for root. But for instance, uh creating a user you can do with uh yast. That is yet another setup tool. So here you have a guey for editing a user, adding a user or even deleted. So that makes things a lot easier. One other thing is also that um a lot of the software you can just install it with y um so and even let's just say the software that you use on the command line that can also be installed with y with a guey. So here you can see that for instance vk cube uh falcon info you can just install it with this guey.

Kapitel 8: vkCube Now as I as they said uh 3D acceleration it's not yet implemented or at least not fully implemented. So if we have a look at VK cube then you can see that it's using a lot of CPU. It does work but it's using a lot of CPU.

Kapitel 9: Future of YaST2 Now one more thing about Yust. Uh it seems uh they want to phase it out and I think one of the reasons is that it was written in Ruby and not that many people use Ruby anymore or develop in Ruby anymore. So yeah, I think that there's not really something that really replaces Yust completely, but there are of course other things. For instance, the package manager, you can try to use Mirlin. Uh I also see that for instance like the administration part that they say that you can try soua multi Linux manager those kind of things but to be honest I never really used open soua before so it's still a lot of uh homework that I have to do but I think the good part is that you and start testing it on a Raspberry Pi 5.

Kapitel 10: Closing Thoughts And for the boot process, they're upstreaming it to Uboot. So perhaps other distributions can also make use of this in the future. So yeah, I would say anyone that is interested, give it a try. Um, first boot process can take a while. uh let it boot for a couple of minutes before giving up. And remember that you need to have a recent firmware. So this is all for now and hope to see you again in my next video.

(Rå) Transcription : Kapitel 1: Intro 0.010 sekunderWelcome to my channel Living Linux. 0.040 sekunderIn this video, I want to have a quick look at Open Soua on the Raspberry Pi 5. Kapitel 2: openSUSE Announcement 0.120 sekunderSo, you can see that early November, they announced that they support the Raspberry Pi 5 0.200 sekunderand it took them quite some time to get it booting. And it looks like that they are upstreaming their changes to Uboot. 0.340 sekunderNow, there's still a lot of work to be done, but I'm creating uh this video on a 0.410 sekunderRaspberry Pi 5, or at least you see the desktop running on a Raspberry Pi 5. There are still a 0.500 sekunderlot of things missing, but of course, they're working hard on it. 0.560 sekunderAnd it might be that you have to update your EPROM. 1.021 sekundAnd yeah, I can show you that I have the firmware from April. Kapitel 3: System Information 1.111 sekundSo that one is good enough to get started with Open Soua. 1.181 sekundAnd yeah, here you see unfortunately at the moment graphics is software rendering and I'm more of a desktop 1.261 sekundperson not really a server person. So that means that my uh use cases will be limited for 1.341 sekundthe time being. Good thing is is that it has kernel 6.17.8. Kapitel 4: Boot Issue (Fixed) 1.461 sekundNow there was an issue that booting uh could hang. 1.541 sekundUm but it looks like that that one has been fixed. 2.032 sekunderSo here is let's just say the main page for open sus on the Raspberry Pi 5. Kapitel 5: Images 2.102 sekunderSo you can download different images and it's if you want to 2.172 sekunderhave a desktop image uh better skip KDE for now because it seems it has a graphic 2.262 sekunderproblem at the moment. You have to boot from micro SD. No other option. Kapitel 6: Known Issues 2.362 sekunderNo support for I2S, ADC, I2C. Well, some more things. 3D 2.422 sekunderacceleration not fully supported, but as you can see, you are able to get a working desktop. Kapitel 7: YaST2 (Setup Tool) 2.542 sekunderNow, one of the things that I've heard uh a lot of complaints about is that with 3.033 sekunderLinux, people say that you have to use the terminal. 3.083 sekunderNow, uh yeah, the default login is root with this password. 3.193 sekunderAnd the only thing I did on the command line was change the password for root. 3.273 sekunderBut for instance, uh creating a user you can do with uh yast. 3.393 sekunderThat is yet another setup tool. 3.513 sekunderSo here you have a guey for editing a user, adding a user or even deleted. 4.014 sekunderSo that makes things a lot easier. One other thing is also that um a lot of the software 4.104 sekunderyou can just install it with y um 4.234 sekunderso and even let's just say the software that you use on the command 4.334 sekunderline that can also be installed with y with a guey. So here you can see that for 4.414 sekunderinstance vk cube uh falcon info you can just install it with this guey. Kapitel 8: vkCube 4.544 sekunderNow as I as they said uh 3D acceleration it's not yet implemented or at least not fully implemented. 5.045 sekunderSo if we have a look at VK cube then you can see that it's using a lot of CPU. 5.135 sekunderIt does work but it's using a lot of CPU. Kapitel 9: Future of YaST2 5.255 sekunderNow one more thing about Yust. 5.295 sekunderUh it seems uh they want to phase it out and I think one of the reasons is that 5.375 sekunderit was written in Ruby and not that many people use Ruby anymore or develop in Ruby anymore. 5.485 sekunderSo yeah, I think that there's not really something that 5.555 sekunderreally replaces Yust completely, but there are of course other things. For instance, the package manager, you can try to use Mirlin. 6.086 sekunderUh I also see that for instance like the administration part that they say that 6.166 sekunderyou can try soua multi Linux manager those kind of things but to be honest I 6.256 sekundernever really used open soua before so it's still a lot of uh homework that I 6.336 sekunderhave to do but I think the good part is is that you and start testing it on a Raspberry Pi Kapitel 10: Closing Thoughts 6.406 sekunder5. And for the boot process, they're upstreaming it to Uboot. So perhaps other distributions can also make use of this in the future. 6.526 sekunderSo yeah, I would say anyone that is interested, give it a try. Um, first boot process 7.027 sekundercan take a while. uh let it boot for a couple of minutes before giving up. 7.097 sekunderAnd remember that you need to have a recent firmware. 7.157 sekunderSo this is all for now and hope to see you again in my next video.

https://invidious.nerdvpn.de/watch?v=yGVdI0C_2Ro https://www.youtube.com/watch?v=yGVdI0C_2Ro

The Linux Lighthouse, your guide to Linux

Welcome to The Linux Lighthouse, Your openSUSE Linux Guide! In this video, we'll dive deep into systemd, the core of system and service management on Linux. If you're using openSUSE Linux, this guide is for you! We'll cover everything you need to know about systemd-from basic commands for managing services to advanced customizations with unit files, snapshots, and timers. Learn how to control your system's startup, schedule jobs like a pro with systemd timers, and debug services using journalctl. With clear examples and step-by-step instructions, this is your ultimate guide to mastering systemd on openSUSE Leap!

What You'll Learn:

Understanding systemd and its advantages
Essential systemctl commands for managing services
Switching and configuring targets (runlevels)
Customizing systemd with unit files
Creating system snapshots for safe rollbacks (deprecated)
Scheduling tasks with systemd timers
Managing temporary directories and cleaning them automatically
Monitoring logs and debugging with journalctl

Whether you're a beginner or a sysadmin, this video will give you the tools to take control of your openSUSE Linux system. Don't forget to like, subscribe, and hit the bell icon to get notified about new Linux tutorials!

🔗 Resources:

Official systemd Documentation: https://www.freedesktop.org/wiki/Soft...


openSUSE Reference Manual: Official systemd Documentation: https://www.freedesktop.org/wiki/Soft...

Online Shop US - https://the-linux-lighthouse.myspread... Online Shop EU - https://the-linux-lighthouse.myspread... Buy Me a coffee ☕️: https://buymeacoffee.com/thelinuxligh...

Linux #systemd #openSUSE #LinuxTutorial #openSUSELeap #opensusetumbleweed #SystemManagement #LinuxForBeginners #LinuxAdministration #TechTutorial #LinuxCommands #openSUSELinux #ITTraining #LearnLinux #linuxtutorial #tech

AI-genereret videooversigt AI kan begå fejl, så sørg for at dobbelttjekke dens svar.

The Linux Lighthouse explores systemd, the Linux initialization and service manager. The guide details how to use systemctl for process management, configure custom unit files, schedule tasks with timers, automate temporary file cleanup, and monitor logs using journalctl on openSUSE.