I’m not sure if you’re joking or not, but the behavior of journald is fairly dynamic and can be configured to an obnoxious degree, including compression and sealing.

By default, the size limit is 4GB:

SystemMaxUse= and RuntimeMaxUse= control how much disk space the journal may use up at most. SystemKeepFree= and RuntimeKeepFree= control how much disk space systemd-journald shall leave free for other uses. systemd-journald will respect both limits and use the smaller of the two values.

The first pair defaults to 10% and the second to 15% of the size of the respective file system, but each value is capped to 4G.

That’s a BSOD for DRM failures I think, not a generic BSOD like on Windows.

What? I thought Nvidia didn’t want to mainline the open driver??

Edit: Grrrr, clickbait. This is not about their open driver but as far as I understood about exposing a more minimal driver for vGPU usage, in light of development of Nova, a Rust based nouveau successor.

Are we really going to start this pointless discussion again? They are two licenses with different use cases and different considerations. GPL has a lot more mental overhead to using it, MIT is hands off, both of these aren’t inherently invalid.

Also Tanenbaum in your own link mentions that Intel probably would have just written their own microkernel if need be.

You need to wander through links a bit to find it but https://ofourdan.blogspot.com/2023/10/xwayland-rootful-part1.html talks about the rootful and the recent changes.

Blame the Mastodon team, if you’re not running a fork, you have to go into the source and adjust the character limit manually.

Nobody has to do it like this, Mastodon supports longer posts since other servers and clients support more, it’s seemingly just a choice from upstream.

Essentially functionally stripped sudo, smaller in size than sudo. See also Pottering’s thoughts about the ecosystem

Holy shit the comments on this one are vile. If you don’t like the article, don’t read it and go on with your day.

The footer of the blog shows a Nix file structure, skimming their blog they wrote a bunch of articles and guides for Nix, checking their repo they have a bunch of Nix work, they’re not exactly a nobody (if you couldn’t judge from the people saying they’ll miss them on the Nix forum post)

This entire article is an extension of https://save-nix-together.org which is the actual thing that sparked the the gasoline covered Nix community, this will probably seem more coherent with that background.

What I said especially applies for single GPU passthrough, minus the two GPU part, I say that because I’ve done that on Desktop.

Single GPU passthrough (for me) was a journey of misery where a series of bash scripts with crude busyloop synchronization kept me from having no display output and needing to restart my system to test my changes again.

It’s probably the last thing I’d recommend for someone who wants something that works, unless you know something I don’t.

GPU passthrough requires two GPUs, a system with compatible components, a lot of caffeine and a lot of patience. Not something for someone who wants something that just works.