News for hackers. Stuff that matters.
Re:OpenBSD 7.0 by mirekrusin on Thursday October 14, 2021 @11:28AM (#28865654)
I'd love to try but I'm experiencing hardcore option paralysis every time I start thinking about it.

FreeBSD, OpenBSD or NetBSD – _that_ is the question.

Wait, maybe DragonFly actually? illumos? ...wait, I mean OpenIndiana, I think... wait, what's OmniOS? Is Darwin a thing, like I could just have BSD and macOS for free or something?

Re:OpenBSD 7.0 by chousuke on Thursday October 14, 2021 @12:41PM (#28866600)
I recommend giving OpenBSD a try over the others. It's just... a clean OS, and the base system is extremely well documented; to the point that I think it's the only OS you can learn inside out without ever using Google.

OpenBSD might not be the best choice for any given use, but it's so remarkably consistent and understandable that I think everyone interested in alternative OSes should try it out at least once.

Re:OpenBSD 7.0 by kazen44 on Thursday October 14, 2021 @01:21PM (#28867171)
OpenBSD has been the OS with the lowest amount of maintenance in my opinion.

used it as a webserver and VPN appliance for a couple of years now.

only thing in terms of maintenance is the following when a new release is released.

pkg_add -u ( i usually update extra packages every 6 months, which is mainly lets encrypt). syspatch sysupgrade

reboot:

after reboot

sysmerge to see if i need to do a config diff.

Has been rocksolid and very future rich in base aswell.

Re:OpenBSD 7.0 by snvzz on Thursday October 14, 2021 @03:08PM (#28868595)
While sysupgrade is convenient, there's usually some manual steps.

Always read the upgrade guide before upgrading.

Re:OpenBSD 7.0 by wahern on Thursday October 14, 2021 @06:27PM (#28871033)
For the OpenBSD curious:

This release only includes changes related to SNMP, which I imagine are irrelevant to most people, though probably exciting for a subset of OpenBSD users. https://www.openbsd.org/faq/upgrade70.html

The upgrade guide for 6.9 gives a better flavor for how OpenBSD handles and documents subsystem and configuration changes: https://www.openbsd.org/faq/upgrade69.html

Notice how succinct and consistent (across decades!) are the upgrade guides. The above have the same basic format and content as this one from 2004: https://www.openbsd.org/faq/upgrade35.html I've been doing remote upgrades of OpenBSD and Linux (mostly Debian, but also occasionally Red Hat derivatives) for over 20 years. While I've fortunately only rarely encountered significant problems with any of them, OpenBSD upgrades are the only ones where I can have any confidence in understanding and tracking how the system evolves across upgrades. Follow the upgrade guide and delete outdated files (much easier since sysclean(8)), and a 10-year-old OpenBSD box can have a filesystem as pristine as a freshly installed system.

I'm not one of those people who wants pristine for the sake of pristine. But pristine is important when you care about security, and maintenance burden is a huge component of security, as are simplicity and transparency.

Re:OpenBSD 7.0 by matja on Thursday October 14, 2021 @06:34PM (#28871086)
Lack of ZFS, or any checksumming filesystem at all is a hard "no" for me.
Re:OpenBSD 7.0 by melony on Thursday October 14, 2021 @01:29PM (#28867279)
I don't want a OS where I have to read man pages and documentation to get around. The whole self documentation excuse is the same reason why Emacs is slowly losing market share. People want software that is intuitive, and failing that, have all answers available on their favorite search engine. Short of baking a chatbot or search engine into OpenBSD, relying purely on self documentation is not sustainable. Though the idea of Clippy being powered by GPT3 does sound appealing.
Re:OpenBSD 7.0 by chousuke on Thursday October 14, 2021 @02:28PM (#28868044)
"Intuitive" is often a code word for "familiar to me". A full-blown general purpose OS cannot be completely intuitive; the user always needs something to build from.

For what it's worth, I think OpenBSD is intuitive because of its consistency. It's certainly been more intuitive to me than any other OS; it just makes sense as a whole in a way that no other OS quite does, and that's refreshing in a world where users are expected not to understand what their tools are and how they work.

OpenBSD just builds its intuitive bits on things you may not yet know. Fortunately, it has excellent documentation to get you started.

Re:OpenBSD 7.0 by mrweasel on Thursday October 14, 2021 @02:49PM (#28868319)
Don't take this as argumentation against what you're saying, because it makes a lot of sense. However, I would love for my phone or Mac to at least have the option of reading the documentation, but it's not easily accessible. Some things a deemed so intuitive that it doesn't need documentation, yet I still can't use it or find it.

On OpenBSD, if you're stuck on something in ksh, cwm, pf or any other built in tool, the man page is right there. Easily accessible, easy to read and comprehensive. When I play around on my OpenBSD box, the man pages is often my first choice over a search engine.

Also, not confuse man pages on OpenBSD with Linux man pages. Those two are remarkably different. Many Linux tools have good and comprehensive man pages. On OpenBSD everything has great man pages.

Re:OpenBSD 7.0 by lcall on Thursday October 14, 2021 @01:40PM (#28867429)
You can still use search engines, but once you learn your way around the documentation, you might find it is more reliable and quicker.

To me, it seems worthwhile to have fewer 0-day bugs to worry about, and more reliable separation between user accounts (fewer privilege escalation bugs, etc etc). (I also recommend setting default umask to 0077 for the same reason, except while using pkg_add -- I have a wrapper script that undoes it temporarily for that due to issues encountered.)

There are reasons people use Windows or Apple (perceived convenience), and reasons not to (long-term cost/benefit decisions for known uses).

In case it becomes useful to anyone: One way to traverse the docs is (occasionally helpful) is using something like http://man.bsd.lv/ for OBSD docs, like putting in an "=" (w/o quotes) in the search field then clicking "apropos" shows all the commands -- a useful way to learn "what is available in the base system"; or doing full-text searches (can be learned locally, I have an awkward script for it if needed),

(Edit: s/what is available/what is available in the base system/ .)

And: I find the ~"only 2 remote holes in the default install since about 1996" to be very impressive.

Edit: Another way to look at it might be by priorities. I have come to see priorities of some systems roughly as:

OpenBSD: security, openness, correctness (including of documentation), portability.

Linux: features, performance, openness, breadth of everything, compatibility, convenience (distributions vary in specifics of course; debian and/or devuan continue to impress me in their own way).

FreeBSD: performance, stability, openness.

NetBSD: portability, stability?, maybe enjoyment for its developers, openness. (I know least here.)

Windows / Apple: profitability while targeting preferences of specific groups who want different specific kinds of convenience, it seems.

Re:OpenBSD 7.0 by tiew9Vii on Thursday October 14, 2021 @07:24PM (#28871579)
If you used Linux for any amount of time it'll take a couple of days to get familiar with OpenBSD and they you will be more at home with it than Linux.

To me OpenBSD is similar to what Slackware was, as simple as it possibly can be, with the advantage of a BSD being coherent and consistent.

I'm a long time Linux user and only used OpenBSD recently. I often find myself Googling Linux configs. I did use Google for OpenBSD to get started but found after a day I wasn't and relying on the man pages instead for system settings etc. They really are short, concise and complete, everyone says this but until you use them it's hard to understand.

I use Emacs I don't know Emacs. Emacs is a completely different beast to OpenBSD. Emacs is a huge rabbit hole and you spend as much time building your own Emacs as you do using Emacs. OpenBSD i've set up once which was simple as someone never using it before, and then forgot about it. It's been sat ticking away in a corner, no interruptions.

As much as I really like OpenBSD I don't think I can use it as a primary desktop. There's a few compromises on hardware support, no docker for my day job and I've read the desktop experience is slower than Linux just because it hasn't had the money and people Linux has had with drivers etc.

I'd really recommend anyone try OpenBSD for it's simplicity and educational purposes. If you use it as your main OS you will likely be dissapointed with some of the limitations, as a server / secondary educational device you might be pleasantly surprised.

Re:OpenBSD 7.0 by xet7 on Thursday October 14, 2021 @05:14PM (#28870206)
Oh, having man pages included is much better than "read the source code".

Unfortunately search engines are unreliable, some "search engine optimized" virus pages could be first, and not some bank or docs website.

Re:OpenBSD 7.0 by Koshkin on Thursday October 14, 2021 @03:29PM (#28868850)
Sure, you could make the OS CLI "intuitive" (by which I am sure you mean discoverable) by supplying the 'help' command, but in the end wouldn't this still amount to reading a bunch of text?..
Re:OpenBSD 7.0 by ori_b on Thursday October 14, 2021 @04:42PM (#28869793)
> and failing that, have all answers available on their favorite search engine.

Luckily, the manpages are available on your favorite search engine!

Re:OpenBSD 7.0 by szundi on Thursday October 14, 2021 @05:44PM (#28870588)
This is not math what you can derive from some axioms, this is a system and software that other people invented. Good luck feeling and thinking just like all of those 41234 people involved.
Re:OpenBSD 7.0 by undoware on Thursday October 14, 2021 @12:53PM (#28866753)
My advice? Go with OpenBSD.

These are the folks that brought you the word 'hackathon', and OpenSSH. (Ever use ssh? Thank OpenBSD.)

These are the folks that actually bother to read not just a PR, but actual full codebases, just to make sure their pointers don't dangle.

It's been years since the DevOps space was first told to prefer 'livestock' -- disposable, nearly-identical instances -- to pets -- long-lived customized instances and servers -- but as every farmer knows, if you have lots of sheep, the job is a lot easier if you have a sheepdog. Not quite a pet, but not cattle, either.

OpenBSD is my sheepdog. It keeps my git repos, it runs my wireguard VPN, and it, above all the other systems I touch, is trusted.

But trust is ultimately about people, not about systems. Systems get their trusthworthiness from their creators, the way the moon gets light from the sun.

And in trustworthiness, the OpenBSD community has a breathtaking superpower: They can say no. They are good at saying no. Do you know how hard that is -- to have someone ask for a feature, and just tell them off? That's the hardest thing any manager ever has to do, and these guys are good at it. Rare, in FOSS space.

These are the folks that are so good at saying 'no' that they ship with a literal actual bespoke copy of 'vi', that does exactly what it is supposed to, does not take packages, and also does not have a package manager pulling in raw github HEADs. (I love you, neovim, but you are so trusting!)

OpenBSD has been around for most of my 20+ career in this industry and it's sort of always been this aggressively reliable paperweight of a distro. I'm never quite sure what to do with it (NixOS is my go-to for my workstations -- NixOS + Wayland + Sway + Alacritty + Neovim is as close to godliness as a user interface can come) but OpenBSD finds its uses, and in those uses, it is smooth and heavy and reliable, making it the perfect foil for the rest of my infra: For where NixOS is neurotic and brittle, OpenBSD is saturnine and malleable.

I think of my infra as sort of being like a knife blade, with a glittering Nixos/Wayland/Neovim edge supported by a soft, heavy core of OpenBSD.

If everything else breaks, so long as I have my OpenBSD instances, I can recover.

One final word: At my end, I just finished upgrading my instance at openbsd.amsterdam; big shoutout to that amazing team for their incredible support. (Mischa, in particular, is a force of nature, and I am fan. ;D)

Re:OpenBSD 7.0 by bpye on Thursday October 14, 2021 @01:55PM (#28867634)
OpenBSD is definitely the free OS than I enjoyed running the most. I now use NixOS for most of my server and VM uses because I really appreciate being able to trivially keep all the configuration state in version control.

However when I ran OpenBSD on an old Chromebook I did really enjoy using it, I made a point of trying to use just the base system and aside from needing a web browser it was extremely usable. The documentation is universally good all the built in tools are well maintained. In the near future I’m gonna setup a separate firewall/router machine from my NixOS box and I think I’m going to use OpenBSD there too.

Re:OpenBSD 7.0 by undoware on Thursday October 14, 2021 @03:22PM (#28868763)
I too have the nixos vs openbsd decision nibbling at me every time I spin something up.

Here's what helps me decide: I simulate a disaster. Since I'm just me, I do it on paper (empirical ways are best but are also the most expensive, and in a pinch, a thought experiment can illuminate as well. Not always the same things, but light is light.)

Try it -- open a scratch.txt and write about things that would happen, and then the things that would probably happen as a result of that.

The one that often comes up for NixOS is "I lose network connectivity." While NixOS is phenomenal in its ability to roll changes back, the fact that I need a stable Internet connection in order to make any change whatsoever to the current config makes that little piece of CAT-8 a SPOF for any number of unexpected (and intuitively unrelated) matters, making the overall system hard to reason about.

You can mitigate this by hosting your own NixOS channels, which is sort of the equivalent of hosting your own apt-get repo.

But, as you might expect, that's actually a fair amount of extra work. So I don't, especially not on laptops, where space can (still) be limited.

So, every time I do `home-manager switch` I need a viable network connection.

This is especially galling if you (like me) manage most of your apps with Nix' `home-manager`. Think it through; Nix manages (say) your word processor; you want to change the font size in your word processor; you edit your home.nix and hit `home-manager switch`.

But look at what this entails! My apartment building's fibre-optic cabling should never be a depenency on altering the font size in my word processor, but here I am. Ironically, for the sake of convenience.

Now, none of this is to slag on NixOS. As I mentioned above, it's my favourite way to encounter reality. I'm typing this to you on NixOS right now. For me, the pros outweigh the cons. Provided, of course, I have something less brittle than NixOS to back me up, and for me, that means OpenBSD.

I have an OpenBSD instance in the cloud and a break-glass procedure for getting into it. It backs up via another old-school friend, tarsnap. It hosts the git repos that contain my nixos and home-manager configs. If I can talk to it, I can simply zap my NixOS config onto some new edge device and be back up and running in no time.

I also typically have a NUC running OpenBSD present as well, in case that apartment-building fibre gets troublesome (again,) but not at the moment, because my beloved PCEngines device has apparently become unstable under any OS. But when I get that OBSD NUC set (back) up, it will absolutely have a NixOS channel on it, and it will serve as a firewall, a SAN, serving NixOS channels to the edge devices. It will have an actual serial port and a password on a wax-sealed bit of paper in my fireproof safe. Because I think ahead, and that's what I need to get back up and running under the worst circumstances.

I simply can't imagine a non-hardware-failure disaster that could take out an aggressively boring OpenBSD bastion instance. They are just relentless in their persistence.

As I keep saying, NixOS and OpenBSD pair together like honey and mustard. Contrastive but unexpectedly delicious.

Take-home: If you're building infra, try adding some OpenBSD to the mix. It can make the unrecoverable recoverable.

Re:OpenBSD 7.0 by Datagenerator on Thursday October 14, 2021 @01:13PM (#28867054)
Thank you for writing this. Analogous to spinning wheels, the outside rotating very fast ( NixOS/Arch) and near the stable center we have several BSD's. FreeBSD for the excellent ZFS, OpenBSD for vital network functions, Wireguard etc.

Cheers, happy donations to the BSD Foundation!

Re:OpenBSD 7.0 by bluejekyll on Thursday October 14, 2021 @11:59AM (#28866089)
This isn’t all that different from choosing the Linux OS of choice. That decision often is partnered with the package manager that’s desired, and how quickly things are upstreamed in it. Do you want apt, nix, yum/rpm? Then how stable do you want it? Debian, Ubuntu, etc? How much support are you looking for? Redhat, etc.

I guess I don’t see a major difference in the complexity of that decision process in the Linux space, which might have been alluded to.

Re:OpenBSD 7.0 by 5e92cb50239222b on Thursday October 14, 2021 @12:11PM (#28866234)
Most Linux distributions are much more similar to each other than BSDs are. At least that's my impression after spending the last month at work porting a bunch of scripts from Linux to several BSDs (Free, Open, and Net). The differences are too many to describe here, from where they install third party libraries, to configuration file locations and formats, to how basic tools work (essential things like grep/sed/awk have (sometimes very) different feature sets, flags, and runtime characteristics (for example, how exactly do they handle signals)). Default shells are also very different, though that's a pretty minor thing.

If you compare something like Debian, Alpine, and NixOS, then maybe..

Re:OpenBSD 7.0 by bluejekyll on Thursday October 14, 2021 @03:37PM (#28868942)
I find each Linux OS that’s based around a different package manager to generally feel like a different operating system. That’s my point.

The BSDs all have a common ancestor. The Linux’s tend to all have a GNU user space, the kernels are mostly the same, but the OS layout tends to differ in important ways.

Re:OpenBSD 7.0 by anthk on Thursday October 14, 2021 @12:19PM (#28866325)
Not even close. Each BSD is it's own OS.
Re:OpenBSD 7.0 by bluejekyll on Thursday October 14, 2021 @03:34PM (#28868918)
Is Debian a different OS from Redhat?
Re:OpenBSD 7.0 by anthk on Thursday October 14, 2021 @03:39PM (#28868963)
Can you run Debian stuff on a RedHat chroot without needing different ABI compat libraries? Yes.

Can you run FreeBSD binaries under OpenBSD? No.

Re:OpenBSD 7.0 by hulitu on Friday October 15, 2021 @06:46AM (#28876340)
With shared libraries versioning enabled it is like in this famous movie "HAL: Without your space helmet, Dave, you're going to find that rather difficult." And taken into account that it is in fashion to introduce incompatibilities even between shared libraries minor versions, more so.
Re:OpenBSD 7.0 by bluejekyll on Thursday October 14, 2021 @05:01PM (#28870047)
This depends on the glibc version, but sure, that's a valid difference between the two.

edit: and oddly if you only go with this definition, that is Windows with WSL also a Linux OS? I'm guessing most people wouldn't say yes...

Re:OpenBSD 7.0 by xet7 on Thursday October 14, 2021 @05:18PM (#28870272)
WSL2 does include full Linux kernel.

I would presume Linux OS to run Linux kernel on host OS. By default Windows runs Windows kernel.

Re:OpenBSD 7.0 by szundi on Thursday October 14, 2021 @05:46PM (#28870602)
WSL2 uses HyperV for that.
Re:OpenBSD 7.0 by GekkePrutser on Thursday October 14, 2021 @07:56PM (#28871935)
Good question. Depends how you define OS. I consider them different OSes based on the same kernel.

They have too much disparity in terms of configuration to consider them the same OS for management purposes which is my main focusat work. But I can understand if someone with another perspective feels differently.

Re:OpenBSD 7.0 by snvzz on Thursday October 14, 2021 @03:10PM (#28868621)
*its
Re:OpenBSD 7.0 by t-3 on Thursday October 14, 2021 @01:29PM (#28867273)
OpenBSD for laptops, VM guests, and VPSs. It has a very coherent userland, and the devs dogfood heavily, my go-to for anything I have to actually administer.

FreeBSD for servers and NAS, desktop. FreeBSD has high performance all around, ZFS, jails, bhyve, linux compatability, etc. But it's not as nice to administer as OpenBSD. I want to love it, but it's tedious.

NetBSD is an OK choice for anything, and very capable, but doesn't stand out for anything other than portability. If you enjoy hacking on things, you might find a lot of use in it.

Re:OpenBSD 7.0 by na85 on Thursday October 14, 2021 @01:45PM (#28867498)
Openbsd has consistently scored towards the bottom in all performance benchmarks that I've seen in the last few years, when compared to FreeBSD and various linuxen.

I would personally never use it for a laptop.

Re:OpenBSD 7.0 by wowtip on Thursday October 14, 2021 @02:16PM (#28867908)
Scores are one thing, using it is another.

I ran OpenBSD on a Thinkpad T450 for over a year, but recently switched to OpenSUSE Tumbleweed, not because of lack of speed, but some missing applications and blutooth support.

Given I don't run a heavy desktop environment, rather just StumpWM, but still I did not in any way feel OpenBSD was slower than Linux, using the same applications.

OpenSUSE is the most solid Linux I have used so far, but OpenBSD was more to my liking setting up and maintaining. It is well thought out, simple, and... just makes sense.

Re:OpenBSD 7.0 by na85 on Thursday October 14, 2021 @10:40PM (#28873516)
>Scores are one thing, using it is another.

Indeed but I ran it on my Thinkpad and it was a sluggish mess.

Re:OpenBSD 7.0 by doublepg23 on Friday October 15, 2021 @07:36PM (#28884336)
When I ran it on my X200 it was simply unusable with GNOME, which isn’t giving it a fair shot yes, but it’s fine with GNOME on Trisquel and Arch.
Re:OpenBSD 7.0 by t-3 on Thursday October 14, 2021 @02:17PM (#28867916)
OpenBSD has way better ACPI, power management, and less setup hassle than FreeBSD, and way cleaner and nicer out of the box than any linux distro. You don't generally have to hack on anything to get basic laptop functionality working, and the small loss of performance from mitigations, disabling SMT, etc. is really not as big a deal for me, because my laptop is used for ssh and web browsing, not compiling huge projects or playing games.
Re:OpenBSD 7.0 by ndiddy on Thursday October 14, 2021 @04:14PM (#28869406)
Even using it for web browsing, I found that Firefox was much slower on OpenBSD than it was on either Linux or Windows on the same hardware.
Re:OpenBSD 7.0 by tcmart14 on Saturday October 16, 2021 @12:06AM (#28885461)
It depends on where you fall in trade-offs. OpenBSD also tend to be proactive in security and will choose security over performance enhancements. FreeBSD aims for performance. If you need a super performant desktop that is running a BSD flavor, FreeBSD is the choice. If your focus is having a secure desktop, OpenBSD is probably more up your alley. It is the age old question, you want speed, quality and quantity, but you can only choose 2, so which 2? Neither is a lesser system, they just have different priorities. For BSD, I have a preference for NetBSD, mostly because I value portability. I can take pksgrc and use it on my MacOS machine or my Linux box.
Re:OpenBSD 7.0 by anthk on Thursday October 14, 2021 @01:54PM (#28867616)
If you cared about actual security, you would use it in a laptop thanks to bioctl and full disk encryption.
Re:OpenBSD 7.0 by ranger_danger on Thursday October 14, 2021 @02:28PM (#28868040)
OpenBSD is not really as secure as people make it out to be: https://madaidans-insecurities.github.io/openbsd.html

And plenty of other OSes have FDE and everything in-between.

Re:OpenBSD 7.0 by nix23 on Saturday October 16, 2021 @04:01AM (#28886296)
Really good to see hardenedbsd is being mentioned, thanks for the link.
Re:OpenBSD 7.0 by na85 on Thursday October 14, 2021 @06:41PM (#28871164)
I don't think OpenBSD's reputation for security is warranted. Their vaunted claims of only two remote holes in the default install is useless because if you're using it for a daily driver you're going well beyond the default install.
Re:OpenBSD 7.0 by doublepg23 on Friday October 15, 2021 @07:40PM (#28884352)
I would have to agree with with your assessment, referencing the link in the above tree and this isopenbsdsecu.re .

Not to imply I don’t like OpenBSD, I love their first class support of old architectures.

Re:OpenBSD 7.0 by __turbobrew__ on Thursday October 14, 2021 @07:03PM (#28871395)
> OpenBSD for laptops

Only if you carefully pick your laptop hardware. I tried giving OpenBSD a spin as a daily driver on my XPS13 9343 and was plagued by issues:

1.) The network firmware is not included in the base OS. I had to download the firmware onto a USB storage device since the XPS doesn't have an ethernet port.

2.) 802.11ac isn't supported on my network card

3.) The login manager and window environment are unusable on a 4k screen. Trying to scale using xrandr --scale caused everything to appear fuzzy. I scoured the @misc mailing archives and could not find a suitable way to scale display without causing blur.

4.) Suspend/resume is broken and causes the kernel to panic.

5.) X.org doesn't use the inteldrm driver by default which causes choppy media playback

6.) OpenBSD puts memory limits on processes by default which causes memory hungry applications -- like web browsers -- to run choppy unless you change the memory limits.

None of these issues came up when using Ubuntu on my XPS 13. On Ubuntu it "just worked".

Re:OpenBSD 7.0 by wyager on Thursday October 14, 2021 @02:32PM (#28868088)
I haven’t used OpenBSD yet, but I found FreeBSD to be a total breeze to administer compared to Linux. You’ve gotten me very excited about OpenBSD…
Re:OpenBSD 7.0 by rjsw on Thursday October 14, 2021 @06:05PM (#28870808)
I use NetBSD because I want the same OS on the things that I'm hacking on and on my development machine.
Re:OpenBSD 7.0 by bilinguliar on Thursday October 14, 2021 @03:52PM (#28869118)
In the case of OpenBSD, it is more “drinking your own champagne” than “eating your own dog food.”
Re:OpenBSD 7.0 by ink_13 on Thursday October 14, 2021 @11:34AM (#28865724)
IME it depends on your use case.

If you want something you can use as a border router/firewall, OpenBSD.

If you want something for more general-purpose computing (like a desktop or home server), FreeBSD.

If you want something you can install on your toaster, NetBSD.

Re:OpenBSD 7.0 by messe on Thursday October 14, 2021 @11:57AM (#28866053)
I think this is a bit limiting. FreeBSD's networking performance can be significantly higher than OpenBSD's (although IMO OpenBSD's pf has nicer syntax), so it's a great firewall choice.

Similarly, on desktop, OpenBSD can be pretty nice if you're a developer comfortable in the terminal; it runs the same graphics drivers as FreeBSD and Linux (other than NVIDIA). It's defaults tend to be a bit more sensible on desktop/laptops too IMO as its developers are more likely to dogfood it. There's been good progress on NetBSD desktops over the past few years as well, but I'm less familiar with it, so I can't comment too much.

With regards to portability, NetBSD supports more systems, but often I've found that OpenBSD is a little bit more stable on the ones they do support as they insist on not using cross compilation: so every system they do support is at least stable enough to build itself, which is a good stress test, especially on older machines.

Re:OpenBSD 7.0 by hackbinary on Thursday October 14, 2021 @12:47PM (#28866668)
If you are looking to dip your toe in and have a tinker with BSD, FreeBSD is probably the best place to start because it has spread of compatibility.

But if you are looking for more focused projects, then Dragonfly for best out of box desktop experience, openbsd for security and firewall, and netbsd for compatibility and portability across loads of devices.

Re:OpenBSD 7.0 by theonemind on Thursday October 14, 2021 @03:43PM (#28869001)
I'd recommend trying one of the big three. If you value performance, FreeBSD. If you like a really well-documented, simple, coherent system, OpenBSD. If you've got a real tinkerer mindset, NetBSD--like, kernel extensions in Lua, run it on anything you can find with a processor in it.

They're all good. I wouldn't over-complicate it. Just look at the one with known strengths that most match what you most value and dip in. A lot of the knowledge crosses over if you want to try other ones anyway, they're all related.

Re:OpenBSD 7.0 by epitactic on Thursday October 14, 2021 @12:01PM (#28866114)
This is why I've setup my homelab with a hypervisor, you don't have to choose and can run each of these operating systems, for specific purposes they are best suited for. This is what I do:

OpenIndiana: file server (ZFS)

OpenBSD: firewall, router, network services (DHCP, DNS, NAT)

DragonflyBSD: game server

FreeBSD: other general application services

I haven't found a personal use case for NetBSD yet, though I would like to (it is great for embedded systems).

Re:OpenBSD 7.0 by bpye on Thursday October 14, 2021 @01:57PM (#28867653)
Is OpenIndiana really better than FreeBSD or ZFS on Linux today? I’ve had a pretty great experience using ZFS with NixOS but I’m curious if I’m missing anything.
Re:OpenBSD 7.0 by doublepg23 on Friday October 15, 2021 @07:41PM (#28884364)
Yeah I think using ZFS on even Linux is fine now since they’re using the same code base at this point.(IME Ubuntu has the most painless experience as it ships with the kernel by default.)
Re:OpenBSD 7.0 by Enginerrrd on Thursday October 14, 2021 @12:12PM (#28866239)
Which hypervisor are you using for that? I used to run Xen for a similar purpose, but I ended up just running normal debian with a bunch of lxc containers instead after dealing with some Xen issues that were difficult to unravel.
Re:OpenBSD 7.0 by epitactic on Thursday October 14, 2021 @12:36PM (#28866538)
ESXi (free version), it works well though if I had to do it again from scratch today, I'd probably go with KVM
Re:OpenBSD 7.0 by Datagenerator on Thursday October 14, 2021 @01:05PM (#28866949)
Tried Proxmox?
Re:OpenBSD 7.0 by NexRebular on Thursday October 14, 2021 @04:18PM (#28869459)
Or SmartOS?
Re:OpenBSD 7.0 by johnisgood on Thursday October 14, 2021 @12:41PM (#28866592)
Why did you choose DragonflyBSD for the game server vs. another BSD?
Re:OpenBSD 7.0 by amatecha on Thursday October 14, 2021 @01:06PM (#28866968)
Also, which games? curious what is easily hosted on BSD :)
Re:OpenBSD 7.0 by na85 on Thursday October 14, 2021 @01:17PM (#28867111)
Which games are you hosting on dragonfly, and is the performance actually better than freebsd?
Re:OpenBSD 7.0 by mirekrusin on Thursday October 14, 2021 @02:42PM (#28868209)
"All of them" is an interesting answer.
Re:OpenBSD 7.0 by foodstances on Thursday October 14, 2021 @12:01PM (#28866108)
They all feel different, I would encourage you to install each in a VM and play around and see which one you like the best.
Re:OpenBSD 7.0 by snvzz on Thursday October 14, 2021 @03:07PM (#28868583)
Try them all. Or as a start, try any. You can eventually try them all.
Re:OpenBSD 7.0 by proxysna on Thursday October 14, 2021 @12:56PM (#28866796)
If you are looking for a great server system give Omnios/Smartos and other Illumos distributions a try. Rock solid, well engineered and legitimately fun to tinker with. OpenIndiana is the desktop option, heard a lot, but i have no experience myself.
Re:OpenBSD 7.0 by ktm5j on Saturday October 16, 2021 @09:36AM (#28887773)
I'm quite fond of Dragonfly BSD. It's a pleasure to use, well documented and hammerfs seems pretty decent.
Re:OpenBSD 7.0 by rgacote on Thursday October 14, 2021 @01:42PM (#28867451)
It's not like there's not 42 different flavors of Linux...