Nature of BSD operating system providers

My hunch: The statement "DragonflyBSD is an outstanding OS for HPC applications" is complete nonsense, and based on wishful thinking
Let's suppose it is true, then the gain by replacing the current infrastructure with this new one needs to justify the downtime, training costs, ... The better we get, the harder it will become to gain from such a switch as the possible gains get smaller and the cost gets higher.
 
Let's suppose it is true, then the gain by replacing the current infrastructure with this new one needs to justify the downtime, training costs, ... The better we get, the harder it will become to gain from such a switch as the possible gains get smaller and the cost gets higher.
In the scenario that I “dreamt of” with LLVM Flang being used on DragonflyBSD, training costs will apply mostly to administrating OS (which is not hard to grasp), researchers are already familiar with NVIDIA/PGI
 
Can you point to some benchmarks comparison, please?

Also, what we talked about here (please see few posts up) is that LLVM is needed for Flang, and Flang is based on the NVIDIA/PGI commercial compiler, which is important for HPC environments.
In NetBSD I made the mistake to switch to Clang and building world takes a lot of time. Switched back to GCC and it's faster. Compiling DragonflyBSD is a breeze. I wish FreeBSD could be compiled faster like this.
 
In NetBSD I made the mistake to switch to Clang and building world takes a lot of time. Switched back to GCC and it's faster. Compiling DragonflyBSD is a breeze. I wish FreeBSD could be compiled faster like this.
Given that running world binaries does not take up much time anyway, esp. for HPC, you may switch to -O1 and try again. If compiling fast is your goal, that is. Once upon a time kernel builds were using -O0, if I remember correctly.

In the scenario that I “dreamt of” with LLVM Flang being used on DragonflyBSD, training costs will apply mostly to administrating OS (which is not hard to grasp), researchers are already familiar with NVIDIA/PGI
That is only a fraction of the training involved. You also need to educate the higher ups. That will cost you.
 
That is only a fraction of the training involved. You also need to educate the higher ups. That will cost you.
Well, tell to higher-ups that better number crunching will save the $ and at the end of the day get them bigger bonusses – that’s all of the edu they’ll need 😉

Sorta how Unix was born when Patriarchs fooled Bell that they need new PDP for the legal dept to write forms faster 😁

No wonder I’m not a successful businessman 🤭
 
Well, tell to higher-ups that better number crunching will save the $ and at the end of the day get them bigger bonusses – that’s all of the edu they’ll need 😉

Sorta how Unix was born when Patriarchs fooled Bell that they need new PDP for the legal dept to write forms faster 😁

No wonder I’m not a successful businessman 🤭
You need to take this into account:
  1. recompile all software
  2. validate all software
  3. install new software
  4. validate installation
  5. train users/admins on small differences
All that for a what? 0.5% improvement? At the risc that everything falls flat on its face on any step? And of course, nobody has been fired for buying IBM (in the past).
 
You need to take this into account:
  1. recompile all software
  2. validate all software
  3. install new software
  4. validate installation
  5. train users/admins on small differences
All that for a what? 0.5% improvement? At the risc that everything falls flat on its face on any step? And of course, nobody has been fired for buying IBM (in the past).
I get your point, and it’s valid one from business perspective, because business is making their own $’s which they can burn as shareholders want, but from pure research perspective, which depends on other people money is not so simple if they look ahead.

Who can guarantee them that companies that provide infrastructure and software will not get into sold-resold-bust cycle tomorrow?

I know, it’s almost unimaginable today to think that Intel or Nvidia or whoever is providing them with tools will go down tomorrow, but look at DEC or Sun?

Life happens; FOSS helps.
(I should make t-shirt for myself with that slogan 😉)
 
Isn't IBM already sort of rocking a bit? Having to deal with massive cuts?

(Purely off of random yt videos, do not quote me)
 
Isn't IBM already sort of rocking a bit? Having to deal with massive cuts?

(Purely off of random yt videos, do not quote me)
IBM and Oracle are entangled with so many governments around, that they will probably last until end of this civilization cycle.
 
SecBSD - Security BSD for network security testing based on CURRENT OpenBSD released monthly. It's self described as "for Ethical Hacking & Pentesting." It's only available for the AMD64 architecture.

Started in December 2018; first release in February 2019. Its first release was announced on UnitedBSD.com. This OS is based worldwide. It's maintained by Dark Intelligence Team.

There's an episode from the podcast Hacker Talk interviewing a developer to SecBSD BSDBandit from September 2022: https://www.jiosaavn.com/shows/secbsd-the-penetration-testing-distribution-for-the-bsd-community-|-bsdbandit-on-hacker-talk/1Gk7AV-EH-E_. He started developing for SecBSD later in 2019.

