DOCSLIB.ORG

Network Working Group J. Reynolds Request for Comments: 1700 J

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Network Working Group J. Reynolds Request for Comments: 1700 J Network Working Group J. Reynolds Request for Comments: 1700 J. Postel STD: 2 ISI Obsoletes RFCs: 1340, 1060, 1010, 990, 960, October 1994 943, 923, 900, 870, 820, 790, 776, 770, 762, 758,755, 750, 739, 604, 503, 433, 349 Obsoletes IENs: 127, 117, 93 Category: Standards Track ASSIGNED NUMBERS Status of this Memo This memo is a status report on the parameters (i.e., numbers and keywords) used in protocols in the Internet community. Distribution of this memo is unlimited. OVERVIEW This RFC is a snapshot of the ongoing process of the assignment of protocol parameters for the Internet protocol suite. To make the current information readily available the assignments are kept up-to- date in a set of online text files. This RFC has been assembled by catinating these files together with a minimum of formatting "glue". The authors appologize for the somewhat rougher formatting and style than is typical of most RFCs. We expect that various readers will notice specific items that should be corrected. Please send any specific corrections via email to . Reynolds & Postel [Page 1] RFC 1700 Assigned Numbers October 1994 INTRODUCTION The files in this directory document the currently assigned values for several series of numbers used in network protocol implementations. ftp://ftp.isi.edu/in-notes/iana/assignments The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols. The IANA is chartered by the Internet Society (ISOC) and the Federal Network Council (FNC) to act as the clearinghouse to assign and coordinate the use of numerous Internet protocol parameters. The Internet protocol suite, as defined by the Internet Engineering Task Force (IETF) and its steering group (the IESG), contains numerous parameters, such as internet addresses, domain names, autonomous system numbers (used in some routing protocols), protocol numbers, port numbers, management information base object identifiers, including private enterprise numbers, and many others. The common use of the Internet protocols by the Internet community requires that the particular values used in these parameter fields be assigned uniquely. It is the task of the IANA to make those unique assignments as requested and to maintain a registry of the currently assigned values. Requests for parameter assignments (protocols, ports, etc.) should be sent to . Requests for SNMP network management private enterprise number assignments should be sent to . The IANA is located at and operated by the Information Sciences Institute (ISI) of the University of Southern California (USC). If you are developing a protocol or application that will require the use of a link, socket, port, protocol, etc., please contact the IANA to receive a number assignment. Joyce K. Reynolds Internet Assigned Numbers Authority USC - Information Sciences Institute 4676 Admiralty Way Marina del Rey, California 90292-6695 Electronic mail: [email protected] Phone: +1 310-822-1511 Reynolds & Postel [Page 2] RFC 1700 Assigned Numbers October 1994 Most of the protocols are documented in the RFC series of notes. Some of the items listed are undocumented. Further information on protocols can be found in the memo, "Internet Official Protocol Standards" (STD 1). Data Notations The convention in the documentation of Internet Protocols is to express numbers in decimal and to picture data in "big-endian" order [COHEN]. That is, fields are described left to right, with the most significant octet on the left and the least significant octet on the right. The order of transmission of the header and data described in this document is resolved to the octet level. Whenever a diagram shows a group of octets, the order of transmission of those octets is the normal order in which they are read in English. For example, in the following diagram the octets are transmitted in the order they are numbered. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1 | 2 | 3 | 4 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 5 | 6 | 7 | 8 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 9 | 10 | 11 | 12 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Transmission Order of Bytes Whenever an octet represents a numeric quantity the left most bit in the diagram is the high order or most significant bit. That is, the bit labeled 0 is the most significant bit. For example, the following diagram represents the value 170 (decimal). 0 1 2 3 4 5 6 7 +-+-+-+-+-+-+-+-+ |1 0 1 0 1 0 1 0| +-+-+-+-+-+-+-+-+ Significance of Bits Similarly, whenever a multi-octet field represents a numeric quantity the left most bit of the whole field is the most significant bit. When Reynolds & Postel [Page 3] RFC 1700 Assigned Numbers October 1994 a multi-octet quantity is transmitted the most significant octet is transmitted first. Special Addresses There are five classes of IP addresses: Class A through Class E. Of these, Classes A, B, and C are used for unicast addresses, Class D is used for multicast addresses, and Class E addresses are reserved for future use. With the advent of classless addressing [CIDR1, CIDR2], the network-number part of an address may be of any length, and the whole notion of address classes becomes less important. There are certain special cases for IP addresses. These special cases can be concisely summarized using the earlier notation for an IP address: IP-address ::= { , } or IP-address ::= { , , } if we also use the notation "-1" to mean the field contains all 1 bits. Some common special cases are as follows: (a) {0, 0} This host on this network. Can only be used as a source address (see note later). (b) {0, } Specified host on this network. Can only be used as a source address. (c) { -1, -1} Limited broadcast. Can only be used as a destination address, and a datagram with this address must never be forwarded outside the (sub-)net of the source. (d) {, -1} Directed broadcast to specified network. Can only be used as a destination address. Reynolds & Postel [Page 4] RFC 1700 Assigned Numbers October 1994 (e) {, , -1} Directed broadcast to specified subnet. Can only be used as a destination address. (f) {, -1, -1} Directed broadcast to all subnets of specified subnetted network. Can only be used as a destination address. (g) {127, } Internal host loopback address. Should never appear outside a host. REFERENCES [COHEN] Cohen, D., "On Holy Wars and a Plea for Peace", IEEE Computer Magazine, October 1981. [CIDR1] Fuller, V., T. Li, J. Yu, and K. Varadhan, "Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy", RFC 1519, September 1993. [CIDR2] Rekhter, Y., and T. Li, "An Architecture for IP Address Allocation with CIDR", RFC 1518, September 1993. [] URL = ftp://ftp.isi.edu/in-notes/iana/assignments/introduction Reynolds & Postel [Page 5] RFC 1700 Assigned Numbers October 1994 VERSION NUMBERS In the Internet Protocol (IP) [RFC791] there is a field to identify the version of the internetwork general protocol. This field is 4 bits in size. Assigned Internet Version Numbers Decimal Keyword Version References ------- ------- ------- ---------- 0 Reserved [JBP] 1-3 Unassigned [JBP] 4 IP Internet Protocol [RFC791,JBP] 5 ST ST Datagram Mode [RFC1190,JWF] 6 SIP Simple Internet Protocol [RH6] 7 TP/IX TP/IX: The Next Internet [RXU] 8 PIP The P Internet Protocol [PXF] 9 TUBA TUBA [RXC] 10-14 Unassigned [JBP] 15 Reserved [JBP] REFERENCES [RFC791] Postel, J., ed., "Internet Protocol - DARPA Internet Program Protocol Specification", STD 5, RFC 791, USC/Information Sciences Institute, September 1981. [RFC1190] Topolcic, C., Editor, "Experimental Internet Stream Protocol, Version 2 (ST-II)", RFC 1190, CIP Working Group, October 1990. PEOPLE [JPB] Jon Postel [JWF] Jim Forgie [RH6] Robert Hinden [RXU] Robert Ullmann [PXF] Paul Francis [RXC] Ross Callon [] Reynolds & Postel [Page 6] RFC 1700 Assigned Numbers October 1994 URL = ftp://ftp.isi.edu/in-notes/iana/assignments/version-numbers Reynolds & Postel [Page 7] RFC 1700 Assigned Numbers October 1994 PROTOCOL NUMBERS In the Internet Protocol (IP) [DDN], [RFC791] there is a field, called Protocol, to identify the next level protocol. This is an 8 bit field. Assigned Internet Protocol Numbers Decimal Keyword Protocol References ------- ------- -------- ---------- 0 Reserved [JBP] 1 ICMP Internet Control Message [RFC792,JBP] 2 IGMP Internet Group Management [RFC1112,JBP] 3 GGP Gateway-to-Gateway [RFC823,MB] 4 IP IP in IP (encasulation) [JBP] 5 ST Stream [RFC1190,IEN119,JWF] 6 TCP Transmission Control [RFC793,JBP] 7 UCL UCL [PK] 8 EGP Exterior Gateway Protocol [RFC888,DLM1] 9 IGP any private interior gateway [JBP] 10 BBN-RCC-MON BBN RCC Monitoring [SGC] 11 NVP-II Network Voice Protocol [RFC741,SC3] 12 PUP PUP [PUP,XEROX] 13 ARGUS ARGUS [RWS4] 14 EMCON EMCON [BN7] 15 XNET Cross Net Debugger [IEN158,JFH2] 16 CHAOS Chaos [NC3] 17 UDP User Datagram [RFC768,JBP] 18 MUX Multiplexing [IEN90,JBP] 19 DCN-MEAS DCN Measurement Subsystems [DLM1] 20 HMP Host Monitoring [RFC869,RH6] 21 PRM Packet Radio Measurement [ZSU] 22 XNS-IDP XEROX NS IDP [ETHERNET,XEROX] 23 TRUNK-1 Trunk-1 [BWB6] 24 TRUNK-2 Trunk-2 [BWB6] 25 LEAF-1 Leaf-1 [BWB6] 26 LEAF-2 Leaf-2 [BWB6] 27 RDP Reliable Data Protocol [RFC908,RH6] 28 IRTP Internet Reliable Transaction [RFC938,TXM] 29 ISO-TP4 ISO Transport Protocol Class 4 [RFC905,RC77] 30 NETBLT Bulk Data Transfer Protocol [RFC969,DDC1] 31 MFE-NSP MFE Network Services
Load more

