OpenBSD Review at DistroWatch
jpkunst writes "Robert Storey at DistroWatch com has written an in-depth and favorable review of OpenBSD: OpenBSD - For Your Eyes Only. 'The first OpenBSD memento I ever saw was a T-shirt with a picture of a cop chasing a script kiddie. That image remained etched in my mind for well over a year before I finally got my hands on a copy of this fine OS. Now that I have it installed on my machine, I only wonder what took me so long.'"
Now that OpenBSD is implementing SMP support, I wonder if (more?) high-end servers will start running it.
tasks(723) drafts(105) languages(484) examples(29106)
I learned my packet filtering basics on FreeBSD. I've looked at ipchains and iptables/netfilter, but the ipfilter/pf packages just seem to be the packages that best encompass my beliefs of how firewalls should be constructed. I've always liked the syntax and organization; I suppose that's one of the major reasons I've stuck with FreeBSD for so long.
OpenBSD felt "more" secure than FreeBSD, but in terms of desktop use, FreeBSD just offered more. I'll run OpenBSD on my servers, but for my desktop I want FreeBSD.
non-trivial to whom? as a linux dork maybe 5 years ago, i installed BSD on a friends laptop without ever reading a single thing about BSD. He asked me if I would, then handed me the cd's. A little while later it was up and running.
non-trivial to MS-Windows users, Mac users, and Linux initiates maybe. But 5 years ago, I was barely above the status of linux newb. Ok, so it wasn't exactly trivial to do at the time, but easy enough to do without documentation.
Still, your point is well taken.
Keep in mind that all the BSDs share code with eachother. FreeBSD and NetBSD have imported OpenBSD's PF. NetBSD has imported OpenBSD W^X. All of the BSD's share various internals and device drivers.
There have been 300+ committers to FreeBSD in the past year. I'm guessing Open/Net/DragonFlyBSD have 1-3 dozen developers each. Apple has a bunch of developers. All combined, the BSDs are doing pretty good.
Since each BSD has a different focus, the developer has a choice of which fits their style best.
I have found OpenBSD to be trivial to install on one platform out of the three I have tried. When installing OpenBSD on an UltraSparc 10 there was no issues what-so-ever and everything might as well have been point and click. The x86 family of processors and the Power PC processors, however, were an entirely different story and headache all together. You'd think that with OpenBSD talking about how secure it is and how great it is, that you'd see one of those developers make some user friendly installer in order to increase the popularity of the operating system. Personally I believe that more people running more secure computers is a good thing, but thats just me and I ramble.
The best example of a stupid GNU man page is the GCC man page. It's downright insulting: "If we find that the things in this man page that are out of date cause significant confusion or complaints, we will stop distributing the man page." In other words, don't complain or they'll take it away!
Don't blame me, I didn't vote for either of them!
man does not come with its own viewer. By default, man pages are viewed with 'more', which is the behaviour you see in Solaris.
Apparently, under BSD, the pager has been set to 'less', which supports the vi commands.
Under Solaris, I try setting the PAGER environment variable to '/usr/bin/less -isrm' or something similar in your startup scripts. This will change man's behaviour.