“Stable” distros often had a long and risky process of upgrading to the next major release.

But you only do that once every 3-4 years, and you have months to carefully plan ahead.

Meanwhile, pacman -Syu could just provide you a major breaking multi-package upgrade of, say, your desktop environment on any random Tuesday. And then your only options are to either roll the dice and accept that update right then, and deal with all the breaking changes it may introduce, or not receive any updates at all, including security fixes, until you do.

I use Arch myself, and it’s been pretty troublefree the past 2 years or so, but it was pretty rough around the Plasma 6 release, and there have been other rough periods as well, like when there were bluetooth/wifi and amdgpu regressions in the kernel.

Just stick these commands in a cron.weekly job or something, so you can forget about it:

paccache -rk2  # Remove packages from the cache, but keep the latest 2 versions
paccache -ruk0 # Remove packages from cache that are no longer installed

No. They produce for income

I never said they were altruistic. I’m saying: at the end of the line, there is a consumer buying the stuff they polluted for.

I understand the sentiment, but doesn’t “the industry” essentially produce things that are for “us”, even if indirectly?

Factories don’t exist for their own sake, they exist to make an end product for people. So if you want to change that, we do need to consume less, like the parent you replied to said.

I want newer software and I’m just not into going to the work needed to get the things I want running and still being easy to maintain

I don’t really get the “newer software” argument … they just leapfrog each other every year or so, if you stick to LTS versions. For example, when Trixie came out it was more up-to-date than Noble Numbat (24.04 LTS), and then Resolute Racoon (26.04 LTS) leapfrogged Trixie again, and next year Forky will leapfrog Resolute Racoon.

Also, with Debian, if the stable release is getting a bit stale, you always have the option to start off with Debian Testing, and get something that’s near bleeding edge up-to-date, and then follow testing until the next stable release and then stay on stable.

Ubuntu Server with CasaOS was fast and easy to setup. Maybe 15 minutes to get he basic file server I want

Never used CasaOS, but how would the setup process be any different on Debian? From an admin perspective, they’re nearly identical …

I had a quick glance at the CasaOS getting started page, and not only does Debian have official support but it’s recommended over Ubuntu, and the installation instructions appear to be exactly the same.

To me it just sounds like you’re a little bit stuck in your ways.

There were still plenty of annoying parts left when I ditched Ubuntu Server as my default server OS for plain Debian. In fact, increasing annoyances was one of the reason I made the switch. This was around 2018 or so, during the 16.04 LTS to 18.04 LTS switch, and I haven’t looked back. I’m quite happy with Debian 13 that’s currently powering my VMs.

Fair game not wanting to change a running setup of course, but do yourself a favor and look into Debian the next time you’re doing a new install of something.

Debian is just Ubuntu without all the annoying parts.

Both.

Debian for anything that has to run unattended for a long time without requiring much care. Arch for the desktop.

• Favorite distro: Debian
• Also favorite distro: Arch
• First distro: Red Hat Linux 5.1 (not RHEL!).
• Honorable mention: Slackware for most of the 00s

Everybody gangsta until “A stop job is running for …”

Especially since memory training on DDR5 can take upwards of a minute.

Just FYI: most bioses have a setting to save the memory training, so it doesn’t have to be re-done each boot. On an Asus board it’s called “Memory Context Restore”.

It’s “coffee” for people who don’t really like coffee and want to drink something warm with cream, sugary syrup and artificial flavoring.

Cronjob? I’m not a systemd evangelist or anyting, but certbot literally has a timer included in the package that you just have to enable to make it run twice a day: systemctl enable certbot.timer

Removed by mod

Removed by mod

Removed by mod

Removed by mod

Removed by mod

The laws can absolutely be written such that companies are required to suspend service to any suspected child without requiring ID to use the service.

The laws shouldn’t focus on “harming children” so much, but on “harming humans”.

The big tech companies should be held responsible for the actual damage they are inflicting upon society, and their methods to artificially inflate “engagement” (or whatever the hell they call it) should be held to scrutiny. Whether or not the damage is inflicted upon an underage person or an adult, is merely a distraction.

Those assholes would love it if we all had to identify ourselves and prove our age, if it means they get to keep inflicting their shit upon us.

Removed by mod