''Tw O Years in the Trenches''

Total Page:16

File Type:pdf, Size:1020Kb

''Tw O Years in the Trenches'' ‘‘Tw o years in the trenches’’ Evolution of a free software project GregLehey President, AUUG Inc. [email protected] Member,FreeBSD Core team [email protected] ABSTRACT Free software projects have been around for overten years now, and they’ve become an important part of the UNIX community.With the example of the FreeBSD project, this paper illustrates some of the changes that have occurred in that time and attempts to guess what the future may bring. The three ages of UNIX The evolution of free UNIX UNIX® is nowathird of a century old. In this Free software has been around for ever. Until the time, the face of computing has changed dramati- end of the 60s, coincidentally the time when cally.It’sinteresting to consider the evolution of UNIX evolved, software was almost always free. UNIX in three phases of roughly 11 years each: And whynot? Most system software came with the machines and would only run on them, so • From 1969 until about 1980, UNIX was there was little incentive tocharge separately for mainly a research project, little known outside the software. Applications software was tuned to AT&T except at some universities. specific applications, so piracywas hardly worth • From 1980 until about 1991, UNIX developed worrying about. into a commercial operating system with re- By the end of the 1960s, that had changed. IBM leases likeUNIX System V (remember that?), wasfaced with competitors who built hardware XENIX, SunOS, Ultrix and friends. which was strikingly compatible with the Sys- • In the early 90s, efforts at the University of tem/360, and IBM’ssoftware ran on it. It started California in Berkeleytoproduce free UNIX to makecommercial sense for IBM to unbundle came to fruition. At pretty much exactly the its software. Over the course of the following ten same time, the Linux project started. UNIX years, more and more compatible hardware be- wasonthe way to becoming free. came available, and by 1980 just about all soft- ware cost money. Vendors had a perception that This paper looks at the last third of this history in access to the source code would give their com- more detail. petitors an advantage, so theyrestricted availabili- ty of their software to object form only.The re- sultant inflexibility was one of the reasons which led to the formation of the Free Software Founda- tion in the mid-80s. To wards the end of the 70s, the price of ‘‘real’’ computers dropped to the point where individuals • The release of the Intel 80386 processor and could own them. People started sharing programs systems based on it, gav e the average hacker for their CP/M based machines, and later for their an affordable machine with virtual memory, Microsoft-based replacements. Most software for capable of running modern UNIX without small machines continued to cost money, howev- significant compromises. er,and the machines themselves were too small to • Improvedaccess to the Internet, especially for run UNIX effectively. students, made cooperation on software pro- This changed round about 1990 with the availabil- jects more practicable. ity of machines based on the Intel 80386 proces- In those days, for most people the attraction was sor.Atthe same time, individual access to the In- the challenge of running UNIX on one’sown ternet became easier,especially for students. computer,not anycommercial intent. Indeed, These were the background for a number of free Bill Jolitz staunchly refused to commercialize his software projects which were initially completely 386BSD operating system, and in August 1991, independent of the Free Software Foundation and Linus Torvalds wrote in the original announce- its values. ment of Linux ‘‘just a hobby,won’tbebig and The early 90s professional likegnu’’. Idon’tbelieve that religious belief in ‘‘free soft- Computer hackers1 have been around as long as ware’’was a big thing at the time. The GNU pro- computers. Theyhav e probably dreamed of hav- ject had been around for a while, and both 386 ing their own computer that long, too, but it really BSD and Linux took advantage of the software, only became evenremotely possible in the butinitially there was little synergy between the mid-1970s. People started working on UNIX-like GNU project and the free OS projects. systems early: During this period, relatively fewpeople con- • In the late 1970s, a companycalled Electro- tributed to the projects. Forexample, the release labs started working on a UNIX-likesystem notes of FreeBSD 2.0, released in January 1995, called OS-2, intended to run on the Z-80 pro- mention a total of 55 contributors, including a 15 cessor.Itnev erpassed the beta stage running member core team, who really were the project. under CP/M. Most of the other contributors had only loose • In the early 1980s, Mark Williams Company links with the FreeBSD project. ported their Coherent system, a clone of the UNIX Seventh edition, to the IBM PC. With- The compromise OS out memory protection, and with the memory Along with the free operating system projects limitations of the original success, it was not a there was also a ‘‘reasonable’’operating system great success. project, BSD/386 from BerkeleySoftware Design • Andy Tanenbaum’sMinix operating system Inc., or BSDI (later BSDi). BSD/386 was derived ran on a number of processors, including the from the same code base as 386BSD, and was in Intel 8086 family. fact quite closely related. The story of that rela- tionship is interesting enough to be the topic for None of these projects became very large. The another paper.The difference was that BSD/386 hardware wasn’tuptoit, and none of them made cost money. Including complete source code, it the source code freely available, though the re- cost $1,000 US. That may seem to be a lot of strictions on Minix were relatively minor.Two money, but in those days source licenses for Sys- things changed that situation in the late 1980s and tem V cost at least $50,000, and a BSD/386 early 1990s: source license was was cheaper than a binary li- cense for the System V implementations for the Intel platform. In addition, it was complete—no dozens of additional packages to add, each with their own activation key.Evenmore surprisingly, 1. Ahacker is, of course, somebody who can’ttell the difference between work and play with computers. See the BSD/386 was more reliable than System V. NewHacker’sDictionary (http://www.tuxedo.org/˜esr/jargon/html/entry/hacker.html ) for more details. The mid-90s In the early days, nobody had very great expecta- Social changes tions for the free operating systems. Theydidn’t expect them to be as reliable as UNIX® System Clearly the social structure of the FreeBSD pro- V. Theydidn’tevenexpect them to be as reliable ject has changed greatly in its nature in the last as Microsoft’sofferings, though theydid expect ten years. By mid-2000, the strain was beginning them to be easier to use. to show: In a fewyears, something happened that nobody • The core team was no longer the group of the had expected. Well, very fewpeople: the operat- most active comitters. Their function had ef- ing systems did become as reliable as Microsoft’s fectively become more administrative,but offerings, quite quickly in fact. One of the first theyhadn’trecognized the fact yet. results of this recognition came from the massive • The architectural direction of the project had increase in Internet usage, which created a re- become a little vague. The position of chief quirement for low-cost web servers. This wasthe architect, previously held by David Green- reason for the foundation of BSDI, who branded man, had been vacant for some time. In the their operating system ‘‘Internet Server’’, later early stages of the project, most of the work ‘‘Internet Super Server’’. Initially theywere very in the project had been to makeFreeBSD a successful. As time went on, though, enterprising stable UNIX-likeoperating system, but that startups realized that theycould save the cost of goal had nowbeen achieved. There wasmore the software by using free operating systems in- work to do, but the only clearly defined goal stead of BSD/386. Thus in 1995, when Yahoo! wastoimprove the SMP performance—the started up, it was based on FreeBSD. SMPng project, which at the time had just Linux was slower to reach reliability than the started, and which is still continuing. BSD systems: it had to be written from scratch, • Arelated problem was the attractiveness to whereas the free BSD systems were based on a end users. Likeother free operating systems, code base at least ten years old, including the FreeBSD has always been a developer-driven most mature of TCP/IP stacks. project, but the main source of project fund- By the late 1990s, though, Linux had effectively ing came from selling CD-ROMs. The sales caught up with the BSDs, and depending on of the CD-ROMs were obviously dependent which bigot you ask, either overtook the BSDs or on the perception of the purchaser,but no- neverquite made it. body in the project was overly concerned with this issue. In the mid-1990s, another thing happened: the general public became aware of the concept of • Some developers exploited the ineffectiveness free operating systems. Theywere still consid- of the core team by doing whateverthey ered very much the realm of geeks, but theywere wanted. This notably included making becoming known. changes to the system to match their viewof what was needed, possibly breaking parts of During this time, more and more people became the system (those parts which theydidn’t involved with the projects.
Recommended publications
  • Ebook - Informations About Operating Systems Version: August 15, 2006 | Download
    eBook - Informations about Operating Systems Version: August 15, 2006 | Download: www.operating-system.org AIX Internet: AIX AmigaOS Internet: AmigaOS AtheOS Internet: AtheOS BeIA Internet: BeIA BeOS Internet: BeOS BSDi Internet: BSDi CP/M Internet: CP/M Darwin Internet: Darwin EPOC Internet: EPOC FreeBSD Internet: FreeBSD HP-UX Internet: HP-UX Hurd Internet: Hurd Inferno Internet: Inferno IRIX Internet: IRIX JavaOS Internet: JavaOS LFS Internet: LFS Linspire Internet: Linspire Linux Internet: Linux MacOS Internet: MacOS Minix Internet: Minix MorphOS Internet: MorphOS MS-DOS Internet: MS-DOS MVS Internet: MVS NetBSD Internet: NetBSD NetWare Internet: NetWare Newdeal Internet: Newdeal NEXTSTEP Internet: NEXTSTEP OpenBSD Internet: OpenBSD OS/2 Internet: OS/2 Further operating systems Internet: Further operating systems PalmOS Internet: PalmOS Plan9 Internet: Plan9 QNX Internet: QNX RiscOS Internet: RiscOS Solaris Internet: Solaris SuSE Linux Internet: SuSE Linux Unicos Internet: Unicos Unix Internet: Unix Unixware Internet: Unixware Windows 2000 Internet: Windows 2000 Windows 3.11 Internet: Windows 3.11 Windows 95 Internet: Windows 95 Windows 98 Internet: Windows 98 Windows CE Internet: Windows CE Windows Family Internet: Windows Family Windows ME Internet: Windows ME Seite 1 von 138 eBook - Informations about Operating Systems Version: August 15, 2006 | Download: www.operating-system.org Windows NT 3.1 Internet: Windows NT 3.1 Windows NT 4.0 Internet: Windows NT 4.0 Windows Server 2003 Internet: Windows Server 2003 Windows Vista Internet: Windows Vista Windows XP Internet: Windows XP Apple - Company Internet: Apple - Company AT&T - Company Internet: AT&T - Company Be Inc. - Company Internet: Be Inc. - Company BSD Family Internet: BSD Family Cray Inc.
    [Show full text]
  • Advanced Integration
    ZFS: Advanced Integration Allan Jude -- [email protected] @allanjude Introduction: Allan Jude • 16 Years as FreeBSD Server Admin • FreeBSD src/doc committer (ZFS, installer, boot loader, GELI, bhyve, libucl, libxo) • FreeBSD Core Team (July 2016 - 2018) • Co-Author of “FreeBSD Mastery: ZFS” and “FreeBSD Mastery: Advanced ZFS” with Michael W. Lucas • Architect of the ScaleEngine CDN (HTTP and Video) • Host of weekly BSDNow.tv Podcast • Personally Responsible for 1000 TB of ZFS Storage ZFS: What Is It? • ZFS is a filesystem with a built in volume manager (combine multiple disks into a pool) • Space from the pool is thin-provisioned to multiple filesystems or block volumes (zvols) • All data and metadata is checksummed • Optional transparent compression • Copy-on-Write with snapshots and clones • Each filesystem is tunable with properties Snapshots and Clones • Copy-on-Write means snapshots are instant • Blocks referenced by a snapshot kept when they are removed from the live filesystem • Snapshots allows you to access the file- system as it was when snapshot was taken • No performance impact on reads/writes • Take no additional space until blocks change • Clones allow you to “fork” a filesystem Boot Environments • If the root filesystem is on ZFS, you can snapshot before an upgrade, then clone it • You now have 2 filesystems, one before the upgrade, and one after. Only takes the space of blocks that changed • FreeBSD boot loader allows you to select which one to use from a menu • Upgrade without fear, can always rollback Boot Environment Tooling • Existing tool: sysadmin/beadm • GSoC 2017: be(8) and libbe(3) • New tool supports better management of filesystem properties for boot integration • New tool will support “deep” boot environments.
    [Show full text]
  • Absolute BSD—The Ultimate Guide to Freebsd Table of Contents Absolute BSD—The Ultimate Guide to Freebsd
    Absolute BSD—The Ultimate Guide to FreeBSD Table of Contents Absolute BSD—The Ultimate Guide to FreeBSD............................................................................1 Dedication..........................................................................................................................................3 Foreword............................................................................................................................................4 Introduction........................................................................................................................................5 What Is FreeBSD?...................................................................................................................5 How Did FreeBSD Get Here?..................................................................................................5 The BSD License: BSD Goes Public.......................................................................................6 The Birth of Modern FreeBSD.................................................................................................6 FreeBSD Development............................................................................................................7 Committers.........................................................................................................................7 Contributors........................................................................................................................8 Users..................................................................................................................................8
    [Show full text]
  • The Release Engineering of Freebsd 4.4
    The Release Engineering of FreeBSD 4.4 Murray Stokely [email protected] Wind River Systems Abstract different pace, and with the general assumption that they This paper describes the approach used by the FreeBSD re- have first gone into FreeBSD-CURRENT and have been lease engineering team to make production-quality releases thoroughly tested by our user community. of the FreeBSD operating system. It details the methodol- In the interim period between releases, nightly snap- ogy used for the release of FreeBSD 4.4 and describes the shots are built automatically by the FreeBSD Project build tools available for those interested in producing customized machines and made available for download from ftp: FreeBSD releases for corporate rollouts or commercial pro- //stable.FreeBSD.org. The widespread availabil- ductization. ity of binary release snapshots, and the tendency of our user community to keep up with -STABLE development with CVSup and “make world”[8] helps to keep FreeBSD- 1 Introduction STABLE in a very reliable condition even before the qual- ity assurance activities ramp up pending a major release. The development of FreeBSD is a very open process. Bug reports and feature requests are continuously sub- FreeBSD is comprised of contributions from thousands of mitted by users throughout the release cycle. Problem people around the world. The FreeBSD Project provides reports are entered into our GNATS[9] database through anonymous CVS[1] access to the general public so that email, the send-pr(1) application, or via a web-based form. others can have access to log messages, diffs between de- In addition to the multitude of different technical mailing velopment branches, and other productivity enhancements lists about FreeBSD, the FreeBSD quality-assurance mail- that formal source code management provides.
    [Show full text]
  • The Complete Freebsd
    The Complete FreeBSD® If you find errors in this book, please report them to Greg Lehey <grog@Free- BSD.org> for inclusion in the errata list. The Complete FreeBSD® Fourth Edition Tenth anniversary version, 24 February 2006 Greg Lehey The Complete FreeBSD® by Greg Lehey <[email protected]> Copyright © 1996, 1997, 1999, 2002, 2003, 2006 by Greg Lehey. This book is licensed under the Creative Commons “Attribution-NonCommercial-ShareAlike 2.5” license. The full text is located at http://creativecommons.org/licenses/by-nc-sa/2.5/legalcode. You are free: • to copy, distribute, display, and perform the work • to make derivative works under the following conditions: • Attribution. You must attribute the work in the manner specified by the author or licensor. • Noncommercial. You may not use this work for commercial purposes. This clause is modified from the original by the provision: You may use this book for commercial purposes if you pay me the sum of USD 20 per copy printed (whether sold or not). You must also agree to allow inspection of printing records and other material necessary to confirm the royalty sums. The purpose of this clause is to make it attractive to negotiate sensible royalties before printing. • Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. • For any reuse or distribution, you must make clear to others the license terms of this work. • Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above.
    [Show full text]
  • Freebsd Handbook
    FreeBSD Handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/han... FreeBSD Handbook The FreeBSD Documentation Project Copyright © 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013 The FreeBSD Documentation Project Welcome to FreeBSD! This handbook covers the installation and day to day use of FreeBSD 8.3-RELEASE and FreeBSD 9.1-RELEASE. This manual is a work in progress and is the work of many individuals. As such, some sections may become dated and require updating. If you are interested in helping out with this project, send email to the FreeBSD documentation project mailing list. The latest version of this document is always available from the FreeBSD web site (previous versions of this handbook can be obtained from http://docs.FreeBSD.org/doc/). It may also be downloaded in a variety of formats and compression options from the FreeBSD FTP server or one of the numerous mirror sites. If you would prefer to have a hard copy of the handbook, you can purchase one at the FreeBSD Mall. You may also want to search the handbook. REDISTRIBUTION AND USE IN SOURCE (XML DOCBOOK) AND 'COMPILED' FORMS (XML, HTML, PDF, POSTSCRIPT, RTF AND SO FORTH) WITH OR WITHOUT MODIFICATION, ARE PERMITTED PROVIDED THAT THE FOLLOWING CONDITIONS ARE MET: 1. REDISTRIBUTIONS OF SOURCE CODE (XML DOCBOOK) MUST RETAIN THE ABOVE COPYRIGHT NOTICE, THIS LIST OF CONDITIONS AND THE FOLLOWING DISCLAIMER AS THE FIRST LINES OF THIS FILE UNMODIFIED. 2. REDISTRIBUTIONS IN COMPILED FORM (TRANSFORMED TO OTHER DTDS, CONVERTED TO PDF, POSTSCRIPT, RTF AND OTHER FORMATS) MUST REPRODUCE THE ABOVE COPYRIGHT NOTICE, THIS LIST OF CONDITIONS AND THE FOLLOWING DISCLAIMER IN THE DOCUMENTATION AND/OR OTHER MATERIALS PROVIDED WITH THE DISTRIBUTION.
    [Show full text]
  • UCL for Freebsd
    UCL for FreeBSD A universal config language for (almost) everything in FreeBSD Allan Jude -- ScaleEngine Inc. [email protected] twitter: @allanjude Introduction Allan Jude ● 13 Years as FreeBSD Server Admin ● FreeBSD docs committer (focus: ZFS, bhyve, ucl, xo) ● Co-Author of “FreeBSD Mastery: ZFS” ● Architect of the ScaleEngine CDN (HTTP and Video) ● Host of BSDNow.tv & TechSNAP.tv Podcasts ● Extensive work with Puppet to manage our 100+ servers in 35 data centers in 12 countries ● Lots of work with ZFS to manage large collections of videos, extremely large website caches, and the pkg mirror for PCBSD Impetus At EuroBSDCon 2014 in Sofia, Jordan Hubbard ([email protected]) gave the opening keynote Among the recommendations for how FreeBSD could be improved and made easier to manage was to move away from the ‘one config file format per utility’ Jordan, being from Apple, suggested the binary XML plists used by launchd. I really didn’t want the “one true format” to be XML. Why is this a “Good Idea”™? ● Includes allow for more readable, structured, and upgradable config files ● Overlays separate the defaults from your site wide settings, and from your local settings (like defaults/rc.conf rc.conf rc.conf.local) ● Includes allow packages to install default settings (installing apache or nginx adds its log rotation to newsyslog) ● ● What is UCL ● UCL -- universal configuration language ● Inspired by bind/nginx style configuration file that all sysadmins know well ● Fully compatible with JSON, but more liberal in what it accepts, so users do
    [Show full text]
  • Jordan Hubbard Apple Computer, Inc. Oh Really?
    *BSD is dying - Anonymous Coward, Slashdot ©1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 Jordan Hubbard Apple Computer, Inc. Oh really? Let’s look at some stats... FreeBSD Users: 2.5 Million Server Installations (Netcraft) 2,500,000 1,875,000 1,250,000 625,000 0 1993 1997 2001 2003 2004 12 Mac OS X Users: 9 6 3 0 12 Million Jul '01 Oct '01 Jan '02 Apr '02 Jul '02 Oct '02 Jan '03 Apr '03 Jun '03 Oct '03 Oct '04 Applications: FreeBSD ports 12,000 9,000 6,000 10,796 9,662 3,000 6,077 2,723 1,161 0 209 1995 1997 1999 2001 2003 2004 Applications: 12,000 Mac OS X Native 12,000 9,000 6,000 3,000 0 Apr '01 Jul '01 Oct '01 Jan '02 Apr '02 Jul '02 Oct '02 Jan '03 Apr '03 Jun '03 Oct '03 Oct '04 Since the arrival of Mac OS X, BSD has become the biggest desktop UNIX variant on the planet. Yes, even bigger than Linux Take that, Anonymous Coward! Selective overview of Mac OS X Mac OS X Architecture Applications User Interface Application Frameworks Graphics and Media System Services OS Foundation Apple Confidential OS Foundation Usermode BSD Commands and Usermode User FileSystem Libraries Drivers Kernel BSD Kernel IOKit Driver FileSystem Network Families Process Management Drivers Mach Kernel VM Scheduling IPC Open Source “Darwin” base OS Foundation Usermode BSD Commands and Usermode User FileSystem Libraries Drivers Kernel BSD Kernel IOKit Driver FileSystem Network Families Process Management Drivers Mach Kernel VM Scheduling IPC BSD Kernel • FreeBSD 5.1 based (networking, vfs, filesystems, etc) • Unified Buffer Cache (different
    [Show full text]
  • DN Print Magazine BSD News BSD Mall BSD Support Source Wars Join Us
    Mirrors Primary (US) Issues August 2001 August 2001 Get BSD Contact Us Search BSD FAQ New to BSD? DN Print Magazine BSD News BSD Mall BSD Support Source Wars Join Us T H I S M O N T H ' S F E A T U R E S From the Editor The Effects of Tuning a FreeBSD Box for High Open Packages Reaches Performance Milestone 2 by Gilbert Gong by Chris Coleman Each BSD project has its A stock FreeBSD installation delivers a system which is own 3rd party software designed to meet the needs of most users, and strives to packaging system. They are provide the best balance of safety, reliablity, and all based on the same code, performance in a multi-user environment. It is therefore not yet, each of them have optimized for use as a high performance dedicated network features that make one server. This article investigates the effect of tuning a better than the other. Open FreeBSD for use as a dedicated network server. Read More Packages is a volunteer project to unify that code base and incorporate the best features of each. The NetBSD rc.d system by Will Andrews Get BSD Stuff There's been a lot of hubbub the last few months about NetBSD's new rc.d system being the successor of 4.4BSD's. At the USENIX Annual Technical Conference 2001 in Boston, MA, I had the pleasure of sitting down to listen to Luke Mewburn of Wasabi Systems discuss the new rc system NetBSD introduced in their operating system in the 1.5 release earlier this year.
    [Show full text]
  • UNIX History Page 1 Tuesday, December 10, 2002 7:02 PM
    UNIX History Page 1 Tuesday, December 10, 2002 7:02 PM CHAPTER 1 UNIX Evolution and Standardization This chapter introduces UNIX from a historical perspective, showing how the various UNIX versions have evolved over the years since the very first implementation in 1969 to the present day. The chapter also traces the history of the different attempts at standardization that have produced widely adopted standards such as POSIX and the Single UNIX Specification. The material presented here is not intended to document all of the UNIX variants, but rather describes the early UNIX implementations along with those companies and bodies that have had a major impact on the direction and evolution of UNIX. A Brief Walk through Time There are numerous events in the computer industry that have occurred since UNIX started life as a small project in Bell Labs in 1969. UNIX history has been largely influenced by Bell Labs’ Research Editions of UNIX, AT&T’s System V UNIX, Berkeley’s Software Distribution (BSD), and Sun Microsystems’ SunOS and Solaris operating systems. The following list shows the major events that have happened throughout the history of UNIX. Later sections describe some of these events in more detail. 1 UNIX History Page 2 Tuesday, December 10, 2002 7:02 PM 2 UNIX Filesystems—Evolution, Design, and Implementation 1969. Development on UNIX starts in AT&T’s Bell Labs. 1971. 1st Edition UNIX is released. 1973. 4th Edition UNIX is released. This is the first version of UNIX that had the kernel written in C. 1974. Ken Thompson and Dennis Ritchie publish their classic paper, “The UNIX Timesharing System” [RITC74].
    [Show full text]
  • Freebsd Release Engineering
    FreeBSD Release Engineering Murray Stokely <[email protected]> FreeBSD is a registered trademark of the FreeBSD Foundation. Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trade- marks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the “™” or the “®” symbol. 2018-06-12 18:54:46 +0000 by Benedict Reuschling. Abstract Note This document is outdated and does not accurately describe the current release procedures of the FreeBSD Release Engineering team. It is re- tained for historical purposes. The current procedures used by the Free- BSD Release Engineering team are available in the FreeBSD Release Engi- neering article. This paper describes the approach used by the FreeBSD release engineering team to make pro- duction quality releases of the FreeBSD Operating System. It details the methodology used for the official FreeBSD releases and describes the tools available for those interested in produc- ing customized FreeBSD releases for corporate rollouts or commercial productization. Table of Contents 1. Introduction ........................................................................................................................... 1 2. Release Process ......................................................................................................................
    [Show full text]
  • Freebsd VS. Linux: ZFS by ALLAN JUDE
    SEE TEXT ONLY FreeBSD VS. Linux: ZFS BY ALLAN JUDE Why Use ZFS? It is not that other filesystems are bad; they just make the mistake of trusting your storage hardware to return your data when you ask for it. As it turns out, hard drives are pretty good at that, but pretty good is often not good enough. ZFS is the only open-source, OpenZFS is available on many plat- production-quality filesystem that can not only forms, including FreeBSD and Solaris detect but correct the errors when a disk derivatives like IllumOS, as well as Mac returns incorrect data. By combining the roles of filesystem and volume manager, ZFS is also OS X and Linux. However, not all of the able to ensure your data is safe, even in the functionality is available on the latter absence of one or more disks, depending on platforms. The FreeBSD Project has fully your configuration. ZFS doesn’t trust your adopted ZFS, putting significant effort hardware; it verifies that the correct data was into integrating it with the system and returned from each read from the disk. The primary design consideration for ZFS is management tools to make ZFS a seam- the safety of the data. Every block that is writ- less part of the OS, rather than a bolt- ten to the filesystem is accompanied by a ed-on extra. OpenZFS is better inte- checksum of the data, stored with the other grated, instrumented, and documented metadata. That metadata block also has a on FreeBSD than on any of the various checksum, as does its parent, all the way up to the top-level block, called the uber block.
    [Show full text]