Based on my experiences with them so far, it seems like a pretty good team, give or take. I think they'll be able to focus most on what the project needs.
The important part is they know how to have fun with it.;)
Say, I wonder... why does Linux Kernel Version 1.2.3.4.5.6 patchlevel 7 make it to the front page and this does not? In my opinion, this news is of a bit more influence (at least to the BSD world) than yet another patchlevel...
Re:Why?
by
Anonymous Coward
·
· Score: 0
Concentrate on what you do best and you will eventually be noticed. Mac OS X is based off freebsd and has a larger user base than Linux; it's a given. It doesn't need to be posted on the frontpage of a hobby site.
Well, this would fail.
by
Anonymous Coward
·
· Score: 0
Ozzy Osburne should join the FreeBSD dev team, 'cos they'll need someone to raise the dead (and the dedd of course).
*bsd is dying...
by
Anonymous Coward
·
· Score: 4, Funny
Ahhh so linux users shout *bsd is dying. Yet according to netcraft 44 of the top 50 longest living machines are running some form of BSD. What do I have to worry about?
http://uptime.netcraft.com/up/today/top.avg.html
BSD machines may be dying but they take so damn long to do so who knows who or what will be around for the funeral. I sure hope linux can attend.
Re:*bsd is dying...
by
Anonymous Coward
·
· Score: 0
If *BSD is dying, why is our old Sun Sparc2 upstairs still running SunOS4.1?? I mean, they *should* retire the damn thing, the hardware is getting a little tired (the last diskless workstation that booted off of it, Sparc SLC, finally died.. so its just the "server" now), but its been up for years w/o a problem. In fact, I'd bet it would have at least 5 years of uptime except for the fact that I powered it down and moved it into another area about 6 months ago.
Re:*bsd is dying...
by
Anonymous Coward
·
· Score: 0
LOL that's why in 2 days you've had 7 bsd users and 20 trolls show up.
BSD is dying. This section of/. is a joke.
BSD amiga, beos, os/2 the list goes on.
Re:*bsd is dying...
by
Anonymous Coward
·
· Score: 0
Just more proof that BSD "advocates" are brain damaged monkies (or perhaps just rabid liars).
In case you're just stupid, and not dishonest, you should go read about how uptime stats are measured by netcraft.
I'll give you a hint. The OSes represented in the list (BSD and IRIX) are the only ones that netcraft can remotely measure uptime over 497 days. Note that all 50 of them are well above 497 days.
Re:*bsd is dying...
by
Anonymous Coward
·
· Score: 0
Hate to tell you, slashdot is not of major significance in the world.
Just because the BSD section of a major pro-Linux site is less than wonderful, this does not prove that *BSD is dead. Please, get a clue.
Re:*bsd is dying...
by
Anonymous Coward
·
· Score: 0
This section of slashdot is a joke because people go to places like daemonnews.org to get real ( and accurate I might add ) information about BSD goings on. The average slashdot poster wouldn't know BSD from their own rear ends. The remaining slashdot posters are just mindless Linux zealots.
Re:*bsd is dying...
by
Anonymous Coward
·
· Score: 0
Why would Theo want to serve on the FreeBSD core team? He writes OpenBSD!
Where is Matt Dillon?
by
Anonymous Coward
·
· Score: 0
==vv New Core vv==
rwatson (171)
imp (157)
peter (151)
murray (128)
markm (119)
jhb (99)
grog (88)
wes (85)
kuriyama (83)
==^^ New Core ^^==
brian (79)
matusita (72)
dillon (64)
could someone explain how Matt Dillon missed out on core? i'm not talking about the voting process, but isn't he one of the best freebsd hackers?
Re:Where is Matt Dillon?
by
Anonymous Coward
·
· Score: 0
Yeah, he's a superb hacker (the FreeBSD VM subsystem, which he's largely responsible for, absolutely rocks). But that doesn't instantly make him a good administrator for the project!
I mean, think of it in terms of Linux. Rik van Riel is a great programmer, but I wouldn't necessarily want him to replace Torvalds or even maintain a kernel tree.
so-called core team is not what you think. It does not do more than what a committer do.
Re:notably absent
by
Anonymous Coward
·
· Score: 0
Which ignoramus modded this clueless guy up? Theo has NOTHING to do with FreeBSD. He runs an entirely separate project which just so happens to be derived from a codebase which split over a decade ago. Jeesh...
Who the hell gave "+1 Interesting" to the parent? How is it interesting that two people who have nothing to do with FreeBSD development, and did not run for FreeBSD Core, were not elected to FreeBSD Core?
for those to lazy to follow links
by
Anonymous Coward
·
· Score: 0, Funny
Here's a list of the latest members of the BSD core team:
Aliyah Lisa Left Eye Lopez Robin Crosby Randy Castillo Joey Ramone Dee Dee Ramone Layne Staley Scott Smith John Entwistle
With such a stunning array of talent, it should be quite obvious that *BSD Iz Not Dying!!!
Core Insider: Why FreeBSD is Dying
by
Anonymous Coward
·
· Score: 0
The End of FreeBSD [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
--
To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. -- Theodore Roosevelt
Actually, I found it "+1 Funny" but I didn't have any
moderator points.
Seriously, though, it looks like a good group,
one that will be a little more activist than the
last one, more likely to reign in some of the
petty weenie-waving that has happened of late
but not get overbearing about it.
-Ed
I know this is probably flaimbait
by
fooguy
·
· Score: 0, Flamebait
But I say "good".
What is going on with the FreeBSD team recently? I used to be an avid FreeBSD user, but the last year or so have not been the best.
There was some serious hostility that the latest FreeBSD release was announced too early. In this community that kind of thing happens all the time. Not ideal, but not much you can do about it either.
There was a contest for a new logo, and after over 100 people participated they decided that "none of them were what we were looking for".
FreeBSD 5.0 is supposed to have some great features, but it seems to get more distant with each passing day.
There have been some issues with the last couple releases (though I haven't tried 4.6 yet) with how it's packaged. I've heard grumbling about this outside the Linux/BSD community as well.
The port collection in FreeBSD, well frankly I think it stinks. I'm always running into broken ports that should have never made it in in the first place.
Don't get me wrong, I think that the work the FreeBSD team has done is outstanding, but their behavior has been really whacky for quite a while. Maybe a new core team will do them some good.
-- "All I ever wanted was to see Larry Wall give Bill Gates a Perl necklace."
http://www.eisenschmidt.org/jweisen
Re:I know this is probably flaimbait
by
Anonymous Coward
·
· Score: 0
Probably at least half of the ports are suffering
from bit rot and are broken in some way or other. Sadly,
many of the ports have no real maintainers.
They have not received sufficient testing.
Merely getting something to compile does not
assure that all is OK. It should be but one
step in a qualification process. Unfortunately,
the ports collection lacks sufficient quality
control.
Re:I know this is probably flaimbait
by
Atrus5
·
· Score: 2, Informative
There was a contest for a new logo, and after over 100 people participated they decided that "none of them were what we were looking for".
That was the FreeBSD Foundation, which I'm fairly certain is seperate from the FreeBSD core team.
Re:I know this is probably flaimbait
by
Anonymous Coward
·
· Score: 0
Bull,
when 4.6-RELEASE was being prepared, there were statistics published stating that more than 90% of the ports were successfully built into packages. Not bad for a collection of more than 7k ports.
The worm is thought to be capable of spreading only to Web servers running
the FreeBSD operating system, an open-source variant of Unix, that haven't
had a patch applied for the recent flaw. Although few home users have reported
the worm, it is thought to be infecting vulnerable Web servers worldwide.
This worm is only a threat to *BSD systems. *sigh*
Based on my experiences with them so far, it seems like a pretty good team, give or take. I think they'll be able to focus most on what the project needs. The important part is they know how to have fun with it. ;)
// -- http://www.BRAD-X.com/ --
Say, I wonder... why does Linux Kernel Version 1.2.3.4.5.6 patchlevel 7 make it to the front page and this does not? In my opinion, this news is of a bit more influence (at least to the BSD world) than yet another patchlevel...
Ozzy Osburne should join the FreeBSD dev team, 'cos they'll need someone to raise the dead (and the dedd of course).
Ahhh so linux users shout *bsd is dying. Yet according to netcraft 44 of the top 50 longest living machines are running some form of BSD. What do I have to worry about?
l
http://uptime.netcraft.com/up/today/top.avg.htm
BSD machines may be dying but they take so damn long to do so who knows who or what will be around for the funeral. I sure hope linux can attend.
Why would Theo want to serve on the FreeBSD core team? He writes OpenBSD!
Which ignoramus modded this clueless guy up? Theo has NOTHING to do with FreeBSD. He runs an entirely separate project which just so happens to be derived from a codebase which split over a decade ago. Jeesh...
Who the hell gave "+1 Interesting" to the parent? How is it interesting that two people who have nothing to do with FreeBSD development, and did not run for FreeBSD Core, were not elected to FreeBSD Core?
Here's a list of the latest members of the BSD core team:
Aliyah
Lisa Left Eye Lopez
Robin Crosby
Randy Castillo
Joey Ramone
Dee Dee Ramone
Layne Staley
Scott Smith
John Entwistle
With such a stunning array of talent, it should be quite obvious that *BSD Iz Not Dying!!!
The End of FreeBSD
[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
--
To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. -- Theodore Roosevelt
Actually, I found it "+1 Funny" but I didn't have any moderator points.
Seriously, though, it looks like a good group, one that will be a little more activist than the last one, more likely to reign in some of the petty weenie-waving that has happened of late but not get overbearing about it.
But I say "good".
What is going on with the FreeBSD team recently? I used to be an avid FreeBSD user, but the last year or so have not been the best.
There was some serious hostility that the latest FreeBSD release was announced too early. In this community that kind of thing happens all the time. Not ideal, but not much you can do about it either.
There was a contest for a new logo, and after over 100 people participated they decided that "none of them were what we were looking for".
FreeBSD 5.0 is supposed to have some great features, but it seems to get more distant with each passing day.
There have been some issues with the last couple releases (though I haven't tried 4.6 yet) with how it's packaged. I've heard grumbling about this outside the Linux/BSD community as well.
The port collection in FreeBSD, well frankly I think it stinks. I'm always running into broken ports that should have never made it in in the first place.
Don't get me wrong, I think that the work the FreeBSD team has done is outstanding, but their behavior has been really whacky for quite a while. Maybe a new core team will do them some good.
"All I ever wanted was to see Larry Wall give Bill Gates a Perl necklace."
http://www.eisenschmidt.org/jweisen