DOCSLIB.ORG

OPENSOURCES Voices from the Open Source Revolution Michael Tiemann Future of Cygnus Solutions: an Entrepreneur’S Account

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Eric S. Raymond A Brief History of Hackerdom Marshall Kirk McKusick Twenty Years of Berkeley Unix: From AT&T-Owned to Freely Redistributable Scott Bradner The Internet Engineering Task Force Richard Stallman The GNU Operating System and the Free Software Movement OPENSOURCES Voices from the Open Source Revolution Michael Tiemann Future of Cygnus Solutions: An Entrepreneur’s Account Paul Vixie Software Engineering Linus Torvalds The Linux Edge Robert Young Giving It Away: How Red Hat Software Stumbled Across a New Economic Model and Helped Improve an Industry Larry Wall Diligence, Patience, and Humility Bruce Perens The Open Source Definition Tim O'Reilly Hardware, Software, and Infoware Jim Hamerly and Tom Paquin with Susan Walton Freeing the Source: The Story of Mozilla Eric S. Raymond Edited by The Revenge of the Hackers Chris DiBona, Sam Ockman and Mark Stone OPENSOURCES Voices from the Open Source Revolution Edited by Chris DiBona, Sam Ockman and Mark Stone Copyright “Free Software” is Copyright c ; 1998 Richard M. Stallman Verbatim copying and duplication is permitted in any medium provided this notice is preserved. “A Brief History of Hackerdom” and “Revenge of the Hackers” are Copyright c ; 1998 Eric S. Raymond. These essays are free; you can redistribute them and/or modify them under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. These essays are distributed in the hope that they will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. See Appendix B for a copy of the GNU General Public License, or write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330 Boston, MA 02111-1307, USA. Eric Raymond [email protected] 6 Karen Drive Malvern, PA 19355 “Open Source Software” is free; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This essay is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. See Appendix B for a copy of the GNU General Public License, or write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. Bruce Perens [email protected] c/o Pixar Animation Studios 1001 West Cutting #200 Richmond, CA 94804 All essays not mentioned above are freely redistributable without modification provided this notice is preserved. All other material is copyright c 1999 O’Reilly & Associates. All rights reserved. Acknowledgments No book like this happens without the help and counsel of a num- I’d like to thank Sam and Chris for bringing this crazy idea to ber of people, so I thank my Mom, Dad, Trish, Denise, Neil, and me in the first place. I’m sure they had no idea what they were Mickey. I’d also like to thank the folks at the Coffeenet, who getting into, but I’m equally sure it has been worth it. I’d also have been there for me. And of course my thanks to the contribu- like to thank each of the contributors; each is a creative spirit tors who have wasted valuable coding time to work on this book; with more ideas than time to execute them, but each understood I appreciate it! the importance of this project and the need to make time for it. To the people at VA Research Linux Systems, I couldn’t have For every book there are people behind the scenes who work hoped for a better collection of smart, dedicated people; thanks their magic to make the book a success. On this book especially, for putting up with me during the writing of this book. some of these quiet heroes deserve acknowledgment: Troy Mott, This book would not have happened without the continual sup- Katie Gardner, Tara McGoldrick, Jane Ellin, Robert Romano, port and dedication of Mark Stone. He is the true hero behind Rhon Porter, Nancy Wolfe Kotary, Sheryl Avruch, Mike Sierra, this book’s creation. He has said that “A book could be written and Edie Freeman. Of course I’d also like to thank my friends about how this book was written,” which I’m sure he means in and family who have supported me through yet another of Dad’s the nicest way possible. I’m sure one day he will look back and crazy book projects. Finally, my thanks to the good people at laugh at this time — right, Mark? Mark? Lytton Coffee Roasting Company, my “office away from home.” In the initial brainstorming period for the book, a number of Mark Stone people contributed ideas and support that eventually led to Open Sources. These people include Paul Crowley, Paul Russell, Corey Saltiel, Edward Avis, Jeff Licquia, Jeff Knox, Becky Wood, and the guy whose site (http://slashdot.org) acted as the cat- alyst, Rob Malda. Thanks to all; I hope this book is everything you had wished it to be. Finally, I could not have completed this work without the morale of Christine Hillmer, who selflessly unpacked our apart- ment while I toiled away at my keyboard. You are all that I ever could have wished for and I am reminded each day how lucky I am. Chris DiBona I’d like to thank the following people for the many ways that they have supported me: Joe McGuckin, Peter Hendrickson, Jo Schuster, Ruth Ockman, Allison Huynh, and Nina Woodard. I’d also like to thank my favorite hackers: David S. Miller and H. Peter Anvin. Sam Ockman Contents Acknowledgments 4 The Internet Engineering Task Force 28 Scott Bradner 1 Introduction 8 4.1 The History of the IETF . 28 Chris DiBona, Sam Ockman, and Mark Stone 4.2 IETF Structure and Features . 28 1.1 What Is Free Software and How Does It Relate 4.3 IETF Working Groups . 29 to Open Source? . 8 4.4 IETF Documents . 29 1.2 What Is Open Source Software? . 9 4.5 The IETF Process . 29 1.3 The Dark Side of the Force . 9 4.6 Open Standards, Open Documents, and Open 1.4 Use the Source, Luke . 9 Source . 30 1.5 Innovation Through the Scientific Method . 10 1.6 Perils to Open Source . 12 5 The GNU Operating System and the Free Software 1.7 Motivating the Open Source Hacker . 13 Movement 31 1.8 The Venture and Investment Future of Linux . 13 Richard Stallman 5.1 The First Software-Sharing Community . 31 1.9 Science and the New Renaissance . 14 5.2 The Collapse of the Community . 31 2 A Brief History of Hackerdom 16 5.3 A Stark Moral Choice . 32 Eric S. Raymond 5.4 Free as in Freedom . 32 2.1 Prologue: The Real Programmers . 16 5.5 GNU Software and the GNU System . 32 5.6 Commencing the Project . 32 2.2 The Early Hackers . 16 5.7 The First Steps . 33 2.3 The Rise of Unix . 17 5.8 GNU Emacs . 33 2.4 The End of Elder Days . 18 5.9 Is a Program Free for Every User? . 33 2.5 The Proprietary Unix Era . 18 5.10 Copyleft and the GNU GPL . 33 2.6 The Early Free Unixes . 19 5.11 The Free Software Foundation . 34 2.7 The Great Web Explosion . 20 5.12 Free Software Support . 34 5.13 Technical Goals . 34 3 Twenty Years of Berkeley Unix 21 5.14 Donated Computers . 34 Marshall Kirk McKusick 5.15 The GNU Task List . 34 3.1 Early History . 21 5.16 The GNU Library GPL . 35 3.2 Early Distributions . 22 5.17 Scratching an Itch? . 35 3.3 VAX Unix . 22 5.18 Unexpected Developments . 35 3.4 DARPA Support . 22 5.19 The GNU HURD . 35 3.5 4.2BSD . 23 5.20 Alix . 35 3.6 4.3BSD . 24 5.21 Linux and GNU/Linux . 36 3.7 Networking, Release 1 . 25 5.22 Challenges in Our Future . 36 3.8 4.3BSD-Reno . 25 5.23 Secret Hardware . 36 3.9 Networking, Release 2 . 25 5.24 Non-Free Libraries . 36 3.10 The Lawsuit . 26 5.25 Software Patents . 36 3.11 4.4BSD . 27 5.26 Free Documentation . 37 3.12 4.4BSD-Lite, Release 2 . 27 5.27 We Must Talk About Freedom . 37 6 7 5.28 “Open Source” . 37 12 The Open Source Definition 79 5.29 Try! . 37 Bruce Perens 12.1 History . 79 6 Future of Cygnus Solutions 39 12.2 KDE, Qt, and Troll Tech . 80 Michael Tiemann 12.3 Analysis of the Open Source Definition . 81 6.1 Introduction . 39 12.4 Analysis of Licenses and Their Open Source 6.2 Cygnus in the Early Years . 42 Compliance . 83 6.3 GNUPro . 42 12.5 Choosing a License . 85 6.4 Challenges . 44 12.6 The Future . 85 6.5 Getting Funded Beyond Open Source — eCos . 45 13 Hardware, Software, and Infoware 87 6.6 Reflections and Vision of the Future . 46 Tim O’Reilly 7 Software Engineering 47 14 Freeing the Source 91 Paul Vixie Jim Hamerly and Tom Paquin with Susan Walton 7.1 The Software Engineering Process . 47 14.1 Making It Happen . 92 7.2 Testing Details .
Recommended publications
  • FAI.Me a Build Service for Installation Images and Cloud Images

    FAI.Me a Build Service for Installation Images and Cloud Images

    FAI.me A Build Service for Installation Images and Cloud Images Thomas Lange, Debian Developer and sysadmin at the University of Cologne [email protected] MiniDebConf Hamburg 2018 1/19 finger Mrfai@localhost ◮ whoami ◮ Sysadmin for more than two and a half decades ◮ Debian developer since 2000 ◮ Diploma in computer science, University of Bonn, Germany ◮ SunOS 4.1.1 on SPARC hardware, then Solaris Jumpstart ◮ Started FAI in 1999 for my first cluster (16× Dual PII 400 MHz) ◮ Several talks and tutorials: Linux Kongress, Linuxtag, DebConf, SANE, LCA, FOSDEM, CeBit, OSDC, UKUUG, FrOSCon, Chemnitzer Linuxtag ◮ FAI trainings 2/19 Motivation ◮ Debian installer is not that easy for beginners ◮ Also FAI is not for beginners ◮ How to make FAI usable for beginners? 3/19 The idea ◮ An installer should cover the most usual installations ◮ Ignore the special cases ◮ Do only ask the really important questions ◮ Ask everything at the beginning ◮ Create a customized installation media ◮ Boot this installation media and get yourself a coffee ◮ Ready! 4/19 FAI ◮ FAI = Fully Automatic Installation ◮ FAI is a tool for experienced sysadmins ◮ You have to adjust the config files to your local needs ◮ How to make FAI usable for beginners? FAI.me 5/19 FAI.me 6/19 FAI.me ◮ Easy creation of the installation media (CD/USB stick) ◮ Customizations are easy to do (clicks on a web page) ◮ Lanuage, user name and pw, root pw ◮ Select one of the common desktops ◮ Additional packages ◮ Distributions: stable, stable+backports, testing 7/19 Some more advanced features ◮ A couple of different partitioning variants ◮ SSH key for root login ◮ Use your github account (ssh pub key) for the root login ◮ Add one public available repository 8/19 FAI.me for the cloud ◮ Cloud Images ◮ Get your customized cloud image by just a few clicks ◮ Disk size ◮ Disk image format (raw.xz, raw.zst, qcow2, vmdk,...) ◮ Hostname 9/19 FAI.me more ideas ◮ Make web page dynamic: easy mode Thanks Juri! ◮ Images for non-amd64 archs ◮ Other distributions (e.g.
  • Debian Developer's Reference Version 12.0, Released on 2021-09-01

    Debian Developer's Reference Version 12.0, Released on 2021-09-01

    Debian Developer’s Reference Release 12.0 Developer’s Reference Team 2021-09-01 CONTENTS 1 Scope of This Document 3 2 Applying to Become a Member5 2.1 Getting started..............................................5 2.2 Debian mentors and sponsors......................................6 2.3 Registering as a Debian member.....................................6 3 Debian Developer's Duties 9 3.1 Package Maintainer's Duties.......................................9 3.1.1 Work towards the next stable release............................9 3.1.2 Maintain packages in stable .................................9 3.1.3 Manage release-critical bugs.................................. 10 3.1.4 Coordination with upstream developers............................ 10 3.2 Administrative Duties.......................................... 10 3.2.1 Maintaining your Debian information............................. 11 3.2.2 Maintaining your public key.................................. 11 3.2.3 Voting.............................................. 11 3.2.4 Going on vacation gracefully.................................. 12 3.2.5 Retiring............................................. 12 3.2.6 Returning after retirement................................... 13 4 Resources for Debian Members 15 4.1 Mailing lists............................................... 15 4.1.1 Basic rules for use....................................... 15 4.1.2 Core development mailing lists................................. 15 4.1.3 Special lists........................................... 16 4.1.4 Requesting new
  • The Kernel Report

    The Kernel Report

    The kernel report (ELC 2012 edition) Jonathan Corbet LWN.net [email protected] The Plan Look at a year's worth of kernel work ...with an eye toward the future Starting off 2011 2.6.37 released - January 4, 2011 11,446 changes, 1,276 developers VFS scalability work (inode_lock removal) Block I/O bandwidth controller PPTP support Basic pNFS support Wakeup sources What have we done since then? Since 2.6.37: Five kernel releases have been made 59,000 changes have been merged 3069 developers have contributed to the kernel 416 companies have supported kernel development February As you can see in these posts, Ralink is sending patches for the upstream rt2x00 driver for their new chipsets, and not just dumping a huge, stand-alone tarball driver on the community, as they have done in the past. This shows a huge willingness to learn how to deal with the kernel community, and they should be strongly encouraged and praised for this major change in attitude. – Greg Kroah-Hartman, February 9 Employer contributions 2.6.38-3.2 Volunteers 13.9% Wolfson Micro 1.7% Red Hat 10.9% Samsung 1.6% Intel 7.3% Google 1.6% unknown 6.9% Oracle 1.5% Novell 4.0% Microsoft 1.4% IBM 3.6% AMD 1.3% TI 3.4% Freescale 1.3% Broadcom 3.1% Fujitsu 1.1% consultants 2.2% Atheros 1.1% Nokia 1.8% Wind River 1.0% Also in February Red Hat stops releasing individual kernel patches March 2.6.38 released – March 14, 2011 (9,577 changes from 1198 developers) Per-session group scheduling dcache scalability patch set Transmit packet steering Transparent huge pages Hierarchical block I/O bandwidth controller Somebody needs to get a grip in the ARM community.
  • Study of File System Evolution

    Study of File System Evolution

    Study of File System Evolution Swaminathan Sundararaman, Sriram Subramanian Department of Computer Science University of Wisconsin {swami, srirams} @cs.wisc.edu Abstract File systems have traditionally been a major area of file systems are typically developed and maintained by research and development. This is evident from the several programmer across the globe. At any point in existence of over 50 file systems of varying popularity time, for a file system, there are three to six active in the current version of the Linux kernel. They developers, ten to fifteen patch contributors but a single represent a complex subsystem of the kernel, with each maintainer. These people communicate through file system employing different strategies for tackling individual file system mailing lists [14, 16, 18] various issues. Although there are many file systems in submitting proposals for new features, enhancements, Linux, there has been no prior work (to the best of our reporting bugs, submitting and reviewing patches for knowledge) on understanding how file systems evolve. known bugs. The problems with the open source We believe that such information would be useful to the development approach is that all communication is file system community allowing developers to learn buried in the mailing list archives and aren’t easily from previous experiences. accessible to others. As a result when new file systems are developed they do not leverage past experience and This paper looks at six file systems (Ext2, Ext3, Ext4, could end up re-inventing the wheel. To make things JFS, ReiserFS, and XFS) from a historical perspective worse, people could typically end up doing the same (between kernel versions 1.0 to 2.6) to get an insight on mistakes as done in other file systems.
  • SFLC V Conservancy

    SFLC V Conservancy

    Trademark Trial and Appeal Board Electronic Filing System. http://estta.uspto.gov ESTTA Tracking number: ESTTA863914 Filing date: 12/11/2017 IN THE UNITED STATES PATENT AND TRADEMARK OFFICE BEFORE THE TRADEMARK TRIAL AND APPEAL BOARD Proceeding 92066968 Party Defendant Software Freedom Conservancy Correspondence PAMELA S CHESTECK Address CHESTEK LEGAL P O BOX 2492 RALEIGH, NC 27602 UNITED STATES Email: [email protected] Submission Motion for Summary Judgment Yes, the Filer previously made its initial disclosures pursuant to Trademark Rule 2.120(a); OR the motion for summary judgment is based on claim or issue pre- clusion, or lack of jurisdiction. The deadline for pretrial disclosures for the first testimony period as originally set or reset: 07/20/2018 Filer's Name Pamela S Chestek Filer's email [email protected] Signature /Pamela S Chestek/ Date 12/11/2017 Attachments Motion for SJ on affirmative defenses-signed.pdf(756280 bytes ) Kuhn-Declara- tion_summary-judgment_as-submitted_reduced-size-signed.pdf(2181238 bytes ) Sandler-declara- tion_summary-judgment_as-submitted-reduced-size-signed.pdf(1777273 bytes ) Chestek declaration_summary-judgment-signed-with-exhibits.pdf(2003142 bytes ) IN THE UNITED STATES PATENT AND TRADEMARK OFFICE BEFORE THE TRADEMARK TRIAL AND APPEAL BOARD In the Mater of Registraion No. 4212971 Mark: SOFTWARE FREEDOM CONSERVANCY Registraion date: September 25, 2012 Sotware Freedom Law Center Peiioner, v. Cancellaion No. 92066968 Sotware Freedom Conservancy Registrant. RESPONDENT’S MOTION FOR SUMMARY JUDGMENT ON ITS AFFIRMATIVE DEFENSES Introducion The Peiioner, Sotware Freedom Law Center (“SFLC”), is a provider of legal services. It had the idea to create an independent enity that would ofer inancial and administraive services for free and open source sotware projects.
  • Studying the Real World Today's Topics

    Studying the Real World Today's Topics

    Studying the real world Today's topics Free and open source software (FOSS) What is it, who uses it, history Making the most of other people's software Learning from, using, and contributing Learning about your own system Using tools to understand software without source Free and open source software Access to source code Free = freedom to use, modify, copy Some potential benefits Can build for different platforms and needs Development driven by community Different perspectives and ideas More people looking at the code for bugs/security issues Structure Volunteers, sponsored by companies Generally anyone can propose ideas and submit code Different structures in charge of what features/code gets in Free and open source software Tons of FOSS out there Nearly everything on myth Desktop applications (Firefox, Chromium, LibreOffice) Programming tools (compilers, libraries, IDEs) Servers (Apache web server, MySQL) Many companies contribute to FOSS Android core Apple Darwin Microsoft .NET A brief history of FOSS 1960s: Software distributed with hardware Source included, users could fix bugs 1970s: Start of software licensing 1974: Software is copyrightable 1975: First license for UNIX sold 1980s: Popularity of closed-source software Software valued independent of hardware Richard Stallman Started the free software movement (1983) The GNU project GNU = GNU's Not Unix An operating system with unix-like interface GNU General Public License Free software: users have access to source, can modify and redistribute Must share modifications under same
  • Membrane: Operating System Support for Restartable File Systems Swaminathan Sundararaman, Sriram Subramanian, Abhishek Rajimwale, Andrea C

    Membrane: Operating System Support for Restartable File Systems Swaminathan Sundararaman, Sriram Subramanian, Abhishek Rajimwale, Andrea C

    Membrane: Operating System Support for Restartable File Systems Swaminathan Sundararaman, Sriram Subramanian, Abhishek Rajimwale, Andrea C. Arpaci-Dusseau, Remzi H. Arpaci-Dusseau, Michael M. Swift Computer Sciences Department, University of Wisconsin, Madison Abstract and most complex code bases in the kernel. Further, We introduce Membrane, a set of changes to the oper- file systems are still under active development, and new ating system to support restartable file systems. Mem- ones are introduced quite frequently. For example, Linux brane allows an operating system to tolerate a broad has many established file systems, including ext2 [34], class of file system failures and does so while remain- ext3 [35], reiserfs [27], and still there is great interest in ing transparent to running applications; upon failure, the next-generation file systems such as Linux ext4 and btrfs. file system restarts, its state is restored, and pending ap- Thus, file systems are large, complex, and under develop- plication requests are serviced as if no failure had oc- ment, the perfect storm for numerous bugs to arise. curred. Membrane provides transparent recovery through Because of the likely presence of flaws in their imple- a lightweight logging and checkpoint infrastructure, and mentation, it is critical to consider how to recover from includes novel techniques to improve performance and file system crashes as well. Unfortunately, we cannot di- correctness of its fault-anticipation and recovery machin- rectly apply previous work from the device-driver litera- ery. We tested Membrane with ext2, ext3, and VFAT. ture to improving file-system fault recovery. File systems, Through experimentation, we show that Membrane in- unlike device drivers, are extremely stateful, as they man- duces little performance overhead and can tolerate a wide age vast amounts of both in-memory and persistent data; range of file system crashes.
  • Logiciel Libre, Une Introduction Part I Perspective Historique Des Étapes

    Logiciel Libre, Une Introduction Part I Perspective Historique Des Étapes

    Logiciel libre, une introduction Logiciel libre, une introduction Logiciel libre, une introduction Part I Roberto Di Cosmo Perspective historique Université Paris Diderot UFR Informatique Laboratoire Preuves, Programmes et Systèmes [email protected] 7 Février 2012 Logiciel libre, une introduction Logiciel libre, une introduction Une brève histoire du logiciel Une brève histoire du logiciel Des étapes importantes Une brève histoire du logiciel I Années 50-60: Logiciel libre ante litteram Logiciel Libre aux origines La propriétarisation du logiciel I Années 70: La proprietarisation du logiciel I Années 70-80: Les briques de base I Donald Knuth et TEX Le logiciel libre ante litteram I X Windows System Le système TEX I AT&T et Unix Le système X I Années 80: le matériel devient suffisamment puissant pour des AT&T et Unix vrai OS Linux I Années 80: Richard Stallman, GNU et la Free Software Foundation Le logiciel libre formalisé I Années 1990: Linux, GNU/Linux etc.: la prise de conscience I Années 2000 : l’expansion Les années 1990 Logiciel libre, une introduction Logiciel libre, une introduction Une brève histoire du logiciel Une brève histoire du logiciel Logiciel Libre aux origines Logiciel Libre aux origines Au début le logiciel fût distribué librement. c’était une nécéssité Jusqu’à la fin des années 1960, le logiciel, avec les sources, était N’oublions pas les raisons techniques de cette réalité: distribué gratuitement, comme un complément pour les ordinateurs I modèle de service clé en main comprenant hw & sw & vendus (très chers) à l’époque. service I logiciel très dépendant de la machine utilisateur (n.
  • Bibliography of Erik Wilde

    Bibliography of Erik Wilde

    dretbiblio dretbiblio Erik Wilde's Bibliography References [1] AFIPS Fall Joint Computer Conference, San Francisco, California, December 1968. [2] Seventeenth IEEE Conference on Computer Communication Networks, Washington, D.C., 1978. [3] ACM SIGACT-SIGMOD Symposium on Principles of Database Systems, Los Angeles, Cal- ifornia, March 1982. ACM Press. [4] First Conference on Computer-Supported Cooperative Work, 1986. [5] 1987 ACM Conference on Hypertext, Chapel Hill, North Carolina, November 1987. ACM Press. [6] 18th IEEE International Symposium on Fault-Tolerant Computing, Tokyo, Japan, 1988. IEEE Computer Society Press. [7] Conference on Computer-Supported Cooperative Work, Portland, Oregon, 1988. ACM Press. [8] Conference on Office Information Systems, Palo Alto, California, March 1988. [9] 1989 ACM Conference on Hypertext, Pittsburgh, Pennsylvania, November 1989. ACM Press. [10] UNIX | The Legend Evolves. Summer 1990 UKUUG Conference, Buntingford, UK, 1990. UKUUG. [11] Fourth ACM Symposium on User Interface Software and Technology, Hilton Head, South Carolina, November 1991. [12] GLOBECOM'91 Conference, Phoenix, Arizona, 1991. IEEE Computer Society Press. [13] IEEE INFOCOM '91 Conference on Computer Communications, Bal Harbour, Florida, 1991. IEEE Computer Society Press. [14] IEEE International Conference on Communications, Denver, Colorado, June 1991. [15] International Workshop on CSCW, Berlin, Germany, April 1991. [16] Third ACM Conference on Hypertext, San Antonio, Texas, December 1991. ACM Press. [17] 11th Symposium on Reliable Distributed Systems, Houston, Texas, 1992. IEEE Computer Society Press. [18] 3rd Joint European Networking Conference, Innsbruck, Austria, May 1992. [19] Fourth ACM Conference on Hypertext, Milano, Italy, November 1992. ACM Press. [20] GLOBECOM'92 Conference, Orlando, Florida, December 1992. IEEE Computer Society Press. http://github.com/dret/biblio (August 29, 2018) 1 dretbiblio [21] IEEE INFOCOM '92 Conference on Computer Communications, Florence, Italy, 1992.
  • Producing Open Source Software How to Run a Successful Free Software Project

    Producing Open Source Software How to Run a Successful Free Software Project

    Producing Open Source Software How to Run a Successful Free Software Project Karl Fogel Producing Open Source Software: How to Run a Successful Free Software Project by Karl Fogel Copyright © 2005-2018 Karl Fogel, under the CreativeCommons Attribution-ShareAlike (4.0) license. Version: 2.3098 Home site: http://producingoss.com/ Dedication This book is dedicated to two dear friends without whom it would not have been possible: Karen Under- hill and Jim Blandy. i Table of Contents Preface ............................................................................................................................. vi Why Write This Book? ............................................................................................... vi Who Should Read This Book? .................................................................................... vii Sources ................................................................................................................... vii Acknowledgements ................................................................................................... viii For the first edition (2005) ................................................................................ viii For the second edition (2017) ............................................................................... x Disclaimer .............................................................................................................. xiii 1. Introduction ...................................................................................................................
  • Twenty Years of Berkeley Unix : from AT&T-Owned to Freely

    Twenty Years of Berkeley Unix : from AT&T-Owned to Freely

    Twenty Years of Berkeley Unix : From AT&T-Owned to Freely Redistributable Marshall Kirk McKusick Early History Ken Thompson and Dennis Ritchie presented the first Unix paper at the Symposium on Operating Systems Principles at Purdue University in November 1973. Professor Bob Fabry, of the University of California at Berkeley, was in attendance and immediately became interested in obtaining a copy of the system to experiment with at Berkeley. At the time, Berkeley had only large mainframe computer systems doing batch processing, so the first order of business was to get a PDP-11/45 suitable for running with the then-current Version 4 of Unix. The Computer Science Department at Berkeley, together with the Mathematics Department and the Statistics Department, were able to jointly purchase a PDP-11/45. In January 1974, a Version 4 tape was delivered and Unix was installed by graduate student Keith Standiford. Although Ken Thompson at Purdue was not involved in the installation at Berkeley as he had been for most systems up to that time, his expertise was soon needed to determine the cause of several strange system crashes. Because Berkeley had only a 300-baud acoustic-coupled modem without auto answer capability, Thompson would call Standiford in the machine room and have him insert the phone into the modem; in this way Thompson was able to remotely debug crash dumps from New Jersey. Many of the crashes were caused by the disk controller's inability to reliably do overlapped seeks, contrary to the documentation. Berkeley's 11/45 was among the first systems that Thompson had encountered that had two disks on the same controller! Thompson's remote debugging was the first example of the cooperation that sprang up between Berkeley and Bell Labs.
  • Linux at 25 PETERHISTORY H

    Linux at 25 PETERHISTORY H

    Linux at 25 PETERHISTORY H. SALUS Peter H. Salus is the author of A n June 1991, at the USENIX conference in Nashville, BSD NET-2 was Quarter Century of UNIX (1994), announced. Two months later, on August 25, Linus Torvalds announced Casting the Net (1995), and The his new operating system on comp.os.minix. Today, Android, Google’s Daemon, the Gnu and the Penguin I (2008). [email protected] version of Linux, is used on over two billion smartphones and other appli- ances. In this article, I provide some history about the early years of Linux. Linus was born into the Swedish minority of Finland (about 5% of the five million Finns). He was a “math guy” throughout his schooling. Early on, he “inherited” a Commodore VIC- 20 (released in June 1980) from his grandfather; in 1987 he spent his savings on a Sinclair QL (released in January 1984, the “Quantum Leap,” with a Motorola 68008 running at 7.5 MHz and 128 kB of RAM, was intended for small businesses and the serious hobbyist). It ran Q-DOS, and it was what got Linus involved: One of the things I hated about the QL was that it had a read-only operating system. You couldn’t change things ... I bought a new assembler ... and an editor.... Both ... worked fine, but they were on the microdrives and couldn’t be put on the EEPROM. So I wrote my own editor and assembler and used them for all my programming. Both were written in assembly language, which is incredibly stupid by today’s standards.