aard

Did pretty much the same with a new server recently - spent ages debugging why it didn’t find the SAS disks. Turns out, disks like to have power connected, and no amount of debugging on software level will help you.

I was referring to work setups with the overengineering - if I had a cent for every time I had to argue with somebody at work to not make things more complex than we actually need I’d have retired a long time ago.

Unless you are gunning for a job in infrastructure you don’t need to go into kubernetes or terraform or anything like that,

Even then knowing when not to use k8s or similar things is often more valuable than having deep knowledge of those - a lot of stuff where I see k8s or similar stuff used doesn’t have the uptime requirements to warrant the complexity. If I have something that just should be up during working hours, and have reliable monitoring plus the ability to re-deploy it via ansible within 10 minutes if it goes poof maybe putting a few additional layers that can blow up in between isn’t the best idea.

Everything is deployed via ansible - including nameservices. So I already have the description of my infra in ansible, and rest is just a matter of writing scripts to pull it in a more readable form, and maybe add a few comment labels that also get extracted for easily forgettable admin URLs.

Shitty companies did it like that back then - and shitty companies still don’t properly utilize what easy tools they have available for controlled deployment nowayads. So nothing really changed, just that the amount of people (and with that, amount of morons) skyrocketed.

I had automated builds out of CVS with deployment to staging, and option to deploy to production after tests over 15 years ago.

I nowadays manage my private stuff with the ansible scripts I develop for work - so mostly my own stuff is a development environment for work, and therefore doesn’t need to be done on private time.

One thing I like about bluesky is that your identity doesn’t have to be tied to an instance domain - you’d still have issues if you want to change is later, but if you plan ahead and use your domain you can just move it between instances.

A lot of the Zen based APUs don’t support ECC. The next thing is if it supports registered or unregistered modules - everything up to threadripper is unregistered (though I think some of the pro parts are registered), Epycs are registered.

That makes a huge difference in how much RAM you can add, and how much you pay for it.

Funny timing, I’m currently going through a stack of Sun hardware in my garage to decide what to keep, and for what I’ll try to find a good home (or eventually dispose of it).

It has been a while since I touched ssmtp, so take what I’m saying with a grain of salt.

Problem with ssmtp and related when I was testing it was its behaviour in error conditions - due to a lack of any kind of spool it doesn’t fail very gracefully, and if the sending software doesn’t expect it and implement a spool itself (which it typically doesn’t have a reason to, as pretty much the only situation where something like sendmail would fail is a situation where it also wouldn’t be able to write a spool) this can very easily lead to loss of mails.

I already had a working SMTP client capable of fishing mails out of a Maildir at that point, so I ended up just doing a simple sendmail program throwing whatever it receives into a Maildir, and a cronjob to send this forward. This might be the most minimalistic setup for reliably sending out mail (and I’m using it an all my computers behind Emacs to do so) - but it is badly documented, so if you don’t care about reliability postfix might be a better choice, or if you don’t just go with ssmtp or similar. Or if you do want to dig into that message me, and I’ll help making things more user friendly.

A problem of this bubble is that it is making AI synonymous with LLM - and when it goes down will burn other more sensibly forms of AI.

It surely is a bubble - so probably a bit different than many other bubbles.

I think OpenAI made the right call (for them) to commercialize when they did - as that pretty much was their only chance to do so. Things has moved fast over the last 1.5 years - and what used to take a decade in tech has happened within months: OpenAI is the dinosaur company grandfathered in, while for already about a year it’s been more sensible for anybody wanting to do something with LLM to selfhost (or buy hosting capacity, but put up own data) one of the more open language models, and possibly adjust or re-train it.

As a company owner I get a ridiculous amount of spam for a year already from all kinds of companies building products on top of OpenAI stack, or are trying to sell training or conferences. All those companies will be left with nothing once all the slower users realize technology has moved on. It’s like somebody trying to build all their product offerings based on VMWare stack nowadays.

If you as a company want to offer something around AI right now the safest option is probably offering hosting, or if you want to do more hands on, adjustment of open models. Both of those are very risky, and many will go bust in years to come - but not as suicidal as building on top of a closed dinosaur.

All my software can be configured using dedicated configuration files (.c)

Because it does JBOD if the controller supports it. Pretty much none of the controllers you’ll find in consumer hardware support that.

JBOD relies on an optional SATA extension, which most of your controllers won’t have.

That leaves you with RAID in the controller - which is a bad idea, as you don’t have much control over what is going on, and recovery if it fails will possibly messy.

I nowadays typically have three outcomes to similare situations:

• I find my own question without solution from a while ago
• I find my own comment or blog entry describing how to fix it
• I find a friends comment or blog entry on how to fix it

You still might want to do something like alias pbtar='tar --use-compress-prog=pbzip2 to easily use pbzip2 - unless you have an ancient system that’ll speed things up significantly. And even if you don’t it’d be nice to use it for creation - to utilize more than one core the archive needs to be created for parallel extraction.

They used to link to my dig wrapper on my homepage for having their clients debug DNS problems for many years - even with translations of my UI in the various language help sites. I always found it amusing that a hoster of their size does that, instead of spending a lunchbreak to throw something together that integrates with their help page.

There also was a non significant number of users which didn’t understand that my homepage had nothing to do with OVH, and ended up mailing me about their DNS problems.

His first colony will be a death trap.

That’s a feature, not a bug. His family got rich with mines in south africa, exploiting the locals. For getting more rich by mining mars you’ll have to bring your own locals to exploit, and there’s no need to make it to comfortable for them.