Introduction to the Command Line

Introduction to the Command Line. Free Software Foundation, Abernathy, W., Anderson, G., Anhalt, C., Bai, L., Baptista, V., Barakat, M., Batini, E., Bavier, E., Becher, J., Becher, V., Biberg Kristensen, L., Boyle, T., Brown, P., Catkan, B., Charzat, S., Cherlin, E., Compall, S., Davies, P., de Rigo, D., Devarajan, D., Dorrington, M., Fernández Piñas, D., Fortin, P., Gauland, M., Gillmor, D. K., Goh, T., Golin, R., Haichao, X., Hall, D., Hyde, A., Innoccenti, B., Jonsson, A., Kibbe, D., Kochenderfer, V., Krampis, N., Lee, M., Lockwood-Childs, S., Lucifredi, F., Magallon, M., Martin, A., McConnaughey, W., McNeely, M., Mengel, M., Merriam, W., Nair, S., Newell, M., Oliver, J., Oram, A., Oranen, J., Pawson, D., Prastowo, T., Ravikumar, S., Revilak, S., Schaumburg, S., Skwarecki, B., Sullivan, J., Tange, O., Tenney, K., Thahir, S., Walck, S., Weissmann, B., Wells, S., Williams, C., Woodacre, B., Woof, J., & et al. FLOSS Manuals.

Paper abstract bibtex

[Excerpt: Outline] This book is an introduction to using the shell with a focus on empowering GNU/Linux newbies. This page has an outline. The book itself is being written at: [\n] http://en.flossmanuals.net/bin/view/CommandLineIntro/WebHome [\n] It is meant to be fun and encourage the reader to play, so it is not organized in a formal manner (for instance, discussing all metacharacters in one place). Instead, features are introduced in the context of useful tasks. Rarely used features are not discussed. [\n] The main topic is the GNU/Linux Bash shell, but useful features of the Korn shell and zsh may be introduced in advanced chapters. The C family of shells and non-Unix shells are beyond the scope of the book. [\n] It assumes the reader is familiar with graphical interfaces, and refers to one or more free desktop environments where discussions of GUIs are necessary. [::Getting Started] Modern computing is highly interactive, and using the command line is just another form of interaction. Most people use the computer through its desktop or graphical interface, interacting at a rapid pace. They click on an object, drag and drop it, double-click another to open it, alter it, etc. Although interactions happen so fast you don't think about it, each click or keystroke is a command to the computer, which it reacts to. Using the command line is the same thing, but more deliberate. [...] [::Multiple files] After getting used to the command line, you will start looking for ways to do more in less time. One of the easiest ways to achieve that is to work on multiple files at the same time [...][...] [::Processes] Processes are programs in action. Programs in binary/executable form reside on your disk; when they are executed (run), they are moved into memory and become a process. Each and every program we run is a process. [...] [::Piping] Pipes let programs work together by connecting the output from one to be the input for another. The term "output" has a precise meaning here: it is what the program writes to the standard output, via C program statements such as printf or the equivalent, and normally it appears on the terminal screen. And "input" is the standard input, usually coming from the keyboard. Pipes are built using a vertical bar ("|") as the pipe symbol. [...] [::Permissions] Your computer system stores a lot of information about files that normally remains hidden as you create and play with the files. One set of file attributes you'll run into, though, is permissions. Who's able to edit your files? Hopefully not every person who logs in to the system (and many systems are still shared by multiple people nowadays). [...] [::Scripting] If you have a collection of commands you'd like to run together, you can combine them in a script and run them all at once. You can also pass arguments to the script so that it can operate on different files or other input. [...] [::Other scripting languages] The shell is a wonderful friend. If you have read the rest of the book up to this point, you may well be dizzy with the possibilities it presents. But the shell is still tremendously limited compared to many languages. We'll give you just a taste of other tools and languages you can explore. [...]

