Slashdot Mirror
Enhanced WiFi Security Patch For FreeBSD
Dan writes "Roland van Laar has a new, significant wi-fi patch for FreeBSD 5.1 and higher. The patch, available for download and testing, blocks clients with an empty or 'ANY' ssid and disables ssid broadcasting using the underlying firmware feature. SSID (Service Set ID) is used to identify wireless clients to a wireless / wired gateway. Wireless devices from the same manufacturer generally ship with the same default SSID. A beacon is a type of packet/frame that contains the SSID of a network. It is used to sync clocks on client devices and to make it easy for new network clients to see what networks are available. Preventing others from using your ssid is a means (although not foolproof!) of securing your wireless network."
SHIT ON ME! It's official - Slashdot has fucking confirmed: Trollkore is dying
Yet another cunting bombshell hit the community of Trollkore asswipes when Slashdot recently confirmed that Trollkore accounts for less than a fraction of one single puny fucking percent of all trolls. Coming hot on the heels of the latest Slashdot survey which plainly states that Trollkore has lost more fucking fp's to the GNAA, this news serves to reinforce what we've known all along. Trollkore is ingesting itself backwards, disappearing up its very own shitter, as fittingly exemplified by beeing fucking owned in this recent Slashdot story.
You don't need to be a cock-sucking Kreskin to predict Trollkore's future. The hand writing is on the wall: Trollkore faces a bleak future. In fact there won't be any fucking future at all for Trollkore because that sorded, shit-filled, mutated testicle of a troll group is dying. Things are looking very bad for Trollkore. As many of us are already aware, Trollkore continues to lose first posts. Red ink splashes across the accounting documents like a series of exploding bloodfarts. Trollkore munches the most ass of them all, having lost 93% of its core trollers. The sudden and unpleasant departures of long time Trollkore cuntwipes Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: Trollkore is dying and its rotting corpse smells worse than a maggot, vomit, shit and piss cocktail.
Due to the troubles of those arseholes at Slashdot, abysmal trolls and so on, Trollkore showed themselves to be a bunch of retarded tossers, went out of business and were taken over by GNAA who troll another type of trolls. Now Trollkore is also a miserable failure, its corpse turned over to yet another charnel house... pathetic.
All major surveys show that Trollkore has steadily fucking declined in first posts. Trollkore is where it belongs, at death's door and its long term survival prospects are almost non-fucking-existant. If Trollkore is to survive at all it will be among moronic, dilettante shitheads. Trollkore continues to Chew Satan's Dick And Fuck The Baby Jesus Up The Pooper. Nothing short of a miracle could save it at this point in time. For all practical purposes, Trollkore is dead.
Fact: Trollkore WILL FUCKING LOOSE THE UPCOMING FP-BATTLE!!.
gathers GAY NIGGERS from all over America and abroad for one common goal - being GAY NIGGERS.
Are you GAY ?
Are you a NIGGER ?
Are you a GAY NIGGER ?
If you answered "Yes" to any of the above questions, then GNAA (GAY NIGGER ASSOCIATION OF AMERICA) might be exactly what you've been looking for!
Join GNAA (GAY NIGGER ASSOCIATION OF AMERICA) today, and enjoy all the benefits of being a full-time GNAA member.
GNAA (GAY NIGGER ASSOCIATION OF AMERICA) is the fastest-growing GAY NIGGER community with THOUSANDS of members all over United States of America. You, too, can be a part of GNAA if you join today!
Why not? It's quick and easy - only 3 simple steps!
First, you have to obtain a copy of GAY NIGGERS FROM OUTER SPACE THE MOVIE (Click Here to download the ~280MB MPEG off of BitTorrent)
Second, you need to succeed in posting a GNAA "first post" on slashdot.org, a popular "news for trolls" website
Third, you need to join the official GNAA irc channel #GNAA on EFNet, and apply for membership.
Talk to one of the ops or any of the other members in the channel to sign up today!
If you are having trouble locating #GNAA, the official GAY NIGGER ASSOCIATION OF AMERICA irc channel, you might be on a wrong irc network. The correct network is EFNet, and you can connect to irc.secsup.org or irc.easynews.com as one of the EFNet servers.
If you do not have an IRC client handy, you are free to use the GNAA Java IRC client by clicking here
If you have mod points and would like to support GNAA, please moderate this post up.
________________________________________________
| ______________________________________._a,____ |
| _______a_._______a_______aj#0s_____aWY!400.___ |
| __ad#7!!*P____a.d#0a____#!-_#0i___.#!__W#0#___ |
| _j#'_.00#,___4#dP_"#,__j#,__0#Wi___*00P!_"#L,_ |
| _"#ga#9!01___"#01__40,_"4Lj#!_4#g_________"01_ |
| ________"#,___*@`__-N#____`___-!^_____________ |
| _________#1__________?________________________ |
| _________j1___________________________________ |
| ____a,___jk_ GAY_NIGGER_ASSOCIATION_OF_AMERICA_|
| ____!4yaa#l___________________________________ |
| ______-"!^____________________________________ |
` _______________________________________________'
TEHRAN, Dec. 27 -- The death toll from the devastating earthquake that shook the southern Iranian city of Bam for 12 seconds on Friday morning rose to 25,001, city officials said Saturday, and confirmed that BSD was among the dead.
The interior minister, Abdolvahed Moussavi Lari, said on state television from Bam: "The city is ruined. More than 70 percent of it is destroyed. And BSD was crushed, there is no hope of survival"
On Saturday, the tens of thousands of injured people crowded field hospitals or lay helplessly in the streets, while survivors and rescuers dug frantically trying in vain to save the crushed form of *BSD. Aftershocks jolted the area, shaking down the crumbled remains of the city's low-rise clay-tile, brick and concrete-block dwellings, which was now BSD's tomb.
[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
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 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.
Now what does that tell you bitch?
BSD IS FUCKING DEAD, NOBODY FUCKING CARES ABOUT THIS ROTTING CORPSE
Lameness filter encountered. Post aborted!
Reason: Don't use so many caps. It's like YELLING.
Lameness filter encountered. Post aborted!
Reason: Don't use so many caps. It's like YELLING.
Lameness filter encountered. Post aborted!
Reason: Don't use so many caps. It's like YELLING.
I suppose it's good news that there are people who do care about Wifi security.
However, I'm wondering: how much security does SSID-based blocking add (could individuals forge SSIDs, or would they have to be organizations with cash and determination?)? Shouldn't all connections on a wireless network use a strong encoding (SSH or such)?
How do real people provide and use services that are normally insecure (NFS comes to mind) over Wifi?
This crutch and vacant stool have become orphans, not unlike the now dead FreeBSD. No longer will FreeBSD hobble about on its cripple's crutch. Like the empty hearth, and the vacant stool, FreeBSD lies cold and still. FreeBSD's corpse, lifeless beneath frozen earth and December snows, will see no more Christmas cheer. No, there will be no Christmas ever again for FreeBSD, for FreeBSD is dead.
Goodbye, FreeBSD. The pain of life forever stilled, sleep for all eternity in that long winter's nap. Fade gently into Earth's frozen bosom where in dreams even cripples walk and blind men see.
This is a great addition nontheless. If you can hide your SID then some warfaring punk can't find you easy. But then again you probably are using WEP or WPA or whatever the encyrption of the week is, so that is a nonissue. Now, I would be impressed if more wireless cards were supported. I am getting sick and tired of using my windows machine to down load my FreeBSD software toys.
The views expressed are mine own and do not express the views of my employer.
I'll have to give this a try. While it does not make WiFi secure, it is a small step to making it a bit more secure. At least this way, if I'm not using my wireless network (which is most of the time), it's not broadcasting SSID's for people to sniff.
On a side note, it's a real shame that a useful article has garnered mostly trolls and flamebait as responses. Sigh...
Back in the day, around FreeBSD 2.2.8, it was a very nice operating system. However, when RELENG_5 was branched, a lot of wrong decisions were made, most of them by people with zero clue about how to implement proper SMP (e.g. John Baldwin). Matt Dillon tried to fix the situation, but all he got in response was a commit bit suspension, which later lead to his expulsion.
You can thank assholes like: Poul-Henning Kamp (POT, KETTLE, BLACK), Greg Lehey, Dag-Erling Smorgrav, Mark Murray and Bill Fumerola for kicking him out and making sure that, thanks to overengineering, RELENG_5 will never work.
Further proof, FreeBSD recently went 100% dynamic to allow the use of NSS switch system. John Dyson, who did most of the VM work back in the day, pointed out how wrong this decision was. Dillon also jumped in and offered a better solution. What he got as reward was Scott Long telling him to go away. Listen Scott, YOU ARE A FUCKING IDIOT. Not only you don't even know how to quote, but you also managed to fuck the 5.1-R isos twice. I wonder how can you be in re@, that sure has lead to the piss-poor quality of the last 2 or 3 releases.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
20528Back in the day, around FreeBSD 2.2.8, it was a very nice operating system. However, when RELENG_5 was branched, a lot of wrong decisions were made, most of them by people with zero clue about how to implement proper SMP (e.g. John Baldwin). Matt Dillon tried to fix the situation, but all he got in response was a commit bit suspension, which later lead to his expulsion.
You can thank assholes like: Poul-Henning Kamp (POT, KETTLE, BLACK), Greg Lehey, Dag-Erling Smorgrav, Mark Murray and Bill Fumerola for kicking him out and making sure that, thanks to overengineering, RELENG_5 will never work.
Further proof, FreeBSD recently went 100% dynamic to allow the use of NSS switch system. John Dyson, who did most of the VM work back in the day, pointed out how wrong this decision was. Dillon also jumped in and offered a better solution. What he got as reward was Scott Long telling him to go away. Listen Scott, YOU ARE A FUCKING IDIOT. Not only you don't even know how to quote, but you also managed to fuck the 5.1-R isos twice. I wonder how can you be in re@, that sure has lead to the piss-poor quality of the last 2 or 3 releases.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
18510Back in the day, around FreeBSD 2.2.8, it was a very nice operating system. However, when RELENG_5 was branched, a lot of wrong decisions were made, most of them by people with zero clue about how to implement proper SMP (e.g. John Baldwin). Matt Dillon tried to fix the situation, but all he got in response was a commit bit suspension, which later lead to his expulsion.
You can thank assholes like: Poul-Henning Kamp (POT, KETTLE, BLACK), Greg Lehey, Dag-Erling Smorgrav, Mark Murray and Bill Fumerola for kicking him out and making sure that, thanks to overengineering, RELENG_5 will never work.
Further proof, FreeBSD recently went 100% dynamic to allow the use of NSS switch system. John Dyson, who did most of the VM work back in the day, pointed out how wrong this decision was. Dillon also jumped in and offered a better solution. What he got as reward was Scott Long telling him to go away. Listen Scott, YOU ARE A FUCKING IDIOT. Not only you don't even know how to quote, but you also managed to fuck the 5.1-R isos twice. I wonder how can you be in re@, that sure has lead to the piss-poor quality of the last 2 or 3 releases.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
6000Back in the day, around FreeBSD 2.2.8, it was a very nice operating system. However, when RELENG_5 was branched, a lot of wrong decisions were made, most of them by people with zero clue about how to implement proper SMP (e.g. John Baldwin). Matt Dillon tried to fix the situation, but all he got in response was a commit bit suspension, which later lead to his expulsion.
You can thank assholes like: Poul-Henning Kamp (POT, KETTLE, BLACK), Greg Lehey, Dag-Erling Smorgrav, Mark Murray and Bill Fumerola for kicking him out and making sure that, thanks to overengineering, RELENG_5 will never work.
Further proof, FreeBSD recently went 100% dynamic to allow the use of NSS switch system. John Dyson, who did most of the VM work back in the day, pointed out how wrong this decision was. Dillon also jumped in and offered a better solution. What he got as reward was Scott Long telling him to go away. Listen Scott, YOU ARE A FUCKING IDIOT. Not only you don't even know how to quote, but you also managed to fuck the 5.1-R isos twice. I wonder how can you be in re@, that sure has lead to the piss-poor quality of the last 2 or 3 releases.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
23055Back in the day, around FreeBSD 2.2.8, it was a very nice operating system. However, when RELENG_5 was branched, a lot of wrong decisions were made, most of them by people with zero clue about how to implement proper SMP (e.g. John Baldwin). Matt Dillon tried to fix the situation, but all he got in response was a commit bit suspension, which later lead to his expulsion.
You can thank assholes like: Poul-Henning Kamp (POT, KETTLE, BLACK), Greg Lehey, Dag-Erling Smorgrav, Mark Murray and Bill Fumerola for kicking him out and making sure that, thanks to overengineering, RELENG_5 will never work.
Further proof, FreeBSD recently went 100% dynamic to allow the use of NSS switch system. John Dyson, who did most of the VM work back in the day, pointed out how wrong this decision was. Dillon also jumped in and offered a better solution. What he got as reward was Scott Long telling him to go away. Listen Scott, YOU ARE A FUCKING IDIOT. Not only you don't even know how to quote, but you also managed to fuck the 5.1-R isos twice. I wonder how can you be in re@, that sure has lead to the piss-poor quality of the last 2 or 3 releases.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
19327Back in the day, around FreeBSD 2.2.8, it was a very nice operating system. However, when RELENG_5 was branched, a lot of wrong decisions were made, most of them by people with zero clue about how to implement proper SMP (e.g. John Baldwin). Matt Dillon tried to fix the situation, but all he got in response was a commit bit suspension, which later lead to his expulsion.
You can thank assholes like: Poul-Henning Kamp (POT, KETTLE, BLACK), Greg Lehey, Dag-Erling Smorgrav, Mark Murray and Bill Fumerola for kicking him out and making sure that, thanks to overengineering, RELENG_5 will never work.
Further proof, FreeBSD recently went 100% dynamic to allow the use of NSS switch system. John Dyson, who did most of the VM work back in the day, pointed out how wrong this decision was. Dillon also jumped in and offered a better solution. What he got as reward was Scott Long telling him to go away. Listen Scott, YOU ARE A FUCKING IDIOT. Not only you don't even know how to quote, but you also managed to fuck the 5.1-R isos twice. I wonder how can you be in re@, that sure has lead to the piss-poor quality of the last 2 or 3 releases.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
11917Back in the day, around FreeBSD 2.2.8, it was a very nice operating system. However, when RELENG_5 was branched, a lot of wrong decisions were made, most of them by people with zero clue about how to implement proper SMP (e.g. John Baldwin). Matt Dillon tried to fix the situation, but all he got in response was a commit bit suspension, which later lead to his expulsion.
You can thank assholes like: Poul-Henning Kamp (POT, KETTLE, BLACK), Greg Lehey, Dag-Erling Smorgrav, Mark Murray and Bill Fumerola for kicking him out and making sure that, thanks to overengineering, RELENG_5 will never work.
Further proof, FreeBSD recently went 100% dynamic to allow the use of NSS switch system. John Dyson, who did most of the VM work back in the day, pointed out how wrong this decision was. Dillon also jumped in and offered a better solution. What he got as reward was Scott Long telling him to go away. Listen Scott, YOU ARE A FUCKING IDIOT. Not only you don't even know how to quote, but you also managed to fuck the 5.1-R isos twice. I wonder how can you be in re@, that sure has lead to the piss-poor quality of the last 2 or 3 releases.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
9313Back in the day, around FreeBSD 2.2.8, it was a very nice operating system. However, when RELENG_5 was branched, a lot of wrong decisions were made, most of them by people with zero clue about how to implement proper SMP (e.g. John Baldwin). Matt Dillon tried to fix the situation, but all he got in response was a commit bit suspension, which later lead to his expulsion.
You can thank assholes like: Poul-Henning Kamp (POT, KETTLE, BLACK), Greg Lehey, Dag-Erling Smorgrav, Mark Murray and Bill Fumerola for kicking him out and making sure that, thanks to overengineering, RELENG_5 will never work.
Further proof, FreeBSD recently went 100% dynamic to allow the use of NSS switch system. John Dyson, who did most of the VM work back in the day, pointed out how wrong this decision was. Dillon also jumped in and offered a better solution. What he got as reward was Scott Long telling him to go away. Listen Scott, YOU ARE A FUCKING IDIOT. Not only you don't even know how to quote, but you also managed to fuck the 5.1-R isos twice. I wonder how can you be in re@, that sure has lead to the piss-poor quality of the last 2 or 3 releases.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
9883Back in the day, around FreeBSD 2.2.8, it was a very nice operating system. However, when RELENG_5 was branched, a lot of wrong decisions were made, most of them by people with zero clue about how to implement proper SMP (e.g. John Baldwin). Matt Dillon tried to fix the situation, but all he got in response was a commit bit suspension, which later lead to his expulsion.
You can thank assholes like: Poul-Henning Kamp (POT, KETTLE, BLACK), Greg Lehey, Dag-Erling Smorgrav, Mark Murray and Bill Fumerola for kicking him out and making sure that, thanks to overengineering, RELENG_5 will never work.
Further proof, FreeBSD recently went 100% dynamic to allow the use of NSS switch system. John Dyson, who did most of the VM work back in the day, pointed out how wrong this decision was. Dillon also jumped in and offered a better solution. What he got as reward was Scott Long telling him to go away. Listen Scott, YOU ARE A FUCKING IDIOT. Not only you don't even know how to quote, but you also managed to fuck the 5.1-R isos twice. I wonder how can you be in re@, that sure has lead to the piss-poor quality of the last 2 or 3 releases.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
1210Back in the day, around FreeBSD 2.2.8, it was a very nice operating system. However, when RELENG_5 was branched, a lot of wrong decisions were made, most of them by people with zero clue about how to implement proper SMP (e.g. John Baldwin). Matt Dillon tried to fix the situation, but all he got in response was a commit bit suspension, which later lead to his expulsion.
You can thank assholes like: Poul-Henning Kamp (POT, KETTLE, BLACK), Greg Lehey, Dag-Erling Smorgrav, Mark Murray and Bill Fumerola for kicking him out and making sure that, thanks to overengineering, RELENG_5 will never work.
Further proof, FreeBSD recently went 100% dynamic to allow the use of NSS switch system. John Dyson, who did most of the VM work back in the day, pointed out how wrong this decision was. Dillon also jumped in and offered a better solution. What he got as reward was Scott Long telling him to go away. Listen Scott, YOU ARE A FUCKING IDIOT. Not only you don't even know how to quote, but you also managed to fuck the 5.1-R isos twice. I wonder how can you be in re@, that sure has lead to the piss-poor quality of the last 2 or 3 releases.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
27127Back in the day, around FreeBSD 2.2.8, it was a very nice operating system. However, when RELENG_5 was branched, a lot of wrong decisions were made, most of them by people with zero clue about how to implement proper SMP (e.g. John Baldwin). Matt Dillon tried to fix the situation, but all he got in response was a commit bit suspension, which later lead to his expulsion.
You can thank assholes like: Poul-Henning Kamp (POT, KETTLE, BLACK), Greg Lehey, Dag-Erling Smorgrav, Mark Murray and Bill Fumerola for kicking him out and making sure that, thanks to overengineering, RELENG_5 will never work.
Further proof, FreeBSD recently went 100% dynamic to allow the use of NSS switch system. John Dyson, who did most of the VM work back in the day, pointed out how wrong this decision was. Dillon also jumped in and offered a better solution. What he got as reward was Scott Long telling him to go away. Listen Scott, YOU ARE A FUCKING IDIOT. Not only you don't even know how to quote, but you also managed to fuck the 5.1-R isos twice. I wonder how can you be in re@, that sure has lead to the piss-poor quality of the last 2 or 3 releases.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
17285Back in the day, around FreeBSD 2.2.8, it was a very nice operating system. However, when RELENG_5 was branched, a lot of wrong decisions were made, most of them by people with zero clue about how to implement proper SMP (e.g. John Baldwin). Matt Dillon tried to fix the situation, but all he got in response was a commit bit suspension, which later lead to his expulsion.
You can thank assholes like: Poul-Henning Kamp (POT, KETTLE, BLACK), Greg Lehey, Dag-Erling Smorgrav, Mark Murray and Bill Fumerola for kicking him out and making sure that, thanks to overengineering, RELENG_5 will never work.
Further proof, FreeBSD recently went 100% dynamic to allow the use of NSS switch system. John Dyson, who did most of the VM work back in the day, pointed out how wrong this decision was. Dillon also jumped in and offered a better solution. What he got as reward was Scott Long telling him to go away. Listen Scott, YOU ARE A FUCKING IDIOT. Not only you don't even know how to quote, but you also managed to fuck the 5.1-R isos twice. I wonder how can you be in re@, that sure has lead to the piss-poor quality of the last 2 or 3 releases.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
9445Back in the day, around FreeBSD 2.2.8, it was a very nice operating system. However, when RELENG_5 was branched, a lot of wrong decisions were made, most of them by people with zero clue about how to implement proper SMP (e.g. John Baldwin). Matt Dillon tried to fix the situation, but all he got in response was a commit bit suspension, which later lead to his expulsion.
You can thank assholes like: Poul-Henning Kamp (POT, KETTLE, BLACK), Greg Lehey, Dag-Erling Smorgrav, Mark Murray and Bill Fumerola for kicking him out and making sure that, thanks to overengineering, RELENG_5 will never work.
Further proof, FreeBSD recently went 100% dynamic to allow the use of NSS switch system. John Dyson, who did most of the VM work back in the day, pointed out how wrong this decision was. Dillon also jumped in and offered a better solution. What he got as reward was Scott Long telling him to go away. Listen Scott, YOU ARE A FUCKING IDIOT. Not only you don't even know how to quote, but you also managed to fuck the 5.1-R isos twice. I wonder how can you be in re@, that sure has lead to the piss-poor quality of the last 2 or 3 releases.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
7913At least the BSD community doesn't have a BSD company suing BSD providers.
Unlike GNU/Linux, where a company called Caldera IPOed based on 'selling a GNU/Linux fork', took the IPO money, bought up the SYS V UNIX IP rights, then started suing other members of the GNU/Linux 'community' once they figured out the business model for selling yet another GNU/Linux fork was not going to get them any $$$. With 'leading community members' like that, how can GNU/Linux be expected to beat Microsoft if they spend all their time beating up on each other?
I've been an avid follower of the developments in FreeBSD for around 5 years now, so my overview of the entire history of "glue that binds" FreeBSD together isn't complete. That said, I've come to be a bit disappointed at how events in the last 18 months or so seem to be pushing the project in a direction that has made things more difficult, instead of more successful, that has shown distain for experience and quality and made FreeBSD a platform for large ego's to push their personal projects down everyone's throat.
The statistics sample from 2001 over a year was a cheap attempt to minimize Matt's contribution to the project. The reason why he has been mostly silent is probably one of the most prominent signs of his superior maturity. The fact that the official defense (mostly fronted by Greg, atm) he wasn't such a substantial committer is crap, for the most part. If one wanted to go by the stats, Jeff Robertson (sorry if I munged the spelling) would be one of the key committers, and his UMA system isn't even entirely ripe yet, it's just been committed within the sample timeframe. That suddenly phk is at the top of the list, is simple a result of his newest attempt to add another large chunk of bit rot to the project that he can later claim not to have time to maintain "unless someone is willing to pay for my time" (like the atm bits, the half-finished devd monster, et.al.) One can hardly get him to look at his malloc bits, that put his name in lights at some point in the long past.
Matt didn't contribute because he was convinced that that the smp development direction that was chosen (my impression at least from the archives and my fading memory) was overly complex, too complex for the number and talent level of the contributers involved, and that it would delay a release from the -current branch significantly. So he was right. I'll almost bet that that was a constant sore for John, who still hasn't gotten his long-promised, but little delivered re-entrant work done, but he always had time enough to object to any other commits that might help along the way. Strangely Julian and Matt could work together. One might attribute certain commits to both Matt and Julian (if that would matter anyway, since -core is interested in proving the opposite statistically).
If the issue here had anything to do with IPFW, then you all better get out your C-coder hats and take a little more time to fix that rotting pile of muck that has been the standard broken packet filter interface for FreeBSD long past its possible usefulness. A packet filter with no central maintainer which is subject to once yearly random feature bloat through some wild university project from Luigi. The brokenness that Luigi introduced (and the repository bloat through backing out and recommitting, ad absurdum) was probably no less a threat to security than anything Matt did. If the security officer was to be blatantly honest with himself, ipfw would be marked broken for either a full audit or full removal (just port obsd's pf or something that someone actually actively _cares_ about).
You've alienated Jordan, Mike, Bill Paul (for all I can see), Greenman, you constantly rag on Terry, even though he's seen and done more with FreeBSD than most of you, O'Brien is on the verge of quitting (since he, like I, am not convinced that GEOM is anything more than an ego trip that will never be completely maintained or usefully documented). There are certainly others, too, that have attempted to make technically correct contributions, but didn't fit into the sort of paranoid "glee club" that core would like to have around them. You guys lack the talent to steer the positive from Matt into the project and let the crap fall by the wayside. I'm not saying Matt's rants are the most intelligent thing he's done, but he's sat by the wayside and watch the superstars beat up the code to a point where it's less stable, slower, and more bloated than it ever was. I, for one, can understand his frustration (as I can with Mike's, Jordan's, and a few o
I've been an avid follower of the developments in FreeBSD for around 5 years now, so my overview of the entire history of "glue that binds" FreeBSD together isn't complete. That said, I've come to be a bit disappointed at how events in the last 18 months or so seem to be pushing the project in a direction that has made things more difficult, instead of more successful, that has shown distain for experience and quality and made FreeBSD a platform for large ego's to push their personal projects down everyone's throat.
The statistics sample from 2001 over a year was a cheap attempt to minimize Matt's contribution to the project. The reason why he has been mostly silent is probably one of the most prominent signs of his superior maturity. The fact that the official defense (mostly fronted by Greg, atm) he wasn't such a substantial committer is crap, for the most part. If one wanted to go by the stats, Jeff Robertson (sorry if I munged the spelling) would be one of the key committers, and his UMA system isn't even entirely ripe yet, it's just been committed within the sample timeframe. That suddenly phk is at the top of the list, is simple a result of his newest attempt to add another large chunk of bit rot to the project that he can later claim not to have time to maintain "unless someone is willing to pay for my time" (like the atm bits, the half-finished devd monster, et.al.) One can hardly get him to look at his malloc bits, that put his name in lights at some point in the long past.
Matt didn't contribute because he was convinced that that the smp development direction that was chosen (my impression at least from the archives and my fading memory) was overly complex, too complex for the number and talent level of the contributers involved, and that it would delay a release from the -current branch significantly. So he was right. I'll almost bet that that was a constant sore for John, who still hasn't gotten his long-promised, but little delivered re-entrant work done, but he always had time enough to object to any other commits that might help along the way. Strangely Julian and Matt could work together. One might attribute certain commits to both Matt and Julian (if that would matter anyway, since -core is interested in proving the opposite statistically).
If the issue here had anything to do with IPFW, then you all better get out your C-coder hats and take a little more time to fix that rotting pile of muck that has been the standard broken packet filter interface for FreeBSD long past its possible usefulness. A packet filter with no central maintainer which is subject to once yearly random feature bloat through some wild university project from Luigi. The brokenness that Luigi introduced (and the repository bloat through backing out and recommitting, ad absurdum) was probably no less a threat to security than anything Matt did. If the security officer was to be blatantly honest with himself, ipfw would be marked broken for either a full audit or full removal (just port obsd's pf or something that someone actually actively _cares_ about).
You've alienated Jordan, Mike, Bill Paul (for all I can see), Greenman, you constantly rag on Terry, even though he's seen and done more with FreeBSD than most of you, O'Brien is on the verge of quitting (since he, like I, am not convinced that GEOM is anything more than an ego trip that will never be completely maintained or usefully documented). There are certainly others, too, that have attempted to make technically correct contributions, but didn't fit into the sort of paranoid "glee club" that core would like to have around them. You guys lack the talent to steer the positive from Matt into the project and let the crap fall by the wayside. I'm not saying Matt's rants are the most intelligent thing he's done, but he's sat by the wayside and watch the superstars beat up the code to a point where it's less stable, slower, and more bloated than it ever was. I, for one, can understand his frustration (as I can with Mike's, Jordan's, and a few o
I've been an avid follower of the developments in FreeBSD for around 5 years now, so my overview of the entire history of "glue that binds" FreeBSD together isn't complete. That said, I've come to be a bit disappointed at how events in the last 18 months or so seem to be pushing the project in a direction that has made things more difficult, instead of more successful, that has shown distain for experience and quality and made FreeBSD a platform for large ego's to push their personal projects down everyone's throat.
The statistics sample from 2001 over a year was a cheap attempt to minimize Matt's contribution to the project. The reason why he has been mostly silent is probably one of the most prominent signs of his superior maturity. The fact that the official defense (mostly fronted by Greg, atm) he wasn't such a substantial committer is crap, for the most part. If one wanted to go by the stats, Jeff Robertson (sorry if I munged the spelling) would be one of the key committers, and his UMA system isn't even entirely ripe yet, it's just been committed within the sample timeframe. That suddenly phk is at the top of the list, is simple a result of his newest attempt to add another large chunk of bit rot to the project that he can later claim not to have time to maintain "unless someone is willing to pay for my time" (like the atm bits, the half-finished devd monster, et.al.) One can hardly get him to look at his malloc bits, that put his name in lights at some point in the long past.
Matt didn't contribute because he was convinced that that the smp development direction that was chosen (my impression at least from the archives and my fading memory) was overly complex, too complex for the number and talent level of the contributers involved, and that it would delay a release from the -current branch significantly. So he was right. I'll almost bet that that was a constant sore for John, who still hasn't gotten his long-promised, but little delivered re-entrant work done, but he always had time enough to object to any other commits that might help along the way. Strangely Julian and Matt could work together. One might attribute certain commits to both Matt and Julian (if that would matter anyway, since -core is interested in proving the opposite statistically).
If the issue here had anything to do with IPFW, then you all better get out your C-coder hats and take a little more time to fix that rotting pile of muck that has been the standard broken packet filter interface for FreeBSD long past its possible usefulness. A packet filter with no central maintainer which is subject to once yearly random feature bloat through some wild university project from Luigi. The brokenness that Luigi introduced (and the repository bloat through backing out and recommitting, ad absurdum) was probably no less a threat to security than anything Matt did. If the security officer was to be blatantly honest with himself, ipfw would be marked broken for either a full audit or full removal (just port obsd's pf or something that someone actually actively _cares_ about).
You've alienated Jordan, Mike, Bill Paul (for all I can see), Greenman, you constantly rag on Terry, even though he's seen and done more with FreeBSD than most of you, O'Brien is on the verge of quitting (since he, like I, am not convinced that GEOM is anything more than an ego trip that will never be completely maintained or usefully documented). There are certainly others, too, that have attempted to make technically correct contributions, but didn't fit into the sort of paranoid "glee club" that core would like to have around them. You guys lack the talent to steer the positive from Matt into the project and let the crap fall by the wayside. I'm not saying Matt's rants are the most intelligent thing he's done, but he's sat by the wayside and watch the superstars beat up the code to a point where it's less stable, slower, and more bloated than it ever was. I, for one, can understand his frustration (as I can with Mike's, Jordan's, and a few o
I've been an avid follower of the developments in FreeBSD for around 5 years now, so my overview of the entire history of "glue that binds" FreeBSD together isn't complete. That said, I've come to be a bit disappointed at how events in the last 18 months or so seem to be pushing the project in a direction that has made things more difficult, instead of more successful, that has shown distain for experience and quality and made FreeBSD a platform for large ego's to push their personal projects down everyone's throat.
The statistics sample from 2001 over a year was a cheap attempt to minimize Matt's contribution to the project. The reason why he has been mostly silent is probably one of the most prominent signs of his superior maturity. The fact that the official defense (mostly fronted by Greg, atm) he wasn't such a substantial committer is crap, for the most part. If one wanted to go by the stats, Jeff Robertson (sorry if I munged the spelling) would be one of the key committers, and his UMA system isn't even entirely ripe yet, it's just been committed within the sample timeframe. That suddenly phk is at the top of the list, is simple a result of his newest attempt to add another large chunk of bit rot to the project that he can later claim not to have time to maintain "unless someone is willing to pay for my time" (like the atm bits, the half-finished devd monster, et.al.) One can hardly get him to look at his malloc bits, that put his name in lights at some point in the long past.
Matt didn't contribute because he was convinced that that the smp development direction that was chosen (my impression at least from the archives and my fading memory) was overly complex, too complex for the number and talent level of the contributers involved, and that it would delay a release from the -current branch significantly. So he was right. I'll almost bet that that was a constant sore for John, who still hasn't gotten his long-promised, but little delivered re-entrant work done, but he always had time enough to object to any other commits that might help along the way. Strangely Julian and Matt could work together. One might attribute certain commits to both Matt and Julian (if that would matter anyway, since -core is interested in proving the opposite statistically).
If the issue here had anything to do with IPFW, then you all better get out your C-coder hats and take a little more time to fix that rotting pile of muck that has been the standard broken packet filter interface for FreeBSD long past its possible usefulness. A packet filter with no central maintainer which is subject to once yearly random feature bloat through some wild university project from Luigi. The brokenness that Luigi introduced (and the repository bloat through backing out and recommitting, ad absurdum) was probably no less a threat to security than anything Matt did. If the security officer was to be blatantly honest with himself, ipfw would be marked broken for either a full audit or full removal (just port obsd's pf or something that someone actually actively _cares_ about).
You've alienated Jordan, Mike, Bill Paul (for all I can see), Greenman, you constantly rag on Terry, even though he's seen and done more with FreeBSD than most of you, O'Brien is on the verge of quitting (since he, like I, am not convinced that GEOM is anything more than an ego trip that will never be completely maintained or usefully documented). There are certainly others, too, that have attempted to make technically correct contributions, but didn't fit into the sort of paranoid "glee club" that core would like to have around them. You guys lack the talent to steer the positive from Matt into the project and let the crap fall by the wayside. I'm not saying Matt's rants are the most intelligent thing he's done, but he's sat by the wayside and watch the superstars beat up the code to a point where it's less stable, slower, and more bloated than it ever was. I, for one, can understand his frustration (as I can with Mike's, Jordan's, and a few o
No matter how much you try to patch it, there is a gaping hole left where FreeBSD's heart used to be. Now crows peck out its eyes, and the stench of death lays upon the land.
You fanatics, let BSD be. You come with your rakes and shovels to uncover that which has died long, long ago.
Robust anonymous P2P across a mobile/fixed wireless mesh networks are the future of the net and the old net can connect or die. Intel has hyped this new trend as bigger than the net, they also claim the can put they will put an xbox in a PDA. Given a little bit of time the telcos and the RIAA will die the same obsolete death. At the end of Q2 next year every new PC will ship with WiMax on board and this will do it.
I remember reading the remarks of someone is dismay over discovering that search engines were being used for info searches and not to locate websites. Of course, the Internet was alive and well before all this extraneous marketing fluff. Its number one application is not business or how much money can be made, in fact a key application may be ridding the public of may organizations that were not in its interest. The next net is bigger and it will not involve telco sponsored back bones and all that stuff. The net belongs to the public- sort of an immenient domain arguement but it is defacto.
The day will come when people buy that mainframe node in a pda, and there won't be room along the way for greedy snooping relics.
The issue is that througout the city we have omni antenna's - where -anyone- can associate with - and directional antennas which provide the interlinks between nodes (although the network covers a medium sized city - we use no copper; all interlinks are wireless).
On these interlinks we only want node-to-node traffic.
As the network is totally open (no username, password or any thing) - we have no easy way to educate our users to use the right 'omni' antenna's, other than descriptive names. I.e. we do not catch them early enough.
So often people associate with the interlinks rather than the omni (if a beam passes over their house) - and then complain, or are surprized, that DHCP does not give them an address.
This problem is made worse by some windows userinterface tools which will automatically re-select networks based on some internal metric.
So what we wanted was to 'hide' the interlinks. So that clueless users are not accidentally ensnared. Rolands patch does exactly this.
Dw
I love FreeBSD, but I have a question. When on earth is anyone going to recognize the fact that there is a serious problem with the wi driver for dwl650 pcmcia cards? So many of us have them and yet the current driver for it, after a small amount of usage causes a full system lock up. Anyone have any info on that? I'd like to see the drivers for widely used software perfected before setting up default security for those who don't know how to on their access points.
The question beg's to be asked, shouldn't someone capable of installing and using FreeBSD be knowledgeable enough to secure their wifi ap?
./revolution
I want to stick my pee pee in your poo poo hole
I want to stick my pee pee in your poo poo hole
I want to stick my pee pee in your poo poo hole
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page) # If you want replies to your comments sent to you, consider logging in or creating an account. I want to stick my pee pee in your poo poo hole
I want to stick my pee pee in your poo poo hole
I want to stick my pee pee in your poo poo hole
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page) # If you want replies to your comments sent to you, consider logging in or creating an account. I want to stick my pee pee in your poo poo hole
I want to stick my pee pee in your poo poo hole
I want to stick my pee pee in your poo poo hole
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page) # If you want replies to your comments sent to you, consider logging in or creating an account. I want to stick my pee pee in your poo poo hole
I want to stick my pee pee in your poo poo hole
I want to stick my pee pee in your poo poo hole
I want to stick my pee pee in your poo poo hole
I want to stick my pee pee in your poo poo hole
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page) # If you want replies to your comments sent to you, consider logging in or creating an account. I want to stick my pee pee in your poo poo hole
I want to stick my pee pee in your poo poo hole
I want to stick my pee pee in your poo poo hole
# Important Stuff: Please try to keep posts on topic. # Try to reply to other people's comments instead of starting new threads. # Read other people's messages before posting your own to avoid simply duplicating what has already been said. # Use a clear subject that describes what your message is about. # Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, b
I want to stick my pee pee in your poo poo hole
_ MM MM MMNMMMM MMMMMMMMM MMMMMMMMMMMMMMMM MMMMMM MMMNM MM M Fuck your mother
_ M_M_r'_.',._.',.',._.__________________.',._.',.'
_MM_W_M'_.',._.',.'---|Trollkore Forever!|---,_'_._`__7M_X_M Fuck your mother
_M,___M'_.',._.',.', _'------------------'_,_'_.',____M__B_0 Fuck your mother
_M_W__M'_.',._.',.',._.',.',._.', ',._.',._,_'_.',___WM__0_MX Fuck your mother
_M2_S_M_;_,_Xi'_.',.
_MS_@MM_X0'_.',._.',.',____S_____;i'_.',._.',.',_
_MWMMM'_._`__a0BMMMZ.',._`__XB_rS___.MMMMMMMMMB'_
_MM_MM____MMMMMMMMMMMMMMMMr'_._`_:MMMMMMMMMMMMMMM
_ MMM2__MMMM.____.MMMMMMMMMM __ XMMMMMMMMMMMMMMMMMMMM._BM:MX Fuck your mother
_ MMM__MMMMM|._. |MMMMMMMMMMM _ MMMMMMMMMMMMMMMMMMMMMM__MMMM Fuck your mother
_MMZ__BMMMMM||o| |MMMMMMMMMMM _ MMMMMMMMMMMMMMMMMMMMMB____MM Fuck your mother
_M____MMMMMM'----'MMMMMMMMMMM _ MMMMMMMMMMMMMMMMMMMMMW_WM__M Fuck your mother
WM__i_MMMMMMMMMMMMMMMMMMMMMMM _M MMMMMMMMMMM.____.MMM,_____M0 Fuck your mother
MX__r_MMMMMMMMMMMMMMMMMMMMMM'_._` MMMMMMMMMM|._. |MMM'_._`_MM Fuck your mother
MZ____7MMMMMMMMMMMMMMMMMMMM __._Z_ MMMMMMMMM||o| |MMM__X___ZM Fuck your mother
MM__Z__MMMMMMMMMMMMMMMMMM; __MM_MM_ WMMMMMMM'----'MM__a____M0 Fuck your mother
_M__,r___XMMMMMMMMMMMMM ___:MMM_MMM:_ MMMMMMMMM MM____7____M Fuck your mother
_MM'_.',____,M0'_.',_____,,MMMB_MMMM_,____ZMMM:__
_ M_____ii_X___7__S_,2____SMMMM_MMMM'_.',______2:r'
_ MM'_.',._.',._,_'_._`_8:MMMMM_MMMMM_;__;ii.',._,_
__ MM'_.',._.',.',______;WMMMMM_MMMMM_M'_.',._.',.',
____ MMM'_.',._.',.',_____MMMMM_MMMMM'_.',._.',.',___X
____ 0MMMMr'_._,_'_.',____BMMM@_ZMMM;'_._,_'_._`__aMMM
'_._` MMMMMM_M_,__;'_._,_'_._`_i'_._,_'_._`_i____MMMMaM
'_._` M__BMMMM_2_ZM__@r___Z'_.',___,,__._'___M__;M@___M Fuck your mother
'_._` MM___M2MMM8M___Z___XM___X,____M._r_____MMMM@____M Fuck your mother
'_._` MM___M___ZMMMMMMMMMMMiMMM_____WMSMMMMMMM_ZM____MM Fuck your mother
'_._`_ MW__MM__W__X___M___iMaXMMMMMMBM_S__7__:_MM____MX Fuck your mother
'_._`_ MM__XMM2MM_M___M___,r__M'
'_.',__ M2__M__@__MMMMMMMMMr _M__M._MM_ZMZMM_;MM____MM Fuck your mother
'_.',___ M___MMM0_Z___M_ _MMB7MM2MM_M__S_____MW_____M Fuck your mother
'_.',___ M_____SMMMMWSM_ __i__M___a_M___M:MMB_S____MM Fuck your mother
'_.',___ MM'_.',___2XMMMWMMMM0MMMMMMMMMMMM__r_____2M Fuck your mother
'_.',____ MM_:'_.',______;_____8'_.',._.',.',____MM Fuck your mother
'_.',_____ XMMM'_._`_.aM'_._`__, ____;;:'_._`__MMM Fuck your mother
'_._,_'_.',__ WMM'_._,_'
'_.',._.',.',__ MMM_:__,____M.__XS2,_____ZMMMX Fuck your mother
'_.',._.',.',___ rMMMZMM___;____B_____rMMMM Fuck your mother
'_.',._.',._,_'_._` irXS2MMMMMMB8ZMMMMX: Fuck your mother
I want to stick my pee pee in your poo poo hole
1. You can not play games on it.
2. It cannot be used by my grandma.
3. It lacks a GUI of any note.
4. There is no support available for it.
5. It is an assortment of fragmented OSes.
6. It cannot be run on the x86 platform.
7. You have to compile everything and know C.
8. Support for the latest hardware is always poor.
9. It is incompatiable with GNU/Linux.
10. It is dying.
We need to see more of this good shit in the BSD section.
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 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 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 dead
The Year of Our Lord 2003 has been a particularly bad year for the "B"s,
- Bob Hope
- Buddy Ebsen
- Buddy Hackett
- Barry White
- BSD
This honored list of dead is but a small token of adieu from the many fans of the deceased.These dead were truly some American Icons. They will be missed.
Access points broadcast beacon frames, which contain some information about the AP, including the name (SSID). If there are multiple APs in range, the SSID helps you identify and select the right one.
Now, what the patch does is hide the SSID in the beacon frames, and blocks clients with SSID "ANY". This prevents clients from automatically associating with the AP with best signal quality.
Hiding the SSID doesn't help a lot, because advanced wardriving tools like Kismet will still pick up the network. It keeps script kiddies out though, Netstumbler (Windows wardriver) won't see the AP.