Live data from Hacker News

The BSD family tree

github.com

31–40 of 59 posts

Re: The BSD family tree

#31
post #5

Earlier quoted context omitted.

Along with DEC Ultrix, and (kind of OSF/1, Tru64, etc). There were lots of other proprietary BSD based systems in the 80s as well.

Ultrix forked off BSD 4.2. It was the Unix I learned first, and working with it when the civilized world was working off BSD 4.3 variants made life really awkward.

Ultrix was my 2nd unix, after SunOS 4.1 on a massively over-committed Solbourne. I preferred Ultrix just because the machines were in a closed lab, and "faster" because there weren't 300 undergrads trying to compile their projects all at the same time on an overheating Solbourne...

Re: The BSD family tree

#32

This is missing a lot of BSDs. Now granted some of them are dead, some inactive, some just missing. The ones I can think of off the top of my head: PC-BSD/TruOS, MirBSD/MirOS, Bitrig, HardenedBSD.

Most of those are just FreeBSD. Pulling from the FreeBSD tree for their base.

Re: The BSD family tree

#33

Heh. Between NetBSD 1.4 and Darwin/Mac OS X there's an entry that just says "(?)". It's probably pretty well-known that question mark is NeXTSTEP, which was built at NeXT, the company that Steve Jobs founded after he left Apple the first time around. NeXTSTEP was built around BSD mostly because of Avie Tevanian's involvement in CMU's Mach kernel project.

I was wondering about that; didn't realize it was NeXT. A friend of mine still has his original NeXT box for the short time he worked on it. I was also surprised at the origins of DarwinBSD. I never really looked up the history and didn't realize it forked some of the code off FreeBSD. It's interesting to note that the PS4 OS is also a forked FreeBSD variant as well.

As is the Nintendo Switch.

Re: The BSD family tree

#34

It is funny.. I was just combing through old BSDs earlier today. I'm giving an internal talk next week about some changes I've been making to mbufs, and I was trying to find out when mbufs were introduced. They've been around since before I wrote my first FreeBSD, Tru64, and BSDI drivers in the 90s. The earliest I can find is 4.1c from 1983, but that looks more fully formed that I expected. And there is a fragment in…

3BSD-4.2 sounds about right -

My thinking w/o references (enthusiast but was not 'there' at the time) is that this was introduced with either the 32Bit VM system, FFS implementation, or BSD network starck - probably the McCusick FFS papers [ed: are worth a read].

Really it's kind of nuts how 'usable' and 'current' a load of 4.3BSD on a VM load feels out of the box.

Re: The BSD family tree

#35

Heh. Between NetBSD 1.4 and Darwin/Mac OS X there's an entry that just says "(?)". It's probably pretty well-known that question mark is NeXTSTEP, which was built at NeXT, the company that Steve Jobs founded after he left Apple the first time around. NeXTSTEP was built around BSD mostly because of Avie Tevanian's involvement in CMU's Mach kernel project.

I was wondering about that; didn't realize it was NeXT. A friend of mine still has his original NeXT box for the short time he worked on it. I was also surprised at the origins of DarwinBSD. I never really looked up the history and didn't realize it forked some of the code off FreeBSD. It's interesting to note that the PS4 OS is also a forked FreeBSD variant as well.

Switch also forked

Re: The BSD family tree

#37
post #17

Heh. Between NetBSD 1.4 and Darwin/Mac OS X there's an entry that just says "(?)". It's probably pretty well-known that question mark is NeXTSTEP, which was built at NeXT, the company that Steve Jobs founded after he left Apple the first time around. NeXTSTEP was built around BSD mostly because of Avie Tevanian's involvement in CMU's Mach kernel project.

This is a bit complicated because NeXTstep didn't use a BSD kernel, using the Mach microkernel instead. Much of the layers above were taken from BSD, so it definitely had a BSD feel to it, but it wasn't a BSD kernel so maybe couldn't really be called a BSD derived OS?

Mach did not separate BSD into userland (like a true "microkernel") until 3.0. NeXTSTEP did not use Mach 3.0. Mac OS X still has the BSD code in the kernel.

Re: The BSD family tree

#38

Earlier quoted context omitted.

I was wondering about that; didn't realize it was NeXT. A friend of mine still has his original NeXT box for the short time he worked on it. I was also surprised at the origins of DarwinBSD. I never really looked up the history and didn't realize it forked some of the code off FreeBSD. It's interesting to note that the PS4 OS is also a forked FreeBSD variant as well.

Switch also forked

Still haven't seen anything showing this, including the license for the FreeBSD kernel can mean a lot of different things. Windows did/does ship with it, I wouldn't call it a fork.

Re: The BSD family tree

#39

Earlier quoted context omitted.

I was wondering about that; didn't realize it was NeXT. A friend of mine still has his original NeXT box for the short time he worked on it. I was also surprised at the origins of DarwinBSD. I never really looked up the history and didn't realize it forked some of the code off FreeBSD. It's interesting to note that the PS4 OS is also a forked FreeBSD variant as well.

Switch also forked

Nah, it turns out the switch is using an OS derived from their custom, proprietary 3DS OS.

They run the FreeBSD network stack in another process in user land, hence the copyright claim.

Re: The BSD family tree

#40
post #33

Earlier quoted context omitted.

I was wondering about that; didn't realize it was NeXT. A friend of mine still has his original NeXT box for the short time he worked on it. I was also surprised at the origins of DarwinBSD. I never really looked up the history and didn't realize it forked some of the code off FreeBSD. It's interesting to note that the PS4 OS is also a forked FreeBSD variant as well.

As is the Nintendo Switch.

Nah, it turns out the switch is using an OS derived from their custom, proprietary 3DS OS.

They run the FreeBSD network stack in another process in user land, hence the copyright claim.

Post reply on HN