• Log in with your local Linux account

• Log in as administrator

• Log in via carrier pigeon

• Psychic log in

• Log in using public shared account (that anyone and everyone can log into and use)

• Log in your pets

• Log in via Hallmark greeting card (only available on your birthday or major holidays)

• Log in with blood sacrifice

the general perception that rolling distros are annoying since they might break sometimes, with the reality that non rolling distros definitely break shit when upgrading versions.

Personally, I still prefer the non-rolling distros.

A rolling distro might break on any update, and you never know when.

But for non-rolling, you can wait until you have available time to deal with any issues. Sure there will be issues and things that need reconfiguring – you basically just reinstalled your whole OS. But you can choose when and if that happens, so you can schedule it for a convenient time when you’ve got time and energy to work on it if necessary.

(And, personally, I wouldn’t do the dist-upgrade thing at all. I just download the newest LTS version and install it as a fresh install, then port everything important over from backups. Nice fresh start with no old baggage hanging around. Often, I’d do that at the same time as a major hardware upgrade as well, so it’s basically a new PC.)

Then … don’t do that?

Is there something that 24 had and 22 didn’t and you just had to have that feature? If not, just stick with 22.

Or if you’re one of those who just has to have the latest of everything, you should be on a rolling release distro instead, and you won’t have this issue.

So many of these things just seem incredibly bizarre once you’re used to Linux.

Give him a bb gun and cardboard armor, then send him to the front lines.

Fucking why? Why would anyone else want to get involved in this war?

Windows and Linux don’t feel fundamentally different these days

Try Windows 11 vs. Linux on a shitty old laptop with a budget 2-core processor and 2GB of RAM. Then tell me Windows and Linux don’t feel any different.

When you become one with the penguin, though … then you can begin to feel how much faster modern hardware is.

Hell, I’ve got a 2016 budget-model chromebook that still feels quick and snappy that way.

and it had Turbo button, which did absolutely nothing

These old ‘turbo’ buttons actually did do something – they limited your CPU clock speed.

Because some old games (and perhaps other software) relied on counting CPU cycles for timing the game. The faster your CPU, the faster the game would run, and the faster things in the game would happen. When CPUs got too fast for this, such games became unplayable because everything was happening in such fast-forward speed that the player could never hope to keep up. The counter-intuitively named ‘turbo’ button would bridge a jumper on the motherboard and change your CPU clock speed to a lower value, slowing it down so these old style games could still run at a reasonable, playable pace.

Ironically enough, the ‘turbo’ button made your PC slower.

(Personally, I think turbo buttons are due for a comeback, but as fan control options. Use a ‘turbo’ button to switch between fan control profiles – turbo off for quiet profile, turbo on for maximum performance profile.)

That’s the tricky part, innit?

A few good options:

A) Set up your backup/restore procedures immediately after setting up your fresh new system. And then immediately test them to see if you can successfully restore, before you’ve done anything important on the new system that you can’t afford to lose. If the restoration completely fails, no biggie. You just have to start over on setting up your fresh new system.

B) Attempt to restore your backup to a different system, not your primary one. You’ll need a second set of hardware to do that, but if you’ve got the hardware lying around, it’s a great way to test your restore procedure. If you’re upgrading your hardware anyway, it could be a good time to do this test – use your backup restoration procedure to move your data to the new hardware. (As an extra bonus, this doesn’t require any downtime on the primary system.)

C) Simulate a complete hard drive failure and replacement by replacing your primary system’s drive(s) with a blank new one. If the backup restoration fails, you should (fingers crossed) be able to just plug the old hard drive back in and everything will go back to how it was before your test.

D) Have multiple backups and multiple restore plans, and just hope to fuck that at least one of them actually works during your testing.

Option A can only be done if you’re proactive about it and do it at the right time.

Options B and C require extra hardware, but are probably the best choice if you have the hardware or can afford it.

And Option D will always have at least a tiny amount of risk associated with it.

Do you know how to transfer the files back if your OS has completely failed?

Verifying the files are there in your backup is only, like 10% of verifying that it’s a real, usable backup.

The important question is: can you successfully restore those files from the backup? Can you successfully put them back where they’re supposed to be after losing your primary copy?

Paying attention to a trans man’s feelings would only give them feelings of gender dysphoria.