Slashdot Mirror
NetBSD Status Report January - March 2005
jschauma writes "The NetBSD Foundation published its first quarterly
status report in 2005, covering the months January through March of 2005.
Among many other things, this status report covers the addition of TCP/SACK
and PAM support, the opening of the Foundations Online Store, the new stable
pkgsrc branch and various port-specific items."
http://www.daemonnews.org/200104/bsd_family.html
That's exactly the point of Xen. As it says on the Xen page, each domain is a completely separate virtual machine. So no only are you "jailing" the web server application, your jailing the entire OS image that it is runnning on. In this way it's just like VMware. The difference is that by requiring some small changes to the guess OSes, Xen can avoid needing to trap and emulate any protected instructions which results in much better performance.
there's also Darwin, which is the BSD-core of Apple's Mac OS X. Darwin is Open Source, though Apple is pretty finnicky about who they let contribute for obvious reasons (it's the core of a commercial Operating System). There's also OpenDarwin which is basically a community controlled branch of Darwin that occasionally serves as a testbed for standard Darwin features. Darwin is based on a Mach 3.0 microkernel, though it's more of a hybrid than that simplistic description would suggest.
BSD/OS is commercial.
FreeBSD _was_ performing very good on x86 hardware (only), FreeBSD 5.x is often slower on single-cpu machines because they try to improve SMP performance and functionality. 5.x supports quite a few architectures aswell.
DragonFly is a fork of FreeBSD 4.x, better performance than FreeBSD 5.x but not for production (if you ask them), if I've understood everything correct their goal is among others fast IPC and beeing able to run the OS on a cluster. Right now they are going x86 only I think.
NetBSD is about portability, clean code and correctness, earlier it was slower than FreeBSD but it has catched up a lot with 2.x.
OpenBSD is a fork of NetBSD which centers about security, althought many people are sceptical.
Personally I've got more and more tired of OpenBSD, really like NetBSD and are very intrested in what will become of DragonFly. If you just want something which works as a desktop FreeBSD might still be your best bet thought.
The problem is that even the loopback interface can be sniffed on (usually only by root, admittedly, but still) so any authentication happening with sockets is going to be a bit on the dangerous side. Libraries are still in the protected address space of their host process, so there's no problem. I like daemons, don't get me wrong, but I wouldn't trust one to handle authentication - especially since there's no real advantage to it.
Now, if we were talking about network authentication with decent SSL or other encryption between daemon and client, that I could agree with. But I believe that's already been done in other ways...
Sam ty sig.
Socket traffic between processes on the same machine doesn't have to go over the loopback interface.
(Hint: "UNIX-domain sockets".)
You can use pkg_add on any supported NetBSD platform, assuming someone built a package. Otherwise, you'll have to download pkgsrc.tar.gz, untar it, and use "make && make install"