source: general/sysutils/dbus.xml@ 1fac6dd7

11.3 12.0 12.1 kea ken/TL2024 ken/inkscape-core-mods ken/tuningfonts lazarus lxqt plabs/newcss plabs/python-mods python3.11 qt5new rahul/power-profiles-daemon renodr/vulkan-addition trunk xry111/llvm18 xry111/xf86-video-removal
Last change on this file since 1fac6dd7 was 3f2db3a6, checked in by Pierre Labastie <pierre.labastie@…>, 19 months ago

Remove sect1info tags

They only contain a date tag that is nowhere used.

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