Slashdot Mirror
OpenBSD 3.2 Available
fredrikv writes "Right on time, the files defining OpenBSD 3.2 have moved away from "snapshots" to the 3.2 directory of the OpenBSD mirrors. It is well known as the world's most secure operating system and now sports chroot'd Apache, fewer suid binaries, cool pictures for xdm-logins, a brilliant "antispoof" packet filtering rule and as usual includes lots of small updates and fixes. The files are there. What are you waiting for?"
of Deeeezzzzz Nutz
(written by Lee Barnett and Kim Morrissey)
... as in "High"
1. GRAMS "HAIL TO THE CHIEF"
2. CLINTON : Well, boys, what's the situation with Hi-ate-ee?
3. ADVISOR 1 (WOMAN): Excuse me, Mr. President. I think that's pronounced "High-ti
4. ADVISOR 2 (WOMAN): Actually, Mr. President, I think you'll find it's pronounced "Hate-ti" as in "hate"
5. CLINTON: Gosh darn, I don't give a damn how you pronounce it, what's happening to our men?
6. ADVISOR 1: Well, it's not looking good. Two hundred of our men are being held off by sixteen hundred armed troops.
7. CLINTON: So, you think we should use nucular weapons?
8. ADVISOR 1: Excuse me, Mr. President. I think you mean "nuclear"
9. CLINTON Do I?
(Page 2)
1. ADVISOR 2: No, no, of course not.
2. ADVISOR 1: Certainly not.
3. ADVISOR 2: After all, after Somalia, Nicaragua and the Gulf, the last thing we need is to spoil our image as the world's peacemaker.
4. GRAMS "HAIL TO THE CHIEF"
ENDS
I HATE-ti you.
openbsd is superior
openbsd is being a pain in the
openbsd is installed
openbsd is superior by ben goren background
openbsd is freely available from our ftp sites
openbsd is all free
openbsd is also an extremely capable operating system
openbsd is not secure anymore
openbsd is for monkeys
openbsd is being a pain in the neck
openbsd is a serious project
openbsd is shipping does not support hdlc or isdnd
openbsd is indeed not "a server os" or "a hacker os"
openbsd is a really nice os
openbsd is audited for that most frequent of security problems
openbsd is the perfect tool in other situations
openbsd is even driving my hp laserjet 5l and deskjet 882c printers for my windows clients
openbsd is more secure than most versions of linux
openbsd is one os that's likely to be voted "most secure
openbsd is extremely robust and is capable of anything that commercial competitors such as checkpoint are
openbsd is now booting multiuser and generally useable on 64 bit sparc systems
openbsd is just awesome
openbsd is put together that the linux community needs to take note of
openbsd is often noted for its code auditing and integrated crypto
openbsd is for december
openbsd is stable and runs on several different types of computers
openbsd is security
openbsd is a fairly complete system of its own
openbsd is thought of by many security professionals to be the most secure unix
openbsd is the most secure server operating system now available
openbsd is preparing a libssl based on the patented rsaref code
openbsd is one
openbsd is complete packaging for the average joe shmoe user
openbsd is following netbsd's source tree > that it has all of the nbsd 1
openbsd is my operating system of choice
openbsd is pretty much straight forward
openbsd is also available separately
openbsd is used for dns
openbsd is one of the few systems that ships with perl preinstalled
openbsd is hailed by security buffs as uncrackable; it's been over three years
openbsd is the first unix
openbsd is free
openbsd is an open
openbsd is great
openbsd is the secure os specialist
openbsd is the closest thing to a set
openbsd is unsupported under virtual pc
openbsd is freely available from
openbsd is widely hailed as being the most secure os available
openbsd is a group that has done it right
openbsd is released on a sixth month development cycle
openbsd is still relatively new
openbsd is our favourite operating system
openbsd is a free
openbsd is used to provide various network services in the department of genome sciences
openbsd is much better then linux
openbsd is highly regarded as a great firewall
openbsd is one of the industry's most secure operating systems
openbsd is nothing for pure office work
openbsd is regarded as one of the most secure operating systems on the market today
openbsd is an open source multi
openbsd is developed and released from canada and due to canadian law it is legal to export crypto to the world
openbsd is only able to boot from hfs
openbsd is supposed to be indestructable
openbsd is to give the boot loader
openbsd is a free version of unix that runs on intel/cyrix/amd pentium
openbsd is unfriendly
openbsd is now available from openbsd
openbsd is a free unix
openbsd is very difficult
openbsd is the operating system for your site
openbsd is a robust and competent open source operating system project besides freebsd
openbsd is not covered by this faq
openbsd is my
openbsd is based on netbsd so it inherits most of it's advantages
openbsd is een open source operating system en gebaseerd op de bsd kernel
openbsd is comparatively minimalist
openbsd is indeed very minimalistic but it is a bit on the slow side for a couple reasons
openbsd is one choise but their linux version didn't work on my laptop
openbsd is a vulnerable operating system because it runs on a computer which can be physically accessed by an intruder
kthx
I thought the most secure OS was Windows 95. With NIC support like that nobody should be able to connect to your computer. On a more serious note, is OpenBSD recommended as an internet server over all of the other distros?
Does anyone know if they have the threading issues resolved with the kernel scheduler yet?
Tha last time I worked on any BSD code they were still having some low level race conditions occuring where the kernel scheduler would actually hit two proccesses at the same time which made it look like the program had some mutex corruption when it was actually a problem with the kernel and the semaphores they use to map memory for threads.
Granted if you're only using it as a workstation you'll never see it happen as it only happened under load but I found my clients were forced to move to a commercial Unix (I still recommend Sun) as they were the only products on the market able to handle enterprise type server loads with non-trivial applications. (okay, wer're talking n-tier Olog(n) cluster nodes which is very demanding but still...)
Warmest regards,
--Jack
Wagner LLC Consulting Co. - Getting it right the first time
Why? So it runs slower and is less secure?
Wow, OpenBSD 3.2. For a while there I wasn't sure they'd ever get another release out (heh, and I'm not one of those "BSD is dying!" trolls, either!). It's always been one of my favorite BSD distros, and I'd never have switched to Linux if OpenBSD had had an SB Live! driver back in the day. The name "OpenBSD" was synonymous with "rock hard security."
It was sad to see the record for "no remote holes" disappear earlier this year. Even sadder when the holes in OpenSSH and -SSL were found. It seemed like the OpenBSD developers had maybe started to get lazy, or were too busy rushing to support the latest gee-whiz hardware and flashy features to keep an eye on security. And for most unix admins out there, flashy features aren't worth much if you don't have security.
I guess it's good to see that Theo isn't giving up. But I'm wondering if this release is going to be just another stepping stone on OpenBSD's recent path to shame, or if they are turning it around in an attempt to regain the glory of, say, 2.7. What do people think, is OpenBSD rising from the ashes or gasping its last breath?
Karma: Good (despite my invention of the Karma: sig)
How does buying OpenBSD support Windows 2000?
There's a link to a Finnish mirror of the backgrounds available here.
Some really neat stuff in there. I'm looking forward to getting it all unzipped.
It's not easy to compare these two, so I've come up with a useful analogy. FreeBSD would be 'dead', and OpenBSD 'fossilised'.
cann somedbody tell my if its worth it to upgradee my omputer from windows to windowsME???/ ADVthxANCE
[ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It's when you get distracted by the politickers that they sideline you. The tireless work that you perform keeping the system clean and building is what provides the platform for the obsessives and the prima donnas to have their moments in the sun. In the end, we need you all; in order to go forwards we must first avoid going backwards.
To the paranoid conspiracy theorists - yes, I work for Apple too. No, my resignation wasn't on Steve's direct orders, or in any way related to work I'm doing, may do, may not do, or indeed what was in the tea I had at lunchtime today. It's about real problems that the project faces, real problems that the project has brought upon itself. You can't escape them by inventing excuses about outside influence, the problem stems from within.
To the politically obsessed - give it a break, if you can. No, the project isn't a lemonade stand anymore, but it's not a world-spanning corporate juggernaut either and some of the more grandiose visions going around are in need of a solid dose of reality. Keep it simple, stupid.
To the grandstanders, the prima donnas, and anyone that thinks that they can hold the project to ransom for their own agenda - give it a break, if you can. When the current core were elected, we took a conscious stand against vigorous sanctions, and some of you have exploited that. A new core is going to have to decide whether to repeat this mistake or get tough. I hope they learn from our errors.
Future
I started work on FreeBSD because it was fun. If I'm going to continue, it has to be fun again. There are things I still feel obligated to do, and with any luck I'll find the time to meet those obligations.
However I don't feel an obligation to get involved in the political mess the project is in right now. I tried, I burnt out. I don't feel that my efforts were worthwhile. So I won't be standing for election, I won't be shouting from the sidelines, and I probably won't vote in the next round of ballots.
You could say I'm packing up my toys. I'm not going home just yet, but I'm not going to play unless you can work out how to make the project somewhere fun to be again.
= Mike
--
cool pictures for xdm-logins
I'm afraid all the "BSD is dying" posts are true. If that's one of the offerings worth mentioning, I think I'll stick with Linux or FreeBSD for my Unix fix.