Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:4955 comp.os.386bsd.misc:936 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!usc!yeshua.marcam.com!zip.eecs.umich.edu!caen!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc Subject: A merge of FreeBSD and NetBSD? (One person's opinion) Date: 10 Sep 1993 07:04:53 GMT Organization: Montana State University, Bozeman MT Lines: 66 Message-ID: <26p8ul$1eb@pdq.coe.montana.edu> References: <1993Sep8.231610.9740@ccds3.ntu.edu.tw> <CD190K.FwG@latcs1.lat.oz.au> <CD3JII.F5w.1@cs.cmu.edu> NNTP-Posting-Host: bsd.coe.montana.edu In article <CD3JII.F5w.1@cs.cmu.edu>, Robert Baron <rvb+@cs.cmu.edu> wrote: >My best advice is to just wait. I've heard on some other news >groups that FreeBSD and NetBSD are going to merge together soon. >I'd like to hear that confirmed here. You heard Jordan's words already on what is going/not-going to happen. >Well, which kernel do I hack to fix this? You hack whichever kernel you feel most comfortable in, and if you're code is good then both the NetBSD and FreeBSD folks will use it. I think the diversity has helped in many ways, as it has caused both groups to see things that the other group has been lacking in. Opinion follows: For one example of this. I believe the FreeBSD folks do a better job of packaging the release into a more palatable state for users to use, while the NetBSD spend more time trying to make the system into a more palatable system for developer's to use. It's just a difference in priorities. This isn't to say that the FreeBSD folks don't care what the system looks like, nor does it imply that the NetBSD folks don't package their system well, it's just that the amount of time spent in those areas are different for the different groups. Alot of folks may say, "Hey, you should get together, since you do different things, and together you could be a better team". That may be true, but because of those strengths, I (a lame kernel hacker by all standards) would never be allowed to touch the kernel again. Right now, I like being a little fish in a small pond. But, if I were to join NetBSD today, I (have been told) that I am to keep my grubby little fingers out of the kernel. So, I choose to stay where I only get yelled at for doing stupid kernel changes, (but at least I can make them. :-) So, more than just talents are at stake. I *like* playing with *BSD. I haven't gotten a dime since I started doing this when 0.1 was released, and I don't expect to get anything. So, when it starts becoming less fun, it's not worth it to me. A merge may happen, and then again, it may not. But, I don't think anyone is *losing* out except for those folks who think there has to be one unified release. If you want one unified release, buy BSDI. There release is a lot less fragmented and more stable than any of the free versions. In the meantime, I'm gonna have some fun, and learn on the way. If you like what I do, I'm more than welcome to share it with you, and even ask for your help, but you don't have to accept my work, or even like it for me to feel fulfilled. (But I *do* appreciate when people appreciate me and my work. :-) Off my soap-box and off to bed, Nate -- nate@bsd.coe.montana.edu | In the middle of it ........ again. nate@cs.montana.edu | Running/supporting one of many freely available work #: (406) 994-4836 | Operating Systems for [34]86 machines. home #: (406) 586-0579 | (based on Net/2, name changes all the time :-) -- nate@bsd.coe.montana.edu | In the middle of it ........ again. nate@cs.montana.edu | Running/supporting one of many freely available work #: (406) 994-4836 | Operating Systems for [34]86 machines. home #: (406) 586-0579 | (based on Net/2, name changes all the time :-)