DOCSLIB.ORG

BSD Is Dying a Cautionary Tale of Sex and Greed

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

BSD is Dying A cautionary tale of Sex and Greed 1 2 Prologue 2 3 What is BSD? 3 4 What is UNIX? 4 5 What is an Operating System? 5 6 What is a Computer? 6 7 What is a user? 7 8 Who am I? 8 SysAdmin 9 networks 10 firewalls 11 tweaking 12 13 14 Programmer (sorta) 15 16 17 18 19 jdixon@ 20 21 Consultant 22 DixonGroup Consulting 23 Employee 24 25 Lover 26 27 27 28 Why am I here? 28 29 To talk about why... 29 30 ... is dying. 31 31 32 33 34 What is BSD? 34 35 What is UNIX? 35 36 What is an Operating System? 36 37 What is a Computer? 37 com-pu-ter [kuh m-pyoo-ter] n. 1. A device that computes, especially a programmable electronic machine that performs high-speed mathematical or logical operations or that assembles, stores, correlates, or otherwise processes information. 2. One who computes. 38 39 40 41 42 43 44 What does a Computer do ? 44 45 46 47 48 49 pr0n 50 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 51 52 53 54 55 How... ? 55 56 00100011011010010110111001 10001101101100011101010110 01000110010100100000001111 00011100110111100101110011 00101111011010110110010101 11001001101110011001010110 11000010111001101000001111 10 56 foundation 57 kernel + 58 libraries + 59 userland applications 60 = operating system 61 61 62 62 63 What is a kernel? 63 management 64 processes 65 memory 66 peripheral devices 67 68 69 And by extension... 69 networking 70 security 71 disks and file systems 72 user interfaces 73 userland applications 74 75 76 77 pr0n 78 79 80 much, much more... 81 81 [ pause ] 82 83 In summary... 83 84 BSD is a UNIX-derived Operating System. Enables users to harness the power of a computer to process information. It uses a kernel to manage processes, memory, and peripheral devices. By extension, we can perform networking, enforce security, read from and write to storage devices, and interface visually to applications like text editors, mail clients, web browsers, multimedia players, and games. [ catch breath ] 84 85 Genesis 85 In the beginning... (1960s) 86 87 88 Multiplexed Information and Computing Service 88 89 Life was Good (TM) 90 WRONG Life was Good (TM) 90 commercial failure 91 92 Ken Thompson 93 Space Travel 94 95 What is an assembly programmer to do? 95 96 Dennis Ritchie 97 98 1970 99 100 Uniplexed Information and Computing System 100 101 number of users 101 102 2 102 UNIX 103 104 text processing 105 roff 106 text editor 107 patents 108 1973 109 rewrote UNIX 110 111 portable 112 113 source code available 114 1974 115 Bob Fabry 116 117 $99 118 119 1977 120 Bill Joy 121 Berkeley Software Distribution 122 1BSD 123 Pascal compiler 124 ex 125 1978 126 2BSD 127 vi 128 csh 129 1979 130 3BSD 131 VMUNIX (Virtual VAX/UNIX) 132 133 Computer Systems Research Group 134 1980 135 4BSD 136 job control 137 delivermail 138 curses 139 1981 140 4.1BSD 141 performance on VAX 142 1983 143 4.2BSD 144 TCP/IP 145 Berkeley Fast File System 146 Marshall Kirk McKusick 147 148 1986 149 4.3BSD 150 performance improvements over 4.2BSD 151 1988 152 4.3BSD-Tahoe 153 initially designed for Power 6/32 “Tahoe” platform 154 some machine-independent code 155 1989 156 Net/1 157 separated networking code from AT&T UNIX code 158 permissive BSD license 159 1990 160 4.3BSD-Reno 161 MACH virtual memory system 162 Sun-compatible NFS 163 moving towards POSIX 164 1991 165 Net/2 166 all AT&T code and utilities were replaced or removed 167 168 basis for 386BSD and BSD/386 169 William Jolitz 170 386BSD 171 171 172 173 Exodus 173 1992 174 Unix System Laboratories 175 176 177 USL v. BSDI 177 178 injunction 179 180 1-800-ITS UNIX 181 Net/2 + 6 files 182 Dickinson R. Debevoise 183 184 complaint narrowed 185 recent copyrights 186 possiblilty of the loss of trade secrets 187 state court 188 189 countersuit 190 191 not coincidentally... 192 USL 193 193 194 Ray Noorda, CEO 195 1994 196 197 settlement 198 2004 199 200 • 4.4BSD-lite to be released containing no disputed files. University to encourage licensees to switch from Net-2. • University to cease distribution of certain files. • USL to grant three months grace period to users of disputed files. • Certain files distributed by University to carry USL copyright notice. • Certain files distributed by USL to carry University copyright notices. • USL to permit free distribution of certain files. • University not to actively assist in legal attempts to challenge USL's rights to certain files. 201 202 203 4.4BSD-Encumbered (USL license) 204 4.4BSD-Lite (BSD license) 205 206 Resurrection 206 207 208 208 Intel x86 209 Intel x86 Intel Itanium 209 Intel x86 Intel Itanium AMD64 209 Intel x86 Intel Itanium AMD64 Alpha 209 Intel x86 Intel Itanium AMD64 Alpha Sun UltraSPARC 209 jail access control lists mandatory access controls historically, strong TCP/IP and SMP performance dtrace ZFS 210 211 211 212 over 50 hardware platforms from a single source tree 212 213 acorn26 acorn32 algor alpha amd64 amiga amigappc arc arm32 atari bebox cats cesfic cobalt dreamcast evbarm evbmips evbppc evbsh3 evbsh5 ews4800mips hp300 hp700 hpcarm hpcmips hpcsh i386 ibmnws iyonix luna68k mac68k macppc mipsco mmeye mvme68k mvmeppc netwinder news68k newsmips next68k ofppc pc532 playstation2 pmax pmppc prep sandpoint sbmips sgimips sh3 sh5 shark sparc sparc64 sun2 sun3 vax x68k xen 213 214 214 forked from NetBSD 1.0 215 Alpha 216 Alpha i386 216 Alpha AMD64 i386 216 Alpha AMD64 i386 MacPPC 216 Alpha AMD64 i386 MacPPC SGI 216 Alpha AMD64 i386 MacPPC SGI Sparc 216 Alpha AMD64 i386 MacPPC SGI Sparc Sparc64 216 Alpha AMD64 i386 MacPPC SGI Sparc Sparc64 VAX 216 Alpha AMD64 i386 MacPPC SGI Sparc Sparc64 VAX Zaurus 216 new release every 6 months 217 “secure by default” 218 219 full disclosure 219 full disclosure audits 219 full disclosure audits privsep & revocation 219 full disclosure audits privsep & revocation chroot jails 219 full disclosure audits privsep & revocation chroot jails random pids 219 full disclosure audits privsep & revocation chroot jails random pids ProPolice 219 PF 220 PF PF 220 PF authpf PF 220 PF authpf CARP PF 220 PF authpf CARP pfsyncd PF 220 PF authpf CARP pfsyncd sasyncd PF 220 PF authpf CARP pfsyncd sasyncd bioctl PF 220 PF authpf CARP pfsyncd sasyncd bioctl hoststated PF 220 221 221 logical continuation of FreeBSD 4.8 222 SMP revamp 223 224 225 226 others 227 228 Revelations 228 229 Why is BSD dying? 229 230 Because IDC says so. 230 market share <1% 231 232 Netcraft confirms these findings. 232 233 Last place, SysAdmin networking test LOSER 233 234 Open-source projects are giving away free software. 234 Free Software == Terrism BSD... Bad! 235 236 Inability to adapt. 236 ASP .NET pages served per hour 250.0 187.5 125.0 62.5 0 Windows Linux FreeBSD NetBSD OpenBSD Source: MCSE Weekly, Feb. 2003 237 238 Loss of talent. 238 FreeBSD has lost 93% of their core developers. 239 240 Not all is lost. 240 Fortunately, a few small companies still use BSD. 241 242 243 244 245 246 247 248 249 250 251 252 Epilogue 252 technological challenges 253 virtualization 254 DRM 255 political challenges 256 blobs 257 NDAs 258 closed documentation 259 diversity 260 unity 261 262 the end 263.
Recommended publications
  • BSD – Alternativen Zu Linux

    BSD – Alternativen Zu Linux

    ∗BSD { Alternativen zu Linux Karl Lockhoff March 19, 2015 Inhaltsverzeichnis I Woher kommt BSD? I Was ist BSD? I Was ist sind die Unterschiede zwischen FreeBSD, NetBSD und OpenBSD? I Warum soll ich *BSD statt Linux einsetzen? I Chuck Haley und Bill Joy entwickeln den vi in Berkeley I Bill Joy erstellt eine Sammlung von Tools, 1BSD I Unix Version 7 erscheint I 2BSD erscheint (Basis f¨urdie Weiterentwicklung PDP-11) I 3BSD erscheint (erstmalig mit einen eigenen Kernel) I 4BSD erscheint (enth¨altdas fast file system (ffs)) I Bill Joy wechselt zu Sun Microsystems I Kirk McKusick ¨ubernimmt die Entwicklung von BSD I 1978 I 1979 I 1980 I 1981 Woher kommt BSD? I 1976 I Unix Version 6 erscheint I 2BSD erscheint (Basis f¨urdie Weiterentwicklung PDP-11) I 3BSD erscheint (erstmalig mit einen eigenen Kernel) I 4BSD erscheint (enth¨altdas fast file system (ffs)) I Bill Joy wechselt zu Sun Microsystems I Kirk McKusick ¨ubernimmt die Entwicklung von BSD I Bill Joy erstellt eine Sammlung von Tools, 1BSD I Unix Version 7 erscheint I 1979 I 1980 I 1981 Woher kommt BSD? I 1976 I Unix Version 6 erscheint I 1978 I Chuck Haley und Bill Joy entwickeln den vi in Berkeley I 2BSD erscheint (Basis f¨urdie Weiterentwicklung PDP-11) I 3BSD erscheint (erstmalig mit einen eigenen Kernel) I 4BSD erscheint (enth¨altdas fast file system (ffs)) I Bill Joy wechselt zu Sun Microsystems I Kirk McKusick ¨ubernimmt die Entwicklung von BSD I Unix Version 7 erscheint I 1979 I 1980 I 1981 Woher kommt BSD? I 1976 I Unix Version 6 erscheint I 1978 I Chuck Haley und Bill Joy entwickeln den
  • Openbsd and Soekris

    Openbsd and Soekris

    OpenBSD and Soekris UUASC meeting June 3, 2004 Presented by Arild Jensen Outline ● What is OpenBSD and where do I get it? ● Built-in security features ● Maintaining an OpenBSD system ● The PF packet filter Outline (cont'd) ● What is Soekris and where do I get it? ● Different models and accessories ● Getting OpenBSD onto a Soekris box ● Maintaining a Soekris/OpenBSD solution What is OpenBSD? History BSD Net/2 (4.3BSD Lite) NetBSD 0.8 386BSD 0.0 NetBSD 0.9 386BSD 0.1 4.4BSD Lite 1 NetBSD 1.0 386BSD 1.0 NetBSD 1.1 OpenBSD FreeBSD What is OpenBSD? From the creators: “...freely available, multi- platform 4.4BSD-based UNIX-like OS.” Emphasis on: ● Portability ● Standardization ● Correctness ● Proactive Security ● Integrated Cryptography ...and where do I get it? www.openbsd.org CD sales only No .iso downloads $40 Portability ● i386 ● MVME68k ● Sparc ● MVME88k ● Sparc64 ● AMD64 ● HP300 ● CATS (ARM) ● Mac68k ● MacPPC ● HPPA Standardization The Story of CARP ● Firewall failover desired ● IEEE VRRP (Virtual router redundancy protocol) ● Cisco patents involved, HSRP protocol ● Cisco and Alcatel dispute ● Birth of CARP (Common address redundancy protocol ● Early implementation included in OpenBSD 3.5 Correctness The Audit Process ● 6-12 member security team ● Continuous audit of code multiple times by different people ● Security holes and common errors ● Result: Newly discovered bugs often already fixed in OpenBSD Pro-active Security Source Code Run Time ● ProPolice ● Privilege Separation – Buffer overflow – Avoid running as root protection – Dual-process setup – Similar to Stackguard – Daemons being ● W^X converted – Write xor Execute ● Chroot – Fine-grained memory – Apache /var/www permission layout – BIND /var/named – Only on some architectures Cryptography ● Based outside of U.S.
  • 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.
  • 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

    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
  • United States Court of Appeals for the FOURTH CIRCUIT

    United States Court of Appeals for the FOURTH CIRCUIT

    Case: 10-1482 Document: 35 Date Filed: 09/17/2010 Page: 1 No. 10-1482 IN THE United States Court of Appeals FOR THE FOURTH CIRCUIT dNOVELL, INCORPORATED, Plaintiff-Appellant, —v.— MICROSOFT CORPORATION, Defendant-Appellee. ON APPEAL FROM THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF MARYLAND BRIEF OF APPELLEE MICROSOFT CORPORATION RICHARD J. WALLIS DAVID B.TULCHIN STEVEN J. AESCHBACHER Counsel of Record MICROSOFT CORPORATION STEVEN L. HOLLEY One Microsoft Way SULLIVAN & CROMWELL LLP Redmond, Washington 98052 125 Broad Street (425) 882-8080 New York, New York 10004 (212) 558-4000 G. S TEWART WEBB VENABLE LLP 750 East Pratt Street, Suite 900 Baltimore, Maryland 21202 (410) 244-7400 Attorneys for Microsoft Corporation September 17, 2010 Case: 10-1482 Document: 35 Date Filed: 09/17/2010 Page: 2 UNITED STATES COURT OF APPEALS FOR THE FOURTH CIRCUIT DISCLOSURE OF CORPORATE AFFILIATIONS AND OTHER INTERESTS Only one form needs to be completed for a party even if the party is represented by more than one attorney. Disclosures must be filed on behalf of all parties to a civil, agency, bankruptcy or mandamus case. Corporate defendants in a criminal or post-conviction case and corporate amici curiae are required to file disclosure statements. Counsel has a continuing duty to update this information. No. _______ Caption: __________________________________________________ Pursuant to FRAP 26.1 and Local Rule 26.1, ______________________ who is _______________________, makes the following disclosure: (name of party/amicus) (appellant/appellee/amicus) 1. Is party/amicus a publicly held corporation or other publicly held entity? YES NO 2. Does party/amicus have any parent corporations? YES NO If yes, identify all parent corporations, including grandparent and great-grandparent corporations: 3.
  • A Brief Technical Introduction

    A Brief Technical Introduction

    Mac OS X A Brief Technical Introduction Leon Towns-von Stauber, Occam's Razor LISA Hit the Ground Running, December 2005 http://www.occam.com/osx/ X Contents Opening Remarks..............................3 What is Mac OS X?.............................5 A New Kind of UNIX.........................12 A Diferent Kind of UNIX..................15 Resources........................................39 X Opening Remarks 3 This is a technical introduction to Mac OS X, mainly targeted to experienced UNIX users for whom OS X is at least relatively new This presentation covers primarily Mac OS X 10.4.3 (Darwin 8.3), aka Tiger X Legal Notices 4 This presentation Copyright © 2003-2005 Leon Towns-von Stauber. All rights reserved. Trademark notices Apple®, Mac®, Macintosh®, Mac OS®, Finder™, Quartz™, Cocoa®, Carbon®, AppleScript®, Bonjour™, Panther™, Tiger™, and other terms are trademarks of Apple Computer. See <http://www.apple.com/legal/ appletmlist.html>. NeXT®, NeXTstep®, OpenStep®, and NetInfo® are trademarks of NeXT Software. See <http://www.apple.com/legal/nexttmlist.html>. Other trademarks are the property of their respective owners. X What Is It? 5 Answers Ancestry Operating System Products The Structure of Mac OS X X What Is It? Answers 6 It's an elephant I mean, it's like the elephant in the Chinese/Indian parable of the blind men, perceived as diferent things depending on the approach X What Is It? Answers 7 Inheritor of the Mac OS legacy Evolved GUI, Carbon (from Mac Toolbox), AppleScript, QuickTime, etc. The latest version of NeXTstep Mach, Quartz (from Display PostScript), Cocoa (from OpenStep), NetInfo, apps (Mail, Terminal, TextEdit, Preview, Interface Builder, Project Builder, etc.), bundles, faxing from Print panel, NetBoot, etc.
  • Mac OS X Intro for UNIX Users

    Mac OS X Intro for UNIX Users

    Mac OS X An Introduction for UNIX Users Leon Towns-von Stauber, Occam's Razor Seattle BSD Users Group, October 2004 http://www.occam.com/osx/ X Contents Opening Remarks.............................3 Where Did Mac OS X Come From?.....5 What is Mac OS X?..........................13 A New Kind of UNIX........................25 A Different Kind of UNIX.................28 Why Use Mac OS X?.........................60 Resources.......................................63 Closing Remarks.............................67 X Opening Remarks 3 This is a technical introduction to Mac OS X, mainly targeted to experienced UNIX users for whom OS X is at least relatively new Some emphasis on comparisons with FreeBSD I'm assuming basic familiarity with operating system design Where I'm coming from: UNIX user and some-time admin since 1990 Full-time UNIX admin since 1995 NeXTstep user and admin since 1991 This presentation covers primarily Mac OS X 10.3.5 (Darwin 7.5) X Legal Notices 4 This presentation Copyright © 2003-2004 Leon Towns-von Stauber. All rights reserved. Trademark notices Apple®, Mac®, Macintosh®, Mac OS®, Aqua®, Finder™, Quartz™, Cocoa®, Carbon®, AppleScript®, Rendezvous™, Panther™, and other terms are trademarks of Apple Computer. See <http:// www.apple.com/legal/appletmlist.html>. NeXT®, NeXTstep®, OpenStep®, and NetInfo® are trademarks of NeXT Software. See <http://www.apple.com/legal/nexttmlist.html>. PowerPC™ is a trademark of International Business Machines. Java™ is a trademark of Sun Microsystems. Other trademarks are the property of their
  • Kratka Povijest Unixa Od Unicsa Do Freebsda I Linuxa

    Kratka Povijest Unixa Od Unicsa Do Freebsda I Linuxa

    Kratka povijest UNIXa Od UNICSa do FreeBSDa i Linuxa 1 Autor: Hrvoje Horvat Naslov: Kratka povijest UNIXa - Od UNICSa do FreeBSDa i Linuxa Licenca i prava korištenja: Svi imaju pravo koristiti, mijenjati, kopirati i štampati (printati) knjigu, prema pravilima GNU GPL licence. Mjesto i godina izdavanja: Osijek, 2017 ISBN: 978-953-59438-0-8 (PDF-online) URL publikacije (PDF): https://www.opensource-osijek.org/knjige/Kratka povijest UNIXa - Od UNICSa do FreeBSDa i Linuxa.pdf ISBN: 978-953- 59438-1- 5 (HTML-online) DokuWiki URL (HTML): https://www.opensource-osijek.org/dokuwiki/wiki:knjige:kratka-povijest- unixa Verzija publikacije : 1.0 Nakalada : Vlastita naklada Uz pravo svakoga na vlastito štampanje (printanje), prema pravilima GNU GPL licence. Ova knjiga je napisana unutar inicijative Open Source Osijek: https://www.opensource-osijek.org Inicijativa Open Source Osijek je član udruge Osijek Software City: http://softwarecity.hr/ UNIX je registrirano i zaštićeno ime od strane tvrtke X/Open (Open Group). FreeBSD i FreeBSD logo su registrirani i zaštićeni od strane FreeBSD Foundation. Imena i logo : Apple, Mac, Macintosh, iOS i Mac OS su registrirani i zaštićeni od strane tvrtke Apple Computer. Ime i logo IBM i AIX su registrirani i zaštićeni od strane tvrtke International Business Machines Corporation. IEEE, POSIX i 802 registrirani i zaštićeni od strane instituta Institute of Electrical and Electronics Engineers. Ime Linux je registrirano i zaštićeno od strane Linusa Torvaldsa u Sjedinjenim Američkim Državama. Ime i logo : Sun, Sun Microsystems, SunOS, Solaris i Java su registrirani i zaštićeni od strane tvrtke Sun Microsystems, sada u vlasništvu tvrtke Oracle. Ime i logo Oracle su u vlasništvu tvrtke Oracle.
  • Motivations of Participating in Open Source Projects

    Motivations of Participating in Open Source Projects

    Proceedings of the 34th Hawaii International Conference on System Sciences - 2001 Working for Free? – Motivations of Participating in Open Source Projects Alexander Hars Shaosong Ou IOM Department IOM Department Marshall School of Business Marshall School of Business University of Southern California University of Southern California [email protected] [email protected] Abstract the public, including the right to use, to redistribute and to The success of the Linux operating system has modify the software free of charge. This is a direct demonstrated the viability of an alternative form of challenge to the established assumptions about software software development – open source software – that markets that threatens the position of commercial challenges traditional assumptions about software software vendors. markets. Understanding what drives open source The open source phenomenon raises many interesting developers to participate in open source projects is questions. Its proponents regard it as a paradigmatic crucial for assessing the impact of open source software. change where the economics of private goods built on the This article identifies two broad types of motivations that scarcity of resources are replaced by the economics of account for their participation in open source projects. public goods where scarcity is not an issue. Critics argue The first category includes internal factors such as that open source software will always be relegated to intrinsic motivation and altruism, and the second niche areas, that it cannot compete with their commercial category focuses on external rewards such as expected opponents in terms of product stability and reliability future returns and personal needs. This article also [15], and that open source projects lack the capability to reports the results of a survey administered to open innovate.
  • Openafs: BSD Clients 2009

    Openafs: BSD Clients 2009

    OpenAFS: BSD Clients 2009 Matt Benjamin <[email protected]> OpenAFS: BSD Clients 2009 Who am I? ● OpenAFS developer interested in various new-code development topics ● for the last while, “portmaster” for BSD clients except DARWIN/MacOS X ● involves evolving the ports, interfacing withusers and port maintainers in the BSD communities OpenAFS: BSD Clients 2009 Former Maintainers ● Tom Maher, MIT ● Jim Rees, University of Michigan (former Gatekeeper and Elder) ● Garret Wollman, MIT OpenAFS: BSD Clients 2009 Other Active ● Ben Kaduk (FreeBSD) ● Tony Jago (FreeBSD) ● Jamie Fournier (NetBSD) OpenAFS: BSD Clients 2009 Historical Remarks ● AFS originated in a BSD 4.2 environment ● extend UFS with coherence across a group of machines ● Terminology in common with BSD, SunOS, etc, e.g., vnodes ● Followed SunOS and Ultrix to Solaris and Digital Unix in Transarc period ● 386BSD released at 4.3 level in the Transarc period, some client development never publically released (or independent of Transarc) OpenAFS: BSD Clients 2009 BSD Clients Today ● Descendents of 386BSD distribution and successors, not including DARWIN/MacOS X ● DARWIN separately maintained, though of course there are similarities OpenAFS: BSD Clients 2009 Today ● FreeBSD ● OpenBSD Soon ● NetBSD ● OpenBSD Not yet supported (as a client): ● Dragonfly BSD OpenAFS: BSD Clients 2009 BSD Port History I ● First 386BSD port probably that of John Kohl (MIT), for NetBSD ● First to appear in OpenAFS is FreeBSD, by Tom Maher ● Next to appear in OpenAFS is OpenBSD, by Jim Rees ● Significant evolution
  • Softraid Boot

    Softraid Boot

    softraid boot Stefan Sperling <[email protected]> EuroBSDcon 2015 Introduction to softraid OpenBSD's softraid(4) device emulates a host controller which provides a virtual SCSI bus uses disciplines to perform I/O on underlying disks: RAID 0, RAID 1, RAID 5, CRYPTO, CONCAT borrows the bioctl(8) configuration utility from the bio(4) hardware RAID abstraction layer softraid0 at root scsibus4 at softraid0: 256 targets sd9 at scsibus4 targ 1 lun 0: <OPENBSD, SR RAID 1, 005> SCSI2 0/direct fixed sd9: 1430796MB, 512 bytes/sector, 2930271472 sectors (RAID 1 softraid volume appearing as disk sd9) OpenBSD softraid boot 2/22 Introduction to softraid OpenBSD's softraid(4) device uses chunks (disklabel slices of type RAID) for storage records meta data at the start of each chunk: format version, UUID, volume ID, no. of chunks, chunk ID, RAID type and size, and other optional meta data # disklabel -pm sd2 [...] # size offset fstype [fsize bsize cpg] c: 1430799.4M 0 unused d: 1430796.9M 64 RAID # bioctl sd9 Volume Status Size Device softraid0 0 Online 1500298993664 sd9 RAID1 0 Online 1500298993664 0:0.0 noencl <sd2d> 1 Online 1500298993664 0:1.0 noencl <sd3d> (RAID 1 softraid volume using sd2d and sd3d for storage) OpenBSD softraid boot 3/22 Introduction to softraid softraid volumes can be assembled manually with bioctl(8) or automatically during boot softraid UUID ties volumes and chunks together disk device names and disklabel UUIDs are irrelevant when softraid volumes are auto-assembled volume IDs are used to attach volumes in a predictable order stable disk device names unless disks are added/removed chunk IDs make chunks appear in a predictable order important for e.g.
  • UNIX History Page 1 Tuesday, December 10, 2002 7:02 PM

    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].