NetBSD in 2003 - Annual NetBSD Status Report 49
jschauma writes "On February 7th, The NetBSD Foundation held it's annual meeting, during which
the developers discussed, among other things, how NetBSD progressed over the
last year and what things are planned for the comming year. The Annual NetBSD Status
Report summarizes this meeting and provides an overview of past, present
and future of the NetBSD Project, the NetBSD operating system, pkgsrc and the NetBSD Foundation both in general
and from the perspective of each group, to give users and people interested in
NetBSD insight into the project. Please join our mailing lists for participating in ongoing discussion, and see our web site for more information about the
NetBSD project, http://www.NetBSD.org."
good report (Score:5, Interesting)
One funny thing is that the pkgsrc section mentions a patch in the GNATS database to allow pkgsrc to run on GNU Hurd systems! (it already runs on GNU/Linux)
I doubt any established distros are going to ditch their existing package systems, but if a new distro was to begin (as a non-Debian testbed for GNU/Hurd) - it would be worthwhile evaluating the *BSD package systems.
Re:good report (Score:5, Informative)
Re:good report (Score:5, Funny)
NetBSD Status Report (Score:1, Interesting)
Re:NetBSD Status Report (Score:5, Insightful)
is there any reason to really use NetBSD over even FreeBSD unless you have some extravagantly ancient hardware?
Portable code tends to be rather clean code.
Clean code tends to run better and have fewer bugs.
Re:NetBSD Status Report (Score:4, Interesting)
Re:NetBSD Status Report (Score:5, Interesting)
Clean code tends to run better and have fewer bugs.
Yep. One of the more interesting ones to me was the new RC system, which when implemented on Vax was very noticably slower than the old one. I remember reading the whole thread on ways to resolve it. No flame wars, no little ranting "children", just a solid technical discussion on ways to fix it.
It points out things when something that maybe adds
Plus, having the same PCI card driver on your PC and your PPC Mac makes for easier fixes. Find a bug, fix it in one place, and all PCI platforms are fixed.
I run NetBSD everywhere I can. The people on the boards are generally always very "professional", I don't see people getting flamed for asking "stupid" questions, and in general I see a lot of thought going into the *design* before things get implemented. I always find the Linux approach of "just start coding, figure it out as you go" to be a recipe for bad things... like a VM change in the middle of the 2.4 chain. Sorry, I want risk, I'll run -current. I want stability, I run a normal release. Never gotten bit on NetBSD yet.
Re:NetBSD Status Report (Score:4, Informative)
Is Linux a 501(c)(3) like NetBSD? (Score:5, Interesting)
Linux isn't a company (Score:5, Informative)
Debian might fall into this category, but I wouldn't know about others
Re:Is Linux a 501(c)(3) like NetBSD? (Score:2)