source: general/sysutils/dbus.xml@ d741dcb

10.0 10.1 11.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind ken/refactor-virt lazarus perl-modules qt5new trunk upgradedb xry111/git-date xry111/git-date-for-trunk xry111/git-date-test
Last change on this file since d741dcb was d741dcb, checked in by Douglas R. Reno <renodr@…>, 5 years ago

Cleanup in the dbus page. Thanks Pierre

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@18480 af4574ff-66df-0310-9fd7-8a98e5e911e0

  • Property mode set to 100644
File size: 24.5 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
6
7 <!ENTITY dbus-download-http "http://dbus.freedesktop.org/releases/dbus/dbus-&dbus-version;.tar.gz">
8 <!ENTITY dbus-download-ftp " ">
9 <!ENTITY dbus-md5sum "7f06c43736874c1ff50ae20392955511">
10 <!ENTITY dbus-size "1.9 MB">
11 <!ENTITY dbus-buildsize "27 MB (add 23 MB for the tests)">
12 <!ENTITY dbus-time "0.3 SBU (add 2 SBU for the tests)">
13]>
14
15<sect1 id="dbus" xreflabel="dbus-&dbus-version;">
16 <?dbhtml filename="dbus.html"?>
17
18 <sect1info>
19 <othername>$LastChangedBy$</othername>
20 <date>$Date$</date>
21 </sect1info>
22
23 <title>dbus-&dbus-version;</title>
24
25 <indexterm zone="dbus">
26 <primary sortas="a-D-Bus">D-Bus</primary>
27 </indexterm>
28
29 <sect2 role="package">
30 <title>Introduction to D-Bus</title>
31
32 <para revision="sysv">
33 <application>D-Bus</application> is a message bus system, a simple way
34 for applications to talk to one another.
35 <application>D-Bus</application> supplies both a system daemon (for
36 events such as <quote>new hardware device added</quote> or <quote>printer
37 queue changed</quote>) and a per-user-login-session daemon (for general
38 IPC needs among user applications). Also, the message bus is built on top
39 of a general one-to-one message passing framework, which can be used by
40 any two applications to communicate directly (without going through the
41 message bus daemon).
42 </para>
43
44 <para revision="systemd">
45 Even though <application>D-Bus</application> was built in LFS, there are
46 some features provided by the package that other BLFS packages need, but
47 their dependencies didn't fit into LFS.
48 </para>
49
50 &lfs80_checked;
51
52 <bridgehead renderas="sect3">Package Information</bridgehead>
53 <itemizedlist spacing="compact">
54 <listitem>
55 <para>
56 Download (HTTP): <ulink url="&dbus-download-http;"/>
57 </para>
58 </listitem>
59 <listitem>
60 <para>
61 Download (FTP): <ulink url="&dbus-download-ftp;"/>
62 </para>
63 </listitem>
64 <listitem>
65 <para>
66 Download MD5 sum: &dbus-md5sum;
67 </para>
68 </listitem>
69 <listitem>
70 <para>
71 Download size: &dbus-size;
72 </para>
73 </listitem>
74 <listitem>
75 <para>
76 Estimated disk space required: &dbus-buildsize;
77 </para>
78 </listitem>
79 <listitem>
80 <para>
81 Estimated build time: &dbus-time;
82 </para>
83 </listitem>
84 </itemizedlist>
85
86 <bridgehead renderas="sect3">D-Bus Dependencies</bridgehead>
87
88<!--
89 <bridgehead renderas="sect4">Required</bridgehead>
90 <para role="required">
91 <xref linkend="expat"/>
92 </para>
93-->
94 <bridgehead renderas="sect4">Recommended</bridgehead>
95 <para role="recommended">
96 <xref linkend="xorg7-lib"/> (for <command>dbus-launch</command> program)
97 </para>
98
99 <bridgehead renderas="sect4">Optional</bridgehead>
100 <para role="optional">
101 For the tests:
102 <xref linkend="dbus-glib"/>,
103 <xref linkend="dbus-python"/>,
104 <xref linkend="pygobject2"/> (built with gobject-introspection support),
105 and <xref linkend="valgrind"/>;
106
107 for documentation:
108 <xref linkend="doxygen"/>,
109 <xref linkend="xmlto"/>,
110 <ulink url="https://pypi.python.org/pypi/mallard-ducktype">Ducktype</ulink>,
111 and
112 <ulink url="http://ftp.gnome.org/pub/gnome/sources/yelp-tools/">Yelp Tools</ulink>
113 </para>
114
115 <para condition="html" role="usernotes">User Notes:
116 <ulink url="&blfs-wiki;/dbus"/>
117 </para>
118 </sect2>
119
120 <sect2 role="installation">
121 <title>Installation of D-Bus</title>
122
123 <para revision="sysv">
124 If they do not already exist,
125 as the <systemitem class="username">root</systemitem> user, create a
126 system user and group to handle the system message bus activity:
127 </para>
128
129<screen role="root" revision="sysv"><userinput>groupadd -g 18 messagebus &amp;&amp;
130useradd -c "D-Bus Message Daemon User" -d /var/run/dbus \
131 -u 18 -g messagebus -s /bin/false messagebus</userinput></screen>
132
133 <para>
134 Install <application>D-Bus</application> by running the following
135 commands (you may wish to review the output from <command>./configure
136 --help</command> first and add any desired parameters to the
137 <command>configure</command> command shown below):
138 </para>
139
140<screen revision="sysv"><userinput>./configure --prefix=/usr \
141 --sysconfdir=/etc \
142 --localstatedir=/var \
143 --disable-doxygen-docs \
144 --disable-xml-docs \
145 --disable-static \
146 --disable-systemd \
147 --without-systemdsystemunitdir \
148 --with-console-auth-dir=/run/console \
149 --docdir=/usr/share/doc/dbus-&dbus-version; &amp;&amp;
150make</userinput></screen>
151
152<screen revision="systemd"><userinput>./configure --prefix=/usr \
153 --sysconfdir=/etc \
154 --localstatedir=/var \
155 --disable-doxygen-docs \
156 --disable-xml-docs \
157 --disable-static \
158 --with-console-auth-dir=/run/console \
159 --docdir=/usr/share/doc/dbus-&dbus-version; &amp;&amp;
160make</userinput></screen>
161
162 <para>
163 See below for test instructions.
164 </para>
165
166 <warning revision="systemd">
167 <para>
168 Installing the package will override all files installed by
169 <application>D-Bus</application> in LFS. It is critical that
170 nothing uses <application>D-Bus</application> libraries or
171 programs during the installation. The best way to ensure that these
172 libraries are not being used is to run the installation in rescue mode.
173 To switch to rescue mode, run the following command as the
174 <systemitem class="username">root</systemitem> user (from a TTY):
175 </para>
176
177<screen role="root"><userinput>systemctl start rescue.target</userinput></screen>
178
179 </warning>
180
181 <para>
182 Now, as the <systemitem class="username">root</systemitem> user:
183 </para>
184
185<screen role="root"><userinput>make install</userinput></screen>
186
187 <para revision="systemd">
188 The shared library needs to be moved to
189 <filename class="directory">/lib</filename>, and as a result the
190 <filename class="extension">.so</filename> file in
191 <filename class="directory">/usr/lib</filename> will need to be
192 recreated. Run the following command as the
193 <systemitem class="username">root</systemitem> user:
194 </para>
195
196<screen revision="systemd" role="root"><userinput>mv -v /usr/lib/libdbus-1.so.* /lib
197ln -sfv ../../lib/$(readlink /usr/lib/libdbus-1.so) /usr/lib/libdbus-1.so</userinput></screen>
198
199 <para>
200 If you are using a DESTDIR install,
201 <command>dbus-daemon-launch-helper</command> needs to be fixed
202 afterwards. Issue, as <systemitem class="username">root</systemitem>
203 user:
204 </para>
205
206<screen role="root"><userinput>chown -v root:messagebus /usr/libexec/dbus-daemon-launch-helper &amp;&amp;
207chmod -v 4750 /usr/libexec/dbus-daemon-launch-helper</userinput></screen>
208
209 <para revision="sysv">
210 If you are still building your system in chroot or you did not start the
211 daemon yet, but you want to compile some packages that require
212 <application>D-Bus</application>, generate
213 <application>D-Bus</application> UUID to avoid warnings when compiling
214 some packages with the following command as the
215 <systemitem class="username">root</systemitem> user:
216 </para>
217
218<screen role="root" revision="sysv"><userinput>dbus-uuidgen --ensure</userinput></screen>
219
220 <para revision="systemd">
221 If not in chroot, at this point, you should reload the systemd daemon,
222 and reenter multi-user mode with the following commands (as the
223 <systemitem class="username">root</systemitem> user):
224 </para>
225
226<screen role="root" revision="systemd"><userinput>systemctl daemon-reload
227systemctl start multi-user.target</userinput></screen>
228
229 <para>
230 The dbus tests cannot be run until after <xref linkend="dbus-glib"/> has
231 been installed. They must be run as an unprivileged user from a local
232 session with bus address. Tests fail through ssh. If you want to run only
233 the unit tests, replace, below, <parameter>--enable-tests</parameter> by
234 <parameter>--enable-embedded-tests</parameter>, otherwise, <xref
235 linkend="dbus-python"/> has to be installed, before. The tests require
236 passing additional parameters to <command>configure</command> and
237 exposing additional functionality in the binaries. These interfaces are
238 not intended to be used in a production build of
239 <application>D-Bus</application>. If you would like to run the tests,
240 issue the following commands (for the tests, you don't need to build the
241 docs):
242 </para>
243
244<screen><userinput>make distclean &amp;&amp;
245./configure --enable-tests \
246 --enable-asserts \
247 --disable-doxygen-docs \
248 --disable-xml-docs &amp;&amp;
249make &amp;&amp;
250make check</userinput></screen>
251
252 <para>
253 The <quote>estimated disk space required</quote> reported above is
254 obtained in a build using the switches disabling documents generation.
255 This and the use of the <command>make distclean</command> command implies
256 that the build directory size is smaller than the one for a full build
257 with documents generated. There is one error, test-bus.sh, for unknown
258 reasons.
259 </para>
260<!--
261 <para>
262 If <command>run-test.sh</command> fails, it can be disabled with the
263 following sed, before running the commands for the tests:
264 </para>
265
266<screen><userinput>sed -i -e 's:run-test.sh:$(NULL):g' test/name-test/Makefile.in</userinput></screen>-->
267
268 <para>
269 There has been a report that the tests may fail if running inside a
270 Midnight Commander shell. You may get out-of-memory error messages when
271 running the tests. These are normal and can be safely ignored.
272 </para>
273
274 </sect2>
275
276 <sect2 role="commands">
277 <title>Command Explanations</title>
278
279 <para>
280 <parameter>--disable-doxygen-docs</parameter>: This switch disables
281 doxygen documentation build and install, if you have
282 <application>doxygen</application> installed. If
283 <application>doxygen</application> is installed, and you wish to build
284 them, remove this parameter.
285 </para>
286
287 <para>
288 <parameter>--disable-xml-docs</parameter>: This switch disables html
289 documentation build and install, if you have
290 <application>xmlto</application> installed. If
291 <application>xmlto</application> is installed, and you wish to build
292 them, remove this parameter.
293 </para>
294
295 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
296 href="../../xincludes/static-libraries.xml"/>
297
298 <para revision="sysv">
299 <parameter>--disable-systemd</parameter>: This switch disables systemd
300 support in <application>D-Bus</application>.
301 </para>
302
303 <para revision="sysv">
304 <parameter>--without-systemdsystemunitdir</parameter>: This switch
305 prevents installation of systemd unit files.
306 </para>
307
308 <para>
309 <parameter>--with-console-auth-dir=/run/console/</parameter>: This
310 parameter specifies location of the
311 <application>ConsoleKit</application> auth dir.
312 </para>
313
314 <para>
315 <parameter>--enable-tests</parameter>: Build extra parts of the code to
316 support all tests. Configure will end with a NOTE warning about increased
317 size of libraries and decreased security.
318 </para>
319
320 <para>
321 <option>--enable-embedded-tests</option>: Build extra parts of the
322 code to support only unit tests. Configure will end with a NOTE warning
323 about increased size of libraries and decreased security.
324 </para>
325
326 <para>
327 <parameter>--enable-asserts</parameter>: Enable debugging code to run
328 assertions for statements normally assumed to be true. This prevents a
329 warning that '<parameter>--enable-tests</parameter>' on its own is only
330 useful for profiling and might not give true results for all tests, but
331 adds its own NOTE that this should not be used in a production build.
332 </para>
333
334 </sect2>
335
336 <sect2 role="configuration">
337 <title>Configuring D-Bus</title>
338
339 <sect3 id="dbus-config">
340 <title>Config Files</title>
341
342 <para>
343 <filename>/etc/dbus-1/session.conf</filename>,
344 <filename>/etc/dbus-1/system.conf</filename> and
345 <filename>/etc/dbus-1/system.d/*</filename>
346 </para>
347
348 <indexterm zone="dbus dbus-config">
349 <primary sortas="e-etc-dbus-1-session.conf">/etc/dbus-1/session.conf</primary>
350 </indexterm>
351
352 <indexterm zone="dbus dbus-config">
353 <primary sortas="e-etc-dbus-1/system.conf">/etc/dbus-1/system.conf</primary>
354 </indexterm>
355
356 <indexterm zone="dbus dbus-config">
357 <primary sortas="e-etc-dbus-1-system.d-star">/etc/dbus-1/system.d/*</primary>
358 </indexterm>
359
360 </sect3>
361
362 <sect3 id="dbus-session-config" xreflabel="D-Bus custom services directory">
363 <title>Configuration Information</title>
364
365 <para>
366 The configuration files listed above should probably not be
367 modified. If changes are required, you should create
368 <filename>/etc/dbus-1/session-local.conf</filename> and/or
369 <filename>/etc/dbus-1/system-local.conf</filename> and make any
370 desired changes to these files.
371 </para>
372
373 <para>
374 If any packages install a
375 <application>D-Bus</application> <filename>.service</filename>
376 file outside of the standard <filename
377 class="directory">/usr/share/dbus-1/services</filename> directory,
378 that directory should be added to the local session configuration.
379 For instance, <filename
380 class="directory">/usr/local/share/dbus-1/services</filename> can
381 be added by performing the following commands as the
382 <systemitem class="username">root</systemitem> user:
383 </para>
384
385<screen role="root"><userinput>cat &gt; /etc/dbus-1/session-local.conf &lt;&lt; "EOF"
386<literal>&lt;!DOCTYPE busconfig PUBLIC
387 "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
388 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd"&gt;
389&lt;busconfig&gt;
390
391 &lt;!-- Search for .service files in /usr/local --&gt;
392 &lt;servicedir&gt;/usr/local/share/dbus-1/services&lt;/servicedir&gt;
393
394&lt;/busconfig&gt;</literal>
395EOF</userinput></screen>
396
397 </sect3>
398
399 <sect3 id="dbus-session">
400 <title>D-Bus Session Daemon</title>
401
402 <para revision="sysv">
403 To automatically start <command>dbus-daemon</command> when the
404 system is rebooted, install the
405 <filename>/etc/rc.d/init.d/dbus</filename> bootscript from the
406 <xref linkend="bootscripts"/> package.
407 </para>
408
409 <indexterm zone="dbus dbus-session" revision="sysv">
410 <primary sortas="f-dbus">dbus</primary>
411 </indexterm>
412
413<screen role="root" revision="sysv"><userinput>make install-dbus</userinput></screen>
414
415 <para revision="sysv">
416 Note that this boot script only starts the system-wide
417 <application>D-Bus</application> daemon. Each user requiring access to
418 <application>D-Bus</application> services will also need to run a
419 session daemon as well. There are many methods you can use to start a
420 session daemon using the <command>dbus-launch</command> command. Review
421 the <command>dbus-launch</command> man page for details about the
422 available parameters and options. Here are some suggestions and
423 examples:
424 </para>
425
426 <para revision="systemd">
427 There are many methods you can use to start a session daemon
428 using the <command>dbus-launch</command> command. Review the
429 <command>dbus-launch</command> man page for details about the
430 available parameters and options. Here are some suggestions and
431 examples:
432 </para>
433
434
435 <itemizedlist spacing="compact">
436 <listitem>
437 <para>
438 Add <command>dbus-launch</command> to the line in the
439 <filename>~/.xinitrc</filename> file that starts your graphical
440 desktop environment.
441 </para>
442 </listitem>
443 <listitem>
444 <para>
445 If you use <command>xdm</command> or some other display manager
446 that calls the <filename>~/.xsession</filename> file, you can add
447 <command>dbus-launch</command> to the line in your
448 <filename>~/.xsession</filename> file that starts your graphical
449 desktop environment. The syntax would be similar to the example in
450 the <filename>~/.xinitrc</filename> file.
451 </para>
452 </listitem>
453 <listitem>
454 <para>
455 The examples shown previously use
456 <command>dbus-launch</command> to specify a program to be run. This
457 has the benefit (when also using the
458 <parameter>--exit-with-session</parameter> parameter) of stopping the
459 session daemon when the specified program is stopped. You can also
460 start the session daemon in your system or personal startup scripts
461 by adding the following lines:
462 </para>
463
464<screen role="nodump"><userinput><literal># Start the D-Bus session daemon
465eval `dbus-launch`
466export DBUS_SESSION_BUS_ADDRESS</literal></userinput></screen>
467
468 <para>
469 This method will not stop the session daemon when you exit
470 your shell, therefore you should add the following line to your
471 <filename>~/.bash_logout</filename> file:
472 </para>
473
474<screen role="nodump"><userinput><literal># Kill the D-Bus session daemon
475kill $DBUS_SESSION_BUS_PID</literal></userinput></screen>
476 </listitem>
477
478 <listitem>
479 <para>
480 A hint has been written that provides ways to start scripts
481 using the KDM session manager of KDE. The concepts in this hint could
482 possibly be used with other session managers as well. The hint is
483 located at <ulink
484 url="&hints-root;/downloads/files/execute-session-scripts-using-kdm.txt"/>.
485 </para>
486 </listitem>
487
488 </itemizedlist>
489
490 </sect3>
491
492 </sect2>
493
494 <sect2 role="content" revision="sysv">
495 <title>Contents</title>
496
497 <segmentedlist>
498 <segtitle>Installed Programs</segtitle>
499 <segtitle>Installed Library</segtitle>
500 <segtitle>Installed Directories</segtitle>
501
502 <seglistitem>
503 <seg>
504 dbus-cleanup-sockets, dbus-daemon, dbus-launch, dbus-monitor,
505 dbus-run-session, dbus-send, dbus-test-tool,
506 dbus-update-activation-environment, and dbus-uuidgen
507 </seg>
508 <seg>
509 libdbus-1.so
510 </seg>
511 <seg>
512 /etc/dbus-1,
513 /usr/{include,lib}/dbus-1.0,
514 /usr/share/dbus-1,
515 /usr/share/doc/dbus-&dbus-version;, and
516 /var/{lib,run}/dbus
517 </seg>
518 </seglistitem>
519 </segmentedlist>
520
521 <variablelist>
522 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
523 <?dbfo list-presentation="list"?>
524 <?dbhtml list-presentation="table"?>
525
526 <varlistentry id="dbus-cleanup-sockets">
527 <term><command>dbus-cleanup-sockets</command></term>
528 <listitem>
529 <para>
530 is used to clean up leftover sockets in a directory.
531 </para>
532 <indexterm zone="dbus dbus-cleanup-sockets">
533 <primary sortas="b-dbus-cleanup-sockets">dbus-cleanup-sockets</primary>
534 </indexterm>
535 </listitem>
536 </varlistentry>
537
538 <varlistentry id="dbus-daemon">
539 <term><command>dbus-daemon</command></term>
540 <listitem>
541 <para>
542 is the <application>D-Bus</application> message bus daemon.
543 </para>
544 <indexterm zone="dbus dbus-daemon">
545 <primary sortas="b-dbus-daemon">dbus-daemon</primary>
546 </indexterm>
547 </listitem>
548 </varlistentry>
549
550 <varlistentry id="dbus-launch">
551 <term><command>dbus-launch</command></term>
552 <listitem>
553 <para>
554 is used to start <command>dbus-daemon</command> from a shell
555 script. It would normally be called from a user's login
556 scripts.
557 </para>
558 <indexterm zone="dbus dbus-launch">
559 <primary sortas="b-dbus-launch">dbus-launch</primary>
560 </indexterm>
561 </listitem>
562 </varlistentry>
563
564 <varlistentry id="dbus-monitor">
565 <term><command>dbus-monitor</command></term>
566 <listitem>
567 <para>
568 is used to monitor messages going through a
569 <application>D-Bus</application> message bus.
570 </para>
571 <indexterm zone="dbus dbus-monitor">
572 <primary sortas="b-dbus-monitor">dbus-monitor</primary>
573 </indexterm>
574 </listitem>
575 </varlistentry>
576
577 <varlistentry id="dbus-run-session">
578 <term><command>dbus-run-session</command></term>
579 <listitem>
580 <para>
581 start a process as a new <application>D-Bus</application> session.
582 </para>
583 <indexterm zone="dbus dbus-run-session">
584 <primary sortas="b-dbus-run-session">dbus-run-session</primary>
585 </indexterm>
586 </listitem>
587 </varlistentry>
588
589 <varlistentry id="dbus-send">
590 <term><command>dbus-send</command></term>
591 <listitem>
592 <para>
593 is used to send a message to a <application>D-Bus</application>
594 message bus.
595 </para>
596 <indexterm zone="dbus dbus-send">
597 <primary sortas="b-dbus-send">dbus-send</primary>
598 </indexterm>
599 </listitem>
600 </varlistentry>
601
602 <varlistentry id="dbus-test-tool">
603 <term><command>dbus-test-tool</command></term>
604 <listitem>
605 <para>
606 is a <application>D-Bus</application> traffic generator and test
607 tool; it is a multi-purpose tool for debugging and profiling
608 <application>D-Bus</application>.
609 </para>
610 <indexterm zone="dbus dbus-test-tool">
611 <primary sortas="b-dbus-test-tool">dbus-test-tool</primary>
612 </indexterm>
613 </listitem>
614 </varlistentry>
615
616 <varlistentry id="dbus-update-activation-environment">
617 <term><command>dbus-update-activation-environment</command></term>
618 <listitem>
619 <para>
620 is used to update the environment used for
621 <application>D-Bus</application> session services;
622 it updates the list of environment variables used by
623 <command>dbus-daemon --session</command> when it activates session
624 services without using systemd.
625 </para>
626 <indexterm zone="dbus dbus-update-activation-environment">
627 <primary sortas="b-dbus-update-activation-environment">
628 dbus-update-activation-environment</primary>
629 </indexterm>
630 </listitem>
631 </varlistentry>
632
633 <varlistentry id="dbus-uuidgen">
634 <term><command>dbus-uuidgen</command></term>
635 <listitem>
636 <para>
637 is used to generate a universally unique ID.
638 </para>
639 <indexterm zone="dbus dbus-uuidgen">
640 <primary sortas="b-dbus-uuidgen">dbus-uuidgen</primary>
641 </indexterm>
642 </listitem>
643 </varlistentry>
644
645 <varlistentry id="libdbus-1">
646 <term><filename class="libraryfile">libdbus-1.so</filename></term>
647 <listitem>
648 <para>
649 contains the API functions used by the
650 <application>D-Bus</application> message daemon.
651 <application>D-Bus</application> is first a library that provides
652 one-to-one communication between any two applications;
653 <command>dbus-daemon</command> is an application that uses this
654 library to implement a message bus daemon.
655 </para>
656 <indexterm zone="dbus libdbus-1">
657 <primary sortas="c-libdbus-1">libdbus-1.so</primary>
658 </indexterm>
659 </listitem>
660 </varlistentry>
661
662 </variablelist>
663
664 </sect2>
665
666 <sect2 role="content" revision="systemd">
667 <title>Contents</title>
668
669 <para>
670 A list of the installed files, along with their short
671 descriptions can be found at
672 <ulink url="&lfs-rootd;/chapter06/dbus.html#contents-dbus"/>.
673 </para>
674
675 </sect2>
676
677
678</sect1>
679
Note: See TracBrowser for help on using the repository browser.