[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
howtos:cli_manual:introduction [2012/09/23 20:35 (UTC)] – [CLI is powerful - Use it wisely] Added a section sycamorexhowtos:cli_manual:introduction [2012/09/26 04:11 (UTC)] (current) – changed chapter links to relative links mfillpot
Line 1: Line 1:
 <!-- Add your text below. We strongly advise to start with a Headline (see button bar above). --> <!-- Add your text below. We strongly advise to start with a Headline (see button bar above). -->
-<note important>Work in Progress</note> 
 ====== CLI Introduction ====== ====== CLI Introduction ======
  
Line 8: Line 7:
  
  
-===== CLI is good - Do not fear it =====+===== CLI is Good - Do Not Fear It =====
  
 The following are some of the advantages to using CLI: The following are some of the advantages to using CLI:
Line 21: Line 20:
   - CLI scripts can include comments that can act as notes and internal documentation explaining the functionality and simplifying future modifications.   - CLI scripts can include comments that can act as notes and internal documentation explaining the functionality and simplifying future modifications.
   - CLI based instructions are easier to document for sharing with others as opposed to long how-tos and screenshots necessary for GUI instructions.   - CLI based instructions are easier to document for sharing with others as opposed to long how-tos and screenshots necessary for GUI instructions.
 +  - CLI commands let you easily access and manage remote systems.
  
-===== CLI is powerful - Use it wisely =====+===== CLI is Powerful - Use it Wisely =====
  
 Being very powerful and flexible, CLI commands can also be unforgiving and potentially harmful to your system. Please remember about the following: Being very powerful and flexible, CLI commands can also be unforgiving and potentially harmful to your system. Please remember about the following:
Line 31: Line 31:
   - Avoid running commands that you do not understand (especially as root)    - Avoid running commands that you do not understand (especially as root) 
  
-===== CLI ????=====+===== CLI Offers You Choice =====
  
-A program that provides a command line interface is called a ''shell'' and is loaded when a user logs in to a system. The default shell in Slackware is called ''Bash'' (Bourne-again shell).  Once you've started the X window system, you can access the shell via ''virtual terminals'' which are accessible by pressing <key>Alt</key>+<key>F2</key> through <key>F6</key> (the 7th being the current X session). A more convenient and common solution is to access the shell via ''terminal emulators''. Slackware ships with the following terminal emulators:+A program that provides a command line interface is called a ''shell'' and is loaded when a user logs in to a system. The default shell in Slackware is called ''Bash'' (Bourne-again shell). Although other shells will be briefly discussed in [[.shells|Chapter 3]], the CLI manual will focus predominantly on Bash, the most common shell on today's Linux systems. Once you've started the X window system, you can access the shell via ''virtual terminals'' which can be opened by pressing <key>Alt</key>+<key>F2</key> through <key>F6</key> (the 7th being the current X session).  
 + 
 +===== Terminals ===== 
 +==== Terminal Emulators ==== 
 + 
 +A more convenient and common solution, however, is to access the shell via ''terminal emulators''. Slackware ships with the following terminal emulators:
  
   * xterm   * xterm
Line 42: Line 47:
 There are many more terminal emulators available from [[http://www.slackbuilds.org|Slackbuilds.org]]. Some popular ones are: There are many more terminal emulators available from [[http://www.slackbuilds.org|Slackbuilds.org]]. Some popular ones are:
  
-  * aterm +  * [[http://slackbuilds.org/system/aterm/|aterm]] 
-  * eterm +  * [[http://slackbuilds.org/system/eterm/|eterm]] 
-  * rxvt-unicode +  * [[http://slackbuilds.org/system/rxvt-unicode/|rxvt-unicode (urxvt)]] 
-  * sakura +  * [[http://slackbuilds.org/system/sakura/|sakura]] 
-  * terminator+  * [[http://slackbuilds.org/system/terminator/|terminator]] 
 + 
 +Despite the fact that ultimately they all provide access to the shell, some of them offer unique features that may be appealing to you so it is worth doing some research on them. 
 + 
 +==== Terminal Multiplexers ==== 
 + 
 +Another CLI tool that may come in handy, especially if you are working on remote systems, are [[http://en.wikipedia.org/wiki/Terminal_multiplexer|terminal multiplexers]] which make it possible to run multiple terminal sessions within one virtual terminal or terminal emulator window. Two most popular terminal multiplexers are ''screen'' (comes with Slackware) and ''tmux'' (available from [[http://slackbuilds.org/system/tmux/|SlackBuilds]]). 
 + 
 +====== Chapter Navigation ====== 
 + 
 +**Next Chapter: [[.first_steps|First Steps]]** 
 + 
 ====== Sources ====== ====== Sources ======
 <!-- If you are copying information from another source, then specify that source --> <!-- If you are copying information from another source, then specify that source -->
Line 56: Line 73:
 <!-- Please do not modify anything below, except adding new tags.--> <!-- Please do not modify anything below, except adding new tags.-->
 <!-- You must remove the tag-word "template" below before saving your new page --> <!-- You must remove the tag-word "template" below before saving your new page -->
-{{tag>work_in_progress author_sycamorex}}+{{tag>cli author_sycamorex}}
 howtos:cli_manual:introduction ()