Diffstat (limited to 'docs/usermanual/embeddedkonsole.sgm') (more/less context) (ignore whitespace changes)
| -rw-r--r-- | docs/usermanual/embeddedkonsole.sgm | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/docs/usermanual/embeddedkonsole.sgm b/docs/usermanual/embeddedkonsole.sgm index 4ba0287..838e705 100644 --- a/docs/usermanual/embeddedkonsole.sgm +++ b/docs/usermanual/embeddedkonsole.sgm @@ -58,8 +58,10 @@ A shell is a program that accepts input from a user, and runs commands. Each "command" in the shell is actually a separate program (unless you are using a shell like BusyBox, which makes some of the more common commands part of its own program in order to save space). Shells can actually be very powerful, and many + + of them allow you to write something called "shell scripts" which are just a sequence of commands, sometimes with some flow control statements, saved to a file and run each time the script is run. For the most part, the average user does not need to know about any of this, though. If you are running Opie on the @@ -145,9 +147,9 @@ to delete a directory that is not empty, along with all its contents, run <userinput>rm -r dir</userinput>. </para> </section> -<section><title>Linking Files</title> +<section id=symlink><title>Linking Files</title> <para> In Linux, you can have a special file called a "symbolic link" that acts just like a copy of another file, except it takes up less space. This is convinient if two applications are looking for the same file in two separate places, @@ -159,5 +161,5 @@ This is also useful for naming applications independant of their version number. "application1.0". To create a link, use the following command: <userinput>ln -s originalfile link</userinput>. </para> </section> -</chapter>
\ No newline at end of file +</chapter> |