This is x86 assembler. (Actually, looking at the register names, it’s probably x86_64. On old school x86, they were named something like al, ah (8 bit), ax (16 bit), or eax (32 bit).) Back in the old days, when you pressed a key on the keyboard, the keyboard controller would generate a hardware interrupt, which, unless masked, would immediately make the CPU jump to a registered interrupt handler, interrupting whatever else it was doing at the point. That interrupt handler would then usually save all registers on the stack, communicate with the keyboard controller to figure out what exactly happened, react to that, restore the old registers again and then jump back to where the CPU was before.

In modern times, USB keyboards are periodically actively polled instead.

Why the fuck is a Microsoft account so important to Windows that running it without one is considered a “loophole”?

There’s that “I never vote because politicians do not care about the issues of people like me anyway” attitude again.

(Hint: They don’t care because your kind won’t vote anyway.)

S-ATA still is the only way to have more than two drives in the system.

IMHO, it was a mistake to make USB block storage use the same line of names also used for local hard disks. Sure, the block device drivers for USB mass storage internally hook into the SCSI subsystem to provide block level access, and that’s why the drives are called sd[something], but why should I as an end user have to care about that? A USB drive is very much not the same thing for me as a SCSI harddisk. A NVMe drive on the other hand, kinda sorta is, at least from a practical purpose point of view, yet NVMe drives get a completely different naming scheme.

That aside, suggest you use lsblk before dd.

The last Windows I installed was Windows 10. I was trying to install onto a SATA SSD, while keeping my pre-existing Linux installation on the M.2 SSD intact. This took me an unreasonably long time and lots of failed attempts, and in the end, the only way I could find to make it work was to first physically remove the M.2, then install Windows, then add the M.2 back again. Which sucked a lot, because M.2s are really not optimized for easy or frequent installation and deinstallation.

Is OpenBSD seriously still using CVS for development?

And “nothing” does not fit, either.

Can’t you just use just about any m.2 SSD with the 2230 form factor?

I have been sort of following Wayland’s development for over 10 years now. I have been using Wayland for over 2 years now. I have been reading and watching various lengthy arguments online for and against it. I still don’t feel like I actually know it even is, not beyond some handwavey superficialities. Definitely not to the extent and depth I could understand what X11 was and how to actually work with it, troubleshoot it when necessary and achieve something slightly unusual with it. I feel like, these days, you are either getting superficial marketing materials, ELI5 approaches that seem to be suited at best to pacify a nosy child without giving them anything to actually work with, or reference manuals full of unexplained jargon for people who already know how it works and just need to look up some details now and then…

Maybe I’m getting old. I used to like Linux because I could actually understand what was going on…

The KDE team has already determined that this is not a bug and that both you and me must just be imagining it:

https://bugs.kde.org/show_bug.cgi?id=481058

It’s a lot better than the system that just randomly throws in your USB drives with your SCSI/SAS/SATA/PATA drives. Or the systems that calls everything a SCSI drive when it usually isn’t a SCSI drive.

About 20 years ago, Microsoft was found guilty and convicted, because they forced their browser on their users, driving out competitors by abusing their de facto monopoly on PC operating systems. These days, they are doing the exact same thing again, just on an even broader base. I don’t even understand how this verdict took so long.

Smartctl works on nvme drives. Use it.

btop for bling

htop for practical utility

top for minimalism, availability, reliability

6. WebEx hat Sicherheitslücken, die im Öffentlichen agierende Security Researcher nicht gefunden haben, weil das closed source ist und man da legal nicht so einfach rankommt, während im dunklen agierende Zeitgenossen, die sich um legal versus illegal nicht kümmern, schon seit 10 Jahren auswendig wissen, wo genau man einen Stapelüberlauf provozieren kann,und welche Rücksprungadresse man da reinschmuggeln muss, damit das Ding macht, was man will…
7. WebEx hat absichtliche Sicherheitslücken, die Cisco vom Amerikanischen Staat aufobtruiert wurden, und die dann entweder durch Spionagegeschichten oder Eigenrecherche auch den Russen bekannt wurden.

Gut, in diesem konkreten Fall ist die Erklärung natürlich noch viel einfacher: Ein Konferenzteilnehmer hat über eine altmodische, unverschlüsselte Telefonleitung aus Singapur teilgenommen, und die abzuhören, war noch nie ein Problem.

Whoops, Weihenstephan gehört zu Müller?

Gut, dass das mal jemand erwähnt…

Ich bin ganz froh, dass sie’s irgendwie geschafft haben, der Versuchung zu widerstehen, da noch irgendwelche Produktwerbung rein zu schmuggeln…

To be a bit pedantic about it, they are perfectly valid, they just don’t exist.

Honestly, why would you host a service like that under the Afghani TLD, knowing fully well what kind of country Afghanistan is these days?

“Shut down by the Taliban”, sure, because you handed them the switch to shut down for no good reason.