FreeBSD gains eMMC support so … errr … watch out, Android Version 10.4 of FreeBSD has landed, with the headline feature being support for eMMC. For those of you still short of your best after nocturnal chemical exertions, eMMC – aka Embedded Multimedia Card – packs some flash memory and a controller into a single package. That arrangement is handy for manufacturers of personal …
This post has been deleted by its author
I use it at home on my servers and my UNIXlike desktop for the same reason, out of the box ZFS.
I switched from CentOS and Fedora about three years ago and haven't looked back. Its nice to not have to constantly fuck around with broken bullshit (or listening to constant whining about how systemd is the spawn of satan, though those issues were more a problem with Fedora than CentOS) to get the OS to work the way I want it to.
I just wish that AMD had more than two people working on FreeBSD, but oh well.
After having (re)discovered the virtues of true Unix by starting to use NetBSD instead of Linux for single task systems, *BSD is a perfect fit for smaller devices. The people building this, are real geniuses, and understand where Unix is about: the user is in control, and not systemd, obese package management software that doesn't stop installing "dependencies" or dbus. And it is possible to build a kernel !, it takes less then 2 hours to find out how to configure and build a NetBSD kernel, something I gave up on Linux a decade ago, since moving the smallest pebble on the mount Himalaya of Linux kernel build software would prevent the new kernel to compile with vague messages not related to the change.
The results of this approach are clearly visible in the CVE database: BSD security rocks !.
"I gave up on Linux a decade ago, since moving the smallest pebble on the mount Himalaya of Linux kernel build software would prevent the new kernel to compile with vague messages not related to the change."
As a long time Gentoo user, I'm sympathetic to that. I've spent many hours trying to figure out what I need enabled and what can safely be disabled in my kernel. Setting up graphics, network and sound card support doesn't take too long with the gentoo online documentation, but you're on your own if you want to go through and turn off a whole load of stuff you'll never, ever use, and it almost certainly is not worth the effort, unless you're desperate to shave a few kb off your kernel. The descriptive comments from the "gui" based "menuconfig" are sometimes good, sometimes unhelpful, and sometimes non-existant.
I can't say that I've ever really had problems building my own Linux kernels, since the later 2.0 kernels - around 1999. Yes, there are one or two things to watch out for but by stripping out all the drivers and sub-systems I don't need means less stuff to go wrong and a reduced attack surface. My kernel packages are between one third to one half the size of a typical distro supplied kernel and come in at ~12/13MB, not that the size, in and of itself, is all that important.
The version 10.4-Release of FreeBSD is legacy. The current release is 11.1-Release and is from July. The driver changes can be found here with other changes. I need to upgrade my FreeBSD server to this new release soon.
https://www.freebsd.org/releases/11.1R/relnotes.html#drivers
"The version 10.4-Release of FreeBSD is legacy."
10.4 for is current and fully supported for a quite some time. It's not "legacy" and you don't have to "upgrade" to the 11 series if you don't want to. the 10 series doesn't go EOL 'till Oct.18 at the earliest,
In general, stable release get 5 years support, so it may be time to start planning a move to 11, but there's no real rush yet,
F26 -> systemd pulseaudio -> some folks have an allergy to Poettering. And workstation comes with far too much crap for some folks. My hate for systemd is *starting* to dissipate but only because I've found some interesting functionality that makes automation and error messaging within automation somewhat informative - given a bit of creativity.
Pulse -- well -- I hate that it brought windows audio functionality to linux and I love that it brought windows audio functionality to linux. It just depends on if I'm talking about WOW on wine or trying to conf call on lync in a KVM guest windows instance.
Freebsd -> sysvinit, absolutely minimal requirements to get it off the ground and running, and the cross dependency tree for things is *much* shorter. and networking -- network network. Just try it on the same hardware -- you will understand quickly.
What special arrangements are you talking about?
Besides, this is talking about backporting to a legacy version (FreeBSD 10)
If you cared about more uptodate features, you'd be using the official release version, FreeBSD 11.
Or, for someone more used to Linux instability, the development version, FreeBSD 12
<cheapshot>By the way, how's the Fedora Raspberry PI3 support going?</cheapshot>
FreeBSD user here since 4.2, I still have the CD-ROM, in its shrine ... anyway ...
<cheapshot>By the way, how's the Fedora Raspberry PI3 support going?</cheapshot>
Dunno, don't care, FreeBSD cuts it ... so does OpenSuse tumbleweed... needed that for ARM 64-bit software ... well, OpenSuse has some issues, I think, with sound ... and I am not sure it displays the "insufficient power" alert ... so, make sure your PSU's have enough juice.
Ok, tumbleweed has "système d", I could try FreeBSD's linux compatibility layer for my software, not sure it would work, though ...
This post has been deleted by its author
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
