DOCSLIB.ORG

On the Feasibility of Providing Affordable Broadband Services

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
On the Feasibility of Providing Affordable Broadband Services On the Feasibility of Providing Affordable Broadband Services using Backhaul in TV White Spaces Submitted in partial fulfillment of the requirements of the degrees of Master of Technology by Gaurang Naik Roll No. 123079009 Supervisors: Prof. Abhay Karandikar & Prof. Animesh Kumar DEPARTMENT OF ELECTRICAL ENGINEERING INDIAN INSTITUTE OF TECHNOLOGY BOMBAY JUNE, 2015 Approval Sheet This thesis entitled On the Feasibility of Providing Affordable Broadband Ser- vices using Backhaul in TV White Spaces by Gaurang Naik (Roll No. 123079009) is approved for the degree of Master of Technology in Communication and Signal Processing. Examiners Supervisors Chairperson Date: Place: Declaration I declare that this written submission represents my ideas in my own words and where others' ideas or words have been included, I have adequately cited and referenced the original sources. I also declare that I have adhered to all principles of academic honesty and integrity and have not misrepresented or fabricated or falsified any idea/data/fac- t/source in my submission. I understand that any violation of the above will be cause for disciplinary action by the Institute and can also evoke penal action from the sources which have thus not been properly cited or from whom proper permission has not been taken when needed. Gaurang Naik Date: Roll No: 123079009 To Amma & Anna Acknowledgements I would like to express my sincere gratitude to my supervisors, Prof. Abhay Karandikar and Prof. Animesh Kumar for the invaluable guidance they have provided over the last three years. The discussions I have had with them have helped me give a definite direc- tion to my thought process. Their enthusiasm has been a source of constant motivation for me throughout my stay at IIT Bombay. I will always be grateful to Karandikar Sir for the innumerable opportunities given to me to interact with some of the most intellectual people I have come across. A large part of the work done in this thesis is collaborated with my friend and colleague Sudesh Singhal. We have been working on this project from day-1 at IIT Bombay, and I would like to sincerely thank him for the support he has provided throughout. I have had few of the best moments in the InfoNet Lab and the Wireless Networks Lab with all the lab members. I would like to specially thank Soumik Ghosh and Rajeev Kumar for the time we spent during the project deployment at Palghar and in the lab. I am also thankful to Sonal, Dhanashree, Aditya Sir, Sangeeta Ma'am, Shubhada Ma'am and Tusharika for helping me on innumerable occassions in the InfoNet Lab. I would simply not have been here had it not been for my parents' support, love and motivation. I am extremely fortunate to be their son, and will always remain indebted to them. Their immense faith in me made it possible for me to come to IIT Bombay, and survive here for three years. I also thank Priyanka, my partner in life and my best friend for all the support she has given me. Without my parents and Priyanka, none of what I am today would have been possible. I dedicate this thesis to them! Finally, I would like to thank my dearest friends Kumar, Venkhat, Shrikant, Pravjyot, Shashi, Navneet, Mayank and Naireeta for making my stay at IIT Bombay one of the most wonderful and enriching experience in life. All of you turned the Wireless Networks Lab into my home away from home. Thank you all! June 3, 2015 Gaurang Naik Abstract Licensed but unutilized television (TV) band spectrum is called as TV white space in the literature. Ultra high frequency (UHF) TV band spectrum has very good wireless radio propagation characteristics. Even though research issues related to TV White Spaces started emerging only after the FCC regulations in 2009, several issues have been identified and studied extensively in literature. These research problems range right from estimating the available White Space in TV band and proposing ideas for interference avoidance to predicting the use cases of TV White Space operations and proposing solutions for the same. Most of the research pertaining to TV White Spaces started from United States, Japan and European countries. In this report, some key questions regarding TV White Space operations in India have been raised and some solutions have been offered. We first look at the global scenario for usage of TV White Space. Regulations and study of quantitative analysis of TV White Space in different countries have been studied. TV band utilization in India is much different and interesting as compared to that in other countries. Owing to the presence of a single TV broadcaster in India, much of the TV band remains underutilized in India. This calls for applications different from those being studied in other countries of the world. We look at one such application | affordable provision of broadband services, especially in the rural areas. The implementation and planning details of a pilot test-bed in the Palghar district of Maharashtra state have been outlined, and some preliminary experimental results have been presented. In any wireless network using TV white spaces (either for backhaul or access), a geo- location database can be used for the protection of the terrestrial TV broadcast receivers, and the coexistence of secondary devices. To the best of our knowledge, though TV White Space calculations are available, an active online database does not exist for India. The development of the first TVWS database for India is detailed and is released for public i access. A standardized protocol to access the TV White Space database on a readily available hardware platform is implemented. A hardware prototype, which is capable of querying the TV White Space database and operating in the TV band without causing harmful interference to the TV receivers in UHF TV bands, is developed. The source code of our implementation has been released under the GNU general public license version 2.0. ii Contents Abstract i 1 Introduction1 1.1 Present Status of Broadband in India....................1 1.1.1 Rural Broadband Challenges in India................1 1.1.2 National Optical Fiber Network Plan................2 1.1.3 Middle Mile/ Last Mile Problem...................2 1.2 TV White Space - A Potential Solution to the Rural Broadband Problem3 1.2.1 Primary and Secondary Users....................4 1.2.2 TV White Spaces and Rural Broadband..............4 2 TV White Space Around the World6 2.1 TV White Space in United States......................6 2.1.1 Regulations..............................6 2.1.2 Spectrum Sensing...........................8 2.1.3 Geolocation Databases........................8 2.1.4 Beacon.................................9 2.1.5 Availability of TV White Space in United States.......... 10 2.2 TV White Space in United Kingdom.................... 10 2.2.1 Regulations.............................. 10 2.2.2 Availability of TV White Space in United Kingdom........ 13 2.3 TV White Space in Japan.......................... 14 2.3.1 Regulations.............................. 14 2.3.2 Availability of TV White Space in Japan.............. 15 2.4 TV White Space in Europe......................... 15 2.4.1 Regulations.............................. 15 2.5 TV White Space in India........................... 16 2.5.1 How is the Indian Situation Different?............... 17 3 Test-bed for Affordable Broadband in India using Backhaul in TV White Space 19 3.1 Proposed Solution for Rural Broadband and Associated TV White Space Backhaul.................................... 19 3.1.1 Architecture for TV White Space Based Network Operations in India 21 3.1.2 Architecture for Database Assisted TV White Space Operations in India.................................. 22 3.1.3 Regulatory Approach for the Use of TV White Space in India.. 23 3.1.4 Details of the Proposed Test-bed.................. 24 iv 3.1.5 Selection of Sites for Test-bed.................... 24 3.2 Topographic Details of Wireless Nodes................... 26 3.3 Equipment for TV White Space....................... 28 3.3.1 Available Products/Prototypes................... 30 3.4 IP Connectivity Details............................ 31 3.4.1 Private IP-addresses to Enable Networking within the Wireless Lo- cal Area Network........................... 31 3.5 Experimental Results............................. 34 4 Implementation of Protocol to Access White Space (PAWS) Database on OpenWrt platform 43 4.1 OpenPAWS: Protocol Details........................ 44 4.1.1 Format of PAWS Messages...................... 46 4.2 Implementation Architecture......................... 47 4.2.1 TV White Space Database for India................. 48 4.3 Experimental Results............................. 52 5 Conclusions 56 5.1 Summary................................... 56 5.2 Future Work.................................. 57 5.2.1 Minimum Amount of Spectrum Needed for Target Quality of Service 57 5.2.2 Frequency of Operation and Coexistence Study with Adjacent Band Technologies.............................. 57 5.2.3 Spectral Mask and Out-of-band Emissions............. 57 5.2.4 Element Management System and Control Server......... 58 5.2.5 Implementation of Scheduling Algorithms, Extensions of Frottle for Multi-hop, Interference Management................ 58 5.2.6 Technology to be Used for Backhaul Network........... 58 5.2.7 Study of Coexistence in Multi-operator Environment....... 58 5.2.8 Study of Propagation Model in the 470-585Hz Band in the Indian Context................................ 59 Appendix A Compilation of RouterBoard 433AH in Bridged AP and Routed AP/Client modes 61 A.1 Make kernel and rootfs files for the desired OS............... 61 A.2 Flash kernel and rootfs files into the RouterBoard............. 63 A.3 Configure relevant files and install selected tools.............. 65 Appendix B Compilation of OpenWrt Attitude Adjustment 12.09 from source-code 68 B.1 Operation mode of RouterBoard 433AH.................. 69 B.1.1 Bridged AP.............................. 69 B.1.2 Routed AP.............................. 70 Publications 83 v List of Figures 1.1 Number of Habitat clusters in India and share of population.......3 1.2 The concept of TV White Space.
Load more