Other BSD
DamnSmallBSD is a BSD operating system, which looks like is being revived. https://damnsmallbsd.org/ also keeps track of other BSD operating systems, including defunct ones, especially lightweight BSD's.

NetBSD based
Hardly anything is based off of it, except OpenBSD. There are a few commercial operating systems based on NetBSD. https://www.netbsd.org/gallery/products.html

RiscOS - while this operating system for Arm64 didn't originate off as a BSD, it has imported kernel components and other parts from NetBSD. Open sourced in 2018.

OS108 - open source operating system based on NetBSD.

FDGW - is a Japanese derivative of NetBSD for floppy disks which last major activity was in 2013. It's still available.

smolBSD - a tool to create custom light VM images from NetBSD.

BlackBSD, EdgeBSD, NetBSD LiveCD, and Jibbed are defunct or no longer maintained operating systems that were based on NetBSD. PocketSan is an operating system with major activity from 2 decades ago hosted by DamnSmallBSD.

Defunct OpenBSD based
MirOS was based on OpenBSD. Bitrig, AErieBSD, LibertyBSD, OliveBSD, Anonym.OS, isotop & ekkoBSD are other defunct operating systems that were based on OpenBSD. MicroBSD was a tool to make customized OpenBSD installs.
 
Sometimes, I question the wisdom of creating a brand-new OS that is aimed at a specific audience like FortranBSD.

That's because most of the time, any of the existing OS'es can be set up with a toolchain for the specific task. Linux, BSD, Apple, Windows - all of them can be set up for a specific task, even knitting your socks or playing with Google's Gemini API.

Having toy OSes around does have a purpose - they are a valuable teaching prop.

But creating a brand-new OS just because of a personal itch - I just don't see it as 'cool' any more. There are already way too many options out there. Being able to do research and problem-solving using the existing options - I think there's a lot to be gained from that.
 
Sometimes, I question the wisdom of creating a brand-new OS that is aimed at a specific audience like FortranBSD.
Boffins are usually not admins; I didn't check FortranBSD, but if everything is set up for them to install it and start coding in Fortran, I see merit in that.
 
FortranBSD, but if everything is set up for them to install it and start coding in Fortran, I see merit in that.
The author specializes in kernel modifications for improved performance. Based on that, I guess that's what he did with FortranBSD. It would make more sense for Fortran to have a special bootstrap, and make it a wider purpose math processing operating system. Let Python and other mathematical languages have a bootstrap there too.

As for SecBSD, lots of people are looking for that in an operating system. It looks like it has the maintainership to thrive.

Zrouter, because there's no other specialized router/NAS distribution for Arm64. There's NetBSD, OpenBSD and FreeBSD, and not much else, but these aren't specialized for router/NAS/firewall. This OS needs more attention for help on maintenance and upkeep for survivability

Not much is known for running on NetBSD, so I gave it attention on defunct less well known operating systems based on it. Also, didn't realize that MirBSD was based on OpenBSD.
 
I have to ask, what's the point of setting up an entirely separate OS?

If you wanna patch the kernel for improved performance, why not just follow the FreeBSD kernel development, and create a script to automate applying that specific patch? That is a lot less work than trying to replace stuff like the pkg infrastructure, making separate announcements about releases, worrying about staying up to date with security patches, and the like. FreeBSD has all those details and more already ironed out.

No need to completely reinvent the wheel just because the default color is black and all you want is to paint it red. If red paint is all you can do, what about the rest of the process of even making the wheel? Like factory, raw materials, equipment, and lining it all up, from raw materials into hands of the customer? How long can you keep that going?
 
GhostBSD had its first virtual GhostBSDCon which is also for other BSD's on the desktop in March 29th, 2025. There are few materials from this on GhostBSD's forums and on its official YouTube channel. This virtual conference presentation occurred at the Berkeley Forest: FreeBSD Lodge which is a fictional virtual location. There were a few mentions on these forums of Berkeley Forest and its virtual BSD library. Here's one mention of Berkeley Forest on these forums: https://forums.freebsd.org/threads/invitation-to-visit-berkeley-forest-and-the-bsd-library.97402/. The participation of GhostBSDCon was announced since last January, and the call for papers occurred from January 14th, until February 21st. GhostBSD intends to have a more prominent role in a desktop BSD conference in the future.
As a note: GhostBSD wasn't based on FreeBSD for a few years: when TrueOS went defunct, GhostBSD became based on FreeBSD again.


MidnightBSD wants to incorporate a nonprofit foundation to support it,* but it doesn't have the user base and donations to justify doing so at the moment.


