To be fair, a lot of server distros have systemd. So, maybe Alpine since it has OpenRC? However it has musl instead of glibc so that might be a problem depending of your use case.

Though cannot think of anything really, breaking after reboot says it's most likely software related. But why would that happen, no idea.

Integrity verification and immutability doesn't need to be implemented through attestation. Attestation is a horrible concept used by companies to dictate you what you can and what you can not use on your hardware.

Attestation has nothing to do with security.

First, because attestation doesn't enforce any security standards by default, it just requires an "official" hardware-software stack. It may be used for such enforcement, but no one gives a shit, including Google with their Play Integrity Protection that allows immensely outdated devices to be accepted as "secure".

Second, because one leaked key, and all the devices signed with that key immediately become a security circus. Yes, eMudhra way.

Banking software

Banking software is an absolutely horrible thing both security-wise and privacy-wise. Having it on Linux is exactly the opposite of what Linux needs.

Do we have a choice?

Yes. Do not use anti-consumer tech. Do not use services that require such anti-consumer tech. Demand from your banks and your government support for open technologies and standards (literally W3C-compliant web browsers are enough for practically anything).

I do realize that it's extremely difficult and barely possible at all. But bringing that crap to open ecosystems is not the answer.

Does it have easy LUKS BTRFS + snapshots setup?

That is somehow really hard on Debian

I tried debain server and ubuntu server. Same issues with both. You have any suggestions?

But not right after the fresh installation? May sound weird but have you tried a different distro or a different init system? Might worth to explore.

I replaced the empty CMOS battery and tested the RAM and it still just goes down after a couple days

Hmm, maybe it has a bad RAM. Have you tried memtest86 on it?

I bought them a long time ago, and always refused to pay scalper prices. My Zero 2Ws were all $15, most of the others are Pi4 and Pi5 from before the RAM inflation.

Power is nice and stable in this arrangement, a bunch of the RasPi foundation supply bricks on a power strip mounted to the breeze-tunnel.

I've been a NUC fan since forever, but last year I had two NUCs that I bought in 2020 die within a month of each other, one had a power supply issue and I think the other one had a worn out SSD - it was working fine when I unplugged it, but when I plugged it back in 6 weeks later it wouldn't boot.

Like I said, one old / low power NUC could do this, but when it dies far too much of our smart home goes dumb all at once.

I tried it once and didn't care for it. Opinionated distros are really not my thing.

Intel Quick sync is exactly the reason I got a NUC running an Intel as opposed to AMD.

4 Raspberry Pi's

Get a load of this cat flexing their wealth :D

The isolation of services makes some sense, but I found that there was plenty of single points of failure anyway (power, internet, router, pihole), so not worth worrying about a few more. And the reliability of the nuc has mostly given me peace of mind. I do have a separate nuc for a NAS, though.

Another thing LLM agents are good at is reading log files and giving you clues as to what just went sideways, when that includes a system restart it's nice to be able to look back acrosss the logs of the past several cycles.

just try to build a module with clang for a kernel build with GCC

I did just now, and it worked fine.

I guess it would be better with MySQL. MSSQL is generally on the heavy side. Though, haven't tried before but theoretically it should be possible to install LAMP with SQLite instead of MySQL. It can be actually fine on a hardware like this.

Nice. I got 2 thin hp pro/elitedesks. One to run my MC servers and one for other homelab stuff though that one keeps fucking crashing/turning off and I cannot fucking figure out why. It only ever runs fine after installing the OS if you ever rebolt it it will just not stay on for more than a couple days.

If you're not doing a lot of writes, log2ram might be good enough and isn't that hard to set up

Used mssql-server at work where we usually use windows and its a bit shit if you want low memory hosting. Though when I have run MySQL I haven't tested low resource systems to compare that either tbh.

It's awesome. It's like opensuse aeon but more popular. I haven't touched my os in years.

Technically you're right. Apache can run on pretty much anything. Though when I say Apache, my mind shifts to LAMP immediately. Sorry about that. However LAMP can run on this too but the performance wouldn't be good I assume.

Honest question: apart from Tuxedo hardware support, what would be the reason to use Tuxedo OS specifically? There are plenty of beginner frientdly distributions out there. I liked Tuxedo quite well, but it's basically a pretty Kubuntu with specific hardware support.

In my case, I had swap space on the SD card, and suspect that's what killed it. After replacing the card and disabling swap, I haven't had any problems for the last couple years

Because people who use it apparently aren't interested in talking about it more?

is it anything special compared to normal debian?

They (fs2ram and similar) are annoyingly, frustratingly fiddly and not worth the effort IMO... until I got Claude to do the fiddly bits for me... It isn't just the initial setup, it's also the additional hoops you have to go through whenever you want to change something on the "protected" partition. Fiddly is the word for it, not hard, but time and brain-power consuming.

I've got a box I made with a air filter and 200mm fan on one end, then it blows through a "tunnel" that has a network switch and 4 Raspberry Pis inside, one runs Frigate with an AI hat, another runs home assistant, another is running my Pi Hole, another is basically a NAS with a 2TB external USB drive, and they do a whole bunch of other miscellaneous ad-hoc tasks. The clean airflow keeps them cool just sitting there with open PCBs and the normal little heat sinks, they're all wired to the switch so only 1 ethernet cable comes out.

On the one hand, a single Core i3 PC could probably handle ALL the tasks easily enough, but... what about when Frigate goes weird? I don't want my whole home DNS/DHCP and home automation to go with it. Same for everything else, and if one of the microSD cards goes bad (none have yet after over 1000 days of 24 hour continuous operation except during power outages) - that's just one thing going bad, not EVERYTHING.

I must admit the 2TB external drive is cheap junk, and those things do "wear out" - even internal SSDs go bad over time, I've had it happen at work more than once within about 5 years of normal use. I try to get the better microSD cards for the Pis and so far they're not having problems for me.

One thing you can look into if you like messing around with system configurations is partitioning your microSD with "immutable" partitions where any changes are written in RAM (yes, RAM heavy Pis are even more expensive than they used to be, but it all depends on your application...) I do this for my Pis that run around in the world and get their power cut off without warning - failures are so rare in the first place it's hard to know if all the partition work is worth the effort, but so far I've never had a corrupt file system with the immutable partitions carefully configured, and I have had several before I started doing that - not failed SD cards, just corrupt filesystems that needed to be re-formatted.