The_Decryptor

Tizen (resting place of Meego)

I’d say SailfishOS is the final resting place of MeeGo, especially since it’s maintained by ex-Nokia devs.

I mean, the point of the init process is to bring up the filesystem and disks, if the configuration is wrong that’ll be the process to complain about it.

“No, go away.”

That’s a perfectly valid way to deal with toxic contributors. There’s always people with better social skills and equal developer skills out there, you don’t have to accept and include toxic people just because they wrote some code.

Also, compared to something like the Switch? I don’t see MS remotely bricking these devices if you run “homebrew” on them.

I’d double check, if you haven’t picked an option specifically it might just default to the fallback (i.e. BOOTX64) It’ll be under the boot device order section.

(Not my picture, stole it from Reddit)

Here it’s listing all the possible boot options this mobo can find, but there’s a generic “UEFI OS” option which I’d bet is the fallback. And once a choice is made it’s kept unless something resets it, so if it just happened to be set to the fallback once it’ll stick with that until a change is forced.

When installing windows while there is a Linux install, windows will see the EFI partition already there and just decides to share it, and doesn’t create its own.

That’s what it’s supposed to do, it’s a plain FAT32 partition, the bootloaders are just files you put in there.

Part of the issue is that while a well-made motherboard will look for all bootloaders on the partition and present them as options in the firmware UI, bad ones will only look for a specific file (\EFI\BOOT\BOOTX64.EFI) and use that. For an OS to have a chance of booting on those boards it has to overwrite that file, blowing away whatever other bootloader was there before.

It’s annoying, since Windows is mostly well behaved here (It puts the main copy of the bootloader at \EFI\Microsoft\Boot\bootmgfw.efi and Linux bootloaders can see that and offer it, the reverse isn’t true) and can co-exist with Linux well (Well…), but manufacturers cutting corners causes more problems for everybody.

And there’s still web directories hanging around, similar to the now dead dmoz site.

https://url.town/ and https://curlie.org/ for example

(and why isn’t spell check core Windows functionality?)

It actually is, introduced in Windows 8, it’s just taken devs ages to actually start using it (Notepad only got it last year, 12 years after it was introduced)

Good news, they’re making it easier to fix stuff like “spurious double clicks”.

https://who-t.blogspot.com/2025/05/libinput-and-lua-plugins.html

True, that’d definitely make it a lot more viable to hold corporations to account.

It’s an easy license to reason about, allows for basically any project to use it, and you don’t need to worry about trying to enforce it (Because the GPL is only as good as your lawyers are)

Plan 9 is inspired by UNIX (Helps that it had the same devs), but it’s not a direct continuation.

UnixWare is I think the only direct continuation of the original AT&T UNIX. The various BSDs are close enough but were re-written entirely in the late 80s/early 90s so there’s nothing original remaining.

Should be possible, as it’s a normal VM you can already install flatpak apps in said VM as normal, you’d just need a Windows side bit to invoke the install within WSL when you opened the flatpak bundle, and then something to add a start menu shortcut from the app inside the VM (Which I actually assume already exists, I never actually ran WSL2 when I was on Windows)

Why have a laptop or a dual boot with Linux when you can now more easily stay on the proprietary OS ?

This is called market retention.

Preventing migration to another OS, another software ecosystem.

The ‘Embrace’ and ‘Extend’ parts of EEE.

That’s stretching the definition to the point it’s nearly unrecognisable.

What the term meant was for things like Internet Explorer, where MS adopted an existing standard (Embrace), started changing it in incompatible ways (Extend), while using their market power to lock out competitors (Extinguish)

e.g. IE used an incompatible method for sizing and laying out elements than any other browser, so a site that laid out properly in NN4 looked broken in IE6, and vise versa. So most devs targeted IE6 as it was more popular, and NN4 users got more and more broken sites.

ACPI was similar, Windows had an extremely lax implementation of it, so motherboards often shipped with bugs that Windows would ignore but would stop anything else from booting. Intentional? Doesn’t really matter, since it sure was helpful in slowing the adoption of things like Linux, that had to come up with workarounds for all the broken hardware.

Not like you can fork it to run on a different OS.

For WSL1? yep that’s effectively impossible.

WSL2 is effectively just a wrapper around the kernel virtualization support and a bundling format, as long as whatever image you run talks to the host properly (like any other virtualised OS would) it’d run.

I can’t imagine the shame I’d feel if there was a legal finding stating that I was a fan of the minions.

e.g. Mastodon has been around for years, is actually really federated, not owned by a corporation, and a lot more features than BlueSky… but bluesky already has more users and i think largely because: marketing… how are people going to talk about “Mastodon” when they’ve probably never even heard the word before? (also named after a cool band, but not suitable for the masses).

Also fewer syllables, which apparently has a noticeable impact.

It is all generic layers, the base USB stuff is called a “Human Interface Device”, controllers/keyboards/mice/etc. all show up as a HID to the OS. But you need some way to standardise the input and map the device side events to the host side, so the OS will have a mapping layer above the base USB layer that turns a generic HID into a “controller device” that an app can use.

As you can see from the patch, that’s all they’re doing. They’re adding the USB IDs of these controllers to the mapping layer so instead of being shown as a “Generic HID”, they’re shown as “Generic Xbox Controller”. Doing so also means the controller layer can drive the devices specifically, e.g. xbox controllers need a special handshake to enable the xbox button, the base generic input layer doesn’t need to know that stuff.

He could have tried to fight the order, that’s what the previous management used to do.

Musk defends enabling Turkish censorship on Twitter, calling it his “choice”