Slashdot Mirror
OpenBSD 6.2 Released (openbsd.org)
basscomm writes: OpenBSD 6.2 has now been released. Check out the release notes if you're into that kind of thing. Some of the new features and systems include improved hardware support, vmm(4)/ vmd(8) improvements, IEEE 802.11 wireless stack improvements, generic network stack improvements, installer improvements, routing daemons and other userland network improvements, security improvements and more. Here is the full list of changes.
Seems that the post is missing the big feature to appear in 6.2, KARL - Kernel Address Randomized Link.
I don't think that "elitist" is the right word to use. I think the correct word is "professional". The *BSD communities are some of the most welcoming around, and they're always willing to help. The only caveat is that they expect you to act professionally, as well. That is, they don't put up with bullshit. If you're going to contribute code, you will be held to a high standard. If you're going to ask a question, it's expected that you've at least put in some serious effort to figure out the answer on your own. They won't necessarily hold your hand, but if you come in with good intentions they'll often go to the ends of the Earth to help you out.
Their professionalism is also why Linux starts to seem so amateurish after you've used the *BSDs for any period of time, and especially after you've interacted with the *BSD communities. Debacles like how Debian switched to systemd, causing severe stability problems and disruption for so many Debian users, would never be allowed to happen within the *BSD communities.
Oh. Oh, my. I'm sorry to say that that there is almost no paying work involving any of the BSD's, except for MacOS as a descendant of FreeBSD. Even the most casual search of job sites, whether hiring or looking for work, lists Linux over any or all of the BSD's by a ratio of hundreds to one.
The idea that they are a "go-to" operating system ignores that actual job listings involving the non-MacOS BSD's are almost entirely migration projects, to migrate from the BSD selected by a former technology architect, to a supportable and hardware compatible operating system. The individual BSD's can, and many do, have significant feature benefits over Linux. The lack of systemd is one of them, I can agree. But the featues you list have proven insufficient to gain market share compared to the ease of development, the ease of installation, and the broad usage of Linux.
Oh boy, so many things wrong here...
Welp I know this will get modded down, but hell why not play devil's advocate here? Vendor support. You have actual companies that will stand behind and certify software and hardware for Linux.
Hilarious. Try getting actual, useful support from Red Hat and SuSE, to name just two of the biggest... Go on, I'll be waiting right here.
The level of incompetence in these companies is simply astounding. Sure, there are some very good guys in there, but not in front-line support, that's for sure.
And, just so you know: hardware certification these days is usually Linux + FreeBSD, and it's done by the hardware vendor, not the software "supplier".
systemd homogenizes Linux. A single known Linux versus a half dozen BSDs where commercial support is iffy at best [...]
Yes, systemd homogenizes Linux... Down to the level of utter, absolutely unstable crap like Windows.
And there is not "a half dozen BSDs" - there is only three: FreeBSD, NetBSD, OpenBSD.
Compared to the situation of Linux, with not "half a dozen BSD", but litterally HUNDREDS of distributions, I am not sure you are being serious...
Most of them will get ten seconds to have 100 servers up and running, ready for whatever software the PHB has selected. With BSD you'll be lucky to get past configuring disks in that ten seconds. With Linux you'll have an army of AWS boxes at your command ready to go before your first cup of coffee is poured.
Ah yes, AWS, that marvelous field of shitty softare and even shittier infrastructure. Just FYI, it's called an "AMI", a system image in other words, and there are AMI for all of the BSDs. And the same is true for Azure and many other cloud offerings out there. You simply don't know what you are talking about, right? Either that, or you should stop blindly clicking on the Ubuntu AMI every time you create a VM in EC2.
Now don't get me wrong, I'm not sitting here dissing the BSD folks, but there's a serious need for folks to look past systemd as the sole reason everyone and their dog is leaving Linux.
Actually, no, systemd IS the reason serious system administrators and quite a few devops are leaving Linux behind. The crap you have to deal with gets simply unbearable after a while.
I could go on refuting your ridiculous arguments again and again, but frankly, I have better things to do with my time. You are a very poor devil's advocate and an even worse technologist/system admin/unix admin I am afraid. Your level of ignorance is frankly stunning.
The right to offend is far more important than the right not to be offended. (Rowan Atkinson)
Hit "enter" a few times
Yes, if you hit enter at the part where it says "Enter passphrase (empty for no passphrase)", you'll get no passphrase. News at 11. Now since this behavior is consistent across all systems that have ssh-keygen, including linux, why are you using this to discredit OpenBSD? And it may have not occured to you, but there are legitimate use cases for unencrypted keys.
*Look, ma!!!* Home directories with .ssh/id_rsa, .ssh/id_dsa
Look ma, even if you're too lazy to enter a passphrase, they're still not world readable. This is, btw, layered security, the very thing you're trying to talk away.
Stop spreading nonsense in order to appear to have a point.
CLI paste? paste.pr0.tips!