V2TXZi
V2TXZi
V2TXZi
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
34 CHAPTER 1<br />
primarily by word of mouth (in person or online) at school or work, or perhaps<br />
through one of the early print journals. As one South African developer<br />
now living in the Netherlands recounted during an interview:<br />
It was a friend in that big [college] residence who came along with a<br />
� oppy, and because of his typical, very dramatic personality, he just<br />
put the � oppy in my computer and switched it on, and up came Linux<br />
0.9, and it was the end of 1993 and that was the end for me as well,<br />
or at least the beginning. All these � ashing lines coming by [ . . . ] just<br />
immediately appealed to me.<br />
The “ah- ahhh,” “oh my gosh,” “this is so cool,” “oh my god” factor of discovering<br />
free software depended on a myriad of intersecting elements. For<br />
some hackers, free software meant they could � nally have a workable Unix<br />
operating system for their personal computer (previously, Unix ran primarily<br />
on larger, more expensive machines). Gone were the days of having to<br />
trudge through snowy streets to access a beloved Unix machine in the computer<br />
science department.<br />
Prior to Linux, there were few workable Unix systems that ran on personal<br />
computers and were nonproprietary. The production of Linux thus<br />
represented a general liberation of the Unix architecture, and also inaugurated<br />
its individualization, decentralization, and proliferation. Unhitched<br />
from the sole province of the university, corporation, and stringent rules<br />
of conventional intellectual property law, Linux was released as a public<br />
good and was also produced in public fashion through a volunteer association.<br />
10 Most signi� cantly, hackers were able to run Linux on mass- produced<br />
personal computers at home, spending more quality one- on- one time than<br />
before with an architecture that even now, still demands an active and dedicated<br />
partner. One programmer explained his early excitement as “� nally”<br />
having “a workshop with all the most powerful tools to hack on real stuff at<br />
home.” Most young hackers, however, were thrilled, and many were downright<br />
“� oored,” at the newfound unlimited access to source code.<br />
Yet the real adventure of free software came after its discovery. In the<br />
early days, when Linux distributions were only available off the Net, one<br />
had to download the system from a slow connection, usually a modem— a<br />
technical feat in and of itself. Taking at least a week to accomplish, the<br />
connection would undoubtedly crash, multiple times (but fortunately the<br />
download protocols allowed resuming from where it crashed), and a number<br />
of the � oppies would invariably be corrupt. Once completed, Linux<br />
would often occupy around “forty � oppy disks.” 11 With a stack of � oppies,<br />
some hackers would immediately begin installation, and then had to hack<br />
at the system to make it actually work. Others � rst had to fend off accusations<br />
of piracy from what some developers intimated was some pesky,<br />
ignorant, low- level computer lab administrator. The annoyed but excited<br />
hacker could offer the administrator only an ambiguous defense, because<br />
at this time most hackers lacked the vocabulary with which to describe the