DOCSLIB.ORG

Introduction to Linux - June 2010

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Introduction to Linux - June 2010 Introduction to Linux - June 2010 Introduction to Linux Outline • An Overview of Linux • Accessing Pawsey Supercomputers • The Linux Command Line Interface • The vi Editor I. OVERVIEW OF LINUX About Linux • It is an Operating System • Free and open source • Runs on just about anything • Is used on supercomputers and data stores • Is used in mobile phones and tablets (Android) • Has a graphical user interface (GUI) and command line interface (CLI) • Can be accessed via remote terminal windows • MobaXterm on PC, Terminal on Mac Linux Operating System • Linux is the kernel, or basic operating system. • On top of this is a software stack including utilities, libraries, compilers, office suites, email clients, web browsers etc. • Linux itself is very robust and secure. Apps are usually the problem. Linux Distributions • Different organisations package Linux with various user applications. These are “Distributions”. • They include package managers, to simplify application and dependency management. • Common distributions are: • CentOS, SuSE, SLES – used on Pawsey supercomputers • Ubuntu – used on NeCTAR • Android is based on Linux II. LINUX STORAGE LAYOUT Linux Filesystem Linux has a single hierarchical structure of directories. Everything starts from the root directory “/”. A file can be specified by the absolute path through the directory tree from the root directory. For example: /etc/motd or by its relative path to where you are. For example: ../motd Directories have a list of files in the directory as well as their properties Typical Linux Layout / bin dev etc home lib opt mnt usr var bash sda hostname user1 cdrom lib log cp sdb motd user2 usb include Linux Directory Structure /bin contains essential programs for booting and maintaining the system; e.g. bash, chmod, chown, cp, grep, kill, ps, rm, tar /dev special files pointing to system devices /etc configuration files for various applications /home contains directories for all users a system has e.g. /home/username /usr contains almost all the programs which are not located in /bin or /sbin, manual pages /var files like logs, emails User Interface from Iron Man 2 III. USING LINUX Shells A shell is a command-line interpreter. Popular shells include: • bash Bourne-Again Shell, default shell on most Linux systems and at Pawsey • sh Bourne Shell, an older shell, superseded by Bash • csh C Shell, with a syntax that resembles the C programming language syntax • tcsh an improved version of the C Shell • ksh Korn Shell Remote Access Access to Pawsey machines is via ssh • ssh creates an encrypted tunnel to the remote host. By default it starts a remote shell. • ssh can also tunnel graphical programs. • ssh uses fingerprints to identify computers … so you don't give your password to someone pretending to be the remote host magnus: 02:2e:b8:f5:0c:e8:f2:ab:7b:66:33:41:39:5a:13:12 Command line SSH Within a terminal window, type: ssh [email protected] • Common terminal programs: • Windows, use MobaXterm (download required) • Linux, use xterm (preinstalled) • OS X, use Terminal (preinstalled) or xterm (download required) Graphical Interfaces • Remote graphical interface for some tasks available. • Graphical debuggers, text editors, remote visualisation. • Low performance over long distances. • Very easy to set up for Linux, Mac and MobaXterm clients. Add -X flag to ssh. ssh -X [email protected] • For higher performance remote GUI, use VNC. See portal.pawsey.org.au/docs/Supercomputers/Remote_Visualisation Basic Commands Most Linux commands follow the general form: command [option(s)] [filename(s)] Examples: ls ls -la ls / ls -la /home/cou000 Basic Commands cd change directory ls list directory contents pwd print name of current/working directory mkdir make directories rm remove files or directories mv move (rename) files cp copy (replicate) files cat concatenate files and print on the standard output more / less view files a page at a time Note: Transferring files between Pawsey machines scp mymotd3 [email protected]:/home/username Exercise 1 Connect to magnus.pawsey.org.au using SSH: ssh [email protected] Enter the following commands: pwd cd /usr/share ls ls –l pwd cd pwd Exercise 2 Create some files and directories mkdir test1 test2 test3 ls -la cp /etc/motd test1 ls test1 cat test1/motd (use tab to autocomplete filenames) Move into and out of directories pwd cd test1 pwd cd .. pwd Deleting files and directories: rmdir test1 rm test1/motd rmdir test1 (or rm -r for recursive delete - use with care!) Inbuilt Help Information Most commands have help command line options, typically: -h --help There are also manual pages for most commands: man ls (press q to exit manual pages) Exercise 3 Run the word count utility on the motd file wc /etc/motd Read the manual page to find out what the output values refer to man wc What option would just output the word count? Command History The command line interface keeps a history of your commands, which you can view with the history command You can reuse commands from your history using the exclamation mark (also referred to as bang or shriek) and the line number (eg !42) Alternatively the up and down arrow keys can scroll through previous commands, and Ctrl-r can let you search for the matching command The exclamation mark can also be used to shortcut to the last command (!!) or last argument of the last command (!$) Piping & Grep Pipes are a UNIX feature which allows you to connect several commands together in one line and pass data from one to the next. • Most UNIX commands get input from stdin and pass output to stdout • The pipe symbol “|” directs UNIX to connect stdout from the first command to the stdin of the second command. • > will redirect the output to a file, >> will append to an existing file, < will redirect input from a file grep is a command line text search utility. It gets its name from global / regular expression / print. • grep Pawsey /etc/motd 23 Exercise 4 More handy commands history tail /etc/motd tail -5 /etc/motd grep Pawsey !$ history !! !<number> (to repeat history item <number>) What’s in the Magnus queue? squeue squeue | less (press space for next page) squeue | wc squeue | grep <username> File Permissions There are three sets of permissions. Each of these is via numerical (bitwise) addition. User Group Others read-write-execute read-write-execute read-write-execute 4-2-1 4-2-1 4-2-1 E.g. 750 = 4+2+1,4+1,0 = rwxr-x--- • Use the chmod command to set permissions: chmod 750 myfile chmod u=rwx,g=rx,o= myfile File Permissions User Group Others read-write-execute read-write-execute read-write-execute 4-2-1 4-2-1 4-2-1 • The group applies to the group associated with the file/directory. • Change the group of a file with the chgrp command. Exercise 5 Create a file and change its permissions: cd ~ cat /etc/motd > mymotd ls -l chmod 700 mymotd ls -l chmod 644 mymotd ls -l IV. THE VI EDITOR vi Concepts Two modes: • Command Mode: Enter commands to delete, cut, paste, save, quit, etc. • Text Entry Mode: Type characters in file • If you can’t tell which mode you’re in, press ESC and you will then be in command mode • vi is case-sensitive: J and j do very different things! • To use vi: • at command prompt type vi filename to edit/create file filename • type vi without filename to open new buffer Vi Commands See vi commands handout Getting into text entry mode: type i a o or O in command mode . redo most recent command u undo most recent command $ go to end of line 0 (zero) go to beginning of line More useful vi commands ➡ vi <filename> Moving around: ➡ hjkl or cursor keys to move one char/line ➡ w to move a word at a time ➡ ^ and $ for start and end of line Editing text: (two modes - move and edit, ESC to return to move) ➡ i or I for inserting text, ESC to finish ➡ a or A to append text, ESC to finish ➡ dd to delete a line ➡ cw to change a word, ESC to finish ➡ u to undo last command Saving/closing files: ➡ :w <enter> to save ➡ :wq <enter> save and quit (or ZZ) ➡ :q! <enter> to quit without saving Exercise 6 ➡ cd ~ ➡ vi mymotd Edit some text: ➡ Type “i” to insert text, then type: ➡ Today I’ve learnt a bit about Linux which should help me to use supercomputers and is just a cool thing to know! ➡ Press “esc” to exit editing mode Changing text and moving around: ➡ Use hjkl or cursor keys to move to the L in Linux and type “i” to insert the word “using”, then press “esc” ➡ Type w to move a word at a time across to the start of the word “should”, then type “cw” to change the word... type “will” and press “esc” ➡ Move the cursor to the word cool, then type $ to go to the end of line, type “a” to append and put a few more exclamation marks in Saving/closing files: ➡ :wq <enter> save and quit (or ZZ) Exercise 7 Creating a file to edit: ➡ cd ~ ➡ vi myscript Edit some text: ➡ Type “i” to insert text, then type: #!/bin/bash echo echo "Hello World!" echo ➡ Press “esc” to exit editing mode Saving/closing file: ➡ :wq <enter> save and quit (or ZZ) Changing permission on the file: ➡ At the prompt, type: chmod 700 myscript Running the script: ➡ At the prompt, type: ./myscript Exercise 8 - bonus Ideas for another script: #!/bin/bash cd STR=”Experiment run" echo $STR $1 $(date) # mkdir $1 cd $1 touch testdata # could be a wget, cp, scp for i in `seq 1 10`; do mkdir $1$i copy testdata $1$i done # For i in $( ls ); do echo Processing item: $i done cd OF=~/backups-$!-$(date +%Y%m%d).tgz Tar –cZf $OF ~/$1 Things you can do now… • Remotely log in to Pawsey machines • Transfer files to and from Pawsey machines • Run commands • Change file permissions to share with colleagues • Change file permissions to make scripts executable • Organise files into directories • Edit text files, including code and scripts • Write scripts to automate repetitive tasks Further Help Unix / Linux Tutorial for Beginners http://www.ee.surrey.ac.uk/Teaching/Unix/ UNIX Command Summary http://linuxconfig.org/linux-commands Do a Google image search for “vi cheat sheet”.
Load more

