A former Wagner mercenary in July told Euronews that while he served in Ukraine one of his main duties was to ensure Russian conscripts - “barely 21-years-old” - would not run away, as they were so reluctant to fight.

Doesn’t this compare apples to oranges?

One is an aggressive war. People are shipped into Randomiskan without clear indication what’s going on, why they should be there and they are supposed to die for the glory of the state. Sorry, but that’s when everyone wants to run. That’s also distinctively different from WW2, when concrete evidence of mass murder in occupied europe was available.

The other would be a defensive war. An outside aggressor wants to wipe out your culture and accepts killing or deporting anyone you consider important in your life. Putting it like that, WW2 was very much a defensive war from the allied side. That’s a very different motivation.

The thing is, I don’t have an answer to all of these questions.

On the other hand, I know pagan bands with songs about “Killing all the christian heathens coming to colonize scandinavia”. About “Crushing the roman christians coming to take germanic women with their fairy tales of a weak god”. (BTW, this is explicitly not about german nationalism. There are nazis abusing these terms of skandinavian/germanic origins, many of them, but this isn’t part of that). Those are what I meant when I said: I’m not sure if I want to discuss those with a christian I don’t necessarily trust. Because face it, norse mythology was colonized by roman christians. maybe for good, maybe not, I don’t know.

And in another direction, a lot of metal / heavy metal / rock imagery is based around pushing and prodding and poking christians. Not just subtly. They thrived on this to establish themself as counter-culture. “You are Christians. We are sons of satan. We listen to the other music.” For those, I can very much find a foundation in christian religion. Like, look at denmark. Burning a stack of paper shouldn’t be a big thing, but now they are creating laws against burning the Koran. Not sure how I feel about this.

In that light, I’d very much be in favor of a school uniform, or a specification of unicolor shirts / t-shirts without imagery, I have to say. Concessions are bound to be abused in every way, with that hat on.

The sad thing to me personally is: IMO, we should embrace diversity. Someone wearing a weird cloth on top of their hair should be a source of curiosity. It should be an exposure to something new and an option to grow and reflect and to learn they are just a person, just a bit different. Like the first time you try to cook for a vegetarian, a vegan, or try to date a lesbian.

Hm. Not sure about school, because I have little reason to go there. But I certainly have shirts that are work or grandma unfriendly, or that I would only wear around devote christians I trust. With that, I wouldn’t be opposed with a ban for shirts that are created to offend specific religions. It’s a different side of a very similar coin.

I mean to a certain degree, I can understand if people find a problem with Poetterings approach of doing things !CORRECTLY!. Like, systemd-resolved resolving A-records with multiple addresses ina deterministic fashion because it’s not defined not to be deterministic, and because actual load balancing would be better. It’s not wrong, but it’s breaking everything. And it got patched after some uproar. And there are a few things like that.

But at the same time - I don’t think people appreciate how hard doing process management right on linux can be, especially if the daemon to run is shitty. Like, init scripts just triggering the shutdown port on a tomcat - except the tomcat is stuck and not reacting to the normal shutdown port and now you have a zombie process and an init script in a fucked up state. Or, just killing the main process and for some reason not really removing the children, now there’s zombies all over the place. Or, not trying appropriate shutdown procedures first and just killing things, “because it’s easier” - except my day just got harder with a corrupt dataset. Or, just trying soft and “Pwease wexit Mr Pwocess” signals and then just giving up. Or having “start” just crash because there was a stale PID from an OOM killed process around. Man I’m getting anxiety just thinking about this.

And that’s just talking about ExecStart and ExecStop, pretty much, which I have done somewhat correct in a few init scripts back in the day (over months of iteration of edge cases). Now start thinking about the security features systemd-analyze can tell you about, like namespaces, unmapping syscalls, masking parts of the filesystem, … imagine doing that with the jankyness of the average init.d script. At that point I’d start thinking about rebooting systems instead of trying to restart services, honestly.

And similarly, I’m growing fond of things like systemd-networkd, systemd-timesyncd. I’ve had to try to manage NetworkManager automatically and jeez… Or just directly handling networking with network-scripts. Always a pleasure. Chucking a bunch of pretty readable ini-files into /etc/systemd/networkd is a blessing. They are even readable even to people rather faint on the networking heart.

And even password based disk encryption can be defeated with 2-3 physical accesses if an organization wants to hard enough. Keyloggers can be very, very sneaky.

At that point you’d have to roll something like Yubikey-based disk encryption to be safe, because this re-establishes control over some physical parts of the system. Until they find the backup Yubikey you had to not lose all data by losing the primary key you’re carrying around to maintain control over it.

It’s not a battle the defending side can win.

Wow. I’m not particularly sensitive, but that seems like the right amount of very bright strobe that gives me headaches in concerts, especially at night in the dark. That’s very much the level of trying to find out a way to get to the roof to unplug it.

And that skeleton of a system becomes easier to test.

I don’t need to test ~80 - 100 different in-house applications on whatever many different versions of java, python, .net and so on.

I rather end up with 12 different classes of systems. My integration tests on a buildserver can check these thoroughly every night against multiple versions of the OS. And if the integration tests are green, I can be 95 - 99% sure things will work right. The dev and testing environments will figure out the rest if something wonky is going on with docker and new kernels.

Entirely true.

I’m currently working on a little project that’s interesting to me (a low-spoiler walkthrough system for adventure games) and after a lot of back and forth, I decided to cut all of JS out of the picture. Just get rid of all of it, and do good old 90s server-side rendered HTML with modern CSS placed on top of it.

And that’s, honestly, a joy. The first draft of a page looks like the first screenshot, then you add some semantic classes to the html and throw some simple CSS at it and it looks acceptably neat. And I could get rid of so much janky toolchain I just fail to understand.

I just enjoy the scene of the oldtimers strutting in like true chads and showing the youngsters how to take care of the big lady. It’s so wonderfully corny. And it’s such wonderful bullshit, and when you learn how many hands were necessary to run such a ship, it’s even more fun.