DOCSLIB.ORG

Programming Utilities Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Programming Utilities Guide Programming Utilities Guide Sun Microsystems, Inc. 2550 Garcia Avenue Mountain View, CA 94043-1100 U.S.A. Part No: 802-5880 August 1997 Copyright 1997 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California 94303-4900 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, SunSoft, SunDocs, SunExpress, and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and SunTM Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements. RESTRICTED RIGHTS: Use, duplication, or disclosure by the U.S. Government is subject to restrictions of FAR 52.227–14(g)(2)(6/87) and FAR 52.227–19(6/87), or DFAR 252.227–7015(b)(6/95) and DFAR 227.7202–3(a). DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. Copyright 1997 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, Californie 94303-4900 Etats-Unis. Tous droits réservés. Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l’utilisation, la copie, la distribution, et la décompilation. Aucune partie de ce produit ou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit, sans l’autorisation préalable et écrite de Sun et de ses bailleurs de licence, s’il y en a. Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices de caractères, est protégé par un copyright et licencié par des fournisseurs de Sun. Des parties de ce produit pourront être dérivées du système Berkeley BSD licenciés par l’Université de Californie. UNIX est une marque déposée aux Etats-Unis et dans d’autres pays et licenciée exclusivement par X/Open Company, Ltd. Sun, Sun Microsystems, le logo Sun, SunSoft, SunDocs, SunExpress, et Solaris sont des marques de fabrique ou des marques déposées, ou marques de service, de Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays. Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d’autres pays. Les produits portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc. L’interface d’utilisation graphique OPEN LOOK et SunTM a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun reconnaît les efforts de pionniers de Xerox pour la recherche et le développement du concept des interfaces d’utilisation visuelle ou graphique pour l’industrie de l’informatique. Sun détient une licence non exclusive de Xerox sur l’interface d’utilisation graphique Xerox, cette licence couvrant également les licenciés de Sun qui mettent en place l’interface d’utilisation graphique OPEN LOOK et qui en outre se conforment aux licences écrites de Sun. CETTE PUBLICATION EST FOURNIE “EN L’ETAT” ET AUCUNE GARANTIE, EXPRESSE OU IMPLICITE, N’EST ACCORDEE, Y COMPRIS DES GARANTIES CONCERNANT LA VALEUR MARCHANDE, L’APTITUDE DE LA PUBLICATION A REPONDRE A UNE UTILISATION PARTICULIERE, OU LE FAIT QU’ELLE NE SOIT PAS CONTREFAISANTE DE PRODUIT DE TIERS. CE DENI DE GARANTIE NE S’APPLIQUERAIT PAS, DANS LA MESURE OU IL SERAIT TENU JURIDIQUEMENT NUL ET NON AVENU. Please Recycle Contents Preface xi 1. Tracing Program Execution With the TNF Utilities 1 Defining Types of Users 2 Using Existing Probe Points 2 Debugging a Program 2 Inserting Probe Points in a Library 2 Tracing Kernel Execution 2 How TNF Works 2 Inserting Probe Points 3 Starting prex 3 Running prex 6 Reading the Trace File 18 Kernel Tracing 19 Controlling Kernel Tracing (prex)20 Extracting Kernel Trace Data (tnfxtract)23 Examining Kernel Trace Data (tnfdump)24 Available Kernel Probes (tnf_probes)24 Thread Probes 25 Shell Script for Kernel Tracing 28 Contents iii Advanced Topics 31 Inserting Probe Points 31 Defining User Types for Probe Points 36 Performance Issues 38 /proc 38 dlopen() and dlclose() and History 39 Signals 39 Failure of Event-Writing Operations 39 Target Executing a fork() or exec() 40 2. Lexical Analysis 41 Internationalization 42 Generating a Lexical Analyzer Program 42 Writing lex Source 44 The Fundamentals of lex Rules 44 Advanced lex Features 49 C++ Mangled Symbols 57 Using lex and yacc Together 59 Automaton 62 Summary of Source Format 62 3. yacc — A Compiler Compiler 65 Internationalization 67 Basic Specifications 67 Actions 69 Lexical Analysis 72 Parser Operation 73 Ambiguity and Conflicts 77 Precedence 81 Error Handling 85 iv Programming Utilities Guide ♦ August 1997 The yacc Environment 88 Hints for Preparing Specifications 89 Input Style 89 Left Recursion 89 C++ Mangled Symbols 90 Lexical Tie-Ins 91 Reserved Words 91 Advanced Topics 92 Simulating error and accept in Actions 92 Accessing Values in Enclosing Rules 92 Support for Arbitrary Value Types 93 yacc Input Syntax 94 Examples 96 A Simple Example 96 An Advanced Example 99 4. make Utility 107 Dependency Checking: make vs. Shell Scripts 108 Writing a Simple Makefile 109 Basic Use of Implicit Rules 111 Processing Dependencies 111 Null Rules 114 Special Targets 114 Unknown Targets 115 Duplicate Targets 115 Reserved make Words 115 Running Commands Silently 116 Automatic Retrieval of SCCS Files 117 Passing Parameters: Simple make Macros 118 Contents v .KEEP_STATE and Command Dependency Checking 120 .KEEP_STATE and Hidden Dependencies 121 Displaying Information About a make Run 122 Using make to Compile Programs 125 Simple Makefile Example 125 Using make’s Predefined Macros 126 Using Implicit Rules to Simplify a Makefile: Suffix Rules 127 When to Use Explicit Target Entries vs. Implicit Rules 129 Implicit Rules and Dynamic Macros 129 Adding Suffix Rules 132 Pattern-Matching Rules: An Alternative to Suffix Rules 133 Building Object Libraries 139 Libraries, Members, and Symbols 139 Library Members and Dependency Checking 140 Using make to Maintain Libraries and Programs 141 More about Macros 141 Linking with System-Supplied Libraries 143 Compiling Programs for Debugging and Profiling 144 Compiling Debugging and Profiling Variants 146 Maintaining Separate Program and Library Variants 147 Maintaining a Directory of Header Files 150 Compiling and Linking with Your Own Libraries 151 Nested make Commands 151 Passing Parameters to Nested make Commands 154 Compiling Other Source Files 156 Maintaining Shell Scripts with make and SCCS 158 Running Tests with make 159 Maintaining Software Projects 161 vi Programming Utilities Guide ♦ August 1997 Organizing a Project for Ease of Maintenance 162 Building the Entire Project 163 Maintaining Directory Hierarchies with the Recursive Makefiles 165 Maintaining Recursive Targets 165 Maintaining a Large Library as a Hierarchy of Subsidiaries 166 Reporting Hidden Dependencies to make 168 make Enhancements Summary 168 Default Makefile 168 The State File .make.state 169 Hidden-Dependency Checking 169 Command-Dependency Checking 169 Automatic Retrieval of SCCS Files 169 Pattern-Matching Rules 170 Pattern-Replacement Macro References 170 New Options 172 Support for C++ and Modula-2 172 Naming Scheme for Predefined Macros 172 New Special-Purpose Targets 173 New Implicit lint Rule 173 Macro Processing Changes 173 Improved ar Library Support 175 Target Groups 175 Incompatibilities with Previous Versions 176 The −d Option 176 Dynamic Macros 176 Tilde Rules 177 Target Names 177 5. SCCS Source Code Control System 179 Contents vii The sccs Command 179 The sccs create Command 180 Basic sccs Subcommands 180 Deltas and Versions 181 sccs Subcommands 182 Checking Files In and Out 182 Incorporating Version-Dependent Information by Using ID Keywords 186 Making Inquiries 187 Deleting Committed Changes 190 Version Control for Binary Files 193 Maintaining Source Directories 194 Duplicate Source Directories 194 SCCS and make 194 Keeping SIDs Consistent Across Files 195 Starting a New Release 195 Temporary Files Used by SCCS 195 Branches 196 Using Branches 198 Administering SCCS Files 199 Interpreting Error Messages: sccs help 199 Altering History File Defaults: sccs admin 200 Validating the History File 201 Restoring the History File
Load more

