Slashdot Mirror
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."
Manually creating a BSD disklabel is not to be taken lightly. If you're experienced you can do it, but it's very far from friendly. Anyone know if they've done anything to make it easier?
I am trolling
I can't wait to install this on all my servers with Adaptec RAID cards! Oh yeah... Damn dirty Adaptec! How's Theo's battle with them going, by the way?
Check out the Unofficial OpenBSD Bittorrent Page. If the torrent isn't here, it will be, soon!
Maybe yes
Fanboy.
William the Conqueror was a bastard too, and you'll notice that you don't have anyone on the English throne named Ethelbert or or Athelstan.
The world's burning. Moped Jesus spotted on I50. Details at 11.
.. the song is good.
"Systemagic" and "E-railed" are still my favorite ones. They went sillier after that. "The Ballad of Puffy Hood" is okay-ish, anyway.
"Systemagic" is really a nice song to chant, drunk, with nerd friends."Cracking the bedroom, HEY, cracking the vault, cracking the bedroom HEY SECURE BY DEFAULT. CAAAAAAAAAAAAAN'T FIIIIIIIGHT THE SYSTEMAGIC. ÜBER TRAGIC. CAAAAN'T FIGHT THE SYSTEMAGIC! SYSTEMAGIC!.
3.6 is stuck on 0.8
does my head in
I know a page where one can get a patchset against 1.01 and compile but I like my systems and vanilla as possible, ports & packages only, then I can reliably install a new box via script
There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
Soon it will reach the crucial watershed version 3.11
One of the new features is Intel Wireless support. I think that's very significant.
I must say that OpenBSD is a joy to work with. It is much cleaner and more consistently designed than everything else out there, including Linux. I have an old OBSD box that acts as a router and wireless access point, hasn't been updated in years, and I know I'll be giving it 3.7 to keep it up to date.
Now that it has Intel Wireless support, I might just switch to OBSD from Debian on my laptop.
Maybe. What color is your mouse?
This rating is Unfair ( ) ( ) Fair (*) Funny
Sigh... If only. Modding would be so much more fun.
If you want to know how to install OpenBSD, then you will *gasp HAVE TO READ!
n .html
http://www.wbglinks.net/pages/openbsd/installatio
ftp://mirror.sg.depaul.edu/pub/OpenBSD/3.7/i386/
http://www.openbsd.org/faq/faq3.html#ISO
You can't get them (officially). If it's that much trouble to do that once for an OS that is truly a joy to work with then you're priorities are screwed up.
Buy the official CDs and support the project, roll up your sleeves and make your own or use another OS. It's a free world.
Trolling is a art,
I haven't followed openBSD in quite some time and the answer wasn't apparent from the "features" link...but... Did Theo get around to supporting SMP yet? Given the avalanche of "cheap" multicore processors coming down the pike, SMP support sure would be nice.
Why was William the Conquerer standing on your ancestor?!?
Here's the plan:
1. Set up High Availability router with pfsync. (using computers rescued from the trash)
2. Set up a HA Network RAID system using DRBD or something similar. (using more computers rescued from the trash)
3. Build a Kerrighed or OpenSSI Single System Image cluster. (using the latest and greatest computers one can rescue from the trash)
4. ???
5. Profit! (and thus, have enough money to actually buy equipment)
I've already set aside Tuesday evening to upgrade my bandwidth throttling OpenBSD router. I set it up the day before 3.6 came out, so I didn't feel like upgrading until now. I'm tired of the typical hardware failures you tend to get out of computers people throw out (maybe that's why they threw them out in the first place) but mostly I'm looking forward to getting a learning experience hundreds of times more valuable (personally) than getting my MCSE 2003.
\/\/\/
Download the appropriate files from a trusted source and make an ISO yourself. I would never download a premade ISO without knowing who created it.
t ips/cdrom/
http://www.webengr.com/development/tools/openbsd/
I'm primarily a Linux user who does some OpenBSD on the side. I don't use GUIs that much, I configure everything by hand, and I do a lot of coding. I've written kernel stuff.
I can tell you that it is clear that OpenBSD is simpler, more consistent, and just plain makes more sense than Linux. Coming from Linux, OpenBSD is more than a joy to work with.
Linux is very ad-hoc. It just sort of "grew." It was developed in many places by many people, few of them working together with the big context of "the Linux system" in mind. The pace of development is very rush-rush-rush, and for example many times, the approach of the kernel developers is "let's shove this out to userland and let distributors worry about writing a script to make sense of it."
OpenBSD is the opposite. People working on OpenBSD core packages have a specific kernel, userland, config script, etc., etc. in mind. There is a concept of "the OpenBSD system" and it is fairly consistent. People are working together to acheive that goal. The pace of development is more relaxed, and the people working on the userland are some of the same folks writing the kernel. So you don't get the sort of ad-hoc interfaces that make no sense to anything but a shell script (i.e. iptables), you get something which at every level, the user can get an idea how it works (i.e. pf).
Or take wireless. Until recently I had a Linux box set up as a wireless access point. To do that I had to play around with different kernel modules, some of them shipping with the kernel, some of them not, ad nauseum until something worked. This was very annoying.
Awhile ago I put the very same wireless card in an OpenBSD box whose software had not been updated in a few years. The card just worked! Without rebuilding or changing any config files, the card was detected.
Then, I put a 2-line file in
The fact is, OpenBSD just does things the Right Way. People say OpenBSD's big strength is security, but that's slightly missing the point. OpenBSD's strength is correctness. From correctness yields stability, security, and all around ease of use.
You can call me a fanboy, but I say OpenBSD wins hands down against any Linux distribution, with the only exception being that Linux generally supports more hardware, quicker.
MOD PARENT UP!!! The parent makes a very good point. Correctness is an often-overlooked quality that should exist in every piece of widely-accepted FOSS. I hope for the day that high muckety-mucks in the FOSS community actually start caring about correctness.
I pity the foo that isn't metasyntactic
please support the project if you can by buying CDs and t-shirts, ...
I would love to, except Puffy the logo fish is horribly disfigured.
Linux shirts are out, too: Tux is overweight. No, I can't buy a FreeBSD T-shirt either: I live in Texas.
The DHCP client included has always worked. There was a problem in some Comcast markets including my own though. What you probably saw has been fixed, I believe as of 3.5 or 3.6. Essentially some markets were sending back DHCP responses out of spec causing the hosts client to disregard the information.
Then why didn't you go to the website and read the FAQ's? http://www.openbsd.org/faq/faq5.html#Flavors
The two newest releases are supported and a new "stable" version of the OpenBSD is released every 6 months. So, each release of OpenBSD is supported for one year.
-- "At Microsoft, quality is job 1.1" -- PC Magazine, Nov. 1994
But OBSD is more problematic on my web/mail server. The ports collection is nowhere near as comprehensive as FreeBSD's (or Debian & Gentoo for that matter) and so you'll likely scrounge for upstream versions of more obscure packages.
Worse, OBSD's Apache is stuck at version 1 (Theo has issues with the Apache 2 license) and more and more software wants Apache 2. I guess you can fix that, but it's back upstream you go me bucko. Oh, and OBSD's default Apache installation is chrooted, which you'll probably defeat after your first CGI integration experience.
I like OBSD a lot, and I don't mean to suggest that it's only good for embedding in a router. But if your application requirements are remotely bleeding edge (and you want to save yourself some work at the risk of some unquantifiable security exposure) then you might want to look elsewhere.
You can call me a fanboy, but I say
OK, you're a fanboy.
Selling CDs is one of the ways that the OpenBSD project is able to make money, and as far as I know, they don't provide checksums for the general public to verify the integrity of downloaded .iso's.
So by all means feel free to download some J. Random bitTorrent ISO of OpenBSD, but keep in mind that you have no way of knowing if it's been trojaned, root-kitted, or otherwise compromised If you really need a free install, just use the freakin network floppy. It's super easy, and you download directly from official OpenBSD mirrors.
Causation can cause correlation
My setup: I use OpenBSD 3.6 (no upgrade for me yet, mirrors are totally) as a firewall and server (NFS, web, SSH, DHCP, that sort of thing). I use Debian-testing as a desktop on a different machine.
The documentation is second to none. That includes all the Linuxes I've tried as well as the BSDs. The fact that it's actually worth reading the docs means you do it early and often, which is nice.
Installing things out of ports is about as easy as any of the other good package managers I've used on Linux. The one thing to be aware of is that pkg_add can take a filename argument in the form of a URL to the FTP site. It's better to do that because it can resolve dependencies from the FTP site instead of you having to download them manually.
DO NOT ROLL A CUSTOM KERNEL. The generic one supports virtually everything that has been tested properly. If you have a problem with generic, report the bug because they'll want to fix it.
The firewall, PF, rocks. It's easy to set up and very powerful.
Overall, the differences between distros are as big as the differences with OpenBSD. I had to go through a lot of distros before I found the one I was happy with, and if you can wrap your brain around, say, both Slackware and Suse, you'll be fine.
I rarely criticize things I don't care about.
It is very easy to install OpenBSD without any official ISOs.
Method 1:
Download the boot ISO (there is a boot ISO available for download), burn to CD, boot, set up your hard disk, then tell it to do an FTP install.
Method 2:
Download the boot ISO, and also download all the basic packages (the ones in the form of base37.tgz etc.) Burn the boot ISO to one CD, then create a normal CD containing all the packages.
Boot the bootable CD, swap the CDs over, then tell it to install from CD.
Using the two CD method, I can go from a blank computer to a working OpenBSD system in less than 15 minutes.
Oolite: Elite-like game. For Mac, Linux and Windows
Back when SAMBA was in 2.0 or thereabouts I looked at the samba.org site for the first time and found a bit on how the name "samba" came to be. The original intention was to simply call it SMB but there was concern about using a registered name so the name SAMBA was arrived upon by grepping a dictionary file based on the letters SMB in that order.
It was certainly not the result of an attempt to come up with some cute name for the software.
I think the point is to get "lamers" (MSCs maybe?) to be willing to install OpenBSD. They have to be willing to try it first, then you can criticize them.
I _was_ a [Slackware] Linux user for quite some time between around 1995-2001. I discovered OpenBSD because all my 'elite' friends were using it or FreeBSD. I did my homework and chose OpenBSD for my firewall, web, dhcp, nntp, db, app server.. I started to use it at home and was instantly impressed. The 1st time I ever touched it I had my server up in 30 minutes!! It seems more to be more mature and consistant. It is well documented and works great! I haven't used Linux since ;p Not to say Linux doesn't have it's place, but it's not with me right now. One thing you'll find though, you usually won't we using '0day' software. This is because it takes time to create something of quality, that has been checked and balanced.
We use it at my work now, we have about 10 OpenBSD servers at different locations all over North America, we don't need the newest software, we have no problem waiting a few months sometimes. We need something that is easy to manage and works consistantly.
OpenBSD!
OpenBSD always supports the current release, and the previous one. This means it now supports versions 3.7 and 3.6
You should note however that the OpenBSD systems are very easily upgraded from the install media. Simply choose the upgrade option and then follow the simple instructions to make other changes.
Remember though that only sequential updates are supported. Example 3.6 -> 3.7, if you're upgrading from 3.5 you'd need to: 3.5 -> 3.6 -> 3.7
Hope that helps you,
Tim
The first time I installed it, it took a few attempts. Had to figure out the networking, etc. (I had problems with Redhat 6.2 as well, the installer was great, but no tools that I could find to edit them until I learned my way around the text files).
:)
However, after 3 attempts when we got the hang of it, I looked at my partner (it was our first webserver for our little company) and we were like COOL. Once you get the handle of the installer and ports, its a DREAM, much EASIER than the Redhat what do I want and where is it problem.
That said, RHEL 4 is pretty slick, but nowhere near as impressively simple as OpenBSD + Ports. The installed OpenBSD system is SO FUCKING clean its not funny, and then you add the few ports, nice and customized, that you want.
One day I build 4 OpenBSD machines. Build the (customized) packages on one and distributed, and it was REALLY, REALLY, REALLY nice).
It's a great system, but you gotta really be a Unix-lover. If you want the click-click install, the Linux distros are great, but with OpenBSD I understand what is going on with my system.
That said, you can just TRY to get my OS X Powerbook away from me...
Alex
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!"
He didn't bother to check what the torrents are. They are a mirror of what is on the official ftp sites. I just downloaded them and verified their MD5 checksums with the MD5 file on a second level mirror.
But you don't speak for everybody. I've found no problem with getting help for OpenBSD (I recommend www.bsdforums.org). I think you just need to make some effort to solve the problem yourself first. I can quite understand why people get annoyed with newbs who ask facile questions because they can't be bothered to try the most basic steps themselves. That's hardly unique to OpenBSD users though.
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.
See? I told you. I told all of you. I told you FOUR YEARS AGO but nobody believed me.
Now take a look at the OpenBSD web page. Just try and tell me the fish didn't finally come out of the closet with this release. The raised eyebrow, the pouty lips, the rainbow background. I told you.
Sigh, I hate people.
I don't even understand why you're fighting with this guy. I use OpenBSD, you use OpenBSD, we both think it's great. If they want to troll in OpenBSD related slashdot threads that's their social problem, not ours. I'd prefer if the trolling/negative crap went ignored and got modded into oblivion.
-If God wanted people to be better than me, he would have made them that way.