Recommended publications
  • George R. Lewycky 30 Regent St, Apt
    George R. Lewycky 30 Regent St, Apt. # 709, Jersey City, NJ 07302 [email protected] (646) 252 8882 http://georgenet.net/resume SUMMARY Over three decades of IT experience in various industries and lines of business with assorted technologies, databases, languages and operating systems. COMPUTER EXPERIENCE AND SKILLS Databases: Oracle, SQL Server, ADABAS (relational), dBase III, Access, Filemaker Pro 5 Oracle: Oracle Financials 11.5.7, Utilities, PL/SQL, SQL*Plus, SQL*Loader, TOAD SQL Server: T-SQL, SQL Server 2008 R2/2010/2012, Microsoft SQL Server Management Studio, SourceSafe, SSRS Languages : SQL, VB.NET, COBOL, JCL, SAS/SPSS (Statistics), CICS, ADA/SQL Operating Systems : IBM MVS & z/OS, Windows, UNIX (SCO & Sun), Mac, DOS (PC's), X-Windows, PICK and Primos Mainframe : JCL, MVS Utilities (DFSORT), COBOL, VSAM NOTE: Supplemental PDF’s available for Oracle, SQL Server, Mainframe & ADABAS at http://georgenet.net/resume DATA PROCESSING SKILLS • Data Analysis; ETL Methodology (Extract, Transform and Load); Interfaces, Data Migration and Cleansing • Packaged (Oracle eBusiness, Real World) and Custom/Internal Applications • Developing algorithms, techniques to re-engineer improve the procedure & processing flow • User interaction on all levels including documentation and training • Experience in Multi-Platform environments; Adaptable to new languages, software packages and industries EMPLOYMENT State Government Agency, NY, NY November 1997 to Present Senior Computer Programmer/Analyst Internet Technologies: February 2010 to present Involved in a major team effort replacing a customized Filemaker Pro 5 database/application, used as a customer service tool into a custom intranet and internet application under Visual Studio 2008 and ASP.NET 3.5 with SQL Server 2008 R2 backend in order to expedite customer claims in a diverse customized and complex customer claim processing system within various departments.
    [Show full text]
  • Emerging Technologies Multi/Parallel Processing
    Emerging Technologies Multi/Parallel Processing Mary C. Kulas New Computing Structures Strategic Relations Group December 1987 For Internal Use Only Copyright @ 1987 by Digital Equipment Corporation. Printed in U.S.A. The information contained herein is confidential and proprietary. It is the property of Digital Equipment Corporation and shall not be reproduced or' copied in whole or in part without written permission. This is an unpublished work protected under the Federal copyright laws. The following are trademarks of Digital Equipment Corporation, Maynard, MA 01754. DECpage LN03 This report was produced by Educational Services with DECpage and the LN03 laser printer. Contents Acknowledgments. 1 Abstract. .. 3 Executive Summary. .. 5 I. Analysis . .. 7 A. The Players . .. 9 1. Number and Status . .. 9 2. Funding. .. 10 3. Strategic Alliances. .. 11 4. Sales. .. 13 a. Revenue/Units Installed . .. 13 h. European Sales. .. 14 B. The Product. .. 15 1. CPUs. .. 15 2. Chip . .. 15 3. Bus. .. 15 4. Vector Processing . .. 16 5. Operating System . .. 16 6. Languages. .. 17 7. Third-Party Applications . .. 18 8. Pricing. .. 18 C. ~BM and Other Major Computer Companies. .. 19 D. Why Success? Why Failure? . .. 21 E. Future Directions. .. 25 II. Company/Product Profiles. .. 27 A. Multi/Parallel Processors . .. 29 1. Alliant . .. 31 2. Astronautics. .. 35 3. Concurrent . .. 37 4. Cydrome. .. 41 5. Eastman Kodak. .. 45 6. Elxsi . .. 47 Contents iii 7. Encore ............... 51 8. Flexible . ... 55 9. Floating Point Systems - M64line ................... 59 10. International Parallel ........................... 61 11. Loral .................................... 63 12. Masscomp ................................. 65 13. Meiko .................................... 67 14. Multiflow. ~ ................................ 69 15. Sequent................................... 71 B. Massively Parallel . 75 1. Ametek.................................... 77 2. Bolt Beranek & Newman Advanced Computers ...........
    [Show full text]
  • Reference & Manual
    DynaPDF 4.0 Reference & Manual API Reference Version 4.0.59 September 16, 2021 Legal Notices Copyright: © 2003-2021 Jens Boschulte, DynaForms GmbH. All rights reserved. DynaForms GmbH Burbecker Street 24 D-58285 Gevelsberg, Germany Trade Register HRB 9770, District Court Hagen CEO Jens Boschulte Phone: ++49 23 32-666 78 37 Fax: ++49 23 32-666 78 38 If you have questions please send an email to [email protected], or contact us by phone. This publication and the information herein is furnished as is, is subject to change without notice, and should not be construed as a commitment by DynaForms GmbH. DynaForms assumes no responsibility or liability for any errors or inaccuracies, makes no warranty of any kind (express, implied or statutory) with respect to this publication, and expressly disclaims any and all warranties of merchantability, fitness for particular purposes and no infringement of third-party rights. Adobe, Acrobat, and PostScript are trademarks of Adobe Systems Inc. AIX, IBM, and OS/390, are trademarks of International Business Machines Corporation. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation. Apple, Mac OS, and Safari are trademarks of Apple Computer, Inc. registered in the United States and other countries. TrueType is a trademark of Apple Computer, Inc. Unicode and the Unicode logo are trademarks of Unicode, Inc. UNIX is a trademark of The Open Group. Solaris is a trademark of Sun Microsystems, Inc. Tru64 is a trademark of Hewlett-Packard. Linux is a trademark of Linus Torvalds. Other company product and service names may be trademarks or service marks of others.
    [Show full text]
  • ADMINISTRATION GUIDE Version 7.2
    GUIDE STORMSHIELD ENDPOINT SECURITY ADMINISTRATION GUIDE Version 7.2 Document last update: June 2, 2021 Reference: ses-en-administration_guide-v7.2 SES - ADMINISTRATION GUIDE - V 7.2 Table of contents Preface 9 Thanks! 9 What is the target audience? 9 Contact 9 1. Use environment 10 1.1 Recommendations on security watch 10 1.2 Recommendations on keys and certificates 10 1.3 Recommendations on algorithms 10 1.4 Recommendations on administrators 10 1.5 Recommendations on workstations 10 1.6 Recommendations on administration workstations 11 1.7 Certification and qualification environment 11 2. Stormshield Endpoint Security Overview 12 2.1 Concepts 12 2.1.1 Concept 1: Integrated security 12 2.1.2 Concept 2: Proactive protection 12 2.1.3 Concept 3: Adaptive control 13 2.1.4 Concept 4: Flexible policy control 13 2.1.5 Concept 5: Application of policies based on the organization's directory 13 2.1.6 Concept 6: Information feedback 13 2.1.7 Concept 7: Data encryption 13 2.2 Protection mechanisms 13 2.2.1 Rule-based protection 14 2.2.2 Automatic protections 14 2.3 Architecture 15 2.3.1 Concepts 15 2.3.2 Stormshield Endpoint Security components 15 2.4 Packages and licenses 18 2.4.1 Packages 18 2.4.2 Licenses 21 3. Stormshield Endpoint Security Installation and Uninstallation 24 3.1 Downloading the Stormshield Endpoint Security software 24 3.1.1 Downloading from the client area 24 3.1.2 Checking software authenticity 24 3.2 System prerequisites for Stormshield Endpoint Security under Windows 25 3.2.1 Active Directory prerequisites 25 3.2.2 Stormshield
    [Show full text]
  • Informa2on Retrieval
    Introducon to Informaon Retrieval Introducon to Informaon Retrieval Brief (non‐technical) history . Early keyword‐based engines ca. 1995‐1997 Introducon to . Altavista, Excite, Infoseek, Inktomi, Lycos Informaon Retrieval . Paid search ranking: Goto (morphed into Overture.com → Yahoo!) CS276 . Your search ranking depended on how much you Informaon Retrieval and Web Search paid Pandu Nayak and Prabhakar Raghavan . Aucon for keywords: casino was expensive! Lecture 15: Web search basics 2 Introducon to Informaon Retrieval Introducon to Informaon Retrieval Brief (non‐technical) history . 1998+: Link‐based ranking pioneered by Google . Blew away all early engines save Inktomi . Great user experience in search of a business model . Meanwhile Goto/Overture’s annual revenues were nearing $1 billion Paid . Result: Google added paid search “ads” to the side, Search Ads independent of search results . Yahoo followed suit, acquiring Overture (for paid placement) and Inktomi (for search) . 2005+: Google gains search share, dominang in Europe and very strong in North America . 2009: Yahoo! and Microso propose combined paid search offering Algorithmic results. 3 4 Introducon to Informaon Retrieval Sec. 19.4.1 Introducon to Informaon Retrieval Sec. 19.4.1 Web search basics User Needs . Need [Brod02, RL04] User . Informaonal – want to learn about something (~40% / 65%) . Navigaonal – want to go to that page (~25% / 15%) Web spider . Transaconal – want to do something (web‐mediated) (~35% / 20%) . Access a service . Downloads Search . Shop Indexer . Gray areas . Find a good hub . Exploratory search “see what’s there” The Web Indexes Ad indexes5 6 1 Introducon to Informaon Retrieval Introducon to Informaon Retrieval How far do people look for results? Users’ empirical evaluaon of results .
    [Show full text]
  • User Interface Commands
    CHAPTER 2 User Interface Commands This chapter describes the commands used to access user and privileged EXEC command modes. It provides a description of the help command and features, lists the command editing keys and functions, and details the command history feature. This chapter also includes the EXEC commands that can be used to set various terminal parameters on a temporary basis (for the duration of a session). It includes the Telnet commands you can use to make a connection from a terminal to a remote router in order to configure the router. The commands to actually configure these parameters on a more permanent basis are provided in the “Terminal Line and Modem Support Commands” chapter in the Router Products Command Reference publication. You need enter only enough characters of a command to uniquely identify the command, thereby abbreviating the command syntax you type. For user interface task information and examples, refer to the “Understanding the User Interface” chapter of the Router Products Configuration Guide. User Interface Commands 2-1 clear line clear line Use the clear line EXEC command to return a terminal line to idle state. clear line line-number Syntax Description line-number Absolute line number Default None Command Mode EXEC Usage Guidelines Use this command to log out of a specific session running on another line. If the line uses a modem, the modem will be disconnected. Example In the following example, line 3 is reset: clear line 3 2-2 Router Products Command Reference connect connect To make a Telnet connection, enter the connect EXEC command at the system prompt.
    [Show full text]
  • Pete's Unsung Contribution to IEEE Standard 754 for Binary Floating
    File: 19July10 Pete’s Unsung Contribution to IEEE 754 Version dated July 10, 2010 8:21 am Pete’s Unsung Contribution to IEEE Standard 754 for Binary Floating-Point Prepared for the Conference to Celebrate Prof. G.W. “Pete” Stewart’s 70th Birthday July 19-20, 2010, at the University of Texas at Austin by Prof. W. Kahan Mathematics Dept. & Computer Science Dept. University of California @ Berkeley This is posted at <www.eecs.berkeley.edu/~wkahan/19July10.pdf> Prof. W. Kahan Page 1/18 File: 19July10 Pete’s Unsung Contribution to IEEE 754 Version dated July 10, 2010 8:21 am Pete’s Unsung Contribution to IEEE Standard 754 for Binary Floating-Point Abstract The near-universal portability, after recompilation, of numerical software for scientific, engineering, medical and entertaining computations owes a lot to the near-universal adoption of IEEE Standard 754 by computer arithmetic hardware starting in the 1980s. But in 1980, after forty months of dispute, the committee drafting this Standard was still unable to reach a consensus. The disagreement seemed irreconcilable. That was when Pete helped to close the divide. This is posted at <www.eecs.berkeley.edu/~wkahan/19July10.pdf> Prof. W. Kahan Page 2/18 File: 19July10 Pete’s Unsung Contribution to IEEE 754 Version dated July 10, 2010 8:21 am “Three Removes are as bad as a Fire.” Benjamin Franklin, Preface to Poor Richard’s Almanack (1758) My office has been moved twice since 1980, so now my notes for the events in question are buried in one of a few dozen full cartons,— I know not which.
    [Show full text]
  • Network Working Group N. Freed Request for Comments: 2049 Innosoft Obsoletes: 1521, 1522, 1590 N
    Network Working Group N. Freed Request for Comments: 2049 Innosoft Obsoletes: 1521, 1522, 1590 N. Borenstein Category: Standards Track First Virtual November 1996 Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract STD 11, RFC 822, defines a message representation protocol specifying considerable detail about US-ASCII message headers, and leaves the message content, or message body, as flat US-ASCII text. This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages to allow for (1) textual message bodies in character sets other than US-ASCII, (2) an extensible set of different formats for non-textual message bodies, (3) multi-part message bodies, and (4) textual header information in character sets other than US-ASCII. These documents are based on earlier work documented in RFC 934, STD 11, and RFC 1049, but extends and revises them. Because RFC 822 said so little about message bodies, these documents are largely orthogonal to (rather than a revision of) RFC 822. The initial document in this set, RFC 2045, specifies the various headers used to describe the structure of MIME messages. The second document defines the general structure of the MIME media typing system and defines an initial set of media types.
    [Show full text]
  • CSE 142 Python Slides
    CSE 390a Lecture 4 Persistent shell settings; intro to shell scripting slides created by Marty Stepp, modified by Jessica Miller & Ruth Anderson http://www.cs.washington.edu/390a/ 1 Lecture summary • persistent settings for your bash shell • basic script syntax and running scripts • shell variables and types • control statements: the for loop 2 .bash_profile and .bashrc • Every time you log in to bash, the commands in ~/.bash_profile are run . you can put any common startup commands you want into this file . useful for setting up aliases and other settings for remote login • Every time you launch a non-login bash terminal, the commands in ~/.bashrc are run . useful for setting up persistent commands for local shell usage, or when launching multiple shells . often, .bash_profile is configured to also run .bashrc, but not always Note: a dot (.) in front of a filename indicates a normally hidden file, use ls –a to see 3 Exercise:Edit your .bashrc • Exercise : Make it so that our attu alias from earlier becomes persistent, so that it will work every time we run a shell. • Exercise : Make it so that whenever you try to delete or overwrite a file during a move/copy, you will be prompted for confirmation first. 4 .plan • Another fun settings file • Stored in your home directory • Contains information you’d like others to be able to see . is displayed when the finger protocol is run • Exercise: create a quick .plan file, and make sure it works with finger 5 Shell scripts • script: A short program meant to perform a targeted task.
    [Show full text]
  • Operating-System Examples
    OPERATING SYSTEM CONCEPTS Sixth Edition ABRAHAM SILBERSCHATZ Bell Laboratories PETER BAER GALVIN Corporate Technologies, Inc. GREG GAGNE Westminster College JOHN WILEY & SONS, INC, New York / Chichester / Weinheim / Brisbane / Singapore / Toronto ACQUISITIONS EDITOR Paul Crockett SENIOR MARKETING MANAGER Katherine Hepburn SENIOR PRODUCTION EDITOR Ken Santor COVER DESIGNER Madelyn Lesure COVER ART Susan E. Cyr SENIOR ILLUSTRATION COORDINATOR Anna Melhorn This book was set in Palatino by Abraham Silberschatz and printed and bound by Courier-Westford. The cover was printed by Phoenix Color Corporation. This book is printed on acid-free paper. The paper in this book was manufactured by a mill whose forest manage- ment programs include sustained yield harvesting of its timberlands. Sustained yield harvesting principles ensure that the numbers of trees cut each year does not exceed the amount of new growth. Copyright O 2002 John Wiley & Sons, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permis- sion of the Publisher, or authorization through payment of the appropriate per- copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (508) 750-8400, fax (508) 750-4470. Requests to the Publisher for permis- sion should be addressed to the Permissions Department, John Wiley & Sons, Inc., 605 Third Avenue, New York, NY 10158-0012, (212) 850-6011, fax (212) 850- ISBN 0-471-41743-2 Printed in the United States of America PREFACE Operating systems are an essential part of any computer system.
    [Show full text]
  • Network Working Group S. Kirkpatrick Request for Comments: 1166 M
    Network Working Group S. Kirkpatrick Request for Comments: 1166 M. Stahl Obsoletes RFCs: 1117, 1020, 997, 990, 960, 943, M. Recker 943, 923, 900, 870, 820, 790, 776, 770, 762, July 1990 758, 755, 750, 739, 604, 503, 433, 349 Obsoletes IENs: 127, 117, 93 INTERNET NUMBERS Status of this Memo This memo is a status report on the network numbers and autonomous system numbers used in the Internet community. Distribution of this memo is unlimited. Table of Contents Introduction.................................................... 1 Network Numbers................................................. 4 Class A Networks................................................ 7 Class B Networks................................................ 8 Class C Networks................................................ 47 Other Reserved Internet Addresses............................... 100 Network Totals.................................................. 101 Autonomous System Numbers....................................... 102 Documents....................................................... 111 Contacts........................................................ 115 Security Considerations......................................... 182 Authors' Addresses.............................................. 182 Introduction This Network Working Group Request for Comments documents the currently assigned network numbers and gateway autonomous systems. This RFC will be updated periodically, and in any case current information can be obtained from Hostmaster at the DDN Network Information
    [Show full text]
  • Final Version of Thesis
    JAPANESE INNOVATION STRATEGY AND THE ACQUISITION OF UK INFORMATION TECHNOLOGY FIRMS T H W Minshall Christ’s College, Cambridge A dissertation submitted to the University of Cambridge for the Degree of Doctor of Philosophy Cambridge University Engineering Department April 1997 Preface Except for commonly understood and accepted ideas, or where specific reference is made, the work reported in this dissertation is my own and includes nothing which is the outcome of work done in collaboration. No part of the dissertation has been previously submitted to any university for any degree, diploma or other qualification. T H W Minshall Cambridge April 1997 Acknowledgements I am particularly grateful to my supervisor, Elizabeth Garnsey, for her guidance and support throughout the course of this research. In addition, thanks are due to Nick Oliver and Hugh Whittaker, and all my colleagues at the Manufacturing and Management Division of the Engineering Department, and at the Judge Institute of Management Studies for their advice and constructive criticism. On the industry side, my gratitude to the companies in the UK and Japan who agreed to contribute to the contents of this dissertation. Finally, my thanks to my family, for encouraging me, and to Nicola, for all her support and for applying her new-found skills at proof-reading. This programme of research was supported by a Postgraduate Training Award (J00 429 332012) from the ESRC. Table of contents Chapter 1 Introduction ...........................................................................................................
    [Show full text]