DOCSLIB.ORG

SURPRISES with SCO UNIX/386 Serial Number and Activation Key, Was Set up to Support Only Two Users at a Time

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
SURPRISES with SCO UNIX/386 Serial Number and Activation Key, Was Set up to Support Only Two Users at a Time .0 of Unix, determined by the SURPRISES WITH SCO UNIX/386 serial number and activation key, was set up to support only two users at a time. But the initialization file started BY SIMSON L. GARFINKEL login programs for 12 termi- nals: instant lock-out. I called SCO and got a new t's really hard to write good software, and the people at The numb er and key that solved my problem. Santa Cruz Operation have earned a well-deserved reputa- tion for their excellent ports of Unix software to industry- A FAS TOPERATING SYSTEM standard 286 and 386 platforms. When I heard that SCO was This Unix is fast. offering AT&T Unix System V release 3.2, it was enough to Beiing a true 386 operating system, convince me to replace my old 286 box with an AST Premium Unix, unlike 16-bit DOS, lets my cornm- 386C computer so I could run the new operating system. puter run at its full speed. By virtue of I was in for a lot of surprises. being Unix, it lets me take advantage of Si UnixSystem For nearly two months I've wrestled with SCO's System more than 15 years of operating system - I. V/386 release 3.2. The verdict from the front lines is that while techmology, such as posted disk writes, /386~s~ the operating system may be a good product for Unix system strean,s support, and some exception- real Unix hackers or product developers, it is not yet ready for the ally powerful (and efficient) program- general Unix community. mer's tools. for PCs, Unix System V/386 is real Unix on a PC. It is also real SC() has added a lot of functionality System V, which I don't like because it is filled with many to AT &Ts vanilla Unix. First is SCO's but it's still arbitrary restrictions. Niceties such as file names longer than "multiscreen" system, which turns my etWare® 14 characters, symbolic links, and job control are missing or keybo ard and console into 12 virtual ter- John T. Mc( buggy only partially implemented in the current release, 3.2. AT&T minal s. Simply by pressing Alt with a h Adam T. F plans to incorporate these and other features from Berkeley functiion key, I switch to another virtual of Business Unix in its release 4.0. SCO plans to have them in 3.2 by the termirial with its own login: prompt. second half of 1990, according to David R. Bernstein, SCO's Multis,creen is not a window system, but intained are manager of Unix product marketing. I haveea dozen 80 x 25 terminals at my :lude unders instant disposal. And they are all vely are's® undoc INSTALLATION IS LESS THAN SMOOTH fast, thanks to SCO's amazing screen lities, implenrr My first surprise with Unix System V/386 was its size: the I/O dirivers. ,Ns, refining operating system comes on 29 1.2-Mbyte floppy disks. This C2-l4evel security is another feature SCO ich more! takes up 73.5 Mbytes of hard drive, including swap space - has brought to System V/386 release lok only and that's without application software. 3.2. We believe security is not an add- When I started, I already had a 30-Mbyte DOS partition on on; it is an integral part of the system," my 210-Mbyte SCSI hard disk. SCO's installation procedure says EBernstein, adding that B1 security. AN Troul was very careful to prevent me from overwriting it. I patiently with access control lists and mandatorv andbook fed my computer the disks as they were requested. Then came accesss control parameters, will be avail- Mark A. Mill a media error on disk B6 -I had a bad distribution disk. I able siometime this year. continued the installation anyway to see what would happen. SC() has made it very easy to relink dressed are The install program crashed in a few minutes because I was the Urnix kernel and add new device driv- h troubleshc missing important files (on disk B6) that are required to set up ers. Feor example, you only have to type N architectu a password for the root user. Without a password for root, I mkdexv streams, and the streams pack- hernet, and was locked out of my new Unix system. age is automatically compiled and linked ok & Disk (A In two days I received a good B6 disk from SCO. But when I into tIhe kernel, and the new kernel is ok only tried to reinstall V/386 - Surprise!- the boot program dis- ready to boot. covered a valid Unix operating system on the hard disk and But my favorite SCO enhancement to ueprint tried to run it. Unfortunately, it was the Unix operating system Unix is native support of DOS file sys- Craig Chaik I had made but couldn't use. tems. 'The kernel implements a file sys- I couldn't find any instructions on what to do in this situation, ter switch that allows non-Unix file twork admir even from SCO's technical support. I was finally reduced t systenns (such as networks and write- Id and insta deleting the Unix partition and starting over. But you need once optical disks) to be linked into the )les, configL Unix to delete Unix partitions. The only way I could find to Unix kernel and accessed transparently. 'dware and salvage my hard disk was to perform a low-level format. - A DO!S switch lets me mount my entire itinuing sup With the new B6 disk and the newly formatted hard disk, the DOS partition. I like this much better kcontaining installation went smoothly until I tried to log in.-My version than he DOS disk utilities because the k & Disk (A ok only · *-AV W(MaTAT1ONJ 78 JUNE 1990 & _i:['.011 0[3l:l I switch allows Unix programs to access the editor, but there is apparently no way I've scanned the documentation, but I DOS files transparently. The DOS utili- to restart it. Furthermore, the console is can't figure out how to rebuild the data- ties are still available if you want them. The left in raw mode with echo turned off. base to restore consistency. And since I only bug I have found with the DOS file When I discussed the problem on the can't edit the files by hand without shut- system is that 'sh' does not do wild-card phone with SCO, I was told to type Ct r 1- ting myself out, I'm effectively barred matching, although 'csh' does it just fine. Jstty saneCtrl-J to restore the con- from adding new users (or changing ex- sole (which it did). But this command isting ones) on my system, now that the SYSTEM V LACKS JOB CONTROL is neither elegant nor intuitive, which 'tcb' is corrupted. Berkeley Unix has the ability to suspend means that it is a potential problem for the process that you are running and non-gurus. TWO COMPILERS FOR FLEXIBILITY return control to the shell, restart a sus- The Unix/386 development system comes pended process, or start up a new pro- SECURITY CAN BE DANGEROUS with two C compilers: Microsoft's com- A friend at Wang Laboratories described piler (named 'cc') and the AT&T System C2 security under Unix as "running with V compiler (named 'rcc'). a loaded gun pointed at your head." For The Microsoft compiler generates example, if the system discovers that an Xenix-format object files that are A friend at unauthorized change has been made to automatically converted to Unix COFF the password file, it will assume that the (Common Object Format Files) through Wang Laboratories system has been compromised and not a program called 'cvtomf. There are sev- let anybody log in. eral bugs in the included 'cvtomf that described C2 security Editing the password file, changing a prevent it from converting large object user's login shell, and other functions files with debugging information. How- must be done through the new system ever, SCO was happy to send me a fixed under Unix as administration shell, 'sysadmsh'. Unfor- version of 'cvtomf. tunately, 'sysadmsh' sometimes leaves I used both cc and rcc to compile the "running with a the trusted computing base files incon- Free Software Foundation's program- sistent with the password and group files. mer's editor, 'gnuemacs', and the FSF's loaded gun pointed I didn't believe my friend until I tried to C compiler, 'gcc'. Generally, rcc emitted add a new account to my system on the code that was smaller and faster than cc. morning I was finishing this review. I got (gcc's code was smaller and faster yet. at your head." messages telling me the file control data- Unfortunately, since gcc requires include base was inconsistent. files in order to operate, you must pur- cess. The only limit on the number of processes is the system-wide process limit. System V doesn't provide this. In- stead SCO implements a travesty of pro- f you want to ask SCO for technical support after you've gotten your Unix up and cess control abstraction called the Shell running, be warned that you'll have to pay for it. Layer Manager ('shl'), which allows the "We sell our software through anetwork of distributors, resellers, and. VARP,-:. :. user to spawn multiple shells; each shell, says Jeff Hill, SCO's manager of services marketing. "One of the things that we feel is in turn, is used to run a single user very important is that the resellers and VARS who sell our software to end users program.
Load more

Recommended publications
  • Xenix* 286 Installation and Configuration Guide
    XENIX* 286 INSTALLATION AND CONFIGURATION GUIDE *XENIX is a trademark of Microsoft Corporation. Copyright@ 1984, Intel Corporation Intel Corporation, 3065 Bowers Avenue. Santa Clara, California 95051 Order Number: 174386-001 XENIX* 286 INSTALLATION AND CONFIGURATION GUIDE Order Number: 174386-001 *XENIX is a trademark of Microsoft Corporation Copyright @ 1984 Intel Corporation I Intel Corporation, 3065 Bowers Avenue, Santa Clara, California 95051 I The information in this document is subject to change without notice. Intel Corporation makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Intel Corporation assumes no responsibility for any errors that may appear in this document. Intel Corporation makes no commitment to update or to keep current the information contained in this document. Intel Corporation assumes no responsibility for the use of any circuitry other than circuitry embodied in an Intel product. No other circuit patent licenses are implied. Intel software products are copyrighted by and shall remain the property oflntel Corporation. Use, duplication or disclosure is subject to restrictions stated in Intel's software license, or as defined in ASPR 7-104.9 (a) (9). No part of this document may be copied or reproduced in any form or by any means without prior written consent of Intel Corporation. The following are trademarks of Intel Corporation and its affiliates and may be used only to identify Intel products: BITBUS im iRMX OpenNET COMMputer iMDDX iSBC Plug-A-Bubble CREDIT iMMX iSBX PROMPT I Data Pipeline Insite iSDM Promware Genius intel iSXM QUEST t::t.
    [Show full text]
  • Caldera Systems to Acquire Sco Server Software
    CALDERA SYSTEMS TO ACQUIRE SCO SERVER SOFTWARE AND PROFESSIONAL SERVICESDIVISIONS, PROVIDING WORLD'S LARGEST LINUX /UNIX CHANNEL Submitted by: Archetype (Text100) Wednesday, 2 August 2000 Offers First Open Internet Platform, Embracing Open Access to Linux and UNIX Technologies OREM, UT - August 2, 2000 - Caldera Systems, Inc., (Nasdaq: CALD), a "Linux for Business" leader and The Santa Cruz Operation, Inc., (SCO) (Nasdaq: SCOC), the world's leading provider of UNIX operating systems, today announced that Caldera Systems has entered into an agreement to acquire the SCO Server Software Division and the Professional Services Division. The Professional Services Division will operate as a separate business unit of Caldera, to provide services to meet the Internet and eBusiness infrastructure needs of customers. The new company will offer the industry's first comprehensive Open Internet Platform (OIP) combining Linux and UNIX server solutions and services globally. The OIP provides commercial customers and developers with a single platform that can scale from the thinnest of clients to the clustering needs of the largest data center. The Open Internet Platform combines the robust scalability of the UNIX system with the low-cost, developer-accepted Linux operating system. The products, solutions, and services developed for the Open Internet Platform will be available through more than 15,000 partners worldwide. Details of the Agreement Caldera Systems, Inc. will form a new holding company, Caldera, Inc., to acquire assets from the SCO Server Software Division plus the SCO Professional Services Division, including a highly skilled workforce, products and channel resources. Caldera, Inc. will have exclusive distribution rights for the SCO OpenServer product line, and is fully committed to servicing and supporting the SCO OpenServer customer base.
    [Show full text]
  • SYSTEM V RELEASE 4 Migration Guide
    - ATlaT UN/~ SYSTEM V RELEASE 4 Migration Guide UNIX Software Operation Copyright 1990,1989,1988,1987,1986,1985,1984,1983 AT&T All Rights Reserved Printed In USA Published by Prentice-Hall, Inc. A Division of Simon & Schuster Englewood Cliffs, New Jersey 07632 No part of this publication may be reproduced or transmitted in any form or by any means-graphic, electronic, electrical, mechanical, or chemical, including photocopying, recording in any medium, tap­ ing, by any computer or information storage and retrieval systems, etc., without prior permissions in writing from AT&T. IMPORTANT NOTE TO USERS While every effort has been made to ensure the accuracy of all information in this document, AT&T assumes no liability to any party for any loss or damage caused by errors or omissions or by state­ ments of any kind in this document, its updates, supplements, or special editions, whether such er­ rors are omissions or statements resulting from negligence, accident, or any other cause. AT&T furth­ er assumes no liability arising out of the application or use of any product or system described herein; nor any liability for incidental or consequential damages arising from the use of this docu­ ment. AT&T disclaims all warranties regarding the information contained herein, whether expressed, implied or statutory, including implied warranties of merchantability or fitness for a particular purpose. AT&T makes no representation that the interconnection of products in the manner described herein will not infringe on existing or future patent rights, nor do the descriptions contained herein imply the granting or license to make, use or sell equipment constructed in accordance with this description.
    [Show full text]
  • Marjn Norling November 2012
    Mar$n Norling November 2012 UNIX Lecture Goals • Goal 1: Know basic UNIX commands and their use from memory. • Goal 2: Know how to find informaon on more advanced UNIX commands and their use. • Goal 3: Understand the basics of regular expression paerns. • Goal 4: Know the basic loops and condi$onals for shell scrip$ng and understand how to use them. UNIX Schedule Thursday Friday 09.00-09.45 UNIX introduc$on 09.00-09.45 Bash Scrip$ng 10.00-10.45 UNIX basics 10.00-10.45 Tutorial: Bash scrip$ng 11.00-12.00 Redirects to regexp 11.00-12.00 Tips & Quesons 12.00-13.00 Lunch 12.00-13.00 Lunch 13.00-16.00 Tutorial: Basics 13.00-16.00 Tutorial: finishing up UNIX HISTORY UNIX History • 1969 – First Version of UNIX developed at Bell Labs by AT&T • 1975 – UNIX 6, the first to be widely available outside Bell Labs. The first “Berkeley So]ware Distribu$on” (BSD) is released. • 1989 – UNIX System V, the last tradi$onal UNIX version. • 1991 – Linus Torvalds begin developing Linux. “UNIX-like” • Today – UNIX itself, what’s now called “tradi$onal UNIX” is not used, except by enthusiasts. • There are many “UNIX-like” systems (also known as *nix or UN*X) that are similar to UNIX while not conforming to the Single UNIX Specificaon. • In fact, most operang systems today except windows are “UNIX like”. Single UNIX Specificaon (SUS) • Developed and maintained by the Aus$n Group, based on earlier work by the IEee and The Open Group.
    [Show full text]
  • The Santa Cruz Operation, Inc. Products and Services
    THE SANTA CRUZ OPERATION, INC. PRODUCTS AND SERVICES PRICE LIST December 1984 sea 500 CHESTNUT STREET, P.O. BOX 1900, SANTA CRUZ, CA 95061 • (408) 425-7222 • TWX: 910-598-4510 sca SACZ TABLE of CONTENTS IBM PC, PC XT, PC Compatibles and Apple Lisa 2 1 Tandy Machines 2 AT&T Machines 3 Standard Software Products 4 DEC Systems 5 Macro Assemblers 6 SoftCare Support Services 7 The UNIX System Tutorials 8 Documentation 9 © 1984 The Santa Cruz Operation. Inc. UNIX is a trademark of AT&T Bell Laboratories. DEC is a registered trademark and PDP. Professional 350 and VAX are trademarb of Digital Equipment Corporation. IBM is a registered trademark of In:ternational Business Machines Corporation. Apple and Lisa are registered trademarks of Apple Computer. Inc. LEVEL II COBOL. FORM5-2 and ANIMATOR are trademarks of Micro Focus. Ltd. Informix is a registered trademark and Ace. ~rfonn. and C-ISAM are trademarks of Relational Database Systems. Inc. Lyrix is a trademark of The Santa Cruz Operation. Inc. Multiplan and XENIX are registered trademarks of Microsoft Corporation. ZOO, Z8001 and ZS002are registered trademarks of Zilog. Inc. Audiodigital is a trademark of User Training Corporation. TR5-80 is a registered trademark of Tandy Corporation. Sunol is a trademark of Sunol Corporation. Tecmar and MassFile are trademarks of Tecmar. Inc. Priam is a registered trademark and DataTower is a trademark of Priam Corporation. Tallgrass is a registered trademark of Tallgrass Technologies Corporation. IOMEGA is a trademark of IOMEGA Corporation. SoftCare is a service mark of The Santa Cruz Operation. Inc. seo PRODUCTS AND SERVICES PRICE LIST for the IBM PC.
    [Show full text]
  • C168H/PCI 8-Port RS-232 PCI Boards
    Multiport Serial Boards C168H/PCI 8-port RS-232 PCI boards › 8-port RS-232 high-speed communication board › Compact PCI board size › Versatile OS driver support › Various connection options › Data transmission speed up to 921.6 Kbps › On-chip hardware flow control › Easy configuration without switches or jumpers › Convenient connection cables Overview The Smartio C168H/PCI Series allows you to install additional RS- And C168H/PCI’s versatile OS driver support truly fulfills the needs 232 serial communication ports on your PC by providing 8 serial of our customers’ varied applications. This product is available for ports per board for connecting all types of serial devices, including use on either a PCI bus, with both types offering a reliable and high terminals, modems, printers, data acquisition equipment, and more. performance solution for serial multiport communications. Specifications Hardware DOS, AT&T UNIV SVR4.2, MITUX DVR4.2, UnixWare SVR4.2, I/O Controller: 16C550C or compatible x 8 UnixWare7, SCO OpenServer, SCO Unix, SCO XENIX, QNX 4.2x, Bus: PCI ver. 2.1 (32-bit) FreeBSD Serial Interface Physical Charateristics Maximum No. of Ports: 32 (4 boards) Dimensions: 123 x 100 mm (W x D) Performance Environmental Limits Speed: 50 bps to 921.6 Kbps Operating Temperature: 0 to 55°C Serial Communication Parameters Storage Temperature: -20 to 85°C Data Bits: 5, 6, 7, 8 Ambient Relative Humidity: 5 to 95% RH Stop Bits: 1, 1.5, 2 Standards and Certifications Parity: None, Even, Odd, Space, Mark Regulatory Approvals: FCC, CE I/O Address:
    [Show full text]
  • UNIX System Services Z/OS Version 1 Release 7 Implementation
    Front cover UNIX System Services z/OS Version 1 Release 7 Implementation z/OS UNIX overview z/OS UNIX setup z/OS UNIX usage Paul Rogers Theodore Antoff Patrick Bruinsma Paul-Robert Hering Lutz Kühner Neil O’Connor Lívio Sousa ibm.com/redbooks International Technical Support Organization UNIX System Services z/OS Version 1 Release 7 Implementation March 2006 SG24-7035-01 Note: Before using this information and the product it supports, read the information in “Notices” on page xiii. Second Edition (March 2006) This edition applies to Version 1 Release 7 of z/OS (5637-A01), and Version 1, Release 7 of z/OS.e (5655-G52), and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 2003, 2006. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . xiii Trademarks . xiv Preface . .xv The team that wrote this redbook. .xv Become a published author . xvi Comments welcome. xvii Chapter 1. UNIX overview. 1 1.1 UNIX fundamentals . 2 1.1.1 UNIX objectives . 2 1.1.2 What people like about UNIX . 2 1.1.3 What people don’t like about UNIX . 3 1.1.4 UNIX operating system . 3 1.1.5 UNIX file system . 4 1.1.6 Parameter files . 6 1.1.7 Daemons. 6 1.1.8 Accessing UNIX . 6 1.1.9 UNIX standards. 7 1.1.10 MVS and UNIX functional comparison . 8 1.2 z/OS UNIX System Services fundamentals .
    [Show full text]
  • History of Unix.Pdf
    History of Unix In order to define UNIX, it helps to look at its history. In 1969, Ken Thompson, Dennis Ritchie and others started work on what was to become UNIX on a "little-used PDP-7 in a corner" at AT&T Bell Labs. For ten years, the development of UNIX proceeded at AT&T in numbered versions. V4 (1974) was re-written in C -- a major milestone for the operating system's portability among different systems. V6 (1975) was the first to become available outside Bell Labs -- it became the basis of the first version of UNIX developed at the University of California Berkeley. Bell Labs continued work on UNIX into the 1980s, culminating in the release of System V (as in "five," not the letter) in 1983 and System V, Release 4 (abbreviated SVR4) in 1989. Meanwhile, programmers at the University of California hacked mightily on the source code AT&T had released, leading to many a master thesis. The Berkeley Standard Distribution (BSD) became a second major variant of "UNIX." It was widely deployed in both university and corporate computing environments starting with the release of BSD 4.2 in 1984. Some of its features were incorporated into SVR4. As the 1990s opened, AT&T's source code licensing had created a flourishing market for hundreds of UNIX variants by different manufacturers. AT&T sold its UNIX business to Novell in 1993, and Novell sold it to the Santa Cruz Operation two years later. In the meantime, the UNIX trademark had been passed to the X/Open consortium, which eventually merged to form The Open Group.1 While the stewardship of UNIX was passing from entity to entity, several long- running development efforts started bearing fruit.
    [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]
  • Who Owns UNIX? Caldera Paid Just $36 Million for Two Divisions Of
    Who Owns UNIX? Caldera paid just $36 million for two divisions of the Santa Cruz Operation and their assets1. They claim that billions have been spent developing UNIX, without explaining that most of that funding was provided by the general public. SCO has even threatened Government users with litigation unless they purchase the “SCO Intellectual Property Licenses”.2 Unix was collaboratively developed by it's end-users (the public) and Bell Labs as an essential public facility for many years. In just one example, AT&T licensed-back publicly funded Berkeley Software Distribution (BSD) enhancements for use in their products as early as 1979. By 1993, The Regents of California claimed that as much as 50% of USL's System VR4 source code had been developed by Berkeley.3 The Berkeley CSRG was part of a public trust whose source code was developed with funding supplied via gifts, grants, or contracts provided by the NSF, DARPA, DOE, NASA and others4. Under the terms of a 1956 DOJ Consent Decree, and the FCC Computer Inquiry I and II regulations, neither AT&T nor Western Electric could legally market UNIX as a product or service. AT&T was restricted to the common carrier business. UNIX was offered "as is" to universities and businesses with no technical support or bug fixes. Organizations could obtain a copy of the UNIX source code and a royalty-free license to produce derivative works by paying a $99 administration fee. Under the decree, Bell Labs was limited to doing research for AT&T or contract work for the federal government.
    [Show full text]
  • Linux? POSIX? GNU/Linux? What Are They? a Short History of POSIX (Unix-Like) Operating Systems
    Unix? GNU? Linux? POSIX? GNU/Linux? What are they? A short history of POSIX (Unix-like) operating systems image from gnu.org Mohammad Akhlaghi Instituto de Astrof´ısicade Canarias (IAC), Tenerife, Spain (founder of GNU Astronomy Utilities) Most recent slides available in link below (this PDF is built from Git commit d658621): http://akhlaghi.org/pdf/posix-family.pdf Understanding the relation between the POSIX/Unix family can be confusing Image from shutterstock.com The big bang! In the beginning there was ... In the beginning there was ... The big bang! Fast forward to 20th century... Early computer hardware came with its custom OS (shown here: PDP-7, announced in 1964) Fast forward to the 20th century... (∼ 1970s) I AT&T had a Monopoly on USA telecommunications. I So, it had a lot of money for exciting research! I Laser I CCD I The Transistor I Radio astronomy (Janskey@Bell Labs) I Cosmic Microwave Background (Penzias@Bell Labs) I etc... I One of them was the Unix operating system: I Designed to run on different hardware. I C programming language was designed for writing Unix. I To keep the monopoly, AT&T wasn't allowed to profit from its other research products... ... so it gave out Unix for free (including source). Unix was designed to be modular, image from an AT&T promotional video in 1982 https://www.youtube.com/watch?v=tc4ROCJYbm0 User interface was only on the command-line (image from late 80s). Image from stevenrosenberg.net. AT&T lost its monopoly in 1982. Bell labs started to ask for license from Unix users.
    [Show full text]
  • Chapter 4 Introduction to UNIX Systems Programming
    Chapter 4 Introduction to UNIX Systems Programming 4.1 Introduction Last chapter covered how to use UNIX from from a shell program using UNIX commands. These commands are programs that are written in C that interact with the UNIX environment using functions called Systems Calls. This chapter covers this Systems Calls and how to use them inside a program. 4.2 What is an Operating System An Operating System is a program that sits between the hardware and the application programs. Like any other program it has a main() function and it is built like any other program with a compiler and a linker. However it is built with some special parameters so the starting address is the boot address where the CPU will jump to start the operating system when the system boots. Draft An operating system typically offers the following functionality: ● Multitasking The Operating System will allow multiple programs to run simultaneously in the same computer. The Operating System will schedule the programs in the multiple processors of the computer even when the number of running programs exceeds the number of processors or cores. ● Multiuser The Operating System will allow multiple users to use simultaneously in the same computer. ● File system © 2014 Gustavo Rodriguez-Rivera and Justin Ennen,Introduction to Systems Programming: a Hands-on Approach (V2014-10-27) (systemsprogrammingbook.com) It allows to store files in disk or other media. ● Networking It gives access to the local network and internet ● Window System It provides a Graphical User Interface ● Standard Programs It also includes programs such as file utilities, task manager, editors, compilers, web browser, etc.
    [Show full text]