Or just git push origin --force blank:main

Wait. So the flaw was in uutils, and this article reported it as a systemd bug…?

Debian on my personal computers and servers.

Ubuntu on my work desktop, RHEL on work’s servers

I wouldn’t consider Debian “Canonical”-y, it’s just what they happened to pick as their upstream.

I tried some of the atomic distros, but ran into too many problems. When I buy a new computer, I sometimes have to run Opensuse Tumbleweed or Arch to get new enough hardware support… Too lazy to rebuild my kernel and mesa at home

I’m confused… Cursor? Surely you control everything via keyboard?

Just need to use less obvious insults, a la, “your mother was a hamster, and your father smelt of elderberries”

Still poisons the model with something an end user won’t like, but isn’t easy enough to train out

The software manager they’re using already looks like GNOME 3+

Why do people keep referencing this like it was merged…

It was specifically rejected

Maybe to help, you can see where you’ve enabled “repositories” that APT can download from in /etc/apt/sources.list and /etc/apt/sources.list.d

As long as you haven’t manually installed a .dpkg package, or manually modified it, they should be something like

deb.debian.org security.debian.org

Some things like Slack may try to add their own repositories down there

When you type “sudo apt install” it is allowed to install from any configured repos down there

Oof. Should we tell him what he’s in store for, guys?

I set up, and prefer, iptables rules to rate limit logins.

I have mine set so you can connect up to 5 times per 15 minutes.

Blocks bots well enough, and if I really mess up, I just wait 15 mins

At least for a long time, you had to set up RPMFusion to be able to play media, and having the additional repos tended to break on major upgrades for a bit after release

So, for beginners, it was a bit painful to suggest

That’s what I’m using these days at home

Only thing to keep in mind is that it won’t give you a notification when you need to do a major version update (pretty consistently every 2 years)

Probably less of an issue these days; they relaxed their stance on proprietary drivers:

https://www.zdnet.com/article/debian-linux-accepts-proprietary-firmware-in-major-policy-change/#ftag=RSSbaffb68

The problem with the simplified phrase is that your computer is expected to run more than one program at a time.

If you are only running one program, it should certainly use all the RAM of your system.

However, your desktop, laptop, phone, tablet, game console, etc. all run hundreds or thousands of programs at the same time. Each individual application should optimize RAM usage so the whole system can work together.

Another commenter in the chain talks about disk caching, which is what the phrase “unused ram is wasted ram” came from

It’s been coopted by application programmers who don’t want to optimize their software

If your motherboard manufacturer releases firmware through LVFS, you can use

sudo fwupdmgr refresh --force sudo fwupdmgr update

But that should normally be offered through the GNOME or KDE update utility.

I’m assuming your motherboard manufacturer doesn’t support updating through the OS (or hasn’t released a new enough AGESA build) based off your issue

Cynically, isn’t this just because Debian did it with Trixie, so now Ubuntu’s next version is pulling in the change?

You’ve updated your motherboard’s firmware to a version that includes the fix?

What issue are you having from the missing instruction?

Okay Claude, but this is running on iOS. Do you think there’s another solution?

The reason I don’t recommend it by default is that there is no updater across releases.

The official upgrade process is to modify apt sources files and run upgrade, then full-upgrade, etc.

That’s fine for me but it makes it hard to recommend to people who may not be as willing to deal with modifying system files and reading some upgrade notes

I think mech@feddit.org is right, but one other piece I’ve heard is that “unmanaged” desktops make things like randsomware insurance harder