source: general/sysutils/dbus.xml@ ad4d3fd

elogind
Last change on this file since ad4d3fd was ad4d3fd, checked in by DJ Lucas <dj@…>, 5 years ago

Update to elogind-241.1.
Remove some unneeded patches and update instrucitons appropriately.

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

  • 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.gz">
8 <!ENTITY dbus-download-ftp " ">
9 <!ENTITY dbus-md5sum "ea11069521beeee4e47f0086596a43c8">
10 <!ENTITY dbus-size "2.0 MB">
11 <!ENTITY dbus-buildsize "21 MB (add 8 MB for the tests)">
12 <!ENTITY dbus-time "0.3 SBU (add 0.8 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 &lfs84_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"><xref linkend="elogind"/> (first build
98 without, and then again after elogind is installed)</phrase>
99 </para>
100
101 <bridgehead renderas="sect4">Optional</bridgehead>
102 <para role="optional">
103 For the tests:
104 <xref linkend="dbus-glib"/>,
105 <xref linkend="dbus-python"/>,
106 <xref linkend="pygobject3"/>,
107 and <xref linkend="valgrind"/>;
108
109 for documentation:
110 <xref linkend="doxygen"/>,
111 <xref linkend="xmlto"/>,
112 <ulink url="https://pypi.python.org/pypi/mallard-ducktype">Ducktype</ulink>,
113 and
114 <ulink url="http://ftp.gnome.org/pub/gnome/sources/yelp-tools/">Yelp Tools</ulink>
115 </para>
116
117 <para condition="html" role="usernotes">User Notes:
118 <ulink url="&blfs-wiki;/dbus"/>
119 </para>
120 </sect2>
121
122 <sect2 role="installation">
123 <title>Installation of D-Bus</title>
124
125 <para revision="sysv">
126 If they do not already exist,
127 as the <systemitem class="username">root</systemitem> user, create a
128 system user and group to handle the system message bus activity:
129 </para>
130
131<screen role="root" revision="sysv"><userinput>groupadd -g 18 messagebus &amp;&amp;
132useradd -c "D-Bus Message Daemon User" -d /var/run/dbus \
133 -u 18 -g messagebus -s /bin/false messagebus</userinput></screen>
134
135 <para revision="sysv">
136 Apply a patch to fix detection of <application>elogind</application>:
137 </para>
138
139 <para>
140 Install <application>D-Bus</application> by running the following
141 commands (you may wish to review the output from <command>./configure
142 --help</command> first and add any desired parameters to the
143 <command>configure</command> command shown below):
144 </para>
145
146<screen revision="sysv"><userinput>./configure --prefix=/usr \
147 --sysconfdir=/etc \
148 --localstatedir=/var \
149 --enable-user-session \
150 --disable-doxygen-docs \
151 --disable-xml-docs \
152 --disable-static \
153 --with-systemduserunitdir= \
154 --with-systemdsystemunitdir= \
155 --docdir=/usr/share/doc/dbus-&dbus-version; \
156 --with-console-auth-dir=/run/console \
157 --with-system-pid-file=/run/dbus/pid \
158 --with-system-socket=/run/dbus/system_bus_socket &amp;&amp;
159make</userinput></screen>
160
161<screen revision="systemd"><userinput>./configure --prefix=/usr \
162 --sysconfdir=/etc \
163 --localstatedir=/var \
164 --enable-user-session \
165 --disable-doxygen-docs \
166 --disable-xml-docs \
167 --disable-static \
168 --docdir=/usr/share/doc/dbus-&dbus-version; \
169 --with-console-auth-dir=/run/console \
170 --with-system-pid-file=/run/dbus/pid \
171 --with-system-socket=/run/dbus/system_bus_socket &amp;&amp;
172make</userinput></screen>
173
174 <para>
175 See below for test instructions.
176 </para>
177
178 <warning revision="systemd">
179 <para>
180 Installing the package will override all files installed by
181 <application>D-Bus</application> in LFS. It is critical that
182 nothing uses <application>D-Bus</application> libraries or
183 programs during the installation. The best way to ensure that these
184 libraries are not being used is to run the installation in rescue mode.
185 To switch to rescue mode, run the following command as the
186 <systemitem class="username">root</systemitem> user (from a TTY):
187 </para>
188
189<screen role="root"><userinput>systemctl start rescue.target</userinput></screen>
190
191 </warning>
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
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 <para revision="systemd">
240 If not in chroot, at this point, you should reload the systemd daemon,
241 and reenter multi-user mode with the following commands (as the
242 <systemitem class="username">root</systemitem> user):
243 </para>
244
245<screen role="root" revision="systemd"><userinput>systemctl daemon-reload
246systemctl start multi-user.target</userinput></screen>
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><userinput>make distclean &amp;&amp;
265./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 The test <command>test-bus.sh</command> is known to fail. There has also
274 been reports that the tests may fail if running inside a Midnight
275 Commander shell. You may get out-of-memory error messages when running
276 the tests. These are normal and can be safely ignored.
277 </para>
278
279 </sect2>
280
281 <sect2 role="commands">
282 <title>Command Explanations</title>
283
284 <para>
285 <parameter>--disable-doxygen-docs</parameter>: This switch disables
286 doxygen documentation build and install, if you have
287 <application>doxygen</application> installed. If
288 <application>doxygen</application> is installed, and you wish to build
289 them, remove this parameter.
290 </para>
291
292 <para>
293 <parameter>--disable-xml-docs</parameter>: This switch disables html
294 documentation build and install, if you have
295 <application>xmlto</application> installed. If
296 <application>xmlto</application> is installed, and you wish to build
297 them, remove this parameter.
298 </para>
299
300 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
301 href="../../xincludes/static-libraries.xml"/>
302
303 <para>
304 <parameter>--enable-user-session</parameter>: This parameter enables
305 per-user DBus sessions with
306 <phrase revision="sysv"><application>elogind</application>.</phrase>
307 <phrase revision="systemd"><application>systemd</application>.</phrase>
308 </para>
309
310 <para revision="sysv">
311 <parameter>--with-systemd{user,system}unitdir=</parameter>: These
312 switches disable installation of systemd units on elogind based systems.
313 </para>
314 <para>
315 <parameter>--with-console-auth-dir=/run/console/</parameter>: This
316 parameter specifies the location of the
317 <application>ConsoleKit</application> auth dir.
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>: Build 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>: Build 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>: Enable 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>xdm</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 <listitem>
493 <para>
494 A hint has been written that provides ways to start scripts
495 using the KDM session manager of KDE. The concepts in this hint could
496 possibly be used with other session managers as well. The hint is
497 located at <ulink
498 url="&hints-root;/downloads/files/execute-session-scripts-using-kdm.txt"/>.
499 </para>
500 </listitem>
501
502 </itemizedlist>
503
504 </sect3>
505
506 </sect2>
507
508 <sect2 role="content" revision="sysv">
509 <title>Contents</title>
510
511 <segmentedlist>
512 <segtitle>Installed Programs</segtitle>
513 <segtitle>Installed Library</segtitle>
514 <segtitle>Installed Directories</segtitle>
515
516 <seglistitem>
517 <seg>
518 dbus-cleanup-sockets, dbus-daemon, dbus-launch, dbus-monitor,
519 dbus-run-session, dbus-send, dbus-test-tool,
520 dbus-update-activation-environment, and dbus-uuidgen
521 </seg>
522 <seg>
523 libdbus-1.so
524 </seg>
525 <seg>
526 /etc/dbus-1,
527 /usr/{include,lib}/dbus-1.0,
528 /usr/share/dbus-1,
529 /usr/share/doc/dbus-&dbus-version;, and
530 /var/{lib,run}/dbus
531 </seg>
532 </seglistitem>
533 </segmentedlist>
534
535 <variablelist>
536 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
537 <?dbfo list-presentation="list"?>
538 <?dbhtml list-presentation="table"?>
539
540 <varlistentry id="dbus-cleanup-sockets">
541 <term><command>dbus-cleanup-sockets</command></term>
542 <listitem>
543 <para>
544 is used to clean up leftover sockets in a directory.
545 </para>
546 <indexterm zone="dbus dbus-cleanup-sockets">
547 <primary sortas="b-dbus-cleanup-sockets">dbus-cleanup-sockets</primary>
548 </indexterm>
549 </listitem>
550 </varlistentry>
551
552 <varlistentry id="dbus-daemon">
553 <term><command>dbus-daemon</command></term>
554 <listitem>
555 <para>
556 is the <application>D-Bus</application> message bus daemon.
557 </para>
558 <indexterm zone="dbus dbus-daemon">
559 <primary sortas="b-dbus-daemon">dbus-daemon</primary>
560 </indexterm>
561 </listitem>
562 </varlistentry>
563
564 <varlistentry id="dbus-launch">
565 <term><command>dbus-launch</command></term>
566 <listitem>
567 <para>
568 is used to start <command>dbus-daemon</command> from a shell
569 script. It would normally be called from a user's login
570 scripts.
571 </para>
572 <indexterm zone="dbus dbus-launch">
573 <primary sortas="b-dbus-launch">dbus-launch</primary>
574 </indexterm>
575 </listitem>
576 </varlistentry>
577
578 <varlistentry id="dbus-monitor">
579 <term><command>dbus-monitor</command></term>
580 <listitem>
581 <para>
582 is used to monitor messages going through a
583 <application>D-Bus</application> message bus.
584 </para>
585 <indexterm zone="dbus dbus-monitor">
586 <primary sortas="b-dbus-monitor">dbus-monitor</primary>
587 </indexterm>
588 </listitem>
589 </varlistentry>
590
591 <varlistentry id="dbus-run-session">
592 <term><command>dbus-run-session</command></term>
593 <listitem>
594 <para>
595 start a process as a new <application>D-Bus</application> session.
596 </para>
597 <indexterm zone="dbus dbus-run-session">
598 <primary sortas="b-dbus-run-session">dbus-run-session</primary>
599 </indexterm>
600 </listitem>
601 </varlistentry>
602
603 <varlistentry id="dbus-send">
604 <term><command>dbus-send</command></term>
605 <listitem>
606 <para>
607 is used to send a message to a <application>D-Bus</application>
608 message bus.
609 </para>
610 <indexterm zone="dbus dbus-send">
611 <primary sortas="b-dbus-send">dbus-send</primary>
612 </indexterm>
613 </listitem>
614 </varlistentry>
615
616 <varlistentry id="dbus-test-tool">
617 <term><command>dbus-test-tool</command></term>
618 <listitem>
619 <para>
620 is a <application>D-Bus</application> traffic generator and test
621 tool; it is a multi-purpose tool for debugging and profiling
622 <application>D-Bus</application>.
623 </para>
624 <indexterm zone="dbus dbus-test-tool">
625 <primary sortas="b-dbus-test-tool">dbus-test-tool</primary>
626 </indexterm>
627 </listitem>
628 </varlistentry>
629
630 <varlistentry id="dbus-update-activation-environment">
631 <term><command>dbus-update-activation-environment</command></term>
632 <listitem>
633 <para>
634 is used to update the environment used for
635 <application>D-Bus</application> session services;
636 it updates the list of environment variables used by
637 <command>dbus-daemon --session</command> when it activates session
638 services without using systemd.
639 </para>
640 <indexterm zone="dbus dbus-update-activation-environment">
641 <primary sortas="b-dbus-update-activation-environment">
642 dbus-update-activation-environment</primary>
643 </indexterm>
644 </listitem>
645 </varlistentry>
646
647 <varlistentry id="dbus-uuidgen">
648 <term><command>dbus-uuidgen</command></term>
649 <listitem>
650 <para>
651 is used to generate a universally unique ID.
652 </para>
653 <indexterm zone="dbus dbus-uuidgen">
654 <primary sortas="b-dbus-uuidgen">dbus-uuidgen</primary>
655 </indexterm>
656 </listitem>
657 </varlistentry>
658
659 <varlistentry id="libdbus-1">
660 <term><filename class="libraryfile">libdbus-1.so</filename></term>
661 <listitem>
662 <para>
663 contains the API functions used by the
664 <application>D-Bus</application> message daemon.
665 <application>D-Bus</application> is first a library that provides
666 one-to-one communication between any two applications;
667 <command>dbus-daemon</command> is an application that uses this
668 library to implement a message bus daemon.
669 </para>
670 <indexterm zone="dbus libdbus-1">
671 <primary sortas="c-libdbus-1">libdbus-1.so</primary>
672 </indexterm>
673 </listitem>
674 </varlistentry>
675
676 </variablelist>
677
678 </sect2>
679
680 <sect2 role="content" revision="systemd">
681 <title>Contents</title>
682
683 <para>
684 A list of the installed files, along with their short
685 descriptions can be found at
686 <ulink url="&lfs-rootd;/chapter06/dbus.html#contents-dbus"/>.
687 </para>
688
689 </sect2>
690
691
692</sect1>
693
Note: See TracBrowser for help on using the repository browser.