I don’t.

Clearly you don’t know.

If I wanted to run updates frequently I would run arch lmao. Even if I did apt update every day, debian stable doesn’t get that many updates.

You’re not updating for features you’re updating for bug and security fixes. That’s why Debian stable doesn’t have many updates. But the ones they do are typically important.

That’s… Not how it works… Debian is “stable” not “secure”. You use Debian so that is easier to run updates frequently since they’ll be unlikely to break things.

All systems, daily via a single ansible script. That’s apt update, upgrade and reboot if needed (some systems set to only reboot with a separate script so I can handle them separately).

Rarely have any sort of problems.

No.

Sounds like you bookmarked the while flippin’ Internet.

Then how do you know that “most streaming services don’t work on Linux?”

This is an awful analogy…

squeezing every last drop of resource form tired old hardware

This is such a myth. 99% of the time your hardware is doing there doing nothing. Even when running “bloated” services.

Nextcloud, for example, uses practically zero cpu and a few tens on mb when sitting around yet people avoid it for “bloat”.

I’m not sure how the *arr stuff works but hard links don’t let you “edit a file while preserving the original” - they let you have mulltiple paths to the same file.

$ echo "hello" > file1
$ ln file1 file2
$ echo "world" > file2
$ cat file1 file2
world
world

Does *arr have some sort of copy-on-write behavior? Some modern file-systems have de-duping behavior and copy-on-write built in that you may be able to save some space with.

But the point of topic 1 was to simplify. You can keep doing your hardlink stuff but standardize it and simplify setup/configuration. If you always do things in the same way it’s less complicated to keep track of and fix.

You’ve understood the difference in terraform/ansible, and yeah terraform is probably not going to be as helpful. Ansible would be much more likely to help. It can seem burdensome to have to write configuration files for things at first, but it forces you to do things in a way that is standardized and repeatable.

1. Simplify. You’ve made a system more complex than it needs to be. Copy files rather than working around hard link limitations. Use off-the-shelf backup solutions. Have a single file server with a known location for all your mounts. Etc.

2. Automate. Not with bespoke bash scripts but with tools like ansible and terraform. These tools are built to help manage infrastructure and configurations.

Everything is a file? Naah, everything is a hard link ! (Or inode? xD)

Hard links are files…

Well - it was nowhere near helpful.

you’re already using a different DE than Pop comes with

Pop comes with KDE/Plasma.

I use PopOS because I have a System76 laptop. It runs well on my hardware. I’m allowed to complain about things without some shit telling me to just “use another distro”. If I wanted to run another distro I’d run another distro. Lordy…

This makes no sense - Pop_OS offers Gnome, KDE/Plasma, etc. as alternatives. Why should I stop using it because I don’t like one of the other DEs?

New software has bugs??

I’m very annoyed - I hate cosmic and just want normal sytem updates.

I tried a number of the alphas and just hate it. Like fundamentally hate it, not just because it was buggy.

I wish System76 would just put out a 24.10 release instead of spending all their resources on this DE.

Oh for sure - containers are fantastic. Even if you’re just using them as glorified chroot jails they provide a ton of benefit.

Containers run on “bare metal” in exactly the same way other processes on your system do. You can even see them in your process list FFS. They’re just running in different cgroup’s that limit access to resources.

Yes, I’ll die on this hill.