To add some points, that I do:

• Proper logging: So I could realize something unusual is going on
• rootless podman container: harder to escalate privileges and gain root
• Apparmor: same, plus it could trigger suspicious log entries

Don’t feed the troll

If a firefox add-on is okay: Brief

Dicky McDickface

Sure they could, but why would they?

Hollies - Long dark road?

Is this “Don’t be evil!”?

Ultima Underworld 1

Baldur’s Gate 2

Would it not just be the easiest way to put your scripts under /etc/network/if-up.d/? Then they get run once that connection is brought up.

Birds aren’t real!

Dito

Joe - just for quick edits on a text file

I just debuged it like every other of my scripts that failed. Again, I didn’t need any special knowledge of the init process, just general (and for me: very limited) knowledge.

The answer to your other questions: I don’t thing I ever did that.

I find everything so complicated with systemd.

SysV was just intuitive for me and my knowledge. There was just one directory with all the startup scripts in it. And they were run in their alphanumerical ordner. Just that simple. If I wanted to change the order in which the scripts started, I just had to rename the file. You don’t want a script to run at all? Just remove it.

I assume, systemd has many advantages for a knowledged user. But for me, it still is just a hassle.

Sorry for the delayef answer (still short of new to lemmy).

Basically you crasped the core of Icewm: super minimalistic. But it does everything I need.

Over the years, I have looked into fancier desktop environments, but they all seem unnecessary overloaded to me.

Maybe a short work flow clarifies how I use icewm:

1. After login, the startup script starts all programs that I regularly need.
2. Shortcuts to resize windows and move them to different desktops and circle through open windows.
3. Shortcuts to open more common programs
4. For everything else: konsole

IceWM. Just the bare minimum I need. But nothing more.