DOCSLIB.ORG

25 YEARS AGO Communicate Directly with the PETER H

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
25 YEARS AGO Communicate Directly with the PETER H USENIX BOARD OF DIRECTORS 25 YEARS AGO Communicate directly with the PETER H. SALUS USENIX Board of Directors by writing to [email protected]. [email protected] It was October 1980. PRESIDENT ;login: carried an article headed: USENIX Michael B. Jones, “Microsoft Xenix Operating Sys- [email protected] tem.” With all the to-do over who did what to whom when in UNIX notes (see http://www.groklaw.net), I VICE PRESIDENT thought I’d read it and quote USENIX MEMBER BENEFITS Clem Cole, from it. [email protected] “The XENIX* Operating System Members of the USENIX Associa- from Microsoft is a microprocessor tion receive the following benefits: SECRETARY adaptation of Bell Laboratories’ FREE SUBSCRIPTION to ;login:, the Associ- Version 7 UNIX* operating system. Alva Couch, ation’s magazine, published six times With the XENIX operating system, a year, featuring technical articles, [email protected] Microsoft is bringing the power system administration articles, tips of the UNIX OS to microcomput- and techniques, practical columns on such topics as security, Perl, Java, and TREASURER ers. The XENIX Operating System will be released in versions that operating systems, book reviews, and Theodore Ts’o, run on the Zilog Z8000, Motorola summaries of sessions at USENIX [email protected] conferences. M68000, Intel 8086, and the DEC PDP-11*.” A C CESS TO ;LOGIN: online from October DIRECTORS 1997 to this month: www.usenix.org/ That’s how it began. It continued: Matt Blaze, publications/login/. “The XENIX system is an interac- [email protected] ACCESS TO PAPERS from USENIX confer- tive, multi-user, multi-tasking op- ences online: www.usenix.org/ Jon “maddog” Hall, erating system with a flexible user publications/ library/proceedings/ [email protected] interface. THE RIGHT TO VOTE on matters affecting Geoff Halprin, “Microsoft is committed to sup- the Association, its bylaws, and elec- [email protected] porting the XENIX system as an tion of its directors and officers. Marshall Kirk McKusick, environment for program develop- DISCOUNTS on registration fees for all [email protected] ment that will be identical on all USENIX conferences. the popular 16-bit microproces- sors. Different CUs, as well as dif- DISCOUNTS on the purchase of proceed- EXECUTIVE DIRECTOR ings and CD-ROMs from USENIX ferent hardware boards for the conferences. Ellie Young, same CU, will be supported. .” [email protected] SPECIAL DISCOUNTS on a variety of prod- Interestingly, even 25 years ago, it ucts, books, software, and periodi- “sounds” like Microsoft: “backed cals. For details, see www.usenix.org/ by Microsoft’s experience and ex- membership/specialdisc.html. pertise in producing quality system software.” “Microsoft is committed FOR MORE INFORMATION regarding membership or benefits, please see to having a version of the XENIX www.usenix.org/membership/ system for every popular 16-bit mi- or contact offi[email protected]. croprocessor by the end of 1981.” Phone: 510-528-8649 Go talk to “Bob Greenberg, XENIX Product Manager,” should you have any questions. Oh. Those asterisks. There’s a 4- line footnote about TMs. 48 ;LO GIN: V OL. 30, NO. 5 WORKSHOP PROCEEDINGS SAGE UPDATE Perrine, Stephen Potter, and Pat The October 1985 ;login: carried Wilson. seven papers from the December CHRIS PALMER Then, from July 29th to the 31st, 1984 Graphics Workshop, held in [email protected] the new Board met for a strategic planning session and first Board Monterey. In Atlanta, in June Since the writing of the August meeting of the new SAGE. We 1986, Reidar Bornholt accosted me SAGE update, many of the transi- elected our officers: Tom Perrine is with questions about the “pro- tional arrangements necessary to now the president, Pat Wilson the ceedings” for the 1985 workshop. form a new, independent SAGE vice president, and Andrew Hume When I got back to El Cerrito have come to pass. First and fore- is secretary/treasurer. We then (where the USENIX office was most, we held elections for the spent nearly all of our time plan- then situated), I asked, and a dusty new Board. The SAGE Board con- ning for the short and medium manila envelope was produced. A sists of Geoff Halprin, Trey Harris, term, and doing preliminary long- photo-offset Proceedings was Doug Hughes, Andrew Hume, term brainstorming. available by September. It was the Chris Palmer, David Parter, Tom first workshop so memorialized. ;LOGIN: OCTOBER 2005 USENIX NOTES 49.
Load more

Recommended publications
  • Mandoc: Becoming the Main BSD Manual Toolbox
    mandoc: becoming the main BSD manual toolbox BSDCan 2015, June 13, Ottawa Ingo Schwarze <[email protected]> Cynthia Livingston’sOTTB “Bedifferent” (c) 2013 C. Livingston (with permission) > Ingo Schwarze: mandoc page 2: INTROI BSDCan 2015, June 13, Ottawa Brief history of UNIX documentation • The key point: All documentation in one place and one format. Easy to find, uniform and easy to read and write. Be correct, complete, concise. • 1964: RUNOFF/roffmarkup syntax by Jerome H. Saltzer,MIT. Unobtrusive,diff(1)-friendly,easy to hand-edit, simple tools, high quality output. • 1971: Basic manual structure by Ken Thompson and Dennis Ritchie for the AT&T Version 1 UNIX manuals, Bell Labs. • 1979: man(7) physical markup language for AT&T Version 7 UNIX. • 1989: mdoc(7) semantic markup by Cynthia Livingston for 4.3BSD-Reno. Powerful, self-contained, portable. • 1989: GNU troffbyJames Clarke. • 2001: mdoc(7) rewrite by Werner Lemberg and Ruslan Ermilovfor groff-1.17. • 2008: mandoc(1) started by Kristaps Dzonsons. • 2010: mandoc(1) is the only documentation formatter in the OpenBSD base system. • 2014: mandoc(1) used by default in OpenBSD, FreeBSD, NetBSD, illumos. 16:19:30 What is the mandoc toolbox? → < > Ingo Schwarze: mandoc page 3: INTROIIBSDCan 2015, June 13, Ottawa What is the mandoc toolbox? User perspective:man(1), the manual viewer One comprehensive tool! Normal operation always proceeds in three steps: 1. Find one or more manuals in the file system or using a database by manual name — man(1) — or by search query — apropos(1) =man -k The result of this step can be printed out with man -w.
    [Show full text]
  • A Fast File System for UNIX*
    A Fast File System for UNIX* Marshall Kirk McKusick, William N. Joy†, Samuel J. Leffler‡, Robert S. Fabry Computer Systems Research Group Computer Science Division Department of Electrical Engineering and Computer Science University of California, Berkeley Berkeley, CA 94720 ABSTRACT A reimplementation of the UNIX file system is described. The reimplementation provides substantially higher throughput rates by using more flexible allocation policies that allow better locality of reference and can be adapted to a wide range of peripheral and processor characteristics. The new file system clusters data that is sequentially accessed and provides two block sizes to allow fast access to large files while not wasting large amounts of space for small files. File access rates of up to ten times faster than the traditional UNIX file system are experienced. Long needed enhancements to the pro- grammers’ interface are discussed. These include a mechanism to place advisory locks on files, extensions of the name space across file systems, the ability to use long file names, and provisions for administrative control of resource usage. Revised February 18, 1984 CR Categories and Subject Descriptors: D.4.3 [Operating Systems]: File Systems Management − file organization, directory structures, access methods; D.4.2 [Operating Systems]: Storage Management − allocation/deallocation strategies, secondary storage devices; D.4.8 [Operating Systems]: Performance − measurements, operational analysis; H.3.2 [Information Systems]: Information Storage − file organization Additional Keywords and Phrases: UNIX, file system organization, file system performance, file system design, application program interface. General Terms: file system, measurement, performance. * UNIX is a trademark of Bell Laboratories. † William N. Joy is currently employed by: Sun Microsystems, Inc, 2550 Garcia Avenue, Mountain View, CA 94043 ‡ Samuel J.
    [Show full text]
  • Secure Programming for Linux and Unix HOWTO
    Secure Programming for Linux and Unix HOWTO David A. Wheeler v3.010 Edition Copyright © 1999, 2000, 2001, 2002, 2003 David A. Wheeler v3.010, 3 March 2003 This book provides a set of design and implementation guidelines for writing secure programs for Linux and Unix systems. Such programs include application programs used as viewers of remote data, web applications (including CGI scripts), network servers, and setuid/setgid programs. Specific guidelines for C, C++, Java, Perl, PHP, Python, Tcl, and Ada95 are included. For a current version of the book, see http://www.dwheeler.com/secure−programs This book is Copyright (C) 1999−2003 David A. Wheeler. Permission is granted to copy, distribute and/or modify this book under the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any later version published by the Free Software Foundation; with the invariant sections being ``About the Author'', with no Front−Cover Texts, and no Back−Cover texts. A copy of the license is included in the section entitled "GNU Free Documentation License". This book 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. Secure Programming for Linux and Unix HOWTO Table of Contents Chapter 1. Introduction......................................................................................................................................1 Chapter 2. Background......................................................................................................................................4
    [Show full text]
  • Chapter 2 Unix
    Chapter 2 Unix UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity. –DennisRitchie 2.1 Unix History For many people the term “System Administrator” implies operation of Unix systems, even though the same concepts, tasks and practices apply largely to the maintenance of hosts running any operating system. In this book, we strive to describe principles that are universally applicable and not bound by a specific operating system. We will regularly use Unix as the prime example and cite its features and specific aspects because of its academic background, long history of openness, high penetration of the infrastructure marketplace, and its role as a cornerstone of the Internet. 2.1.1 The Operating System How the Unix operating system came to be and how that relates to the de- velopment of the Internet and various related technologies is fascinating; just 28 CHAPTER 2. UNIX 29 about every other Unix-related book already covers this topic in great detail. In this chapter, we summarize these developments with a focus on the major milestones along the road from the birth of Unix as a test platform for Ken Thompson’s “Space Travel” game running on a PDP-7 to the most widely used server operating system that nowadays also happens to power consumer desktops and laptops (in the form of Linux and Apple’s OS X), mobile de- vices (Apple’s iOS is OS X based and thus Unix derived; Google’s Android is a Linux flavor), TVs, commodity home routers, industry scale networking equipment, embedded devices on the Internet of Things (IoT), and virtually all supercomputers1.
    [Show full text]
  • Release Notes for Platform LSF Chapter 1
    Platform LSF Version 9 Release 1.2 Release Notes GI13-3413-03 Platform LSF Version 9 Release 1.2 Release Notes GI13-3413-03 Note Before using this information and the product it supports, read the information in “Notices” on page 31. First edition This edition applies to version 9, release 1 of IBM Platform LSF (product number 5725G82) and to all subsequent releases and modifications until otherwise indicated in new editions. Significant changes or additions to the text and illustrations are indicated by a vertical line (|) to the left of the change. If you find an error in any Platform Computing documentation, or you have a suggestion for improving it, please let us know. Send your suggestions, comments and questions to the following email address: [email protected] Be sure include the publication title and order number, and, if applicable, the specific location of the information about which you have comments (for example, a page number or a browser URL). When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright IBM Corporation 1992, 2013. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Chapter 1. Release Notes for IBM Bugs fixed ...............28 Platform LSF ............1 Learn more about IBM Platform LSF ......1 Chapter 2. Platform LSF product We’d like to hear from you .........3 packages..............29 Requirements and compatibility ........3 Downloading the Platform LSF product packages .
    [Show full text]
  • Reflections on UNIX Vulnerabilities
    Reflections on UNIX Vulnerabilities Matt Bishop Department of Computer Science University of California at Davis Davis, CA 95616-8562 [email protected] Abstract—The UNIX operating system was developed in composition, or even the proper definition of policy. Instead, a friendly, collaborative environment without any particular it focuses on a particular category of security holes or predefined objectives. As it entered less friendly environments, vulnerabilities for the UNIX1 operating system. Because of expanded its functionality, and became the basis for commer- cial, infrastructure, and home systems, vulnerabilities in the the natural evolution of systems over the years that this paper system affected its robustness and security. This paper presents spans, I construe the terms “UNIX” and “UNIX operating a brief history of UNIX vulnerabilities, beginning with a report system” liberally, to include UNIX-like systems such as written in 1981–1983, but never published. It examines how the Linux. nature of vulnerabilities has (and has not) changed since then, A report I wrote in 1981, and expanded in 1983, motivates and presents some thoughts on the future of vulnerabilities in 2 the UNIX operating system and its variants and other UNIX- this reflection. That report presented several UNIX security like systems. vulnerabilities, and discussed their causes and how to fix them or, where no fixes were available, how to ameliorate Keywords-UNIX security; vulnerabilities; security policy; history; future them. It was circulated among computer security researchers, system administrators, and developers of UNIX systems, but was never published. I. INTRODUCTION This paper examines UNIX vulnerabilities, and their im- In 1981, computer security was not considered a main- pact on UNIX security, in three periods that are roughly stream subdiscipline of computer science.
    [Show full text]
  • Andrew S. Tanenbaum: the Impact of MINIX
    COMPUTINGCOLUMN SECTION CONVERSATIONS TITLE Andrew S. Tanenbaum: The Impact of MINIX Charles Severance, University of Michigan Andrew S. Tanenbaum describes the motivation, development, and market impact of the MINIX operating system. he story of the evolution when teaching courses about OSes. crashing at random. The functionality of Unix and Unix-like At first, Tanenbaum used a booklet was there, but it would run for 15 min- operating systems written by John Lions ( John Lions’ utes and then crash. T is very convoluted. Commentary on Unix 6th ed., with Modern Unix-like OSes generally Source Code; Peer-to-Peer Communi- Tanenbaum knew he was close, derive from AT&T/BSD Unix or some cations, 1976) to teach his classes: but he had trouble solving that “one variation of Linux. But in the begin- last bug” so he wrote software to ning, there was only AT&T Unix, I was teaching a course on operating emulate the PC hardware: and if you trace the moment where systems using version 6 Unix; John the Linux-like OSes flickered to life, Lions wrote a book describing it line by I ran my operating system on a sim- you’ll find the MINIX OS. line that was very popular at universi- ulator for the PC that was entirely MINIX’s original purpose was ties. The bean counters at AT&T didn’t deterministic and reproducible, and simply to support university courses like this: having every computer sci- then after it crashed, I ran it again and that attempted to teach OSes. Es- ence student in the world learn about looked at the last 100,000 instructions sentially, it was a set of floppy disks its product was a horrible idea.
    [Show full text]
  • A UNIX™ Operating System for the DEC VAX-11/780 Computer*
    A UNIX™ Operating System for the DEC VAX-11/780 Computer* Thomas B. London John F. Reiser ABSTRACT A UNIX operating system together with a complete user environment has been implemented on the VAX-11/780 computer manufactured by Digital Equipment Corpora- tion. The VAX-11/780 system provides 32-bit addresses and data. It uses the same input/output devices and the PDP-11 family and is controlled through a console computer which can be remotely accessed. Additionally, the VAX-11/780 is priced nearly the same as a PDP-11/70 and executes most programs somewhat faster than a PDP-11/780. This memorandum describes the VAX-11/780 hardware and the UNIX operating system and the C programming language software implementation, records some obser- vations on program portability, and speculates ways in which the operating system over- head can be significantly reduced. The authors conclude that the VAX-11/780 provides and excellent hardware environment for running UNIX and C software. Introduction The VAX-11/780 [1] is a new, general-purpose, stored-program electronic digital computer manufac- tured by Digital Equipment Corporation. At minicomputer prices it provides addresses and data which are 32 bits wide; the traditional minicomputer address space bound of 64K is gone. This memorandum describes the VAX-11/780 and the implementation of a UNIX operating system and complete user environ- ment for it. Section 2 contains an overview suitable for general consumption; details normally of interest only to devotees of computer system architecture appear in Section 3. The authors comment on software portability in Section 4.
    [Show full text]
  • A Repository of Unix History and Evolution
    Empirical Software Engieering 10.1007/s10664-016-9445-5 A Repository of Unix History and Evolution Diomidis Spinellis Abstract The history and evolution of the Unix operating system is made avail- able as a revision management repository, covering the period from its inception in 1972 as a five thousand line kernel, to 2016 as a widely-used 27 million line system. The 1.1gb repository contains 496 thousand commits and 2,523 branch merges. The repository employs the commonly used Git version control system for its storage, and is hosted on the popular GitHub archive. It has been created by synthesizing with custom software 24 snapshots of systems developed at Bell Labs, the University of California at Berkeley, and the 386bsd team, two legacy repositories, and the modern repository of the open source Freebsd system. In total, 973 individual contributors are identified, the early ones through primary research. The data set can be used for empirical research in software engineering, information systems, and software archaeology. Keywords Software archeology · Unix · configuration management · Git 1 Introduction The Unix operating system stands out as a major engineering breakthrough due to its exemplary design, its numerous technical contributions, its impact, its develop- ment model, and its widespread use (Gehani 2003, pp. 27{29). The design of the Unix programming environment has been characterized as one offering unusual The work has been partially funded by the Research Centre of the Athens University of Eco- nomics and Business, under the Original Scientific Publications framework (project code EP- 2279-01) and supported by computational time granted from the Greek Research & Technology Network (grnet) in the National hpc facility | aris | under project id pa003005-cdolpot.
    [Show full text]
  • Basics of System Administration on a Unix System Contents
    Basics of system administration on a Unix system Contents Introduction 3 Unix 9 User environment: the shell 10 File management: starting from / 11 Text editing 12 Package management 13 User management 14 Process management 15 Networking services 16 Web 17 Database 18 Mail 19 Users 20 Files 21 DNS 22 Printing 23 Credits 24 This is a development version of the text that should be considered a work-in-progress. Copyright © 2011 Dara Adib. This is a freely licensed work, as explained in the Definition of Free Cultural Works (freedomdefined.org). It is licensed under the Creative Commons Attribution- Share Alike 3.0 United States License. To view a copy of this license, visit: http://creativecommons.org/licenses/by-sa/3.0/ 2 Introduction What is a computer? A computer is a combination of hardware and software that can store, retrieve, and process infor- mation. Hardware Hardware is the physical electronics of a computer, which include one or more processors (“the brain”), random-access memory (“short-term memory”), disk (“long-term memory”), input/output devices (“sense/motor organs”), power supply, and complex circuitry and buses which connect components. Software Software is the conceptual instructions that run on hardware, including system programs and application programs. An operating system is an essential software component. What is an operating system? An operating system (OS) is a collection of system programs (and depending on definition, application programs) that accomplish User abstraction through hardware, file, process, and user manage- ment (and depending again on definition, by providing a user Application environment). Operating System Hardware management An operating system deals with the physical complexity of initial- Hardware izing, calibrating, polling, and resetting hardware components.
    [Show full text]
  • UNIX for Beginners — Second Edition Brian W. Kernighan Bell
    UNIX For Beginners — Second Edition Brian W. Kernighan Bell Laboratories Murray Hill, New Jersey 07974 ABSTRACT This paper is meant to help new users get started on the UNIX† operating system. It includes: • basics needed for day-to-day use of the system — typing commands, correcting typing mistakes, logging in and out, mail, inter-terminal communication, the file system, printing files, redirecting I/O, pipes, and the shell. • document preparation — a brief discussion of the major formatting programs and macro packages, hints on preparing documents, and capsule descriptions of some supporting software. • UNIX programming — using the editor, programming the shell, programming in C, other languages and tools. • An annotated UNIX bibliography. November 2, 1997 †UNIX is a Trademark of Bell Laboratories. -- -- UNIX For Beginners — Second Edition Brian W. Kernighan Bell Laboratories Murray Hill, New Jersey 07974 INTRODUCTION 5. A UNIX Reading List. An annotated bibliography From the user’s point of view, the UNIX operating of documents that new users should be aware of. system is easy to learn and use, and presents few of the usual impediments to getting the job done. It is hard, I. GETTING STARTED however, for the beginner to know where to start, and how to make the best use of the facilities available. Logging In The purpose of this introduction is to help new users You must have a UNIX login name, which you can get used to the main ideas of the UNIX system and start get from whoever administers your system. You also making effective use of it quickly. need to know the phone number, unless your system You should have a couple of other documents with uses permanently connected terminals.
    [Show full text]
  • Timeline of Operating Systems - Wikipedia, the Free Encyclopedia
    Timeline of operating systems - Wikipedia, the free encyclopedia http://en.wikipedia.org/wiki/Timeline_of_operating_systems Timeline of operating systems From Wikipedia, the free encyclopedia This article presents a timeline of events in the history of computer operating systems from 1951 to 2009. For a narrative explaining the overall developments, see the History of operating systems. Contents 1 1950s 2 1960s 3 1970s 4 1980s 5 1990s 6 2000s 7 See also 7.1 Category links 8 References 9 External links 1950s 1951 LEO I 'Lyons Electronic Office'[1] was the commercial development of EDSAC computing platform, supported by British firm J. Lyons and Co. 1954 MIT's operating system made for UNIVAC 1103[2] 1955 General Motors Operating System made for IBM 701[3] 1956 GM-NAA I/O for IBM 704, based on General Motors Operating System 1957 Atlas Supervisor (Manchester University) (Atlas computer project start) BESYS (Bell Labs), for IBM 7090 and IBM 7094 1958 University of Michigan Executive System (UMES), for IBM 704, 709, and 7090 1959 SHARE Operating System (SOS), based on GM-NAA I/O 1 of 16 2/24/11 9:28 PM Timeline of operating systems - Wikipedia, the free encyclopedia http://en.wikipedia.org/wiki/Timeline_of_operating_systems 1960s 1960 IBSYS (IBM for its 7090 and 7094) 1961 CTSS (MIT's Compatible Time-Sharing System for the IBM 7094) MCP (Burroughs Master Control Program) 1962 Atlas Supervisor (Manchester University) (Atlas computer commissioned) GCOS (GE's General Comprehensive Operating System, originally GECOS, General Electric Comprehensive
    [Show full text]