Korn Shell Variables

Total Page:16

File Type:pdf, Size:1020Kb

Korn Shell Variables V4.1 cover Front cover Korn and Bash Shell Programming (Course code AL32) Student Notebook ERC 1.0 IBM Certified Course Material Student Notebook Trademarks IBM® is a registered trademark of International Business Machines Corporation. The following are trademarks of International Business Machines Corporation in the United States, or other countries, or both: AIX® AIX 5L™ Language Environment® OS/2® POWER™ RISC System/6000® RS/6000® Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Windows is a trademark of Microsoft Corporation in the United States, other countries, or both. UNIX® is a registered trademark of The Open Group in the United States and other countries. Linux® is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. October 2007 edition The information contained in this document has not been submitted to any formal IBM test and is distributed on an “as is” basis without any warranty either express or implied. The use of this information or the implementation of any of these techniques is a customer responsibility and depends on the customer’s ability to evaluate and integrate them into the customer’s operational environment. While each item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will result elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk. © Copyright International Business Machines Corporation 2007. All rights reserved. This document may not be reproduced in whole or in part without the prior written permission of IBM. Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. V4.1 Student Notebook TOC Contents Trademarks . xi Course description . xiii Agenda . xv Unit 1. Basic Shell Concepts . .1-1 Unit Objectives . 1-2 Shells . 1-3 This Course . 1-5 Directories . 1-6 Basic File Commands . 1-7 A File . 1-8 AIX File Names . 1-9 What Is a Shell Script? . 1-10 Invoking Shells . 1-11 Invoking Scripts . 1-12 Korn Shell Configuration Files . 1-13 What Are Metacharacters? . 1-15 Wildcard Metacharacters . 1-16 Sample Directory . 1-17 Expansion Examples . 1-18 More Shell Metacharacters . 1-19 Quoting Metacharacters . 1-20 Process I/O . 1-21 Input Redirection . 1-22 Output Redirection . 1-23 Output Appending . 1-24 Association . 1-25 Setting I/O or File Descriptors . 1-26 Setting I/O Descriptor Examples . 1-27 Pipes . 1-28 Command Grouping { { and ( ) . 1-29 Background Processing . 1-30 Shell Job Control . 1-31 Job Control Example . 1-32 Command Substitution . 1-33 Command Substitution Examples (1 of 2) . 1-34 Command Substitution Examples (2 of 2) . 1-35 Command Line Editing and Recall . 1-36 Checkpoint . 1-38 Unit Summary . 1-39 © Copyright IBM Corp. 2007 Contents iii Course materials may not be reproduced in whole or in part without the prior written permission of IBM. Student Notebook Unit 2. Variables. 2-1 Unit Objectives . .2-2 Setting Variables . .2-3 Referencing Variables . .2-4 Positional Parameters . .2-5 Setting Positional Parameters . .2-6 Variable Parameters . .2-7 Some Shell Parameters . .2-8 Shifting Arguments . .2-9 Parameter Code Example . .2-10 Parameter Output Example . .2-11 This Shell and the Next . .2-12 Inheritance Example - The export Command . .2-13 Korn Shell Variables . .2-14 Environment Variables . .2-15 Korn Environment Variables (1 of 2) . .2-16 Korn Environment Variables (2 of 2) . .2-17 Korn Shell 93 Variables . .2-18 Bash Environment Variables . .2-19 Checkpoint . .2-20 Unit Summary . .2-21 Unit 3. Return Codes and Traps . 3-1 Unit Objectives . .3-2 Return Values . .3-3 Exit Status . .3-4 Conditional Execution . ..
Recommended publications
  • Beginning Portable Shell Scripting from Novice to Professional
    Beginning Portable Shell Scripting From Novice to Professional Peter Seebach 10436fmfinal 1 10/23/08 10:40:24 PM Beginning Portable Shell Scripting: From Novice to Professional Copyright © 2008 by Peter Seebach All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without the prior written permission of the copyright owner and the publisher. ISBN-13 (pbk): 978-1-4302-1043-6 ISBN-10 (pbk): 1-4302-1043-5 ISBN-13 (electronic): 978-1-4302-1044-3 ISBN-10 (electronic): 1-4302-1044-3 Printed and bound in the United States of America 9 8 7 6 5 4 3 2 1 Trademarked names may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, we use the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. Lead Editor: Frank Pohlmann Technical Reviewer: Gary V. Vaughan Editorial Board: Clay Andres, Steve Anglin, Ewan Buckingham, Tony Campbell, Gary Cornell, Jonathan Gennick, Michelle Lowman, Matthew Moodie, Jeffrey Pepper, Frank Pohlmann, Ben Renow-Clarke, Dominic Shakeshaft, Matt Wade, Tom Welsh Project Manager: Richard Dal Porto Copy Editor: Kim Benbow Associate Production Director: Kari Brooks-Copony Production Editor: Katie Stence Compositor: Linda Weidemann, Wolf Creek Press Proofreader: Dan Shaw Indexer: Broccoli Information Management Cover Designer: Kurt Krames Manufacturing Director: Tom Debolski Distributed to the book trade worldwide by Springer-Verlag New York, Inc., 233 Spring Street, 6th Floor, New York, NY 10013.
    [Show full text]
  • Ardpower Documentation Release V1.2.0
    ardPower Documentation Release v1.2.0 Anirban Roy Das Sep 27, 2017 Contents 1 Introduction 1 2 Screenshot 3 3 Documentaion 5 3.1 Overview.................................................5 3.2 Installation................................................7 3.3 Usage................................................... 12 4 Indices and tables 13 i ii CHAPTER 1 Introduction Its a custom Oh-My-Zsh Theme inspired by many custom themes suited for a perfect ZSH Environment under Byobu with Tmux Backend. 1 ardPower Documentation, Release v1.2.0 2 Chapter 1. Introduction 3 ardPower Documentation, Release v1.2.0 CHAPTER 2 Screenshot 4 Chapter 2. Screenshot CHAPTER 3 Documentaion You can also find PDF version of the documentation here. Overview We will start with understanding the individual components of an entire CLI. Generally we don’t put much attention to what we do. We just fire up a terminal or some say sheel and start typing our commands and get the result. That’s all. But there are a lot of things that goes behind all this. Terminal The very first component is the Terminal. So what is a Terminal? A terminal emulator, terminal application, term, or tty for short, is a program that emulates a video ter- minal within some other display architecture. Though typically synonymous with a shell or text terminal, the term terminal covers all remote terminals, including graphical interfaces. A terminal emulator inside a graphical user interface is often called a terminal window.A terminal window allows the user access to a text terminal and all its applications such as command-line interfaces (CLI) and text user interface (TUI) applications.
    [Show full text]
  • Php Tutorial
    PHP About the Tutorial The PHP Hypertext Preprocessor (PHP) is a programming language that allows web developers to create dynamic content that interacts with databases. PHP is basically used for developing web-based software applications. This tutorial will help you understand the basics of PHP and how to put it in practice. Audience This tutorial has been designed to meet the requirements of all those readers who are keen to learn the basics of PHP. Prerequisites Before proceeding with this tutorial, you should have a basic understanding of computer programming, Internet, Database, and MySQL. Copyright & Disclaimer © Copyright 2016 by Tutorials Point (I) Pvt. Ltd. All the content and graphics published in this e-book are the property of Tutorials Point (I) Pvt. Ltd. The user of this e-book is prohibited to reuse, retain, copy, distribute or republish any contents or a part of contents of this e-book in any manner without written consent of the publisher. We strive to update the contents of our website and tutorials as timely and as precisely as possible, however, the contents may contain inaccuracies or errors. Tutorials Point (I) Pvt. Ltd. provides no guarantee regarding the accuracy, timeliness or completeness of our website or its contents including this tutorial. If you discover any errors on our website or in this tutorial, please notify us at [email protected] i PHP Table of Contents About the Tutorial ...........................................................................................................................................
    [Show full text]
  • Bash Guide for Beginners
    Bash Guide for Beginners Machtelt Garrels Garrels BVBA <tille wants no spam _at_ garrels dot be> Version 1.11 Last updated 20081227 Edition Bash Guide for Beginners Table of Contents Introduction.........................................................................................................................................................1 1. Why this guide?...................................................................................................................................1 2. Who should read this book?.................................................................................................................1 3. New versions, translations and availability.........................................................................................2 4. Revision History..................................................................................................................................2 5. Contributions.......................................................................................................................................3 6. Feedback..............................................................................................................................................3 7. Copyright information.........................................................................................................................3 8. What do you need?...............................................................................................................................4 9. Conventions used in this
    [Show full text]
  • Unix Systems: Shell Scripting (III)
    Unix Systems: Shell Scripting (III) Bruce Beckles University of Cambridge Computing Service 1 Introduction • Who: ! Bruce Beckles, e-Science Specialist, UCS • What: ! Unix Systems: Shell Scripting (III) course ! Follows on from “Unix Systems: Shell Scripting (II)” ! Part of the Scientific Computing series of courses • Contact (questions, etc): ! [email protected] • Health & Safety, etc: ! Fire exits • Please switch off mobile phones! [email protected] Unix Systems: Shell Scripting (III) 2 As this course is part of the Scientific Computing series of courses run by the Computing Service, all the examples that we use will be more relevant to scientific computing than to system administration, etc. This does not mean that people who wish to learn shell scripting for system administration and other such tasks will get nothing from this course, as the techniques and underlying knowledge taught are applicable to shell scripts written for almost any purpose. However, such individuals should be aware that this course was not designed with them in mind. For details of the “Unix Systems: Shell Scripting (II)” course, see: http://www.cam.ac.uk/cs/courses/coursedesc/linux.html#script2 2 What we don’t cover • Different types of shell: ! We are using the Bourne-Again SHell (bash). • Differences between versions of bash • Very advanced shell scripting – try this course instead: ! “Programming: Python for Absolute Beginners” [email protected] Unix Systems: Shell Scripting (III) 3 bash is probably the most common shell on modern Unix/Linux systems – in fact, on most modern Linux distributions it will be the default shell (the shell users get if they don’t specify a different one).
    [Show full text]
  • A Common Framework for Scripting Tutorials Erik Hjelmås and Ivar
    A Common Framework for Scripting Tutorials Erik Hjelmås and Ivar Farup Abstract A scripting tutorial should focus on teaching the characteristics of scripting languages, avoiding the pitfall of teaching only syntax conversion from system programming languages. Examples should be selected to emphasize features of scripting languages in general (e.g. weak typing, associate arrays, “gluing”) and the scripting language at hand. Students might benefit from using the same framework (structure of programming elements and examples) for learning multiple scripting languages. Their existing programming skills should be reused while newly introduced scripting concepts should be reinforced in subsequent examples. 1 Introduction Scripting languages are popular for solving problems in many different domains [8]. Some are general scripting languages such as Perl, Python and Ruby, while others are slightly domain-specific (platform-specific: Bash, PowerShell) or very domain-specific (application-specific: Cfengine, Matlab). They can be characterized as high-level and weakly typed, as opposed to system programming languages such as Java and C++ [11]. In higher education, scripting languages are used both for introductory programming courses [14] and for lab exercises in later courses. It is in this last context the present work seeks to contribute to a better learning experience for students. Although much effort has been invested in researching ways of teaching introductory programming [12], the problem of how to convert existing programming skills to a new language seems slightly overlooked. The way this is solved in practice is by either providing a short tutorial style introduction to the new language, or referring the student to an online tutorial resource.
    [Show full text]
  • Bash Tutorial
    Bash Shell Lecturer: Prof. Andrzej (AJ) Bieszczad Email: [email protected] Phone: 818-677-4954 Bash Shell The shell of Linux • Linux has a variety of different shells: – Bourne shell (sh), C shell (csh), Korn shell (ksh), TC shell (tcsh), Bour ne Again shell (bash). • Certainly the most popular shell is “bash”. Bash is an sh- compatible shell that incorporates useful features from the Korn shell (ksh) and C shell (csh). • It is intended to conform to the IEEE POSIX P1003.2/ISO 9945.2 Shell and Tools standard. • It offers functional improvements over sh for both programming and interactive use. Bash Shell Programming or Scripting ? • bash is not only an excellent command line shell, but a scripting language in itself. Shell scripting allows us to use the shell's abilities and to automate a lot of tasks that would otherwise require a lot of commands. • Difference between programming and scripting languages: – Programming languages are generally a lot more powerful and a lot faster than scriptin g languages. Programming languages generally start from source code and are compil ed into an executable. This executable is not easily ported into different operating syste ms. – A scripting language also starts from source code, but is not compiled into an executabl e. Rather, an interpreter reads the instructions in the source file and executes each inst ruction. Interpreted programs are generally slower than compiled programs. The main a dvantage is that you can easily port the source file to any operating system. bash is a s cripting language. Other examples of scripting languages are Perl, Lisp, and Tcl.
    [Show full text]
  • Individual Coursework 5: Implementing a UNIX Shell Introduction
    UCL CS 0019 Brad Karp Individual Coursework 5: Implementing a UNIX Shell Due date: 5:05 PM GMT, 30th March 2020, EXTENDED to 6th April 2020 Value: 6% of marks for module Introduction The design of the UNIX1 system call APIs for creating and controlling processes and plumbing together their inputs and outputs is one of the gems of modern software systems architecture. To help you become fluent in using this powerful set of mechanisms in C, in this assignment you will use fork(), exec(), and several other interesting system calls to build a command shell, or shell for short. A shell reads commands on its standard input and executes them. Modern UNIXes include multiple shells (and developers over the years have created still more shells with different syntaxes and features). In your shell, you will implement simple commands, background commands, conditional commands (i.e., using the && and || operators), I/O redirection, and pipes. You will also imple- ment command interruption (i.e., with Ctrl-C). Your shell will implement a subset of the bash shell’s syntax, as defined at: http://www.gnu.org/software/bash/manual/bashref.html and will be generally compatible with bash for the features they share. You may find a tutorial on how to use the UNIX shell useful preparation for CW5; one such tutorial is available at: http://www.linuxcommand.org/lc3_learning_the_shell.php This coursework must be done in a UNIX programming environment. We recommend that all 0019 students develop in the 0019 Linux virtual machine (VM) provided for use in this class, available at: http://www.cs.ucl.ac.uk/staff/B.Karp/0019/s2020/cw.html If you happen to have another UNIX machine at your disposal (including a Mac OS machine), you may find that you can develop your solution to CW5 in that environment, but the only development environment the 0019 staff can support is the 0019 VM.
    [Show full text]
  • Unix/Mac/Linux OS Malware 10/15/2020
    Unix/Mac/Linux OS Malware 10/15/2020 Report #: 202010151030 Agenda • Executive Summary • Origin of Modern Operating Systems • Overview of Operating Systems o Desktop o Servers o Super Computers o Mobile o Attack Surface and CVEs • Malware Case Studies o Drovorub o Hidden Wasp o Operation Windigo o MAC Malware Slides Key: • Defending Against Malware The picture can't be displayed. Non-Technical: Managerial, strategic and high- • Summary level (general audience) The picture can't be displayed. Technical: Tactical / IOCs; requiring in-depth knowledge (system admins, IRT) TLP: WHITE, ID# 202010151030 2 Executive Summary • Unix and Unix-like systems drive most of today's computer systems. • Vulnerabilities and malware • Threat mitigation o Comprehensive security policies o Access control o Regular updates and backups o Training employees o Improving posture and maturity TLP: WHITE, ID# 202010151030 3 Modern Operating Systems "Determining the operating system on which the server runs is the most important part of hacking. Mostly, hacking is breaking into the target's system to steal data or any such purpose. Hence, the security of the system becomes the thing of prime importance." Source: Parikh, K. (2020, August) The Hackers Library Functions of Operating Systems Timeline of the Origins of Operating Systems TLP: WHITE, ID# 202010151030 4 Overview of Operating Systems (Non-Mobile) Unix Chrome OS •Derived from Original AT&T Unix •Free and open-source •Command-line input •Graphical user interface •Very popular among scientific, •Based on Linux
    [Show full text]
  • Rc the Plan 9 Shell
    Rc ߞ The Plan 9 Shell Tom Duff [email protected]−labs.com ABSTRACT Rc is a command interpreter for Plan 9 that provides similar facilities to UNIXߣs Bourne shell, with some small additions and less idiosyncratic syntax. This paper uses numerous examples to describe rcߣs features, and contrasts rc with the Bourne shell, a model that many readers will be familiar with. 1. Introduction Rc is similar in spirit but different in detail from UNIXߣs Bourne shell. This paper describes rcߣs principal features with many small examples and a few larger ones. It assumes familiarity with the Bourne shell. 2. Simple commands For the simplest uses rc has syntax familiar to Bourne-shell users. All of the fol­ lowing behave as expected: date cat /lib/news/build who >user.names who >>user.names wc <file echo [a−f]*.c who | wc who; date vc *.c & mk && v.out /*/bin/fb/* rm −r junk || echo rm failed! 3. Quotation An argument that contains a space or one of rcߣs other syntax characters must be enclosed in apostrophes (’): rm ’odd file name’ An apostrophe in a quoted argument must be doubled: echo ’How’’s your father?’ 4. Patterns An unquoted argument that contains any of the characters *?[is a pattern to be matched against file names. A * character matches any sequence of characters, ? matches any single character, and [class] matches any character in the class, unless the first character of class is ~, in which case the class is complemented. The class may ­ 2 ­ also contain pairs of characters separated by −, standing for all characters lexically between the two.
    [Show full text]
  • The Korn Shell
    UNIX Basics by Peter Collinson, Hillside Systems BEK SHAKIROV The Korn Shell ell, nobody’s perfect. I cre- the most recent version of the shell. The dtksh is large, and you probably don’t ated an incorrect impression version that you can pull from AT&T is want to use it as your login shell. W about the Korn shell in my ksh93, and has several enhancements If you do use ksh as your login shell, articleW “Over revisited” (SW Expert that increase the power of the language. then what can it do for you? Most mor- August 2000). I said that the source for For some time, David Korn has been tal users only scratch the surface of the the most recent version of the Korn shell repositioning the shell; taking it from a power of any shell they use, and para- (ksh93) was not publicly available. This program that is used to control program doxically, most of the usage of any shell statement was incorrect, and I received execution towards a powerful interpreted is made by people simply typing com- email from a couple of people (one of language. He’s been aiming to create a mands and having them executed. So, them David Korn) telling me that the “scripting language” that directly sup- I’m going to concentrate on the shell source has been available since 1999, ports many of the programming struc- features that make your life easier. pointing me to www.kornshell.com. tures and features that you will find in I suppose that most of these features The state of the art is that the program other UNIX super-tools, like awk.
    [Show full text]
  • An Introduction to the C Shell
    -- -- An Introduction to the C shell William Joy (revised for 4.3BSD by Mark Seiden) Computer Science Division Department of Electrical Engineering and Computer Science University of California, Berkeley Berkeley, California 94720 ABSTRACT Csh is a newcommand language interpreter for UNIX†systems. It incorporates good features of other shells and a history mechanism similar to the redo of INTERLISP. While incorporating manyfeatures of other shells which makewriting shell programs (shell scripts) easier,most of the features unique to csh are designed more for the interac- tive UNIX user. UNIX users who have read a general introduction to the system will find a valuable basic explanation of the shell here. Simple terminal interaction with csh is possible after reading just the first section of this document. The second section describes the shell’s capabilities which you can explore after you have begun to become acquainted with the shell. Later sections introduce features which are useful, but not necessary for all users of the shell. Additional information includes an appendix listing special characters of the shell and a glossary of terms and commands introduced in this manual. Introduction A shell is a command language interpreter. Csh is the name of one particular command interpreter on UNIX.The primary purpose of csh is to translate command lines typed at a terminal into system actions, such as invocation of other programs. Csh is a user program just likeany you might write. Hopefully, csh will be a very useful program for you in interacting with the UNIX system. In addition to this document, you will want to refer to a copyofthe UNIX User Reference Manual.
    [Show full text]