View Single Post
  #1   (View Single Post)  
Old 12th July 2015
hanzer's Avatar
hanzer hanzer is offline
Real Name: Adam Jensen
just passing through
 
Join Date: Oct 2013
Location: EST USA
Posts: 307
Default *BSD Geneology and Future

Inspired by the thread: "Tor-0.2.5.12 can crash OpenBSD-5.7-stable"

I can see that DragonFlyBSD is a fork of FreeBSD 4.8. and OpenBSD was forked from NetBSD in late 1995. But that doesn't help much. The Wikipedia entry for Unix has this diagram (below) but it doesn't have adequate resolution[1] into the BSD subspecies (to help with my speculative thinking).

[1]: Information resolution. A higher visual resolution file is hyper-linked to the image.




Evolution of Unix and Unix-like systems

{A cut to the point}:
  1. I'm thinking about how some of the DragonFlyBSD capabilities and features might be useful to OpenBSD users, developers and engineers.
  2. I'm trying to get a probable architectural gist of how different the OpenBSD and DragonFlyBSD kernels are from each other, with an eye on engineering concerns.
  3. And I wonder if it would make sense, theoretically, if a new generation of OpenBSD had some of (or all) the Dragonfly developer-engineer-operator tools/features and some of (or all) the process-cluster capabilities/possibilities (including HammerFS if it makes sense).

...just for speculative fun (but good traction with reality). <- That reminds me of a joke:
The optimist says, “The glass is half full”.
The pessimist says, “The glass is half empty”.
The engineer says, “The glass is twice as big as it needs to be”.
Reply With Quote