Seems like dinosaur, isn’t: https://i.ebayimg.com/images/g/TGwAAOSw9mFWHRS~/s-l400.jpg

If they have to change the names of things, Xfce users are probably fine with taking it one letter at a time.

It’s fucking systemd again isn’t it

Poor Nvidia… the AI bubble is going to burst, the gamer market has all kinds of reasons to hate them now, and all they’ll have to console themselves with is several trillion dollars.

Okay I’m not surprised that C and Rust are popular, but I didn’t expect there to be so much Vala in there.

Device drivers are not like other software in at least one important way: They have access to and depend on kernel internals which are not visible to applications, and they need to be rebuilt when those change. Something as huge and complicated as a GPU driver depends on quite a lot of them. The kernel does not provide a stable binary interface for drivers so they will frequently need to be recompiled to work with new versions of linux, and then less frequently the source code also needs modification as things are changed, added to, and improved.

This is not unique to Linux, it’s pretty normal. But it is a deliberate choice that its developers made, and people generally seem to think it was a good one.

Nouveau might be good enough by now for most games that will run on a 1060, maybe worth a try.

The driver needs to interface with the OS kernel which does change, so the driver needs updates. The old Nvidia driver is not open source or free software, so nobody other than Nvidia themselves can practically or legally do it. Nvidia could of course change that if they don’t want to do even the bare minimum of maintenance.

They started 9 years ago, but they remained popular into 2020 and according to wikipedia the last new pascal model was released in 2022. The 1080 and the 1060 are both still pretty high up on the Steam list of the most common GPUs.

Those are the GPUs they were selling — and a whole lot of people were buying — until about five years ago. Not something you’d expect to suddenly be unsupported. I guess Nvidia must be going broke or something, they can’t even afford to maintain their driver software any more.

… but it helps.

One of the things I immediately liked about cargo is that (so far as I’ve seen thus far) the source is already there, without vendoring, in ~/.cargo/registry. In Debian, to get the source it’s apt-get source $package and as an end user it’s super easy to build things from those source packages if you want to.

Yeah, the personal risk doesn’t worry me as much as the idea that it might eventually get to be as bad as npm.

I did not mean to suggest that crates.io is “bad”. It’s obviously quite useful. It’s just that I would like it better if there were some kind of systematic review of newly submitted packages by someone other than their authors, and I would like rust better if its standard library included a random number generator.

I would suggest that Debian is quite good, and is indeed something special, but that’s another story.

Trusting an organization because it has a long track record of being trustworthy is “invalid”? You guys are pretty weird.

I got the compiler and whatever comes with it from the debian package manager, which has existed for much longer than has crates.io and has had fewer malicious packages get into it.

i3c updates RTC updates bpf updates gfs2 updates configfs updates MM updates non-MM updates more MM updates misc updates

In total 183 “updates” for all the things. It seems to me that in times past these summaries normally gave us slightly better descriptions of what had changed.

If it was something like “our policy is to use AI where it’s useful, so we’ve used it to reformat all the documentation” that wouldn’t worry me. Going “AI first” for “faster innovation” to “unlock the next stage of rsyslog’s evolution” is just not what I’m looking for in a logging daemon.

At least for my home network I’m going to just go with plain old GNU syslogd.

Anyone else suddenly wondering what other syslog implementations are available? Apparently the big one at the moment is syslog-ng.

$ uname -srv Linux 6.18.0-kbal #111 SMP PREEMPT Mon Dec 1 10:26:08 EST 2025

Ah yes that’s all fine but the real secret is the meaning of that #111. (I only thought to find out a couple days ago — apparently I’ve done 111 kernel builds on this machine.)