Recommended publications
  • The Strange Birth and Long Life of Unix - IEEE Spectrum Page 1 of 6
    The Strange Birth and Long Life of Unix - IEEE Spectrum Page 1 of 6 COMPUTING / SOFTWARE FEATURE The Strange Birth and Long Life of Unix The classic operating system turns 40, and its progeny abound By WARREN TOOMEY / DECEMBER 2011 They say that when one door closes on you, another opens. People generally offer this bit of wisdom just to lend some solace after a misfortune. But sometimes it's actually true. It certainly was for Ken Thompson and the late Dennis Ritchie, two of the greats of 20th-century information technology, when they created the Unix operating system, now considered one of the most inspiring and influential pieces of software ever written. A door had slammed shut for Thompson and Ritchie in March of 1969, when their employer, the American Telephone & Telegraph Co., withdrew from a collaborative project with the Photo: Alcatel-Lucent Massachusetts Institute of KEY FIGURES: Ken Thompson [seated] types as Dennis Ritchie looks on in 1972, shortly Technology and General Electric after they and their Bell Labs colleagues invented Unix. to create an interactive time- sharing system called Multics, which stood for "Multiplexed Information and Computing Service." Time-sharing, a technique that lets multiple people use a single computer simultaneously, had been invented only a decade earlier. Multics was to combine time-sharing with other technological advances of the era, allowing users to phone a computer from remote terminals and then read e -mail, edit documents, run calculations, and so forth. It was to be a great leap forward from the way computers were mostly being used, with people tediously preparing and submitting batch jobs on punch cards to be run one by one.
    [Show full text]
  • The Strange Birth and Long Life of Unix - IEEE Spectrum
    The Strange Birth and Long Life of Unix - IEEE Spectrum http://spectrum.ieee.org/computing/software/the-strange-birth-and-long-li... COMPUTING / SOFTWARE FEATURE The Strange Birth and Long Life of Unix The classic operating system turns 40, and its progeny abound By WARREN TOOMEY / DECEMBER 2011 They say that when one door closes on you, another opens. People generally offer this bit of wisdom just to lend some solace after a misfortune. But sometimes it's actually true. It certainly was for Ken Thompson and the late Dennis Ritchie, two of the greats of 20th-century information technology, when they created the Unix operating system, now considered one of the most inspiring and influential pieces of software ever written. A door had slammed shut for Thompson and Ritchie in March of 1969, when their employer, the American Telephone & Telegraph Co., withdrew from a collaborative project with the Photo: Alcatel-Lucent Massachusetts Institute of KEY FIGURES: Ken Thompson [seated] types as Dennis Ritchie looks on in 1972, shortly Technology and General Electric after they and their Bell Labs colleagues invented Unix. to create an interactive time-sharing system called Multics, which stood for "Multiplexed Information and Computing Service." Time-sharing, a technique that lets multiple people use a single computer simultaneously, had been invented only a decade earlier. Multics was to combine time-sharing with other technological advances of the era, allowing users to phone a computer from remote terminals and then read e-mail, edit documents, run calculations, and so forth. It was to be a great leap forward from the way computers were mostly being used, with people tediously preparing and submitting batch jobs on punch cards to be run one by one.
    [Show full text]
  • Introduction to UNIX What Is UNIX? Why UNIX? Brief History of UNIX Early UNIX History UNIX Variants
    What is UNIX? A modern computer operating system Introduction to UNIX Operating system: “a program that acts as an intermediary between a user of the computer and the computer hardware” CS 2204 Software that manages your computer’s resources (files, programs, disks, network, …) Class meeting 1 e.g. Windows, MacOS Modern: features for stability, flexibility, multiple users and programs, configurability, etc. *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003. (C) Doug Bowman, Virginia Tech, 2001- 2 Why UNIX? Brief history of UNIX Used in many scientific and industrial settings Ken Thompson & Dennis Richie Huge number of free and well-written originally developed the earliest software programs versions of UNIX at Bell Labs for Open-source OS internal use in 1970s Internet servers and services run on UNIX Borrowed best ideas from other Oss Largely hardware-independent Meant for programmers and computer Based on standards experts Meant to run on “mini computers” (C) Doug Bowman, Virginia Tech, 2001- 3 (C) Doug Bowman, Virginia Tech, 2001- 4 Early UNIX History UNIX variants Thompson also rewrote the operating system Two main threads of development: in high level language of his own design Berkeley software distribution (BSD) which he called B. Unix System Laboratories System V Sun: SunOS, Solaris The B language lacked many features and Ritchie decided to design a successor to B GNU: Linux (many flavors) which he called C. SGI: Irix They then rewrote UNIX in the C FreeBSD programming language to aid in portability. Hewlett-Packard: HP-UX Apple: OS X (Darwin) … (C) Doug Bowman, Virginia Tech, 2001- 5 (C) Doug Bowman, Virginia Tech, 2001- 6 1 Layers in the UNIX System UNIX Structure User Interface The kernel is the core of the UNIX Library Interface Users system, controlling the system Standard Utility Programs hardware and performing various low- (shell, editors, compilers, etc.) System Interface calls User Mode level functions.
    [Show full text]
  • LINCS Server Release 1.0 Administration
    LINCS Server Release 1.0 Administration 585-313-507 Comcode 108599200 October 1999 Issue 2 Copyright © 1999 by Lucent Technologies. All rights reserved. For trademark, regulatory compliance, and related legal information, see the copyright and legal notices section of this document. Copyright and legal notices Copyright Copyright © 1999 by Lucent Technologies. All rights reserved. Printed in the USA. This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts or licensing, without the express written consent of the Business Communications Systems (BCS) Global Learning Solutions organization and the business management owner of the material. Acknowledgment This document was prepared by the Global Learning Solutions organization of the BCS division of Lucent Technologies. Offices are located in Denver CO, Columbus OH, Middletown NJ, and Basking Ridge NJ, USA. LINCS Server Administration 585-313-507 Issue 2 October 1999 iii Copyright and legal notices Trademarks Lucent Technologies has made every effort to supply the following trademark information about company names, products, and services mentioned in the LINCS server documentation library: • Adobe Systems, Inc. — Trademarks: Adobe, Acrobat. • Enhanced Software Technologies, Inc. — Trademark: Quickstart. • Equinox Systems, Inc — Registered trademark: Equinox • Hewlett Packard Corporation — Registered trademarks: Hewlett-Packard and HP • Intel Corporation — Registered trademarks: Pentium. • International Business Machines Corporation — Registered trademarks: IBM, VTAM. • Lucent Technologies — Registered trademarks: 4ESS, 5ESS, AUDIX, CONVERSANT, DEFINITY, Voice Power. Trademarks: FlexWord, Intuity, Lucent. • Microsoft Corporation — Registered trademarks: Excel, Internet Explorer, Microsoft, MS, MS-DOS, Windows, Windows NT.
    [Show full text]
  • Supply Chain Risk Management (SCRM) Task Force (TF) Threat Evaluation Working Group: Threat Scenarios, CISA, February 2020 TLP: WHITE
    Appendix 1 Information And Communications Technology (ICT) Supply Chain Risk Management (SCRM) Task Force (TF) Threat Evaluation Working Group: Threat Scenarios, CISA, February 2020 TLP: WHITE CYBERSECURITY AND INFRASTRUCTURE SECURITY AGENCY INFORMATION AND COMMUNICATIONS TECHNOLOGY SUPPLY CHAIN RISK MANAGEMENT TASK FORCE Threat Evaluation Working Group: Threat Scenarios February 2020 TLP: WHITE TLP: WHITE This page is intentionally left blank. CYBERSECURITY AND INFRASTRUCTURE SECURITY AGENCY TLP: WHITE ii TLP: WHITE EXECUTIVE SUMMARY Cyber Supply Chain Risk Management (C-SCRM) is the process of identifying, assessing, preventing, and mitigating the risks associated with the distributed and interconnected nature of Information and Communications Technology (ICT) (including the Internet of Things) product and service supply chains. C-SCRM covers the entire life cycle of ICT, and encompasses hardware, software, and information assurance, along with traditional supply chain management and supply chain security considerations. In October 2018, the Cybersecurity and Infrastructure Security Agency (CISA) launched the ICT Supply Chain Risk Management Task Force, a public-private partnership to provide advice and recommendations to CISA and its stakeholders on means for assessing and managing risks associated with the ICT supply chain. Working Group 2 (WG2), Threat Evaluation, was established for the purpose of the identification of processes and criteria for threat-based evaluation of ICT suppliers, products, and services. WG2 focused on threat evaluation as opposed to the more comprehensive task of risk assessment which considers threats as well as an organization’s tolerance for risk, the criticality of the specific asset or business/mission purpose, and the impact of exploitation of specific vulnerabilities that might be exploited by an external threat.
    [Show full text]
  • Avaya Definity ECS Whats New in R9.0.Pdf
    DEFINITY® Enterprise Communications Server What’s New for Release 9 555-233-766 Issue 2 February 2001 Copyright 2001 Avaya Inc. All rights reserved. For trademark, regulatory compliance, and related legal information, see the copyright and legal notices section of this document. Copyright and legal notices Copyright Copyright 2001 by Avaya Inc. All rights reserved. This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Avaya), except in accordance with applicable agreements, contracts or licensing, without the express written consent of the BCS Product Publications organization and the business management owner of the material. This document was prepared by the Product Publications department of the Business Communications Systems division of Avaya. Offices are located in Denver CO, Columbus OH, Middletown NJ, and Basking Ridge NJ, USA. DEFINITY ECS What’s New for Release 9 555-233-766 Issue 2 February 2001 iii Copyright and legal notices Trademarks DEFINITY, AUDIX, CONVERSANT, elemedia, SABLIME, Talkbak, Terranova, WaveLAN, MERLIN, MERLIN LEGEND and GuestWorks are registered trademarks and 4ESS, 5ESS, Intuity, OneMeeting, OneVision, PacketStar, PathStar, ProLogix, Lucent, Lucent Technologies, and the Lucent Technologies logo are trademarks of Lucent Technologies. Pentium is a registered trademark of Intel Corporation. Microsoft, Windows, and Windows NT are registered trademarks and Video for Windows is a trademark of Microsoft Corporation. UNIX is a registered trademark of UNIX System Laboratories, Inc., a wholly-owned subsidiary of Novell, Inc. X Window System is a trademark and product of the Massachusetts Institute of Technology.
    [Show full text]
  • A Brief History of Unix
    A Brief History of Unix Tom Ryder [email protected] https://sanctum.geek.nz/ I Love Unix ∴ I Love Linux ● When I started using Linux, I was impressed because of the ethics behind it. ● I loved the idea that an operating system could be both free to customise, and free of charge. – Being a cash-strapped student helped a lot, too. ● As my experience grew, I came to appreciate the design behind it. ● And the design is UNIX. ● Linux isn’t a perfect Unix, but it has all the really important bits. What do we actually mean? ● We’re referring to the Unix family of operating systems. – Unix from Bell Labs (Research Unix) – GNU/Linux – Berkeley Software Distribution (BSD) Unix – Mac OS X – Minix (Intel loves it) – ...and many more Warning signs: 1/2 If your operating system shows many of the following symptoms, it may be a Unix: – Multi-user, multi-tasking – Hierarchical filesystem, with a single root – Devices represented as files – Streams of text everywhere as a user interface – “Formatless” files ● Data is just data: streams of bytes saved in sequence ● There isn’t a “text file” attribute, for example Warning signs: 2/2 – Bourne-style shell with a “pipe”: ● $ program1 | program2 – “Shebangs” specifying file interpreters: ● #!/bin/sh – C programming language baked in everywhere – Classic programs: sh(1), awk(1), grep(1), sed(1) – Users with beards, long hair, glasses, and very strong opinions... Nobody saw it coming! “The number of Unix installations has grown to 10, with more expected.” — Ken Thompson and Dennis Ritchie (1972) ● Unix in some flavour is in servers, desktops, embedded software (including Intel’s management engine), mobile phones, network equipment, single-board computers..
    [Show full text]
  • Supplier, Products, and Services Threat Evaluation (To Include Impact Analysis and Mitigation) Version 3.0
    CYBERSECURITY AND INFRASTRUCTURE SECURITY AGENCY INFORMATION AND COMMUNICATIONS TECHNOLOGY SUPPLY CHAIN RISK MANAGEMENT TASK FORCE Threat Evaluation Working Group: Supplier, Products, and Services Threat Evaluation (to include Impact Analysis and Mitigation) Version 3.0 July 2021 This page is intentionally left blank. This latest report from the Threat Evaluation Working Group adds the assessment of Products and Executive Services to include impacts and mitigating controls to each of the Supplier Threat Scenarios Summary provided in the original version released in February 2020, and later augmented with impacts and mitigating controls in October 2020. These additional sections are included in Appendix C, Threat Scenarios, of this report. The Working Group (WG) chose to include these updates as a standalone report to benefit the audience without the need to include numerous references to the original reports. Cyber Supply Chain Risk Management (C-SCRM) is the process of identifying, assessing, preventing, and mitigating the risks associated with the distributed and interconnected nature of Information and Communications Technology (ICT) (including the Internet of Things [IoT]) product and service supply chains. C-SCRM covers the entire life cycle of ICT, and encompasses hardware, software, and information assurance, along with traditional supply chain management and supply chain security considerations. In October 2018, the Cybersecurity and Infrastructure Security Agency (CISA) launched the ICT Supply Chain Risk Management Task Force, a public-private partnership to provide advice and recommendations to CISA and its stakeholders on means for assessing and managing risks associated with the ICT supply chain. Working Group 2 (WG2), Threat Evaluation, was established for the purpose of the identification of processes and criteria for threat-based evaluation of ICT suppliers, products, and services.
    [Show full text]
  • An Overview of the Netware Operating System
    An Overview of the NetWare Operating System Drew Major Greg Minshall Kyle Powell Novell, Inc. Abstract The NetWare operating system is designed specifically to provide service to clients over a computer network. This design has resulted in a system that differs in several respects from more general-purpose operating systems. In addition to highlighting the design decisions that have led to these differences, this paper provides an overview of the NetWare operating system, with a detailed description of its kernel and its software-based approach to fault tolerance. 1. Introduction The NetWare operating system (NetWare OS) was originally designed in 1982-83 and has had a number of major changes over the intervening ten years, including converting the system from a Motorola 68000-based system to one based on the Intel 80x86 architecture. The most recent re-write of the NetWare OS, which occurred four years ago, resulted in an “open” system, in the sense of one in which independently developed programs could run. Major enhancements have occurred over the past two years, including the addition of an X.500-like directory system for the identification, location, and authentication of users and services. The philosophy has been to start as with as simple a design as possible and try to make it simpler as we gain experience and understand the problems better. The NetWare OS provides a reasonably complete runtime environment for programs ranging from multiprotocol routers to file servers to database servers to utility programs, and so forth. Because of the design tradeoffs made in the NetWare OS and the constraints those tradeoffs impose on the structure of programs developed to run on top of it, the NetWare OS is not suited to all applications.
    [Show full text]
  • MERLIN LEGEND Communications System Release 6.1 Installation
    MERLIN LEGEND® Communications System Release 6.1 Installation 555-661-140 Comcode 108198029 Issue 1 August 1998 Copyright © 1998, Lucent Technologies 555-661-140 All Rights Reserved Issue 1 Printed in USA August 1998 Copyright © 1998, Lucent Technologies 555-661-140 All Rights Reserved Issue 1 Printed in USA August 1998 Notice Every effort was made to ensure that the information in this book was complete and accurate at the time of printing. However, information is subject to change. See Appendix A, “Customer Support Information,” for important information. It follows Maintenance and Troubleshooting in this binder. Your Responsibility for Your System’s Security Toll fraud is the unauthorized use of your telecommunications system by an unauthorized party, for example, persons other than your company’s employees, agents, subcontractors, or persons working on your company’s behalf. Note that there may be a risk of toll fraud associated with your telecommunications system, and if toll fraud occurs, it can result in substantial additional charges for your telecommunications services. You and your system manager are responsible for the security of your system, such as programming and configuring your equipment to prevent unauthorized use. The system manager is also responsible for reading all installation, instruction, and system administration documents provided with this product in order to fully understand the features that can introduce risk of toll fraud and the steps that can be taken to reduce that risk. Lucent Technologies does not warrant that this product is immune from or will prevent unauthorized use of common-carrier telecommunication services or facilities accessed through or connected to it.
    [Show full text]
  • Applicationdec 433MP Software Installation Roadmap
    dt applicationDEC 433MP Software Installation Roadmap Order Number: EK–PS100–SR–001 February 1991 This document is a guide to installing software on the applicationDEC 433MP system. The Roadmap addresses the following software products: • SCO UNIX • SCO Open Desktop • SCO MPX • SCO VP/ix • Digital PS1XG–AA graphics configuration utilities Digital Equipment Corporation Maynard, Massachusetts First Printing, February 1991 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1991. The following are trademarks of Digital Equipment Corporation: applicationDEC, DEC, VAX DOCUMENT, and the DIGITAL logo. The following are third-party trademarks: Intel is a trademark of Intel Corporation; MS-DOS is a registered trademark of Microsoft Corporation; NFS is a trademark of Sun Microsystems, Inc.; Open Desktop is a registered trademark of The Santa Cruz Operation, Inc.; OSF/Motif is a registered trademark of Open Software Foundation, Inc.; SCO is a registered trademark of The Santa Cruz Operation, Inc.; UNIX is a registered trademark of UNIX System Laboratories, Inc.; VP/ix is a registered trademark of VP/ix Joint Venture.
    [Show full text]
  • The Single UNIX® Ingle UNIX Specification History & Timeline
    The Single UNIX® Specifi cationcation HistoryHistory && TTimelineimeline The history of UNIX starts back in 1969, when Ken UNIX System Laboratories (USL) becomes a company Thompson, Dennis Ritchie and others started working on 1969 The Beginning “The Single UNIX Specifi cation brings all the benefi ts of a single standard 1991 - majority-owned by AT&T. Linus Torvalds commences the “little-used PDP-7 in a corner” at Bell Labs and what operating system, namely application and information portability, scalability, Linux development. Solaris 1.0 debuts. was to become UNIX. fl exibility and freedom of choice for customers” USL releases UNIX System V Release 4.2 (Destiny). It had an assembler for a PDP-11/20, fi le system, fork(), October - XPG4 Brand launched by X/Open. December 1992 SVR4.2 1971 First Edition roff and ed. It was used for text processing of patent Allen Brown, President and CEO, The Open Group 22nd - Novell announces intent to acquire USL. Solaris documents. 2.0 and HP-UX 9.0 ship. 4.4BSD the fi nal release from Berkeley. June 16 - Novell First UNIX The fi rst installations had 3 users, no memory protection, 1993 4.4BSD 1972 The Story of the License Plate... acquires USL Installations and a 500 KB disk. Novell decides to get out of the UNIX business. Rather It was rewritten in C. This made it portable and changed than sell the business as a single entity, Novell transfers 1973 Fourth Edition In 1983 Digital Equipment Corporation the middle of it, Late the rights to the UNIX trademark and the specifi cation the history of OS’s.
    [Show full text]