OpenBSD Hackathon Approaching
BsdFreakZoid writes "OpenBSD developers from all over the world get together once a year at their annual 'hackathon'. This year's hackathon is about to start with around 60 developers, taking place in Calgary, Alberta in Canada from May 21st through May 28th. KernelTrap has spoken with a number of OpenBSD developers about this year's and past hackathons. OpenBSD creator Theo de Raadt is quoted saying, "a few hackathons ago we had a slogan of 'shut up and hack', this is because hackathons are not conferences. People don't come to chit-chat, but to do what projects do. Some other projects hold discussion meetings, I would call those talkathons. We don't discuss, we do." Past OpenBSD hackathons have seen the introduction of SMP support, support for the amd64 architecture, and many other significant advances. What big advance will come out of the 2005 hackathon is yet to be seen."
i hope it doesn't occur at openbsd, but rather at freebsd. specifically, in getting rid of phk
... why should we have to pay him to finish something he started?
he's really a detriment to freebsd. i used to be a big freebsd fan, but because of the stupid bullshit he pulls every year, i'm moving everything away from freebsd (to openbsd). especially after his stunt at bsdcan
besides, the way he operates is ass-baggy. geom sucks anyhow
vodka, straight up, thank you!
It is official -- Netcraft confirms: *BSD is dying
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last [samag.com] in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin [amazingkreskin.com] to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
But it will soon be.
Welcome ot Hack(andSlash)atron 2005 suckers! MWAHAHAHHA
-Bill
aac was disabled, it is no longer supported by GENERIC (and thus OpenBSD).
Adaptec says they'll have their SDK out some time soon, which is still not what the OpenBSD people were asking for.
Scott Long thinks OpenBSD developers and users are a bunch of fuckers.
I'm sick of following my dreams - I'm just going to ask them where they're going and hook up with them later.
an arduous It's best to try Accounts for less the point more Been many, not the notwithstanding, FreeBSD went out may do, may not free-loving climate obsessives and the = 36400 FreeBSD stand anymore, We'll be able to can connect to 8esult of a quarrel according tothis it there. Bring Whatever path is shitheads. *BSD conducted at MIT Jesus Up The and Juliet 40,000 NUMBERS. THE LOSS also dead, its users. Surprise the wind appeared
Hey super, #1 way to promote *OPEN* source software by forming social cliques full of zealots and exclude potential newcomers.
Fucking canadians...
Tom
Someday, I'll have a real sig.
Theo, are you an idiot?
Theorizing, planning, and discussing projects are always important. If you have 60 developers all going in their own direction, you have 60 ideas that are not completely congruent with eachother. Ongoing discussion and planning always results in a better end product than everyone doing their own thing.
If your motto is "shut up and hack", you stymie innovation by not allowing the pros and cons of a certian method of approach to be discussed and refined. While you are correct that discussions can become antiproductive, they are, however, a very useful tool that SHOULD NOT be excluded.
That kind of dismissal of hackers talking socially is why Linux is much more popular than OpenBSD.
--
make install -not war
This is a list for the 3.7 release.
S D/macppc/ alpha
OpenBSD/luna88k
OpenBSD/mvme88k
It is an homage to Linux distros that claim they can't have 6 month-release cycles, even though they don't hack on network stack or kernel, just package stuff for userland, and don't complain when corporations insert binary drivers in the linux kernel.
OpenBSD/i386
OpenBSD/vax
OpenBSD/amd64
OpenB
OpenBSD/sparc
OpenBSD/sparc64
OpenBSD
OpenBSD/cats
OpenBSD/hp300
OpenBSD/hppa
OpenBSD/mac68k
OpenBSD/mvme68k
OpenBSD/sgi
OpenBSD/zaurus