Some #NetBSD questions that keep coming up.

We don't use modules for HW drivers in the default install. All baked into the kernel. If you're curious about desktop hardware, for x86 there are lists https://wiki.netbsd.org/laptops/ https://wiki.netbsd.org/gpus/ (and the pci/usb manual pages)

x86 virtual machines. https://www.netbsd.org/docs/guide/en/chap-virt.html#chap-virt-guest

For disk encryption there's different options, such as creating a small root with the installer, then adding encrypted partitions later (see man cgdconfig). Also: cgdroot.

I created a thing because I'm tired of having to look this stuff up every time I open an editor on a new machine or new install. I always end up fighting with it instead of just trying to find the setting, because it's always called something different ("close braces", "brace completion", "insert closing ] } )", etc.")

Now I have a place to look it up every time, with an easy to remember URL!

https://fuckautobraces.com/

I found my drawing tablet and I'm not afraid to use it

IPv6

@ShadowJonathan I also have plans for world domination but it falls flat because I discovered that falling asleep is a much easier task and at least as satisfying

Potos chimistes, j'avoue humblement que je sèche.
Edit : Ok le 2e est le THC :p

#Mood

Ok, looks like this is the week of funny experiences.

Customer: "I had an AI check our server and it says the SSH port is open and that's not very secure."

Me: "Yes, you asked us to open it so you could access the server via SFTP (actually, you wanted FTP, but we discussed it a bit and found this compromise). Don't worry, it's only accessible from your IP and you land in a dedicated FreeBSD jail. From there, you can only access the 'exchange' directory on your server, where you can upload and download files without affecting the application."

(NB: I had suggested a VPN, but they declined because it was too complicated.)

Customer: "Yes, but maybe it's still insecure. Can't we close it?"

Me: "No, unless you want to lose access to that directory."

Customer: "Ok, thanks."

One hour later:

Customer: "Hi, I think we've found a solution. We've just created an app (!!!) with AI that lets us access the files anyway, but more securely than SSH (!!!). Can we install that and close SSH? Oh, and not in the dedicated jail, but directly in the application's jail, because it needs access to the application's files."

Me: "Frankly, I trust SSH in a dedicated jail, restricted by the firewall, a lot more. I don't think this is a good idea."

Customer: "Ok, thanks."

Half an hour later:

Customer: "Ok, now it's secure. I had another AI check it and it found some security issues, but it fixed them all. Can you install it and disable SSH?"

Me: "I strongly advise against it. I can see problems coming."

Customer: "Ok, thanks."

One hour later, my phone rings.

Their internal IT guy (who has access to the machine, which, after all, belongs to them) had given the AI the login credentials to go ahead with the operation.

Except the AI had managed to lock itself out via the firewall, without even starting the app. And now they couldn't get back in.

Fortunately, I had my own access, via VPN, to a separate jail that the AI hadn't touched (or even considered).

Customer: "SORRYSORRYSORRYSORRYSORRY! From now on, we do things your way."

Well, at least it ended well.

PS: The customer knows I'm sharing this story and agreed to it.

#IT #SysAdmin

RE: https://hachyderm.io/@rain/117446083340236126

This is why, when people say things like "omg the LLM can generate an embedded kernel for me!!!" I can't help but think

"Yeah, it was trained on _at least_ three of mine, plus immeasurable training load on my webserver serving the docs."

By claiming ownership of the result, or even just claiming to have managed the machine while it spit it out, you're basically just stripping all attribution for the actual work that went into its inputs. You might as well just clone my repo, remove the license, and remove my name. So no, I am not impressed.

Anyway, Anthropic just ripped off a bunch of Rain's work with no attribution, as they do.

# grep -E -e $'GET /git/[^\t]*/(commit|file)/[^\t]*\t200\t' /var/log/syslog/NightmareMoon/local7_nginx/2026/10/1* | wc -l
11
# grep -E -e $'GET /git/[^\t]*/(commit|file)/[^\t]*\t401\t' /var/log/syslog/NightmareMoon/local7_nginx/2026/10/1* | wc -l
283712

Daang.

@rysiek

#IA
En réponse à un collègue:
"Je vais être franc:
Je n'arrive pas à me réjouir d'une techno qui pille le travail de tous les créateurs/travailleurs, écroule des millions de sites web, ruine la planète en consommant des quantité affreuses d'énergie, exploite des travailleurs sous-payés pour l'améliorer, provoque le burnout de plein de développeurs/mainteneurs, donne encore plus de pouvoir à des milliardaires fachos, et va ruiner plein de gens en provoquant une crise économique majeure."

+       case TELSE:
+               ppelse();
                break;
        case TIFN


Sent with Proton Mail secure email.DEF:
-               error(&tok.loc, "#ifndef directive is not implemented");
+               scan(&tok);

Commercial email providers never fail to be ridiculous.