Just for comparison, here’s someone with a similar question that makes sense, asks detailed questions based on their knowledge and also responds to people in the comments.

https://lemmy.ml/post/46031895

Wouldn’t that be the most canny?

I’ve been following the discussion and it’s great to see this finally complete. Will definitely it once I have KDE 6.7

Don’t leave us hanging

Hedge bovine

hotfix²

https://bandcamp.com/

Perfectly illustrates how it doesn’t make sense.

I can get behind

• 11.30pm
• 12.30pm
• 1.30am

Or

• 11.30pm
• 0.30am
• 1.30am

But

• 11.30pm
• 12.30am
• 1.30am

just doesn’t make sense.

Didn’t appear to be vibecoded last I checked. Guy’s been working on this since 2024

Bro could build his own hornyposting community

That’s why bleeding edge distributions should not be recommended to new users.

Podman is an alternative to Docker which integrates better with systemd and it also offers a way to automatically update containers.

We should really tax them some more

They could easily make their own store with the original prices and increase the price on Steam to cover those 30%.

/etc/profile also needs root to edit. I agree that there should be a config file in a standard location, my issue is that using $(your local shell config) is barely a standard.
For this purpose PAM’s /etc/environment works great in the global context, but there’s no PAM equivalent for each user.
Systemd has global and per user environment stuff, but last I checked this only worked for systemd services

I didn’t know there was a fourth book. Awesome!

Edit: tbf, released in 2026

This is one of the exceptions to prove the rule

Hey fellow reader of that book!

At the risk of being serious, there’s really no good way to set user environment variables. (It’s been a while since I last checked, so I might be wrong)

PAM used to have an equivalent to their /etc/environment for users, but that was deprecated or maybe removed last I checked.

Systemd user environment variables don’t apply in a shell context

.bashrc only works if you use bash as login shell and I’m not sure if it applies everywhere. Sure, I can set stuff in the shell I use, but it feels weird to modify my shell in order to change global environment variables.

I’ve always used the longer version that asks processes to stop, then kills them before syncing and umnounting the disk.

REISUB: Reboot even if system utterly broken

Also, SysRq is often Print Screen on modern keyboards.