summaryrefslogtreecommitdiff
path: root/docs/usermanual
Unidiff
Diffstat (limited to 'docs/usermanual') (more/less context) (ignore whitespace changes)
-rw-r--r--docs/usermanual/usermanual.tex16
1 files changed, 16 insertions, 0 deletions
diff --git a/docs/usermanual/usermanual.tex b/docs/usermanual/usermanual.tex
index ebfc456..97df90c 100644
--- a/docs/usermanual/usermanual.tex
+++ b/docs/usermanual/usermanual.tex
@@ -274,25 +274,41 @@ The command list is a pulldown menu with a list of commonly used commands. Sele
274 274
275A 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 Familiar distribution, it is advisable to install the bash shell (ipkg install bash) because it offers things like tab completion, use of the backspace key, and a command history, as well as offering a more advanced scripting languauge than most other shells. 275A 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 Familiar distribution, it is advisable to install the bash shell (ipkg install bash) because it offers things like tab completion, use of the backspace key, and a command history, as well as offering a more advanced scripting languauge than most other shells.
276 276
277\section{Running Programs} 277\section{Running Programs}
278 278
279To run a program or a command (remember, a command is just another program), you simply type the name of the program and hit ``Return'' (in Linux, program names do not have a special suffix like they do in windows, in fact the ``.'' character has no special meaning unless it is at the begining of a filename, in which case it makes the file ``hidden''). When you type a program name and hit ``Return'' the shell looks in a special list of directories called your ``path'', and if it cannot find it in any of those directories, it stops looking and tells you it could not find them. If you want to run a program that is not in your path, you must specify an absolute or relative path to that program. For instance, to run a program that is in the directory you are currently in, you would type \verb+./program+ (``./'' is a special directory that is explained below), or to run a program in /home/username/ you would call \verb+/home/username/program+. 279To run a program or a command (remember, a command is just another program), you simply type the name of the program and hit ``Return'' (in Linux, program names do not have a special suffix like they do in windows, in fact the ``.'' character has no special meaning unless it is at the begining of a filename, in which case it makes the file ``hidden''). When you type a program name and hit ``Return'' the shell looks in a special list of directories called your ``path'', and if it cannot find it in any of those directories, it stops looking and tells you it could not find them. If you want to run a program that is not in your path, you must specify an absolute or relative path to that program. For instance, to run a program that is in the directory you are currently in, you would type \verb+./program+ (``./'' is a special directory that is explained below), or to run a program in /home/username/ you would call \verb+/home/username/program+.
280 280
281Most programs take ``arguments'' when run from the command line. An argument is a string that contains no spaces that changes how the program behaves (a text editor, for instance, might take a single argument, which would be the name of the file you wish to edit). Usually, you can use the arguments ``-h'' or ``--help'' to get a list of the common arguments that that program takes, along with a short usage description, and a short description of what each argument does. 281Most programs take ``arguments'' when run from the command line. An argument is a string that contains no spaces that changes how the program behaves (a text editor, for instance, might take a single argument, which would be the name of the file you wish to edit). Usually, you can use the arguments ``-h'' or ``--help'' to get a list of the common arguments that that program takes, along with a short usage description, and a short description of what each argument does.
282 282
283\section{Basic Navigation} 283\section{Basic Navigation}
284 284
285The command that you will use most often in the shell is probably the ``cd'' command, which stands for ``change directory.'' With this command, you can move around in the file system, by issuing the command like this: \verb+cd [new directory]+, where \verb+[new directory]+ is the directory you want to move to. This directory name does not have to include the entire directory structure, but can be ``relative'' which means it assumes you are talking about directories relative to the directory you are in. For example, if you are in a directory called /home/username and you want to move to the directory /home/username/other/dir you could simply type \verb+cd other/dir+ and you would end up in /home/username/other/dir. You can also specify a full, or ``absolute'' path, by specifying the entire path name starting with / ( / is a special directory called the ``root'' directory, and does not have a ``parent'' directory, which means that it is not in any other directory). There are also two special directories called ``./'' and ``../''. The ``./'' directory is the current directory you are in, and you will probably never use this in conjunction with the cd command (why would you want to move to the directory you are already in?). The ``../'' directory represents the parent directory of the directory you are currently in, so if you are in /home/username, ../ is the same as /home. You can string several ../'s together, so if you are in /home/username/dir/ ../../ represents /home. There is one other special directory, called ``$\sim$/'' that points to your home directory (usually /home/username or /root for the root user). 285The command that you will use most often in the shell is probably the ``cd'' command, which stands for ``change directory.'' With this command, you can move around in the file system, by issuing the command like this: \verb+cd [new directory]+, where \verb+[new directory]+ is the directory you want to move to. This directory name does not have to include the entire directory structure, but can be ``relative'' which means it assumes you are talking about directories relative to the directory you are in. For example, if you are in a directory called /home/username and you want to move to the directory /home/username/other/dir you could simply type \verb+cd other/dir+ and you would end up in /home/username/other/dir. You can also specify a full, or ``absolute'' path, by specifying the entire path name starting with / ( / is a special directory called the ``root'' directory, and does not have a ``parent'' directory, which means that it is not in any other directory). There are also two special directories called ``./'' and ``../''. The ``./'' directory is the current directory you are in, and you will probably never use this in conjunction with the cd command (why would you want to move to the directory you are already in?). The ``../'' directory represents the parent directory of the directory you are currently in, so if you are in /home/username, ../ is the same as /home. You can string several ../'s together, so if you are in /home/username/dir/ ../../ represents /home. There is one other special directory, called ``$\sim$/'' that points to your home directory (usually /home/username or /root for the root user).
286 286
287\section{Moving Files} 287\section{Moving Files}
288 288
289To move files around, you need to use the ``cp'' (copy) and ``mv'' (move) commands. Both of these are run the same way: \verb+command originalfile newfile+. The only difference is that cp creates a new file without touching the old one, while mv deletes the original file. The two path names can be either absolute or relative. If you only specify a directory for the destination, and no filename, it will use the filename for the original file. 289To move files around, you need to use the ``cp'' (copy) and ``mv'' (move) commands. Both of these are run the same way: \verb+command originalfile newfile+. The only difference is that cp creates a new file without touching the old one, while mv deletes the original file. The two path names can be either absolute or relative. If you only specify a directory for the destination, and no filename, it will use the filename for the original file.
290 290
291\section{Deleting Files} 291\section{Deleting Files}
292 292
293To delete a file, run the ``rm'' command, and to delete a directory, run the ``rmdir'' command, each of them take the file to be removed as their only argument. The rmdir command requires the directory to be empty, so if you want to delete a directory that is not empty, along with all its contents, run \verb+rm -r dir+. 293To delete a file, run the ``rm'' command, and to delete a directory, run the ``rmdir'' command, each of them take the file to be removed as their only argument. The rmdir command requires the directory to be empty, so if you want to delete a directory that is not empty, along with all its contents, run \verb+rm -r dir+.
294 294
295\section{Linking Files} 295\section{Linking Files}
296 296
297In 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, because the file can be in both places at once, without taking up any extra space, and any change to one is automatically applied to the other (really, there is only one file, the link is just a file pointing to the original file). This is also useful for naming applications independant of their version number. For instance, you could have a link called ``application'' that points to ``application1.0''. To create a link, use the following command: \verb+ln -s originalfile link+. 297In 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, because the file can be in both places at once, without taking up any extra space, and any change to one is automatically applied to the other (really, there is only one file, the link is just a file pointing to the original file). This is also useful for naming applications independant of their version number. For instance, you could have a link called ``application'' that points to ``application1.0''. To create a link, use the following command: \verb+ln -s originalfile link+.
298
299\part{Settings}
300\chapter{Software}
301%This section needs a lot of work, describing things like destinations, feeds, etc, but this should probably be added after oipkg works properly.
302
303The ``Software'' application, also called oipkg, is what is used to install and remove software. It is actually a frontend to the command line program ``ipkg'' so most things you can do with oipkg you can also do with ipkg. Oipkg can install things either remotely from a web server (called a ``feed'') or it can install an ipkg package file that resides on the local filesystem.
304
305Note: There is a bug in oipkg that prevents it from installing packages properly. There is, however, a workaround for it. Simply run oipkg from Embedded Konsole to avoid the bug.
306
307\section{Installing Software}
308
309To install software, first select ``Opie'' from the ``Section'' pulldown menu, the press the ``+'' icon next to ``Feeds'' in the main view. This will show all the available Opie packages (you can change which packages to view by selecting something else from the ``Section'' pulldown). Installed packages are marked with a blue circle, while packages that are not installed are marked with a red box. If you click on the icon for an uninstalled package, it will turn into an open box, with a blue circle coming out of it, indicating that you have marked this package to be installed. Mark as many packages as you wish this way, and then press the ``Apply'' icon (same red box and blue dot icon) to install all the marked packages. It will also remove any packages marked for removal (see below). Clicking this will open a window showing all the packages marked to be removed and installed, with some check boxes on the bottom, which represent arguments to be sent to ipkg, which you can usually ignore. After verifying that all the packages to be installed are correct, press ``Ok'' in the upper right corner (or press ``x'' to cancel and go back to the package selection window). The packages should then install, and you should see their icons appear in the Launcher, if they are Opie applications.
310
311\section{Removing Software}
312
313Removing software is the same as installing software, except you will press the blue circle icon of an installed package, and it will have a red ``X'' over it. Then press the apply icon, and ``Ok''. You can install and remove packages at the same time by marking the ones you want to install and the ones you want to remove, and then pressing apply.
298\end{document} \ No newline at end of file 314\end{document} \ No newline at end of file