source: general/sysutils/dbus.xml@ 819a4c7

10.0 10.1 11.0 11.1 11.2 11.3 12.0 12.1 9.0 9.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 upgradedb xry111/intltool xry111/llvm18 xry111/soup3 xry111/test-20220226 xry111/xf86-video-removal
Last change on this file since 819a4c7 was 819a4c7, checked in by Douglas R. Reno <renodr@…>, 5 years ago

Update to dbus-1.12.16. This fixes CVE-2019-12749, an authentication bypass in DBUS.

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