Reading Linux news is increasingly like getting Facebook updates from a family member who joined a cult and subsequently broke off contact
2 Boosts
0 Likes
@mcc What is this supposed to mean? Was the headline generated by a Markov chain?
@jackemled We may never know.
@mcc “oh yes, we don’t open that door anymore, after The Beast came…”
@mcc I was gonna ask if it has ribs in its mouth, but then I remembered most of y'all didn't grow up in actual cults and won't get the reference, and my childhood religion was the socialization injury that keeps on giving.
EDIT: in a moment that isn't at all shocking in hindsight, the ribaholic beast has SO much AI art of it in an image search these days, and I don't want to subject anyone to that, so have this old, low-res image with Comic Sans, which is comparatively innocent and charming in its naive, bygone aesthetic. I probably blocked out seeing this on my Facebook in like 2011.
@mcc
crazy beast?
@vgarzareyna i have no idea
@mcc Will we finally get the year or the FreeBSD desktop?
@wildrose i think we might be about to get the year of the freebsd desktop
@mcc @wildrose We really need FreeBSD to be the new Steam Deck 2 so Valve the company makes a Proton for FreeBSD 😂
But yeah, there is the Linux compatibility layer (which acts like Proton for Linux programs) for FreeBSD, but layering that with Proton is asking for delay and a lot of compatibility problems unlike having just one compatibility layer.
@XavianFox @mcc @wildrose Unfortunately FreeBSD is as bad as Linux about LLMs. I'm pretty sure every other BSD except Mac OS is fine though.
@jackemled @mcc @wildrose oh really? That's too bad. I guess no one can actually be happy with any OS 😂
We honestly just need a good and strong no AI kernel, like what Linux was before AI. Or replace it with a no AI BSD kernel or wait for the GNU Hurd kernel to finish (likely being extremely unstable when it is finished).
The GNU project is cool, but they only shine in user space. Kernel and BIOS development, they just suck at it due to lack of resources, people, and poor architectural design.
@dpflug @jackemled @mcc @wildrose I've noticed that, but isn't that whole operating system built on Rust? I don't like Rust very much as a preference.
@XavianFox @dpflug @mcc @wildrose Rust is horrible unless the developer has already built binaries for a release. It's ridiculous that you have to have a complete development environment just for the compiler to work instead of the compiler being standalone except for maybe some libraries.
@jackemled @XavianFox @dpflug Redox isn't self-hosting yet. You are not terribly likely to be building the kernel yourself, and if you are, you aren't building it on Redox. I don't understand what you mean by "a complete development environment".
@mcc @XavianFox @dpflug I don't remember exactly how it worked last time I touched Rust because it was a long time ago & the documentation is really really bad. You had to have a compiler, a package manager specific to Rust, & like five other things for any of it to work & it was a whole special system that you had to have to develop Rust programs. You can't just install the compiler & use the makefile in a git repository like you can with other languages.
@jackemled @XavianFox @dpflug Similar to how C needs a build system (Make), Rust needs a build system. If you think Make is an inherent property of operating systems I'd suggest you maybe have not experienced how hard a Makefile based project can be to build on Microsoft Windows.
You additionally need the package manager because the software may use packages and they have to come from somewhere.
You *could* invoke rustc by itself from a Makefile, but you would not have fun doing so.
@mcc I couldn't find a "Crazy Beast" on itch.io or steam. Gamers, you know what to do.
@mcc you can download and install Crazy Beast from source or using Snap or Flatpak packages.
@mcc Ok, so reading the article, it seems that some LLM software was using a kernel debugging interface (bind/unbind in sysfs) to change which driver was controlling a device out from under it. The kernel developers were tired of getting bug reports that were caused by this, so they made the kernel flag itself as tainted until the next reboot if this interface was ever used.
And then they discovered that that same interface is how VM GPU passthrough works and they had to revert it.
New Linux 7.4 Feature For Reducing AI Noise Already Reverted Due To A "Crazy Beast"