6 karma · joined June 23, 2019
for previous data I can't bear to go less than raid 6 (equiv). And require ECC ram. I've had several events where after one drive failed, I discovered minor errors on a second drive...
Currently kernel raid can't use raid 6 to decide a majority win if a bit error is discovered. MD-integrity seems to cost a fair bit of performance (relative to zfs). So I like either plain LVM+raid 6 or also add an integrity option if I want to defend against bit rot.
It's simple to operate. Loads of experts available if it breaks. Well tested. easy to expand or even drastically reshape.
It lacks "send". and performance of snapshots could be lower (try thin pools). Can easily add SSD caching, but performance improvement is possibly not as high as with alternatives
works well enough for me...
So for example one possible implementation of state is that you catch your own crash, save some state and then restore it when you restart
You aren't supposed to ever crash, however the whole language it's based around designing a framework to handle what happens if you do crash
So you design a whole framework of supervisors, watching processes, that all have a defined startup and shutdown order. You build structures with rules such as: if my cache module fails, them restart this whole chunk of application over here.
it's very cool
(for me it's the lack of one way sync, ignoring deletes, and no partial directory sync)
I find myself thinking the reverse to be honest. this infection has caused the largest worldwide distribution event in recent history, (possibly ever). the longer it persists, the greater the cost (economically and socially). As such I'm happy to try all kinds of things if they have a reasonable basis to help with the problem and the cost is reasonable
Granted the definition of "cost" is personal, but equally I'm genuinely surprised by the number of people who feel that mask wearing has a high perceived cost! It really feels like a small inconvenience to me.
If someone popularised the idea that the virus will go away if we only all wear pink trousers for a week. I'm sceptical of the science, but you know what, the personal cost is low. I'll "cooperate" just to ensure we have it a fair try.
masks at least have a very strong theoretical reason to be effective. I'm not really sure I understand the relatively heavy opposition? keen to hear from those who disagree?
However I agree that nim / zig could also be good directions
It is nicely decentralised. Nice UI. Run your own server. Deserves more love!
I've got more than a thousand of the previous unit in production. just ramping up on APU units. yes they are higher power than a Pi, but still very low. easy to develop for (amd64). tons of Ethernet ports. easy to use reliable storage. USB3, SATA, mpcie ports, SIM slots. openly available schematics
Not a lot not to like!
If you are familiar with gentoo it has a package manager called portage. You type “emerge packagename” and it installs it. Prepend ROOT=blah and it installs it in that dir instead!
So your build scripts are pretty trivial. Just write a bunch of emerge lines and you are done. Install in your new root, then package that ROOT. Simples!
Building from source could be slow, so cache binaries once built. Subsequent binaries will be used by adding “-k” to emerge above.
Profiles allow you to build target versions of software, E.g. customising compile flags or software versions. I use both a libc and a processor profile. The arch profile is also split between host and target, so for example static libs might be installed on host but not in target.
I used an overlayfs system to trim the delivery.
I think the big difference is I can rely on this huge distribution. Yet if I need some platform patch I need only drop it in my patches directory and hit rebuild. Put the patches dir in git and I’ve got a trackable distribution!
Comments?