OpenBSD 3.7 Released
pgilman writes "It's official: OpenBSD
3.7 has been released.
There are oodles of new features, including tons of new and improved wireless
drivers (covered
here
previously),
new ports for the Sharp
Zaurus and SGI,
improvements to
OpenSSH,
OpenBGPD,
OpenNTPD, CARP, PF, a new OSPF daemon, new functionality for the already-excellent ports & packages system, and lots more. As always, please support the
project if you can by buying CDs and
t-shirts, or grab the goodness from your local mirror."
Check out the Unofficial OpenBSD Bittorrent Page. If the torrent isn't here, it will be, soon!
Yes, people who say OpenBSD is hard because of the non-GUI installer just end up making themselves look lame. OpenBSD really is not that hard to install, and I actually prefer it to Red Hat's do-as-we-want-you-to-do installer.
It is confusing when you come from i386 and have used Linux. It was, at least for me, quite confusing the usage of the word "partition".
To simplify, on Linux on i386 for each file system there will be a partition (DOS type). On BSD you commonly create a primary DOS parition using fdisk, and then use disklabel to create different filesystems on that particular DOS partition. "Primary" beacuse BSD may only boot from a primary DOS partition (at most four of those).
Now, when you enter fdisk you are asked to "parition" your harddisk(s). Then you enter disklabel and are asked to create new partitions. WTF? I just did that! Enter the term "slice" that is not quite the same across the BSD. Erh, you won't see the word "slice" in the man pages, though.
Not sure if OpenBSD 3.7 still have this usage of partition, though.
In any case, I'm a happy user of OpenBSD since 3.2/3.3.
3.7 comes with 1.01. Current version is 1.0.4.
Expanding on a previous comment: A 1970's IBM project, System/R, developed "Structured English Query Language" shortened to "SEQUEL", and later changed to SQL. The CORRECT pronunciation of "SQL" is still "sequel". Saying "ess kew ell" is the sign of a newbie. Not that there's anything wrong with newbies, until they get fresh about things they don't know about. See e.g. http://www.faqs.org/docs/ppbook/c1164.htm
Even the packages that ARE from external sources are better integrated.
(By the way: for every Linux distro I've used, the default kernel always lacks something or doesn't work in some way, and I always end up building a custom one. With OpenBSD, the default kernel is much better than any default Linux kernel I've seen.)
If you disagree with my accessments on integration, I encourage you to look at a base OpenBSD system, and a Debian base system, compare the two, and I think it will be very clear which is better integrated. Look, particularly, at the headers, and the interfaces between kernel and userland, some of the manpages for kernel features, and this is easily apparent.
And remember, I'm writing this all as a Debian user. I use Debian much more often than I use OpenBSD.
As for your last argument, about how many people use Linux: This proves nothing. I can just as easily say, "Look how many people use Microsoft Windows! Obviously, it must be better!"
I don't know if you are really aware of it, but note that the link you gave mentions the story behind the acronym SQL, which certainly used to be SEQUEL before and had to be changed for legal reasons, but doesn't mention the pronunciation of SQL at all. Actually it _is_ "Es Queue El": http://en.wikipedia.org/wiki/SQL.
If you read the documentation of popular relational databases, it's quite possible that you find a paragraph regarding the pronunciation, and in that case you'll find they follow the ANSI convention. [1] [2]
I know when I started using RDBMs years ago I read about it, and ever since whenever I see someone pronouncing SQL as "sequel" the first thing that comes to my mind is "newbie". I suspect from now on one more thing will come to mind: a prick who wants to sound clever when he's actually an ignorant.