Free for All by Peter Wayner (good books to read for young adults .TXT) 📕

Of course, the folks who are working on free software projects have advantages that money can't buy. These programmers don't need lawyers to create licenses, negotiate contracts, or argue over terms. Their software is free, and lawyers lose interest pretty quickly when there's no money around. The free software guys don't need to scrutinize advertising copy. Anyone can download the software and just try it. The programmers also don't need to sit in the corner when their computer crashes and complain about the idiot who wrote the software. Anyone can read the source code and fix the glitches.

The folks in the free source software world are, in other words, grooving on freedom. They're high on the original American dream of life, liberty, and the pursuit of happiness. The founders of the United States of America didn't set out to create a wealthy country where citizens spent their days worrying whether they would be able to afford new sport utility vehicles when the stock options were vested. The founders just wanted to secure the blessings of liberty for posterity. Somehow, the wealth followed.

This beautiful story is easy to embrace: a group of people started out swapping cool software on the Net and ended up discovering that their free sharing created better software than what a corporation could produce with a mountain of cash.

The programmers found that unrestricted cooperation made it easy for everyone to contribute. No price tags kept others away. No stereotypes or biases excluded anyone. The software and the source code were on the Net for anyone to read.

Wide-open cooperation also turned out to be wide-open competition because the best software won the greatest attention. The corporate weasels with the ear of the president could not stop a free source software project from shipping. No reorganization or downsizing could stop people from working on free software if they wanted to hack. The freedom to create was more powerful than money.

That's an idyllic picture, and the early success of Linux, FreeBSD, and other free packages makes it tempting to think that the success will build. Today, open source servers power more than 50 percent of the web servers on the Internet, and that is no small accomplishment. Getting thousands, if not millions, of programmers to work together is quite amazing given how quirky programmers can be. The ease of copying makes it possible to think that Alan Cox could get up late and still move the world.

But the 1960s were also an allegedly idyllic time when peace, love, and sharing were going to create a beautiful planet where everyone gave to everyone else in an eternal golden braid of mutual respect and caring. Everyone assumed that the same spirit that so quickly and easily permeated the college campuses and lovefests in the parks was bound to sweep the world. The communes were really happening, man. But somehow, the groovy beat never caught on beyond those small nests of easy caring and giving. Somehow, the folks started dropping back in, getting real jobs, taking on real mortgages, and buying back into the world where money was king.

Over the years, the same sad ending has befallen many communes, utopian visions, and hypnotic vibes. Freedom is great. It allows brilliant inventors to work independently of the wheels of power. But capital is another powerful beast that drives innovation. The great communes often failed because they never converted their hard work into money, making it difficult for them to save and invest. Giving things away may be, like, really groovy, but it doesn't build a nest egg.

Right now, the free software movement stands at a crucial moment in its history. In the past, a culture of giving and wide-open sharing let thousands of programmers build a great operating system that was, in many ways, better than anything coming from the best companies. Many folks began working on Linux, FreeBSD, and thousands of other projects as hobbies, but now they're waking up to find IBM, HewlettPackard, Apple, and all the other big boys pounding on their door. If the kids could create something as nice as Linux, everyone began to wonder whether these kids really had enough good stuff to go the distance and last nine innings against the greatest power hitters around.

Perhaps the free software movement will just grow faster and better as more people hop on board. More users mean more eyes looking for bugs. More users mean more programmers writing new source code for new features. More is better.

On the other hand, sharing may be neat, but can it beat the power of capital? Microsoft's employees may be just serfs motivated by the dream that someday their meager stock options will be worth enough to retire upon, but they have a huge pile of cash driving them forward. This capital can be shifted very quickly. If Bill Gates wants 1,000 programmers to create something, he can wave his hand. If he wants to buy 1,000 computers, it takes him a second. That's the power of capital.

Linus Torvalds may be on the cover of magazines, but he can't do anything with the wave of a hand. He must charm and cajole the thousands of folks on the Linux mailing list to make a change. Many of the free software projects may generate great code, but they have to beg for computers. The programmers might even surprise him and come up with an even better solution. They've done it in the past. But no money means that no one has to do what anyone says.

In the past, the free software movement was like the movies in which Mickey Rooney and Judy Garland put on a great show in the barn. That part won't change. Cool kids with a dream will still be spinning up great programs that will be wonderful gifts for the world.