Recommended publications
  • Solid Truss to Shell Numerical Homogenization of Prefabricated Composite Slabs
    materials Article Solid Truss to Shell Numerical Homogenization of Prefabricated Composite Slabs Natalia Staszak 1, Tomasz Garbowski 2 and Anna Szymczak-Graczyk 3,* 1 Research and Development Department, FEMat Sp. z o. o., Romana Maya 1, 61-371 Pozna´n,Poland; [email protected] 2 Department of Biosystems Engineering, Poznan University of Life Sciences, Wojska Polskiego 50, 60-627 Pozna´n,Poland; [email protected] 3 Department of Construction and Geoengineering, Poznan University of Life Sciences, Pi ˛atkowska94 E, 60-649 Pozna´n,Poland * Correspondence: [email protected] Abstract: The need for quick and easy deflection calculations of various prefabricated slabs causes simplified procedures and numerical tools to be used more often. Modelling of full 3D finite element (FE) geometry of such plates is not only uneconomical but often requires the use of complex software and advanced numerical knowledge. Therefore, numerical homogenization is an excellent tool, which can be easily employed to simplify a model, especially when accurate modelling is not necessary. Homogenization allows for simplifying a computational model and replacing a complicated composite structure with a homogeneous plate. Here, a numerical homogenization method based on strain energy equivalence is derived. Based on the method proposed, the structure of the prefabricated concrete slabs reinforced with steel spatial trusses is homogenized to a single plate element with an effective stiffness. There is a complete equivalence between the full 3D FE model built with solid elements combined with truss structural elements and the simplified Citation: Staszak, N.; Garbowski, T.; Szymczak-Graczyk, A. Solid Truss to homogenized plate FE model.
    [Show full text]
  • Dot at Command Firmware Release 4.0.0 Release 3.3.5
    Product Change Notification Software Release Notes Dot AT Command Firmware Release 4.0.0 Release 3.3.5 MultiTech xDot® MultiTech mDot™ Date: March 30, 2021 Contents Product Change Notification (PCN) Number PCN 03302021-001 (Dot) I. Overview II. Suggested Action Plan I. Overview MultiTech announces the availability of new AT Command III. Release 4.0.0 Overview Firmware for use on MultiTech® Long Range LoRa® Modules: MultiTech xDot® (MTXDOT Series) IV. Release 3.3.5 Overview MultiTech mDot™ (MTDOT Series) V. Schedule New versions are currently available for download and VI. Flashing mDot Firmware evaluation: VII. Part Numbers Impacted Release 4.0.0 (shipping in June 2021) Release 3.3.5 VIII. Mbed OS Overview IX. xDot Overview Release 4.0.0 will released into standard MultiTech product starting in June 2021. Currently, product ships with X. mDot Overview Release 3.2.1 XI. xDot Micro Developer Kit II. Suggested Action Plan XII. Additional Information Customers Review the information in this PCN and forward to Attachments others within your organization who are actively Identifying Firmware Version involved with the development of IoT applications using the MultiTech xDot and MultiTech mDot. Identifying Date of Manufacture Consider downloading the firmware available on MultiTech or Mbed websites to check compatibility mPower & mLinux Software with existing deployments. PCN 03302021-001 (Dot) Page 1 of 12 https://support.multitech.com Review the release schedule for the upcoming firmware release and understand the effect on your manufacturing and deployment schedules. Distributors Forward this announcement to others within your organization who are actively involved in the sale or support of LoRa-enabled sensors.
    [Show full text]
  • Dell EMC Powerstore CLI Guide
    Dell EMC PowerStore CLI Guide May 2020 Rev. A01 Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners. Contents Additional Resources.......................................................................................................................4 Chapter 1: Introduction................................................................................................................... 5 Overview.................................................................................................................................................................................5 Use PowerStore CLI in scripts.......................................................................................................................................5 Set up the PowerStore CLI client........................................................................................................................................5 Install the PowerStore CLI client..................................................................................................................................
    [Show full text]
  • Shell Variables
    Shell Using the command line Orna Agmon ladypine at vipe.technion.ac.il Haifux Shell – p. 1/55 TOC Various shells Customizing the shell getting help and information Combining simple and useful commands output redirection lists of commands job control environment variables Remote shell textual editors textual clients references Shell – p. 2/55 What is the shell? The shell is the wrapper around the system: a communication means between the user and the system The shell is the manner in which the user can interact with the system through the terminal. The shell is also a script interpreter. The simplest script is a bunch of shell commands. Shell scripts are used in order to boot the system. The user can also write and execute shell scripts. Shell – p. 3/55 Shell - which shell? There are several kinds of shells. For example, bash (Bourne Again Shell), csh, tcsh, zsh, ksh (Korn Shell). The most important shell is bash, since it is available on almost every free Unix system. The Linux system scripts use bash. The default shell for the user is set in the /etc/passwd file. Here is a line out of this file for example: dana:x:500:500:Dana,,,:/home/dana:/bin/bash This line means that user dana uses bash (located on the system at /bin/bash) as her default shell. Shell – p. 4/55 Starting to work in another shell If Dana wishes to temporarily use another shell, she can simply call this shell from the command line: [dana@granada ˜]$ bash dana@granada:˜$ #In bash now dana@granada:˜$ exit [dana@granada ˜]$ bash dana@granada:˜$ #In bash now, going to hit ctrl D dana@granada:˜$ exit [dana@granada ˜]$ #In original shell now Shell – p.
    [Show full text]
  • Application for New Or Duplicate License Plates
    APPLICATION FOR NEW OR DUPLICATE LICENSE PLATES APPLICANT AND VEHICLE INFORMATION Owner(s) Name Daytime Phone Number ( ) - Mailing Address City State ZIP Vehicle Make Model Year VIN Body Style Original License Plate Number Expiration Date Number of Plate(s) lost, stolen, destroyed Plate(s) Surrendered STEP STEP #1 If license plate(s) cannot be surrendered because they are lost or stolen, duplicate license plates (plates that are reproduced with the same plate number) cannot be displayed on the vehicle until the validation stickers on the original plates have expired. This form cannot be used to replace lost, damaged, or mutilated embossed plates. You must reapply for embossed plates using the form MV-145. In case of lost, damaged or mutilated plates, a new or duplicate license plate and registration certificate will be issued by the County Treasurer. Damaged or mutilated license plates must be surrendered to the County Treasurer when you receive your new license plates. The fee to obtain a replacement license plate is eight dollars ($8.00), made payable to the County Treasurer. A replacement plate is the next available consecutive plate. The fee to obtain a duplicate license plate is thirty dollars ($30.00), made payable to the County Treasurer. A duplicate plate is the plate with the same number or combination that you currently have; WYDOT will reproduce your plate. Please note the following plates are the ONLY license plates that can be remade: Prestige, all types of Specialty Plates and preferred number series plates. Preferred number series in each county are determined by the County Treasurer, but will not exceed 9,999.
    [Show full text]
  • The AWK Programming Language
    The Programming ~" ·. Language PolyAWK- The Toolbox Language· Auru:o V. AHo BRIAN W.I<ERNIGHAN PETER J. WEINBERGER TheAWK4 Programming~ Language TheAWI(. Programming~ Language ALFRED V. AHo BRIAN w. KERNIGHAN PETER J. WEINBERGER AT& T Bell Laboratories Murray Hill, New Jersey A ADDISON-WESLEY•• PUBLISHING COMPANY Reading, Massachusetts • Menlo Park, California • New York Don Mills, Ontario • Wokingham, England • Amsterdam • Bonn Sydney • Singapore • Tokyo • Madrid • Bogota Santiago • San Juan This book is in the Addison-Wesley Series in Computer Science Michael A. Harrison Consulting Editor Library of Congress Cataloging-in-Publication Data Aho, Alfred V. The AWK programming language. Includes index. I. AWK (Computer program language) I. Kernighan, Brian W. II. Weinberger, Peter J. III. Title. QA76.73.A95A35 1988 005.13'3 87-17566 ISBN 0-201-07981-X This book was typeset in Times Roman and Courier by the authors, using an Autologic APS-5 phototypesetter and a DEC VAX 8550 running the 9th Edition of the UNIX~ operating system. -~- ATs.T Copyright c 1988 by Bell Telephone Laboratories, Incorporated. 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, photocopy­ ing, recording, or otherwise, without the prior written permission of the publisher. Printed in the United States of America. Published simultaneously in Canada. UNIX is a registered trademark of AT&T. DEFGHIJ-AL-898 PREFACE Computer users spend a lot of time doing simple, mechanical data manipula­ tion - changing the format of data, checking its validity, finding items with some property, adding up numbers, printing reports, and the like.
    [Show full text]
  • Bridge Types in NSW Historical Overviews 2006
    Timber Truss Bridges Study of Relative Heritage Significance of All Timber Truss Road Bridges in NSW 1998 25 Historical Overview of Bridge Types in NSW: Extract from the Study of Relative Heritage Significance of all Timber Truss Road Bridges in NSW HISTORY OF TIMBER TRUSS BRIDGES IN NSW 1.1 GENERAL During the first fifty years of the colony of New South Wales, 1788 - 1838, settlement was confined to the narrow coastal strip between the Pacific Ocean and the Great Dividing Range. The scattered communities were well served by ships plying the east coast and its many navigable rivers. Figure 1.1a: Settlement of early colonial NSW. Shaded areas are settled. In Governor Macquarie's time between 1810-1822, a number of good roads were built, but despite his efforts and those of the subsequent Governors Darling and Bourke, and of road builders George Evans, William Cox and Thomas Mitchell, the road system and its associated bridges could only be described as primitive. Many roads and bridges were financed through public subscriptions or as private ventures, particularly where tolls could be levied. The first significant improvement to this situation occurred in late 1832 when Surveyor- General Mitchell observed a competent stone mason working on a wall in front of the Legislative Council Chambers in Macquarie Street. It was David LennoxR3. He was appointed Sub-Inspector of Roads on October 1, 1832 then Superintendent of Bridges on June 6, 1833. His first project was to span a gully for the newly formed Mitchell's Pass on the eastern side of the Blue Mountains.
    [Show full text]
  • Learning the Methods of Engineering Analysis Using Case Studies, Excel and VBA - Course Design
    Computers in Education, Session 1520 Learning the Methods of Engineering Analysis Using Case Studies, Excel and VBA - Course Design Michael A. Collura, Bouzid Aliane, Samuel Daniels, Jean Nocito-Gobel School of Engineering & Applied Science, University of New Haven Abstract Methods of Engineering Analysis, EAS 112, is a first year course in which engineering and applied science students learn how to apply a variety of computer analysis methods. The course uses a “problem-driven” approach in which case studies of typical engineering and science problems become the arena in which these analytical methods must be applied. A common spreadsheet program, such as Microsoft Excel, is the starting point to teach such topics as descriptive statistics, regression, interpolation, integration and solving sets of algebraic, differential and finite difference equations. Students are also introduced to programming fundamentals in the Visual Basic for Applications environment as they create the algorithms needed for the analysis. In this programming environment students gain an understanding of basic programming concepts, such as data types, assignment and conditional statements, logical and numerical functions, program flow control, passing parameters/returning values with functions and working with arrays. EAS 112 is a stop along the Multidisciplinary Engineering Foundation Spiral1 in the engineering programs at the University of New Haven. A typical student will take the course in the second semester of the first year. Certain engineering foundation topics will appear in the assigned problems and case studies, contributing to students’ understanding of areas such as electrical circuits, mass balances, and structural mechanics. At this point along the spiral curriculum students are given most of the equations needed to analyze the case study problems, but they are responsible for development of the algorithms and implementing these in the spreadsheet and/or programming environment.
    [Show full text]
  • DOT Series at Command Reference Guide DOT SERIES at COMMAND GUIDE
    DOT Series AT Command Reference Guide DOT SERIES AT COMMAND GUIDE DOT Series AT Command Guide Models: MTDOT-915-xxx, MTDOT-868-xxx, MTXDOT-915-xx, MTXDOT-898-xx, Part Number: S000643, Version 2.2 Copyright This publication may not be reproduced, in whole or in part, without the specific and express prior written permission signed by an executive officer of Multi-Tech Systems, Inc. All rights reserved. Copyright © 2016 by Multi-Tech Systems, Inc. Multi-Tech Systems, Inc. makes no representations or warranties, whether express, implied or by estoppels, with respect to the content, information, material and recommendations herein and specifically disclaims any implied warranties of merchantability, fitness for any particular purpose and non- infringement. Multi-Tech Systems, Inc. reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of Multi-Tech Systems, Inc. to notify any person or organization of such revisions or changes. Trademarks and Registered Trademarks MultiTech, and the MultiTech logo, and MultiConnect are registered trademarks and mDot, xDot, and Conduit are a trademark of Multi-Tech Systems, Inc. All other products and technologies are the trademarks or registered trademarks of their respective holders. Legal Notices The MultiTech products are not designed, manufactured or intended for use, and should not be used, or sold or re-sold for use, in connection with applications requiring fail-safe performance or in applications where the failure of the products would reasonably be expected to result in personal injury or death, significant property damage, or serious physical or environmental damage.
    [Show full text]
  • Configuring Your Login Session
    SSCC Pub.# 7-9 Last revised: 5/18/99 Configuring Your Login Session When you log into UNIX, you are running a program called a shell. The shell is the program that provides you with the prompt and that submits to the computer commands that you type on the command line. This shell is highly configurable. It has already been partially configured for you, but it is possible to change the way that the shell runs. Many shells run under UNIX. The shell that SSCC users use by default is called the tcsh, pronounced "Tee-Cee-shell", or more simply, the C shell. The C shell can be configured using three files called .login, .cshrc, and .logout, which reside in your home directory. Also, many other programs can be configured using the C shell's configuration files. Below are sample configuration files for the C shell and explanations of the commands contained within these files. As you find commands that you would like to include in your configuration files, use an editor (such as EMACS or nuTPU) to add the lines to your own configuration files. Since the first character of configuration files is a dot ("."), the files are called "dot files". They are also called "hidden files" because you cannot see them when you type the ls command. They can only be listed when using the -a option with the ls command. Other commands may have their own setup files. These files almost always begin with a dot and often end with the letters "rc", which stands for "run commands".
    [Show full text]
  • 2017 Noise Requirements
    DEPARTMENT OF TRANSPORTATION Noise Requirements for MnDOT and other Type I Federal-aid Projects Satisfies FHWA requirements outlined in 23 CFR 772 Effective Date: July 10, 2017 Website address where additional information can be found or inquiries sent: http://www.dot.state.mn. u /environment/noise/index.html "To request this document in an alternative format, contact Janet Miller at 651-366-4720 or 1-800-657-3774 (Greater Minnesota); 711or1-800-627-3529 (Minnesota Relay). You may also send an e-mail to [email protected]. (Please request at least one week in advance). MnDOT Noise Requirements: Effective Date July 10, 2017 This document contains the Minnesota Department of Transportation Noise Requirements (hereafter referred to as 'REQUIREMENTS') which describes the implementation of the requirements set forth by the Federal Highway Administration Title 23 Code of Federal Regulations Part 772: Procedures for Abatement of Highway Traffic Noise and Construction Noise. These REQUIREMENTS also describe the implementation of the requirements set forth by Minnesota Statute 116.07 Subd.2a: Exemptions from standards, and Minnesota Rule 7030: Noise Pollution Control. These REQUIREMENTS were developed by the Minnesota Department of Transportation and reviewed and approved with by the Federal Highway Administration. C,- 2.8-{7 Charles A. Zelle, Commissioner Date Minnesota Department of Transportation toJ;.11/11 Arlene Kocher, Divi lronAdmini ~ rator Date I Minnesota Division Federal Highway Administration MnDOT Noise Requirements: Effective
    [Show full text]
  • GNU Coreutils Cheat Sheet (V1.00) Created by Peteris Krumins ([email protected], -- Good Coders Code, Great Coders Reuse)
    GNU Coreutils Cheat Sheet (v1.00) Created by Peteris Krumins ([email protected], www.catonmat.net -- good coders code, great coders reuse) Utility Description Utility Description arch Print machine hardware name nproc Print the number of processors base64 Base64 encode/decode strings or files od Dump files in octal and other formats basename Strip directory and suffix from file names paste Merge lines of files cat Concatenate files and print on the standard output pathchk Check whether file names are valid or portable chcon Change SELinux context of file pinky Lightweight finger chgrp Change group ownership of files pr Convert text files for printing chmod Change permission modes of files printenv Print all or part of environment chown Change user and group ownership of files printf Format and print data chroot Run command or shell with special root directory ptx Permuted index for GNU, with keywords in their context cksum Print CRC checksum and byte counts pwd Print current directory comm Compare two sorted files line by line readlink Display value of a symbolic link cp Copy files realpath Print the resolved file name csplit Split a file into context-determined pieces rm Delete files cut Remove parts of lines of files rmdir Remove directories date Print or set the system date and time runcon Run command with specified security context dd Convert a file while copying it seq Print sequence of numbers to standard output df Summarize free disk space setuidgid Run a command with the UID and GID of a specified user dir Briefly list directory
    [Show full text]