Merge lp:~littlergirl/kubuntu-docs/media into lp:kubuntu-docs/precise
- media
- Merge into precise
Proposed by
Little Girl
Status: | Merged |
---|---|
Merge reported by: | David Wonderly |
Merged at revision: | not available |
Proposed branch: | lp:~littlergirl/kubuntu-docs/media |
Merge into: | lp:kubuntu-docs/precise |
Diff against target: |
4104 lines (+1095/-919) 8 files modified
docs/audio/C/audio.xml (+47/-45) docs/bugs/C/bugs.xml (+215/-169) docs/cli/C/cli.xml (+143/-158) docs/media/C/media.xml (+52/-44) docs/network/C/network.xml (+30/-27) docs/security/C/security.xml (+45/-42) docs/sharing/C/sharing.xml (+522/-399) docs/video/C/video.xml (+41/-35) |
To merge this branch: | bzr merge lp:~littlergirl/kubuntu-docs/media |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ubuntu Documentation Committers | Pending | ||
Review via email:
|
Commit message
Description of the change
* Added an entity.
* Added some tags.
* Fixed some grammar.
* Fixed some punctuation.
* Rewrapped some text.
To post a comment you must log in.
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1 | === modified file 'docs/audio/C/audio.xml' |
2 | --- docs/audio/C/audio.xml 2011-12-30 16:40:04 +0000 |
3 | +++ docs/audio/C/audio.xml 2012-03-22 19:19:20 +0000 |
4 | @@ -22,20 +22,20 @@ |
5 | <title>Playing CDs</title> |
6 | <para> |
7 | <application>Amarok</application> is the default application for playing audio |
8 | -<acronym>CDs</acronym> in &kubuntu;. When a <acronym>CD</acronym> is inserted, |
9 | +<acronym>CD</acronym>s in &kubuntu;. When a <acronym>CD</acronym> is inserted, |
10 | &kubuntu; will recognize it and display default options. To hear the content |
11 | with <application>Amarok</application>, select <guilabel>Play Audio CD with |
12 | Amarok</guilabel> and then press the <guibutton>OK</guibutton> button. |
13 | &kubuntu; can be configured to remember this choice every time |
14 | a <acronym>CD</acronym> is inserted by selecting <guilabel>Always do |
15 | this for this type of media</guilabel>, and pressing <guibutton>OK</guibutton>. |
16 | -<application>Amarok</application> also offers other useful features. If connected to |
17 | -the Internet, <application>Amarok</application> will retrieve |
18 | +<application>Amarok</application> also offers other useful features. If |
19 | +connected to the Internet, <application>Amarok</application> will retrieve |
20 | <acronym>CD</acronym> artist, title, and track data from <ulink |
21 | url="http://freedb.org">freedb.org</ulink>. It will also download the lyrics |
22 | -for the current selection if they are available by choosing the |
23 | -<guilabel>Lyrics</guilabel> tab. Other Artist information can be found on <ulink |
24 | -url="http://www.wikipedia.org">Wikipedia</ulink> by selecting the |
25 | +for the current selection — if they are available — by choosing the |
26 | +<guilabel>Lyrics</guilabel> tab. Other artist information can be found on |
27 | +<ulink url="http://www.wikipedia.org">Wikipedia</ulink> by selecting the |
28 | <guilabel>Artist</guilabel> tab. |
29 | </para> |
30 | </sect1> |
31 | @@ -44,19 +44,21 @@ |
32 | <title>Editing Audio </title> |
33 | |
34 | <para> |
35 | -For editing audio files, &kubuntu; provides <application>Sound Editor (Audacity)</application>, |
36 | -a full-featured, free and open source software application. To use |
37 | -<application>Sound Editor (Audacity)</application>: |
38 | +For editing audio files, &kubuntu; provides <application>Sound Editor |
39 | +(Audacity)</application>, a full-featured, free, and open source software |
40 | +application. To use <application>Sound Editor (Audacity)</application>: |
41 | </para> |
42 | <procedure> |
43 | <step> |
44 | <para> |
45 | -Install <application>Sound Editor (Audacity)</application> from the package manager (Muon) |
46 | +Install <application>Sound Editor (Audacity)</application> from the package |
47 | +manager (Muon). |
48 | </para> |
49 | </step> |
50 | <step> |
51 | <para> |
52 | -Run <application>Sound Editor (Audacity)</application> by going to &menuaudacity;. |
53 | +Run <application>Sound Editor (Audacity)</application> by going to |
54 | +&menuaudacity;. |
55 | </para> |
56 | </step> |
57 | <step> |
58 | @@ -64,8 +66,7 @@ |
59 | Detailed instructions (including tutorials and weblinks) on using |
60 | <application>Sound Editor (Audacity)</application> can be found by going to |
61 | <menuchoice> |
62 | -<guimenu>Help</guimenu> |
63 | -<guisubmenu>Contents</guisubmenu> |
64 | +<guimenu>Help</guimenu> <guisubmenu>Contents</guisubmenu> |
65 | </menuchoice> from within <application>Sound Editor (Audacity)</application>. |
66 | </para> |
67 | </step> |
68 | @@ -78,7 +79,7 @@ |
69 | <para> |
70 | In addition to being the default music player in &kubuntu;, |
71 | <application>Amarok</application> is also helpful for managing music |
72 | -collections. Start <application>Amarok</application> by going to &menuamarok;. |
73 | +collections. Start <application>Amarok</application> by going to &menuamarok;. |
74 | </para> |
75 | <para> |
76 | Another useful <application>Amarok</application> feature is the built-in ID3 |
77 | @@ -93,10 +94,11 @@ |
78 | |
79 | <para> |
80 | Another exciting <application>Amarok</application> feature is the ability to |
81 | -play music directly from an iPod or other portable device. <application>Amarok</application> can also be |
82 | -used to transfer music files to and from an iPod. Please refer to the <ulink |
83 | -type="help" url="help:/amarok">Amarok Handbook</ulink> for more information on |
84 | -transferring and managing iPod media files. |
85 | +play music directly from an iPod or other portable device. |
86 | +<application>Amarok</application> can also be used to transfer music files to |
87 | +and from an iPod. Please refer to the <ulink type="help" |
88 | +url="help:/amarok">Amarok Handbook</ulink> for more information on transferring |
89 | +and managing iPod media files. |
90 | </para> |
91 | </sect1> |
92 | |
93 | @@ -105,30 +107,29 @@ |
94 | <procedure> |
95 | <step> |
96 | <para> |
97 | -When a blank <acronym>CD</acronym> is inserted, &kubuntu; will |
98 | -recognize it, mount it, and then ask what to do with the <acronym>CD</acronym>. |
99 | -Choose <guilabel>Create an audio CD with K3B</guilabel> and press |
100 | -<guibutton>OK</guibutton>. This will open |
101 | -<application>K3b</application>, the <acronym>CD</acronym> and |
102 | -<acronym>DVD</acronym> Kreator, and provide various options. |
103 | +When a blank <acronym>CD</acronym> is inserted, &kubuntu; will recognize it, |
104 | +mount it, and then ask what to do with the <acronym>CD</acronym>. Choose |
105 | +<guilabel>Create an audio CD with K3B</guilabel> and press |
106 | +<guibutton>OK</guibutton>. This will open the <application>K3b</application> |
107 | +<acronym>CD</acronym> and <acronym>DVD</acronym> creator, and provide various |
108 | +options. |
109 | </para> |
110 | </step> |
111 | <step> |
112 | <para> |
113 | -To start <application>K3b</application> manually, go to <guilabel>Kickoff Application |
114 | -> Applications > Multimedia > </guilabel><application>Disk Burning (K3b)</application>. |
115 | +To start <application>K3b</application> manually, go to &menuk3b;. |
116 | </para> |
117 | </step> |
118 | <step> |
119 | <para> |
120 | Select <guilabel>New Audio CD Project</guilabel> in the <guilabel>New |
121 | -Project</guilabel> dropdown menu. |
122 | +Project</guilabel> drop-down menu. |
123 | </para> |
124 | </step> |
125 | <step> |
126 | <para> |
127 | Inside <application>K3b</application>, browse and select the tracks to be |
128 | -ripped. Then drag and drop the tracks in the white area at the bottom of the |
129 | +ripped. Then drag and drop the tracks into the white area at the bottom of the |
130 | <application>K3b</application> window. |
131 | <mediaobject> |
132 | <imageobject> |
133 | @@ -154,9 +155,10 @@ |
134 | <itemizedlist> |
135 | <listitem> |
136 | <para> |
137 | -<guilabel>Writing</guilabel> - provides choices related to burning an image from |
138 | -the files selected in the previous step. |
139 | -<note><title>No MP3 Support by Default</title> |
140 | +<guilabel>Writing</guilabel> - provides choices related to burning an image |
141 | +from the files selected in the previous step. |
142 | +<note> |
143 | +<title>No MP3 Support by Default</title> |
144 | <para> |
145 | <acronym>MP3</acronym> is a protocol restricted by patents. In order to use it |
146 | with <application>K3b</application>, please refer to the information at the end |
147 | @@ -194,36 +196,36 @@ |
148 | </step> |
149 | </procedure> |
150 | <para> |
151 | -<application>K3b</application> can extract audio files to the following formats: |
152 | +<application>K3b</application> can extract audio files to the following |
153 | +formats: |
154 | <itemizedlist> |
155 | <listitem> |
156 | <para> |
157 | -<emphasis role="strong">Ogg Vorbis</emphasis> - Ogg |
158 | -Vorbis is a patent-free lossy audio compression format which usually produces |
159 | -higher quality and greater compression than MP3. See the <ulink |
160 | -url="http://www.vorbis.com/faq/">Vorbis website</ulink> for more information. |
161 | +<emphasis role="strong">Ogg Vorbis</emphasis> - Ogg Vorbis is a patent-free |
162 | +lossy audio compression format which usually produces higher quality and |
163 | +greater compression than MP3. See the <ulink url="http://www.vorbis.com/faq/"> |
164 | +Vorbis website</ulink> for more information. |
165 | </para> |
166 | </listitem> |
167 | <listitem> |
168 | <para><emphasis role="strong">FLAC</emphasis> - The Free Lossless Audio |
169 | -Codec, <acronym>FLAC</acronym>, can compress audio files up to 50% without removing |
170 | -any information from the audio stream. For more information on this format, see |
171 | -the <ulink url="http://flac.sourceforge.net/">FLAC homepage</ulink> on |
172 | -sourceforge.net. |
173 | +Codec, <acronym>FLAC</acronym>, can compress audio files up to 50% without |
174 | +removing any information from the audio stream. For more information on this |
175 | +format, see the <ulink url="http://flac.sourceforge.net/">FLAC |
176 | +homepage</ulink> on <trademark>Sourceforge</trademark>. |
177 | </para> |
178 | </listitem> |
179 | <listitem> |
180 | -<para><emphasis role="strong">WAV</emphasis> - Wav is an |
181 | -uncompressed audio format that can be compressed into OGG Vorbis or a codec of |
182 | -your choice. It is often edited in applications such as Audacity before being |
183 | -compressed. |
184 | +<para><emphasis role="strong">WAV</emphasis> - Wav is an uncompressed audio |
185 | +format that can be compressed into OGG Vorbis or a codec of your choice. It is |
186 | +often edited in applications such as Audacity before being compressed. |
187 | </para> |
188 | </listitem> |
189 | </itemizedlist> |
190 | </para> |
191 | <para> |
192 | CD audio files can be extracted to the proprietary, non-free |
193 | -<emphasis role="strong">MP3</emphasis> lossy format by using the |
194 | +<emphasis role="strong">MP3</emphasis> lossy format by using the |
195 | <application>lame</application> encoder. Please refer to the <ulink type="help" |
196 | url="help:/kubuntu/add-applications/">Adding Applications</ulink> documentation |
197 | for help with installing applications such as <application>lame</application>. |
198 | |
199 | === modified file 'docs/bugs/C/bugs.xml' |
200 | --- docs/bugs/C/bugs.xml 2011-09-15 05:13:39 +0000 |
201 | +++ docs/bugs/C/bugs.xml 2012-03-22 19:19:20 +0000 |
202 | @@ -28,8 +28,8 @@ |
203 | <varlistentry><term>Crash</term> |
204 | <listitem> |
205 | <para> |
206 | -An application or system crash or failure. Most of the time, a crash dialog will |
207 | -be presented that can be turned into a bug report. |
208 | +An application or system crash or failure. Most of the time a crash dialog will |
209 | +be presented. This can be turned into a bug report. |
210 | </para> |
211 | </listitem> |
212 | </varlistentry> |
213 | @@ -59,19 +59,25 @@ |
214 | <title>KDE's Bug Tracking System</title> |
215 | <para><ulink url="https://bugs.kde.org/"/></para> |
216 | <para> |
217 | -KDE uses Bugzilla, a "Defect Tracking System". Bugzilla is one of the |
218 | -most popular tools used in the open source development community. |
219 | +<trademark>KDE</trademark> uses <trademark>Bugzilla</trademark>, a |
220 | +<quote>Defect Tracking System</quote>. <trademark>Bugzilla</trademark> is one |
221 | +of the most popular tools used in the open source development community. |
222 | </para> |
223 | <note><title>Register first</title> |
224 | <para> |
225 | -To report a bug, one must register for an account on KDE's Bugzilla |
226 | -at <ulink url="https://bugs.kde.org/createaccount.cgi"/>. A valid email address |
227 | -is required for registration. |
228 | +To report a bug, one must register for an account on |
229 | +<trademark>KDE</trademark>'s <trademark>Bugzilla</trademark> at <ulink |
230 | +url="https://bugs.kde.org/createaccount.cgi"/>. A valid email address is |
231 | +required for registration. |
232 | </para> |
233 | </note> |
234 | <note><title>Only for KDE bugs</title> |
235 | <para> |
236 | -Bugzilla is only for KDE bugs. If the application is not part of KDE, for instance Firefox, LibreOffice, or VLC, then the report should be filed in Launchpad instead. Please see the next section, which covers filing reports concerning Launchpad. |
237 | +<trademark>Bugzilla</trademark> is only for <trademark>KDE</trademark> bugs. If |
238 | +the application is not part of <trademark>KDE</trademark> — Firefox, |
239 | +LibreOffice, or VLC, for instance — then the report should be filed in |
240 | +Launchpad instead. Please see the next section, which covers filing reports |
241 | +concerning Launchpad. |
242 | </para> |
243 | </note> |
244 | </sect2> |
245 | @@ -79,22 +85,24 @@ |
246 | <title>Launchpad</title> |
247 | <para><ulink url="https://launchpad.net/"/></para> |
248 | <para> |
249 | -Launchpad is an open source suite of tools that help people and teams to work |
250 | -together on software projects. Launchpad is used by the Ubuntu and &kubuntu; |
251 | -Projects, as well as various other open source projects. |
252 | +<trademark>Launchpad</trademark> is an open source suite of tools that help |
253 | +people and teams to work together on software projects. Launchpad is used by |
254 | +the &ubuntu; and &kubuntu; projects, as well as various other open source |
255 | +projects. |
256 | </para> |
257 | <note><title>Register first</title> |
258 | <para> |
259 | -To report a bug, one must register for a Launchpad account at |
260 | -<ulink url="https://launchpad.net/+login"/>. A valid email address is required |
261 | -for registration. |
262 | +To report a bug, one must register for a <trademark>Launchpad</trademark> |
263 | +account at <ulink url="https://launchpad.net/+login"/>. A valid email address |
264 | +is required for registration. |
265 | </para> |
266 | </note> |
267 | <note><title>For any bug in &kubuntu;</title> |
268 | <para> |
269 | -Launchpad can be used to file a bug report for any application available in the |
270 | -Ubuntu or &kubuntu; repositories. For KDE applications, the |
271 | -KDE Bug Tracking system (above) is preferred. |
272 | +<trademark>Launchpad</trademark> can be used to file a bug report for any |
273 | +application available in the &ubuntu; or &kubuntu; repositories. For |
274 | +<trademark>KDE</trademark> applications, the <trademark>KDE Bug |
275 | +Tracking</trademark> system (above) is preferred. |
276 | </para> |
277 | </note> |
278 | </sect2> |
279 | @@ -104,18 +112,19 @@ |
280 | <title>Filing a Crash Report</title> |
281 | <para> |
282 | When an application crashes in &kubuntu;, the appropriate crash dialog will |
283 | -appear. It is usually easy to file a bug report from the dialog. With a KDE |
284 | -application, the KDE crash dialog will appear along with instructions |
285 | -for reporting the bug. Otherwise, the Ubuntu crash dialog will appear with |
286 | -instructions for filing a bug on Launchpad. |
287 | +appear. It is usually easy to file a bug report from the dialog. With a |
288 | +<trademark>KDE</trademark> application, the <trademark>KDE</trademark> crash |
289 | +dialog will appear along with instructions for reporting the bug. Otherwise, |
290 | +the &ubuntu; crash dialog will appear with instructions for filing a bug on |
291 | +<trademark>Launchpad</trademark>. |
292 | </para> |
293 | <sect2 id="filing-crash-kde"> |
294 | <title>KDE</title> |
295 | <para> |
296 | -When an application crashes in KDE, a crash dialog will be presented that is |
297 | -similar to the following images. The first image shows the |
298 | -<guilabel>General</guilabel> tab which provides an overview of the crash. The |
299 | -second image shows the <guilabel>Developer Information</guilabel> tab which |
300 | +When an application crashes in <trademark>KDE</trademark>, a crash dialog will |
301 | +be presented that is similar to the following images. The first image shows the |
302 | +<guilabel>General</guilabel> tab, which provides an overview of the crash. The |
303 | +second image shows the <guilabel>Developer Information</guilabel> tab, which |
304 | provides trace information that is useful to developers. |
305 | </para> |
306 | <para> |
307 | @@ -139,10 +148,10 @@ |
308 | </example> |
309 | </para> |
310 | <para> |
311 | -If the trace information is deemed valuable, filing a bug report is |
312 | -easy with the crash dialog wizard. If the trace is not deemed valuable, then it |
313 | -is not possible to file a bug report with the wizard. The bug report can still |
314 | -be filed manually at <ulink url="https://bugs.kde.org/"/>. |
315 | +If the trace information is deemed valuable, filing a bug report is easy with |
316 | +the crash dialog wizard. If the trace is not deemed valuable, then it is not |
317 | +possible to file a bug report with the wizard. The bug report can still be |
318 | +filed manually at <ulink url="https://bugs.kde.org/"/>. |
319 | </para> |
320 | <para> |
321 | To complete the bug reporting process, follow the procedure below. |
322 | @@ -151,14 +160,15 @@ |
323 | <step> |
324 | <para> |
325 | <mousebutton>Click</mousebutton> the <guibutton>Report Bug</guibutton> button. |
326 | -The following dialog will appear. |
327 | +The following dialog will appear: |
328 | </para> |
329 | <para> |
330 | <example> |
331 | <title>Welcome to the Reporting Assistant</title> |
332 | <mediaobject> |
333 | <imageobject> |
334 | -<imagedata fileref="help:/images/C/crash_report_assistant_welcome.png" format="PNG"/> |
335 | +<imagedata |
336 | +fileref="help:/images/C/crash_report_assistant_welcome.png" format="PNG"/> |
337 | </imageobject> |
338 | </mediaobject> |
339 | </example> |
340 | @@ -167,14 +177,15 @@ |
341 | <step> |
342 | <para> |
343 | <mousebutton>Click</mousebutton> the <guibutton>Next</guibutton> button. The |
344 | -following dialog will appear. |
345 | +following dialog will appear: |
346 | </para> |
347 | <para> |
348 | <example> |
349 | <title>What do you know about the crash?</title> |
350 | <mediaobject> |
351 | <imageobject> |
352 | -<imagedata fileref="help:/images/C/crash_report_assistant_about_crash.png" format="PNG"/> |
353 | +<imagedata |
354 | +fileref="help:/images/C/crash_report_assistant_about_crash.png" format="PNG"/> |
355 | </imageobject> |
356 | </mediaobject> |
357 | </example> |
358 | @@ -183,15 +194,17 @@ |
359 | <step> |
360 | <para> |
361 | Select the applicable options. The drop-down box under the question, |
362 | -"<guilabel>Does the application crash again if you repeat the |
363 | -same situation?</guilabel>" has several options. |
364 | +<quote><guilabel>Does the application crash again if you repeat the |
365 | +same situation?</guilabel></quote> has several options. |
366 | </para> |
367 | <para> |
368 | <example> |
369 | <title>Does the application crash again if you repeat the same situation?</title> |
370 | <mediaobject> |
371 | <imageobject> |
372 | -<imagedata fileref="help:/images/C/crash_report_assistant_about_crash_dropdown.png" format="PNG"/> |
373 | +<imagedata |
374 | +fileref="help:/images/C/crash_report_assistant_about_crash_dropdown.png" |
375 | +format="PNG"/> |
376 | </imageobject> |
377 | </mediaobject> |
378 | </example> |
379 | @@ -205,18 +218,21 @@ |
380 | </step> |
381 | <step> |
382 | <para> |
383 | -Depending on the information available in the crash report, either of two |
384 | +Depending on the information available in the crash report, either of two |
385 | dialogs will appear. One is a dialog that indicates that there is not enough |
386 | information to file a good report. The other is a dialog indicating that the |
387 | -information is useful, and that it would be helpful to continue with filing the |
388 | +information is useful and that it would be helpful to continue with filing the |
389 | report. |
390 | </para> |
391 | <para> |
392 | <example> |
393 | -<title>Not enough information for developers to continue the reporting process</title> |
394 | +<title>Not enough information for developers to continue the reporting |
395 | +process</title> |
396 | <mediaobject> |
397 | <imageobject> |
398 | -<imagedata fileref="help:/images/C/crash_report_assistant_not_enough_info.png" format="PNG"/> |
399 | +<imagedata |
400 | +fileref="help:/images/C/crash_report_assistant_not_enough_info.png" |
401 | +format="PNG"/> |
402 | </imageobject> |
403 | </mediaobject> |
404 | </example> |
405 | @@ -226,7 +242,9 @@ |
406 | <title>This crash information is useful</title> |
407 | <mediaobject> |
408 | <imageobject> |
409 | -<imagedata fileref="help:/images/C/crash_report_assistant_useful_information.png" format="PNG"/> |
410 | +<imagedata |
411 | +fileref="help:/images/C/crash_report_assistant_useful_information.png" |
412 | +format="PNG"/> |
413 | </imageobject> |
414 | </mediaobject> |
415 | </example> |
416 | @@ -235,7 +253,7 @@ |
417 | <para> |
418 | It may be necessary to install the proper debug packages in order to get a good |
419 | trace. Such packages include <filename>kdebase-dbg</filename>, |
420 | -<filename>kdebase-workspace-dbg</filename>, |
421 | +<filename>kdebase-workspace-dbg</filename>, and |
422 | <filename>kdebase-runtime-dbg</filename>. |
423 | </para> |
424 | </note> |
425 | @@ -243,36 +261,42 @@ |
426 | <step> |
427 | <para> |
428 | If enough information was provided to continue filing a bug report using |
429 | -the assistant, a dialog will appear to allow logging in to KDE's Bugzilla. |
430 | +the assistant, a dialog will appear to allow logging in to |
431 | +<trademark>KDE</trademark>'s <trademark>Bugzilla</trademark>. |
432 | </para> |
433 | <para> |
434 | <example> |
435 | <title>KDE Bug Tracking System Login</title> |
436 | <mediaobject> |
437 | <imageobject> |
438 | -<imagedata fileref="help:/images/C/crash_report_assistant_bugtracker_login.png" format="PNG"/> |
439 | +<imagedata |
440 | +fileref="help:/images/C/crash_report_assistant_bugtracker_login.png" |
441 | +format="PNG"/> |
442 | </imageobject> |
443 | </mediaobject> |
444 | </example> |
445 | </para> |
446 | <note><title>Use e-mail address as username</title> |
447 | <para> |
448 | -Use the e-mail address that was used to register with KDE's Bugzilla. |
449 | +Use the email address that was used to register with |
450 | +<trademark>KDE</trademark>'s <trademark>Bugzilla</trademark>. |
451 | </para> |
452 | </note> |
453 | </step> |
454 | <step> |
455 | <para> |
456 | -After logging in with username (e-mail address) and password, |
457 | +After logging in with your username (email address) and password, |
458 | <mousebutton>click</mousebutton> the <guibutton>Login</guibutton> button. The |
459 | -assistant will check for duplicates and display the following dialog. |
460 | +assistant will check for duplicates and display the following dialog: |
461 | </para> |
462 | <para> |
463 | <example> |
464 | <title>Bug Report Possible Duplicates List</title> |
465 | <mediaobject> |
466 | <imageobject> |
467 | -<imagedata fileref="help:/images/C/crash_report_assistant_possible_duplicates.png" format="PNG"/> |
468 | +<imagedata |
469 | +fileref="help:/images/C/crash_report_assistant_possible_duplicates.png" |
470 | +format="PNG"/> |
471 | </imageobject> |
472 | </mediaobject> |
473 | </example> |
474 | @@ -283,14 +307,17 @@ |
475 | If there is a possible duplicate report, <mousebutton>click</mousebutton> the |
476 | report in the list and then <mousebutton>click</mousebutton> the <guibutton>Open |
477 | selected report</guibutton> button. Either of the following dialogs will be |
478 | -presented. |
479 | +presented: |
480 | </para> |
481 | <para> |
482 | <example> |
483 | -<title>The report you selected is already marked as a duplicate of bug...</title> |
484 | +<title>The report you selected is already marked as a duplicate of |
485 | +bug...</title> |
486 | <mediaobject> |
487 | <imageobject> |
488 | -<imagedata fileref="help:/images/C/crash_report_assistant_nested_duplicate_detected.png" format="PNG"/> |
489 | +<imagedata |
490 | +fileref="help:/images/C/crash_report_assistant_nested_duplicate_detected.png" |
491 | +format="PNG"/> |
492 | </imageobject> |
493 | </mediaobject> |
494 | </example> |
495 | @@ -300,7 +327,9 @@ |
496 | <title>Showing the duplicate bug report you selected</title> |
497 | <mediaobject> |
498 | <imageobject> |
499 | -<imagedata fileref="help:/images/C/crash_report_assistant_duplicate_report.png" format="PNG"/> |
500 | +<imagedata |
501 | +fileref="help:/images/C/crash_report_assistant_duplicate_report.png" |
502 | +format="PNG"/> |
503 | </imageobject> |
504 | </mediaobject> |
505 | </example> |
506 | @@ -313,23 +342,26 @@ |
507 | bug report and inform the developers that it may be a duplicate. This is |
508 | recommended, except in cases with experienced users where it is clearly not a |
509 | duplicate. <mousebutton>Clicking</mousebutton> the <guibutton>Attach to this |
510 | -report (Advanced)</guibutton> will attach the crash information to the report. |
511 | +report (Advanced)</guibutton> button will attach the crash information to the |
512 | +report. |
513 | </para> |
514 | <para> |
515 | If the bug is not a duplicate, simply <mousebutton>click</mousebutton> |
516 | -the <guibutton>Next</guibutton> in the dialog showing the possible duplicates. |
517 | -A dialog will appear with <guibutton>Let me check more reports</guibutton>. To |
518 | -prevent checking for more reports and continue to file the report, |
519 | -<mousebutton>click</mousebutton> the <guibutton>There |
520 | -are no real duplicates</guibutton> button. A dialog will appear to enter |
521 | -additional information concerning the report. |
522 | +the <guibutton>Next</guibutton> button in the dialog showing the possible |
523 | +duplicates. A dialog will appear with <guibutton>Let me check more |
524 | +reports</guibutton>. To prevent checking for more reports and continue filing |
525 | +the report, <mousebutton>click</mousebutton> the <guibutton>There |
526 | +are no real duplicates</guibutton> button. A dialog will appear asking you to |
527 | +enter additional information concerning the report. |
528 | </para> |
529 | <para> |
530 | <example> |
531 | <title>Details of the Bug Report</title> |
532 | <mediaobject> |
533 | <imageobject> |
534 | -<imagedata fileref="help:/images/C/crash_report_assistant_report_details.png" format="PNG"/> |
535 | +<imagedata |
536 | +fileref="help:/images/C/crash_report_assistant_report_details.png" |
537 | +format="PNG"/> |
538 | </imageobject> |
539 | </mediaobject> |
540 | </example> |
541 | @@ -337,16 +369,18 @@ |
542 | </step> |
543 | <step> |
544 | <para> |
545 | -Once the details of the bug report are complete, |
546 | -<mousebutton>click</mousebutton> the <guibutton>Next</guibutton> button. The |
547 | -following dialog will be presented. |
548 | +Once the details of the bug report are complete, |
549 | +<mousebutton>click</mousebutton> the <guibutton>Next</guibutton> button. The |
550 | +following dialog will be presented: |
551 | </para> |
552 | <para> |
553 | <example> |
554 | <title>Preview Report</title> |
555 | <mediaobject> |
556 | <imageobject> |
557 | -<imagedata fileref="help:/images/C/crash_report_assistant_report_details_preview.png" format="PNG"/> |
558 | +<imagedata |
559 | +fileref="help:/images/C/crash_report_assistant_report_details_preview.png" |
560 | +format="PNG"/> |
561 | </imageobject> |
562 | </mediaobject> |
563 | </example> |
564 | @@ -355,14 +389,16 @@ |
565 | <step> |
566 | <para> |
567 | If the information looks correct, <mousebutton>click</mousebutton> the |
568 | -<guibutton>Next</guibutton> button. The following dialog will be presented. |
569 | +<guibutton>Next</guibutton> button. The following dialog will be presented: |
570 | </para> |
571 | <para> |
572 | <example> |
573 | <title>Send Crash Report</title> |
574 | <mediaobject> |
575 | <imageobject> |
576 | -<imagedata fileref="help:/images/C/crash_report_assistant_report_filed.png" format="PNG"/> |
577 | +<imagedata |
578 | +fileref="help:/images/C/crash_report_assistant_report_filed.png" |
579 | +format="PNG"/> |
580 | </imageobject> |
581 | </mediaobject> |
582 | </example> |
583 | @@ -370,18 +406,19 @@ |
584 | </step> |
585 | </procedure> |
586 | <para> |
587 | -<emphasis role="bold">Congratulations on a successful bug report!</emphasis> |
588 | -Identifying and reporting bugs are essential to improving &kubuntu; and KDE. |
589 | -Some emails may be sent to the registered address to update progress or to |
590 | -allow developers to get additional information about the bug. |
591 | +<emphasis>Congratulations on a successful bug report!</emphasis> Identifying |
592 | +and reporting bugs are essential to improving &kubuntu; and |
593 | +<trademark>KDE</trademark>. Some emails may be sent to the registered address |
594 | +to update progress or to allow developers to get additional information about |
595 | +the bug. |
596 | </para> |
597 | </sect2> |
598 | <sect2 id="filing-crash-lp"> |
599 | <title>Launchpad</title> |
600 | <para> |
601 | -When an application that is not KDE crashes in &kubuntu;, a pop-up notification |
602 | -will appear from <application>Apport</application> that is similar to the |
603 | -following image. |
604 | +When an application that is not <trademark>KDE</trademark> crashes in |
605 | +&kubuntu;, a pop-up notification will appear from |
606 | +<application>Apport</application> that is similar to the following image: |
607 | </para> |
608 | <para> |
609 | <example><title>Apport Crash Pop-pup Notification</title> |
610 | @@ -394,11 +431,11 @@ |
611 | </para> |
612 | <note><title>Crash information may be different</title> |
613 | <para> |
614 | -The following screen shots were created by crashing the application |
615 | -<application>VLC</application> deliberately. Crash dialogs associated with other |
616 | -applications will be different. In an actual bug situation, the application |
617 | -name, <application>VLC</application>, will be replaced by the name of the |
618 | -application that actually crashed. |
619 | +The screen shots below were created by crashing the application |
620 | +<application>VLC</application> deliberately. Crash dialogs associated with |
621 | +other applications will be different. In an actual bug situation, the |
622 | +application name, <application>VLC</application>, will be replaced by the name |
623 | +of the application that actually crashed. |
624 | </para> |
625 | </note> |
626 | <para> |
627 | @@ -409,7 +446,7 @@ |
628 | <para> |
629 | <mousebutton>Click</mousebutton> the <guibutton>Details</guibutton> buttons on |
630 | the <application>System Notification Helper</application>. The following dialog |
631 | -will be presented. |
632 | +will be presented: |
633 | </para> |
634 | <para> |
635 | <example> |
636 | @@ -441,11 +478,11 @@ |
637 | </step> |
638 | <step> |
639 | <para> |
640 | -After all of the information concerning the crash is collected, a dialog will |
641 | -be presented that displays the details of the report, and the report is sent to |
642 | -the developers. <mousebutton>Click</mousebutton> the |
643 | +After all information concerning the crash is collected, a dialog will be |
644 | +presented that displays the details of the report, and the report is sent to |
645 | +the developers. <mousebutton>Click</mousebutton> the |
646 | <guibutton>Details...</guibutton> button to view details of the report. The |
647 | -following dialog will be presented. |
648 | +following dialog will be presented: |
649 | </para> |
650 | <para> |
651 | <example><title>Send problem report to the developers? (Details)</title> |
652 | @@ -460,8 +497,8 @@ |
653 | <step> |
654 | <para> |
655 | <mousebutton>Click</mousebutton> the <guibutton>Send</guibutton> button to send |
656 | -the report to the developers. In this case, it will send the report to |
657 | -Launchpad. The following progress dialog will be presented. |
658 | +the report to the developers. In this case, it will send the report to |
659 | +<trademark>Launchpad</trademark>. The following progress dialog will be presented: |
660 | </para> |
661 | <para> |
662 | <example><title>Uploading problem information</title> |
663 | @@ -476,15 +513,16 @@ |
664 | <step> |
665 | <para> |
666 | After the progress dialog completes, the default web browser will open to |
667 | -Launchpad presenting either the login page or the beginning of the online |
668 | -version of the bug reporting process. After logging in (if necessary) the |
669 | -following page will be presented. |
670 | +<trademark>Launchpad</trademark>, presenting either the log-in page or the |
671 | +beginning of the online version of the bug reporting process. After logging in |
672 | +(if necessary), the following page will be presented: |
673 | </para> |
674 | <para> |
675 | <example><title>Please wait while bug data is processed...</title> |
676 | <mediaobject> |
677 | <imageobject> |
678 | -<imagedata fileref="help:/images/C/apport-browser-processing.png" format="PNG"/> |
679 | +<imagedata fileref="help:/images/C/apport-browser-processing.png" |
680 | +format="PNG"/> |
681 | </imageobject> |
682 | </mediaobject> |
683 | </example> |
684 | @@ -492,8 +530,8 @@ |
685 | </step> |
686 | <step> |
687 | <para> |
688 | -When Launchpad is finished processing the bug data, the following page will be |
689 | -presented. |
690 | +When <trademark>Launchpad</trademark> is finished processing the bug data, the |
691 | +following page will be presented: |
692 | </para> |
693 | <para> |
694 | <example><title>Extra debug information will be added...</title> |
695 | @@ -508,7 +546,7 @@ |
696 | <step> |
697 | <para> |
698 | <mousebutton>Click</mousebutton> the <guibutton>Next</guibutton> button. The |
699 | -following page will be presented. |
700 | +following page will be presented: |
701 | </para> |
702 | <para> |
703 | <example><title>Further information</title> |
704 | @@ -522,10 +560,10 @@ |
705 | </step> |
706 | <step> |
707 | <para> |
708 | -Any extra information can be filled in about the bug report such as what was |
709 | -being done when it crashed or the online file locations that may have caused the |
710 | -crash. The following is a brief description filed with the report in |
711 | -this procedure. |
712 | +Any extra information about the bug report can be filled in to describe, for |
713 | +example, what was being done when the application crashed or the online file |
714 | +locations that may have caused the crash. The following is a brief description |
715 | +filed with the report in this procedure: |
716 | </para> |
717 | <para> |
718 | <example><title>Further information (Completed)</title> |
719 | @@ -540,7 +578,7 @@ |
720 | <step> |
721 | <para> |
722 | <mousebutton>Click</mousebutton> the <guibutton>Submit Bug Report</guibutton> |
723 | -button on the bottom of the page. The following page will be presented. |
724 | +button on the bottom of the page. The following page will be presented: |
725 | </para> |
726 | <para> |
727 | <example><title>Thank you for your bug report</title> |
728 | @@ -554,10 +592,10 @@ |
729 | </step> |
730 | </procedure> |
731 | <para> |
732 | -<emphasis role="bold">Congratulations on making a successful crash |
733 | -report!</emphasis>Identifying and reporting bugs are essential to improving |
734 | -&kubuntu;. Some emails may be sent to the registered address to update progress |
735 | -or to allow developers to get additional information about the bug. |
736 | +<emphasis>Congratulations on making a successful crash report!</emphasis> |
737 | +Identifying and reporting bugs are essential to improving &kubuntu;. Some |
738 | +emails may be sent to the registered address to update progress or to allow |
739 | +developers to get additional information about the bug. |
740 | </para> |
741 | </sect2> |
742 | </sect1> |
743 | @@ -565,32 +603,33 @@ |
744 | <sect1 id="filing-non-crash"> |
745 | <title>Filing a Non-Crash or Regression Report</title> |
746 | <para> |
747 | -If an application has regressed in functionality, a bug report should be |
748 | -filed on that application. A regress occurs when a function worked in a previous |
749 | -release but in the latest release, it is not working. In most cases, this type |
750 | -of report will be filed by those who have more experience and may be testing |
751 | -beta quality software. However there are situations where a user needs to report |
752 | -an issue with an application that isn't working right, but isn't crashing. The |
753 | -following procedures will help. |
754 | +If an application has regressed in functionality, a bug report should be filed |
755 | +on that application. A regression occurs when a function worked in a previous |
756 | +release, but is not working in the latest release. In most cases, this type of |
757 | +report will be filed by those who have previous experience and may be testing |
758 | +beta quality software. There are, however, situations where a user needs to |
759 | +report an issue with an application that isn't working right, but isn't |
760 | +crashing. The following procedures will help: |
761 | </para> |
762 | <sect2 id="filing-non-crash-kde"> |
763 | <title>KDE</title> |
764 | <para> |
765 | -Filing non-crash related bug reports for KDE applications are done with a web |
766 | -browser using <ulink url="https://bugs.kde.org/"/>. |
767 | +Filing non-crash related bug reports for <trademark>KDE</trademark> |
768 | +applications is done with a web browser using |
769 | +<ulink url="https://bugs.kde.org/"/>. |
770 | </para> |
771 | <note><title>Register first</title> |
772 | <para> |
773 | To report a bug, one must register for an account on the bug tracker. |
774 | -KDE's bug tracker is located at <ulink url="https://bugs.kde.org/"/>. |
775 | +<trademark>KDE</trademark>'s bug tracker is located at <ulink |
776 | +url="https://bugs.kde.org/"/>. |
777 | </para> |
778 | </note> |
779 | <procedure><title>Filing a bug report without a crash</title> |
780 | <step> |
781 | <para> |
782 | -In a web browser, go to <ulink url="https://bugs.kde.org/"/> and either |
783 | -create a new account or login. Once logged in, the following page will be |
784 | -presented. |
785 | +In a web browser, go to <ulink url="https://bugs.kde.org/"/> and either create |
786 | +a new account or log in. Once logged in, the following page will be presented: |
787 | </para> |
788 | <para> |
789 | <example><title>Welcome to the KDE Bug Tracking System</title> |
790 | @@ -605,8 +644,8 @@ |
791 | <step> |
792 | <para> |
793 | <mousebutton>Click</mousebutton> the <guilabel>Report New Wish or Bug</guilabel> |
794 | -link in the top-right-hand corner of the page to start the process of filing the |
795 | -bug report. The following page will be presented. |
796 | +link in the top right-hand corner of the page to start the process of filing |
797 | +the bug report. The following page will be presented: |
798 | </para> |
799 | <para> |
800 | <example><title>Welcome to the KDE Bug Report Wizard!</title> |
801 | @@ -620,8 +659,8 @@ |
802 | </step> |
803 | <step> |
804 | <para> |
805 | -<mousebutton>Click</mousebutton> the <guibutton>Continue</guibutton> button. The |
806 | -following page will be presented. |
807 | +<mousebutton>Click</mousebutton> the <guibutton>Continue</guibutton> button. |
808 | +The following page will be presented: |
809 | </para> |
810 | <para> |
811 | <example><title>Software Configuration</title> |
812 | @@ -639,7 +678,7 @@ |
813 | <guilabel>Distribution Method</guilabel> (Should be <guilabel>Ubuntu |
814 | Packages</guilabel>) from the drop-down menus. <mousebutton>Click</mousebutton> |
815 | the <guibutton>Continue</guibutton> button when finished with the selections. |
816 | -The following page will be presented. |
817 | +The following page will be presented: |
818 | </para> |
819 | <para> |
820 | <example><title>Application Selection</title> |
821 | @@ -660,10 +699,10 @@ |
822 | </step> |
823 | <step> |
824 | <para> |
825 | -Under the <guilabel>Find</guilabel> section under the |
826 | -<guilabel>Application</guilabel> list, fill in the <guilabel>Keyword |
827 | +Under the <guilabel>Find</guilabel> section in the |
828 | +<guilabel>Application</guilabel> list, fill in the <guilabel>Keyword |
829 | Search</guilabel> text box with the application being reported. It should look |
830 | -similar to the following image. |
831 | +similar to the following image: |
832 | </para> |
833 | <para> |
834 | <example><title>Application Selection (Search for application)</title> |
835 | @@ -681,8 +720,8 @@ |
836 | </step> |
837 | <step> |
838 | <para> |
839 | -<mousebutton>Click</mousebutton> the <guibutton>Continue</guibutton> button. The |
840 | -following page will be presented. |
841 | +<mousebutton>Click</mousebutton> the <guibutton>Continue</guibutton> button. |
842 | +The following page will be presented: |
843 | </para> |
844 | <para> |
845 | <example><title>General Information</title> |
846 | @@ -700,7 +739,7 @@ |
847 | information similar to the example under the text box. Select |
848 | <guilabel>Linux</guilabel> in the <guilabel>Operating System</guilabel> |
849 | drop-down menu. When completed, <mousebutton>Click</mousebutton> the |
850 | -<guibutton>Continue</guibutton> button. The following page will be presented. |
851 | +<guibutton>Continue</guibutton> button. The following page will be presented: |
852 | </para> |
853 | <para> |
854 | <example><title>Check for Duplicate Bug Reports</title> |
855 | @@ -714,12 +753,12 @@ |
856 | </step> |
857 | <step> |
858 | <para> |
859 | -If a duplicate report is found, click on that report ID to view the report. If |
860 | -it is a duplicate and more information is needed, then simply enter text in the |
861 | -large text box confirming it. If more information is not needed, nothing need |
862 | -be entered. If no duplicate reports are found, <mousebutton>Click</mousebutton> |
863 | -the <guibutton>Continue</guibutton> button. The following page will be |
864 | -presented. |
865 | +If a duplicate report is found, click on that report <acronym>ID</acronym> to |
866 | +view the report. If it is a duplicate and more information is needed, then |
867 | +enter text into the large text box confirming it. If more information is not |
868 | +needed, nothing needs to be entered. If no duplicate reports are found, |
869 | +<mousebutton>Click</mousebutton> the <guibutton>Continue</guibutton> button. |
870 | +The following page will be presented: |
871 | </para> |
872 | <para> |
873 | <example><title>Bug Entry Form</title> |
874 | @@ -734,11 +773,11 @@ |
875 | <step> |
876 | <para> |
877 | The <guilabel>Severity</guilabel> (required) drop-down menu should display the |
878 | -<guilabel>Bug - Bug report (no crashes)</guilabel> option. In the <guilabel>Long |
879 | -Description in English</guilabel> (required) text box, enter all information |
880 | -pertaining to the bug report. When completed, <mousebutton>Click</mousebutton> |
881 | -the <guibutton>Continue</guibutton> button. The following page will be |
882 | -presented. |
883 | +<guilabel>Bug - Bug report (no crashes)</guilabel> option. In the |
884 | +<guilabel>Long Description in English</guilabel> (required) text box, enter all |
885 | +information pertaining to the bug report. When completed, |
886 | +<mousebutton>Click</mousebutton> the <guibutton>Continue</guibutton> button. |
887 | +The following page will be presented: |
888 | </para> |
889 | <para> |
890 | <example><title>Bug Submitted</title> |
891 | @@ -752,27 +791,30 @@ |
892 | </step> |
893 | </procedure> |
894 | <para> |
895 | -<emphasis role="bold">Congratulations on making a successful non-crash related |
896 | -bug report!</emphasis> Identifying and reporting bugs are essential to improving |
897 | -&kubuntu; and KDE. Some emails may be sent to the registered address to update |
898 | -progress or to allow developers to get additional information about the bug. |
899 | +<emphasis>Congratulations on making a successful non-crash-related bug |
900 | +report!</emphasis> Identifying and reporting bugs are essential to improving |
901 | +&kubuntu; and <trademark>KDE</trademark>. Some emails may be sent to the |
902 | +registered address to update progress or to allow developers to get additional |
903 | +information about the bug. |
904 | </para> |
905 | </sect2> |
906 | <sect2 id="filing-non-crash-lp"> |
907 | <title>Launchpad</title> |
908 | <para> |
909 | -Filing non-crash related bug reports in non-KDE applications can be done either |
910 | -by going to <ulink url="https://bugs.launchpad.net/ubuntu/+filebug"/> in a web |
911 | -browser or by using the <application>Apport</application> bug reporting |
912 | -application. The following procedure will demonstrate the use of |
913 | -<application>Apport</application> as this is the recommended way of filing |
914 | -Ubuntu or non-KDE related bug reports. |
915 | +Filing non-crash-related bug reports in non-<trademark>KDE</trademark> |
916 | +applications can be done either by going to <ulink |
917 | +url="https://bugs.launchpad.net/ubuntu/+filebug"/> in a web browser or by using |
918 | +the <application>Apport</application> bug reporting application. The following |
919 | +procedure will demonstrate the use of <application>Apport</application> as this |
920 | +is the recommended way of filing &ubuntu; or |
921 | +non-<trademark>KDE</trademark>-related bug reports: |
922 | </para> |
923 | <procedure><title>Filing a bug report without a crash</title> |
924 | <step> |
925 | <para> |
926 | -Open <application>KRunner</application>, the KDE run command interface, by |
927 | -pressing <keycombo><keycap>Alt</keycap><keycap>F2</keycap></keycombo>. |
928 | +Open <application>KRunner</application>, the <trademark>KDE</trademark> run |
929 | +command interface, by pressing |
930 | +<keycombo><keycap>Alt</keycap><keycap>F2</keycap></keycombo>. |
931 | </para> |
932 | <para> |
933 | <example><title>KRunner</title> |
934 | @@ -786,10 +828,11 @@ |
935 | </step> |
936 | <step> |
937 | <para> |
938 | -In the <application>KRunner</application> dialog, enter <userinput>apport-bug -p |
939 | -PROGRAM_NAME</userinput>. Replace <emphasis>PROGRAM_NAME</emphasis> with the |
940 | -name of the program the bug report is for. Press <keycap>Enter</keycap> when |
941 | -complete. The following dialog will be presented. |
942 | +In the <application>KRunner</application> dialog, enter |
943 | +<userinput>apport-bug -p PROGRAM_NAME</userinput>. Replace |
944 | +<emphasis>PROGRAM_NAME</emphasis> with the name of the program the bug report |
945 | +is for. Press <keycap>Enter</keycap> when complete. The following dialog will |
946 | +be presented: |
947 | </para> |
948 | <para> |
949 | <example><title>Collecting Problem Information</title> |
950 | @@ -818,9 +861,9 @@ |
951 | </step> |
952 | <step> |
953 | <para> |
954 | -<mousebutton>Click</mousebutton> the <guibutton>Details...</guibutton> button to |
955 | -see details of the report to be followed. The following dialog will be |
956 | -presented. |
957 | +<mousebutton>Click</mousebutton> the <guibutton>Details...</guibutton> button |
958 | +to see details of the report to be followed. The following dialog will be |
959 | +presented: |
960 | </para> |
961 | <para> |
962 | <example><title>Report Details</title> |
963 | @@ -835,7 +878,7 @@ |
964 | <step> |
965 | <para> |
966 | <mousebutton>Click</mousebutton> the <guibutton>Send</guibutton> button to send |
967 | -the report to the developers. The following progress dialog will be presented. |
968 | +the report to the developers. The following progress dialog will be presented: |
969 | </para> |
970 | <para> |
971 | <example><title>Uploading Problem Information</title> |
972 | @@ -850,7 +893,7 @@ |
973 | <step> |
974 | <para> |
975 | After the information has been uploaded, the web browser will open and display |
976 | -a page similar to the following. |
977 | +a page similar to the following: |
978 | </para> |
979 | <para> |
980 | <example><title>Please wait while bug data is processed.</title> |
981 | @@ -862,7 +905,7 @@ |
982 | </example> |
983 | </para> |
984 | <para> |
985 | -After the bug data is processed, the following page will be presented. |
986 | +After the bug data is processed, the following page will be presented: |
987 | </para> |
988 | <para> |
989 | <example><title>Report a bug... (Summary)</title> |
990 | @@ -876,9 +919,9 @@ |
991 | </step> |
992 | <step> |
993 | <para> |
994 | -Enter text in the <guilabel>Summary</guilabel> text box that describes the bug |
995 | -with a few words. When finished, <mousebutton>Click</mousebutton> the |
996 | -<guibutton>Next</guibutton> button. The following page will be presented. |
997 | +Enter text that describes the bug into the <guilabel>Summary</guilabel> text |
998 | +box. When finished, <mousebutton>Click</mousebutton> the |
999 | +<guibutton>Next</guibutton> button. The following page will be presented: |
1000 | </para> |
1001 | <para> |
1002 | <example><title>Report a bug... (Further information)</title> |
1003 | @@ -895,7 +938,7 @@ |
1004 | Enter text in the <guilabel>Further information</guilabel> text box describing |
1005 | the bug in detail. When complete, <mousebutton>Click</mousebutton> the |
1006 | <guibutton>Submit Bug Report</guibutton> button. The following page will be |
1007 | -presented. |
1008 | +presented: |
1009 | </para> |
1010 | <para> |
1011 | <example><title>Thank you for your bug report</title> |
1012 | @@ -909,8 +952,8 @@ |
1013 | </step> |
1014 | </procedure> |
1015 | <para> |
1016 | -<emphasis role="bold">Congratulations on making a successful non-crash related |
1017 | -bug report!</emphasis> Identifying and reporting bugs are essential to improving |
1018 | +<emphasis>Congratulations on making a successful non-crash related bug |
1019 | +report!</emphasis> Identifying and reporting bugs are essential to improving |
1020 | &kubuntu;. Some emails may be sent to the registered address to update progress |
1021 | or to allow developers to get additional information about the bug. |
1022 | </para> |
1023 | @@ -920,21 +963,24 @@ |
1024 | <sect1 id="filing-wishlist"> |
1025 | <title>Filing a Feature Request or Wishlist Report</title> |
1026 | <para> |
1027 | -The easiest way to request a new feature in either an application or the |
1028 | -operating system is to file a bug, otherwise known as a wishlist report. |
1029 | +The easiest way to request a new feature, in either an application or the |
1030 | +operating system, is to file a bug — otherwise known as a wishlist |
1031 | +report. |
1032 | </para> |
1033 | <sect2 id="filing-wishlist-kde"> |
1034 | <title>KDE</title> |
1035 | <para> |
1036 | -Filing a feature request report in KDE is exactly the same as filing a <link |
1037 | -linkend="filing-non-crash-kde">non-crash KDE bug report</link>. |
1038 | +Filing a feature request report in <trademark>KDE</trademark> is exactly the |
1039 | +same as filing a <link linkend="filing-non-crash-kde">non-crash |
1040 | +<trademark>KDE</trademark> bug report</link>. |
1041 | </para> |
1042 | </sect2> |
1043 | <sect2 id="filing-wishlist-lp"> |
1044 | <title>Launchpad</title> |
1045 | <para> |
1046 | Filing a wishlist report for &kubuntu; is exactly the same as filing a <link |
1047 | -linkend="filing-non-crash-lp">non-crash Launchpad bug report</link>. |
1048 | +linkend="filing-non-crash-lp">non-crash <trademark>Launchpad</trademark> bug |
1049 | +report</link>. |
1050 | </para> |
1051 | </sect2> |
1052 | </sect1> |
1053 | |
1054 | === modified file 'docs/cli/C/cli.xml' |
1055 | --- docs/cli/C/cli.xml 2011-09-04 21:26:14 +0000 |
1056 | +++ docs/cli/C/cli.xml 2012-03-22 19:19:20 +0000 |
1057 | @@ -13,9 +13,9 @@ |
1058 | &legalnotice; |
1059 | <abstract> |
1060 | <para> |
1061 | -This document provides a brief description of the Linux command line. It is not |
1062 | -a complete guide to the command line, but rather an introduction to complement |
1063 | -&kubuntu;'s graphical tools. |
1064 | +This document provides a brief description of the <trademark>Linux</trademark> |
1065 | +command line. It is not a complete guide, but rather an introduction to |
1066 | +complement &kubuntu;'s graphical tools. |
1067 | </para> |
1068 | </abstract> |
1069 | </articleinfo> |
1070 | @@ -25,37 +25,41 @@ |
1071 | |
1072 | <para> |
1073 | <emphasis> |
1074 | -"Under Linux there are GUIs (graphical user interfaces), where you can point and |
1075 | -click and drag, and hopefully get work done without first reading lots of |
1076 | -documentation. The traditional Unix environment is a CLI (command line |
1077 | -interface), where you type commands to tell the computer what to do. That is |
1078 | -faster and more powerful, but requires finding out what the commands are." -- |
1079 | -from <emphasis role="strong">man intro(1)</emphasis> |
1080 | +"Under <trademark>Linux</trademark> there are <acronym>GUI</acronym>s |
1081 | +(graphical user interfaces), where you can point and click and drag and |
1082 | +hopefully get work done without first reading lots of documentation. The |
1083 | +traditional <trademark>Unix</trademark> environment is a |
1084 | +<acronym>CLI</acronym> (command line interface), where you type commands to |
1085 | +tell the computer what to do. That is faster and more powerful, but requires |
1086 | +finding out what the commands are." -- from <emphasis>man intro(1)</emphasis> |
1087 | </emphasis> |
1088 | </para> |
1089 | <para> |
1090 | -This guide describes some basic GNU/Linux shell commands. It is not intended to |
1091 | -be a complete guide to the command line, just an introduction to complement |
1092 | -&kubuntu;'s graphical tools. |
1093 | +This guide describes some basic <trademark>GNU</trademark>/ |
1094 | +<trademark>Linux</trademark> shell commands. It is not intended to be a |
1095 | +complete guide to the command line, just an introduction to complement |
1096 | +&kubuntu;'s graphical tools. |
1097 | </para> |
1098 | <para> |
1099 | <itemizedlist> |
1100 | <listitem> |
1101 | <para> |
1102 | -All command names, file names or paths to directories will be shown using a <command>monospace font</command>. |
1103 | +All command names, file names, or paths to directories will be shown using a |
1104 | +<command>monospace font</command>. |
1105 | </para> |
1106 | </listitem> |
1107 | <listitem> |
1108 | <para> |
1109 | -The commands should be issued from a command prompt within a |
1110 | +The commands should be issued from a command prompt within a |
1111 | <application>Terminal</application> and will be shown as: |
1112 | <screen>command to type</screen> |
1113 | </para> |
1114 | </listitem> |
1115 | <listitem> |
1116 | <para> |
1117 | -<emphasis role="strong">Command Line Linux is case sensitive.</emphasis> User, |
1118 | -user, and USER are each different and distinct in Linux. |
1119 | +<emphasis>Command Line <trademark>Linux</trademark> is case |
1120 | +sensitive.</emphasis> User, user, and USER are each different and distinct in |
1121 | +<trademark>Linux</trademark>. |
1122 | </para> |
1123 | </listitem> |
1124 | </itemizedlist> |
1125 | @@ -65,12 +69,12 @@ |
1126 | <sect1 id="terminal"> |
1127 | <title>Starting A Terminal</title> |
1128 | <para> |
1129 | -&kubuntu;'s Terminal application is called |
1130 | -<application>Konsole</application>, and is opened by going to &menukonsole;. |
1131 | +&kubuntu;'s Terminal application is called <application>Konsole</application>, |
1132 | +and is opened by going to &menukonsole;. |
1133 | </para> |
1134 | <para> |
1135 | <example> |
1136 | -<title>&kubuntu;'s terminal - Konsole</title> |
1137 | +<title>&kubuntu;'s terminal - Konsole</title> |
1138 | <mediaobject> |
1139 | <imageobject> |
1140 | <imagedata fileref="help:/images/C/C/konsole.png" format="PNG"/> |
1141 | @@ -86,12 +90,10 @@ |
1142 | <sect2 id="pwd"> |
1143 | <title>pwd - print working directory</title> |
1144 | <para> |
1145 | -The <command>pwd</command> command displays the directory where the user is |
1146 | -currently |
1147 | -located. (<acronym>pwd</acronym> stands for <quote>print working |
1148 | -directory</quote>). For example, typing |
1149 | -<screen>pwd</screen> while in the <filename |
1150 | -class="directory">Desktop</filename> will show |
1151 | +The <command>pwd</command> command displays the directory where the user is |
1152 | +currently located. (<acronym>pwd</acronym> stands for <quote>print working |
1153 | +directory</quote>). For example, typing <screen>pwd</screen> while in the |
1154 | +<filename class="directory">Desktop</filename> directory will show |
1155 | <computeroutput>/home/[username]/Desktop</computeroutput>. |
1156 | <note> |
1157 | <para> |
1158 | @@ -105,9 +107,9 @@ |
1159 | <title>cd - change directory</title> |
1160 | <para> |
1161 | The <command>cd</command> command changes directories. (<acronym>cd</acronym> |
1162 | -stands for |
1163 | -<quote>change directory</quote>). When a terminal window is opened, it will be in the user's home directory. Moving around the file system requires the |
1164 | -use of the <command>cd</command>. |
1165 | +stands for <quote>change directory</quote>). When a terminal window is opened, |
1166 | +it will be in the user's home directory. Moving around the file system requires |
1167 | +the use of the <command>cd</command> command. |
1168 | </para> |
1169 | <itemizedlist> |
1170 | <listitem> |
1171 | @@ -125,8 +127,8 @@ |
1172 | </para> |
1173 | <note> |
1174 | <para> |
1175 | -The <command>~</command> character represents the current user's home directory. |
1176 | -As shown above, <command>cd ~</command> is equivalent to <command>cd |
1177 | +The <command>~</command> character represents the current user's home |
1178 | +directory. As shown above, <command>cd ~</command> is equivalent to <command>cd |
1179 | /home/username/</command>. However, when running a command as root (using |
1180 | <command>sudo</command>, for example), <command>~</command> points to <filename |
1181 | class="directory">/root</filename>. When running a <command>cd</command> command |
1182 | @@ -161,8 +163,8 @@ |
1183 | of <filename class="directory">/var/</filename>. For another example, typing: |
1184 | <screen>cd ~/Desktop</screen> |
1185 | moves to the <filename |
1186 | -class="directory">Desktop</filename> subdirectory inside the current user's home |
1187 | -directory. |
1188 | +class="directory">Desktop</filename> subdirectory inside the current user's |
1189 | +home directory. |
1190 | </para> |
1191 | </listitem> |
1192 | </itemizedlist> |
1193 | @@ -171,11 +173,9 @@ |
1194 | <title>ls - list files</title> |
1195 | <para> |
1196 | The <command>ls</command> command outputs a list of the files in the current |
1197 | -directory. (<acronym>ls</acronym> is short for <quote>list</quote>). For example, |
1198 | -typing |
1199 | -<screen>ls ~</screen> |
1200 | -will display the files that are in the current |
1201 | -user's home directory. |
1202 | +directory. (<acronym>ls</acronym> is short for <quote>list</quote>). For |
1203 | +example, typing <screen>ls ~</screen> will display the files that are in the |
1204 | +current user's home directory. |
1205 | </para> |
1206 | <para> |
1207 | Used with the <command>-l</command> option, <command>ls</command> outputs other |
1208 | @@ -185,34 +185,34 @@ |
1209 | <para> |
1210 | Used with the <command>-al</command> options, <command>ls</command> outputs |
1211 | the information associated with the <command>-l</command> option in addition to |
1212 | -showing hidden files (<command>a</command> |
1213 | -option). |
1214 | +showing hidden files (<command>a</command> option). |
1215 | </para> |
1216 | </sect2> |
1217 | <sect2 id="touch"> |
1218 | <title>touch - create empty file</title> |
1219 | <para> |
1220 | -The <command>touch</command> command is used either to change a file's access |
1221 | -and modification timestamps or to create a new empty file. For example, |
1222 | -<screen>touch foo</screen> |
1223 | -will create a new empty file named <filename>foo</filename>. If |
1224 | -<filename>foo</filename> is already a file, then using <command>touch</command> |
1225 | -will update the timestamps on the file which will show |
1226 | -the last time a file was <emphasis>touched</emphasis>. |
1227 | +The <command>touch</command> command is used to change a file's access and |
1228 | +modification timestamps or to create a new empty file. For example, |
1229 | +<screen>touch foo</screen> will create a new empty file named |
1230 | +<filename>foo</filename>. If <filename>foo</filename> is already a file, then |
1231 | +using <command>touch</command> will update the timestamps on the file, which |
1232 | +show the last time a file was <emphasis>touched</emphasis>. |
1233 | </para> |
1234 | </sect2> |
1235 | <sect2 id="mkdir"> |
1236 | <title>mkdir - make directory</title> |
1237 | <para> |
1238 | -The <command>mkdir</command> command is used to create a new directory. (<acronym>mkdir</acronym> stands for <quote>make directory</quote>). To create a |
1239 | -new directory named <filename class="directory">foobar</filename>, type: |
1240 | +The <command>mkdir</command> command is used to create a new directory. |
1241 | +(<acronym>mkdir</acronym> stands for <quote>make directory</quote>). To create |
1242 | +a new directory named <filename class="directory">foobar</filename>, type: |
1243 | <screen>mkdir foobar</screen> |
1244 | </para> |
1245 | </sect2> |
1246 | <sect2 id="cp"> |
1247 | <title>cp - copy files or directories</title> |
1248 | <para> |
1249 | -The <command>cp</command> command makes a copy of a file or directory. (<acronym>cp</acronym> is short for <quote>copy</quote>). To make an exact copy |
1250 | +The <command>cp</command> command makes a copy of a file or directory. |
1251 | +(<acronym>cp</acronym> is short for <quote>copy</quote>). To make an exact copy |
1252 | of <filename>foo</filename> and name it <filename>bar</filename>, type: |
1253 | <screen>cp foo bar</screen> |
1254 | To make an exact copy of the <filename class="directory">foo_dir</filename> |
1255 | @@ -224,34 +224,32 @@ |
1256 | <title>mv - move files or directories</title> |
1257 | <para> |
1258 | The <command>mv</command> command moves a file or directory to a different |
1259 | -location or will rename a file or directory. (<acronym>mv</acronym> is short for |
1260 | +location or renames a file or directory. (<acronym>mv</acronym> is short for |
1261 | <quote>move</quote>). To rename the file <filename>foo</filename> to |
1262 | -<filename>bar</filename>, type: |
1263 | -<screen>mv foo bar</screen> |
1264 | -To move the file <filename>foo</filename> into the current user's <filename |
1265 | -class="directory">Desktop</filename> directory, type: |
1266 | -<screen>mv foo ~/Desktop</screen> |
1267 | -This will not rename <filename>foo</filename> to <filename>Desktop</filename> |
1268 | -because <filename>foo</filename> is a file and <filename |
1269 | -class="directory">Desktop</filename> is a directory. |
1270 | +<filename>bar</filename>, type: <screen>mv foo bar</screen> To move the file |
1271 | +<filename>foo</filename> into the current user's <filename |
1272 | +class="directory">Desktop</filename> directory, type: <screen>mv foo |
1273 | +~/Desktop</screen> This will not rename <filename>foo</filename> to |
1274 | +<filename>Desktop</filename>, because <filename>foo</filename> is a file and |
1275 | +<filename class="directory">Desktop</filename> is a directory. |
1276 | </para> |
1277 | </sect2> |
1278 | <sect2 id="rm"> |
1279 | <title>rm - remove files or directories</title> |
1280 | <para> |
1281 | -The <command>rm</command> command is used to delete files and directories. (<acronym>rm</acronym> is short for <quote>remove</quote>). To delete the file |
1282 | -<filename>foo</filename> for the current directory, type: |
1283 | +The <command>rm</command> command is used to delete files and directories. |
1284 | +(<acronym>rm</acronym> is short for <quote>remove</quote>). To delete the file |
1285 | +<filename>foo</filename> from the current directory, type: |
1286 | <screen>rm foo</screen> |
1287 | </para> |
1288 | <para> |
1289 | By default, <command>rm</command> will not remove directories. To remove a |
1290 | -directory, you must use the <command>-r</command> option (also can be entered |
1291 | -as either <command>-R</command> or <command>--recursive</command>). For example, |
1292 | -<screen>rm -r foobar</screen> or |
1293 | -<screen>rm -R foobar</screen> or |
1294 | -<screen>rm --recursive foobar</screen> |
1295 | -will remove the directory <filename class="directory">foobar</filename>, |
1296 | -<emphasis role="strong"> and all of its contents!</emphasis> |
1297 | +directory, you must use the <command>-r</command> option (which can also be |
1298 | +entered as <command>-R</command> or <command>--recursive</command>). For |
1299 | +example, <screen>rm -r foobar</screen> or <screen>rm -R foobar</screen> or |
1300 | +<screen>rm --recursive foobar</screen> will remove the directory |
1301 | +<filename class="directory">foobar</filename> <emphasis> and all of its |
1302 | +contents!</emphasis> |
1303 | </para> |
1304 | </sect2> |
1305 | |
1306 | @@ -265,8 +263,7 @@ |
1307 | <para> |
1308 | The <command>df</command> command displays filesystem disk space usage for all |
1309 | partitions. (<acronym>df</acronym> stands for <quote>disk free</quote>). |
1310 | -<screen>df -h</screen> |
1311 | -will give information using megabytes |
1312 | +<screen>df -h</screen> will give information using megabytes |
1313 | (<abbrev>M</abbrev>) and gigabytes (<abbrev>G</abbrev>) instead of blocks |
1314 | (<command>-h</command> means <quote>human readable</quote>). |
1315 | </para> |
1316 | @@ -275,26 +272,24 @@ |
1317 | <title>free - display amount of free and used memory</title> |
1318 | <para> |
1319 | The <command>free</command> command displays the amount of free and used memory |
1320 | -in the system. |
1321 | -<screen>free -m</screen> |
1322 | -will give the information using megabytes, which is probably the most useful for |
1323 | -current computers. |
1324 | +in the system. <screen>free -m</screen> will give the information using |
1325 | +megabytes, which is probably the most useful for current computers. |
1326 | </para> |
1327 | </sect2> |
1328 | <sect2 id="top"> |
1329 | <title>top - display top consuming processes</title> |
1330 | <para> |
1331 | -The <command>top</command> command displays information on the Linux system - |
1332 | -processes that are running, system resources including <acronym>CPU</acronym>, |
1333 | -<acronym>RAM</acronym> & swap usage, and the total number of tasks being |
1334 | -run. To |
1335 | -exit <command>top</command>, press <keycap>q</keycap>. |
1336 | +The <command>top</command> command displays information on the |
1337 | +<trademark>Linux</trademark> system - processes that are running, system |
1338 | +resources including <acronym>CPU</acronym>, <acronym>RAM</acronym> & swap |
1339 | +usage, and the total number of tasks being run. To exit <command>top</command>, |
1340 | +press <keycap>q</keycap>. |
1341 | </para> |
1342 | </sect2> |
1343 | <sect2 id="uname"> |
1344 | <title>uname - print details about the current machine</title> |
1345 | <para> |
1346 | -The <command>uname</command> command with the <command>-a</command> options |
1347 | +The <command>uname</command> command with the <command>-a</command> option |
1348 | displays all system information, including machine name, kernel name & |
1349 | version, and other details. This command is useful for checking which kernel is |
1350 | in use. (<abbrev>uname</abbrev> is short for <quote>unix name</quote>). |
1351 | @@ -304,8 +299,8 @@ |
1352 | <title>lsb_release - print details about current Linux release</title> |
1353 | <para> |
1354 | The <command>lsb_release</command> with the <command>-a</command> option prints |
1355 | -version information for the Linux release in use. For example, typing: |
1356 | -<screen>lsb_release -a</screen> will display: |
1357 | +version information for the <trademark>Linux</trademark> release in use. For |
1358 | +example, typing: <screen>lsb_release -a</screen> will display: |
1359 | <screen>No LSB modules are available. |
1360 | Distributor ID: Ubuntu |
1361 | Description: Ubuntu &distro-rev; |
1362 | @@ -323,49 +318,41 @@ |
1363 | The following commands must be prefaced with the |
1364 | <command>sudo</command> command. Please see <ulink |
1365 | url="https://help.ubuntu.com/community/RootSudo">RootSudo</ulink> for |
1366 | -information on using <command>sudo</command>. (<abbrev>sudo</abbrev> is short for |
1367 | -<quote>superuser do</quote>). |
1368 | +information on using <command>sudo</command>. (<abbrev>sudo</abbrev> is short |
1369 | +for <quote>superuser do</quote>). |
1370 | </para> |
1371 | <sect2 id="add-group"> |
1372 | <title>Adding a New Group</title> |
1373 | <para> |
1374 | The <command>addgroup</command> command is used to create a new group in the |
1375 | -system. To create a new group, type: |
1376 | -<screen>sudo addgroup foobar</screen> |
1377 | -The above command will create a new group called <emphasis |
1378 | -role="strong">foobar</emphasis>. |
1379 | +system. To create a new group, type: <screen>sudo addgroup foobar</screen> The |
1380 | +above command will create a new group called <emphasis>foobar</emphasis>. |
1381 | </para> |
1382 | </sect2> |
1383 | <sect2 id="add-user"> |
1384 | <title>Adding a New User</title> |
1385 | <para> |
1386 | The <command>adduser</command> command is used to create a new user on the |
1387 | -system. To create a new user, type: |
1388 | -<screen>adduser foobar</screen> |
1389 | -which will create a new user called <emphasis role="strong">foobar</emphasis>. |
1390 | +system. To create a new user, type: <screen>adduser foobar</screen> which will |
1391 | +create a new user called <emphasis>foobar</emphasis>. |
1392 | </para> |
1393 | </sect2> |
1394 | <sect2 id="passwd"> |
1395 | <title>Add or Change a User Password</title> |
1396 | <para> |
1397 | The <command>passwd</command> command is used to assign a new password to a |
1398 | -new user or to change the current password for an existing user. To add a |
1399 | -password or change the password for the user <emphasis |
1400 | -role="strong">foobar</emphasis>, |
1401 | -type: |
1402 | -<screen>passwd foobar</screen> |
1403 | -For new users, this will generate a prompt to enter the new password. For |
1404 | -an |
1405 | -existing user, there will be a prompt for the existing password before the |
1406 | -prompt for a new password. |
1407 | +new user or change the current password for an existing user. To add a password |
1408 | +or change the password for the user <emphasis>foobar</emphasis>, type: |
1409 | +<screen>passwd foobar</screen> For new users, this will generate a prompt to |
1410 | +enter the new password. For an existing user, there will be a prompt for the |
1411 | +existing password before the prompt for a new password. |
1412 | </para> |
1413 | </sect2> |
1414 | <sect2 id="assign-user-group"> |
1415 | <title>Assign User to Group</title> |
1416 | <para> |
1417 | -To assign the user <emphasis role="strong">foobar</emphasis> to the group |
1418 | -<emphasis role="strong">barfoo</emphasis>, type: |
1419 | -<screen>adduser foobar barfoo</screen> |
1420 | +To assign the user <emphasis>foobar</emphasis> to the group |
1421 | +<emphasis>barfoo</emphasis>, type: <screen>adduser foobar barfoo</screen> |
1422 | </para> |
1423 | </sect2> |
1424 | </sect1> |
1425 | @@ -374,20 +361,20 @@ |
1426 | <sect1 id="options"> |
1427 | <title>Options</title> |
1428 | <para> |
1429 | -The default behavior for a command may usually be modified by adding <command>--option</command> to the command. For example, the <link |
1430 | -linkend="ls"><command>ls</command></link> command has an |
1431 | -<command>-s</command> option. The <command>ls -s</command> will include file |
1432 | -sizes in the listing. There is also a <command>-h</command> option to display |
1433 | -file sizes in a <quote>human readable</quote> format. |
1434 | +The default behavior for a command may usually be modified by adding |
1435 | +<command>--option</command> to the command. For example, the <link |
1436 | +linkend="ls"><command>ls</command></link> command has an <command>-s</command> |
1437 | +option. The <command>ls -s</command> will include file sizes in the listing. |
1438 | +There is also a <command>-h</command> option to display file sizes in a |
1439 | +<quote>human readable</quote> format. |
1440 | </para> |
1441 | <para> |
1442 | Options can be grouped in clusters, so |
1443 | <screen>ls -sh</screen> |
1444 | is the same command as |
1445 | <screen> ls -s -h</screen> |
1446 | -Most options have a long version, prefixed with two dashes instead of one, so |
1447 | -<screen>ls --size --human-readable</screen> |
1448 | -is also the same command as |
1449 | +Most options have a long version prefixed with two dashes instead of one, so |
1450 | +<screen>ls --size --human-readable</screen> is the same command as |
1451 | <screen>ls -sh</screen> |
1452 | </para> |
1453 | </sect1> |
1454 | @@ -396,14 +383,13 @@ |
1455 | <sect1 id="man-help"> |
1456 | <title><quote>Man</quote> and Getting Help</title> |
1457 | <para> |
1458 | -<emphasis role="strong"><emphasis>command</emphasis> --help</emphasis> and |
1459 | -<command>man</command> <emphasis |
1460 | -role="strong"><emphasis>command</emphasis></emphasis> are the two most important |
1461 | +<emphasis><emphasis>command</emphasis> --help</emphasis> and |
1462 | +<command>man</command> <emphasis>command</emphasis> are the two most important |
1463 | tools at the command line. |
1464 | </para> |
1465 | <para> |
1466 | Virtually all commands understand the <command>-h</command> (or |
1467 | -<command>--help</command>) option which will produce a short usage description |
1468 | +<command>--help</command>) option, which will produce a short usage description |
1469 | of the command and its options, then exit back to the command prompt. Type: |
1470 | <screen>man -h</screen> |
1471 | or |
1472 | @@ -411,33 +397,29 @@ |
1473 | to see this in action. |
1474 | </para> |
1475 | <para> |
1476 | -Every command and nearly every application in Linux has a |
1477 | -<abbrev>man</abbrev> (manual) file. It is as simple as typing <command>man |
1478 | +Every command and nearly every application in <trademark>Linux</trademark> has |
1479 | +a <abbrev>man</abbrev> (manual) file. It is as simple as typing <command>man |
1480 | command</command> to bring up a longer manual entry for the specified command. |
1481 | -For example: |
1482 | -<screen>man mv</screen> |
1483 | -brings up the <command>mv</command> manual. |
1484 | +For example: <screen>man mv</screen> brings up the <command>mv</command> |
1485 | +manual. |
1486 | </para> |
1487 | <para> |
1488 | Move up and down the man file with the arrow keys, and quit back to the command |
1489 | prompt with <keycap>q</keycap>. |
1490 | </para> |
1491 | <para> |
1492 | -<screen>man man</screen> |
1493 | -brings up the manual entry for the <command>man</command> command, which is a |
1494 | -good place to start. |
1495 | +<screen>man man</screen> brings up the manual entry for the |
1496 | +<command>man</command> command, which is a good place to start. |
1497 | </para> |
1498 | <para> |
1499 | -<screen>man intro</screen> |
1500 | -is especially useful. It displays the <quote>introduction to user |
1501 | -commands</quote> which is a well-written, brief introduction to the Linux |
1502 | -command line. |
1503 | +<screen>man intro</screen> is especially useful. It displays the |
1504 | +<quote>introduction to user commands</quote> which is a well-written, brief |
1505 | +introduction to the <trademark>Linux</trademark> command line. |
1506 | </para> |
1507 | <para> |
1508 | There are also <command>info</command> pages, which generally go into more |
1509 | -detail than <command>man</command> pages. Try: |
1510 | -<screen>info info</screen> |
1511 | -for the introduction to info pages. |
1512 | +detail than <command>man</command> pages. Try: <screen>info info</screen> for |
1513 | +the introduction to info pages. |
1514 | </para> |
1515 | <sect2 id="searching-for-man-files"> |
1516 | <title>Searching for man files</title> |
1517 | @@ -473,14 +455,14 @@ |
1518 | There are often situations that require text to be pasted into the terminal. |
1519 | </para> |
1520 | <para> |
1521 | -Text copied from a web page using |
1522 | +Text copied from a web page using |
1523 | <keycombo><keycap>Ctrl</keycap><keycap>C</keycap></keycombo> won't paste with |
1524 | <keycombo><keycap>Ctrl</keycap><keycap>V</keycap></keycombo> as it does in |
1525 | -other applications because the |
1526 | -terminal uses a different combination for paste, |
1527 | -<keycombo><keycap>Shift</keycap><keycap>Insert</keycap></keycombo>. Pasting can |
1528 | -also be done using the mouse by <mousebutton>right-clicking</mousebutton> in |
1529 | -the terminal and selecting <guimenuitem>Paste</guimenuitem> from the menu. |
1530 | +other applications, because the terminal uses the |
1531 | +<keycombo><keycap>Shift</keycap><keycap>Insert</keycap></keycombo> |
1532 | +combination. Pasting can also be done using the mouse by |
1533 | +<mousebutton>right-clicking</mousebutton> in the terminal and selecting |
1534 | +<guimenuitem>Paste</guimenuitem> from the menu. |
1535 | </para> |
1536 | <para> |
1537 | Text can also be copied by selecting (highlighting) the text to be copied. |
1538 | @@ -490,8 +472,9 @@ |
1539 | </para> |
1540 | <note> |
1541 | <para> |
1542 | -These actions may work differently in other terminal emulators than <application>Konsole</application>. |
1543 | -Consult your terminal emulator's documentation for details. |
1544 | +These actions may work differently in other terminal emulators than |
1545 | +<application>Konsole</application>. Consult your terminal emulator's |
1546 | +documentation for details. |
1547 | </para> |
1548 | </note> |
1549 | </sect1> |
1550 | @@ -507,7 +490,7 @@ |
1551 | </term> |
1552 | <listitem> |
1553 | <para> |
1554 | -Scrolls backwards through the commands entered previously |
1555 | +Scrolls backwards through the commands entered previously. |
1556 | </para> |
1557 | </listitem> |
1558 | </varlistentry> |
1559 | @@ -518,7 +501,7 @@ |
1560 | </term> |
1561 | <listitem> |
1562 | <para> |
1563 | -Scrolls forward through previous commands |
1564 | +Scrolls forward through previous commands. |
1565 | </para> |
1566 | </listitem> |
1567 | </varlistentry> |
1568 | @@ -528,7 +511,7 @@ |
1569 | </term> |
1570 | <listitem> |
1571 | <para> |
1572 | -Executes the command selected |
1573 | +Executes the selected command. |
1574 | </para> |
1575 | </listitem> |
1576 | </varlistentry> |
1577 | @@ -539,7 +522,7 @@ |
1578 | <listitem> |
1579 | <para> |
1580 | Tab is a useful feature. It autocompletes any commands or filenames if there is |
1581 | -one option, otherwise it displays a list of options that fit the information |
1582 | +one option. Otherwise it displays a list of options that fit the information |
1583 | entered. Using tab in this way reduces typing errors. |
1584 | </para> |
1585 | </listitem> |
1586 | @@ -567,7 +550,7 @@ |
1587 | </term> |
1588 | <listitem> |
1589 | <para> |
1590 | -Moves the cursor to the <emphasis>start</emphasis> of the line |
1591 | +Moves the cursor to the <emphasis>start</emphasis> of the line. |
1592 | </para> |
1593 | </listitem> |
1594 | </varlistentry> |
1595 | @@ -578,7 +561,7 @@ |
1596 | </term> |
1597 | <listitem> |
1598 | <para> |
1599 | -Moves the cursor to the <emphasis>end</emphasis> of the line |
1600 | +Moves the cursor to the <emphasis>end</emphasis> of the line. |
1601 | </para> |
1602 | </listitem> |
1603 | </varlistentry> |
1604 | @@ -588,7 +571,7 @@ |
1605 | </term> |
1606 | <listitem> |
1607 | <para> |
1608 | -Deletes from the current cursor position to the end of the line |
1609 | +Deletes from the current cursor position to the end of the line. |
1610 | </para> |
1611 | </listitem> |
1612 | </varlistentry> |
1613 | @@ -598,7 +581,7 @@ |
1614 | </term> |
1615 | <listitem> |
1616 | <para> |
1617 | -Deletes the entire current line |
1618 | +Deletes the entire current line. |
1619 | </para> |
1620 | </listitem> |
1621 | </varlistentry> |
1622 | @@ -608,7 +591,7 @@ |
1623 | </term> |
1624 | <listitem> |
1625 | <para> |
1626 | -Deletes the word before the cursor |
1627 | +Deletes the word before the cursor. |
1628 | </para> |
1629 | </listitem> |
1630 | </varlistentry> |
1631 | @@ -624,8 +607,8 @@ |
1632 | <itemizedlist> |
1633 | <listitem> |
1634 | <para> |
1635 | -<ulink url="https://help.ubuntu.com/community/AptGetHowto">AptGetHowto</ulink> - |
1636 | -using <command>apt-get</command> to install packages from the command line. |
1637 | +<ulink url="https://help.ubuntu.com/community/AptGetHowto">AptGetHowto</ulink> |
1638 | +- using <command>apt-get</command> to install packages from the command line. |
1639 | </para> |
1640 | </listitem> |
1641 | <listitem> |
1642 | @@ -653,25 +636,26 @@ |
1643 | <para> |
1644 | <ulink url="https://help.ubuntu.com/community/CommandlineHowto">Commandline |
1645 | Howto</ulink> - longer and more complete than this basic guide; still not |
1646 | -finished however. |
1647 | +finished, however. |
1648 | </para> |
1649 | </listitem> |
1650 | <listitem> |
1651 | <para> |
1652 | <ulink url="https://help.ubuntu.com/community/HowToReadline">Howto |
1653 | -Readline</ulink> - information on more advanced customization for the |
1654 | -command line. |
1655 | +Readline</ulink> - information on more advanced customization for the command |
1656 | +line. |
1657 | </para> |
1658 | </listitem> |
1659 | </itemizedlist> |
1660 | <para> |
1661 | -For more detailed tutorials on the Linux command line, please see: |
1662 | +For more detailed tutorials on the <trademark>Linux</trademark> command line, |
1663 | +please see: |
1664 | </para> |
1665 | <itemizedlist> |
1666 | <listitem> |
1667 | <para> |
1668 | -<ulink url="http://ss64.com/bash/"/> - an A-Z index of the Bash command line for |
1669 | -Linux. |
1670 | +<ulink url="http://ss64.com/bash/"/> - an A-Z index of the |
1671 | +<trademark>Bash</trademark> command line for <trademark>Linux</trademark>. |
1672 | </para> |
1673 | </listitem> |
1674 | <listitem> |
1675 | @@ -682,19 +666,20 @@ |
1676 | </listitem> |
1677 | <listitem> |
1678 | <para> |
1679 | -<ulink url="http://linuxsurvival.com/index.php" /> - Java-based tutorials. |
1680 | +<ulink url="http://linuxsurvival.com/index.php" /> - |
1681 | +<trademark>Java</trademark>-based tutorials. |
1682 | </para> |
1683 | </listitem> |
1684 | <listitem> |
1685 | <para> |
1686 | <ulink url="http://rute.2038bug.com/index.html.gz"/> - a massive online book |
1687 | -about system administration, almost all from the command line. |
1688 | +about system administration — almost all from the command line. |
1689 | </para> |
1690 | </listitem> |
1691 | <listitem> |
1692 | <para> |
1693 | -<ulink url="http://www.commandlinefu.com/"/> - a place to record command-line |
1694 | -favorites and view other's gems as well. |
1695 | +<ulink url="http://www.commandlinefu.com/"/> - a place to record command line |
1696 | +favorites and view others' gems as well. |
1697 | </para> |
1698 | </listitem> |
1699 | </itemizedlist> |
1700 | |
1701 | === modified file 'docs/media/C/media.xml' |
1702 | --- docs/media/C/media.xml 2010-03-27 04:09:39 +0000 |
1703 | +++ docs/media/C/media.xml 2012-03-22 19:19:20 +0000 |
1704 | @@ -14,7 +14,7 @@ |
1705 | <abstract> |
1706 | <para> |
1707 | This document provides information concerning the types of media that can be |
1708 | -used with &kubuntu; as well as how to write to the media. |
1709 | +used with &kubuntu;, as well as how to write to the media. |
1710 | </para> |
1711 | </abstract> |
1712 | </articleinfo> |
1713 | @@ -23,20 +23,23 @@ |
1714 | <title>Introduction</title> |
1715 | <para> |
1716 | &kubuntu; supports many types of media with a standard installation, including |
1717 | -USB hard drives, USB flash drives, internal and external CDROMs, CDs, DVDs, and |
1718 | -more. |
1719 | +<acronym>USB</acronym> hard drives, <acronym>USB</acronym> flash drives, |
1720 | +internal and external <acronym>CDROM</acronym>s, <acronym>CD</acronym>s, |
1721 | +<acronym>DVD</acronym>s, and more. |
1722 | </para> |
1723 | <para> |
1724 | -Most of the time, when attaching media such as a CD, DVD, external hard |
1725 | -drive, USB flash drive, or compact flash drives, &kubuntu; automatically |
1726 | -recognizes the media, displays a notification that it has recognized the media, |
1727 | -and allows for an action to be selected depending on the type of media it is. |
1728 | -For instance, inserting a CD or DVD would allow for it to be mounted, opened |
1729 | -with <application>K3b</application> for burning if it is blank, opened with |
1730 | -<application>Amarok</application> if it is an audio CD, or opened with |
1731 | -<application>Dragon Player</application> if it is a DVD. To |
1732 | -see the actions available, <mousebutton>click</mousebutton> the media icon to |
1733 | -the left of the media that has been recognized. |
1734 | +Most of the time, when attaching media such as a <acronym>CD</acronym>, |
1735 | +<acronym>DVD</acronym>, external hard drive, <acronym>USB</acronym> flash |
1736 | +drive, or compact flash drive, &kubuntu; automatically recognizes the media, |
1737 | +displays a notification that it has recognized the media, and allows for an |
1738 | +action to be selected depending on the type of media it is. For instance, |
1739 | +inserting a <acronym>CD</acronym> or <acronym>DVD</acronym> would allow for it |
1740 | +to be mounted, opened with <application>K3b</application> for burning if it is |
1741 | +blank, opened with <application>Amarok</application> if it is an audio |
1742 | +<acronym>CD</acronym>, or opened with <application>Dragon Player</application> |
1743 | +if it is a <acronym>DVD</acronym>. To see the actions available, |
1744 | +<mousebutton>click</mousebutton> the media icon to the left of the media that |
1745 | +has been recognized. |
1746 | </para> |
1747 | <para> |
1748 | <example><title>Media recognized with options</title> |
1749 | @@ -50,25 +53,28 @@ |
1750 | </sect1> |
1751 | |
1752 | <sect1 id="iso"> |
1753 | -<title>ISO Images</title> |
1754 | +<title><acronym>ISO</acronym> Images</title> |
1755 | <para> |
1756 | An <acronym>ISO</acronym> image is an archive file that is formatted to be used |
1757 | -with CDs or DVDs. &kubuntu; is easily acquired as an <acronym>ISO</acronym> file |
1758 | -and then burned to either a CD, DVD, or written to a USB flash drive in a |
1759 | -bootable format. Review the <link linkend="write-cd-dvd">Write to CDs or |
1760 | -DVDs</link> section or the section on creating <link linkend="usb">Bootable ISO |
1761 | -Images From USB Media</link> for further information. |
1762 | +with <acronym>CD</acronym>s or <acronym>DVD</acronym>s. &kubuntu; is easily |
1763 | +acquired as an <acronym>ISO</acronym> file and then burned to either a |
1764 | +<acronym>CD</acronym>, <acronym>DVD</acronym>, or written to a |
1765 | +<acronym>USB</acronym> flash drive in a bootable format. Review the <link |
1766 | +linkend="write-cd-dvd">Write to <acronym>CD</acronym>s or |
1767 | +<acronym>DVD</acronym>s</link> section or the section on creating <link |
1768 | +linkend="usb">Bootable <acronym>ISO</acronym> Images From <acronym>USB</acronym> |
1769 | +Media</link> for further information. |
1770 | </para> |
1771 | </sect1> |
1772 | |
1773 | <sect1 id="write-cd-dvd"> |
1774 | -<title>Write to CDs or DVDs</title> |
1775 | +<title>Write to <acronym>CD</acronym>s or <acronym>DVD</acronym>s</title> |
1776 | <para> |
1777 | &kubuntu; ships with <application>K3b</application>, a <acronym>CD</acronym> and |
1778 | <acronym>DVD</acronym> creator. With <application>K3b</application>, it is |
1779 | possible to create a data or audio project, copy a <acronym>CD</acronym> or |
1780 | <acronym>DVD</acronym>, format or erase a rewritable disk, as well as rip audio |
1781 | -and video <acronym>CD</acronym>' and <acronym>DVD</acronym>'s. |
1782 | +and video <acronym>CD</acronym>s and <acronym>DVD</acronym>s. |
1783 | </para> |
1784 | <variablelist><title>Copy, create, and burn</title> |
1785 | <varlistentry><term>New data project</term> |
1786 | @@ -85,11 +91,11 @@ |
1787 | <varlistentry><term>New audio CD project</term> |
1788 | <listitem> |
1789 | <para> |
1790 | -<mousebutton>Click</mousebutton> the <guibutton>New Audio CD Project</guibutton> |
1791 | -button to get started. This action allows audio file drag-and-drop onto a |
1792 | -<acronym>CD</acronym> that can be played in a home stereo or automobile. |
1793 | -When all files have been copied over, press the <guibutton>Burn</guibutton> |
1794 | -button to write the audio to the disk. |
1795 | +<mousebutton>Click</mousebutton> the <guibutton>New Audio CD |
1796 | +Project</guibutton> button to get started. This action allows audio file |
1797 | +drag-and-drop onto a <acronym>CD</acronym> that can be played in a home stereo |
1798 | +or automobile. When all files have been copied over, press the |
1799 | +<guibutton>Burn</guibutton> button to write the audio to the disk. |
1800 | </para> |
1801 | </listitem> |
1802 | </varlistentry> |
1803 | @@ -97,7 +103,7 @@ |
1804 | <listitem> |
1805 | <para> |
1806 | <mousebutton>Click</mousebutton> the <guibutton>Copy Medium...</guibutton> |
1807 | -button to to copy a <acronym>CD</acronym> to a <acronym>CD</acronym> or copy a |
1808 | +button to copy a <acronym>CD</acronym> to a <acronym>CD</acronym> or copy a |
1809 | <acronym>DVD</acronym> to a <acronym>DVD</acronym>. To start the copying |
1810 | process, simply <mousebutton>click</mousebutton> the |
1811 | <guibutton>Start</guibutton> button. |
1812 | @@ -129,8 +135,9 @@ |
1813 | <para> |
1814 | Go to <menuchoice><guimenu>Tools</guimenu><guimenuitem>Rip Audio |
1815 | CD...</guimenuitem></menuchoice> to rip an audio <acronym>CD</acronym> to files |
1816 | -in Ogg, MP3, or other format that you choose. To start the rip, |
1817 | -<mousebutton>click</mousebutton> the <guibutton>Start</guibutton> button. |
1818 | +in <trademark>Ogg</trademark>, <trademark>MP3</trademark>, or other format that |
1819 | +you choose. To start the rip, <mousebutton>click</mousebutton> the |
1820 | +<guibutton>Start</guibutton> button. |
1821 | </para> |
1822 | </listitem> |
1823 | </varlistentry> |
1824 | @@ -138,13 +145,13 @@ |
1825 | <listitem> |
1826 | <para> |
1827 | Go to <menuchoice><guimenu>Tools</guimenu><guimenuitem>Rip Video |
1828 | -CD...</guimenuitem></menuchoice> to rip a video <acronym>CD</acronym> as a local |
1829 | -file. To start the rip, <mousebutton>click</mousebutton> the |
1830 | +CD...</guimenuitem></menuchoice> to rip a video <acronym>CD</acronym> as a |
1831 | +local file. To start the rip, <mousebutton>click</mousebutton> the |
1832 | <guibutton>Start</guibutton> button. |
1833 | </para> |
1834 | </listitem> |
1835 | </varlistentry> |
1836 | -<varlistentry><term>Rip video DVD</term> |
1837 | +<varlistentry><term>Rip video <acronym>DVD</acronym></term> |
1838 | <listitem> |
1839 | <para> |
1840 | Go to <menuchoice><guimenu>Tools</guimenu><guimenuitem>Rip Video |
1841 | @@ -158,12 +165,13 @@ |
1842 | </sect1> |
1843 | |
1844 | <sect1 id="usb"> |
1845 | -<title>Bootable ISO Images From USB Media</title> |
1846 | +<title>Bootable <acronym>ISO</acronym> Images From <acronym>USB</acronym> |
1847 | +Media</title> |
1848 | <para> |
1849 | &kubuntu; ships with the application <application>Startup Disk |
1850 | -Creator</application>. This application for the creation of a bootable |
1851 | -<acronym>USB</acronym> flash drive to install &kubuntu;, Ubuntu, or other Linux |
1852 | -distributions. |
1853 | +Creator</application>. This application is for the creation of a bootable |
1854 | +<acronym>USB</acronym> flash drive to install &kubuntu;, &ubuntu;, or other |
1855 | +<trademark>Linux</trademark> distributions. |
1856 | </para> |
1857 | <para> |
1858 | <example><title>Startup Disk Creator</title> |
1859 | @@ -174,7 +182,8 @@ |
1860 | </mediaobject> |
1861 | </example> |
1862 | </para> |
1863 | -<procedure><title>Creating a bootable USB flash drive from an ISO image</title> |
1864 | +<procedure><title>Creating a bootable <acronym>USB</acronym> flash drive from |
1865 | +an <acronym>ISO</acronym> image</title> |
1866 | <step> |
1867 | <para> |
1868 | Open <application>Startup Disk Creator</application> by going to |
1869 | @@ -198,11 +207,10 @@ |
1870 | <note><title>Before continuing on...</title> |
1871 | <para> |
1872 | If, after formatting, the device is still not showing any <guilabel>Free |
1873 | -Space</guilabel>, it may be necessary to close out of <application>Startup Disk |
1874 | -Creator</application>, and then physically remove the device. After physically |
1875 | -removing it, wait a few seconds and then insert it back into the computer. Open |
1876 | -<application>Startup Disk Creator</application> and continue with the following |
1877 | -steps. |
1878 | +Space</guilabel>, it may be necessary to close <application>Startup Disk |
1879 | +Creator</application> and then physically remove the device. Then wait a few |
1880 | +seconds and insert it back into the computer. Open <application>Startup Disk |
1881 | +Creator</application> and continue with the following steps: |
1882 | </para> |
1883 | </note> |
1884 | </step> |
1885 | @@ -212,7 +220,7 @@ |
1886 | reserved extra space</guibutton> if the <acronym>USB</acronym> flash drive will |
1887 | be used to run the &kubuntu; desktop live. Use the slider to select the amount |
1888 | of storage space. The other option, <guibutton>Discarded on shutdown, unless you |
1889 | -save them elsewhere</guibutton> will not store data on the device. Use this |
1890 | +save them elsewhere</guibutton>, will not store data on the device. Use this |
1891 | selection if the <acronym>USB</acronym> flash drive is only for installing the |
1892 | &kubuntu; desktop. |
1893 | </para> |
1894 | @@ -220,7 +228,7 @@ |
1895 | <step> |
1896 | <para> |
1897 | To start the process, <mousebutton>click</mousebutton> the <guibutton>Make |
1898 | -Startup Disk</guibutton>. |
1899 | +Startup Disk</guibutton> button. |
1900 | </para> |
1901 | </step> |
1902 | </procedure> |
1903 | |
1904 | === modified file 'docs/network/C/network.xml' |
1905 | --- docs/network/C/network.xml 2010-07-23 02:20:29 +0000 |
1906 | +++ docs/network/C/network.xml 2012-03-22 19:19:20 +0000 |
1907 | @@ -14,7 +14,7 @@ |
1908 | <abstract> |
1909 | <para> |
1910 | This document provides information about configuring systems to connect |
1911 | -to networks, the Internet, and other machines on a shared network. |
1912 | +to networks, the internet, and other machines on a shared network. |
1913 | </para> |
1914 | </abstract> |
1915 | </articleinfo> |
1916 | @@ -66,9 +66,10 @@ |
1917 | </step> |
1918 | <step> |
1919 | <para> |
1920 | -Select the desired connection if it is available and click the |
1921 | -<guibutton>Edit...</guibutton> button. If the proper connection is not |
1922 | -available, click the <guibutton>Add...</guibutton> button. |
1923 | +Select the desired connection if it is available and |
1924 | +<mousebutton>click</mousebutton> the <guibutton>Edit...</guibutton> button. If |
1925 | +the proper connection is not available, <mousebutton>click</mousebutton> the |
1926 | +<guibutton>Add...</guibutton> button. |
1927 | </para> |
1928 | </step> |
1929 | <step> |
1930 | @@ -79,12 +80,14 @@ |
1931 | </step> |
1932 | <step> |
1933 | <para> |
1934 | -Enter the details and click the <guibutton>OK</guibutton> button. |
1935 | +Enter the details and <mousebutton>click</mousebutton> the |
1936 | +<guibutton>OK</guibutton> button. |
1937 | </para> |
1938 | </step> |
1939 | <step> |
1940 | <para> |
1941 | -Click the <guibutton>OK</guibutton> in the main window. |
1942 | +<mousebutton>Click</mousebutton> the <guibutton>OK</guibutton> in the main |
1943 | +window. |
1944 | </para> |
1945 | </step> |
1946 | </procedure> |
1947 | @@ -95,13 +98,13 @@ |
1948 | <sect1 id="wireless"> |
1949 | <title>Wireless</title> |
1950 | <para> |
1951 | -In some cases, the wireless network device may need a restricted driver in |
1952 | +In some cases, the wireless network device may need a restricted driver in |
1953 | order to operate. The best way to check this is to open the application named |
1954 | -<application>Jockey</application>. To open <application>Jockey</application>, go |
1955 | -to &menujockey;. If the wireless network device requires a restricted driver, |
1956 | -<application>Jockey</application> will provide that information and assist with |
1957 | -selecting, installing and activating the proper driver. When this step is |
1958 | -completed, wireless connections can be configured. The machine must be |
1959 | +<application>Jockey</application>. To open <application>Jockey</application>, |
1960 | +go to &menujockey;. If the wireless network device requires a restricted |
1961 | +driver, <application>Jockey</application> will provide that information and |
1962 | +assist with selecting, installing, and activating the proper driver. When this |
1963 | +step is completed, wireless connections can be configured. The machine must be |
1964 | rebooted before the newly installed, restricted driver will make the wireless |
1965 | device work. |
1966 | </para> |
1967 | @@ -115,27 +118,27 @@ |
1968 | <step> |
1969 | <para> |
1970 | <mousebutton>Click</mousebutton> the <guiicon>NetworkManager</guiicon> in |
1971 | -the System Tray area and select <guimenuitem>Manage |
1972 | +the System Tray area and select <guimenuitem>Manage |
1973 | Connections...</guimenuitem>. |
1974 | </para> |
1975 | </step> |
1976 | <step> |
1977 | <para> |
1978 | -If a connection has been made previously to the selected network, connect to that |
1979 | -network by clicking on it in the <guilabel>Wireless</guilabel> tab. If |
1980 | -no connection has been made to the desired network previously, continue with the |
1981 | -following procedure: |
1982 | +If a connection has been made previously to the selected network, connect to |
1983 | +that network by <mousebutton>clicking</mousebutton> on it in the |
1984 | +<guilabel>Wireless</guilabel> tab. If no connection has been made to the |
1985 | +desired network previously, continue with the following procedure: |
1986 | </para> |
1987 | </step> |
1988 | <step> |
1989 | <para> |
1990 | -Click the <guibutton>Add...</guibutton> button. |
1991 | +<mousebutton>Click</mousebutton> the <guibutton>Add...</guibutton> button. |
1992 | </para> |
1993 | </step> |
1994 | <step> |
1995 | <para> |
1996 | Enter the <acronym>SSID</acronym> of the new network. It can be entered |
1997 | -manually if known. If not, press the <guibutton>Scan</guibutton> button to |
1998 | +manually, if known. If not, press the <guibutton>Scan</guibutton> button to |
1999 | search for the network. |
2000 | </para> |
2001 | </step> |
2002 | @@ -161,8 +164,8 @@ |
2003 | <sect1 id="mobile"> |
2004 | <title>Mobile Broadband</title> |
2005 | <para> |
2006 | -<emphasis>Mobile Broadband</emphasis> means any high speed Internet connection |
2007 | -that is provided by an external device such as a <acronym>3G</acronym> |
2008 | +<emphasis>Mobile Broadband</emphasis> means any high speed internet connection |
2009 | +that is provided by an external device, such as a <acronym>3G</acronym> |
2010 | <acronym>USB</acronym> stick or mobile phone with built-in |
2011 | <acronym>HSPA</acronym>, <acronym>UMTS</acronym>, or <acronym>GPRS</acronym> |
2012 | data connection. Some laptops have been offered recently with mobile broadband |
2013 | @@ -192,7 +195,7 @@ |
2014 | </step> |
2015 | <step> |
2016 | <para> |
2017 | -The <guilabel>New Mobile Broadband Connection</guilabel> Wizard will be |
2018 | +The <guilabel>New Mobile Broadband Connection</guilabel> wizard will be |
2019 | displayed. Enter the device and carrier information. |
2020 | </para> |
2021 | </step> |
2022 | @@ -203,9 +206,9 @@ |
2023 | <sect1 id="vpn"> |
2024 | <title>Virtual Private Networks (<acronym>VPN</acronym>)</title> |
2025 | <para> |
2026 | -There are three types of Virtual Private Networks (<acronym>VPN</acronym>) that |
2027 | -are currently supported by <application>NetworkManager</application>. It is |
2028 | -important to know the type of <acronym>VPN</acronym> network in order to |
2029 | +There are three types of Virtual Private Networks (<acronym>VPN</acronym>) |
2030 | +which are currently supported by <application>NetworkManager</application>. It |
2031 | +is important to know the type of <acronym>VPN</acronym> network in order to |
2032 | connect to it. |
2033 | </para> |
2034 | <procedure><title>Connecting to a VPN</title> |
2035 | @@ -253,12 +256,12 @@ |
2036 | </step> |
2037 | <step> |
2038 | <para> |
2039 | -Click the <guilabel>DSL</guilabel> tab. |
2040 | +<mousebutton>Click</mousebutton> the <guilabel>DSL</guilabel> tab. |
2041 | </para> |
2042 | </step> |
2043 | <step> |
2044 | <para> |
2045 | -Click the <guilabel>Add...</guilabel> button. |
2046 | +<mousebutton>Click</mousebutton> the <guilabel>Add...</guilabel> button. |
2047 | </para> |
2048 | </step> |
2049 | </procedure> |
2050 | |
2051 | === modified file 'docs/security/C/security.xml' |
2052 | --- docs/security/C/security.xml 2010-03-26 21:38:03 +0000 |
2053 | +++ docs/security/C/security.xml 2012-03-22 19:19:20 +0000 |
2054 | @@ -70,24 +70,25 @@ |
2055 | Keyboard shortcuts can be changed in <application>System Settings</application> |
2056 | under the <guilabel>Keyboard & Mouse</guilabel>. To access these settings, |
2057 | go to Menu Bread Crumbs. Select <guilabel>Global Keyboard Shortcuts</guilabel>, |
2058 | -in the KDE component dropdown, select <guilabel>Run Command Interface</guilabel> |
2059 | -and locate <guilabel>Lock Session</guilabel>. |
2060 | +in the <trademark>KDE</trademark> component drop-down, select <guilabel>Run |
2061 | +Command Interface</guilabel>, and locate <guilabel>Lock Session</guilabel>. |
2062 | </para> |
2063 | </note> |
2064 | |
2065 | <note><title>Adding a lock screen button to the panel</title> |
2066 | <para> |
2067 | A <guibutton>Lock Screen</guibutton> button can be added to the |
2068 | -<application>Panel</application> for quick and easy screen locking. Right-click |
2069 | -the <application>Panel</application>, select <guibutton>Add |
2070 | -Widgets...</guibutton>, select <guibutton>Lock/Logout</guibutton> and drag it |
2071 | -to the proper location on the Panel. |
2072 | +<application>Panel</application> for quick and easy screen locking. |
2073 | +<mousebutton>Right-click</mousebutton> the <application>Panel</application>, |
2074 | +select <guibutton>Add Widgets...</guibutton>, select |
2075 | +<guibutton>Lock/Logout</guibutton>, and drag it to the proper location on the |
2076 | +<application>Panel</application>. |
2077 | </para> |
2078 | </note> |
2079 | |
2080 | <para> |
2081 | To unlock the screen, move the mouse or press a key. Enter the password, and |
2082 | -either press the <keycap>Return</keycap> key or press the |
2083 | +either press the <keycap>Return</keycap> key or press the |
2084 | <guibutton>Unlock</guibutton> button. |
2085 | </para> |
2086 | <para> |
2087 | @@ -105,17 +106,17 @@ |
2088 | |
2089 | <para> |
2090 | <application>Guarddog</application> is the firewall of choice for &kubuntu;. |
2091 | -Please review the <ulink type="help" |
2092 | -url="help:/kubuntu/network/">Networking</ulink> |
2093 | -documentation and locate the <application>Guarddog</application> section. |
2094 | +Please review the <ulink type="help" |
2095 | +url="help:/kubuntu/network/">Networking</ulink> documentation and locate the |
2096 | +<application>Guarddog</application> section. |
2097 | </para> |
2098 | </sect1> |
2099 | |
2100 | <sect1 id="keep-safe-avoid-internet-crime" status="complete"> |
2101 | <title>Avoid Internet nuisances and crime</title> |
2102 | |
2103 | -<para>From time to time, email messages carry viruses or links to fraudulent |
2104 | -websites. It is important to learn how to deal with these messages, in order to |
2105 | +<para>From time to time email messages carry viruses or links to fraudulent |
2106 | +web sites. It is important to learn how to deal with these messages in order to |
2107 | prevent the computer or personal information from being compromised or misused. |
2108 | </para> |
2109 | |
2110 | @@ -131,20 +132,20 @@ |
2111 | <itemizedlist> |
2112 | <listitem> |
2113 | <para> |
2114 | -Spam (junk) email with offers for unwanted services and products |
2115 | -</para> |
2116 | -</listitem> |
2117 | - |
2118 | -<listitem> |
2119 | -<para> |
2120 | -Scam emails asking for help in exchange for money |
2121 | -</para> |
2122 | -</listitem> |
2123 | - |
2124 | -<listitem> |
2125 | -<para> |
2126 | -Phishing email that appears to be from a bank or other online service, asking |
2127 | -for personal and financial details, or passwords |
2128 | +Spam (junk) email with offers for unwanted services and products. |
2129 | +</para> |
2130 | +</listitem> |
2131 | + |
2132 | +<listitem> |
2133 | +<para> |
2134 | +Scam emails asking for help in exchange for money. |
2135 | +</para> |
2136 | +</listitem> |
2137 | + |
2138 | +<listitem> |
2139 | +<para> |
2140 | +Phishing email, that appears to be from a bank or other online service, asking |
2141 | +for personal and financial details or passwords. |
2142 | </para> |
2143 | </listitem> |
2144 | </itemizedlist> |
2145 | @@ -159,7 +160,7 @@ |
2146 | |
2147 | <listitem> |
2148 | <para> |
2149 | -Never click on links in emails that lead to websites asking for passwords or |
2150 | +Never click on links in emails that lead to web sites asking for passwords or |
2151 | similar information. It is possible for the text of the link to show one |
2152 | address, but clicking on the link actually connects to a different (possibly |
2153 | dangerous) address. Instead of clicking a potentially misleading link, type the |
2154 | @@ -169,22 +170,22 @@ |
2155 | |
2156 | <listitem> |
2157 | <para> |
2158 | -When visiting a website that asks for financial information, ensure that it is |
2159 | -secure. <application>Konqueror</application> and |
2160 | +When visiting a web site that asks for financial information, ensure that it is |
2161 | +secure. <application>Konqueror</application> and |
2162 | <application>Firefox</application> are two browsers commonly used in &kubuntu;. |
2163 | -Both have two areas that indicate if the current page is secure. On secure |
2164 | -webpages, the address bar will have a yellow background and a lock |
2165 | -symbol to the right of the address. The second area is the status bar located at |
2166 | -the bottom right of the browser window. If the page is secure, a lock icon will |
2167 | -appear in this area. Clicking on either of the lock symbols will produce a |
2168 | -dialog that explains the type of licensing and security for that page. |
2169 | +Both have two areas that indicate if the current page is secure. On secure web |
2170 | +pages, the address bar will have a yellow background and a lock symbol to the |
2171 | +right of the address. The second area is the status bar located at the bottom |
2172 | +right of the browser window. If the page is secure, a lock icon will appear in |
2173 | +this area. Clicking on either of the lock symbols will produce a dialog that |
2174 | +explains the type of licensing and security for the page. |
2175 | </para> |
2176 | </listitem> |
2177 | |
2178 | <listitem> |
2179 | <para> |
2180 | Only download and run software from trusted sources. By default, software can |
2181 | -only be downloaded directly from Ubuntu. |
2182 | +only be downloaded directly from &ubuntu;. |
2183 | </para> |
2184 | </listitem> |
2185 | </itemizedlist> |
2186 | @@ -196,8 +197,8 @@ |
2187 | <para> |
2188 | Occasionally users lose computer information. There are many possible causes |
2189 | for such unforeseen <emphasis>data loss</emphasis>. The problem could be |
2190 | -anything from a power loss or equipment failure to accidentally deleting a file. |
2191 | -With regular backup copies, if a problem should occur, it may be possible |
2192 | +anything from a power loss or equipment failure to accidentally deleting a |
2193 | +file. With regular backup copies, if a problem should occur, it may be possible |
2194 | to retrieve important files. Users are strongly encouraged to make backups. |
2195 | </para> |
2196 | <para> |
2197 | @@ -206,9 +207,11 @@ |
2198 | attached to the computer. Options include: |
2199 | </para> |
2200 | <itemizedlist> |
2201 | -<listitem><para>Writable CDs and DVDs</para></listitem> |
2202 | -<listitem><para>External hard disks and flash memory devices</para></listitem> |
2203 | -<listitem><para>Another computer on the network</para></listitem> |
2204 | +<listitem><para>Writable <acronym>CD</acronym>s and <acronym>DVD</acronym>s. |
2205 | +</para></listitem> |
2206 | +<listitem><para>External hard disks.</para></listitem> |
2207 | +<listitem><para>Flash memory devices.</para></listitem> |
2208 | +<listitem><para>Another computer on the network.</para></listitem> |
2209 | </itemizedlist> |
2210 | <para> |
2211 | A simple way of backing up your files is to copy them manually to a safe |
2212 | @@ -217,7 +220,7 @@ |
2213 | </para> |
2214 | <para> |
2215 | Another backup method is <application>Keep</application>, an automated &kubuntu; |
2216 | -backup solution, preferred by many &kubuntu; veterans. To install the |
2217 | +backup solution preferred by many &kubuntu; veterans. To install the |
2218 | <application>Keep</application> package, please refer to the <ulink |
2219 | type="help" url="help:/kubuntu/manage-software/">Adding Applications</ulink> |
2220 | document for help on installing applications. Once installed, |
2221 | |
2222 | === modified file 'docs/sharing/C/sharing.xml' |
2223 | --- docs/sharing/C/sharing.xml 2010-03-26 21:38:03 +0000 |
2224 | +++ docs/sharing/C/sharing.xml 2012-03-22 19:19:20 +0000 |
2225 | @@ -13,7 +13,8 @@ |
2226 | &legalnotice; |
2227 | <abstract> |
2228 | <para> |
2229 | -This document explains how to share files between &kubuntu; and Windows. |
2230 | +This document explains how to share files between &kubuntu; and |
2231 | +<trademark class='registered'>Windows</trademark>. |
2232 | </para> |
2233 | </abstract> |
2234 | </articleinfo> |
2235 | @@ -25,17 +26,20 @@ |
2236 | Computer networks are often comprised of diverse systems. While operating a |
2237 | network made up entirely of &kubuntu; desktop and server computers would |
2238 | certainly be fun, some network environments will consist of &kubuntu; and |
2239 | -<trademark class='registered'>Microsoft</trademark> |
2240 | -<trademark class='registered'>Windows</trademark> systems working together. This |
2241 | -section of the &kubuntu; &sg-title; introduces principles and tools used for |
2242 | -configuring &kubuntu; servers to share network resources with Windows computers. |
2243 | +<trademark class='registered'>Microsoft</trademark> <trademark |
2244 | +class='registered'>Windows</trademark> systems working together. This section |
2245 | +of the &kubuntu; &sg-title; introduces principles and tools used for |
2246 | +configuring &kubuntu; servers to share network resources with <trademark |
2247 | +class='registered'>Windows</trademark> computers. |
2248 | </para> |
2249 | |
2250 | <para> |
2251 | -Successfully networking a &kubuntu; system with Windows clients involves |
2252 | -providing and integrating services common to Windows environments. These |
2253 | -services support sharing data and information about the computers and users |
2254 | -on the network, and may be classified into three major categories: |
2255 | +Successfully networking a &kubuntu; system with <trademark |
2256 | +class='registered'>Windows</trademark> clients involves providing and |
2257 | +integrating services common to <trademark |
2258 | +class='registered'>Windows</trademark> environments. These services support |
2259 | +sharing data and information about the computers and users on the network, and |
2260 | +may be classified into three major categories: |
2261 | </para> |
2262 | |
2263 | <itemizedlist> |
2264 | @@ -48,35 +52,39 @@ |
2265 | </listitem> |
2266 | <listitem> |
2267 | <para> |
2268 | -<emphasis role="bold">Directory Services</emphasis>. Vital information is shared |
2269 | -about the computers and users of the network with such technologies as the |
2270 | -Lightweight Directory Access Protocol (<acronym>LDAP</acronym>) and Microsoft |
2271 | -<trademark class='registered'>Active Directory</trademark>. |
2272 | +<emphasis>Directory Services</emphasis>. Vital information is |
2273 | +shared about the computers and users of the network with such technologies as |
2274 | +the Lightweight Directory Access Protocol (<acronym>LDAP</acronym>) and |
2275 | +<trademark class='registered'>Microsoft</trademark> <trademark |
2276 | +class='registered'>Active Directory</trademark>. |
2277 | </para> |
2278 | </listitem> |
2279 | <listitem> |
2280 | <para> |
2281 | -<emphasis role="bold">Authentication and Access</emphasis>. It is |
2282 | -necessary to be able to establish the identity of a computer or user to |
2283 | -determine the information the computer or user is authorized to access. |
2284 | -Authentication and access use principles and technologies such as file |
2285 | -permissions, group policies, and the Kerberos authentication service. |
2286 | +<emphasis>Authentication and Access</emphasis>. It is necessary to be able to |
2287 | +establish the identity of a computer or user to determine the information the |
2288 | +computer or user is authorized to access. Authentication and access use |
2289 | +principles and technologies such as file permissions, group policies, and the |
2290 | +<trademark>Kerberos</trademark> authentication service. |
2291 | </para> |
2292 | </listitem> |
2293 | </itemizedlist> |
2294 | |
2295 | <para> |
2296 | -A &kubuntu; system can provide all such capabilities for Windows clients and |
2297 | -enable sharing network resources with them. One of the principal pieces of |
2298 | -software included in a &kubuntu; system for Windows networking is the Samba |
2299 | -suite of <acronym>SMB</acronym> server applications and tools. |
2300 | +A &kubuntu; system can provide all such capabilities for <trademark |
2301 | +class='registered'>Windows</trademark> clients and enable sharing network |
2302 | +resources with them. One of the principal pieces of software included in a |
2303 | +&kubuntu; system for <trademark class='registered'>Windows</trademark> |
2304 | +networking is the <application>Samba</application> suite of |
2305 | +<acronym>SMB</acronym> server applications and tools. |
2306 | </para> |
2307 | |
2308 | <para> |
2309 | -This section of the &kubuntu; &sg-title; will introduce some of the ways Samba |
2310 | -is commonly used, and how to install and configure the necessary packages. |
2311 | -Additional detailed documentation and information on Samba can be found |
2312 | -on the <ulink url="http://www.samba.org">Samba website</ulink>. |
2313 | +This section of the &kubuntu; &sg-title; will introduce some of the ways |
2314 | +<application>Samba</application> is commonly used, and how to install and |
2315 | +configure the necessary packages. Additional detailed documentation and |
2316 | +information on <application>Samba</application> can be found on the <ulink |
2317 | +url="http://www.samba.org"><application>Samba</application> website</ulink>. |
2318 | </para> |
2319 | </sect1> |
2320 | |
2321 | @@ -84,22 +92,25 @@ |
2322 | <title>Samba File Server</title> |
2323 | |
2324 | <para> |
2325 | -One of the most common ways to network &kubuntu; and Windows computers is to |
2326 | -configure Samba as a File Server. This section covers setting up a |
2327 | -<application>Samba</application> server to share files with Windows clients. |
2328 | +One of the most common ways to network &kubuntu; and <trademark |
2329 | +class='registered'>Windows</trademark> computers is to configure |
2330 | +<application>Samba</application> as a file server. This section covers setting |
2331 | +up a <application>Samba</application> server to share files with <trademark |
2332 | +class='registered'>Windows</trademark> clients. |
2333 | </para> |
2334 | |
2335 | <para> |
2336 | The server will be configured to share files with any client on the network |
2337 | -without prompting for a password. If the environment requires stricter Access |
2338 | -Controls, see <xref linkend="samba-fileprint-security"/> |
2339 | +without prompting for a password. If the environment requires stricter access |
2340 | +controls, see <xref linkend="samba-fileprint-security"/>. |
2341 | </para> |
2342 | |
2343 | <sect2 id="samba-fileserver-installation"> |
2344 | <title>Installation</title> |
2345 | |
2346 | <para> |
2347 | -The first step is to install the <application>samba</application> package. From a terminal prompt enter: |
2348 | +The first step is to install the <application>samba</application> package. From |
2349 | +a terminal prompt, enter: |
2350 | </para> |
2351 | |
2352 | <screen> |
2353 | @@ -107,7 +118,8 @@ |
2354 | </screen> |
2355 | |
2356 | <para> |
2357 | -That's all there is to it. Samba is ready to be configured for file sharing. |
2358 | +That's all there is to it. <application>Samba</application> is ready to be |
2359 | +configured for file sharing. |
2360 | </para> |
2361 | |
2362 | </sect2> |
2363 | @@ -115,16 +127,18 @@ |
2364 | <title>Configuration</title> |
2365 | |
2366 | <para> |
2367 | -The main Samba configuration file is located in |
2368 | -<filename>/etc/samba/smb.conf</filename>. The default configuration file has a |
2369 | +The main <application>Samba</application> configuration file is located in |
2370 | +<filename>/etc/samba/smb.conf</filename>. The default configuration file has a |
2371 | significant number of comments in order to document various configuration |
2372 | -directives. |
2373 | +directives. |
2374 | </para> |
2375 | <note> |
2376 | <para> |
2377 | -Not all the available options are included in the default configuration file. See the <filename>smb.conf</filename> |
2378 | -<application>man</application> page or the |
2379 | -<ulink url="http://samba.org/samba/docs/man/Samba-HOWTO-Collection/">Samba HOWTO Collection</ulink> for more details. |
2380 | +Not all of the available options are included in the default configuration |
2381 | +file. See the <filename>smb.conf</filename> <application>man</application> page |
2382 | +or the <ulink |
2383 | +url="http://samba.org/samba/docs/man/Samba-HOWTO-Collection/"> |
2384 | +<application>Samba</application> HOWTO Collection</ulink> for more details. |
2385 | </para> |
2386 | </note> |
2387 | |
2388 | @@ -144,8 +158,8 @@ |
2389 | |
2390 | <para> |
2391 | The <emphasis>security</emphasis> parameter is farther down in the [global] |
2392 | -section, and is commented out by default. |
2393 | -Change <emphasis>EXAMPLE</emphasis> to match the actual environment. |
2394 | +section, and is commented out by default. Change <emphasis>EXAMPLE</emphasis> |
2395 | +to match the actual environment. |
2396 | </para> |
2397 | |
2398 | </step> |
2399 | @@ -169,7 +183,7 @@ |
2400 | <itemizedlist> |
2401 | <listitem> |
2402 | <para> |
2403 | -<emphasis>comment:</emphasis> a short description of the share. Adjust to fit |
2404 | +<emphasis>comment:</emphasis> a short description of the share. Adjust to fit |
2405 | as appropriate. |
2406 | </para> |
2407 | </listitem> |
2408 | @@ -180,17 +194,19 @@ |
2409 | <para> |
2410 | This example uses <filename>/srv/samba/sharename</filename> because, according |
2411 | to the <emphasis>Filesystem Hierarchy Standard (FHS)</emphasis>, |
2412 | -<ulink url="http://www.pathname.com/fhs/pub/fhs-2.3. |
2413 | -html#SRVDATAFORSERVICESPROVIDEDBYSYSTEM">/srv</ulink> |
2414 | -is where site-specific data should be served. Technically Samba shares can be |
2415 | -placed anywhere on the filesystem as long as the permissions are correct, but |
2416 | -adhering to standards is recommended. |
2417 | +<ulink |
2418 | +url="http://www.pathname.com/fhs/pub/fhs-2.3.html#SRVDATAFORSERVICESPROVIDEDBYSYSTEM"> |
2419 | +/srv</ulink> is where site-specific data should be served. Technically, |
2420 | +<application>Samba</application> shares can be placed anywhere on the |
2421 | +filesystem as long as the permissions are correct, but adhering to standards is |
2422 | +recommended. |
2423 | </para> |
2424 | </listitem> |
2425 | <listitem> |
2426 | <para> |
2427 | -<emphasis>browsable:</emphasis> enables Windows clients to browse the shared |
2428 | -directory using <application>Windows Explorer</application>. |
2429 | +<emphasis>browsable:</emphasis> enables <trademark |
2430 | +class='registered'>Windows</trademark> clients to browse the shared directory |
2431 | +using <application>Windows Explorer</application>. |
2432 | </para> |
2433 | </listitem> |
2434 | <listitem> |
2435 | @@ -201,13 +217,16 @@ |
2436 | </listitem> |
2437 | <listitem> |
2438 | <para> |
2439 | -<emphasis>read only:</emphasis> determines if the share is read only or if write privileges are granted. Write privileges are allowed only when the value is <emphasis>no</emphasis>, as is seen in this example. If the value is <emphasis>yes</emphasis>, then access to the share is read only. |
2440 | +<emphasis>read only:</emphasis> determines if the share is read only or if |
2441 | +write privileges are granted. Write privileges are allowed only when the value |
2442 | +is <emphasis>no</emphasis>, as is seen in this example. If the value is |
2443 | +<emphasis>yes</emphasis>, then access to the share is read only. |
2444 | </para> |
2445 | </listitem> |
2446 | <listitem> |
2447 | <para> |
2448 | -<emphasis>create mask:</emphasis> determines the permissions new files will have |
2449 | -when created. |
2450 | +<emphasis>create mask:</emphasis> determines the permissions new files will |
2451 | +have when created. |
2452 | </para> |
2453 | </listitem> |
2454 | </itemizedlist> |
2455 | @@ -217,7 +236,7 @@ |
2456 | |
2457 | <para> |
2458 | Now that <application>Samba</application> is configured, the directory needs to |
2459 | -be created and the permissions changed. From a terminal enter: |
2460 | +be created and the permissions changed. From a terminal, enter: |
2461 | </para> |
2462 | |
2463 | <screen> |
2464 | @@ -227,8 +246,9 @@ |
2465 | |
2466 | <note> |
2467 | <para> |
2468 | -The <emphasis>-p</emphasis> switch tells mkdir to create the entire directory |
2469 | -tree if it doesn't exist. Change the share name to fit the environment. |
2470 | +The <emphasis>-p</emphasis> switch tells <command>mkdir</command> to create the |
2471 | +entire directory tree if it doesn't exist. Change the share name to fit the |
2472 | +environment. |
2473 | </para> |
2474 | </note> |
2475 | |
2476 | @@ -236,7 +256,8 @@ |
2477 | <step> |
2478 | |
2479 | <para> |
2480 | -Finally, restart the <application>samba</application> services to enable the new configuration: |
2481 | +Finally, restart the <application>samba</application> services to enable the |
2482 | +new configuration: |
2483 | </para> |
2484 | |
2485 | <screen> |
2486 | @@ -248,21 +269,23 @@ |
2487 | |
2488 | <warning> |
2489 | <para> |
2490 | -The above configuration gives all access to any client on the local network. For |
2491 | -a more secure configuration, see <xref linkend="samba-fileprint-security"/>. |
2492 | +The above configuration gives all access to any client on the local network. |
2493 | +For a more secure configuration, see <xref |
2494 | +linkend="samba-fileprint-security"/>. |
2495 | </para> |
2496 | </warning> |
2497 | |
2498 | <para> |
2499 | -From a Windows client, it should now be possible to browse to the &kubuntu; file |
2500 | -server and see the shared directory. To check that everything is working, try |
2501 | -creating a directory from Windows. |
2502 | +From a <trademark class='registered'>Windows</trademark> client, it should now |
2503 | +be possible to browse to the &kubuntu; file server and see the shared |
2504 | +directory. To check that everything is working, try creating a directory from |
2505 | +<trademark class='registered'>Windows</trademark>. |
2506 | </para> |
2507 | |
2508 | <para> |
2509 | To create additional shares, simply create new <emphasis>[dir]</emphasis> |
2510 | sections in <filename>/etc/samba/smb.conf</filename>, and restart |
2511 | -<emphasis>Samba</emphasis>. Make sure that the directory to be shared actually |
2512 | +<emphasis>Samba</emphasis>. Make sure that the directory to be shared actually |
2513 | exists and that the permissions are correct. |
2514 | </para> |
2515 | </sect2> |
2516 | @@ -273,13 +296,15 @@ |
2517 | <listitem> |
2518 | <para> |
2519 | For in depth Samba configurations see the |
2520 | -<ulink url="http://samba.org/samba/docs/man/Samba-HOWTO-Collection/">Samba HOWTO Collection</ulink> |
2521 | +<ulink url="http://samba.org/samba/docs/man/Samba-HOWTO-Collection/">Samba |
2522 | +HOWTO Collection</ulink> |
2523 | </para> |
2524 | </listitem> |
2525 | <listitem> |
2526 | <para> |
2527 | -The guide is also available in |
2528 | -<ulink url="http://www.amazon.com/exec/obidos/tg/detail/-/0131882228">printed format</ulink>. |
2529 | +The guide is also available in <ulink |
2530 | +url="http://www.amazon.com/exec/obidos/tg/detail/-/0131882228">printed |
2531 | +format</ulink>. |
2532 | </para> |
2533 | </listitem> |
2534 | <listitem> |
2535 | @@ -300,45 +325,50 @@ |
2536 | <title>Samba Security Modes</title> |
2537 | |
2538 | <para> |
2539 | -There are two security levels available to the Common Internet Filesystem (CIFS) |
2540 | -network protocol <emphasis>user-level</emphasis> and |
2541 | -<emphasis>share-level</emphasis>. Samba's <emphasis>security mode</emphasis> |
2542 | -implementation allows more flexibility, providing four ways of implementing |
2543 | -user-level security and one way to implement share-level: |
2544 | +There are two security levels available to the Common Internet Filesystem |
2545 | +(<acronym>CIFS</acronym>) network protocol <emphasis>user-level</emphasis> and |
2546 | +<emphasis>share-level</emphasis>. <application>Samba</application>'s |
2547 | +<emphasis>security mode</emphasis> implementation allows more flexibility, |
2548 | +providing four ways of implementing user-level security and one way to |
2549 | +implement share-level: |
2550 | </para> |
2551 | |
2552 | <itemizedlist> |
2553 | <listitem> |
2554 | <para> |
2555 | <emphasis>security = user:</emphasis> requires clients to supply a username and |
2556 | -password to connect to shares. Samba user accounts are separate from system |
2557 | -accounts, but the <application>libpam-smbpass</application> package will sync |
2558 | -system users and passwords with the Samba user database. |
2559 | -</para> |
2560 | -</listitem> |
2561 | -<listitem> |
2562 | -<para> |
2563 | -<emphasis>security = domain:</emphasis> this mode allows the Samba server to |
2564 | -appear to Windows clients as a Primary Domain Controller (PDC), Backup Domain |
2565 | -Controller (BDC), or a Domain Member Server (DMS). See |
2566 | -<xref linkend="samba-dc"/> for further information. |
2567 | -</para> |
2568 | -</listitem> |
2569 | -<listitem> |
2570 | -<para> |
2571 | -<emphasis>security = ADS:</emphasis> allows the Samba server to join an Active |
2572 | -Directory domain as a native member. See <xref linkend="samba-ad-integration"/> |
2573 | -for details. |
2574 | -</para> |
2575 | -</listitem> |
2576 | -<listitem> |
2577 | -<para> |
2578 | -<emphasis>security = server:</emphasis> this mode is left over from before Samba |
2579 | -could become a member server, and, due to some security issues, should not be |
2580 | -used. See the <ulink |
2581 | +password to connect to shares. <application>Samba</application> user accounts |
2582 | +are separate from system accounts, but the |
2583 | +<application>libpam-smbpass</application> package will sync system users and |
2584 | +passwords with the <application>Samba</application> user database. |
2585 | +</para> |
2586 | +</listitem> |
2587 | +<listitem> |
2588 | +<para> |
2589 | +<emphasis>security = domain:</emphasis> this mode allows the |
2590 | +<application>Samba</application> server to appear to <trademark |
2591 | +class='registered'>Windows</trademark> clients as a Primary Domain Controller |
2592 | +(<acronym>PDC</acronym>), Backup Domain Controller (<acronym>BDC</acronym>), or |
2593 | +a Domain Member Server (<acronym>DMS</acronym>). See <xref linkend="samba-dc"/> |
2594 | +for further information. |
2595 | +</para> |
2596 | +</listitem> |
2597 | +<listitem> |
2598 | +<para> |
2599 | +<emphasis>security = ADS:</emphasis> allows the |
2600 | +<application>Samba</application> server to join an <trademark |
2601 | +class='registered'>Active Directory</trademark> domain as a native member. See |
2602 | +<xref linkend="samba-ad-integration"/> for details. |
2603 | +</para> |
2604 | +</listitem> |
2605 | +<listitem> |
2606 | +<para> |
2607 | +<emphasis>security = server:</emphasis> this mode is left over from before |
2608 | +<application>Samba</application> could become a member server, and, due to some |
2609 | +security issues, should not be used. See the <ulink |
2610 | url="http://samba.org/samba/docs/man/Samba-HOWTO-Collection/ServerType. |
2611 | -html#id349531">Server Security</ulink> section of the Samba guide for more |
2612 | -details. |
2613 | +html#id349531">Server Security</ulink> section of the |
2614 | +<application>Samba</application> guide for more details. |
2615 | </para> |
2616 | </listitem> |
2617 | <listitem> |
2618 | @@ -350,8 +380,8 @@ |
2619 | </itemizedlist> |
2620 | |
2621 | <para> |
2622 | -The preferred security mode depends on the environment and what the Samba |
2623 | -server needs to accomplish. |
2624 | +The preferred security mode depends on the environment and what the |
2625 | +<application>Samba</application> server needs to accomplish. |
2626 | </para> |
2627 | |
2628 | </sect2> |
2629 | @@ -359,15 +389,16 @@ |
2630 | <title>Security = User</title> |
2631 | |
2632 | <para> |
2633 | -This section will reconfigure the Samba file and print server, from <xref |
2634 | -linkend="samba-fileserver"/> and the |
2635 | -<ulink type="help" url="help:/kubuntu/printing/"> Print Server</ulink>, to |
2636 | -require authentication. |
2637 | +This section will reconfigure the <application>Samba</application> file and |
2638 | +print server, from <xref linkend="samba-fileserver"/> and the <ulink |
2639 | +type="help" url="help:/kubuntu/printing/"> Print Server</ulink>, to require |
2640 | +authentication. |
2641 | </para> |
2642 | |
2643 | <para> |
2644 | -First, install the <application>libpam-smbpass</application> package which will |
2645 | -sync the system users to the Samba user database: |
2646 | +First, install the <application>libpam-smbpass</application> package, which |
2647 | +will sync the system users to the <application>Samba</application> user |
2648 | +database: |
2649 | </para> |
2650 | |
2651 | <screen> |
2652 | @@ -376,8 +407,9 @@ |
2653 | |
2654 | <note> |
2655 | <para> |
2656 | -If the <emphasis>Samba Server</emphasis> task was chosen during installation, |
2657 | -<application>libpam-smbpass</application> is already installed. |
2658 | +If the <emphasis><application>Samba</application> Server</emphasis> task was |
2659 | +chosen during installation, <application>libpam-smbpass</application> is |
2660 | +already installed. |
2661 | </para> |
2662 | </note> |
2663 | |
2664 | @@ -391,7 +423,8 @@ |
2665 | </programlisting> |
2666 | |
2667 | <para> |
2668 | -Finally, restart Samba for the new settings to take effect: |
2669 | +Finally, restart <application>Samba</application> for the new settings to take |
2670 | +effect: |
2671 | </para> |
2672 | |
2673 | <screen> |
2674 | @@ -400,14 +433,14 @@ |
2675 | |
2676 | <para> |
2677 | Now when connecting to the shared directories or printers, there will be a |
2678 | -prompt for a username and password. |
2679 | +prompt for a username and password. |
2680 | </para> |
2681 | |
2682 | <note> |
2683 | <para> |
2684 | -To map a network drive to the share, <quote>Reconnect at Logon</quote> should be |
2685 | -checked, which will require the username and password to be entered just once, |
2686 | -at least until the password changes. |
2687 | +To map a network drive to the share, <quote>Reconnect at Logon</quote> should |
2688 | +be checked, which will require the username and password to be entered just |
2689 | +once — at least until the password changes. |
2690 | </para> |
2691 | </note> |
2692 | |
2693 | @@ -416,47 +449,45 @@ |
2694 | <title>Share Security</title> |
2695 | |
2696 | <para> |
2697 | -There are several options available to increase the security for each individual |
2698 | -shared directory. Using the <emphasis>[share]</emphasis> example, this section |
2699 | -will cover some common options. |
2700 | +There are several options available to increase the security for each shared |
2701 | +directory. Using the <emphasis>[share]</emphasis> example, this section will |
2702 | +cover some common options. |
2703 | </para> |
2704 | |
2705 | <sect3 id="windows-networking-groups"> |
2706 | <title>Groups</title> |
2707 | |
2708 | <para> |
2709 | -Groups define a collection of computers or users which have a common level of |
2710 | +Groups define a collection of computers or users who have a common level of |
2711 | access to particular network resources and offer a level of granularity in |
2712 | -controlling access to such resources. For example, if a group |
2713 | -<emphasis role="italic">qa</emphasis> is defined and contains the users |
2714 | -<emphasis role="italic">freda</emphasis>, <emphasis |
2715 | -role="italic">danika</emphasis>, and <emphasis role="italic">rob</emphasis> and |
2716 | -a second group <emphasis role="italic">support</emphasis> is defined and |
2717 | -consists of users <emphasis role="italic">danika</emphasis>, |
2718 | -<emphasis role="italic">jeremy</emphasis>, and <emphasis |
2719 | -role="italic">vincent</emphasis>, then certain network resources configured to |
2720 | -allow access by the <emphasis role="italic">qa</emphasis> group will |
2721 | -subsequently enable access by freda, danika, and rob, but not jeremy or |
2722 | -vincent. Since the user <emphasis role="italic">danika</emphasis> |
2723 | -belongs to both the <emphasis role="italic">qa</emphasis> and <emphasis |
2724 | +controlling access to such resources. For example, if a group <emphasis |
2725 | +role="italic">qa</emphasis> is defined and contains the users <emphasis |
2726 | +role="italic">freda</emphasis>, <emphasis role="italic">danika</emphasis>, and |
2727 | +<emphasis role="italic">rob</emphasis>, and a second group <emphasis |
2728 | +role="italic">support</emphasis> is defined and consists of users <emphasis |
2729 | +role="italic">danika</emphasis>, <emphasis role="italic">jeremy</emphasis>, and |
2730 | +<emphasis role="italic">vincent</emphasis>, then certain network resources |
2731 | +configured to allow access by the <emphasis role="italic">qa</emphasis> group |
2732 | +will subsequently enable access by freda, danika, and rob, but not jeremy or |
2733 | +vincent. Since the user <emphasis role="italic">danika</emphasis> belongs to |
2734 | +both the <emphasis role="italic">qa</emphasis> and <emphasis |
2735 | role="italic">support</emphasis> groups, she will be able to access resources |
2736 | configured for access by both groups, whereas all other users will have only |
2737 | access to resources explicitly allowing the group they are part of. |
2738 | </para> |
2739 | |
2740 | - |
2741 | <para> |
2742 | -By default Samba looks for the local system groups defined in |
2743 | -<filename>/etc/group</filename> to determine which users belong to which |
2744 | -groups. For more information on adding and removing users from groups see |
2745 | -<ulink type="help" url="help:/kubuntu/basics/"> Basics</ulink>. |
2746 | +By default, <application>Samba</application> looks for the local system groups |
2747 | +defined in <filename>/etc/group</filename> to determine which users belong to |
2748 | +which groups. For more information on adding and removing users from groups, |
2749 | +see <ulink type="help" url="help:/kubuntu/basics/"> Basics</ulink>. |
2750 | </para> |
2751 | |
2752 | <para> |
2753 | -When defining groups in the Samba configuration file, |
2754 | -<filename>/etc/samba/smb.conf</filename>, the recognized syntax |
2755 | -is to preface the group name with an "@" symbol. For example, to define a group |
2756 | -named <emphasis role="italic">sysadmin</emphasis> in a certain section of the |
2757 | +When defining groups in the <application>Samba</application> configuration |
2758 | +file, <filename>/etc/samba/smb.conf</filename>, the recognized syntax is to |
2759 | +preface the group name with an "@" symbol. For example, to define a group named |
2760 | +<emphasis role="italic">sysadmin</emphasis> in a certain section of the |
2761 | <filename>/etc/samba/smb.conf</filename>, the group name would be entered as |
2762 | <emphasis role="bold">@sysadmin</emphasis>. |
2763 | </para> |
2764 | @@ -466,19 +497,19 @@ |
2765 | <title>File Permissions</title> |
2766 | |
2767 | <para> |
2768 | -File Permissions define the explicit rights a computer or user has to a |
2769 | -particular directory, file, or set of files. Such permissions may be defined by |
2770 | +File permissions define the explicit rights a computer or user has to a |
2771 | +particular directory, file, or set of files. Such permissions may be defined by |
2772 | editing the <filename>/etc/samba/smb.conf</filename> file and specifying the |
2773 | explicit permissions of a defined file share. |
2774 | </para> |
2775 | |
2776 | <para> |
2777 | -For example, for a defined Samba share called <emphasis>share</emphasis> and |
2778 | -the need to give <emphasis role="italic">read-only</emphasis> permissions to the |
2779 | -group of users known as <emphasis role="italic">qa</emphasis>, while allowing |
2780 | -write permissions to the share by the group called |
2781 | -<emphasis role="italic">sysadmin</emphasis> and the user named <emphasis |
2782 | -role="italic">vincent</emphasis>, then the |
2783 | +For example, for a defined <application>Samba</application> share called |
2784 | +<emphasis>share</emphasis> and the need to give <emphasis |
2785 | +role="italic">read-only</emphasis> permissions to the group of users known as |
2786 | +<emphasis role="italic">qa</emphasis>, while allowing write permissions to the |
2787 | +share by the group called <emphasis role="italic">sysadmin</emphasis> and the |
2788 | +user named <emphasis role="italic">vincent</emphasis>, then the |
2789 | <filename>/etc/samba/smb.conf</filename> file could be edited to add the |
2790 | following entries under the <emphasis>[share]</emphasis> entry: |
2791 | </para> |
2792 | @@ -489,11 +520,11 @@ |
2793 | </programlisting> |
2794 | |
2795 | <para> |
2796 | -Another possible Samba permission is to declare |
2797 | -<emphasis>administrative</emphasis> permissions to a particular shared resource. |
2798 | -Users having administrative permissions may read, write, or modify any |
2799 | -information contained in the resource where the user has been given explicit |
2800 | -administrative permissions. |
2801 | +Another possible <application>Samba</application> permission is to declare |
2802 | +<emphasis>administrative</emphasis> permissions to a particular shared |
2803 | +resource. Users having administrative permissions may read, write, or modify |
2804 | +any information contained in the resource where they have been given |
2805 | +explicit administrative permissions. |
2806 | </para> |
2807 | |
2808 | <para> |
2809 | @@ -508,7 +539,8 @@ |
2810 | </programlisting> |
2811 | |
2812 | <para> |
2813 | -After editing <filename>/etc/samba/smb.conf</filename>, restart Samba for the changes to take effect: |
2814 | +After editing <filename>/etc/samba/smb.conf</filename>, restart |
2815 | +<application>Samba</application> for the changes to take effect: |
2816 | </para> |
2817 | |
2818 | <screen> |
2819 | @@ -518,21 +550,25 @@ |
2820 | <note> |
2821 | <para> |
2822 | For the <emphasis>read list</emphasis> and <emphasis>write list</emphasis> to |
2823 | -work the Samba security mode must <emphasis>not</emphasis> be set to <emphasis |
2824 | -role="italic">security = share</emphasis> |
2825 | +work, the <application>Samba</application> security mode must |
2826 | +<emphasis>not</emphasis> be set to <emphasis role="italic">security = |
2827 | +share</emphasis>. |
2828 | </para> |
2829 | </note> |
2830 | |
2831 | <para> |
2832 | -Now that Samba has been configured to limit which groups have access to the |
2833 | -shared directory, the filesystem permissions need to be updated. |
2834 | +Now that <application>Samba</application> has been configured to limit which |
2835 | +groups have access to the shared directory, the filesystem permissions need to |
2836 | +be updated. |
2837 | </para> |
2838 | |
2839 | <para> |
2840 | -Traditional Linux file permissions do not map well to Windows NT Access Control |
2841 | -Lists (ACLs). Fortunately POSIX ACLs are available on &kubuntu; servers |
2842 | -providing more fine grained control. For example, to enable ACLs on |
2843 | -<filename>/srv</filename> an EXT3 filesystem, edit |
2844 | +Traditional <trademark>Linux</trademark> file permissions do not map well to |
2845 | +<trademark class='registered'>Windows NT Access Control Lists</trademark> |
2846 | +(<acronym>ACL</acronym>s). Fortunately <trademark>POSIX</trademark> |
2847 | +<acronym>ACL</acronym>s are available on &kubuntu; servers providing more |
2848 | +fine-grained control. For example, to enable <acronym>ACL</acronym>s on |
2849 | +<filename>/srv</filename> an <trademark>EXT3</trademark> filesystem, edit |
2850 | <filename>/etc/fstab</filename> adding the <emphasis>acl</emphasis> option: |
2851 | </para> |
2852 | |
2853 | @@ -551,18 +587,20 @@ |
2854 | |
2855 | <note> |
2856 | <para> |
2857 | -The above example assumes <filename>/srv</filename> on a separate partition. If <filename>/srv</filename>, |
2858 | -or wherever the share path is configured, is part of the <filename>/</filename> |
2859 | -partition, a reboot may be required. |
2860 | +The above example assumes <filename>/srv</filename> is on a separate partition. |
2861 | +If <filename>/srv</filename> — or wherever the share path is configured |
2862 | +— is part of the <filename>/</filename> partition, a reboot may be |
2863 | +required. |
2864 | </para> |
2865 | </note> |
2866 | |
2867 | <para> |
2868 | -To match the Samba configuration above, the <emphasis>sysadmin</emphasis> group |
2869 | -will be given read, write, and execute permissions to |
2870 | -<filename>/srv/samba/share</filename>, the <emphasis>qa</emphasis> group will be |
2871 | -given read and execute permissions, and the files will be owned by the username |
2872 | -<emphasis>melissa</emphasis>. Enter the following in a terminal: |
2873 | +To match the <application>Samba</application> configuration above, the |
2874 | +<emphasis>sysadmin</emphasis> group will be given read, write, and execute |
2875 | +permissions to <filename>/srv/samba/share</filename>, the |
2876 | +<emphasis>qa</emphasis> group will be given read and execute permissions, and |
2877 | +the files will be owned by the username <emphasis>melissa</emphasis>. Enter the |
2878 | +following in a terminal: |
2879 | </para> |
2880 | |
2881 | <screen> |
2882 | @@ -575,15 +613,16 @@ |
2883 | <para> |
2884 | The <application>setfacl</application> command above gives |
2885 | <emphasis>execute</emphasis> permissions to all files in the |
2886 | -<filename>/srv/samba/share</filename> directory, which may or may not be |
2887 | +<filename>/srv/samba/share</filename> directory, which may or may not be |
2888 | desirable. |
2889 | </para> |
2890 | </note> |
2891 | |
2892 | <para> |
2893 | -A Windows client will show that the new file permissions are implemented. See |
2894 | -the <application>acl</application> and <application>setfacl</application> man |
2895 | -pages for more information on POSIX ACLs. |
2896 | +A <trademark class='registered'>Windows</trademark> client will show that the |
2897 | +new file permissions are implemented. See the <application>acl</application> |
2898 | +and <application>setfacl</application> man pages for more information on |
2899 | +<trademark>POSIX</trademark> <acronym>ACL</acronym>s. |
2900 | </para> |
2901 | |
2902 | </sect3> |
2903 | @@ -593,16 +632,19 @@ |
2904 | |
2905 | <para> |
2906 | &kubuntu; comes with the <application>AppArmor</application> security module, |
2907 | -which provides mandatory access controls. The default AppArmor profile for Samba |
2908 | -will need to be adapted to the proper configuration. For more details on using |
2909 | -AppArmor, please refer to the<ulink |
2910 | -url="https://help.ubuntu.com/community/AppArmor"> wiki</ulink> |
2911 | +which provides mandatory access controls. The default |
2912 | +<application>AppArmor</application> profile for |
2913 | +<application>Samba</application> will need to be adapted to the proper |
2914 | +configuration. For more details on using <application>AppArmor</application>, |
2915 | +please refer to the <ulink url="https://help.ubuntu.com/community/AppArmor"> |
2916 | +wiki</ulink>. |
2917 | </para> |
2918 | |
2919 | <para> |
2920 | -There are default AppArmor profiles for <filename>/usr/sbin/smbd</filename> and |
2921 | -<filename>/usr/sbin/nmbd</filename>, the Samba daemon binaries, as part of the |
2922 | -<application>apparmor-profiles</application> packages. To install the package, |
2923 | +There are default <application>AppArmor</application> profiles for |
2924 | +<filename>/usr/sbin/smbd</filename> and <filename>/usr/sbin/nmbd</filename>, |
2925 | +the <application>Samba</application> daemon binaries, as part of the |
2926 | +<application>apparmor-profiles</application> packages. To install the package |
2927 | from a terminal prompt, enter: |
2928 | </para> |
2929 | |
2930 | @@ -619,10 +661,11 @@ |
2931 | <para> |
2932 | By default the profiles for <application>smbd</application> and |
2933 | <application>nmbd</application> are in <emphasis>complain</emphasis> mode, |
2934 | -allowing Samba to work without modifying the profile, and only logging errors. |
2935 | -To place the <application>smbd</application> profile into |
2936 | -<emphasis>enforce</emphasis> mode, and have Samba work as expected, the profile |
2937 | -will need to be modified to reflect any directories that are shared. |
2938 | +allowing <application>Samba</application> to work without modifying the |
2939 | +profile, and only logging errors. To place the <application>smbd</application> |
2940 | +profile into <emphasis>enforce</emphasis> mode and have |
2941 | +<application>Samba</application> work as expected, the profile will need to be |
2942 | +modified to reflect any directories that are shared. |
2943 | </para> |
2944 | |
2945 | <para> |
2946 | @@ -636,7 +679,7 @@ |
2947 | </programlisting> |
2948 | |
2949 | <para> |
2950 | -Now place the profile into <emphasis>enforce</emphasis> and reload it: |
2951 | +Now place the profile into <emphasis>enforce</emphasis> mode and reload it: |
2952 | </para> |
2953 | |
2954 | <screen> |
2955 | @@ -648,8 +691,8 @@ |
2956 | It is now possible to read, write, and execute files in the shared directory as |
2957 | normal, and the <application>smbd</application> binary will have access to only |
2958 | the configured files and directories. Be sure to add entries for each directory |
2959 | -that Samba is configured to share. Any errors will be logged to |
2960 | -<filename>/var/log/syslog</filename>. |
2961 | +that <application>Samba</application> is configured to share. Any errors will |
2962 | +be logged to <filename>/var/log/syslog</filename>. |
2963 | </para> |
2964 | |
2965 | </sect2> |
2966 | @@ -659,34 +702,38 @@ |
2967 | <itemizedlist> |
2968 | <listitem> |
2969 | <para> |
2970 | -For in depth Samba configurations, see the |
2971 | -<ulink url="http://samba.org/samba/docs/man/Samba-HOWTO-Collection/">Samba HOWTO Collection</ulink> |
2972 | +For in depth <application>Samba</application> configurations, see the |
2973 | +<ulink url="http://samba.org/samba/docs/man/Samba-HOWTO-Collection/"> |
2974 | +<application>Samba</application> HOWTO Collection</ulink>. |
2975 | </para> |
2976 | </listitem> |
2977 | <listitem> |
2978 | <para> |
2979 | -The guide is also available in |
2980 | -<ulink url="http://www.amazon.com/exec/obidos/tg/detail/-/0131882228">printed format</ulink>. |
2981 | +The guide is also available in <ulink |
2982 | +url="http://www.amazon.com/exec/obidos/tg/detail/-/0131882228">printed |
2983 | +format</ulink>. |
2984 | </para> |
2985 | </listitem> |
2986 | <listitem> |
2987 | <para> |
2988 | O'Reilly's <ulink url="http://www.oreilly.com/catalog/9780596007690/">Using |
2989 | -Samba</ulink> is also a good reference. |
2990 | +<application>Samba</application></ulink> is also a good reference. |
2991 | </para> |
2992 | </listitem> |
2993 | <listitem> |
2994 | <para> |
2995 | <ulink |
2996 | url="http://samba.org/samba/docs/man/Samba-HOWTO-Collection/securing-samba.html" |
2997 | ->Chapter 18</ulink> of the Samba HOWTO Collection is devoted to security. |
2998 | +>Chapter 18</ulink> of the <application>Samba</application> HOWTO Collection is |
2999 | +devoted to security. |
3000 | </para> |
3001 | </listitem> |
3002 | <listitem> |
3003 | <para> |
3004 | -For more information on Samba and ACLs, see the |
3005 | -<ulink url="http://samba.org/samba/docs/man/Samba-HOWTO-Collection/AccessControls.html#id397568">Samba ACLs page |
3006 | -</ulink>. |
3007 | +For more information on <application>Samba</application> and ACLs, see the |
3008 | +<ulink |
3009 | +url="http://samba.org/samba/docs/man/Samba-HOWTO-Collection/AccessControls.html#id397568"> |
3010 | +<application>Samba</application> <acronym>ACL</acronym>s page</ulink>. |
3011 | </para> |
3012 | </listitem> |
3013 | </itemizedlist> |
3014 | @@ -697,27 +744,31 @@ |
3015 | <title>Samba as a Domain Controller</title> |
3016 | |
3017 | <para> |
3018 | -Although it cannot act as an Active Directory Primary Domain Controller (PDC), a |
3019 | -Samba server can be configured to appear as a Windows NT4-style domain |
3020 | -controller. A major advantage of this configuration is the ability to |
3021 | -centralize user and machine credentials. Samba can also use multiple backends |
3022 | -to store the user information. |
3023 | +Although it cannot act as an <trademark class='registered'>Active Directory |
3024 | +Primary Domain Controller</trademark> (<acronym>PDC</acronym>), a |
3025 | +<application>Samba</application> server can be configured to appear as a |
3026 | +<trademark class='registered'>Windows NT</trademark>4-style domain controller. |
3027 | +A major advantage of this configuration is the ability to centralize user and |
3028 | +machine credentials. <application>Samba</application> can also use multiple |
3029 | +backends to store the user information. |
3030 | </para> |
3031 | |
3032 | <sect2 id="samba-pdc-smbpasswd"> |
3033 | <title>Primary Domain Controller</title> |
3034 | |
3035 | <para> |
3036 | -This section covers configuring Samba as a Primary Domain Controller (PDC) using |
3037 | -the default smbpasswd backend. |
3038 | +This section covers configuring <application>Samba</application> as a Primary |
3039 | +Domain Controller (<acronym>PDC</acronym>) using the default |
3040 | +<application>smbpasswd</application> backend. |
3041 | </para> |
3042 | |
3043 | <procedure> |
3044 | <step> |
3045 | |
3046 | <para> |
3047 | -Install Samba and <application>libpam-smbpass</application> to sync the user |
3048 | -accounts, by entering the following in a terminal prompt: |
3049 | +Install <application>Samba</application> and |
3050 | +<application>libpam-smbpass</application> to sync the user accounts, by |
3051 | +entering the following in a terminal prompt: |
3052 | </para> |
3053 | |
3054 | <screen> |
3055 | @@ -728,10 +779,10 @@ |
3056 | <step> |
3057 | |
3058 | <para> |
3059 | -Next, configure Samba by editing <filename>/etc/samba/smb.conf</filename>. The |
3060 | -<emphasis>security</emphasis> mode should be set to <emphasis |
3061 | -role="italic">user</emphasis>, and the <emphasis>workgroup</emphasis> should |
3062 | -relate to the organization properly: |
3063 | +Next, configure <application>Samba</application> by editing |
3064 | +<filename>/etc/samba/smb.conf</filename>. The <emphasis>security</emphasis> |
3065 | +mode should be set to <emphasis role="italic">user</emphasis>, and the |
3066 | +<emphasis>workgroup</emphasis> should relate to the organization properly: |
3067 | </para> |
3068 | |
3069 | <programlisting> |
3070 | @@ -744,7 +795,8 @@ |
3071 | <step> |
3072 | |
3073 | <para> |
3074 | -In the commented <quote>Domains</quote> section, add or uncomment the following: |
3075 | +In the commented <quote>Domains</quote> section, add or uncomment the |
3076 | +following: |
3077 | </para> |
3078 | |
3079 | <programlisting> |
3080 | @@ -753,22 +805,23 @@ |
3081 | logon drive = H: |
3082 | logon home = \\%N\%U |
3083 | logon script = logon.cmd |
3084 | -add machine script = sudo /usr/sbin/useradd -N -g machines -c Machine -d /var/lib/samba -s /bin/false %u |
3085 | +add machine script = sudo /usr/sbin/useradd -N -g machines -c Machine -d |
3086 | +/var/lib/samba -s /bin/false %u |
3087 | </programlisting> |
3088 | |
3089 | <itemizedlist> |
3090 | <listitem> |
3091 | <para> |
3092 | -<emphasis>domain logons:</emphasis> provides the netlogon service causing Samba |
3093 | -to act as a domain controller. |
3094 | +<emphasis>domain logons:</emphasis> provides the netlogon service causing |
3095 | +<application>Samba</application> to act as a domain controller. |
3096 | </para> |
3097 | </listitem> |
3098 | <listitem> |
3099 | <para> |
3100 | -<emphasis>logon path:</emphasis> places the user's Windows profile into their |
3101 | -home directory. It is also possible to configure a |
3102 | -<emphasis>[profiles]</emphasis> share placing all profiles under a single |
3103 | -directory. |
3104 | +<emphasis>logon path:</emphasis> places the user's <trademark |
3105 | +class='registered'>Windows</trademark> profile into their home directory. It is |
3106 | +also possible to configure a <emphasis>[profiles]</emphasis> share placing all |
3107 | +profiles under a single directory. |
3108 | </para> |
3109 | </listitem> |
3110 | <listitem> |
3111 | @@ -784,20 +837,20 @@ |
3112 | <listitem> |
3113 | <para> |
3114 | <emphasis>logon script:</emphasis> determines the script to be run locally once |
3115 | -a user has logged in. The script needs to be placed in the |
3116 | -<emphasis>[netlogon]</emphasis> share. |
3117 | +a user has logged in. The script needs to be placed in the |
3118 | +<emphasis>[netlogon]</emphasis> share. |
3119 | </para> |
3120 | </listitem> |
3121 | <listitem> |
3122 | <para> |
3123 | -<emphasis>add machine script:</emphasis> a script that will automatically create |
3124 | -the <emphasis>Machine Trust Account</emphasis> needed for a workstation to join |
3125 | -the domain. |
3126 | +<emphasis>add machine script:</emphasis> a script that will automatically |
3127 | +create the <emphasis>Machine Trust Account</emphasis> needed for a workstation |
3128 | +to join the domain. |
3129 | </para> |
3130 | <para> |
3131 | -In this example, the <emphasis>machines</emphasis> group will need to be created |
3132 | -using the <application>addgroup</application> utility. See <ulink type="help" |
3133 | -url="help:/kubuntu/basics/"> Basics</ulink> for details. |
3134 | +In this example, the <emphasis>machines</emphasis> group will need to be |
3135 | +created using the <application>addgroup</application> utility. See <ulink |
3136 | +type="help" url="help:/kubuntu/basics/"> Basics</ulink> for details. |
3137 | </para> |
3138 | </listitem> |
3139 | </itemizedlist> |
3140 | @@ -833,7 +886,7 @@ |
3141 | |
3142 | <para> |
3143 | When configured as a domain controller, a <emphasis>[netlogon]</emphasis> share |
3144 | -needs to be configured. To enable the share, uncomment: |
3145 | +needs to be configured. To enable the share, uncomment: |
3146 | </para> |
3147 | |
3148 | <programlisting> |
3149 | @@ -849,7 +902,7 @@ |
3150 | <para> |
3151 | The original <emphasis>netlogon</emphasis> share path is |
3152 | <filename>/home/samba/netlogon</filename>, but according to the Filesystem |
3153 | -Hierarchy Standard (FHS), <ulink |
3154 | +Hierarchy Standard (<acronym>FHS</acronym>), <ulink |
3155 | url="http://www.pathname.com/fhs/pub/fhs-2.3. |
3156 | html#SRVDATAFORSERVICESPROVIDEDBYSYSTEM">/srv</ulink> is the correct location |
3157 | for site-specific data provided by the system. |
3158 | @@ -860,7 +913,7 @@ |
3159 | <step> |
3160 | |
3161 | <para> |
3162 | -Now create the <filename role="directory">netlogon</filename> directory, and an |
3163 | +Now create the <filename role="directory">netlogon</filename> directory and an |
3164 | empty (for now) <filename>logon.cmd</filename> script file: |
3165 | </para> |
3166 | |
3167 | @@ -870,8 +923,9 @@ |
3168 | </screen> |
3169 | |
3170 | <para> |
3171 | -Any normal Windows logon script commands can be entered in |
3172 | -<filename>logon.cmd</filename> to customize the client's environment. |
3173 | +Any normal <trademark class='registered'>Windows</trademark> logon script |
3174 | +commands can be entered in <filename>logon.cmd</filename> to customize the |
3175 | +client's environment. |
3176 | </para> |
3177 | |
3178 | </step> |
3179 | @@ -879,9 +933,9 @@ |
3180 | |
3181 | <para> |
3182 | With <emphasis>root</emphasis> being disabled by default, in order to join a |
3183 | -workstation to the domain, a system group must be mapped to the Windows |
3184 | -<emphasis>Domain Admins</emphasis> group. Using the |
3185 | -<application>net</application> utility, from a terminal enter: |
3186 | +workstation to the domain, a system group must be mapped to the <trademark |
3187 | +class='registered'>Windows</trademark> <emphasis>Domain Admins</emphasis> |
3188 | +group. Using the <application>net</application> utility, from a terminal enter: |
3189 | </para> |
3190 | |
3191 | <screen> |
3192 | @@ -892,9 +946,9 @@ |
3193 | <note> |
3194 | <para> |
3195 | Change <emphasis role="italic">sysadmin</emphasis> to the preferred group. The |
3196 | -user used to join the domain needs to be a member of the |
3197 | +user used to join the domain needs to be a member of the |
3198 | <emphasis>sysadmin</emphasis> group, as well as a member of the system |
3199 | -<emphasis>admin</emphasis> group. The <emphasis>admin</emphasis> group allows |
3200 | +<emphasis>admin</emphasis> group. The <emphasis>admin</emphasis> group allows |
3201 | <application>sudo</application> use. |
3202 | </para> |
3203 | </note> |
3204 | @@ -903,7 +957,8 @@ |
3205 | <step> |
3206 | |
3207 | <para> |
3208 | -Finally, restart Samba to enable the new domain controller: |
3209 | +Finally, restart <application>Samba</application> to enable the new domain |
3210 | +controller: |
3211 | </para> |
3212 | |
3213 | <screen> |
3214 | @@ -914,8 +969,10 @@ |
3215 | <step> |
3216 | |
3217 | <para> |
3218 | -It is now possible to join Windows clients to the Domain in the same manner as |
3219 | -joining them to an NT4 domain running on a Windows server. |
3220 | +It is now possible to join <trademark class='registered'>Windows</trademark> |
3221 | +clients to the domain in the same manner as joining them to an <trademark |
3222 | +class='registered'>NT4</trademark> domain running on a <trademark |
3223 | +class='registered'>Windows</trademark> server. |
3224 | </para> |
3225 | |
3226 | </step> |
3227 | @@ -926,32 +983,36 @@ |
3228 | <title>Backup Domain Controller</title> |
3229 | |
3230 | <para> |
3231 | -With a Primary Domain Controller (PDC) on the network, it is best to have a |
3232 | -Backup Domain Controller (BDC) as well. This will allow clients to authenticate |
3233 | -in case the PDC becomes unavailable. |
3234 | +With a Primary Domain Controller (<acronym>PDC</acronym>) on the network, it is |
3235 | +best to have a Backup Domain Controller (<acronym>BDC</acronym>) as well. This |
3236 | +will allow clients to authenticate in case the <acronym>PDC</acronym> becomes |
3237 | +unavailable. |
3238 | </para> |
3239 | |
3240 | <para> |
3241 | -When configuring Samba as a BDC, there must be a way to sync account information |
3242 | -with the PDC. There are multiple ways of accomplishing this, such as |
3243 | +When configuring <application>Samba</application> as a <acronym>BDC</acronym>, |
3244 | +there must be a way to sync account information with the |
3245 | +<acronym>PDC</acronym>. There are multiple ways of accomplishing this, such as |
3246 | <application>scp</application>, <application>rsync</application>, or by using |
3247 | <application>LDAP</application> as the <emphasis>passdb backend</emphasis>. |
3248 | </para> |
3249 | |
3250 | <para> |
3251 | -Using LDAP is the most robust way to sync account information, because both |
3252 | -domain controllers can use the same information in real time. However, setting |
3253 | -up a LDAP server may be overly complicated for a small number of user and |
3254 | -computer accounts. See Samba<ulink |
3255 | -url="http://wiki.samba.org/index.php/Samba_&_LDAP"> LDAP</ulink> page for |
3256 | -details. |
3257 | +Using <application>LDAP</application> is the most robust way to sync account |
3258 | +information, because both domain controllers can use the same information in |
3259 | +real time. However, setting up an <application>LDAP</application> server may be |
3260 | +overly complicated for a small number of user and computer accounts. See |
3261 | +<application>Samba</application> <ulink |
3262 | +url="http://wiki.samba.org/index.php/Samba_&_LDAP"> |
3263 | +<application>LDAP</application></ulink> page for details. |
3264 | </para> |
3265 | |
3266 | <procedure> |
3267 | <step> |
3268 | |
3269 | <para> |
3270 | -First, install <application>samba</application> and <application>libpam-smbpass</application>. From a terminal enter: |
3271 | +First, install <application>samba</application> and |
3272 | +<application>libpam-smbpass</application>. From a terminal, enter: |
3273 | </para> |
3274 | |
3275 | <screen> |
3276 | @@ -976,7 +1037,7 @@ |
3277 | <step> |
3278 | |
3279 | <para> |
3280 | -In the commented <emphasis>Domains</emphasis> uncomment or add: |
3281 | +In the commented <emphasis>Domains</emphasis>, uncomment or add: |
3282 | </para> |
3283 | |
3284 | <programlisting> |
3285 | @@ -988,8 +1049,9 @@ |
3286 | <step> |
3287 | |
3288 | <para> |
3289 | -Make sure a user has rights to read the files in <filename>/var/lib/samba</filename>. For example, to allow users in the |
3290 | -<emphasis>admin</emphasis> group to <application>scp</application> the files, |
3291 | +Make sure a user has rights to read the files in |
3292 | +<filename>/var/lib/samba</filename>. For example, to allow users in the |
3293 | +<emphasis>admin</emphasis> group to <application>scp</application> the files, |
3294 | enter: |
3295 | </para> |
3296 | |
3297 | @@ -1002,7 +1064,7 @@ |
3298 | |
3299 | <para> |
3300 | Next, sync the user accounts, using <application>scp</application> to copy the |
3301 | -<filename>/var/lib/samba</filename> directory from the PDC: |
3302 | +<filename>/var/lib/samba</filename> directory from the <acronym>PDC</acronym>: |
3303 | </para> |
3304 | |
3305 | <screen> |
3306 | @@ -1012,7 +1074,8 @@ |
3307 | <note> |
3308 | <para> |
3309 | Replace <emphasis>username</emphasis> with a valid username and |
3310 | -<emphasis>pdc</emphasis> with the hostname or IP Address of the actual PDC. |
3311 | +<emphasis>pdc</emphasis> with the hostname or <acronym>IP</acronym> Address of |
3312 | +the actual <acronym>PDC</acronym>. |
3313 | </para> |
3314 | </note> |
3315 | |
3316 | @@ -1031,16 +1094,19 @@ |
3317 | </procedure> |
3318 | |
3319 | <para> |
3320 | -Test that the Backup Domain controller is working by stopping the Samba daemon |
3321 | -on the PDC, then trying to login to a Windows client joined to the domain. |
3322 | +Test that the Backup Domain controller is working by stopping the |
3323 | +<application>Samba</application> daemon on the <application>PDC</application>, |
3324 | +then trying to login to a <trademark class='registered'>Windows</trademark> |
3325 | +client joined to the domain. |
3326 | </para> |
3327 | |
3328 | <para> |
3329 | -If the <emphasis>logon home</emphasis> option has been configured as a directory |
3330 | -on the PDC, and the PDC becomes unavailable, access to the user's |
3331 | -<emphasis>Home</emphasis> drive will also be unavailable. For this reason, |
3332 | -it is best to configure the <emphasis>logon home</emphasis> to reside on a |
3333 | -separate file server from the PDC and BDC. |
3334 | +If the <emphasis>logon home</emphasis> option has been configured as a |
3335 | +directory on the <acronym>PDC</acronym>, and the <acronym>PDC</acronym> becomes |
3336 | +unavailable, access to the user's <emphasis>Home</emphasis> drive will also be |
3337 | +unavailable. For this reason, it is best to configure the <emphasis>logon |
3338 | +home</emphasis> to reside on a separate file server from the |
3339 | +<acronym>PDC</acronym> and <acronym>BDC</acronym>. |
3340 | </para> |
3341 | |
3342 | </sect2> |
3343 | @@ -1051,36 +1117,38 @@ |
3344 | <itemizedlist> |
3345 | <listitem> |
3346 | <para> |
3347 | -For in depth Samba configurations see the |
3348 | -<ulink url="http://samba.org/samba/docs/man/Samba-HOWTO-Collection/">Samba HOWTO Collection</ulink> |
3349 | +For indepth <application>Samba</application> configurations, see the <ulink |
3350 | +url="http://samba.org/samba/docs/man/Samba-HOWTO-Collection/"> |
3351 | +<application>Samba</application> HOWTO Collection</ulink>. |
3352 | </para> |
3353 | </listitem> |
3354 | <listitem> |
3355 | <para> |
3356 | -The guide is also available in |
3357 | -<ulink url="http://www.amazon.com/exec/obidos/tg/detail/-/0131882228">printed format</ulink>. |
3358 | +The guide is also available in <ulink |
3359 | +url="http://www.amazon.com/exec/obidos/tg/detail/-/0131882228">printed format |
3360 | +</ulink>. |
3361 | </para> |
3362 | </listitem> |
3363 | <listitem> |
3364 | <para> |
3365 | O'Reilly's <ulink url="http://www.oreilly.com/catalog/9780596007690/">Using |
3366 | -Samba</ulink> is also a good reference. |
3367 | +<application>Samba</application></ulink> is also a good reference. |
3368 | </para> |
3369 | </listitem> |
3370 | <listitem> |
3371 | <para> |
3372 | <ulink |
3373 | url="http://samba.org/samba/docs/man/Samba-HOWTO-Collection/samba-pdc.html"> |
3374 | -Chapter 4</ulink> of the Samba HOWTO Collection explains setting up a Primary |
3375 | -Domain Controller. |
3376 | +Chapter 4</ulink> of the <application>Samba</application> HOWTO Collection |
3377 | +explains setting up a Primary Domain Controller. |
3378 | </para> |
3379 | </listitem> |
3380 | <listitem> |
3381 | <para> |
3382 | <ulink |
3383 | url="http://us3.samba.org/samba/docs/man/Samba-HOWTO-Collection/samba-bdc.html"> |
3384 | -Chapter 5</ulink> of the Samba HOWTO Collection explains setting up a Backup |
3385 | -Domain Controller. |
3386 | +Chapter 5</ulink> of the <application>Samba</application> HOWTO Collection |
3387 | +explains setting up a Backup Domain Controller. |
3388 | </para> |
3389 | </listitem> |
3390 | </itemizedlist> |
3391 | @@ -1095,14 +1163,16 @@ |
3392 | <title>Accessing a Samba Share</title> |
3393 | |
3394 | <para> |
3395 | -Another use for Samba is to integrate into an existing Windows network. Once |
3396 | -part of an Active Directory (AD) domain, Samba can provide file and print |
3397 | -services to AD users. |
3398 | +Another use for <application>Samba</application> is to integrate into an |
3399 | +existing <trademark class='registered'>Windows</trademark> network. Once part |
3400 | +of an <trademark class='registered'>Active Directory</trademark> |
3401 | +(<acronym>AD</acronym>) domain, <application>Samba</application> can provide |
3402 | +file and print services to <acronym>AD</acronym> users. |
3403 | </para> |
3404 | |
3405 | <para> |
3406 | -The simplest way to join an AD domain is to use |
3407 | -<application>Likewise-open</application>. For detailed instructions, see <xref |
3408 | +The simplest way to join an <acronym>AD</acronym> domain is to use |
3409 | +<application>Likewise-open</application>. For detailed instructions, see <xref |
3410 | linkend="likewise-open"/>. |
3411 | </para> |
3412 | |
3413 | @@ -1115,13 +1185,15 @@ |
3414 | </screen> |
3415 | |
3416 | <para> |
3417 | -Since the <application>likewise-open</application> and <application>samba</application> packages use separate |
3418 | +Since the <application>likewise-open</application> and |
3419 | +<application>samba</application> packages use separate |
3420 | <filename>secrets.tdb</filename> files, a symlink must be created in <filename |
3421 | role="directory">/var/lib/samba</filename>: |
3422 | </para> |
3423 | |
3424 | <screen> |
3425 | -<command>sudo mv /var/lib/samba/secrets.tdb /var/lib/samba/secrets.tdb.orig</command> |
3426 | +<command>sudo mv /var/lib/samba/secrets.tdb /var/lib/samba/secrets.tdb.orig |
3427 | +</command> |
3428 | <command>sudo ln -s /etc/samba/secrets.tdb /var/lib/samba</command> |
3429 | </screen> |
3430 | |
3431 | @@ -1150,10 +1222,10 @@ |
3432 | |
3433 | <para> |
3434 | It should now be possible to access any <application>Samba</application> shares |
3435 | -from a Windows client. However, be sure to give the appropriate AD users or |
3436 | -groups access to the share directory. See <xref |
3437 | -linkend="samba-fileprint-security"/> for |
3438 | -more details. |
3439 | +from a <trademark class='registered'>Windows</trademark> client. However, be |
3440 | +sure to give the appropriate <acronym>AD</acronym> users or groups access to |
3441 | +the share directory. See <xref linkend="samba-fileprint-security"/> for more |
3442 | +details. |
3443 | </para> |
3444 | |
3445 | </sect2> |
3446 | @@ -1162,23 +1234,25 @@ |
3447 | <title>Accessing a Windows Share</title> |
3448 | |
3449 | <para> |
3450 | -Now that the Samba server is part of the Active Directory domain, any Windows |
3451 | -server shares can be accessed: |
3452 | +Now that the <application>Samba</application> server is part of the <trademark |
3453 | +class='registered'>Active Directory</trademark> domain, any <trademark |
3454 | +class='registered'>Windows</trademark> server shares can be accessed: |
3455 | </para> |
3456 | |
3457 | <itemizedlist> |
3458 | <listitem> |
3459 | |
3460 | <para> |
3461 | -To mount a Windows file share, enter the following in a terminal prompt: |
3462 | +To mount a <trademark class='registered'>Windows</trademark> file share, enter |
3463 | +the following in a terminal prompt: |
3464 | </para> |
3465 | <screen> |
3466 | <command>mount.cifs //fs01.example.com/share mount_point</command> |
3467 | </screen> |
3468 | |
3469 | <para> |
3470 | -It is also possible to access shares on computers not part of an AD domain, but |
3471 | -a username and password must be provided. |
3472 | +It is also possible to access shares on computers not part of an |
3473 | +<acronym>AD</acronym> domain, but a username and password must be provided. |
3474 | </para> |
3475 | |
3476 | </listitem> |
3477 | @@ -1186,7 +1260,7 @@ |
3478 | |
3479 | <para> |
3480 | To mount the share during boot, place an entry in |
3481 | -<filename>/etc/fstab</filename>, for example: |
3482 | +<filename>/etc/fstab</filename>. For example: |
3483 | </para> |
3484 | |
3485 | <programlisting> |
3486 | @@ -1197,9 +1271,10 @@ |
3487 | <listitem> |
3488 | |
3489 | <para> |
3490 | -Another way to copy files from a Windows server is to use the |
3491 | -<application>smbclient</application> utility. To list the files in a Windows |
3492 | -share: |
3493 | +Another way to copy files from a <trademark |
3494 | +class='registered'>Windows</trademark> server is to use the |
3495 | +<application>smbclient</application> utility. To list the files in a <trademark |
3496 | +class='registered'>Windows</trademark> share: |
3497 | </para> |
3498 | |
3499 | <screen> |
3500 | @@ -1229,11 +1304,13 @@ |
3501 | </para> |
3502 | |
3503 | <screen> |
3504 | -<command>smbclient //fs01.example.com/share -k -c "put /etc/hosts hosts"</command> |
3505 | +<command>smbclient //fs01.example.com/share -k -c "put /etc/hosts hosts" |
3506 | +</command> |
3507 | </screen> |
3508 | |
3509 | <para> |
3510 | -This will copy the <filename>/etc/hosts</filename> to <filename>//fs01.example.com/share/hosts</filename>. |
3511 | +This will copy the <filename>/etc/hosts</filename> to |
3512 | +<filename>//fs01.example.com/share/hosts</filename>. |
3513 | </para> |
3514 | |
3515 | </listitem> |
3516 | @@ -1241,10 +1318,11 @@ |
3517 | |
3518 | <para> |
3519 | The <emphasis>-c</emphasis> option used above allows execution of the |
3520 | -<application>smbclient</application> command all at once. This is useful for |
3521 | -scripting and minor file operations. To enter the <emphasis>smb: |
3522 | -\></emphasis> prompt, an FTP-like prompt where normal file and directory |
3523 | -commands can be executed, simply run the following in Konsole: |
3524 | +<application>smbclient</application> command all at once. This is useful for |
3525 | +scripting and minor file operations. To enter the <emphasis>smb: |
3526 | +\></emphasis> prompt, an <acronym>FTP</acronym>-like prompt where normal |
3527 | +file and directory commands can be executed, simply run the following in |
3528 | +<application>Konsole</application>: |
3529 | </para> |
3530 | |
3531 | <screen> |
3532 | @@ -1256,11 +1334,12 @@ |
3533 | |
3534 | <note> |
3535 | <para> |
3536 | -Replace all instances of <emphasis>fs01.example.com/share</emphasis>, <emphasis>//192.168.0.5/share</emphasis>, |
3537 | +Replace all instances of <emphasis>fs01.example.com/share</emphasis>, |
3538 | +<emphasis>//192.168.0.5/share</emphasis>, |
3539 | <emphasis>username=steve,password=secret</emphasis>, and |
3540 | -<emphasis>file.txt</emphasis> with the proper server IP, hostname, |
3541 | -share name, file name, and an actual username and password with rights to the |
3542 | -share. |
3543 | +<emphasis>file.txt</emphasis> with the proper server <acronym>IP</acronym>, |
3544 | +hostname, share name, file name, and an actual username and password with |
3545 | +rights to the share. |
3546 | </para> |
3547 | </note> |
3548 | |
3549 | @@ -1269,9 +1348,11 @@ |
3550 | <title>Resources</title> |
3551 | |
3552 | <para> |
3553 | -For more <application>smbclient</application> options see the man page: |
3554 | +For more <application>smbclient</application> options, see the man page: |
3555 | <command>man smbclient</command>, also available |
3556 | -<ulink url="http://manpages.ubuntu.com/manpages/jaunty/en/man1/smbclient.1.html">online</ulink>. |
3557 | +<ulink |
3558 | +url="http://manpages.ubuntu.com/manpages/jaunty/en/man1/smbclient.1.html"> |
3559 | +online</ulink>. |
3560 | </para> |
3561 | |
3562 | <para> |
3563 | @@ -1289,24 +1370,27 @@ |
3564 | |
3565 | <para> |
3566 | <application>Likewise Open</application> simplifies the necessary configuration |
3567 | -needed to authenticate a Linux machine to an Active Directory domain. Based on |
3568 | -<application>winbind</application>, the <application>likewise-open</application> |
3569 | -package takes the pain out of integrating &kubuntu; authentication into an |
3570 | -existing Windows network. |
3571 | +needed to authenticate a <trademark>Linux</trademark> machine to an <trademark |
3572 | +class='registered'>Active Directory</trademark> domain. Based on |
3573 | +<application>winbind</application>, the |
3574 | +<application>likewise-open</application> package takes the pain out of |
3575 | +integrating &kubuntu; authentication into an existing <trademark |
3576 | +class='registered'>Windows</trademark> network. |
3577 | </para> |
3578 | |
3579 | <sect2 id="likewise-open-install"> |
3580 | <title>Installation</title> |
3581 | |
3582 | <para> |
3583 | -There are two ways to use Likewise Open, |
3584 | +There are two ways to use Likewise Open: |
3585 | <application>likewise-open</application> the command line utility and |
3586 | -<application>likewise-open-gui</application>. This section focuses on the |
3587 | +<application>likewise-open-gui</application>. This section focuses on the |
3588 | command line utility. |
3589 | </para> |
3590 | |
3591 | <para> |
3592 | -To install the <application>likewise-open</application> package, open a terminal prompt and enter: |
3593 | +To install the <application>likewise-open</application> package, open a |
3594 | +terminal and enter: |
3595 | </para> |
3596 | |
3597 | <screen> |
3598 | @@ -1322,7 +1406,7 @@ |
3599 | </para> |
3600 | |
3601 | <para> |
3602 | -To install <application>Likewise Open 5.0</application> enter: |
3603 | +To install <application>Likewise Open 5.0</application>, enter: |
3604 | </para> |
3605 | |
3606 | <screen> |
3607 | @@ -1331,8 +1415,9 @@ |
3608 | |
3609 | <warning> |
3610 | <para> |
3611 | -Installing likewise-open5 over an existing likewise-open (4.1) installation will |
3612 | -replace it. The domain will have to be rejoined after install. |
3613 | +Installing <application>likewise-open5</application> over an existing |
3614 | +<application>likewise-open</application> (4.1) installation will replace it. |
3615 | +The domain will have to be rejoined after install. |
3616 | </para> |
3617 | </warning> |
3618 | |
3619 | @@ -1349,25 +1434,29 @@ |
3620 | <itemizedlist> |
3621 | <listitem> |
3622 | <para> |
3623 | -Access to an Active Directory user with appropriate rights to join the domain. |
3624 | -</para> |
3625 | -</listitem> |
3626 | -<listitem> |
3627 | -<para> |
3628 | -The <emphasis>Fully Qualified Domain Name</emphasis> (FQDN) of the domain |
3629 | -being joined. If the AD domain does not match a valid domain such as <emphasis |
3630 | -role="italic">example.com</emphasis>, it is likely that it is in the form of |
3631 | -<emphasis>domainname.local</emphasis>. |
3632 | -</para> |
3633 | -</listitem> |
3634 | -<listitem> |
3635 | -<para> |
3636 | -DNS for the domain set up properly. In a production AD environment, this |
3637 | -is typically the case. Proper Microsoft DNS is needed so that client |
3638 | -workstations can determine that the Active Directory domain is available. |
3639 | -</para> |
3640 | -<para> |
3641 | -If there is not a Windows DNS server on the network, see <xref |
3642 | +Access to an <trademark class='registered'>Active Directory</trademark> user |
3643 | +with appropriate rights to join the domain. |
3644 | +</para> |
3645 | +</listitem> |
3646 | +<listitem> |
3647 | +<para> |
3648 | +The <emphasis>Fully Qualified Domain Name</emphasis> (<acronym>FQDN</acronym>) |
3649 | +of the domain being joined. If the <acronym>AD</acronym> domain does not match |
3650 | +a valid domain such as <emphasis role="italic">example.com</emphasis>, it is |
3651 | +likely that it is in the form of <emphasis>domainname.local</emphasis>. |
3652 | +</para> |
3653 | +</listitem> |
3654 | +<listitem> |
3655 | +<para> |
3656 | +<acronym>DNS</acronym> for the domain set up properly. In a production |
3657 | +<acronym>AD</acronym> environment, this is typically the case. Proper |
3658 | +<trademark class='registered'>Microsoft</trademark> <acronym>DNS</acronym> is |
3659 | +needed so that client workstations can determine that the <trademark |
3660 | +class='registered'>Active Directory</trademark> domain is available. |
3661 | +</para> |
3662 | +<para> |
3663 | +If there is not a <trademark class='registered'>Windows</trademark> |
3664 | +<acronym>DNS</acronym> server on the network, see <xref |
3665 | linkend="likewise-open-ms-dns"/> for details. |
3666 | </para> |
3667 | |
3668 | @@ -1390,22 +1479,23 @@ |
3669 | </note> |
3670 | |
3671 | <para> |
3672 | -There will be a prompt for the user's password. If all goes well, a |
3673 | +There will be a prompt for the user's password. If all goes well, a |
3674 | <emphasis>SUCCESS</emphasis> message should be printed to the console. |
3675 | </para> |
3676 | |
3677 | <note> |
3678 | <para> |
3679 | -After joining the domain, it is necessary to reboot before |
3680 | -attempting to authenticate against the domain. |
3681 | +After joining the domain, it is necessary to reboot before attempting to |
3682 | +authenticate against the domain. |
3683 | </para> |
3684 | </note> |
3685 | |
3686 | <para> |
3687 | -After successfully joining an &kubuntu; machine to an Active Directory domain, |
3688 | -any valid AD user can be used to authenticate. To login, the user name must be |
3689 | -entered as 'domain\username'. For example to ssh to a server joined to the |
3690 | -domain, enter: |
3691 | +After successfully joining an &kubuntu; machine to an <trademark |
3692 | +class='registered'>Active Directory</trademark> domain, any valid |
3693 | +<acronym>AD</acronym> user can be used to authenticate. To log in, the user |
3694 | +name must be entered as 'domain\username'. For example, to |
3695 | +<command>ssh</command> to a server joined to the domain, enter: |
3696 | </para> |
3697 | |
3698 | <screen> |
3699 | @@ -1414,14 +1504,15 @@ |
3700 | |
3701 | <note> |
3702 | <para> |
3703 | -If configuring a Desktop, the user name will need to be prefixed with <emphasis |
3704 | +If configuring a desktop, the user name will need to be prefixed with <emphasis |
3705 | role="italic">domain\</emphasis> in the graphical logon as well. |
3706 | </para> |
3707 | </note> |
3708 | |
3709 | <para> |
3710 | -To make likewise-open use a default domain, the following statement can be added |
3711 | -to <filename>/etc/samba/lwiauthd.conf</filename>: |
3712 | +To make <application>likewise-open</application> use a default domain, the |
3713 | +following statement can be added to |
3714 | +<filename>/etc/samba/lwiauthd.conf</filename>: |
3715 | </para> |
3716 | |
3717 | <programlisting> |
3718 | @@ -1439,14 +1530,14 @@ |
3719 | <note> |
3720 | <para> |
3721 | Once configured for a <emphasis>default domain</emphasis>, the <emphasis |
3722 | -role="italic">'domain\'</emphasis> is no longer required. Users can login using |
3723 | -only their username. |
3724 | +role="italic">'domain\'</emphasis> is no longer required. Users can log in |
3725 | +using only their username. |
3726 | </para> |
3727 | </note> |
3728 | |
3729 | <para> |
3730 | The <application>domainjoin-cli</application> utility can also be used to leave |
3731 | -the domain. From a terminal: |
3732 | +the domain. From a terminal: |
3733 | </para> |
3734 | |
3735 | <screen> |
3736 | @@ -1459,34 +1550,36 @@ |
3737 | |
3738 | <para> |
3739 | The <application>likewise-open</application> package comes with a few other |
3740 | -utilities that may be useful for gathering information about the Active |
3741 | -Directory environment. These utilities are used to join the machine to the |
3742 | -domain, and are the same as those available in the |
3743 | -<application>samba-common</application> and <application>winbind</application> |
3744 | -packages: |
3745 | +utilities that may be useful for gathering information about the <trademark |
3746 | +class='registered'>Active Directory</trademark> environment. These utilities |
3747 | +are used to join the machine to the domain, and are the same as those available |
3748 | +in the <application>samba-common</application> and |
3749 | +<application>winbind</application> packages: |
3750 | </para> |
3751 | |
3752 | <itemizedlist> |
3753 | <listitem> |
3754 | <para> |
3755 | -<application>lwinet</application>: Returns information about the network and the domain. |
3756 | -</para> |
3757 | -</listitem> |
3758 | -<listitem> |
3759 | -<para> |
3760 | -<application>lwimsg</application>: Allows interaction with the <application>likewise-winbindd</application> daemon. |
3761 | -</para> |
3762 | -</listitem> |
3763 | -<listitem> |
3764 | -<para> |
3765 | -<application>lwiinfo</application>: Displays information about various parts of |
3766 | -the Domain. |
3767 | +<application>lwinet</application>: Returns information about the network and |
3768 | +the domain. |
3769 | +</para> |
3770 | +</listitem> |
3771 | +<listitem> |
3772 | +<para> |
3773 | +<application>lwimsg</application>: Allows interaction with the |
3774 | +<application>likewise-winbindd</application> daemon. |
3775 | +</para> |
3776 | +</listitem> |
3777 | +<listitem> |
3778 | +<para> |
3779 | +<application>lwiinfo</application>: Displays information about various parts of |
3780 | +the domain. |
3781 | </para> |
3782 | </listitem> |
3783 | </itemizedlist> |
3784 | |
3785 | <para> |
3786 | -Please refer to each utility's man page specific for details. |
3787 | +Please refer to each utility's man page for details. |
3788 | </para> |
3789 | |
3790 | </sect2> |
3791 | @@ -1496,8 +1589,9 @@ |
3792 | <itemizedlist> |
3793 | <listitem> |
3794 | <para> |
3795 | -If the client has trouble joining the domain, check that the Microsoft DNS is |
3796 | -listed first in <filename>/etc/resolv.conf</filename>. |
3797 | +If the client has trouble joining the domain, check that the <trademark |
3798 | +class='registered'>Microsoft</trademark> <acronym>DNS</acronym> is listed first |
3799 | +in <filename>/etc/resolv.conf</filename>. |
3800 | For example: |
3801 | </para> |
3802 | |
3803 | @@ -1507,26 +1601,30 @@ |
3804 | </listitem> |
3805 | <listitem> |
3806 | <para> |
3807 | -For more information when joining a domain, use the <emphasis>--loglevel verbose</emphasis> or <emphasis>--advanced</emphasis> option of the |
3808 | +For more information when joining a domain, use the <emphasis>--loglevel |
3809 | +verbose</emphasis> or <emphasis>--advanced</emphasis> option of the |
3810 | <application>domainjoin-cli</application> utility: |
3811 | </para> |
3812 | |
3813 | <screen> |
3814 | -<command>sudo domainjoin-cli --loglevel verbose join example.com Administrator</command> |
3815 | +<command>sudo domainjoin-cli --loglevel verbose join example.com Administrator |
3816 | +</command> |
3817 | </screen> |
3818 | </listitem> |
3819 | <listitem> |
3820 | <para> |
3821 | -If an Active Directory user has trouble logging in, check the <filename>/var/log/auth.log</filename> for details. |
3822 | +If an <trademark class='registered'>Active Directory</trademark> user has |
3823 | +trouble logging in, check the <filename>/var/log/auth.log</filename> for |
3824 | +details. |
3825 | </para> |
3826 | </listitem> |
3827 | <listitem> |
3828 | <para> |
3829 | -When joining an &kubuntu; Desktop workstation to a domain, it may be necessary |
3830 | -to edit <filename>/etc/nsswitch.conf</filename> if the AD domain uses the |
3831 | -<emphasis role="italic">.local</emphasis> syntax. In order to join the domain, |
3832 | -the <emphasis>"mdns4"</emphasis> entry should be removed from the |
3833 | -<emphasis>hosts</emphasis> option. For example: |
3834 | +When joining a &kubuntu; Desktop workstation to a domain, it may be necessary |
3835 | +to edit <filename>/etc/nsswitch.conf</filename> if the <acronym>AD</acronym> |
3836 | +domain uses the <emphasis role="italic">.local</emphasis> syntax. In order to |
3837 | +join the domain, the <emphasis>"mdns4"</emphasis> entry should be removed from |
3838 | +the <emphasis>hosts</emphasis> option. For example: |
3839 | </para> |
3840 | |
3841 | <programlisting> |
3842 | @@ -1550,7 +1648,8 @@ |
3843 | </screen> |
3844 | |
3845 | <para> |
3846 | -It should now be possible to join the Active Directory domain. |
3847 | +It should now be possible to join the <trademark |
3848 | +class='registered'>Active Directory</trademark> domain. |
3849 | </para> |
3850 | </listitem> |
3851 | </itemizedlist> |
3852 | @@ -1560,9 +1659,10 @@ |
3853 | <title>Microsoft DNS</title> |
3854 | |
3855 | <para> |
3856 | -The following are instructions for installing DNS on an Active Directory domain |
3857 | -controller running Windows Server 2003, but the instructions should be similar |
3858 | -for other versions: |
3859 | +The following are instructions for installing <acronym>DNS</acronym> on an |
3860 | +<trademark class='registered'>Active Directory</trademark> domain controller |
3861 | +running <trademark class='registered'>Windows Server 2003</trademark>, but the |
3862 | +instructions should be similar for other versions: |
3863 | </para> |
3864 | |
3865 | <!-- Translators: please check http://www.microsoft.com/language/en/us/search.mspx to see how this string is translated in Windows to your language --> |
3866 | @@ -1577,41 +1677,62 @@ |
3867 | This will open the <application>Server Role Management</application> utility. |
3868 | </para> |
3869 | <orderedlist> |
3870 | -<listitem><para>Click <guilabel>Add or remove a role</guilabel></para></listitem> |
3871 | -<listitem><para>Click Next</para></listitem> |
3872 | -<listitem><para>Select "DNS Server"</para></listitem> |
3873 | -<listitem><para>Click Next</para></listitem> |
3874 | -<listitem><para>Click Next again to proceed </para></listitem> |
3875 | -<listitem><para>Select "Create a forward lookup zone" if it is not selected.</para></listitem> |
3876 | -<listitem><para>Click Next</para></listitem> |
3877 | -<listitem><para>Make sure "This server maintains the zone" is selected and click Next.</para></listitem> |
3878 | -<listitem><para>Enter the domain name and click Next</para></listitem> |
3879 | -<listitem><para>Click Next to "Allow only secure dynamic updates"</para></listitem> |
3880 | +<listitem><para><mousebutton>Click</mousebutton> <guilabel>Add or remove a |
3881 | +role</guilabel>.</para></listitem> |
3882 | +<listitem><para><mousebutton>Click</mousebutton> <guilabel>Next</guilabel>. |
3883 | +</para></listitem> |
3884 | +<listitem><para>Select "<acronym>DNS</acronym> Server".</para></listitem> |
3885 | +<listitem><para><mousebutton>Click</mousebutton> <guilabel>Next</guilabel>. |
3886 | +</para></listitem> |
3887 | +<listitem><para><mousebutton>Click</mousebutton> <guilabel>Next</guilabel> |
3888 | +again to proceed.</para></listitem> |
3889 | +<listitem><para>Select "Create a forward lookup zone" if it is not selected. |
3890 | +</para></listitem> |
3891 | +<listitem><para><mousebutton>Click</mousebutton> <guilabel>Next</guilabel>. |
3892 | +</para></listitem> |
3893 | +<listitem><para>Make sure "This server maintains the zone" is selected and |
3894 | +<mousebutton>click</mousebutton> <guilabel>Next</guilabel>.</para></listitem> |
3895 | +<listitem><para>Enter the domain name and <mousebutton>click</mousebutton> |
3896 | +<guilabel>Next</guilabel>.</para></listitem> |
3897 | +<listitem><para><mousebutton>Click</mousebutton> <guilabel>Next</guilabel> to |
3898 | +"Allow only secure dynamic updates".</para></listitem> |
3899 | <listitem> |
3900 | <para> |
3901 | -Enter the IP for DNS servers to forward queries to, or Select "No, it should not forward queries" and click Next. |
3902 | +Enter the <acronym>IP</acronym> for <acronym>DNS</acronym> servers to forward |
3903 | +queries to, or Select "No, it should not forward queries" and |
3904 | +<mousebutton>click</mousebutton> <guilabel>Next</guilabel>. |
3905 | </para> |
3906 | </listitem> |
3907 | -<listitem><para>Click Finish</para></listitem> |
3908 | -<listitem><para>Click Finish</para></listitem> |
3909 | +<listitem><para><mousebutton>Click</mousebutton> |
3910 | +<guilabel>Finish</guilabel></para></listitem> |
3911 | +<listitem><para><mousebutton>Click</mousebutton> |
3912 | +<guilabel>Finish</guilabel></para></listitem> |
3913 | </orderedlist> |
3914 | <para> |
3915 | -DNS is now installed and can be further configured using the <application>Microsoft Management Console</application> DNS snap-in. |
3916 | +<acronym>DNS</acronym> is now installed and can be further configured using the |
3917 | +<application>Microsoft Management Console</application> <acronym>DNS</acronym> |
3918 | +snap-in. |
3919 | </para> |
3920 | </listitem> |
3921 | <listitem> |
3922 | <para> |
3923 | -Next, configure the Server to use itself for DNS queries: |
3924 | +Next, configure the server to use itself for <acronym>DNS</acronym> queries: |
3925 | <orderedlist> |
3926 | -<listitem><para>Click Start</para></listitem> |
3927 | +<listitem><para><mousebutton>Click</mousebutton> <guilabel>Start</guilabel> |
3928 | +</para></listitem> |
3929 | <listitem><para>Control Panel</para></listitem> |
3930 | <listitem><para>Network Connections</para></listitem> |
3931 | -<listitem><para>Right Click "Local Area Connection"</para></listitem> |
3932 | -<listitem><para>Click Properties</para></listitem> |
3933 | -<listitem><para>Double click "Internet Protocol (TCP/IP)"</para></listitem> |
3934 | -<listitem><para>Enter the Server's IP Address as the "Preferred DNS server"</para></listitem> |
3935 | -<listitem><para>Click Ok</para></listitem> |
3936 | -<listitem><para>Click Ok again to save the settings</para></listitem> |
3937 | +<listitem><para><mousebutton>Right click</mousebutton> "Local Area Connection" |
3938 | +</para></listitem> |
3939 | +<listitem><para><mousebutton>Click</mousebutton> Properties</para></listitem> |
3940 | +<listitem><para><mousebutton>Double click</mousebutton> "Internet Protocol |
3941 | +(<acronym>TCP</acronym>/<acronym>IP</acronym>)"</para></listitem> |
3942 | +<listitem><para>Enter the server's <acronym>IP</acronym> address as the |
3943 | +"Preferred <acronym>DNS</acronym> server"</para></listitem> |
3944 | +<listitem><para><mousebutton>Click</mousebutton> <guibutton>Ok</guibutton> |
3945 | +</para></listitem> |
3946 | +<listitem><para><mousebutton>Click</mousebutton> <guibutton>Ok</guibutton> |
3947 | +again to save the settings</para></listitem> |
3948 | </orderedlist> |
3949 | </para> |
3950 | </listitem> |
3951 | @@ -1621,11 +1742,13 @@ |
3952 | <title>References</title> |
3953 | |
3954 | <para> |
3955 | -Please refer to the <ulink url="http://www.likewisesoftware.com/">Likewise</ulink> home page for further information. |
3956 | +Please refer to the <ulink url="http://www.likewisesoftware.com/">Likewise |
3957 | +</ulink> home page for further information. |
3958 | </para> |
3959 | |
3960 | <para> |
3961 | -For more <application>domainjoin-cli</application> options see the man page: <command>man domainjoin-cli</command>. |
3962 | +For more <application>domainjoin-cli</application> options, see the man page: |
3963 | +<command>man domainjoin-cli</command>. |
3964 | </para> |
3965 | |
3966 | </sect2> |
3967 | |
3968 | === modified file 'docs/video/C/video.xml' |
3969 | --- docs/video/C/video.xml 2011-09-15 06:32:00 +0000 |
3970 | +++ docs/video/C/video.xml 2012-03-22 19:19:20 +0000 |
3971 | @@ -21,14 +21,15 @@ |
3972 | <sect1 id="introduction"> |
3973 | <title>Introduction</title> |
3974 | <para> |
3975 | -&kubuntu; comes with a video player installed by default called |
3976 | -<application>Dragon Player</application>. It is a simple and lightweight video |
3977 | +&kubuntu; comes with a video player installed by default called |
3978 | +<application>Dragon Player</application>. It is a simple and light-weight video |
3979 | player that can play almost any video file (provided the necessary codecs are |
3980 | -installed). For video editing, the preferred choice is |
3981 | -<application>Kino</application>, a non-linear video editor. |
3982 | -<application>Kino</application> is not installed by default with &kubuntu;, but |
3983 | -it can be easily installed from the &kubuntu; Software Center: |
3984 | -(<application>Muon</application>). |
3985 | +installed). For video editing, the preferred choice is |
3986 | +<application>Kino</application> — a non-linear video editor. |
3987 | +<application>Kino</application> is not installed by default in &kubuntu;, but |
3988 | +can be easily installed from the &kubuntu; Software Center: |
3989 | +(<application>Muon</application>), which can be started by choosing |
3990 | +&menusysmuon;. |
3991 | </para> |
3992 | </sect1> |
3993 | |
3994 | @@ -41,16 +42,20 @@ |
3995 | |
3996 | <procedure> |
3997 | <title>Open Files From The File Manager</title> |
3998 | -<step><para>Open the <application>Dolphin</application> file manager.</para></step> |
3999 | +<step><para>Open the <application>Dolphin</application> file manager. |
4000 | +</para></step> |
4001 | <step><para>Navigate to the video file.</para></step> |
4002 | -<step><para>Click on the file name to open it with the default video player (<application>Dragon Player</application>).</para></step> |
4003 | +<step><para>Click on the file name to open it with the default video player |
4004 | +(<application>Dragon Player</application>).</para></step> |
4005 | </procedure> |
4006 | |
4007 | <procedure> |
4008 | <title>Open Files From Within Dragon Player</title> |
4009 | -<step><para>Open <application>Dragon Player</application>; &menudragon;</para></step> |
4010 | -<step><para>Click on the <guibutton>Play File</guibutton> button or press <keycombo><keycap>Ctrl</keycap><keycap>O</keycap></keycombo></para></step> |
4011 | -<step><para>Navigate to the selected video file, and click |
4012 | +<step><para>Open <application>Dragon Player</application>; &menudragon;</para> |
4013 | +</step> |
4014 | +<step><para>Click on the <guibutton>Play File</guibutton> button or press |
4015 | +<keycombo><keycap>Ctrl</keycap><keycap>O</keycap></keycombo></para></step> |
4016 | +<step><para>Navigate to the selected video file, and click |
4017 | <guibutton>Open</guibutton></para></step> |
4018 | </procedure> |
4019 | |
4020 | @@ -61,11 +66,11 @@ |
4021 | <title>Editing Videos</title> |
4022 | <para> |
4023 | Video editing in &kubuntu; can be done with an application called |
4024 | -<application>Kino</application> a non-linear video editor. |
4025 | +<application>Kino</application> — a non-linear video editor. |
4026 | <application>Kino</application> is not installed by default. It can be |
4027 | -installed using <application>Muon</application> by going |
4028 | -to &menusysmuon;.</para> |
4029 | -<para>Here's how to open and edit video files in |
4030 | +installed using <application>Muon</application> by going to &menusysmuon;. |
4031 | +</para> |
4032 | +<para>Here's how to open and edit video files in |
4033 | <application>Kino</application>: |
4034 | </para> |
4035 | |
4036 | @@ -84,11 +89,12 @@ |
4037 | <para>To trim a video to shorten it or to export different sections:</para> |
4038 | <procedure> |
4039 | <title>Trimming Videos</title> |
4040 | -<step><para>Once a video file has been imported into |
4041 | +<step><para>Once a video file has been imported into |
4042 | <application>Kino</application>, click on the <guibutton>Trim</guibutton> |
4043 | button.</para></step> |
4044 | -<step><para>A slider below the video preview can be used to specify the starting |
4045 | -(In Point) and the ending (Out Point) points of the trimmed video.</para></step> |
4046 | +<step><para>A slider below the video preview can be used to specify the |
4047 | +starting (In Point) and the ending (Out Point) points of the trimmed video. |
4048 | +</para></step> |
4049 | <step><para>Specify the starting and ending points by dragging each end of the |
4050 | slider.</para></step> |
4051 | <step><para>After the sliders have been positioned, press the |
4052 | @@ -98,21 +104,20 @@ |
4053 | |
4054 | <procedure> |
4055 | <title>Exporting videos</title> |
4056 | -<step><para>When the editing, trimming, etc. are complete, the video is ready |
4057 | -to be exported. To do this, click on the <guibutton>Export</guibutton> on the |
4058 | -right side of the window or go to |
4059 | -<menuchoice><guimenu>View</guimenu><guisubmenu>Export</guisubmenu></menuchoice |
4060 | ->.</para></step> |
4061 | +<step><para>When the editing, trimming, etc., are complete, the video is ready |
4062 | +to be exported. To do this, click on the <guibutton>Export</guibutton> button |
4063 | +on the right side of the window or go to <menuchoice><guimenu>View</guimenu> |
4064 | +<guisubmenu>Export</guisubmenu></menuchoice>.</para></step> |
4065 | <step><para>In the Export mode, the output mode can be specified for saving the |
4066 | -edited video. Exporting to a 'DV' file maintains the quality of the video (this |
4067 | -generally results in a large file).</para></step> |
4068 | +edited video. Exporting to a '<acronym>DV</acronym>' file maintains the quality |
4069 | +of the video (this generally results in a large file).</para></step> |
4070 | <step><para>To export the video to a common format such as |
4071 | <acronym>AVI</acronym>, select the 'Other' tab and specify the type of video to |
4072 | -export, the quality of the output video and the location where the |
4073 | -video should be saved.</para></step> |
4074 | +export, the quality of the output video and the location the video should be |
4075 | +saved to.</para></step> |
4076 | <step><para>When the settings have been customized, click on the |
4077 | -<guibutton>Export</guibutton> button to export the file. This may take some time |
4078 | -depending on the size of file, the format, the quality selected and other |
4079 | +<guibutton>Export</guibutton> button to export the file. This may take some |
4080 | +time depending on the size of file, the format, the quality selected, and other |
4081 | customization choices.</para></step> |
4082 | </procedure> |
4083 | </sect1> |
4084 | @@ -120,14 +125,15 @@ |
4085 | <sect1 id="video-codecs"> |
4086 | <title>Video Codecs</title> |
4087 | <para> |
4088 | -Codecs are software that allow different types of video/audio files to be |
4089 | -played. Some codecs are proprietary, meaning that a license is required to use |
4090 | -them. Some codecs are available under free licenses like GPL. |
4091 | +Codecs are software that allow different types of video/audio files to be |
4092 | +played. Some codecs are proprietary — meaning that a license is required |
4093 | +to use them. Some codecs are available under free licenses like the |
4094 | +<acronym>GPL</acronym>. |
4095 | </para> |
4096 | <para> |
4097 | &kubuntu; does not come pre-installed with codecs to play proprietary formats |
4098 | -like mp3, rm (Real Media) and others. The necessary codecs can be installed from |
4099 | -the repositories. |
4100 | +like mp3, rm (<trademark>Real Media</trademark>), and others. The necessary |
4101 | +codecs can be installed from the repositories. |
4102 | </para> |
4103 | <para> |
4104 | For more information on which formats are supported out of the box by &kubuntu; |