But shows that are charming and fresh in a barn can become thin and weak on a big stage on Broadway. The glitches and raw functionality of Linux and free software don't seem too bad if you know that they're built by kids in their spare time. Building real tools for real companies, moms, police stations, and serious users everywhere is another matter. Everyone may be hoping that sharing, caring, and curiosity are enough, but no one knows for certain. Maybe capital will end up winning. Maybe it won't. It's freedom versus assurance; it's wide-open sharing versus stock options; it's cooperation versus intimidation; it's the geeks versus the suits, all in one knockdown, hack-till-you-drop, winner-take-everything fight.

While Alan Cox was sleeping late and Microsoft was putting Richard Schmalensee on the stand, the rest of the open source software world was tackling their own problems. Some were just getting up, others were in the middle of their day, and still others were just going to sleep. This is not just because the open source hackers like to work at odd times around the clock. Some do. But they also live around the globe in all of the different time zones. The sun never sets on the open source empire.

On January 14, 1999, for instance, Peter Jeremy, an Australian, announced that he had just discovered a potential Y2K problem in the control software in the central database that helped maintain the FreeBSD source code. He announced this by posting a note to a mailing list that forwarded the message to many other FreeBSD users. The problem was that the software simply appended the two characters "19" to the front of the year. When the new millennium came about a year later, the software would start writing the new date as "19100." Oops. The problem was largely cosmetic because it only occurred in some of the support software used by the system.

FreeBSD is a close cousin to the Linux kernel and one that predates it in some ways. It descends from a long tradition of research and development of operating systems at the University of California at Berkeley. The name BSD stands for "Berkeley Software Distribution," the name given to one of the first releases of operating system source code that Berkeley made for the world. That small package grew, morphed, and absorbed many other contributions over the years.

Referring to Linux and FreeBSD as cousins is an apt term because they share much of the same source code in the same way that cousins share some of the same genes. Both borrow source code and ideas from each other. If you buy a disk with FreeBSD, which you can do from companies like Walnut Creek, you may get many of the same software packages that you get from a disk from Red Hat Linux. Both include, for instance, some of the GNU compilers that turn source code into something that can be understood by computers.

FreeBSD, in fact, has some of its own fans and devotees. The FreeBSD site lists thousands of companies large and small that use the software. Yahoo, the big Internet directory, game center, and news operation, uses FreeBSD in some of its servers. So does Blue Mountain Arts, the electronic greeting card company that is consistently one of the most popular sites on the web. There are undoubtedly thousands more who aren't listed on the FreeBSD site. The software produced by the FreeBSD project is, after all, free, so people can give it away, share it with their friends, or even pretend they are "stealing" it by making a copy of a disk at work. No one really knows how many copies of FreeBSD are out there because there's no reason to count. Microsoft may need to count heads so they can bill everyone for using Windows, but FreeBSD doesn't have that problem.

That morning, Peter Jeremy's message went out to everyone who subscribed to the FreeBSD mailing list. Some users who cared about the Y2K bug could take Jeremy's patch and use it to fix their software directly. They didn't need to wait for some central bureaucracy to pass judgment on the information. They didn't need to wait for the Y2K guy at FreeBSD to get around to vetting the change. Everyone could just insert the fix because they had all of the source code available to them.

Of course, most people never use all their freedoms. In this case, most people didn't have to bother dealing with Jeremy's patch because they waited for the official version. The FreeBSD infrastructure absorbed the changes into its source code vaults, and the changes appeared in the next fully updated version. This new complete version is where most people first started using the fix. Jeremy is a programmer who created a solution that was easy for other programmers to use. Most people, however, aren't programmers, and they want their software to be easy to use. Most programmers aren't even interested in poking around inside their machines. Everyone wants the solution to either fix itself or come as close to that as possible.

Jeremy's message was just one of the hundreds percolating through the FreeBSD community that day. Some fell on deaf ears, some drew snotty comments, and a few gathered some real attention. The mailing lists were fairly complex ecologies where ideas blossomed and grew before they faded away and died.

Of course, it's not fair to categorize the FreeBSD world as a totally decentralized anarchy. There is one central team led by one man, Jordan Hubbard, who organizes the leadership of a core group of devoted programmers. The group runs the website, maintains an up-to-date version of FreeBSD, and sponsors dozens of lists devoted to different corners or features. One list focuses on hooking up the fast high-performance SCSI hard disks that are popular with people who demand high-performance systems. Another concentrates on building in enough security to keep out attackers who might try to sneak in through the Internet.