source: general/sysutils/dbus.xml@ 45ab6c7

trunk
Last change on this file since 45ab6c7 was 45ab6c7, checked in by Xi Ruoyao <xry111@…>, 3 months ago

more SVN prop clean up

Remove "$LastChanged$" everywhere, and also some unused $Date$

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