Dexter's Law: Only proprietary software vendors want proprietary software and only fascists want fascism. Toots are my own. Self-employed. Father of three.
I aim to keep this to technical topics relating to bhyve and OpenZFS, and the occasional humor and Latvia.
So far (and from what I'm aware of) smolBSD can boot on
* QEMU/kvm (Linux/kvm, NetBSD/nvmm, macos/hvf) - smol kernel
* Firecracker - smol kernel
* Proxmox - smol kernel (https://github.com/rcarmo/pve-microvm)
* bhyve - NetBSD GENERIC trimmed kernel
* bare metal / USB / Whatever can boot - NetBSD GENERIC
If you’re implementing a timezone selector after handling all continents, oceans, and pseudo-macro regions… don’t forget Büsingen am Hochrhein 😄 https://en.wikipedia.org/wiki/B%C3%BCsingen_am_Hochrhein
A tiny German town of fewer than 1,500 people, completely surrounded by Switzerland.
Fun historical timezone trivia:
Büsingen is associated with Europe/Zurich instead of Europe/Berlin.
Why? In 1980, West Germany introduced DST, but Switzerland initially did not. For a few months:
Germany was UTC+2
Switzerland stayed UTC+1
and Büsingen followed Swiss time to avoid daily chaos with the surrounding area.
That historical difference is still reflected in the tz database today.
#coding 👨💻 #timezone 🌐 #freebsd #unix #time 🕜 #sysadmin 🖥️ #germany 🇩🇪 #Berlin #Switzerland 🇨🇭 #Zurich
@flo The difference really is negligible at least anecdotally, like to the point where it's a rounding error I would say and this is after me testing probably 100s of VMs deployed on all kinds of systems
Also I'd be curious to read the blog you're mentioning and maybe run identical tests so we can find out if the latest versions have any difference to their conclusions
And I personally like the aesthetics of a ZFS volume (which is also why it's a default on Sylve), it's meant to be a block device rather than a file trying to masquerade as one, and by default we have tuned it for performance compared to proxmox, setting things like primary cache to metadata (which gave us 10-20% boost) etc.
There’s no such thing as 30 years of RedHat muscle memory. I used RedHat quite a lot from the late ‘90s until about 20 years ago. I had to use Fedora again about for years ago and nothing I remembered about administering the system still worked. In contrast, 90% of the things I learned 25 years ago the first time I used FreeBSD still work (though they aren’t always the best way of doing things anymore).
Hopefully the recent flurry of Linux vulnerabilities will remind people that monocultures are bad for security. Replacing a Windows monoculture with a Linux monoculture may be a small improvement but does not fix the problem. Both systems are well past the complexity level where you can guarantee no security vulnerabilities.
A local privilege elevation bug combined with a sandboxed arbitrary-code execution bug in some widely deployed userspace software lets an attacker take complete control of all of your infrastructure if you have a single OS. If you have a mix of different systems, it is much harder to build exploits that will work on all of them.
This is part of the reason I strongly encourage digital sovereignty movements to focus on small, composable systems rather than huge monoliths. If every company and government service is running a different mix of modular systems, it’s much harder to create a portable attack that works on all of them.
Street Art Utopia
Emile "iMil" 
Heitor
monument valley girl
Alfonso Siciliano
hayzam
Florian
David Chisnall (*Now with 50% more sarcasm!*)