@book{freesoftwarefoundationIntroductionCommandLine2010,
  title = {Introduction to the {{Command Line}}},
  author = {{Free Software Foundation} and Abernathy, William and Anderson, Gareth and Anhalt, Carolyn and Bai, Luigi and Baptista, Vitor and Barakat, Michel and Batini, Edoardo and Bavier, Eric and Becher, Johannes and Becher, Viktor and Biberg Kristensen, Leif and Boyle, Tom and Brown, Peter and Catkan, Barbaros and Charzat, Sylvain and Cherlin, Edward and Compall, Stephen and Davies, Peter and de Rigo, Daniele and Devarajan, Dev and Dorrington, Michael and Fernández Piñas, David and Fortin, Pierre and Gauland, Michael and Gillmor, Daniel K. and Goh, Tim and Golin, Renato and Haichao, Xie and Hall, Darren and Hyde, Adam and Innoccenti, Bernie and Jonsson, Andreas and Kibbe, Dennis and Kochenderfer, Vance and Krampis, Ntino and Lee, Matt and Lockwood-Childs, S. and Lucifredi, Federico and Magallon, Marcelo and Martin, Austin and McConnaughey, William and McNeely, Mike and Mengel, Marc and Merriam, William and Nair, Sreeraj and Newell, Max and Oliver, Julian and Oram, Andy and Oranen, Jarkko and Pawson, Dave and Prastowo, Tadeus and Ravikumar, Siddharth and Revilak, Steve and Schaumburg, Steffen and Skwarecki, Beth and Sullivan, John and Tange, Ole and Tenney, Kent and Thahir, Sameer and Walck, Scott and Weissmann, Ben and Wells, Scott and Williams, Colin and Woodacre, Ben and Woof, Jason and {et al.}},
  date = {2010},
  publisher = {{FLOSS Manuals}},
  url = {http://mfkp.org/INRMM/article/13644772},
  abstract = {[Excerpt: Outline] This book is an introduction to using the shell with a focus on empowering GNU/Linux newbies. This page has an outline. The book itself is being written at:

[\textbackslash n] http://en.flossmanuals.net/bin/view/CommandLineIntro/WebHome

[\textbackslash n] It is meant to be fun and encourage the reader to play, so it is not organized in a formal manner (for instance, discussing all metacharacters in one place). Instead, features are introduced in the context of useful tasks. Rarely used features are not discussed.

[\textbackslash n] The main topic is the GNU/Linux Bash shell, but useful features of the Korn shell and zsh may be introduced in advanced chapters. The C family of shells and non-Unix shells are beyond the scope of the book.

[\textbackslash n] It assumes the reader is familiar with graphical interfaces, and refers to one or more free desktop environments where discussions of GUIs are necessary.

[::Getting Started] Modern computing is highly interactive, and using the command line is just another form of interaction. Most people use the computer through its desktop or graphical interface, interacting at a rapid pace. They click on an object, drag and drop it, double-click another to open it, alter it, etc. Although interactions happen so fast you don't think about it, each click or keystroke is a command to the computer, which it reacts to. Using the command line is the same thing, but more deliberate. [...]

[::Multiple files] After getting used to the command line, you will start looking for ways to do more in less time. One of the easiest ways to achieve that is to work on multiple files at the same time [...][...]

[::Processes] Processes are programs in action. Programs in binary/executable form reside on your disk; when they are executed (run), they are moved into memory and become a process. Each and every program we run is a process. [...]

[::Piping] Pipes let programs work together by connecting the output from one to be the input for another. The term "output" has a precise meaning here: it is what the program writes to the standard output, via C program statements such as printf or the equivalent, and normally it appears on the terminal screen. And "input" is the standard input, usually coming from the keyboard. Pipes are built using a vertical bar ("|") as the pipe symbol. [...]

[::Permissions] Your computer system stores a lot of information about files that normally remains hidden as you create and play with the files. One set of file attributes you'll run into, though, is permissions. Who's able to edit your files? Hopefully not every person who logs in to the system (and many systems are still shared by multiple people nowadays). [...]

[::Scripting] If you have a collection of commands you'd like to run together, you can combine them in a script and run them all at once. You can also pass arguments to the script so that it can operate on different files or other input. [...]

[::Other scripting languages] The shell is a wonderful friend. If you have read the rest of the book up to this point, you may well be dizzy with the possibilities it presents. But the shell is still tremendously limited compared to many languages. We'll give you just a taste of other tools and languages you can explore. [...]},
  keywords = {*imported-from-citeulike-INRMM,~INRMM-MiD:c-13644772,array-programming,awk,command-line,featured-publication,free-software,gnu-bash,gnu-make,gnu-octave,license-gnu-gpl,multiauthor,perl,python,reference-manual,ruby,text-editors},
  options = {useprefix=true}
}

Downloads: 0