palordrolap

m’user

First episodes almost always don’t count as far as lore goes, even if some things do carry over.

Uh-oh Spagetti-O’s

This is one of the larger plot holes in the 1980s remake of The Fly, in my opinion.

“… you don’t. You recover it from /dev/random. Eventually.”

Hiroshima was a man-made disaster that happened in 1945.

Chernobyl was a man-made disaster that happened in 1986.

And now generalise for the punchline.

And the fact it was called Chicago had absolutely nothing to do with the fact that that Apple Mac system font was called Chicago, no sir, nuh-uh, total coinkidink.

If you have Windows, it might be worth getting it to run Scandisk - or whatever the current equivalent is - on that drive.

That would at least give it less excuse to set problematic bits. In theory there’d be no harm doing this. In practice, well, make sure you have other copies of whatever is on that drive on the off-chance Windows constantly setting that bit is a sign of an underlying problem that Scandisk would make worse (or Windows/the disk decides to mangle files for some other reason.)

Two types of people on Earth. Those in the bottom percentile and everyone else.

Dumb question time: Which distro is this, and could there be a better option?

(Linux Mint deliberately removes Snap from stock Ubuntu, for example, but they dropped KDE a while back, and I don’t know if anyone has got KDE running or not.)

2K was my jam.

The death of the DOS line of Windows (3.x, 9x, ME) lead to the decision to inject clown DNA into NT in order to appeal to the masses and that’s how we ended up with XP.

Vista was an attempt to eradicate the clown, but it was still there, people hated it and because Microsoft thought they had eradicated the clown, they thought people wanted more clown, and that’s how we ended up with Windows 8.

What about 7? The clown gene skipped a generation.

Back in the old days, it was enough to simply defrag a Windows drive - preferably from safe mode or using the DOS it ran on - and there’d be a strong chance that everything would be shunted to the start of the disk, which would be ideal here. It was how I was able to make room to create Linux partitions on my first PC back in the day.

Copying that Windows partition image would have a strong chance of working first time on the new disk (or partition).

These days (which I use very loosely, since XP might have been guilty of this) Windows likes to splat important things all over its partition and can require some convincing to move it. There may also be license problems if Windows thinks something screwy is going on.

Hopefully solidgrue (or others) can recommend something. Third party partition management software and/or boot USBs would be my bet, but I don’t know what’s good.

Worst case, you’ll have to back up your important files and create a new installation on the new disk. It wouldn’t hurt to get started on that backup in the meantime. Better to have one and not need it, etc.

You can’t fool me. I know Shia LaBeouf when I see hi—aaack everything is normal here use Wayland

perl -wle

Sounds like a job for a USB trial run on a rainy weekend when you’re not doing anything else.

Nvidia supply OEM drivers for the Debian family (Debian, Ubuntu, Mint), if not others, assuming the open-source drivers don’t cut it for you. Microcode updates are released for both Intel and AMD.

You’ll probably run into issues with some games. Things are getting better on Linux, slowly and steadily, but many games are written specifically for Windows with no Linux port available. Steam’s store, for example, shows which games are SteamOS compatible, which usually means they’ll run on Linux too.

For other games it’s worth checking the Internet - e.g. www.protondb.com to see if anyone else has a particular game running under Linux. You’re probably aware that there are programs that attempt to provide some layer of Windows behaviour that form part of the solution. Some of the solutions may or may not involve command line use.

This is one of those situations where explaining why I said what I said, when I said it, in the way that I said it, and bring into question whether I could have worded any of it better takes way more time than a glib aside. Something adjacent to the Bullsh*t Asymmetry principle, if not an instance.

Anyway, I was trying to encompass those folks who tend to set their system time to 12hr, and wasn’t really saying anything one way or the other about whether the person who made the screenshot (OP it seems) generally has their system set that way or not. It was more pointing out that having it be 24hr (or leaving it that way) makes the time look a bit like a year in the not-too-distant future (2028), and thus could form part of the date that is otherwise displayed.

It could be that the whole thing is a coincidence, but I was pointing out that it could have been part of the joke.

I feel like the choice of time of day (24hr clock) for the screenshot might have been an attempt at being prophetic.

nano with the new, alternative “GUI editor standard” keybinds or the old pico ones?

AMD graphics drivers might be an example of this. They’re made by AMD for Ubuntu specifically, not Debian. They work* on LMDE, so I assume they will also work** on Debian, but they weren’t specifically developed for that platform.

Installing them was a bit hairy, but they’ve survived at least one kernel update so far, which is somewhat reassuring***.

* on my specific hardware.

** for some hardware combinations, including mine, if not all.

*** but not completely. FrankenDebian is the word I use for it.

I’m not sure I’m a fan of systemctl either, but I think your hatred of it has caused you to read way too much into what I said.

Love it or loathe it, systemctl is trying to do the right thing with regard to stability and data preservation.

If you really mean it, the manual offers a few levels of strength beyond the plain one: -i (don’t check for busy processes, which is what’s going on in the meme), -f (force, presumably asks even less nicely), and -f -f (don’t even ask, just do it now, preservation be damned).