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.

Meanwhile over in Europe - went to the doctor in spring as a cough didn’t go away for ages. As suspected nothing he could do much - irritated throat, and just at the time when cold season was giving way for allergy season. So he prescribed some nose spray - and asked if he should also add some antihistamine to the prescription to save me a few eur (didn’t check, but it probably is single digits. That stuff is cheap)

I personally prefer bzip2 - but it needs to be packed with pbzip, not the regular bzip to generate archives that can be extracted on multiple cores. Not a good option if you have to think about Windows users, though.

Nowadays it matters if you use a compression algorithm that can utilize multiple cores for packing/unpacking larger data. For a multiple GB archive that can be the difference between “I’ll grab a coffee until this is ready” or “I’ll go for lunch and hope it is done when I come back”

Currently my mk4 is printing pretty much 24/7 with IS profiles. I’m applying some lubricant roughly once per week - sometimes I notice the printer starts making strange noises, mostly I notice when rods have zero residue between prints, and just add a bit.

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.

That’s already the friendly variant. Traditional find has a mandatory path as first argument, so to find in the current directory you need to do find .

It also doesn’t know if it really is a path - it just prints that as a likely error. You might just have messed up quoting an argument.

Making an exception for one organisation, pressured by politicians, would be harmful. BBC has the following policy about neutral reporting:

We don’t use loaded words like “evil” or “cowardly”. We don’t talk about “terrorists”. And we’re not the only ones to follow this line. Some of the world’s most respected news organisations have exactly the same policy

Even in this thread I’d rather phrase it explicitly to include everyone - I’ve seen statements like this interpreted by some individuals as “make it welcoming for women at all costs, which may include making it openly hostile for people not meeting my specific definition of woman”, which didn’t have a very pretty end result.

Make sure you’re helping make Lemmy a welcoming place for non-males

I’d phrase that as “make sure you’re helping make Lemmy a welcoming place for everybody”

Being active in a pretty friendly tech scene in the late 90s/early 00s I’ve seen things being ruined for quite a bunch of people who enjoyed being where nobody was judging them for who they were or wanted to be after a bunch of newly joined women decided to try force a bunch of “women only” policies.

Just don’t be dicks to each other, no matter who’s on the other end. And don’t try to force talking about who you are in places where nobody cares - there are specific groups for that.

WoL works as Ethernet¹ broadcast, while Wireguard routes IP, one level above that. So for the purpose of WoL the two ends of the Wireguard tunnel are in two different, not connected networks. In theory you might be able to make it work using subnet directed broadcasts - though creating some means to trigger the WoL packet on where you’re terminating your Wireguard might be easier to manage.

Simple option would be just logging in via SSH to trigger it (you could script that - define a host in your SSH client config that just executes a command on connection), or something like a simple web frontend which will then trigger the WoL event.

¹ it is probably fair to assume nowadays that you’re using Ethernet, and not something like Token Ring. In case you do it still works the same, just the terminology is different.