Why does nobody mention the Discordian calendar? 5 days per week, 73 days per month, 5 months to a year (Chaos, Discord, Confusion, Bureaucracy and the Aftermath). On leap years, it adds one additional day (St. Tib’s day) with a name but no numerical date.
- 0 Posts
- 8 Comments
waigl@lemmy.worldto Technology@lemmy.world•Windows 11 is closing a loophole that let you skip making a Microsoft accountEnglish0·2 months agoWhy the fuck is a Microsoft account so important to Windows that running it without one is considered a “loophole”?
waigl@lemmy.worldto Mildly Infuriating@lemmy.world•Developers: "Yes, the users love cluttered homes, just put everything there and ignore guidelines"English0·4 months agoFiles and directories starting with a dot are hiden by default. You are aksing for this stuff if you manually unhide them.
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.
waigl@lemmy.worldto Technology@lemmy.world•OpenBSD has reached OpenBSD of TheseusEnglish0·10 months agoIs OpenBSD seriously still using CVS for development?
Uh, what’s happening here? The post shows no content for me, and clicking on the title only redirects me back to the post itself. Yet other people in the comment section are talking as if there was some specific content here, other than just the title “ravages of socialism”.
Am I missing something here? Is there a malfunction, or did OP edit their post after the fact so that the actual content is just gone?
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.