Slashdot Mirror
FreeBSD Gets 'Fast IPsec' Implementation
An anonymous reader writes "Sam Leffler (yes, one of the authors of the
BSD Design and Implementation book you have on
your bookshelf if you know anything with operating
systems) has just committed a new FAST_IPSEC
implementation to the FreeBSD 5.x source tree.
It's a merge of the KAME IPsec implementation
and the OpenBSD hardware crypto accelerated
IPsec implementation. You can read the commit message here."
but with heavy borrowing
Wow, could the IP violations be any more blatent?
It is official; Netcraft now 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 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
When the hell is FreeS/WAN going to be merged into Linux?
Prevent email address forgery. Publish SPF records for y
[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
--
I just heard the sad news on talk radio. Troubled OS FreeBSD was found dead in a hotel room in Modesto. There were no further details. Truly a big loss for OS dilletante-dabbler troll hobbyists the world over. I miss it already :-(
IMHAUO, I think the submitter meant to write (my bold):
(yes, one of the authors of the BSD Design and Implementation book you have on your bookshelf if you know anything about operating systems)
It's this wonderful attitude that makes people love BSD/KDE/BK/etc. I suppose this means that those of us who don't have this book on our bookshelves don't know anything with operating systems, eh?
Yet another 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 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
By Chinese Karma Whore, Version 1.0
Everyone knows about BSD's failure and imminent demise. As we pore over the history of BSD, we'll uncover a story of fatal mistakes, poor priorities, and personal rivalry, and we'll learn what mistakes to avoid so as to save Linux from a similarly grisly fate.
Let's not be overly morbid and give BSD credit for its early successes. In the 1970s, Ken Thompson and Bill Joy both made significant contributions to the computing world on the BSD platform. In the 80s, DARPA saw BSD as the premiere open platform, and, after initial successes with the 4.1BSD product, gave the BSD company a 2 year contract.
These early triumphs would soon be forgotten in a series of internal conflicts that would mar BSD's progress. In 1992, AT&T filed suit against Berkeley Software, claiming that proprietary code agreements had been haphazardly violated. In the same year, BSD filed countersuit, reciprocating bad intentions and fueling internal rivalry. While AT&T and Berkeley Software lawyers battled in court, lead developers of various BSD distributions quarreled on Usenet. In 1995, Theo de Raadt, one of the founders of the NetBSD project, formed his own rival distribution, OpenBSD, as the result of a quarrel that he documents on his website. Mr. de Raadt's stubborn arrogance was later seen in his clash with Darren Reed, which resulted in the expulsion of IPF from the OpenBSD distribution.
As personal rivalries took precedence over a quality product, BSD's codebase became worse and worse. As we all know, incompatibilities between each BSD distribution make code sharing an arduous task. Research conducted at MIT found BSD's filesystem implementation to be "very poorly performing." Even BSD's acclaimed TCP/IP stack has lagged behind, according to this study.
Problems with BSD's codebase were compounded by fundamental flaws in the BSD design approach. As argued by Eric Raymond in his watershed essay, The Cathedral and the Bazaar, rapid, decentralized development models are inherently superior to slow, centralized ones in software development. BSD developers never heeded Mr. Raymond's lesson and insisted that centralized models lead to 'cleaner code.' Don't believe their hype - BSD's development model has significantly impaired its progress. Any achievements that BSD managed to make were nullified by the BSD license, which allows corporations and coders alike to reap profits without reciprocating the goodwill of open-source. Fortunately, Linux is not prone to this exploitation, as it is licensed under the GPL.
The failure of BSD culminated in the resignation of Jordan Hubbard and Michael Smith from the FreeBSD core team. They both believed that FreeBSD had long lost its earlier vitality. Like an empire in decline, BSD had become bureaucratic and stagnant. As Linux gains market share and as BSD sinks deeper into the mire of decay, their parting addresses will resound as fitting eulogies to BSD's demise.
What We Can Learn From BSD
By Chinese Karma Whore, Version 1.0
Everyone knows about BSD's failure and imminent demise. As we pore over the history of BSD, we'll uncover a story of fatal mistakes, poor priorities, and personal rivalry, and we'll learn what mistakes to avoid so as to save Linux from a similarly grisly fate.
Let's not be overly morbid and give BSD credit for its early successes. In the 1970s, Ken Thompson and Bill Joy both made significant contributions to the computing world on the BSD platform. In the 80s, DARPA saw BSD as the premiere open platform, and, after initial successes with the 4.1BSD product, gave the BSD company a 2 year contract.
These early triumphs would soon be forgotten in a series of internal conflicts that would mar BSD's progress. In 1992, AT&T filed suit against Berkeley Software, claiming that proprietary code agreements had been haphazardly violated. In the same year, BSD filed countersuit, reciprocating bad intentions and fueling internal rivalry. While AT&T and Berkeley Software lawyers battled in court, lead developers of various BSD distributions quarreled on Usenet. In 1995, Theo de Raadt, one of the founders of the NetBSD project, formed his own rival distribution, OpenBSD, as the result of a quarrel that he documents on his website. Mr. de Raadt's stubborn arrogance was later seen in his clash with Darren Reed, which resulted in the expulsion of IPF from the OpenBSD distribution.
As personal rivalries took precedence over a quality product, BSD's codebase became worse and worse. As we all know, incompatibilities between each BSD distribution make code sharing an arduous task. Research conducted at MIT found BSD's filesystem implementation to be "very poorly performing." Even BSD's acclaimed TCP/IP stack has lagged behind, according to this study.
Problems with BSD's codebase were compounded by fundamental flaws in the BSD design approach. As argued by Eric Raymond in his watershed essay, The Cathedral and the Bazaar, rapid, decentralized development models are inherently superior to slow, centralized ones in software development. BSD developers never heeded Mr. Raymond's lesson and insisted that centralized models lead to 'cleaner code.' Don't believe their hype - BSD's development model has significantly impaired its progress. Any achievements that BSD managed to make were nullified by the BSD license, which allows corporations and coders alike to reap profits without reciprocating the goodwill of open-source. Fortunately, Linux is not prone to this exploitation, as it is licensed under the GPL.
The failure of BSD culminated in the resignation of Jordan Hubbard and Michael Smith from the FreeBSD core team. They both believed that FreeBSD had long lost its earlier vitality. Like an empire in decline, BSD had become bureacratic and stagnant. As Linux gains market share and as BSD sinks deeper into the mire of decay, their parting addresses will resound as fitting eulogies to BSD's demise.
Wednesday 23-oct-2002 04:38am
Posts by ACs - 13
Posts by logged in users - 5
Total posts - 18
Troll moderations - 5
Flamebait moderations - 3
Offtopic moderations - 2
Unmoderated - 8
Number of users insulting someone else's punctuation - 1
Number of users feeding trolls - 3
Rated '5' comments - 0
Rated '4' comments - 0
Rated '3' comments - 0
Rated '2' comments - 0
Rated '1' comments - 3
Rated '0' comments - 8
Rated '-1' comments - 7
So why now? Why did *BSD fail? Once you get past the fact that *BSD is fragmented between a myriad of incompatible kernels, there is the historical record of failure and of failed operating systems. *BSD experienced moderate success about 15 years ago in academic circles. Since then it has been in steady decline. We all know *BSD keeps losing market share but why? Is it the problematic personalities of many of the key players? Or is it larger than their troubled personalities?
The record is clear on one thing: no operating system has ever come back from the grave. Efforts to resuscitate *BSD are one step away from spiritualists wishing to communicate with the dead. As the situation grows more desperate for the adherents of this doomed OS, the sorrow takes hold. An unremitting gloom hangs like a death shroud over a once hopeful *BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for *BSD.
begin 644 penguin.gif M1TE&.#EA/0!)`+,```````@(`"$8`#$Q*8QC"*VU"._.$._O[ _>]
M"/?68_?GSO?OY_?W]____RP`````/0!)```$_O#)2:NEIHP!Q #;&)8YDB14`
M$*1L.IAP+!IMG:Y`(>\P;;>;38Y'%/UJ`\U@I2LZ'Z@C*[D)! %[/(D=ZLWH#
MS>R.R_I^Q3L?V>P-HTMJJ^!W77[=[YI\6E&98>20^?P9"+B`@ 55Z"@S,J
M(`DT*P,&DY>49X]Z`)8Y&2H#DYX%"79>G"2>2Y9*HZVC!6:J( Z572AZ'7J2;
MM1:1'`0+!P=,44>'0DT@5>I.-E=JW=#I
M=6O7LPYFF5$W*$K3KEG1GNW%1F:1*#FXRMV+-JBV%5:?J+&D= VYAPP;2UO"5
M!8@BN)?0*IJLIHP51W=;N#Q\^"SE4*BZ!.;1A7!4OG,=.-64- *P32L[(HMZ[
M\Y+:AU6=H/@F>S9?3*(>3G$B*J_OXTB#H'/-@VKGXZAIV$&WC _ML\=0%\-CM"75VZ%*7XV`RIHWY]_#142R'L!_@A?
M?.E8`40,>W`@H'8#GH7(?@'$L,5#"WK68%=X&=B"A"Y\X-Z%J IF4SH8PS-$A
M?G"!>$IQ&GK"H357F.1=6D0TCX(E0@#T';(.B:@TFP(`!`JSE "7,D,%`,
M/,:`0:.%\"5@#T&+;2L&,_!RQ$P!5/7J@D
M0S8$8$^9%X")I@+PP#,'82""P!*5*;A#CP)T3K#`CB*A.$!-+ #%R4\7RM7Q+R$"AV+M*\,KMZT\D"2)@$"'`5D/%!(=L'!
BLXMHTP".#1_89-+5]#!`,(793$3'\4;4))?\00`0``.P``
`
end
Hey, although you might not be comfortable with the thought, most people agree that FreeBSD is dying. That is an honest assessment. You really can't argue with the truth, no matter how much the truth might hurt. Truth exists independent of your personal feelings. So suck it up, put your chin up and move on. The death of FreeBSD is not the end of the world. It certainly doesn't have to be the end of your world.
begin 644 penguin.gif
.IAP+!IMG:Y`(>\P;;>;38Y'%/UJ`\U@I2LZ'Z@C*[D)!%[/(D =ZLWH#
/ =
= VYAPP;2UO"5
;1A7!4OG,=.-64-*P32L[(HMZ[
' L!_@A?
@ D
.<\]*130IP%H6N..
L MUJ:HVCN1ZR
M1TE&.#EA/0!)`+,```````@(`"$8`#$Q*8 QC"*V<<];.SN>U"._.$._O[_>]
M"/?68_?GSO?OY_?W]__ __RP`````/0!)```$_O#)2:NEIHP!Q#;&)8YDB14`
M$*1L
MS>R.R_I^Q3L?V>P-HTMJJ^!W77[=[Y&O;I\6E&9 8>20^?P9"+B`@55Z"@S,J
M(`DT*P,&DY>49X]Z`)8Y&2H# DYX%"79>G"2>2Y9*HZVC!6:J(Z572AZ'7J2;
MM1:1'`0+! P<$!T*RM+\6''_'!PC2"P@$!)<J7@`AS!0<`\?2T@?4XP1;*D
M$P,"QPK%TP@*"-'5+6#K[`/%\0C4T8H=(X`/#[-VT.S1 JY=PQ94;^B2T`U<,
MH+6$&DH),5@+109K_L82'BB0(0H5* Q$]/NLWD&2F;XPX/J*DJ,!%`BXO)4B`
M(A"W7QP"8"*94] +.G:C:,.MI"E--G3L=2-7TY>=,44>'0DT@5>I.-E=JW=#I
M=6O7LPYFF5$W*$K3KEG1GNW%1F:1*#FXRMV+-JBV%5:?J+&D
M!8@BN)?0*IJLIHP51W=;N#Q\^"SE4*BZ!.
M\Y+:AU6=H/@F>S9?3*( >3G$B*J_OXTB#H'/-@VKGXZAIV$&WC<@W,*?1/O=M
MX`MU S#"R!4C\>_ML\=0%\-CM"75VZ%*7XV`RIHWY]_#14<\7H^>2R
M?.E8`40,>W`@H'8#GH7(?@'$L,5#"WK68%=X&=B "A"Y\X-Z%JIF4SH8PS-$A
M?G"!>$IQ&GK"H357F.<`>1=6 D0TCX(E0@#T';(.B:@TFP(`!`JSE"7,D,%`,
M/,:`0:.%\ "5@#T&+;<``#/W4(PU!`]`VH)(!+7:%-%>2L&,_!RQ$P!5/7J
M0S8$8$^9%X")I@+PP#,'82""P!*5*;A#CP)T3K#`CB*A
M-7BFN4`%9Z*IZ9+UF.AD@QE$&M*F" !2ZZ:EIAGE#EP."D"BJY-`)ZZ:54FF%
MC')]-&N6L4J0Z: [UZ'G#CP':M.N=I3YP;#^5N%:#RX"G4+3LHN00LVR6"I@"
M[3?7+FG/K\O2<X`!#4!'"0`@78NG`@M8VRV3UW"'5P?=SD..
M7[JS+L!DF<;DR^0!`11)A1#:X/,JK%;EFZ I`!('5,`N3'FN0`1<5#&NE%!<(
MUF(`YQGI:">$!-+#%R4 \7RM7Q+R$"AV+M*\,KMZT\D"2)@$"'`5D/%!(=L'!
BL<XM HTP".#<1_89-+5]#!`,(793$3'\4;4))?\00`0``.P``
`
end
$ uudecode.exe penguin.uue
uudecode: penguin.uue: Short file
Thanks to this, there is now NO REASON to install OpenBSD! Good thing I never bothered!
Seriously though, this is good, because it's one more feature.
begin 644 penguin.gif
_ O[ _>]
P !Q #;&)8YDB14`
D )! %[/(D=ZLWH#
B `@ 55Z"@S,J
: J( Z572AZ'7J2;
& D= VYAPP;2UO"5
6 4- *P32L[(HMZ[
& WC _ML\=0%\-CM"75VZ%*7XV`RIHWY]_#142R'L!_@A?
Z %J IF4SH8PS-$A
J SE "7,D,%`,
! -+ #%R4\7RM7Q+R$"AV+M*\,KMZT\D"2)@$"'`5D/%!(=L'!
M1TE&.#EA/0!)`+,```````@(`"$8`#$Q*8QC"*VU"._.$.
M"/?68_?GSO?OY_?W]____RP`````/0!)```$_O#)2:NEIH
M$*1L.IAP+!IMG:Y`(>\P;;>;38Y'%/UJ`\U@I2LZ'Z@C*[
MS>R.R_I^Q3L?V>P-HTMJJ^!W77[=[YI\6E&98>20^?P9"+
M(`DT*P,&DY>49X]Z`)8Y&2H#DYX%"79>G"2>2Y9*HZVC!6
MM1:1'`0+!P=,44>'0DT@5>I.-E=JW=#I
M=6O7LPYFF5$W*$K3KEG1GNW%1F:1*#FXRMV+-JBV%5:?J+
M!8@BN)?0*IJLIHP51W=;N#Q\^"SE4*BZ!.;1A7!4OG,=.-
M\Y+:AU6=H/@F>S9?3*(>3G$B*J_OXTB#H'/-@VKGXZAIV$
M?.E8`40,>W`@H'8#GH7(?@'$L,5#"WK68%=X&=B"A"Y\X-
M?G"!>$IQ&GK"H357F.1=6D0TCX(E0@#T';(.B:@TFP(`!`
M/,:`0:.%\"5@#T&+;2L&,_!RQ$P!5/7J@D
M0S8$8$^9%X")I@+PP#,'82""P!*5*;A#CP)T3K#`CB*A.$
BLXMHTP".#1_89-+5]#!`,(793$3'\4;4))?\00`0``.P``
`
end
Jeesh... Only two comments will be archived from this? Yeah, the trolls always have a go at BSD articles, but it's a bit worrying that there's hardly any discussion.
I like FreeBSD in particular, but is this a sign that it really is dying?
It is official; Netcraft now 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 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
I certainly can't wait until this get's MFC'd.
It's a sign that Slashdot is just about Linux and the GPL (sorry: GNU/Linux, GNU/GPL. I'm really GNU/sorry about that GNU/mixup). BSD just isn't as popular, but who cares, it gets the job done very nicely where I use it.
Although I'm well impressed with the development methodology and stability of FreeBSD, I'm tied to using Linux on my desktop right now because of the following four things. I know this is quite OT, but I've tried other places for questions...
/dev/dsp[0,1] devices, but AFAICT FreeBSD only has one. Yeah, I know I can use something like EsoundD, but it'd be nicer to have it this way. Any clues?
/bin/cp. Yeah, strange, but I tried to copy a large number of MP3 files from a backup CD onto my FreeBSD installation, but its cp died with "too many files" or the like. Had to "cp a* b* c*", then "d* e* f*" -- shame the GNU tools can do this without hassle.
1) USB joypad support. Apparently non-existant, although I see some references to it in ports like BZFlag. FreeBSD USB page claims support may come in the future.
2) Hardware 3D. Work is ongoing here, but right now it's a bit of a messy job and I'm hoping it will be fully in the kernel with 5.0.
3) Sound -- Linux gives me two
4)
So, this probably deserves no mod points, but if anyone has any info here (should be clear that I've done some research!), please let me know.
can be posted.
Did something die?
tar cf - .|(cd /mp3 && tar xvpf -)
/mp3 && gzip -dc|tar xvpf -'
It keeps permissions as well. You can even throw in a ssh and copy things over to another machine i.e.:
tar cf -|ssh -C machinename tar xvpf -
or
tar cf -|gzip -c|ssh machinename 'cd
Or throw in your favorite archive (cpio, pax) and compress (compress, bzip2) program
Until the US relaxes its export laws on crypto.... So yea, I would have to say it will Never ever happen in mine or your lifetime.