notabot

The joys of distributed algorithms. You can now get more errors, more quickly than before!

I remember writing a chat system in assembler, for DOS, using, IIRC, IPX networking. When it went wrong, one or more machines would just freeze, with the string “NETWORK ABEND” in the middle of the screen.

I should fork vim and call it ‘death’, so I can shout “give me vim or give me death!” any time someone suggests a different editor.

That has unironicaly made me nostalgic for the days when the web was a place of experimentation, joy and just a bit of crazy.

They’re publishing articles that are completely false, which suggests failures are the writing and editorial levels, whether or nit they use an LLM. It’s going to take a lot of high quality, accurate, articles to regain my trust.

It looks like the article was AI, it’s been pulled from the site.

Blast. This sounded like really positive news, linux as an ecosystem desperately needs to revisit its init process choices, but there really doesn’t seem to be any hint of it elsewhere. There is a rye that’s written in rust and which has an init command rye init. I wonder if it’s a case of an LLM latching on to that and just making up the rest?

If you are just a user, in that a computer is just a tool you use, then you’re right, there’s comparatively little reason to be concerened or even know about the underlying details of the system. If you go further and start making changes to your system, or even building more complex systems, over time you will find yourself forming quite firm opinions about various parts of the underlying system, especially if you’ve had experience with other options.

Honestly, I’m not sure, I was looking at Devuan, but then noticed that Debian supported sysvinit natively so I went that route instead. I figure that sticking to the source distro was going to give me fewer headaches, and so far it’s been plain sailing.

Debian, installed without systemd as per the wiki. So far I’ve not hit any issues, whilst I’ve recently ended up diving through both kernel and systemd code to find the root cause of an issue I was hitting on one server. I could have just bodged past it, but I wanted to actually understand what the issue was, and what else it was going to affect.