OpenBSD Hackathon
A secretive reader contributes: "Once again, almost all of the OpenBSD developers got together for a full week of intensive coding. Pictures from the hackathon are available for people who want to see how the developers of this fine OS look like. Theo de Raadt announced on the mailing list: 'There is a reason why such a flurry of commits is happening. Once again, we are doing a hackathon; this time in Calgary, for a full week leading up to usenix. Thus far, 32 people have arrived, and are hacking away in a hotel conference room, working on various things, but more people are still flying in from around the world ...'"
Here's proof it aint! hahahahahahaha!!
I dunno -- if it weren't for the parts wrapped in plastic I'd be sure it's actually "chair collapses under weight of OpenBSD hacker".
Also, of interest "drahn" on a TiBook. Looks like Apple's really making some inroads in the Unix world. OpenBSD doesn't really run on that, does it?
What I'm listening to now on Pandora...
I've been watching the CVS commit logs since the beginning of this event - number of bugs getting fixed and new features being added is very impressive.
I especially like that more and more daemons loose their setgid and setuid privileges - great step towards improving the security.
It works VERY well. The cvs-update-and-compile method of system maintenance is astonishingly useful. I love everything about OpenBSD.... except one.
There is no SMP support. There is a cvs branch for SMP development, but after a year the only thing it does is RECOGNIZE the second CPU. It doesnt actually do anything with it.
So, I'm about to build a new server, SMP, and I have two choices. I can run OpenBSD on one CPU hoping for the day I can reboot and have the second fire up, or I can run Gentoo linux, which has all the cvs-and-compile chocolaty goodness of BSD, but will do SMP.
FreeBSD has smp. I believe NetBSD has smp. Darwin has SMP. OpenBSD doesn't. With SMP hardware so cheap (At least on the i386 side) it's ludicrous that it's not in there.
I'm taking bets that the site showing "Pictures from the hackathon" won't get Slashdotted. Who's in?
- Bill
...If OpenBSD continues like this we will see new buzzwords emerge in the underground and ThinkGeek selling tshirts that say "Got Nobody?"
symetrix. We are building a religion, a limited edition.
Netcraft officially confirms: *BSD is dying
Yet another crippling bombshell hit the beleaguered *BSD community when recently IDC confirmed that *BSD accounts for less than a fraction of 1 percent of all servers. Coming on the heels of the latest 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 further exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin 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.
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 *BSD's long term survival prospects are very dim. If *BSD is to survive at all it will be among OS hobbyist 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
Put this on the frontpage, please. Thank you.
An Education is the Font of All Liberty
Close your web browser, shut down your fucking linux "b0xen" and go outside for once in your life.
I think the fact that a site like slashdot, which caters to you fucking nerds out there, can't even
survive without having to charge you for reading it, says alot about how much you fucks are worth to the rest of the world: ZERO.
This should serve as a wakeup call to all you nerds out there who think that working on your b0xen in your one bedroom apartment, posting useless shit to a useless web site like slashdot and reading about the newest version of OpenBSD that can run on your fucking Dreamcast console is a good way to go through life.
So wake the fuck up and DO something productive, something that makes money. Stop wasting your time talking about open source fucking garbage that will never amount to anything useful.
#!/bin/bash
/proc/sys/net/ipv4/tcp_syncookies
# --
# Slashdot Opensores Firewall Script
# --
# Distributed under the superior BSD license
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
#
# 1.Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# 2.Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
# 3.The name of the author may not be used to endorse or promote
# products derived from this software without specific prior
# written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
# IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
# WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
# DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
# GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
# INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
# IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE
#
# -- Start Here
#
IPTABLES="/sbin/iptables"
# Being gang raped by sinos is not fun
echo 1 >
${IPTABLES} -t filter -F INPUT
${IPTABLES} -t filter -F OUTPUT
${IPTABLES} -t filter -P INPUT ACCEPT
${IPTABLES} -t filter -P OUTPUT DROP
# The rulz
${IPTABLES} -t filter -A INPUT -p unprotected -s male/16 --sport penis --dport mouth -j ACCEPT
${IPTABLES} -t filter -A INPUT -p unprotected -s male/16 --sport fist --dport anus -j ACCEPT
${IPTABLES} -t filter -A INPUT -p unprotected -s male/16 --sport finger --dport anus -j ACCEPT
${IPTABLES} -t filter -A INPUT -p protected -s male/16 --sport fist --dport anus -j ACCEPT
${IPTABLES} -t filter -A INPUT -p protected -s male/16 --sport penis -j ACCEPT
# I know this may seem controversial but it feels good
${IPTABLES) -t filter -A INPUT -p unprotected -s female/16 --sport fist --dport anus -j ACCEPT
${IPTABLES) -t filter -A INPUT -p unprotected -s female/16 --sport finger --dport anus -j ACCEPT
${IPTABLES} -t filter -A OUTPUT -d female/16 -j DROP
# TODO: IMPLEMENT NAT AND DMZ
# -- Finish
It is officia l; Netcra ft confirm s: *BSD is d
ying O ne more cripp ling bombshell h it the a
lready beleag ue red *BSD c ommunity when ID C
confir med t hat *BSD m arket share has
droppe d y e t again , now down to le
ss than a f racti on of 1 perce
nt of all s erv ers. Coming
on the he e l s of a recen
t Netcraf t survey whic
h plainly s tates that
*BSD has l o s t m ore marke
t share, t h is n ews serve
s to rein fo rc e what we'v
e known a l l a long. *BS
D is coll a psing in com
plete di sa rray, as fitt
ingl y exe m plified by f a
ilin g d ead last [samag
.co m] in the recent S
ys A dm in comprehensi v
e n e tworking test.
You don't need to be
a K reskin [amdest.
co m] to predict *BSD
's & #9617; future. The hand wr
iti ng is on the wall:
*BSD f aces a bleak futu
re. In f act there won't be
a ny futur e at all for *BSD b
eca use *B SD is dying. Thing
s are l ook ing very bad for *
BSD. As m an y of us are alread
y aware, * BSD c ontinues t o los
e market s har e. Red ink flows l
ike a river o f blood. F reeBSD
is the mos t e ndangered o f them
all, havin g l & #9617; ost 93% of its co
re develop ers. T he sudden and u
npleasa nt depa rtures of long
time F r eeBSD deve
lop ers Jo rdan H
ubb a rd and M ik
e S m it h on ly
se rve t o un der
sc ore t he p
oin t m ore c
lea rly. Th & #9617; ere c an
no l onger be a ny doubt: F reeB
SD is dy ing. Let's keep to the f acts an
d look at t he numbers. Open BSD leader Theo st
For what it's worth, this was not much but a re-post
;-)
of a mail from Theo de Raadt, the OpenBSD leader,
to the "misc" mailing list.
The remaining few hackers were either representing
OpenBSD (and BSD in general) at the German LinuxTag
in Karlsruhe (Wim Vandeputte, the "leader" for Europe,
and (more unknown) Christian Weisgerber and me...
And one was unable to get a passport from the
French authorities - seems as they are jealous
to the German bureaucracy
My Karma isn't excellent, damn it! (And
Where's all the chics?
Theo's comment suggests that commits to the core CVS are being done during this event - that's an impressive application of technology, if so. I wonder how this is funded. Still, you have to admire the singlemindedness of the team.
I'm noticing a lot of Mountain Dew in those pictures, so that inspired me to ask:
Did somebody smuggle a shitload of the stuff from the states, or are hackers working while drinking a beverage with no caffiene or alcohol?
For thoses that don't know, Canadian laws prohibit adding caffiene to any fruit flavoured drink (ergo MD here has no caffiene).
God save our Queen, and Heaven bless The Maple Leaf Forever!
[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
--
Pilsner!
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market shre 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 in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin 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
If they could get away with it?
I don't know about Canada, but the US FDA doesn't seem to have much of a problem with Nico Water being sold. It is touted as a supplement rather than a drug, which has anti-tobacco groups up in arms.
That doesn't really make sense to me, because it truly is a healthier alternative to smoking, and virtually eliminates the possibility of second hand smoke. If you really wanna strech, perhaps a truckload of this stuff could dump into some groundwater, or you might accidentally spill a bottle on somebody leading to dermal absorption - but those idiots should give it a rest. It is even labeled against sale to minors.
If they really need something to protest about, why aren't they protesting the fluoride water whive I've seen for sale. This shit is actually targeted at children, and it never got FDA approval either. Tabacco is carcinogenic because of the other hundred some toxins - while nicotine can be dangerous, it is far less toxic than the industrial waste known as fluoride. That fluoride products can be marketed to children is criminally irresponsible, especially in light of the "Camel Joe" fiasco.
Amdest.com took down the Amazing Kreskin page. I guess their servers couldn't handle the angry, foaming at the mouth *BSD apologists who clicked on the link. Try the Wayback Machine or Google's cache instead.
I look at the pics posted and I see myself in there. You know, slightly overweight, facial hair, balding a bit, staring at a damn console, and loving it. Geeks are sad, yet I am one.
A bunch of people are holed up in a hotel conference room, hacking away like crazy...um, would't it be appropriate to call The Homeland Security office, instead of posting a story?
Is slashdot condoning people who engage in anti-social behavior? And why is it that Theo De Raat expects people to PAY HIM MONEY so he can spend his time breaking into other people's computers?
Dude Your teeth need fluoride and YES I now it is most tooth pastes but You don't ingest any of it. Vitam A can kill you if you take to much. ADA if you don't get enough fluoride your Teeth will decay. However I wonder If the HIGH amount of fluoride in most US teeth pastes is good for you.
Thank you for the link. Although you probably won't see this response as an AC, I will respond because you bothered to use a link.
As stated in the article, fluoride is naturally occuring. As a result of industrialization, there is now more fluoride in the environment (air, water and foods) then any recomended minimum set by the FDA. Note that the FDA has not done any studies on the effects of Fluoride since the WWII era, when nuclear weapons factories started producing the flouride byproduct.
As stated in the first paragraph of the ADA article, Flouride only occurs in counpounds. Naturally occuring fluoride which is good for the teeth is better called "Calcium Fluoride". Why does the ADA recommend just "fluoride" even after admitting that there is no such molecule? So that they can get paid off by industries who can now easily dispose of their toxic wastes, specifically "Sodium Fluoride" and "Potassium Fluoride".
Vitamin C is water soluble, so that excess ascorbic acid can fairly easily be expelled from the body as liquid waste, making it very difficult to take a harmful dose. Vitamin A is fat soluble, and like many dieters can attest, it is much more difficult to excrete excess fat. If too much Vitamin A builds up before the body can properly excrete it, that too can be harmful. Sodium Fluoride harms your organs at much lower dosages, and build up in your bones. Bone matter tends not to be excreted, so fluoridosis is a cumulative danger. The very bones and teeth that (Calcium) fluoride was supposed to protect instead become mottled and brittle. Hell, why do you think it is so important not to ingest toothpaste?
Your body need to ingest nutrients systemically to utilize them beneficially. Topical toothpaste applications are minimally harmful if swallowing is minimized. Adulterating the water supply on the otherhand, is insidious exploitation of misinformation that directly harms public health.
Lift Kit
you know when i read things like this it kind of makes me wonder which really is better linux/*bsd i mean linux has the commercial side over BSD but when you strip it down which one really is better ? i mean i am a linux junkie, never used BSD but this makes me wanna go get openBSD 3.1 just for fun...... only thing is i cant find any ISO's too download
"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe." --Albert Einstein