About 50 results
Open links in new tab
  1. Linux Command Line Books by William Shotts

    In this 250+ page sequel/suplement to The Linux Command Line we'll look at even more cool tools and fun command line topics. With 14 action-packed chapters, it's perfect for makers, …

  2. LinuxCommand.org: Learn The Linux Command Line. Write Shell …

    LinuxCommand.org is a web site that helps users discover the power of the Linux command line.

  3. LinuxCommand.org: Adventures

    This collection is a supplement to my book, The Linux Command Line (TLCL), so if you don't already have a copy, please download one or, if you prefer, pick up a printed copy from your …

  4. LinuxCommand.org: Learning the shell.

    Since I was forced to use the legacy OS while I was on the job, I installed a Linux-like command line environment for it. When I heard about the problem, I realized I could perform this task …

  5. LinuxCommand.org: Writing shell scripts.

    We have already covered many shell features, but we have focused on those features most often used directly on the command line. The shell also provides a set of features usually (but not …

  6. Learning the shell - Lesson 9: Permissions - LinuxCommand.org

    The chmod command is used to change the permissions of a file or directory. To use it, we specify the desired permission settings and the file or files that we wish to modify.

  7. LinuxCommand.org: Resources

    This series goes through the process of upgrading a Linux system from one version of Linux to another by doing a fresh install. Covers backup and installation techniques.

  8. Writing shell scripts - Lesson 12: Positional Parameters

    To handle options on the command line, we use a facility in the shell called positional parameters. Positional parameters are a series of special variables ($0 through $9) that contain the …

  9. Command Documentation

    Manual pages for bash builtins, GNU coreutils, and other commands

  10. Learning the shell - Lesson 5: Manipulating Files

    Before you use rm with wildcards, try this helpful trick: construct your command using ls instead. By doing this, you can see the effect of your wildcards before you delete files.