It's not revolutionary, just very convenient. It's automatic, and I think M:Tier offers a similar service.
> How is this different from […] apt or yum?
It's a "utility for security and reliability binary updates to the base system." Syspatch is only for base system, not ported packages.
: Package Management https://www.openbsd.org/faq/faq15.html
In some ways, the BSDs are just catching up to Linux in terms of update distribution mechanism. They all have a history of being self-hosting compile-from-source systems, and some greybeards are still pretty attached to that idea.
As someone who discovered Linux first and happily used it for many years before discovering the BSDs, I think there's a lot Linux gets right that BSDs will or should adopt to be relevant. (There are also many things the BSDs get right, of course.) This is a good example of that.
But IMO there's nothing wrong with freebsd-update.
"Whenever you remove any fence, always pause long enough to ask yourself, 'Why was it put there in the first place?'" G.K. Chesterton
With the BSDs, you didn't even have the option of binary updates or packages until quite recently.
Fedora, openSUSE, Mageia, etc. use the official term. Debian and the BSDs use the informal "arm64" term.
aarch32 and aarch64 are strictly ARMv8, while arm32, being informal, could really be a catch-all term for all the previous ones. I don't know of any aarch32 distro though, they all seem to limit to ARMv7hf, which is sad because on a Raspberry Pi 3 you can't get the VideoCore binaries and v8 instruction set: going 64bit means most hardware does not work (at least: no X/wayland, no 3D, no sound), and some benchmarks have shown that they bring up 15-20% performance improvements.
Anyway, this is basically the same debate as x64 vs x86-64 vs amd64 and mostly bike shedding at the end of the day.
Edit: Registered for a Pinebook today, will have look for a board to play with. Any suggestions?
I'd probably read the last year-or-so of openbsd-arm list and check the recent commit messges for that part of the tree if that page isn't clear..
eg keyboards with keys that don't work, the GbE network pork actually only running at 100Mb/s, battery's that don't charge, screens with dead pixels
Not sure it's really worth the potential hassles at this stage. :(
That being said, if you can put up with the potential issues then it probably wouldn't hurt to try it out. :)
> The current target platforms are Rockchip RK3399, Allwinner A64/H5, Raspberry Pi 3 and Opteron A1100.
That's a good list, it may cover a number of "Maker"-oriented single-board computers that are fun to play with.
Note that most of the Raspberry Pi chip is its Broadcom Videocore IV graphics processor, which is not supported by the OpenBSD OS. You would have to hook up a screen to the GPIO pins, I think, rather than getting display out of the HDMI port. There are lots of LCD display "hats" on the market.
(I am typing this on my iPad, which is an iOS device, which is a descendent of BSD.)
Alternatively you can just SSH 59 it. It depends on what your objectives are.