You have to have an idea of what you’ll run on it first.

Old corporate desktops will do for a NAS and basic light services. Look for one that has three drive bays plus an NVMe slot.

Bit fields are a necessity in low level networking too.

They’re incredibly useful, I wish more people made use of them.

I remember I interned at a startup programming microcontrollers once and created a few bitfields to deal with something. Then the lead engineer went ahead and changed them to masked ints. Because. The most aggravating thing is that an int size isn’t consistent across platforms, so if they were ever to change platforms to a different word length, they’d be fucked as their code was full of platform specific shenanigans like that.

/rant

Talking heads - once in a lifetime

And you may ask yourself: where is my beautiful house? Where is my beautiful wife?

In the industrial automation world and most of the IT industry, data is aligned to the nearest word. Depending on architecture, that’s usually either 16, 32, or 64 bits. And that’s the space a single Boolean takes.

QNX 6 had a public beta some years ago. It breathed new life on a very old 486 I had laying around.

QNX 4 was also used on some fancy life signs monitors and other safety / mission critical equipment.

Well done! Protip: You can use double new lines to format paragraphs. And full-stops.

No clue, but they could use nice.

Happens.

I’m afraid you answered the wrong comment.

At the workplace?

Great talk indeed. And I will quickly acknowledge that something had to be done, and that systemd had the courage to innovate and address the issues. I just wish it did so in a more transparent way to the end user.

For instance: there’s a whole established system of dealing with logs in place. Why build a separate one just for your init system? Why binary? Why even integrate it with your init? I’m not saying storing everything on /var/log and using logrotate is ideal or even covers all use cases. But a log management system is its own thing.

That’s just an example of how systemd didn’t jive with every other subsystem in a Unix like OS. It could have been done in a Unix way - small cohesive tools that are good at one job and can be combined to do more together.

That’s where I think he missed the mark when dismissing the monolithic criticism by saying “it’s not a single binary so it’s not monolithic”. Its philosophy is monolithic.

That said, I use systemd on my machines because that’s what my do uses and I don’t think it’s a reason to swap distros. For the same reason I use Linux and not a micro kernel. I.e. philosophy is important, but implementation is importanter.

So that’s the story. SystemD feels very Microsofty, though. A big, opinionated, monolith.

Wasn’t the systemd dude a Microsoft employee or something?

Epic?

I started with floppies too, when I bought my copy of Conectiva Linux 3.0. It came with a hefty manual that was instrumental for a newbie like me.

Borg is amazing but I don’t think it’s a good fit for your case.

That would regio explain with there are so few matrix servers out there compared to Lemmy or Mastodon.

How? Why? I can’t even

I don’t want to search this… Wth is it?