yes

IIRC Mono was mostly used for WASM as it was optimized for smaller builds than the full fat CoreCLR (talking about .NET non-Framework Mono)

It really wouldn’t change anything in the long run. Any company that creates a browser is gonna need some form of income and people aren’t willing to pay for a browser. What would be their incentive to continue to work on the browser when they aren’t being paid?

The kernel modules usually are signed with a different key. That key is created at build time and its private key is discarded after the build (and after the modules have been signed) and the kernel uses the public key to validate the modules IIRC. That is how Archlinux enables can somewhat support Secure Boot without the user needing to sign every kernel module or firmware file (it is also the reason why all the kernel packages aren’t reproducible).

And technically you can whitelist other certificates, too, but I have no idea how you might do that.

When you enter the UEFI somewhere there will be a Secure Boot section, there there is usually a way to either disable Secure Boot or to change it into “Setup Mode”. This “Setup Mode” allows enrolling new keys, I don’t know of any programs on Windows that can do it, but sbctl can do it and the systemd-boot bootloader both can enroll your own custom keys.

I did hear that one of their newer versions does use eBPF, but I haven’t even remotely looked into it.

https://nondeterministic.computer/@mjg59/112816011370924959

I don’t think any of the major distros do it currently (some are working twards it tho), but there are ways (primarily/only one I know is with systemd-boot). It invokes one of the boot binaries (usually “Unified Kernel Images”) that are marked as “good” or one that still has “tries left” (whichever is newer). A binary that has “tries left” gets that count decremented when the boot is unsuccessful and when it reaches 0 it is marked as “bad” and if it boot successfully it gets marked as “good”.

So this system is basically just requires restarting the system on an unsuccessful boot if it isn’t done already automatically.

I also didn’t expect Lucy, I expected some other FGC character but I am not too too surprised considering they have RWBY in BBTAG

Accent colors are coming with GNOME 47.

There were talks a few years ago about changing sd-tmpfiles name but it was decide not worth it due to the churn and bikeshedding it would cause.

sd-tmpfiles is generally used to create, modify (e.g. permissions) and remove directories on the system. The home.conf is intended for systems that only ship /usr/ (e.g. containers) to create /home/ and /srv/ as a separate subvolume on btrfs

The BSOD really isn’t something to be mad at, it actually in theory is good but there is only so much you can do when a kernel panics. What you should be mad at is shitty drivers causing BSODs

which definitely seems out of scope.

Doesn’t seem out of scope for a system and service management suite. Like, the timeperiod where systemd was “just an init” was relativly brief (like half a year).

The case is: You switched to it before it was “old-old-stable” and haven’t updated.

Causes for this are likely:

• Software hasn’t been tested on new version
• Software hasn’t been updated to work on new version
• Needs revalidation for some specific certification
• Lazy

Just a minor clarification/correction: the “or later” part also depends on the license per se. There is a GPL-3.0-only and a GPL-3.0-or-later. Usually you’ll find something like “or at your option any later version.” if that is the case, but by default you should expect the GPL-3.0-only to apply.

I genuinly hate NV as a company and their propriatary software, but I can say that the software they provide is decent/good. Like… good cards and software, terrible company and philosophy/moral

they probably made more money from OW1 lootboxes, overall

I really doubt it considering how many boxes you got thrown after you, with coins for dups with which you can just buy skins. Was a great system for the player, but probably terrible monitarily.

The actual reason is to hide the fact they’re probably not gonna have much if any pve content soonish

They literally out right said multiple times that PvE content is mostly shelved and to not expect anything. This isn’t some sort of secret they are keeping

I suspect they skipped checking who controls that domain at the time and just saw that it would make for a good name. Not good practice but I can see how that happened.

https://kbin.social/m/random/p/4648694/To-the-people-who-are-like-What-did-you-expect

Arch: Move more of the things shipped by the distro to /usr/, too many things are still in /etc/, /var/ and /srv/. Generally this isn’t a problem, but when you want to make an A/B updated image where only /usr/ is shipped it is a bit annoying. Also, bash has no way to have a “distro” version of /etc/profile.

Another benefit is: no .pacnew files in /etc/ (or anywhere else) since those would all be managed by the system maintainer and aren’t touched by the package manager