Differences between revisions 146 and 147
Revision 146 as of 2009-12-28 18:09:14
Size: 5014
Editor: GreyCat
Comment: manual TOC for the whole guide; merge most of the old /Introduction
Revision 147 as of 2010-01-21 20:39:00
Size: 6554
Editor: Lhunath
Comment: Add some more introductory information
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
'''This guide is currently still a work in progress. It grows a little every day. You are invited to make additions or modifications so long as you can keep them accurate (and linguistically correct).''' '''You are invited to make additions or modifications so long as you can keep them accurate (and linguistically correct).'''
Line 15: Line 15:
This guide aims to become a point of reference for people interested in learning to work with [[BASH]]. It aspires to teach its readers good practice techniques in developing scripts for the [[BASH]] interpreter and educate them about the internal operation of [[BASH]]. This guide aims to become a point of reference for people interested in learning to work with [[BASH]]. It aspires to teach its readers good practice techniques in developing scripts for the [[BASH]] interpreter and educate them about the internal operation and good practices involving usage of [[BASH]].
Line 17: Line 17:
This guide is targeted at beginning users. It assumes no basic knowledge, but rather expects you to have enough common sense to put two and two together. If something is unclear to you, you should report this so that it may be clarified in this document for future readers. This guide is targeted at beginning users. It assumes no basic knowledge, but rather expects you to have enough common sense to put two and two together. If something is unclear to you, you are invited to report this (consider #bash on irc.freenode.org) so that it may be clarified in this document for future readers.
Line 34: Line 34:
Think of a shell as a way for you to speak to your system. Your system doesn't need it for most of its work, but it is an excellent interface between you and what your system can offer. It allows you to perform basic math, run basic tests and execute applications. More importantly, it allows you to combine these operations and connect applications to each other to perform complex and automated tasks.

Bash is NOT your operating system. It is not your window manager. It does not control your mouse or keyboard. It does not configure your system, activate your screensaver, open your files when you double-click them in some file manager and it is generally not involved in launching applications when you start them from your window manager. It's important to understand that Bash is only the interface for you to execute statements (using Bash syntax), either on the interactive Bash prompt or via Bash scripts.
Line 43: Line 47:
Most users that think of [[BASH]] think of it as a prompt and a command line. That is [[BASH]] in ''interactive mode''. [[BASH]] can also run in ''non-interactive mode'' through scripts. We can use scripts to automate certain logic. Scripts are basically lists of commands that you can type on the command line. When such a script is executed, all these commands are executed sequentially, one after another. Most users that think of [[BASH]] think of it as a prompt and a command line. That is [[BASH]] in ''interactive mode''. [[BASH]] can also run in ''non-interactive mode'' through scripts. We can use scripts to automate certain logic. Scripts are basically lists of commands that you can type on the command line. When such a script is executed, all these commands are (generally) executed sequentially, one after another.
Line 54: Line 58:
The `man` command opens documentation on a certain application. You use it by running the command `man [application]` on the `bash` prompt, where `[application]` is the name of the application as you would use to run it on the prompt. It explains that application's purpose and usage in detail.

Note that if you're looking for information on `bash` built-ins (commands provided by `bash`, not by external applications) you should look in `man bash` instead. `Bash`'s manual is extensive and detailed. It is an excellent reference; albeit more technical than this document.
Line 58: Line 66:
    $ help read

Commands and Arguments ->


Introduction

You are invited to make additions or modifications so long as you can keep them accurate (and linguistically correct).

All the information here is presented without any warranty or guarantee of accuracy. Use it at your own risk. When in doubt, please consult the man pages or the GNU info pages as the authoritative references.

BASH is a BourneShell compatible shell, which adds many new features to its ancestor. Most of them are available in the 'KornShell', too.


About This Guide

This guide aims to become a point of reference for people interested in learning to work with BASH. It aspires to teach its readers good practice techniques in developing scripts for the BASH interpreter and educate them about the internal operation and good practices involving usage of BASH.

This guide is targeted at beginning users. It assumes no basic knowledge, but rather expects you to have enough common sense to put two and two together. If something is unclear to you, you are invited to report this (consider #bash on irc.freenode.org) so that it may be clarified in this document for future readers.

You are invited to contribute to the development of this document by extending it or correcting invalid or incomplete information.

The maintainer(s) of this document:


A Definition

BASH is an acronym for Bourne Again Shell. It is based on the Bourne shell and is mostly compatible with its features.

Shells are applications that provide users with the ability to give commands to their operating system interactively, or to allow them to execute batch processes quickly. In no way are they required for execution of processes; they are merely a layer between system function calls and the user.

Think of a shell as a way for you to speak to your system. Your system doesn't need it for most of its work, but it is an excellent interface between you and what your system can offer. It allows you to perform basic math, run basic tests and execute applications. More importantly, it allows you to combine these operations and connect applications to each other to perform complex and automated tasks.

Bash is NOT your operating system. It is not your window manager. It does not control your mouse or keyboard. It does not configure your system, activate your screensaver, open your files when you double-click them in some file manager and it is generally not involved in launching applications when you start them from your window manager. It's important to understand that Bash is only the interface for you to execute statements (using Bash syntax), either on the interactive Bash prompt or via Bash scripts.



  • Shell: A (possibly interactive) layer between the user and the system.
    BASH: The Bourne Again Shell, a Bourne compatible shell.


Using Bash

Most users that think of BASH think of it as a prompt and a command line. That is BASH in interactive mode. BASH can also run in non-interactive mode through scripts. We can use scripts to automate certain logic. Scripts are basically lists of commands that you can type on the command line. When such a script is executed, all these commands are (generally) executed sequentially, one after another.

We'll start with the basics in an interactive shell. Once you're familiar with those, you can put them together in scripts.

Important!
You should make yourself familiar with the man and apropos commands on the shell. They will be vital to your self-tutoring.

    $ man man
    $ man apropos

The man command opens documentation on a certain application. You use it by running the command man [application] on the bash prompt, where [application] is the name of the application as you would use to run it on the prompt. It explains that application's purpose and usage in detail.

Note that if you're looking for information on bash built-ins (commands provided by bash, not by external applications) you should look in man bash instead. Bash's manual is extensive and detailed. It is an excellent reference; albeit more technical than this document.

BASH also offers a help command which contains brief summaries of some of its built-in commands (which we'll discuss later on).

    $ help
    $ help read



  • Interactive mode: A mode of operation where a prompt asks you for one command at a time.

  • Script: A file that contains a sequence of commands to execute one after the other.


Contents

The guide has been divided into sections, which are intended to be read roughly in the order presented. If you skip ahead to a specific section, you might find yourself missing some background information from previous sections. (Links to relevant sections are not always provided when a topic is mentioned.)


Commands and Arguments ->


CategoryShell

BashGuide (last edited 2015-04-10 20:29:39 by GreyCat)