/mnt is meant for volumes that you manually mount temporarily. This used to be basically the only way to use removable media back in the day.

/media came to be when the automatic mounting of removable media became a fashionable thing.

And it’s kind of the same to this day. /media is understood to be managed by automounters and /mnt is what you’re supposed to mess with as a user.

Just today I heard someone whining about how in LinkedIn and other recruitment sites there’s like five bazillion profile tag options for RDMBSes and various dialects of SQL… when in actuality the recruiters are probably only concerned if the developer can do a bloody SELECT and stuff.

You Chrome folks need extensions to use non-Google search engines?

Firefox uses just bog standard OpenSearch definitions. No shenanigans. Ships with both Google and Bing if you’re into that sort of things. And you can add arbitrary search URLs, no probalo.

deleted by creator

NOP is $EA, of course, and… um…

…sorry, I’m just a Commodore 64 scrub, I don’t know nothing about this high and mighty Intel 8086 nonsense.

[looking up]

…it’s 0x90 on IA-32? WHAT? Someone told me every processor used 0xEA because that was commonly agreed and readily apparent. …guess I was wrong

In Wikimedia projects (and MediaWiki systems in general) you actually have to pay attention to other people’s usernames (when working with histories and in article discussions), and at least in Wikipedia long long time ago there was a lot of trolling/vandalism where people impersonated other users (particularly the admins) and made bunch of sockpuppets with tiny variations in names when they got banned. So this rule makes sense.

Debian, the cool guy distro in 1999. The machine overlords run on Red Hat.

In the low budget parody version, Neo ran Slackware, and the climatic battle was basically about Agent Smith somehow fucking up his libc.so.6 but then Trinity got him a copy of the file on 3.5" floppy from another system. Or something.

Yeah, I just tried upgrading my Gitea Windows instance to Forgejo via Docker, and it actually works pretty much as easily as it did before. Fantastic! Might just leave it here instead of shoving it all in the VM - I can always do that later if it’s necessary. Having a full VM does have upsides, but in this particular instance this is definitely good enough.

Heh, your comment actually made me finally go and resolve a problem I’ve had since I got this laptop in 2020. I didn’t have SVM virtualisation acceleration enabled because that made Windows unable to boot somehow. A bit of twiddling after, it finally did! VirtualBox runs! Docker runs!

…but why would I use Docker for something like this. Might as well blow the dust off of my FreeBSD virtual machine and run Forgejo there!

What’s the latest on Forgejo’s Windows builds? Last I checked there was no Windows build due to no volunteers for build/test - Gitea’s old build stuff should still be good.

Which is a mild shame because Gitea’s Windows version was an insanely simple way to run it if you are a solo dev on Windows and need a private Git site. Drop the binary on an USB hard drive, run it on terminal, boom, done.

(Currently contemplating just setting up a Raspberry Pi server.)

(Webmail provider releases a bespoke desktop app)
(me, old fart, bumbles out from behind the cables and servers and muck)

You fools! Have any of you whippersnappers ever heard of IMAP? No? Thought so.

[I’m not that familiar with ProtonMail. Chances are they already support IMAP. In which case: … …why? Why this? Why in this day and age?]