-rw-r--r-- | docs/usermanual/embeddedkonsole.sgm | 4 | ||||
-rw-r--r-- | docs/usermanual/software.sgm | 67 |
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 | |||
@@ -59,6 +59,8 @@ A shell is a program that accepts input from a user, and runs commands. Each | |||
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 |
@@ -146,7 +148,7 @@ to delete a directory that is not empty, along with all its contents, run | |||
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 |
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 | |||
@@ -46,4 +46,71 @@ the same time by marking the ones you want to install and the ones you want to | |||
46 | remove, and then pressing apply. | 46 | remove, and then pressing apply. |
47 | </para> | 47 | </para> |
48 | </section> | 48 | </section> |
49 | |||
50 | <section><title>Destinations</title> | ||
51 | <para> | ||
52 | Software is distributed in a format called "ipkg" which contains all the | ||
53 | necessary files for the program, as well as information on where to put them. | ||
54 | However, this information is only half complete, as it tells the package manager | ||
55 | where in the "destination" to put the files, but the package manager must know | ||
56 | where this "destination" is. The default destination is "/" (called "root") so | ||
57 | if the package says to install a file in opt/QtPalmtop/ then the file will be | ||
58 | installed in /opt/QtPalmtop/. However, if ask the package manger to use a | ||
59 | destination at /mnt/hda/ (this is typically where a compact flash card would be) | ||
60 | then the files will be installed in /mnt/hda/opt/QtPalmtop/. | ||
61 | </para> | ||
62 | <para> | ||
63 | The problem with installing file in a destination other than root is that the | ||
64 | software usually does not know where to fine the installed files, and Opie does | ||
65 | not know where to find the information that tells it how to display the program | ||
66 | in the Launcher. To get around this, the package manager creates links | ||
67 | <footnote><para>See <xref linkend=symlink> for more information on symbolic | ||
68 | links in Linux</para></footnote> from where the files would be if they were | ||
69 | installed in root to where they are actually installed. This means that no more | ||
70 | space is taken up where the files would normally be installed, but any programs | ||
71 | can still find the files where they think they should be. | ||
72 | </para> | ||
73 | |||
74 | <section><title>Using Destinations</title> | ||
75 | <para> | ||
76 | To install a package in a destination other than root, go to | ||
77 | Settings&arrow;Setups to open the settings dialog to the Setups tab. From here | ||
78 | you can select the destination you would like to install the package to from the | ||
79 | pulldown menu at the bottom. You will also want to check "Link to root | ||
80 | destination" so that links are properly made. Once you have selected the | ||
81 | destination you want to install the package to, click the dialog's "Ok" button, | ||
82 | and all packages that you install will be installed to the destination you | ||
83 | selected. | ||
84 | </para> | ||
85 | </section> | ||
86 | <section><title>Adding Destinations</title> | ||
87 | <para> | ||
88 | To add a destination, go to Settings&arrow;Destinations to bring up the settings | ||
89 | dialog at the Destinations tab, and press the "New" button to add a new | ||
90 | Destination to the list. The new destination should be highlighted | ||
91 | automatically, and you can then change the name and the URL with the two text | ||
92 | entry fields below it. The name is only for easy display of the destination, so | ||
93 | name it whatever makes the most sense to you. The URL is the location that you | ||
94 | want the destination to have. So, if you want all your software to be installed | ||
95 | under /usr/directory then you would set the URL to that. You can then click | ||
96 | "Ok" to save, or "x" to cancel the changes. | ||
97 | </para> | ||
98 | </section> | ||
99 | <section><title>Editing Destinations</title> | ||
100 | <para> | ||
101 | You can edit a destination by going to Settings&arrow;Destinations and selecting | ||
102 | the destination that you would like to edit. Then you can edit the Name and URL | ||
103 | fields in the same manner as when you added a destination. To save, click "Ok" | ||
104 | or cancel by clicking "x". | ||
105 | </para> | ||
106 | </section> | ||
107 | <section><title>Deleting Destinations</title> | ||
108 | <para> | ||
109 | Deleting a destination is very easy. Go to Settings&arrow;Destinations and | ||
110 | select the Destination that you would like to delete in the dialog that appears. | ||
111 | Press the "Remove" button to delete the destination, and press "Ok" to save the | ||
112 | changes, or "x" to cancel them. | ||
113 | </para> | ||
114 | </section> | ||
115 | </section> | ||
49 | </chapter> \ No newline at end of file | 116 | </chapter> \ No newline at end of file |