Diffstat (limited to 'docs/usermanual/embeddedkonsole.sgm') (more/less context) (show whitespace changes)
-rw-r--r-- | docs/usermanual/embeddedkonsole.sgm | 4 |
1 files changed, 3 insertions, 1 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 | |||
@@ -50,24 +50,26 @@ You can edit or hide this menu from <GUIMenu>Options</GUIMenu>&arrow; | |||
50 | <GUIMenuItem>Command List.</GUIMenuItem> | 50 | <GUIMenuItem>Command List.</GUIMenuItem> |
51 | </para> | 51 | </para> |
52 | </section> | 52 | </section> |
53 | </section> | 53 | </section> |
54 | 54 | ||
55 | <section><title>What is a Shell</title> | 55 | <section><title>What is a Shell</title> |
56 | <para> | 56 | <para> |
57 | A shell is a program that accepts input from a user, and runs commands. Each | 57 | A shell is a program that accepts input from a user, and runs commands. Each |
58 | "command" in the shell is actually a separate program (unless you are using a | 58 | "command" in the shell is actually a separate program (unless you are using a |
59 | shell like BusyBox, which makes some of the more common commands part of its own | 59 | shell like BusyBox, which makes some of the more common commands part of its own |
60 | program in order to save space). Shells can actually be very powerful, and many | 60 | program in order to save space). Shells can actually be very powerful, and many |
61 | 61 | ||
62 | |||
63 | |||
62 | of them allow you to write something called "shell scripts" which are just a | 64 | of them allow you to write something called "shell scripts" which are just a |
63 | sequence of commands, sometimes with some flow control statements, saved to a | 65 | sequence of commands, sometimes with some flow control statements, saved to a |
64 | file and run each time the script is run. For the most part, the average user | 66 | file and run each time the script is run. For the most part, the average user |
65 | does not need to know about any of this, though. If you are running Opie on the | 67 | does not need to know about any of this, though. If you are running Opie on the |
66 | Familiar distribution, it is advisable to install the bash shell (ipkg install | 68 | Familiar distribution, it is advisable to install the bash shell (ipkg install |
67 | bash) because it offers things like tab completion, use of the backspace key, | 69 | bash) because it offers things like tab completion, use of the backspace key, |
68 | and a command history, as well as offering a more advanced scripting languauge | 70 | and a command history, as well as offering a more advanced scripting languauge |
69 | than most other shells. | 71 | than most other shells. |
70 | </para> | 72 | </para> |
71 | </section> | 73 | </section> |
72 | 74 | ||
73 | <section><title>Running Programs</title> | 75 | <section><title>Running Programs</title> |
@@ -137,25 +139,25 @@ destination, and no filename, it will use the filename for the original file. | |||
137 | </section> | 139 | </section> |
138 | 140 | ||
139 | <section><title>Deleting Files</title> | 141 | <section><title>Deleting Files</title> |
140 | <para> | 142 | <para> |
141 | To delete a file, run the "rm" command, and to delete a directory, run the | 143 | To delete a file, run the "rm" command, and to delete a directory, run the |
142 | "rmdir" command, each of them take the file to be removed as their only | 144 | "rmdir" command, each of them take the file to be removed as their only |
143 | argument. The rmdir command requires the directory to be empty, so if you want | 145 | argument. The rmdir command requires the directory to be empty, so if you want |
144 | to delete a directory that is not empty, along with all its contents, run | 146 | to delete a directory that is not empty, along with all its contents, run |
145 | <userinput>rm -r dir</userinput>. | 147 | <userinput>rm -r dir</userinput>. |
146 | </para> | 148 | </para> |
147 | </section> | 149 | </section> |
148 | 150 | ||
149 | <section><title>Linking Files</title> | 151 | <section id=symlink><title>Linking Files</title> |
150 | <para> | 152 | <para> |
151 | In Linux, you can have a special file called a "symbolic link" that acts just | 153 | In Linux, you can have a special file called a "symbolic link" that acts just |
152 | like a copy of another file, except it takes up less space. This is convinient | 154 | like a copy of another file, except it takes up less space. This is convinient |
153 | if two applications are looking for the same file in two separate places, | 155 | if two applications are looking for the same file in two separate places, |
154 | because the file can be in both places at once, without taking up any extra | 156 | because the file can be in both places at once, without taking up any extra |
155 | space, and any change to one is automatically applied to the other (really, | 157 | space, and any change to one is automatically applied to the other (really, |
156 | there is only one file, the link is just a file pointing to the original file). | 158 | there is only one file, the link is just a file pointing to the original file). |
157 | This is also useful for naming applications independant of their version number. | 159 | This is also useful for naming applications independant of their version number. |
158 | For instance, you could have a link called "application" that points to | 160 | For instance, you could have a link called "application" that points to |
159 | "application1.0". To create a link, use the following command: | 161 | "application1.0". To create a link, use the following command: |
160 | <userinput>ln -s originalfile link</userinput>. | 162 | <userinput>ln -s originalfile link</userinput>. |
161 | </para> | 163 | </para> |