summaryrefslogtreecommitdiff
path: root/docs
authorspiralman <spiralman>2002-07-30 19:37:51 (UTC)
committer spiralman <spiralman>2002-07-30 19:37:51 (UTC)
commit38714c22a9c99c920bd42dbf7ba81622b735fe16 (patch) (side-by-side diff)
treeb446b829652e74aa44d65cfe19b23cd0867b7c1b /docs
parent988409a5a21b3a4238ce41316e48777c885f147a (diff)
downloadopie-38714c22a9c99c920bd42dbf7ba81622b735fe16.zip
opie-38714c22a9c99c920bd42dbf7ba81622b735fe16.tar.gz
opie-38714c22a9c99c920bd42dbf7ba81622b735fe16.tar.bz2
Added section about destinations to oipkg docs.
Diffstat (limited to 'docs') (more/less context) (show whitespace changes)
-rw-r--r--docs/usermanual/embeddedkonsole.sgm4
-rw-r--r--docs/usermanual/software.sgm67
2 files changed, 70 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
@@ -46,32 +46,34 @@ The other icons are the same as typing (from left to right) enter, space, tab
<para>
The command list is a pulldown menu with a list of commonly used commands.
Selecting one will type the command into the terminal wherever the cursor is.
You can edit or hide this menu from <GUIMenu>Options</GUIMenu>&arrow;
<GUIMenuItem>Command List.</GUIMenuItem>
</para>
</section>
</section>
<section><title>What is a Shell</title>
<para>
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
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.
</para>
</section>
<section><title>Running Programs</title>
<para>
To 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 "."
@@ -133,31 +135,31 @@ newfile</userinput>. 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.
</para>
</section>
<section><title>Deleting Files</title>
<para>
To 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
<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,
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:
<userinput>ln -s originalfile link</userinput>.
</para>
</section>
</chapter> \ No newline at end of file
diff --git a/docs/usermanual/software.sgm b/docs/usermanual/software.sgm
index 459498a..f95772c 100644
--- a/docs/usermanual/software.sgm
+++ b/docs/usermanual/software.sgm
@@ -33,17 +33,84 @@ 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.
</para>
</section>
<section><title>Removing Software</title>
<para>
Removing 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.
</para>
</section>
+
+<section><title>Destinations</title>
+<para>
+Software is distributed in a format called "ipkg" which contains all the
+necessary files for the program, as well as information on where to put them.
+However, this information is only half complete, as it tells the package manager
+where in the "destination" to put the files, but the package manager must know
+where this "destination" is. The default destination is "/" (called "root") so
+if the package says to install a file in opt/QtPalmtop/ then the file will be
+installed in /opt/QtPalmtop/. However, if ask the package manger to use a
+destination at /mnt/hda/ (this is typically where a compact flash card would be)
+then the files will be installed in /mnt/hda/opt/QtPalmtop/.
+</para>
+<para>
+The problem with installing file in a destination other than root is that the
+software usually does not know where to fine the installed files, and Opie does
+not know where to find the information that tells it how to display the program
+in the Launcher. To get around this, the package manager creates links
+<footnote><para>See <xref linkend=symlink> for more information on symbolic
+links in Linux</para></footnote> from where the files would be if they were
+installed in root to where they are actually installed. This means that no more
+space is taken up where the files would normally be installed, but any programs
+can still find the files where they think they should be.
+</para>
+
+<section><title>Using Destinations</title>
+<para>
+To install a package in a destination other than root, go to
+Settings&arrow;Setups to open the settings dialog to the Setups tab. From here
+you can select the destination you would like to install the package to from the
+pulldown menu at the bottom. You will also want to check "Link to root
+destination" so that links are properly made. Once you have selected the
+destination you want to install the package to, click the dialog's "Ok" button,
+and all packages that you install will be installed to the destination you
+selected.
+</para>
+</section>
+<section><title>Adding Destinations</title>
+<para>
+To add a destination, go to Settings&arrow;Destinations to bring up the settings
+dialog at the Destinations tab, and press the "New" button to add a new
+Destination to the list. The new destination should be highlighted
+automatically, and you can then change the name and the URL with the two text
+entry fields below it. The name is only for easy display of the destination, so
+name it whatever makes the most sense to you. The URL is the location that you
+want the destination to have. So, if you want all your software to be installed
+under /usr/directory then you would set the URL to that. You can then click
+"Ok" to save, or "x" to cancel the changes.
+</para>
+</section>
+<section><title>Editing Destinations</title>
+<para>
+You can edit a destination by going to Settings&arrow;Destinations and selecting
+the destination that you would like to edit. Then you can edit the Name and URL
+fields in the same manner as when you added a destination. To save, click "Ok"
+or cancel by clicking "x".
+</para>
+</section>
+<section><title>Deleting Destinations</title>
+<para>
+Deleting a destination is very easy. Go to Settings&arrow;Destinations and
+select the Destination that you would like to delete in the dialog that appears.
+ Press the "Remove" button to delete the destination, and press "Ok" to save the
+changes, or "x" to cancel them.
+</para>
+</section>
+</section>
</chapter> \ No newline at end of file