Slashdot Mirror
FreeBSD 4.8 RC2 / i386 Now Available
Dan writes "FreeBSD Release Engg. Team's Murray Stokely announces the availability of FreeBSD 4.8 RC2 for i386, he says that the alpha build is in progress. You can download 4.8 RC2 mini iso, install iso's, etc. from FreeBSD ftp site or from one of the mirror sites."
The word on the grapevine is (especially in light of the recent deal of isonews.com) is that programs that are commonly used to move software are being bugged magic lantern style by the Federal Gestapo, with FlashFXP's culled data being used as evidence against several people recently in Federal Court! Beware, you may be inviting the vampire in with this software!
A few of my friends have been bitten by DeWeese's shyster tactics. I have too. I can only say avoid this man. He will not answer questions directly, he will not tell you what is the payload of encrypted packets and he insinuates a symbol-less stripped binary created by an obscure (but good) compiler could be reverse engineered enough to prove it is not Trojaned. Its crap. Its dodgy crap. And until the encrypted payload is decrypted, and some source code is released, you have to take his word. And don't; because if you can't trust him to give you the free upgrades he promised because you have 5 computers at home and now you are a pirate if he detects you using FFXP_666 on any of them even if its not at the same time. Try a dual boot, and you'll get the blacklist. Try FFXP on WINE, you'll get the blacklist. Think before paying. This stuff is going to haunt you. And notably absent, OS X and a unice version. Guess he isn't very savvy at writing portable code, probably busy cutting deals with Ashcroft, Robert Mueller, Louis Freeh, Robert Holleyman [BSA], Comet Cursor, Alexa, Aureate, Aureate, Gator and backdooring your computer and canceling registrations and blacklisting people to be bothered with you and your plebian needs. Guess we sheeple are born to serve the masters like Count DeWeese and his squadron of Shylock lawyers with that EULA of DEATH. Just read it. This man is sick, and you will be knifed in the back by him. Read the EULA, see the packets encrypted. No source. And disassembling this wont tell you one way or another what it does for sure. It may not have spyware in it, it might BE spyware. Your info - sold - to the lowest forms of life on earth. No source code, lots of general distrust from many sources, and refusal to completely deny that his calling home is anything more than registration and blacklist data. It's encrypted, so your private information, even yours ftp site list, your machine's sid, your media players GUID, all sorts of UIDs, your life sold down the river to a black-hearted money grubbing heathen. I am appalled DeWeese and his minions have so successfully pulled wool over everyone's eyes. This is as bad as the Nazis with the Reichstag fire! I can't believe Charles the totalitarian and his army of mediocritomatons had the review history wiped out here! He did that to mask the evil at hand. He has sold his own user community to marketers, and his program makes undocumented undesired connections to the internet. He has revoked registrations without cause, had possibly sent ftp saved site data to law enforcement, and frequently uses encrypted payloads in packets so packet sniffer can't tell what the packet has in it. I would hope for your sake you don't save passwords with FlashFXP, our your friends FTP site may become "exhibit A" in a federal court. Beware. WARNING FLASH FXP 2.X IS A TROJAN
And all previous build before and most likely all to come. I implore every use of this software to be weary and on guard! I would have a good firewall with a drop all, allow exception rule set, ethereal, windump/[tcpdump on *nix], and a pcap lib, or use sniffer, and get ready to watch this thing with hawk eyes. Given the author's tradition of reporting usage, selling information to marketing companies, and revoking registrations without cause, we must be prepared for his latest Trojan horse. The program is delightful, irresistible, for it is feature laden, stable. But its target is warez users, and I strongly feel this warez-centric program serves to report to the government the biggest abuses. Remember, that the information he claims is benign is encrypted, so you will never see the payload of this machinations an
Just to explain, for any who aren't familiar with the FreeBSD release process:
FreeBSD 4.8 will be the latest release from the FreeBSD 4-STABLE branch. This could also be thought of for the time being as the -STABLE branch, as there is not yet a 5-STABLE. A lot of the goodies from 5.0 (5-CURRENT) have been merged-from-current (MFC'd) into 4.8, including Firewire and bugfixes. It's GCC2-based, and I run it on my laptop with much luck, though it lacks a lot of the ACPI goodness in 5.
5.0 is a release from 5-CURRENT. Just as they did with 4.0 before, it is released before there is a formal -STABLE branch, which is expected to appear somewhere around 5.1 or 5.2. I use it on all my workstations, and it flies -- GCC3-based, with new kernel magic that has (at least for me) dramatically improved responsiveness.
Which is no small feat, since my FreeBSD/KDE desktops consistently outperform my equivalent Linux machines in terms of, say, running two makes while playing a song over NFS with no skips. (These are k6-2 machines, one with FreeBSD5, one with Gentoo.)
The 4.0 branch will continue to be developed well into the lifetime of 5, just as 3.0 was before it. (Development on 3-STABLE only recently slowed down; it benefited from most of the bugfixes in 4 that didn't break compatibility.)
My suggestions to someone wanting to run FreeBSD right now? If it's a production machine, I'd stick to 4.7 or 4.8, simply because the ability to track the -STABLE branch with cvsup is really nice. Also, if you're not comfortable with updating your sources and recompiling your world periodically, stick to 4.x; since 5.0 doesn't yet have a controlled -STABLE branch, it will occasionally have broken features, though this has only happened to me once.
On the other hand, if you have a recent machine, need good ACPI support, or want to see what all the fuss is about, try 5.0. I use it with great success -- just be warned, you may have to recompile things every so often until it goes -STABLE.
Happy BSDing!
5.0 is suposed to be a bleading-edge technology release.
Given that, 5.0 has been working wonderfully as a Samba server for the last two weeks at two sites.
Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.
i guess nobody cares???
[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'
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
[note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It's wh
pee?
Is BSD Dying? Trolls! Make with the trolling. Jeez...
Recursive (adj.): see 'Recursive'
It doesn't really have any industry support. I guess it is mostly targeted at hobby
interests (more or less). Unfortunately, I'm not looking for a new hobby at this time.
using unstable code for a samba server seems asinine unless you have some sort of esoteric feature requirement
I think it's great that there are still multiple open-source OSes being developed. Competition helps everybody get better.
A Multiplayer Strategy Game for Mac OS X, Windows, and Linux
Sigh.
Wake me when they ship a modern JDK. No, not a buildable patchwork from sources, patches, and linux emulation bootstrapping - a real binary JDK.
Subject says it all.
Just consider this:
Right now you have America and Iraq.
Back then you had America and USSR and Iraq.
Now ofcourse USSR is dead.
Wasnt it better back then??
Think about it for a while Joe.