Not sure if I wanted to write this, but don't hold your breath on DragonFlyBSD forming a nonprofit foundation behind it.


EdgeBSD was a router based BSD derived from NetBSD. While it's no longer developed, it still has a small IRC community, and still has a repository available: https://github.com/edgebsd. It was announced at FrOSCon in 2013 in Germany: https://programm.froscon.org/2013/system/attachments/259/original/edgebsd.pdf.
 
CheriBSD would be worth mentioning for Cheri-capable CPUs.
Unfortunately, I don't have any computer with the fully supported architecture.

I believe this kind of hardware-based (or at least hardware-assisted) approach is the way to go for ALL CPUs for memory safety.
 
I myself never tried, but if DragonflyBSD has full gcc in its kinda ports, it shoud have gfortran.
And, also I've never tried (I dislike FORTRAN except for number crunchers, and I have no needs for number crunchers / HPC), another option for LLVM would be lang/lfortran.
Yeah, gfortran is compiler in FortranBSD. When I said "dreamt of" I was referring to what I said here, in #17:
I think that will interesting to watch what will happen with FortranBSD by Mohamad Badiezadegan (mbzadegan).
Quote: “FortranBSD, a new operating system designed specifically for Fortran developers who demand high-performance and seamless multithreading support. FortranBSD is based on DragonflyBSD which is an outstanding OS for HPC application” /q
It will be very interesting to watch it when/if DragonflyBSD gets better LLVM support, and LLVM Flang gets production ready status (Flang is an open-source Fortran compiler based on the NVIDIA/PGI commercial compiler).
Boffins gonna make those supercomputers full of Nvidia cards go brrr on BSD 😎
 
The era of 16/32-bit task-specific firmwares for phones and TVs and digital watches and calculators is over. Back then, it was cool if you could write a game that could be played on a TI-85 or on an HP 50g (if anyone remembers those calculators from 1990s!).

Samsung is trying to pass of Tizen as task-specific, like for a refrigerator or for a laundry machine, but it's clear as day that it's Android-based - which in turn is Linux-based... Microsoft's XBox is merely a version of Windows modified to suit specific hardware. And even digital watches that used to have their own firmwares - even those are now flashed with a version of Android and iOS. Even for cheap off-brand and knockoff smartwatches, firmware of choice is Android, rather than a separately maintained OS.

My point is, even the big shops that do have the money, metal, staff and expertise to actually pull off setting up a separate OS altogether, even the big guys are saying 'Not worth the trouble' to the very idea of setting up an entire separate OS for a specific task. If somebody can patch an OS to perform better in certain tasks - that's great. But for rank-and-file enthusiasts, creating a whole separate OS is not the easiest thing to get off the ground, much less maintain. Even the TempleOS guy only managed to keep up the efforts for just a few years. He had the programming skills, but not real-life survival skills.

Well, HP still sticks to in-house development of firmwares for the printers they make, and no, you can't install an app from Google Play on your AIO printer. However, HP is really an exception rather than the rule.
 
It seems I've forgotten about an implementation of NetBSD with the Minix3 kernel: Thread netbsd-based-system-using-minix3-microkernel-announced-by-andy-tanenbaum.62501.
It was a temporary version made by Vrije Universiteit (in Amsterdam). This implementation didn't seem to have a name, but it's cool that it was proven that could be done.

This was showcased in BSDCan 2015 & presented by Andy Tanenbaum.
It had many of the same hardware limitations which Minix3 had, likely lack of wireless and USB support.
 
NetBSD was started 1993/04 and FreeBSD later on 1993/11.
You're right. I don't remember if I was looking at when 1.0 was released in 1994, or if I just messed up. NetBSD's first version 0.8, but the first release is what matters, as it's subjective to anyone, including those who released it, what makes it to be 1.0: https://www.netbsd.org/about/history.html. NetBSD was always the first to have formed a foundation. Edited it, to adjust to that, as it's information I intended to have there then.

FreeBSD's first free release was version 2.0. Also: Thread history-of-freebsd-part-1-unix-and-bsd.77407.

Besides that - thanks for gathering all this stuff in one place.
Yw. I like putting things together for organizing concepts.
 
Another convention I've missed, but is no longer active: PkgsrcCon. It has been hosted in cities across Europe, and the last conference was in 2019. The first one was in 2004 in Vienna.
This is in addition to past Pkgsrc hackathons, likely hosted by the Swedish community which uses NetBSD: https://mail-index.netbsd.org/pkgsrc-users/2007/10/28/0001.html.

Pkgsrc also has an IRC channel on Libera.Chat: #pkgsrc.

Pkgsrc has used Fossil and CVS before for Version Control Systems.
 
Back
Top