I broke my #gentoo system again but this time, after going totally nuclear trying to fix it, I find myself with a far faster and stable feeling machine?
Maybe deleting tons of packages and upgrading everything actually had a net-positive impact. Now the idle memory usage is like 1GB and launching applications is literally instantaneous which I find quite impressive.
it was ultimately pretty easy, since im 
with netifrc going, i was finally pointed to by someone in the #gentoo irc to the default config examples for /etc/conf.d/net and with some followup i found out that i just had to symlink the service file for the ens18 device, and then do this:
config_ens18="dhcp 2605:a141:2219:1995::1/64"
(its not exactly a secret, this server is broadcasting an ip address thats kind of the point here lol) and i was able to restart the interface without it kicking me out of the ssh yay! anyway just some #akkoadmin #fediadmin #contabo #gentoo #netifrc #ipv6 tips as i did not find any of the documentation on this straightforward, especially since netifrc isn’t as in vogue as whatever systemd-based hunks of junk everyone is running now
One would think I would learn one day. But seemingly, it still takes me a while to search for the failure in myself when I look for a bug on a failed Gentoo kernel build and don't find any.
Today's variant: Answering "n" to a question for a file path in "make oldconfig" while running a kernel update and desperately trying to figure out why Make is looking for a target called "n" in the kernel's build. 🤦
#3GoodThings @3goodthings
Three good things today.
1. I managed to get the Guest Room (aka My Studio ) ready for my brother. Also put Useful Labels on the different kinds of rubbish bins, for his enlightenment.
2. Started the (slow):process of installing #Gentoo #Linux on my graphics machine.
3. My brother arrived safely.
I've filed a report about a minor problem with a #Python package, namely that the source distribution contained some trailing junk that breaks GNU #tar. On one hand, I'm happy that upstream took the issue seriously. On the other hand, I'm terrified of how much #AI slop was involved in the response.
I mean, my short bug report yielded a few walls of text of #LLM analysis of what the cause of the problem might be, of suggested solutions… and praise of the author's fix. These are interspersed with short comments from the author, all pasted under their own personal account. And the linked pull request is also huge, with "verification code" that's quite sloppy (bits that don't do anything, conditions that will never be true… but at least it seems to do what it was supposed to do).
Honestly, I don't know what to do. Not that I ever planned using this package, but at this point I will definitely stay away from it. It's in #Gentoo, and I'll have to continue maintaining it for the sake of reverse dependencies, but I feel like it's unfair to expose our users to packages that have clearly proven to accept AI slop without reviewing it properly. Or rather, AI slop that's being reviewed… by AI. How can anyone think this a good idea?!
There were multiple times in my life when I've considered retiring from Gentoo, for variety of reasons. There were also multiple times when I wanted to get away from computers altogether. Unfortunately, we're living in a truly fucked up world, and there is no escape. The best you can do is put an ever increasing effort to keep fixing all that crap that will just keep piling on faster and faster.
I finally installed Gentoo ! I don't know how much time will I keep it but, for the moment, it's very fun !
noodleJS 🏳️🌈
arisut 
🎸
Nick (Alatar the Blue)
anna, a criticality incident at the gender accelerator
Michael
Jezus Michał 🏔 (on)
Jesus Michał 🏔 (he)
Kerr Avonsen (she/her)
martinzerty