made you look
KHTML and WebKit is a historic mess but it’s debatable at best if Apple actually violated license terms.
There’s no requirement that a downstream fork needs to contribute their code back to upstream, they just need to release it, and they always did that.
The lead developer of systemd has said multiple times that we should be fine with break POSIX if it means developing faster.
I mean, so does GNU.
A lot of this is also a post-hoc justification, UNIX didn’t get shared libraries until some point in the 80s (Can’t find an exact year), so before that your options were to either statically compile the needed functionality into your program or keep it as an entirely separate program and call out to that.
It’s a perfect mix, in a time where enterprise storage was measured in single digit megabytes, and the only efficient way to created shared functionality was via separate programs, and you’ve got an OS that happens to have “easily pass data between programs” as a core paradigm.
And now people invoke it to attack an init program for also monitoring the programs it starts and not just spawning them.
If you detach the origin from the host it’d work, aka HTTP Alternative Services. Firefox used to (maybe still does? idk) use it to silently switch from using the base hostname to a hidden service when running under Tor, when the site provided the mapping.
Clearnet stuff would work without it, but any I2P/Tor support needs server integration, which would be non-existent at the moment I’d bet.
Git itself (Or any other VCS for that matter) really should treat symlinks as special, similar as to how btrfs stores everything as “reflinks” internally. They be stored as special references to other tracked objects (so it’d be impossible to commit a symlink that pointed at anything other than a checked-in file, and ensure they always match), and git can materialise them as needed.
Windows Terminal is the terminal emulator that hosts the shell (cmd or PowerShell, or anything else really). It’s the modern replacement for “conhost”.
It’s also a fantastic app, some of the devs are on Mastodon too.
It’s real, but probably not an issue in practise.
If it does actually turn out to pose a problem, then just disable secure boot on those systems, not like it’s really securing anything at that point.
Edit: I did learn from this thread today though that ZSH has it set to where you can just type part of what you’re looking for then hit up to do the same thing. Neat!
Fish too, it’s fantastic.
AMD has its own mix of issues with Vulkan between RADV (mesa), AMDVLK, and AMD’s proprietary driver on a per-game basis at times.
Good news, they’re going away. AMD is focusing entirely on Mesa now.
It’s a peaceful life.
And the reason you’ll want to do this is that it exposes FS mounts in the service dependency tree, so e.g. you can delay starting PostgreSQL until after you’ve mounted the network share that it’s using as a backing store, while letting unrelated tasks start concurrently.
If all you want to do is pass some special mount flags (e.g. x-systemd.automount) then fstab is the way, after all it’s still systemd that’s parsing and managing it.
Ideally they’d be set to not be running unless they’re actively needed.
Or Automattic doesn’t have enough employees left to implement it
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.
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.
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
I can’t imagine the shame I’d feel if there was a legal finding stating that I was a fan of the minions.
The latest Nvidia drivers have broken composition in Xfce, so I’ve been raw-dogging basic X11. It’s like I’m using WinXP again.