No offense!? But why THREE ??? i see this with alot of other products reddit / BSD ---------------------------------------------------------------------- deux3xmachina · 2019-08-29 17:32 I don't understand the question. ---------------------------------------------------------------------- Host127001 · 2019-08-29 17:33 I guess "why not just BSD?". They don't write Debian-Linux, Arch-Linux and Gentoo-Linux for example ---------------------------------------------------------------------- bilog78 · 2019-08-29 17:37 The BSDs aren't just packaged differently, they have differences at the kernel level. ---------------------------------------------------------------------- liveoneggs · 2019-08-29 17:40 there are way more than three :) ---------------------------------------------------------------------- [deleted] · 2019-08-29 17:47 [deleted] ---------------------------------------------------------------------- Bphag · 2019-08-29 17:55 [Host127001](https://www.reddit.com/user/Host127001/) is catching what im throwing out. im uninitiated to this world. feel free to ignore my ignorant question ---------------------------------------------------------------------- [deleted] · 2019-08-29 17:59 Three is a number of power. ---------------------------------------------------------------------- shawn_webb · 2019-08-29 18:26 Isn't life too short to fret over such trivial matters? ---------------------------------------------------------------------- Bphag · 2019-08-29 18:30 no fretting just dumb reddit shitpost to be honest. incase it garnered a discussion that i wouldn't other wise be privy to ---------------------------------------------------------------------- jaypatelani · 2019-08-29 18:38 It was initiated by Trinity of Matrix 😎 ---------------------------------------------------------------------- Kernigh · 2019-08-29 18:38 Because they forgot to add [DragonFly BSD](https://www.dragonflybsd.org/). I guess that [MidnightBSD](http://www.midnightbsd.org/) and [Minix](https://www.minix3.org/) still exist, so I am aware of 6 diverging BSD projects. I don't count [TrueOS](https://www.trueos.org/), because they stay compatible with FreeBSD. Apple's macOS has BSD inside, and might count as a 7th BSD. ---------------------------------------------------------------------- deux3xmachina · 2019-08-29 18:40 Ok, no shame in not knowing something. It sounds like you may not be familiar with the BSD family of operating systems, so for a quick(ish) overview, while there are dozens of different, relatively well known distros, they're all the same OS. At least for the overwhelming majority of distros, they use the same Linux kernel, the same C library (glibc), systemd to manage their services, the same GNU coreutils, and likely the same bootloader (GRUB2). They'll have some differences, but the most significantly distinct Linux distros are Void-musl, Alpine, Gentoo, and Funtoo (Slackware, Guix, and NixOS may also qualify, but I know less about them). ​ On the other hand, each BSD is a distinct OS, while FreeBSD, NetBSD, OpenBSD, DragonFly BSD, HardenedBSD, and TrueOS all share code with each other and have a common ancestor (4.4 BSD). Also unlike Linux distros, each BSD is built as a whole OS, their kernel, bootloader, C library, userland, everything is developed together. Things are a little less distinct with TrueOS, Trident, and HardrenedBSD because they're all downstream forks of FreeBSD, but they have their own teams working on their target needs. ​ This is just barely scratching the surface, but if we assume the options are for your OS, there are three different BSDs because FreeBSD, NetBSD, and OpenBSD are all distinct operating systems, while Linux distros are not. ---------------------------------------------------------------------- Bphag · 2019-08-29 18:49 Seems like a waste...if ppl could only get along. In general just focus on fewer things quality would erupt. Imagine a handful of distro (Linux) Instead of 100. Or everyone on GitHub capable of contributing would all do one project for a month so much more would get done etc etc.scake the examples country science teams focused on problems. W.e we all gono die soon ---------------------------------------------------------------------- deux3xmachina · 2019-08-29 19:02 That certainly sounds good in theory, but monocultures are a horrible problem, it's what's causing issues with bananas and has caused bugs like heartbleed to be so devastating. Arguably, monolithic kernels (like Linux and every BSD) are a worse idea than Microkernels (MINIX and GNU HURD), and these may even be a worse idea than things like Exokernels, which is only discussing the merits of kernel design. That alone is a huge point of contention, then we have questions regarding how to improve booting and service management, many people think systemd's the future, but not everyone, and it requires the GNU glibc library to even compile. The C library is also a point of contention, with several different ideas on what's best. This sort of diversity seems like a negative on the surface, but if you had a datacenter that could use different servers, some RHEL, some BSD (doesn't matter which in this example), and some Alpine or Void- musl, it'd be extremely unlikely that an attacker could re-use their exploits on all those systems, so you could in the worst case, have 1/3rd of your servers down or running malicious code, This would give the defenders an edge since the attackers would have to adapt to each new OS to continue making progress. It also means that only 1/3rd of your servers could possibly suffer from bugs in systemd such as a DOS due to problems that were found in \`systemd-resolvd\`. It'd be nice if we could theoretically combine all the efforts of open source devs into a focused project, but we also gain so much more by having these different options available. ---------------------------------------------------------------------- aedinius · 2019-08-29 19:05 Monoculture is bad, and one-size-fits-all leads to being poor at all things. ---------------------------------------------------------------------- desnudopenguino · 2019-08-29 19:42 wonderful things have been developed and implemented at different rates between projects, depending on their priorities. once things get solved, they usually propagate out to the masses (other os's), but that may not always be the case depending on the licensing, and focus of each project. then there are the personalities involved. what happens when you get a RMS, Linus, and TDR in the same room? heck, i run OpenBSD, FreeBSD, and DragonflyBSD, as well as Debian, Ubuntu, Alpine, CoreOS, and CentOS on my servers. would it be cool to have everything in one OS? sure, but at the same time that could lead to a lot of bloat, hits in app-specific efficiency. There's also the "too many cooks in the kitchen" analogy. if you took all the devs from all the projects, even on a specific thing like userland security, they'd probably end up messing each other up, or spending more time arguing about implementation than actually coding and solving problems. ---------------------------------------------------------------------- Bphag · 2019-08-29 19:45 U ppl all assume I'm a commie with monoculture.... ---------------------------------------------------------------------- TheRealLazloFalconi · 2019-08-29 20:20 It's not really. Each distribution has its own focus, and they develop different parts of the system at different speeds, but it's not like they're warring countries or anything. Ideas and code are shared between the distributions often. Just check the manpage for `mount_ffs(8)` on OpenBSD, it attributes NetBSD for that program. `pf(4)` was made for OpenBSD, but is available in Free and Net, and probably others. And those are just two I know of off the top of my head. This split isn't really ideological, it's mostly historical, but it lets each distribution focus on what's important to it. For FreeBSD, that's being the best general purpose OS possible, for NetBSD has focused on being highly portable, while OpenBSD has focused on security and code-correctness. Each distribution has benefited from having these tight focuses, while also getting code and ideas from the others that they didn't have to figure out on their own. In that respect, it's actually a *good* thing that they're all going in different directions. ---------------------------------------------------------------------- Bphag · 2019-08-29 20:23 the point of my analogies is simply resources being fragmented. valid points are brought up. but again. if i need to push my car. it helps to have more than one person. basic principle more is normally good (balance) comes but fragmentation is a problem i feel currently ---------------------------------------------------------------------- FUZxxl · 2019-08-29 20:29 It's not really fragmentation. The various BSD projects cooperate and share a bunch of code. They just have different visions of how the BSD kernel should be developed, so they all kinda do their own thing. There is no hostility or NIH in play. ---------------------------------------------------------------------- Bphag · 2019-08-29 20:34 I guess my last post was more in general than BSD specific ---------------------------------------------------------------------- AskJeevesIsBest · 2019-08-29 21:24 Because those three BSDs are different enough to warrant being mentioned separately. ---------------------------------------------------------------------- techsnapp · 2019-08-30 14:24 > simply resources being fragmented. What resources? ---------------------------------------------------------------------- DamienCouderc · 2019-08-30 15:19 Because, unlike Linux distributions that are based on the same kernel but different userland, the BSD systems are complete solutions with each its own kernel and userland. That said, they share some code. For example a new driver on one BSD can be adapted to work on another one. ---------------------------------------------------------------------- DamienCouderc · 2019-08-30 15:22 AFAIK Minix is not based on Berkeley. ---------------------------------------------------------------------- FUZxxl · 2019-08-30 15:44 Original Minix was not, but modern day Minix is a NetBSD variant. ---------------------------------------------------------------------- Kernigh · 2019-08-30 15:46 [Minix 3.3](https://wiki.minix3.org/doku.php?id=www:download:releaseno tes-3.3.0) has a "NetBSD userland". Minix has [NetBSD libc](https://gi t.minix3.org/index.cgi?p=minix.git;a=tree;f=lib/libc;h=02ec06526f36fc4 59cdee2c2e3953632806f8e52;hb=HEAD) and even [NetBSD kernel headers](ht tps://git.minix3.org/index.cgi?p=minix.git;a=tree;f=sys/sys;h=77092bd3 f6f7a0e3b3de36c13a8360b18f1ed2cb;hb=HEAD), though the kernel of Minix is very different from the kernel of BSD. See also ["MINIX 3 as a BSD"](https://2011.eurobsdcon.org/papers/gras/minix-bsd.pdf). ---------------------------------------------------------------------- DamienCouderc · 2019-08-30 17:07 Thanks for the heads up . ---------------------------------------------------------------------- laffer1 · 2019-09-10 23:02 >There's also MirBSD/MirOS which predates MidnightBSD and is a fork of OpenBSD. it targets very old hardware. ---------------------------------------------------------------------- Cynicastic · 2019-10-07 14:33 I would disagree. MINIX is a microkernel operating system, whereas the BSDs are monolithic kernels (as is Linux). A 'variant' of NetBSD would share major portions of kernel code, MINIX and NetBSD do not. That MINIX is able to use NetBSD userland programs does not make it a NetBSD variant.