[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
slackbook:shell [2012/09/08 11:10 (UTC)] – [less] updated to match original article including formatting mfillpotslackbook:shell [2014/05/21 08:39 (UTC)] (current) – [File and Directory Creation and Deletion] man -> mkdir zithro
Line 15: Line 15:
 (short for **manual**) will bring up the included (short for **manual**) will bring up the included
 man-page for any application, system call, configuration file, or man-page for any application, system call, configuration file, or
-library you tell it too.  For example, man man+library you tell it too.  For example, **man man**
 will bring up the man-page for **//man//** itself. will bring up the man-page for **//man//** itself.
  
Line 196: Line 196:
 "/slack", then "/slack/foo", and finally "/slack/foo/bar".  If you "/slack", then "/slack/foo", and finally "/slack/foo/bar".  If you
 failed to use the //-p// argument, failed to use the //-p// argument,
-**//man//** would fail to create "/slack/foo/bar"+**//mkdir//** would fail to create "/slack/foo/bar"
 unless the first two already existed, as you saw in the example. unless the first two already existed, as you saw in the example.
  
Line 328: Line 328:
 strength. Unfortunately, achieving that greater compression is a slow strength. Unfortunately, achieving that greater compression is a slow
 and CPU-intensive process, so **//bzip2//**  and CPU-intensive process, so **//bzip2//** 
-typicall takes much longer to run than other alternatives.+typically takes much longer to run than other alternatives.
 ==== XZ / LZMA ==== ==== XZ / LZMA ====
  
  
 The latest compression utility added to Slackware is The latest compression utility added to Slackware is
-**//xz//**, which impliments the LZMA compression+**//xz//**, which implements the LZMA compression
 algorithm. This is faster than **//bzip2//** and algorithm. This is faster than **//bzip2//** and
 often compresses better as well. In fact, its blend of speed and often compresses better as well. In fact, its blend of speed and
 compression strength caused it to replace compression strength caused it to replace
 **//gzip//** as the compression scheme of choice for **//gzip//** as the compression scheme of choice for
-Slackware.  Unfortuantely, **//xz//** does not have+Slackware.  Unfortunately, **//xz//** does not have
 a man page at the time of this writing, so to view available options, a man page at the time of this writing, so to view available options,
 use the //--help// argument.  Compressing files is accomplished use the //--help// argument.  Compressing files is accomplished
Line 446: Line 446:
 **//more//** will display the first few lines of a **//more//** will display the first few lines of a
 text file until your screen is full, then pause.  Once you've read text file until your screen is full, then pause.  Once you've read
-through that screen, you can proceed down one line by pressing ENTER, +through that screen, you can proceed down one line by pressing <key>'ENTER'</key>, 
-or an entire screen by pressing <key>SPACE</key>, or by a+or an entire screen by pressing <key>'SPACE'</key>, or by a
 specified number of lines by typing a number and then the specified number of lines by typing a number and then the
-<key>SPACE</key> bar. **//more//** is also+<key>'SPACE'</key> bar. **//more//** is also
 capable of searching through a text file for keywords; once you've capable of searching through a text file for keywords; once you've
 displayed a file in **//more//**, press the / displayed a file in **//more//**, press the /
-key and enter a keyword.  Upon pressing <key>ENTER</key>, the+key and enter a keyword.  Upon pressing <key>'ENTER'</key>, the
 text will scroll until it finds the next match.   text will scroll until it finds the next match.  
  
Line 469: Line 469:
 In fact, modern versions of **//more//**, such In fact, modern versions of **//more//**, such
 as the one shipped with Slackware, do feature a as the one shipped with Slackware, do feature a
-**back** function via the <key>b</key>+**back** function via the <key>'b'</key>
 key. However, the function is only available when opening files key. However, the function is only available when opening files
 directly in **//more//**; not when a file is directly in **//more//**; not when a file is
Line 475: Line 475:
  
 </note> </note>
- 
 ==== less ==== ==== less ====
  
Line 493: Line 492:
 Moreover, Slackware also includes a handy little pre-processor for Moreover, Slackware also includes a handy little pre-processor for
 **//less//** called **//less//** called
-''lesspipe.sh''.  This allows a user to exectute+''lesspipe.sh''.  This allows a user to execute
 **//less//** on a number of non-text files. **//less//** on a number of non-text files.
 ''lesspipe.sh'' will generate text output from ''lesspipe.sh'' will generate text output from
Line 503: Line 502:
 functionality as one might expect from a text editor without functionality as one might expect from a text editor without
 actually being a text editor. Movement line-by-line can be done actually being a text editor. Movement line-by-line can be done
-**//vi//**-style with <key>j</key> and +**//vi//**-style with <key>'j'</key> and 
-<key>k</key>, or with the arrow keys, or +<key>'k'</key>, or with the arrow keys, or 
-<key>ENTER</key>. In the event that a file is too wide to fit+<key>'ENTER'</key>. In the event that a file is too wide to fit
 on one screen, you can even scroll horizontally with the left and on one screen, you can even scroll horizontally with the left and
-right arrow keys. The <key>g</key> key takes you to the top of +right arrow keys. The <key>'g'</key> key takes you to the top of 
-the file, while <key>G</key> takes you to the+the file, while <key>'G'</key> takes you to the
 end. end.
  
Line 514: Line 513:
 Searching is done as with **//more//**, by typing Searching is done as with **//more//**, by typing
 the / key and then your search string, but notice how the search the / key and then your search string, but notice how the search
-results are highlighted for you, and typing <key>n</key> will +results are highlighted for you, and typing <key>'n'</key> will 
-take you to the next occurence of the result while +take you to the next occurrence of the result while 
-<key>N</key> takes you to the previous occurrence.+<key>'N'</key> takes you to the previous occurrence.
  
  
-Also as with **//more//**, files maybe opened+Also as with **//more//**, files may be opened
 directly in **//less//** or piped to it: directly in **//less//** or piped to it:
  
Line 525: Line 524:
 <code> <code>
  
-darkstar:~$  <command>less +darkstar:~$  less 
-/usr/doc/less-&#42;/README</command> +/usr/doc/less:/README 
-darkstar:~$  <command>cat +darkstar:~$  cat 
-/usr/doc/less&#42;/README +/usr/doc/less:/README 
-/usr/doc/util-linux&#42;/README | less</command>+/usr/doc/util-linux:/README | less
 </code> </code>
  
  
 There is much more to **//less//**; from within There is much more to **//less//**; from within
-the application, type <key>h</key> for a full list of+the application, type <key>'h'</key> for a full list of
 commands.  commands. 
 ===== Linking ===== ===== Linking =====
  
-Links are a method of referring to one file by more than one name. By using the ln(1) application, a user can reference one file with more than one name. The two files are not carbon-copies of one another, but rather are the exact same file, just with a different name. To remove the file entirely, all of its names must be deleted. (This is actually the result of the way that rm and other tools like it work. Rather than remove the contents of the file, they simply remove the reference to the file, freeing that space to be re-used. ln will create a second reference or "link" to that file.)+Links are a method of referring to one file by more than one name.  By 
 +using the **//ln//**(1) application, a user can 
 +reference one file with more than one name.  The two files are not 
 +carbon-copies of one another, but rather are the exact same file, just 
 +with a different name.  To remove the file entirely, all of its names 
 +must be deleted.  (This is actually the result of the way that 
 +**//rm//** and other tools like it work.  Rather 
 +than remove the contents of the file, they simply remove the reference 
 +to the file, freeing that space to be re-used. 
 +**//ln//** will create a second reference or "link" 
 +to that file.)
  
-  darkstar:~$ ln /etc/slackware-version foo 
-  darkstar:~$ cat foo 
-  Slackware 12.0.0 
-  darkstar:~$ ls -l /etc/slackware-version foo 
-  -rw-r--r-- 1 root root 17 2007-06-10 02:23 /etc/slackware-version 
-  -rw-r--r-- 1 root root 17 2007-06-10 02:23 foo 
  
-Another type of link exists, the symlink. Symlinks, rather than being another reference to the same file, are actually a special kind of file in their own right. These symlinks point to another file or directory. The primary advantage of symlinks is that they can refer to directories as well as files, and they can span multiple filesystems. These are created with the [-s] argument.+<code> 
 +darkstar:~$ ln /etc/slackware-version foo 
 +darkstar:~$ cat foo 
 +Slackware 14.0 
 +darkstar:~$ ls -l /etc/slackware-version foo 
 +-rw-r--r-- 1 root root 17 2007-06-10 02:23 /etc/slackware-version 
 +-rw-r--r-- 1 root root 17 2007-06-10 02:23 foo 
 +</code>
  
-  darkstar:~$ ln -s /etc/slackware-version foo 
-  darkstar:~$ cat foo 
-  Slackware 12.0.0 
-  darkstar:~$ ls -l /etc/slackware-version foo 
-  -rw-r--r-- 1 root root 17 2007-06-10 02:23 /etc/slackware-version 
-  lrwxrwxrwx 1 root root 22 2008-01-25 04:16 foo -> /etc/slackware-version 
  
-When using symlinks, remember that if the original file is deleted, your symlink is useless; it simply points at a file that doesn't exist anymore. +Another type of link exists, the symlink.  Symlinks, rather than being 
 +another reference to the same file, are actually a special kind of file 
 +in their own right.  These symlinks point to another file or directory. 
 +The primary advantage of symlinks is that they can refer to directories 
 +as well as files, and they can span multiple filesystems.  These are 
 +created with the //-s// argument. 
 + 
 + 
 +<code> 
 +darkstar:~$ ln -s /etc/slackware-version foo 
 +darkstar:~$ cat foo 
 +Slackware 140 
 +darkstar:~$ ls -l /etc/slackware-version foo 
 +-rw-r--r-- 1 root root 17 2007-06-10 02:23 /etc/slackware-version 
 +lrwxrwxrwx 1 root root 22 2008-01-25 04:16 foo -> /etc/slackware-version 
 +</code> 
  
-----+When using symlinks, remember that if the original file is deleted, 
 +your symlink is useless; it simply points at a file that doesn't exist 
 +anymore. 
 +====== Chapter Navigation ======
  
 **Previous Chapter: [[slackbook:booting|Booting]]** **Previous Chapter: [[slackbook:booting|Booting]]**
Line 565: Line 588:
 ====== Sources ====== ====== Sources ======
 <!-- If you copy information from another source, then specify that source --> <!-- If you copy information from another source, then specify that source -->
- * Original source: [[http://www.slackbook.org/beta]] \\+  * Original source: [[http://www.slackbook.org/beta]] \\
 <!-- Authors are allowed to give credit to themselves! --> <!-- Authors are allowed to give credit to themselves! -->
- * Originally written by Alan Hicks, Chris Lumens, David Cantrell, Logan Johnson+  * Originally written by Alan Hicks, Chris Lumens, David Cantrell, Logan Johnson
 <!-- * Contrbutions by [[wiki:user:yyy | User Y]] --> <!-- * Contrbutions by [[wiki:user:yyy | User Y]] -->
  

Trace:

slackbook:shell ()