Slashdot Mirror
FreeBSD 5.2-RC1 Released
Dan writes "FreeBSD Release Engineering Team's Scott Long has uploaded ISO images and FTP install bits for FreeBSD 5.2-RC1. i386, alpha, and pc98 are available now, amd64 will be available shortly, and sparc64 will be available shortly. Please test this as much as possible so that the FreeBSD Team can release a good 5.2-RELEASE next week. Testing focus for 5.2-RELEASE relates to PCM locking and performance issues, ATA driver improvements, GPT support for sysinstall, ATAng disk corruption issues, SMP and random_harvest panic, vinum data corruption, ACPI kernel module and reported NFS failures."
Cheers to the FreeBSD team for bringing us this minor version change.
If Tomorrow Starts Without Me
by *BSD
When tomorrow starts without me
and I'm not there to see..
If the sun should rise
and find your eyes..
all filled with tears for me.
I wish so much you wouldn't cry..
the way you did today,
while thinking of the many things
we didn't get to say.
I know how much you love me,
with the clever tricks I do,
and each time that you think of me,
I know you'll miss me too;
But when tomorrow starts without me,
please try to understand,
that an Angel came and called my name,
and took me by the hand,
It said I had been dead for years,
my heart had filled with hate,
and that you'd switch to a better OS,
like Windows '98
third fp for my bro dandan
Maybe it hasn't had a remote root compromise yet, but somehow that doesn't concern me when my data is compromised from within. I've got the drives wiped again, but I think I'll put Gentoo on there this time just to be on the safe side. Maybe I'll give it another shot with my next non-critical build, because I really do like the interface and system management style.
Get the new BSD, sanctioned and cleared by SCO, for just $699, and if you moderate this post up, you get a 66.6% discount and free penguin corpse.
http://www.699bsd.sco.com/
Just get 4-LATEST or 5-CURRENT...
SCC makes you pay them $699 if you DON'T use Linux.
The recording industry sells all their material online, in a usable format, at a fair price
We don't, for one, welcome our new overlords.
Windows Security is not an oxymoron
All the trolls can't stop proclaiming how *BSD is so alive.
Don't blame Durga. I voted for Centauri.
Last night I was grabbing some 5.1 isos and happened to see 5.2 had just been updated to RC1 so I went ahead and grabbed them. As always another quality release from the FreeBSD team.
then go to releases/ARCH/ISO-IMAGES/5.2-RC1
Going strong, in a mature way! You know, I stay impressed with the quality of FreeBSD. As a longtime UNIX user and Linux user, FreeBSD has the professional "sheen" that I would expect from Solaris or AIX. While I enjoyed using Linux, it was the small things in FreeBSD that made me happy. Complete man pages, vs. halfway done man pages and broken info pages, or ports, or how there was a new kernel of the week (eerie similar to Microsoft). I like the fact that FreeBSD was rather set it up, update it, build your software, and forget about it. It's hard to make the 4.x series die, and the 5.x series is looking close to or already is enterprise ready. Good Luck, God Bless, and keep up the good work FreeBSD Team.
http://www.freebsd.org
The proof is in the pudding.
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 10306ynamic 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 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.
Joseph Mallett, an ex-committer.
0Back 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 13762ynamic 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 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.
Joseph Mallett, an ex-committer.
0Back 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 3126ynamic 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 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.
Joseph Mallett, an ex-committer.
0Back 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 8130ynamic 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 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.
Joseph Mallett, an ex-committer.
0Back 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 22867ynamic 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 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.
Joseph Mallett, an ex-committer.
0Back 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 1011ynamic 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 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.
Joseph Mallett, an ex-committer.
0Back 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 30646ynamic 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 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.
Joseph Mallett, an ex-committer.
0Back 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 4192ynamic 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 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.
Joseph Mallett, an ex-committer.
0Back 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 27885ynamic 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 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.
Joseph Mallett, an ex-committer.
0Back 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 8067ynamic 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 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.
Joseph Mallett, an ex-committer.
0Back 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 17948ynamic 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 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.
Joseph Mallett, an ex-committer.
0Back 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 27449ynamic 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 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.
Joseph Mallett, an ex-committer.
0Back 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 11672ynamic 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 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.
Joseph Mallett, an ex-committer.
0Why should I use FreeBSD over Linux?
The reason I'm asking is this: despite having used Linux for many years, I'm constantly being told by FreeBSD fans to switch to their favourite OS. Some make pleasant suggestions, others act with great zealotry and tell me things I know aren't true. The way I see it is as follows:
Stability - Various BSD fans have told me that it's "more stable" and "crashes less". I can safely say that my Debian and Slackware boxes have _never_ crashed or kernel panicked in five years of use; yes, in comparison to a bleeding edge desktop distro such as Mandrake, FreeBSD is bound to be more solid, but proper, well-designed and thoroughly tested distros like Debian and Slackware are totally rock-solid.
Performance - I've been told by FreeBSD users that their OS is much faster than Linux. To make this judgement myself, I performed a few benchmarks with FreeBSD 4.8 and Linux 2.4.20, and also FreeBSD 5.1 and Linux 2.6.0-test. The differences were negligible, although on my 2-CPU box Linux was the clear winner. 2.6.0-test also showed more responsive behaviour on the desktop.
Hardware support - I had troubles getting FreeBSD running on my laptop. Linux supported the hardware much better, and has a significantly broader range of x86 support.
Software support - It's so much easier to find software that will compile natively on Linux. Yep, Ports are good, but they're nowhere near as tested and integrated as, say, Debian's stable repositories.
Security - Both OSes are pretty secure by modern standards, but I can't see the value in FreeBSD's updating method. With Debian, one simple "apt-get" command is needed to get the latest security fixes. With FreeBSD, a tiresome chore of CVSuping, compiling and installing is required, which is doubly annoying on lots of boxes.
Community - Even when I've researched my problem and read up on the docs, I've had BSD fans act incredibly obnoxiously towards me. That's not good at all.
Long term support - FreeBSD only supports each release for 12 months; this means that users have to upgrade. And although upgrading isn't too difficult, the end result is a slightly different system and difficult to target apps against (new features/bugs/changes is newer Ports releases etc). Meanwhile, Debian has over 2 years support for each release, and Red Hat offer 5 - perfect for corporate adoption.
So those are the criteria I judge an OS on, and while many BSD fans keep telling me to use FreeBSD, I can't see what it offers in the real-world over Linux (subjective licensing issues aside).
What concrete benefits does FreeBSD actually offer? Serious question. It appears that Linux wins in the above areas, but any input would be good to hear.
I don't want to start a holy war here, but what is the deal with you BSD fanatics? I've been sitting here at my freelance gig in front of a BSD box (a PIII 800 w/512 Megs of RAM) for about 20 minutes now while it attempts to copy a 17 Meg file from one folder on the hard drive to another folder. 20 minutes. At home, on my Pentium Pro 200 running NT 4, which by all standards should be a lot slower than this BSD box, the same operation would take about 2 minutes. If that.
In addition, during this file transfer, Netscape will not work. And everything else has ground to a halt. Even Emacs Lite is straining to keep up as I type this.
I won't bore you with the laundry list of other problems that I've encountered while working on various BSD machines, but suffice it to say there have been many, not the least of which is I've never seen a BSD box that has run faster than its Windows counterpart, despite the BSD machines faster chip architecture. My 486/66 with 8 megs of ram runs faster than this 800 mhz machine at times. From a productivity standpoint, I don't get how people can claim that BSD is a "superior" machine.
BSD addicts, flame me if you'd like, but I'd rather hear some intelligent reasons why anyone would choose to use a BSD over other faster, cheaper, more stable systems.
We look forward to AMD64 support coming soon, FreeBSD has been the most reliable OS we have ever used, next to our OpenBSD firewalls.
[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
See my post that discusses this issue
Can't handle the truth
Idiot.
Dead Man Walking
Death of a Salesman
Dead Poets Society
Death to Smoochy
Murder at 1600
A Prayer for the Dying
The Art of Dying
Homicide: Life on the Street: Seasons 1 & 2
Everest: The Death Zone
Dead Presidents
The Dead Zone
I must make it clear that:
1) *BSD is associated with the Devil (see mascot).
2) *BSD promotes anti-social behaviour.
3) *BSD encourages a homosexual lifestyle.
4) *BSD stands for destruction of the economy.
5) *BSD attacks the average man in the street.
6) *BSD allows no critisms of its mission.
7) *BSD harbours terrorists and other state enemies.
8) *BSD collects weapons of mass destruction.
9) *BSD believes in the enprisionment of mankind.
10) *BSD is dying.
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.
.... otherwise this mentally retarded deranged individual wouldn't be spending so much time trying to discredit it.
Seems like this nut runs a Windows or Linux business and feels threatened by FreeBSD!
Can't wait for FreeBSD 5.2 next week, this freak will go nuts!
Don't give the trolls satisfaction of replying to them and thus feeding them to post more.
You people just never get it..
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.
Browsing through the source code of *BSD is a little bit like reading the diary of a dead man.
Why did you mod the parent down but not the grandparent?
Oh thats right, BSD moderators don't believe in fair moderation, only in pro-BSD moderation.
Oh, you're all going to love this!
Free Willy died -- now if you trolls don't come up with some VERY clever trolls in the next FreeBSD post, I'll be sorely disappointed.
Remember: we're all counting on you!!
Nazism must be good, otherwise those uppity Jews wouldn't be spending so much time talking about how evil it was.
I regret to inform you that not all trolls are mentally retarded. In fact I'm far from it.
As a 'BSD is dying' troll I hate BSD because it is crawling with zealots. I'm not scared at all from an OS that is clearly losing users and importance.
Not the OS that is the problem, just the (l)users.
Yours Sincerely,
A. Troll.
P.S. BSD is dying.
In addition, he also can have burned a strong, beautiful fire within his abdomen. It can burn out the dirty stickiness of his body, release his immaterial fiber or third attention, which has been confined to his stickiness. Then, he can shoot out his immaterial fiber or third attention to an object, concentrate on it and attain happy lucky feeling through the success of concentration.
If you don't know concentration, which gives you peculiar pleasure, your life looks like hell.
let me reprint my review of FreeBSD 5.2-RC1 here:
It don't boot for SHIT.
one more release closer to 5.x -stable
After we upgrade to 5.2 we probably won't have to reboot until we install 5.3!
Redundant..
because BSD users already know the painful truth..
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.
The numbers continue to decline for *BSD but FreeBSD may be hurting the most. Look at the numbers. The loss of user base for FreeBSD continues in a head spinning downward spiral. In truth, for all practical purposes FreeBSD is already dead. It is a dead man walking.
It's a fact: FreeBSD is dying.
"2. It cannot be used by my grandma"
Hmmm.... grandma.... is this like the same situation with your friend with the sexually transmitted disease via anal intercourse.
It took you four days to come up with that? Go back to playing with your letter blocks.
flask of ripe urine
pressed to dead bsd lips
bsd drink up
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 legitimize 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.
What I would really like to see is multiple IP's and private System V IPC in jails. It doesn't look like it made it into 5.2, unfortunately....
--
OpenHosting Virtual Servers for the geeks.
"Gillespie, this bitch is dead. It's meat wagon time . . ."
Two thoughts come to mind while reading this:
1) Haven't they asked you, repeatedly, (and besides that, isn't it better etiquette...) to point to a list of mirrors instead of directly to an FTP site?
2) Just saw an ad for Slashdot personals. Heh.
Me: So, you read slashdot?
Her: Yeah.
Me: I gotta get going now, nice meeting you.
- deal with the inevitable.
- grieve for your loss.
- move on.
Never let your emotions get tangled up with something as silly as a computeroperating system. It isn't healthy. So BSD fails. Big whoop. Deal with it and move on.
If you are upgrading to 5.2-RC1 (or -CURRENT) via cvsup/buildworld, make sure that you read UPDATING - just like I didn't :-). Of course, this applies to any time you build. However, it's especially important now or you will have a broken system.
Graham
Graham
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.