Recommended publications
  • Useful Commands in Linux and Other Tools for Quality Control
    Useful commands in Linux and other tools for quality control Ignacio Aguilar INIA Uruguay 05-2018 Unix Basic Commands pwd show working directory ls list files in working directory ll as before but with more information mkdir d make a directory d cd d change to directory d Copy and moving commands To copy file cp /home/user/is . To copy file directory cp –r /home/folder . to move file aa into bb in folder test mv aa ./test/bb To delete rm yy delete the file yy rm –r xx delete the folder xx Redirections & pipe Redirection useful to read/write from file !! aa < bb program aa reads from file bb blupf90 < in aa > bb program aa write in file bb blupf90 < in > log Redirections & pipe “|” similar to redirection but instead to write to a file, passes content as input to other command tee copy standard input to standard output and save in a file echo copy stream to standard output Example: program blupf90 reads name of parameter file and writes output in terminal and in file log echo par.b90 | blupf90 | tee blup.log Other popular commands head file print first 10 lines list file page-by-page tail file print last 10 lines less file list file line-by-line or page-by-page wc –l file count lines grep text file find lines that contains text cat file1 fiel2 concatenate files sort sort file cut cuts specific columns join join lines of two files on specific columns paste paste lines of two file expand replace TAB with spaces uniq retain unique lines on a sorted file head / tail $ head pedigree.txt 1 0 0 2 0 0 3 0 0 4 0 0 5 0 0 6 0 0 7 0 0 8 0 0 9 0 0 10
    [Show full text]
  • A Brief Introduction to Unix-2019-AMS
    A Brief Introduction to Linux/Unix – AMS 2019 Pete Pokrandt UW-Madison AOS Systems Administrator [email protected] Twitter @PTH1 Brief Intro to Linux/Unix o Brief History of Unix o Basics of a Unix session o The Unix File System o Working with Files and Directories o Your Environment o Common Commands Brief Intro to Unix (contd) o Compilers, Email, Text processing o Image Processing o The vi editor History of Unix o Created in 1969 by Kenneth Thompson and Dennis Ritchie at AT&T o Revised in-house until first public release 1977 o 1977 – UC-Berkeley – Berkeley Software Distribution (BSD) o 1983 – Sun Workstations produced a Unix Workstation o AT&T unix -> System V History of Unix o Today – two main variants, but blended o System V (Sun Solaris, SGI, Dec OSF1, AIX, linux) o BSD (Old SunOS, linux, Mac OSX/MacOS) History of Unix o It’s been around for a long time o It was written by computer programmers for computer programmers o Case sensitive, mostly lowercase abbreviations Basics of a Unix Login Session o The Shell – the command line interface, where you enter commands, etc n Some common shells Bourne Shell (sh) C Shell (csh) TC Shell (tcsh) Korn Shell (ksh) Bourne Again Shell (bash) [OSX terminal] Basics of a Unix Login Session o Features provided by the shell n Create an environment that meets your needs n Write shell scripts (batch files) n Define command aliases n Manipulate command history n Automatically complete the command line (tab) n Edit the command line (arrow keys in tcsh) Basics of a Unix Login Session o Logging in to a unix
    [Show full text]
  • Gnu Coreutils Core GNU Utilities for Version 5.93, 2 November 2005
    gnu Coreutils Core GNU utilities for version 5.93, 2 November 2005 David MacKenzie et al. This manual documents version 5.93 of the gnu core utilities, including the standard pro- grams for text and file manipulation. Copyright c 1994, 1995, 1996, 2000, 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”. Chapter 1: Introduction 1 1 Introduction This manual is a work in progress: many sections make no attempt to explain basic concepts in a way suitable for novices. Thus, if you are interested, please get involved in improving this manual. The entire gnu community will benefit. The gnu utilities documented here are mostly compatible with the POSIX standard. Please report bugs to [email protected]. Remember to include the version number, machine architecture, input files, and any other information needed to reproduce the bug: your input, what you expected, what you got, and why it is wrong. Diffs are welcome, but please include a description of the problem as well, since this is sometimes difficult to infer. See section “Bugs” in Using and Porting GNU CC. This manual was originally derived from the Unix man pages in the distributions, which were written by David MacKenzie and updated by Jim Meyering.
    [Show full text]
  • Gnu Coreutils Core GNU Utilities for Version 6.9, 22 March 2007
    gnu Coreutils Core GNU utilities for version 6.9, 22 March 2007 David MacKenzie et al. This manual documents version 6.9 of the gnu core utilities, including the standard pro- grams for text and file manipulation. Copyright c 1994, 1995, 1996, 2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License". Chapter 1: Introduction 1 1 Introduction This manual is a work in progress: many sections make no attempt to explain basic concepts in a way suitable for novices. Thus, if you are interested, please get involved in improving this manual. The entire gnu community will benefit. The gnu utilities documented here are mostly compatible with the POSIX standard. Please report bugs to [email protected]. Remember to include the version number, machine architecture, input files, and any other information needed to reproduce the bug: your input, what you expected, what you got, and why it is wrong. Diffs are welcome, but please include a description of the problem as well, since this is sometimes difficult to infer. See section \Bugs" in Using and Porting GNU CC. This manual was originally derived from the Unix man pages in the distributions, which were written by David MacKenzie and updated by Jim Meyering.
    [Show full text]
  • Ed: a Context Editor for the Cp/M Disk System User's
    Post Office Box 579, Pacific Grove, California 93950, (408) 373-3403 ED: A CONTEXT EDITOR FOR THE CP/M DISK SYSTEM USER'S MANUAL COPYRIGHT © 1976, 1978 DIGIT AL RESEARCH r Copyright © 1976, 1978 by Digital Research. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or trans­ lated into any language or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, without the prior written permission of Digital Research, Post Office Box 579, Pacific Grove, California 93950. Disclaimer Digital Research makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Further, Digital Research reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of Digital Research to notify any person of such revision or changes. Table of Contents 1. ED TUTORIAL • · · · • • · • • 1 l~l Introduction to ED • . 1 1.2 ED Operation .•. 1 1.3 Text Transfer Functions 1 1.4 Memory Buffer Organization. 5 1.5 Memory Buffer Operation..•. 5 1.6 Command Strings 7 1.7 Text Search and Alteration. • • 8 1.8 Source Libraries . • • • . • • 11 1.9 Repetitive Command Execution •• • • 12 2. ED"ERROR CONDITIONS •• . • 13 3. CONTROL CHARACTERS AND COMMANDS . 14 ii ED USER'S MANUAL 1. ED TUTORIAL 1.1. Introduction to ED. ED is the context editor for CP/M, and is used to create and alter CP/M source files.
    [Show full text]
  • Controlling Gpios on Rpi Using Ping Command
    Ver. 3 Department of Engineering Science Lab – Controlling PI Controlling Raspberry Pi 3 Model B Using PING Commands A. Objectives 1. An introduction to Shell and shell scripting 2. Starting a program at the Auto-start 3. Knowing your distro version 4. Understanding tcpdump command 5. Introducing tshark utility 6. Interfacing RPI to an LCD 7. Understanding PING command B. Time of Completion This laboratory activity is designed for students with some knowledge of Raspberry Pi and it is estimated to take about 5-6 hours to complete. C. Requirements 1. A Raspberry Pi 3 Model 3 2. 32 GByte MicroSD card à Give your MicroSD card to the lab instructor for a copy of Ubuntu. 3. USB adaptor to power up the Pi 4. Read Lab 2 – Interfacing with Pi carefully. D. Pre-Lab Lear about ping and ICMP protocols. F. Farahmand 9/30/2019 1 Ver. 3 Department of Engineering Science Lab – Controlling PI E. Lab This lab has two separate parts. Please make sure you read each part carefully. Answer all the questions. Submit your codes via Canvas. 1) Part I - Showing IP Addresses on the LCD In this section we learn how to interface an LCD to the Pi and run a program automatically at the boot up. a) Interfacing your RPI to an LCD In this section you need to interface your 16×2 LCD with Raspberry Pi using 4-bit mode. Please note that you can choose any type of LCD and interface it to your PI, including OLED. Below is the wiring example showing how to interface a 16×2 LCD to RPI.
    [Show full text]
  • Lecture 18 Regular Expressions the Grep Command
    Lecture 18 Regular Expressions Many of today’s web applications require matching patterns in a text document to look for specific information. A good example is parsing a html file to extract <img> tags of a web document. If the image locations are available, then we can write a script to automatically download these images to a location we specify. Looking for tags like <img> is a form of searching for a pattern. Pattern searches are widely used in many applications like search engines. A regular expression(regex) is defined as a pattern that defines a class of strings. Given a string, we can then test if the string belongs to this class of patterns. Regular expressions are used by many of the unix utilities like grep, sed, awk, vi, emacs etc. We will learn the syntax of describing regex later. Pattern search is a useful activity and can be used in many applications. We are already doing some level of pattern search when we use wildcards such as *. For example, > ls *.c Lists all the files with c extension or ls ab* lists all file names that starts with ab in the current directory. These type of commands (ls,dir etc) work with windows, unix and most operating systems. That is, the command ls will look for files with a certain name patterns but are limited in ways we can describe patterns. The wild card (*) is typically used with many commands in unix. For example, cp *.c /afs/andrew.cmu.edu/course/15/123/handin/Lab6/guna copies all .c files in the current directory to the given directory Unix commands like ls, cp can use simple wild card (*) type syntax to describe specific patterns and perform the corresponding tasks.
    [Show full text]
  • Product Datasheet Ls Ay Sup -Cp/P2/500
    PRODUCT DATASHEET LS AY SUP -CP/P2/500 LED STRIP VALUE-600 | LED strips with 600 lm/m for general applications Areas of application − General outdoor illumination Product benefits − Easy installation of connector, no manual wiring required − Tool-free installation September 25, 2021, 10:17:31 © 2021, LEDVANCE GmbH. All rights reserved. LS AY SUP -CP/P2/500 Page 1 of 3 PRODUCT DATASHEET TECHNICAL DATA Electrical data Nominal voltage 25 V Nominal current 5000 mA Dimensions & Weight Length 509.8 mm Cable length 500 mm Width 9.8 mm Width (incl. round luminaires) 9.8 mm Height 5.7 mm Height (incl. round luminaires) 5.7 mm Cable cross-section, input side 0.34 mm² Product weight 5.00 g Colors & materials Product color White Temperatures & operating conditions Ambient temperature range -35…+75 °C Temperature range in operation -35…+75 °C Certificates & Standards Type of protection IP00 LOGISTICAL DATA Temperature range at storage -5…+55 °C DOWNLOAD DATA DOWNLOAD DATA Catalogs LEDVANCE LED Strip System - Wave 2 - Fall 2020 (EN) LOGISTICAL DATA Product code Packaging unit (Pieces/Unit) Dimensions (length x width x height) Gross weight Volume BAG 4058075304413 80 mm x 120 mm x 5 mm 11.00 g 0.05 dm³ 2 Shipping box 4058075304420 213 mm x 213 mm x 215 mm 677.00 g 9.75 dm³ 100 September 25, 2021, 10:17:31 © 2021, LEDVANCE GmbH. All rights reserved. LS AY SUP -CP/P2/500 Page 2 of 3 PRODUCT DATASHEET Product code Packaging unit (Pieces/Unit) Dimensions (length x width x height) Gross weight Volume SHIPPING BOX FOR 5TH-LEVEL 4058075304437 439 mm x 439 mm x 233 mm 3306.00 g 44.90 dm³ 400 The mentioned product code describes the smallest quantity unit which can be ordered.
    [Show full text]
  • GPL-3-Free Replacements of Coreutils 1 Contents
    GPL-3-free replacements of coreutils 1 Contents 2 Coreutils GPLv2 2 3 Alternatives 3 4 uutils-coreutils ............................... 3 5 BSDutils ................................... 4 6 Busybox ................................... 5 7 Nbase .................................... 5 8 FreeBSD ................................... 6 9 Sbase and Ubase .............................. 6 10 Heirloom .................................. 7 11 Replacement: uutils-coreutils 7 12 Testing 9 13 Initial test and results 9 14 Migration 10 15 Due to the nature of Apertis and its target markets there are licensing terms that 1 16 are problematic and that forces the project to look for alternatives packages. 17 The coreutils package is good example of this situation as its license changed 18 to GPLv3 and as result Apertis cannot provide it in the target repositories and 19 images. The current solution of shipping an old version which precedes the 20 license change is not tenable in the long term, as there are no upgrades with 21 bugfixes or new features for such important package. 22 This situation leads to the search for a drop-in replacement of coreutils, which 23 need to provide compatibility with the standard GNU coreutils packages. The 24 reason behind is that many other packages rely on the tools it provides, and 25 failing to do that would lead to hard to debug failures and many custom patches 26 spread all over the archive. In this regard the strict requirement is to support 27 the features needed to boot a target image with ideally no changes in other 28 components. The features currently available in our coreutils-gplv2 fork are a 29 good approximation. 30 Besides these specific requirements, the are general ones common to any Open 31 Source Project, such as maturity and reliability.
    [Show full text]
  • GNU Coreutils Core GNU Utilities for Version 9.0, 20 September 2021
    GNU Coreutils Core GNU utilities for version 9.0, 20 September 2021 David MacKenzie et al. This manual documents version 9.0 of the GNU core utilities, including the standard pro- grams for text and file manipulation. Copyright c 1994{2021 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License". i Short Contents 1 Introduction :::::::::::::::::::::::::::::::::::::::::: 1 2 Common options :::::::::::::::::::::::::::::::::::::: 2 3 Output of entire files :::::::::::::::::::::::::::::::::: 12 4 Formatting file contents ::::::::::::::::::::::::::::::: 22 5 Output of parts of files :::::::::::::::::::::::::::::::: 29 6 Summarizing files :::::::::::::::::::::::::::::::::::: 41 7 Operating on sorted files ::::::::::::::::::::::::::::::: 47 8 Operating on fields ::::::::::::::::::::::::::::::::::: 70 9 Operating on characters ::::::::::::::::::::::::::::::: 80 10 Directory listing:::::::::::::::::::::::::::::::::::::: 87 11 Basic operations::::::::::::::::::::::::::::::::::::: 102 12 Special file types :::::::::::::::::::::::::::::::::::: 125 13 Changing file attributes::::::::::::::::::::::::::::::: 135 14 File space usage ::::::::::::::::::::::::::::::::::::: 143 15 Printing text :::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • LS-50-Cp 3U Compact-PCI Multi-Function PCM Decommutator Data Sheet
    LUMISTAR LS-50-cP 3U Compact-PCI Multi-function PCM Decommutator Data Sheet Description: The Lumistar LS-50-cP 3U Compact PCI Multi-function PCM Decommutator offers the greatest flexibility in the industry by incorporating up to 10 functions typically encountered in flight test applications in a single 3U Compact-PCI card slot. Five functions are achieved on the main board (PCM Simulator which can also operate as a BERT, PCM Decommutator, IRIG Time Code Reader, IRIG Time Code Generator, and the same 5 functions can be achieved on the LS-55-DB Multi-Function Decom Daughterboard. CVSD Voice Decoding and h.261 Video Decoding are achieved through software. The IRIG Time Code Reader and Generator operate with IRIG A, B, or G time codes. The Time Code Generator creates and outputs time information in accordance with the IRIG time code standard. The Time Code Reader is typically used to insert time information into the PCM minor frame block of data. The Lumistar LS-50 Decom can be used for extremely large formats (16,383 words per minor frame up to 1,024 frames deep) and contains dual ping-pong data buffers with up to 128K bytes of memory. The LS-55-DB daughterboard decom can be used for an independent PCM data stream or an embedded PCM data stream in accordance with the IRIG-106 Telemetry Standards. The PCM simulator generates common, unique, and waveform pattern data words. When used with the LS-55-DB daughterboard, the user can generate complex data streams with embedded PCM data, or two totally independent data streams.
    [Show full text]
  • Laboratory 5115-16
    2020 CDOT LMTP 8-01-2021 CP-L 5115 Colorado Procedure – Laboratory 5115-16 Standard Method of Test for Preparing and Determining the Density of Bituminous Mixture Test Specimens Compacted by the Superpave Gyratory Compactor (This procedure is based upon AASHTO T 312-14. AASHTO T 312-14 or any subsequent revision may not be used in place of this procedure.) 1. SCOPE 1.1 This standard covers the compaction of 150 mm diameter and 100 mm diameter test specimens of hot mix asphalt (HMA) using the Superpave gyratory compactor. 1.2 The values stated in SI units are to be regarded as the standard. 1.3 This standard may involve hazardous materials, operations, and equipment. This standard does not purport to address all of the safety problems associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory limitations before use. 2. REFERENCED DOCUMENTS 2.1 AASHTO Standards: • T 312 Preparing and Determining the Density of Asphalt Mixture Specimens using the Superpave Gyratory Compactor • M 231 Weighing Devices Used in the Testing of Materials 2.2 Colorado Procedures: • CP 44 Bulk Specific Gravity and Percent Relative Compaction of Compacted Bituminous Mixtures Using Saturated Surface-Dry Specimens • CP 51 Determining the Maximum Specific Gravity of HMA • CP-L 5101 Verification of Laboratory Equipment Used to Test Bituminous Mixtures • CP-L 5106 Resistance to Deformation of Bituminous Mixtures by Means of Hveem Apparatus • CP-L 5109 Resistance of Compacted Bituminous Mixture to Moisture Induced Damage 2.3 Other Standards: • ASME B46.1 Surface Texture (Surface Roughness, Waviness, and Lay) Page 1 of 10 2020 CDOT LMTP 8-01-2021 CP-L 5115 3.
    [Show full text]