DOCSLIB.ORG

$ Who Am I Mumbo Jumbo?

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
$ Who Am I Mumbo Jumbo? Unix Crash Course Subjects (after lunch) ● Networking and the X windowing system ● Shell scripting concepts ● Regular expressions ● sed and awk ● Miscelanious (editing and programming) Unix Crash Course Slide 1 Unix Crash Course Slide 4 $ who am i Mumbo Jumbo? ● Rob Wolfram ● Unix System administrator ● E-mail: [email protected] ● PGP Key: 0xF7A0F7A0 Unix Crash Course Slide 2 Unix Crash Course Slide 5 Subjects (before lunch) Unix History ● A short history of Unix and Linux ● AT&T abandoned MULTICS ● Structure and philosophy of Unix ● Ken Thompson & Dennis Ritchie developed UNICS on a PDP7 ● Files and filesystems ● UNIX ported to Ritchie's C language ● Shell variables and globbing ● BSD released, many ports followed ● Processes and jobs ● POSIX effort to unify Unices ● GNU project / Linux kernel Unix Crash Course Slide 3 Unix Crash Course Slide 6 Unix History Unix philosophy ● Everything is a file ● Combine small tools to build your requirement Ritchie and Thompson working on a PDP11/20 at Bell Labs Unix Crash Course Slide 7 Unix Crash Course Slide 10 Unix History Unix structure Unix has an onion-like structure, the hardware is handled by the kernel Unix Crash Course Slide 8 Unix Crash Course Slide 11 (Gnu/) Linux distros Kernel provisions The kernel provides: ● CPU scheduling of processes ● Accessing hardware ● System calls for user-land programs ● The filesystem ● Privilege separation etc. Unix Crash Course Slide 9 Unix Crash Course Slide 12 Multi-user environment File permissions ● Unix runs programs from multiple users concurrently, even interactive programs ● User identified by numeric id, user name provided for verbosity ● User is member of one or more groups, identified by group id ● Interactive sessions need a TTY for input and output Unix Crash Course Slide 13 Unix Crash Course Slide 16 The filesystem Lab 1 A single unified tree of multiple filesystems ● ls -l ● cat README ● chmod a+r README ● ls -l ● cat README Unix Crash Course Slide 14 Unix Crash Course Slide 17 Inodes The Shell ● There are various shells available: – sh: the Bourne shell – csh: the C shell – ksh: the Korn shell – tcsh: the TENEX C shell – bash: the Bourne-Again shell – zsh: the Z shell Unix Crash Course Slide 15 Unix Crash Course Slide 18 The Shell Special variables ● The shell interprets entered commands Syntax: command argument_list $PATH $0 $MANPATH $1 - $9 ● Arguments are separated by white space $LD_LIBRARY_PATH $# Certain arguments (usually single characters $HOME $* preceded by a dash change the program's $USER $@ $PWD $? behaviour and are called “options” $SHELL $$ ● The shell will perform command substitution, $PS1 $! variable expansion and globbing and execute $PS2 the command with modified command line. All these steps depend on quoting. Unix Crash Course Slide 19 Unix Crash Course Slide 22 Frequent commands Quoting Variables expand in double quotes, not in single man chmod wc quotes. Backslashes “escape” a single echo chown more read chgrp date character: ls umask time $ HW="Hello, World." cp cat tar $ echo "$HW" mv head gzip Hello, World. ln tail compress $ echo '$HW' rm cut xargs $HW pwd grep tee $ echo \$HW cd sed expr $HW mkdir sort awk $ echo \\$HW rmdir uniq find \Hello, World. $ Unix Crash Course Slide 20 Unix Crash Course Slide 23 Shell variables Command substitution Using shell variables: Use “backquotes” for command substitution: $ echo $HW $ wc log.`date +%Y%m%d` $ HW="Hello, World." 1 8 54 log.20131102 $ echo $HW $ Hello, World. $ On modern shells, $( ) is allowed. This enables nesting: Export variables to make them visible in a sub- bash$ wc log.$(expr $(date +%Y%m%d) – 100) shell: 630 1616 40744 log.20131002 $ export VARIABLE bash$ Use curly braces to disambiguate variables: $ echo ${VARIABLE}more_text Unix Crash Course Slide 21 Unix Crash Course Slide 24 Globbing Redirection ● The asterisk (*) expands to zero or more ● Three file descriptors: characters (e.g. “ls foo*”) – FD0 is standard input (stdin) ● The question mark expands to exactly one – FD1 is standard output (stdout) character (e.g. “ls /etc/?asswd”) – FD2 is standard error (stderr) ● Characters in square brackets expand to one ● More are available for advanced use character from the list. Ranges are allowed. ● Redirect output with and input with (e.g. (“ ”). Negate the list with an > < ls foo.[abc0-9] “ ” or “ ” (FD is exclamation mark (“ ”). command 1> file command 0< file ls foo.[!abc0-9] optional for stdin and stdout) Unix Crash Course Slide 25 Unix Crash Course Slide 28 Globbing Redirection ● On modern Unices, the tilde (~) expands to the ● Connect file descriptors with >& construct: users homedirectory and “~foo” to the (command > file 2> &1) homedirectory of user “foo” ● > overwrites the output file or create a new ● Globbing is handled by the shell, the executed one, command doesn't know if globbing occurred >> will append to the file instead – Notice that this can cause an error of an oversized ● << is called a “here document” and used in argument list scripts. Unix Crash Course Slide 26 Unix Crash Course Slide 29 Lab 2 Pipes ● A pipe connects stdout of a command to stdin of the next ● File & directory management This is central to the Unix philosophy, i.e. ● Variable substitution create small but powerful tools and connect ● Command substitution them Example: ● Globbing ls /tmp | wc -l ● stderr can't be piped alone, only with stdout Unix Crash Course Slide 27 Unix Crash Course Slide 30 tee and xargs Forking ● Two commands used a lot with pipes: ● The shell will start a “child process”. The tee and xargs. Examples: command will be executed in this process. ● Save log output and count entries: ● After the child exits, it signals the “parent”. grep 10.1.2.3 /var/log/apache/access.log \ ● | tee /tmp/rogueclient.txt | wc -l Changed environment in child is not visible in the parent (variables, current directory) ● Search for text in files that are less than 4 days old: ● Parent variables should be “exported” to be find /var/log -mtime -4 -print | xargs \ visible in the child (export VARNAME) grep -l 'kernel error' ● Executing a shell in current process is called “sourcing” (. scriptfile) Unix Crash Course Slide 31 Unix Crash Course Slide 34 Grouping Processes Combine stdout of multiple commands with () or ● Every process has a “process id” {}. Parentheses work in sub-shell, braces in ● Use ps to retrieve information of processes current shell: ● Use kill to send processes a signal $ echo Foo ; echo Bar | wc Some signals (e.g. SIGINT) are handled by the Foo program, others (e.g. SIGKILL) are handled by 1 1 4 the kernel $ { echo Foo ; echo Bar ;} | wc 2 2 8 $ (echo Foo ; echo Bar) | wc 2 2 8 $ Unix Crash Course Slide 32 Unix Crash Course Slide 35 Lab 3 Jobs ● A process can be started in the background by appending an ampersand (&) to the CL ● Redirection and piping ● A program is suspended by sending it a SIGSTOP (e.g. by pressing CTRL-Z) ● jobs gives a list of all suspended and backgrounded processes ● fg and bg continue running a process in the foreground or background respectively (job id may be appended with % sign Unix Crash Course Slide 33 Unix Crash Course Slide 36 Scheduling Networking ● Run a program unattended later with at: ● Interactive shells and file sharing can be echo "find /tmp -mtime +30 | xargs rm -f"\ started from networked hosts | at 20:08 tomorrow ● Common tools: ● Schedule regularly with cron. Syntax: min hou dom mon dow command [arguments] – telnet Example: – ftp 5 * * 3,6 2 echo foo >> /tmp/myfile – “rsh” tools (rsh, rlogin, rcp) – secure shell suite (ssh, scp, sftp) ● Pseudo-TTY's are assigned to interactive networked shells Unix Crash Course Slide 37 Unix Crash Course Slide 40 Shell Initialization The X Windowing System ● The shell will source files on login or other ● The standard Unix GUI (X) is networked startup. based. Consists of an “X server” (which can – sh, ksh: /etc/profile, $HOME/.profile (on display graphics and handle keyboard and login) mouse) and an “X client” (a program requesting graphical output. – bash: /etc/profile, $HOME/.bash_profile, $HOME/.profile (on login) ● The X server is identified by the $DISPLAY /etc/bash.bashrc, $HOME/.bashrc (interactive) variable (e.g. myscreen.example.com:0.0) Unix Crash Course Slide 38 Unix Crash Course Slide 41 Lunch The X Windowing System See you in half an hour Unix Crash Course Slide 39 Unix Crash Course Slide 42 X server access Shell flow: case ● Host based access: (dis)allow all users access ● Syntax: to the X server. Syntax: xhost +|- [hostname] case string in valuelist1) ● Cookie based access. List cookie on X server command list and add it to the .Xauthority file from the user ;; running the X client. xauth is used for cookie valuelist2) command list management ;; ● ssh can automate the xauth process and pass ... valuelistn) X traffic via encrypted tunnel. command list ;; esac Unix Crash Course Slide 43 Unix Crash Course Slide 46 Shell scripting Shell flow: case ● A “shebang” is needed to tell the OS what ● Valuelists consist of one or more patterns to script language is used. Syntax: match against the string, separated by pipes #!/bin/sh (|) ● Functions are “named groupings” and are not ● Shell globbing syntax is allowed when executed at time of declaration. Syntax: matching the string shfunc() { commandlist ; } ● Only the first matching entry is executed ● Here document redirects stdin from the script: command << WORD first line of stdin last line of stdin WORD Unix Crash Course Slide 44 Unix Crash Course Slide 47 Shell flow: if Shell flow: while ● Syntax: ● Repeat a block of commands as long as the if command constraint is valid. Syntax: then while command command list do elif command command list then done command list or else until command command list do fi command list ● Alternative: done command1 && command2 || command3 ● Exit or restart the loop with break or continue Unix Crash Course Slide 45 Unix Crash Course Slide 48 Shell flow: for Lab 4 ● Repeat a loop a number of times while assigning a value to a variable.
Load more

Recommended publications
  • Linux Commands Cheat Sheet
    LINUX COMMANDS CHEAT SHEET System File Permission uname => Displays Linux system information chmod octal filename => Change file permissions of the file to octal uname -r => Displays kernel release information Example uptime => Displays how long the system has been running including chmod 777 /data/test.c => Set rwx permissions to owner, group and everyone (every- load average one else who has access to the server) hostname => Shows the system hostname chmod 755 /data/test.c => Set rwx to the owner and r_x to group and everyone hostname -i => Displays the IP address of the system chmod 766 /data/test.c => Sets rwx for owner, rw for group and everyone last reboot => Shows system reboot history chown owner user-file => Change ownership of the file date => Displays current system date and time chown owner-user: owner-group => Change owner and group owner of the file timedatectl => Query and change the System clock file_name chown owner-user:owner-group- => Change owner and group owner of the directory cal => Displays the current calendar month and day directory w => Displays currently logged in users in the system whoami => Displays who you are logged in as Network finger username => Displays information about the user ip addr show => Displays IP addresses and all the network interfaces Hardware ip address add => Assigns IP address 192.168.0.1 to interface eth0 192.168.0.1/24 dev eth0 dmesg => Displays bootup messages ifconfig => Displays IP addresses of all network interfaces cat /proc/cpuinfo => Displays more information about CPU e.g model, model name, cores, vendor id ping host => ping command sends an ICMP echo request to establish a connection to server / PC cat /proc/meminfo => Displays more information about hardware memory e.g.
    [Show full text]
  • Chapter 19 RECOVERING DIGITAL EVIDENCE from LINUX SYSTEMS
    Chapter 19 RECOVERING DIGITAL EVIDENCE FROM LINUX SYSTEMS Philip Craiger Abstract As Linux-kernel-based operating systems proliferate there will be an in­ evitable increase in Linux systems that law enforcement agents must process in criminal investigations. The skills and expertise required to recover evidence from Microsoft-Windows-based systems do not neces­ sarily translate to Linux systems. This paper discusses digital forensic procedures for recovering evidence from Linux systems. In particular, it presents methods for identifying and recovering deleted files from disk and volatile memory, identifying notable and Trojan files, finding hidden files, and finding files with renamed extensions. All the procedures are accomplished using Linux command line utilities and require no special or commercial tools. Keywords: Digital evidence, Linux system forensics !• Introduction Linux systems will be increasingly encountered at crime scenes as Linux increases in popularity, particularly as the OS of choice for servers. The skills and expertise required to recover evidence from a Microsoft- Windows-based system, however, do not necessarily translate to the same tasks on a Linux system. For instance, the Microsoft NTFS, FAT, and Linux EXT2/3 file systems work differently enough that under­ standing one tells httle about how the other functions. In this paper we demonstrate digital forensics procedures for Linux systems using Linux command line utilities. The ability to gather evidence from a running system is particularly important as evidence in RAM may be lost if a forensics first responder does not prioritize the collection of live evidence. The forensic procedures discussed include methods for identifying and recovering deleted files from RAM and magnetic media, identifying no- 234 ADVANCES IN DIGITAL FORENSICS tables files and Trojans, and finding hidden files and renamed files (files with renamed extensions.
    [Show full text]
  • “Linux at the Command Line” Don Johnson of BU IS&T  We’Ll Start with a Sign in Sheet
    “Linux at the Command Line” Don Johnson of BU IS&T We’ll start with a sign in sheet. We’ll end with a class evaluation. We’ll cover as much as we can in the time allowed; if we don’t cover everything, you’ll pick it up as you continue working with Linux. This is a hands-on, lab class; ask questions at any time. Commands for you to type are in BOLD The Most Common O/S Used By BU Researchers When Working on a Server or Computer Cluster Linux is a Unix clone begun in 1991 and written from scratch by Linus Torvalds with assistance from a loosely-knit team of hackers across the Net. 64% of the world’s servers run some variant of Unix or Linux. The Android phone and the Kindle run Linux. a set of small Linux is an O/S core programs written by written by Linus Richard Stallman and Torvalds and others others. They are the AND GNU utilities. http://www.gnu.org/ Network: ssh, scp Shells: BASH, TCSH, clear, history, chsh, echo, set, setenv, xargs System Information: w, whoami, man, info, which, free, echo, date, cal, df, free Command Information: man, info Symbols: |, >, >>, <, ;, ~, ., .. Filters: grep, egrep, more, less, head, tail Hotkeys: <ctrl><c>, <ctrl><d> File System: ls, mkdir, cd, pwd, mv, touch, file, find, diff, cmp, du, chmod, find File Editors: gedit, nedit You need a “xterm” emulation – software that emulates an “X” terminal and that connects using the “SSH” Secure Shell protocol. ◦ Windows Use StarNet “X-Win32:” http://www.bu.edu/tech/support/desktop/ distribution/xwindows/xwin32/ ◦ Mac OS X “Terminal” is already installed Why? Darwin, the system on which Apple's Mac OS X is built, is a derivative of 4.4BSD-Lite2 and FreeBSD.
    [Show full text]
  • The Linux Command Line
    The Linux Command Line Fifth Internet Edition William Shotts A LinuxCommand.org Book Copyright ©2008-2019, William E. Shotts, Jr. This work is licensed under the Creative Commons Attribution-Noncommercial-No De- rivative Works 3.0 United States License. To view a copy of this license, visit the link above or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042. A version of this book is also available in printed form, published by No Starch Press. Copies may be purchased wherever fine books are sold. No Starch Press also offers elec- tronic formats for popular e-readers. They can be reached at: https://www.nostarch.com. Linux® is the registered trademark of Linus Torvalds. All other trademarks belong to their respective owners. This book is part of the LinuxCommand.org project, a site for Linux education and advo- cacy devoted to helping users of legacy operating systems migrate into the future. You may contact the LinuxCommand.org project at http://linuxcommand.org. Release History Version Date Description 19.01A January 28, 2019 Fifth Internet Edition (Corrected TOC) 19.01 January 17, 2019 Fifth Internet Edition. 17.10 October 19, 2017 Fourth Internet Edition. 16.07 July 28, 2016 Third Internet Edition. 13.07 July 6, 2013 Second Internet Edition. 09.12 December 14, 2009 First Internet Edition. Table of Contents Introduction....................................................................................................xvi Why Use the Command Line?......................................................................................xvi
    [Show full text]
  • Configuration and Administration of Networking for Fedora 23
    Fedora 23 Networking Guide Configuration and Administration of Networking for Fedora 23 Stephen Wadeley Networking Guide Draft Fedora 23 Networking Guide Configuration and Administration of Networking for Fedora 23 Edition 1.0 Author Stephen Wadeley [email protected] Copyright © 2015 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https://fedoraproject.org/wiki/ Legal:Trademark_guidelines. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
    [Show full text]
  • Arxiv:1802.08979V2 [Cs.CL] 2 Mar 2018 Parsing Benchmarks (Dahl Et Al., 1994; Popescu Et Al., 2003)
    NL2Bash: A Corpus and Semantic Parser for Natural Language Interface to the Linux Operating System Xi Victoria Lin*, Chenglong Wang, Luke Zettlemoyer, Michael D. Ernst Salesforce Research, University of Washington, University of Washington, University of Washington [email protected], fclwang,lsz,[email protected] Abstract We present new data and semantic parsing methods for the problem of mapping English sentences to Bash commands (NL2Bash). Our long-term goal is to enable any user to perform operations such as file manipulation, search, and application-specific scripting by simply stating their goals in English. We take a first step in this domain, by providing a new dataset of challenging but commonly used Bash commands and expert-written English descriptions, along with baseline methods to establish performance levels on this task. Keywords: Natural Language Programming, Natural Language Interface, Semantic Parsing 1. Introduction We constructed the NL2Bash corpus with frequently used The dream of using English or any other natural language Bash commands scraped from websites such as question- to program computers has existed for almost as long as answering forums, tutorials, tech blogs, and course materi- the task of programming itself (Sammet, 1966). Although als. We gathered a set of high-quality descriptions of the significantly less precise than a formal language (Dijkstra, commands from Bash programmers. Table 1 shows several 1978), natural language as a programming medium would examples. After careful quality control, we were able to be universally accessible and would support the automation gather over 9,000 English-command pairs, covering over of highly repetitive tasks such as file manipulation, search, 100 unique Bash utilities.
    [Show full text]
  • Scripting in Axis Network Cameras and Video Servers
    Scripting in Axis Network Cameras and Video Servers Table of Contents 1 INTRODUCTION .............................................................................................................5 2 EMBEDDED SCRIPTS ....................................................................................................6 2.1 PHP .....................................................................................................................................6 2.2 SHELL ..................................................................................................................................7 3 USING SCRIPTS IN AXIS CAMERA/VIDEO PRODUCTS ......................................8 3.1 UPLOADING SCRIPTS TO THE CAMERA/VIDEO SERVER:...................................................8 3.2 RUNNING SCRIPTS WITH THE TASK SCHEDULER...............................................................8 3.2.1 Syntax for /etc/task.list.....................................................................................................9 3.3 RUNNING SCRIPTS VIA A WEB SERVER..............................................................................11 3.3.1 To enable Telnet support ...............................................................................................12 3.4 INCLUDED HELPER APPLICATIONS ..................................................................................13 3.4.1 The image buffer - bufferd........................................................................................13 3.4.2 sftpclient.........................................................................................................................16
    [Show full text]
  • Subcontractors – Bc, Xargs, Find
    Subcontractors – bc , xargs , find David Morgan © David Morgan 2011- 14 bc – math help for the shell interactive or programatic can accept its commands from stdin can accept an entire bc program’s worth © David Morgan 2011-14 1 bc – math help for shell bc, commanded interactively by user does what shell cannot e.g. high-precision math ( & much more ) bc, commanded non-interactively by shell shell, by extension, does high-precision can embed bc code wholesale as here document © David Morgan 2011-14 bc – shell script or bc interpreter script © David Morgan 2011-14 2 bc – math help for shell bc code, not bash shell code background: http://jeremykun.com/tag/simpsons-rule http://www.zweigmedia.com/RealWorld/integral/integral.html © David Morgan correct! 2011-14 bc – interactive math help for shell Wicked Cool Shell Scripts , Dave Taylor, p29 © David Morgan 2011-14 3 xargs produce list of vi’s backup files long list ‘em with xargs remove ‘em with xargs gone © David Morgan 2011-14 xargs filename too long to type command to avoid typing it what’s in the file? …oops cat needs filename as argument, not input xargs composes correct cat syntax by pasting its input onto cat’s command line produces: cat /root/class… etc etc produces: cat /etc/resolv.conf /root/class… etc etc xargs composes incorrect cp syntax by pasting its input onto cp’s command line produces: cp . /root/class… etc etc cp differs from cat, needs insertion from xargs not pasting control argument placement with xargs’ –I (xargs stuff goes where the special© char David appears, _ in this case) Morgan 2011-14 4 xargs and efficiency sleeptime totals 15 sec run sleeps simultaneously took 15 sec took 5 sec significant for compute-heavy commands distributes them across multi-cores – simultaneous execution © David Morgan 2011-14 xargs and efficiency commonly used with find to process files functionally equivalent – find .
    [Show full text]
  • USER MANUAL GWR High Speed Cellular Router Series
    GWR USER MANUAL GWR High Speed Cellular Router Series Document version 1.0.0 Date: December 2015 WWW.GENEKO.RS User Manual Document History Date Description Author Comments 24.12.2015 User Manual Tanja Savić Firmware versions: 1.1.2 Document Approval The following report has been accepted and approved by the following: Signature Printed Name Title Date Dragan Marković Executive Director 24.12.2015 GWR High Speed Cellular Router Series 2 User Manual Content DOCUMENT APPROVAL ........................................................................................................................................ 2 LIST OF FIGURES .................................................................................................................................................... 5 LIST OF TABLES ...................................................................................................................................................... 8 DESCRIPTION OF THE GPRS/EDGE/HSPA ROUTER SERIES ...................................................................... 9 TYPICAL APPLICATION ............................................................................................................................... 10 TECHNICAL PARAMETERS ......................................................................................................................... 11 PROTOCOLS AND FEATURES ...................................................................................................................... 14 PRODUCT OVERVIEW ...............................................................................................................................
    [Show full text]
  • GNU Findutils Finding Files Version 4.8.0, 7 January 2021
    GNU Findutils Finding files version 4.8.0, 7 January 2021 by David MacKenzie and James Youngman This manual documents version 4.8.0 of the GNU utilities for finding files that match certain criteria and performing various operations on them. 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, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License". i Table of Contents 1 Introduction ::::::::::::::::::::::::::::::::::::: 1 1.1 Scope :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.2 Overview ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 2 2 Finding Files ::::::::::::::::::::::::::::::::::::: 4 2.1 find Expressions ::::::::::::::::::::::::::::::::::::::::::::::: 4 2.2 Name :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 4 2.2.1 Base Name Patterns ::::::::::::::::::::::::::::::::::::::: 5 2.2.2 Full Name Patterns :::::::::::::::::::::::::::::::::::::::: 5 2.2.3 Fast Full Name Search ::::::::::::::::::::::::::::::::::::: 7 2.2.4 Shell Pattern Matching :::::::::::::::::::::::::::::::::::: 8 2.3 Links ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 8 2.3.1 Symbolic Links :::::::::::::::::::::::::::::::::::::::::::: 8 2.3.2 Hard Links ::::::::::::::::::::::::::::::::::::::::::::::: 10 2.4 Time
    [Show full text]
  • SYSTEM INFORMATION Hostname Internet (IP) Address Ethernet Address Hub and Port Numbers Emergency Contact Person Boot Command Di
    SYSTEM INFORMATION COMMON COMMAND EXAMPLES TOKENS USED IN SENDMAIL.CF Hostname ifconfig plumb # Solaris: probe for network interfaces Token Debug Meaning ifconfig lo0 127.0.0.1 up # Loopback interface ifconfig en0 inet 128.130.240.1 up netmask $@ Match zero tokens (V8 only) 0xFFFFFF00 broadcast 128.130.240.255 $- ^R Match exactly one token $+ ^Q Match one or more tokens Internet (IP) address route add net 128.130.138.0 128.130.240.12 1 $* ^P Match zero or more tokens route add default 128.130.240.12 1 $X Match value of macro variable X # BSD/OS and OSF/1 use –net and –host and no metric $&X Match value of X at run time route add –net 128.130.138.0 128.130.240.12 $=X ^SX Match any token in class X Ethernet address route add default 128.130.240.12 $~X ^TX Match any token not in class X netstat –rn # Routing table (numeric addresses) The Debug column shows the tokens as they will be printed netstat – en0 5 # Monitor en0 at 5-second intervals by sendmail in address test mode (sendmail -bt). netstat –in # Interfaces (numeric addresses) Hub and port numbers dump 0uf /dev/nrst0 /users # Level 0 dump DNS RECORD TYPES dump 0f – /usr | (cd /mnt; restore rvf –) # Copy tar cf – ./from | (cd todir; tar xvfp –) # Copy dir Type Syntax Emergency contact person # Find object files larger than 1MB not accessed in a year SOA zone [ttl] IN SOA primary admin serial find /users –type f –name "*.o" –size +1048576c refresh retry expire min –atime +365 –print NS zone [ttl] IN NS host # List all C source files sorted by number of lines A hostname [ttl] IN A ipaddr PTR ipaddr [ttl] IN PTR hostname Boot command find .
    [Show full text]
  • The Xargs Package
    The xargs package Manuel Pégourié-Gonnard [email protected] v1.1 (2008/03/22) Contents 1 Introduction 1 2 Usage 1 3 Implementation 4 Important note for French users: a French version of the user documentation is included in the xargs-fr.pdf file. 1 Introduction A Defining commands with an optional argument is easy in LTEX2ε. There is, how- ever, two limitations: you can make only one argument optional and it must be the first one. The xargs package provide extended variants of \newcommand & friends, for which these limitations no longer hold: It is now easy to define commands with many (and freely placed) optional arguments, using a nice hkeyi=hvaluei syntax. For example, the following defines a command with two optional arguments. \newcommandx*\coord[3][1=1, 3=n]{(#2_{#1},\ldots,#2_{#3})} $\coord{x}$ (x1,...,xn) $\coord[0]{y}$ (y0,...,yn) $\coord{z}[m]$ (z1,...,zm) $\coord[0]{t}[m]$ (t0,...,tm) 2 Usage 2.1 Basics The xargs package defines an extended variant for every LATEX macro related to macro definition. xargs’s macro are named after their LATEX counterparts, just adding an x at end (see the list in the margin). Here is the complete list: \newcommandx \renewcommandx \newenvironmentx \renewenvironmentx \providecommandx \DeclareRobustCommandx \CheckCommandx 1 If you are not familiar with all of them, you can either just keep using the A commands you already know, or check Lamport’s book or the LTEX Companion (or any LATEX2ε manual) to learn the others. Since these commands all share the same syntax, I’ll always use \newcommandx in the following, but remember it works the same for all seven commands.
    [Show full text]