source: general/sysutils/dbus.xml@ a509a18

10.0 10.1 11.0 11.1 11.2 11.3 12.0 12.1 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind kea ken/TL2024 ken/inkscape-core-mods ken/tuningfonts lazarus lxqt perl-modules 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 a509a18 was a509a18, checked in by DJ Lucas <dj@…>, 6 years ago

Update to p11-kit-0.23.13. Fixes #11004.
Tags

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@20303 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 "c3e12b4206e2a7da39d7cc42567790ef">
10 <!ENTITY dbus-size "2.0 MB">
11 <!ENTITY dbus-buildsize "21 MB (add 8 MB for the tests)">
12 <!ENTITY dbus-time "0.2 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 &lfs83_checked;
51
52 <bridgehead renderas="sect3">Package Information</bridgehead>
53 <itemizedlist spacing="compact">
54 <listitem>
55 <para>
56 Download (HTTP): <ulink url="&dbus-download-http;"/>
57 </para>
58 </listitem>
59 <listitem>
60 <para>
61 Download (FTP): <ulink url="&dbus-download-ftp;"/>
62 </para>
63 </listitem>
64 <listitem>
65 <para>
66 Download MD5 sum: &dbus-md5sum;
67 </para>
68 </listitem>
69 <listitem>
70 <para>
71 Download size: &dbus-size;
72 </para>
73 </listitem>
74 <listitem>
75 <para>
76 Estimated disk space required: &dbus-buildsize;
77 </para>
78 </listitem>
79 <listitem>
80 <para>
81 Estimated build time: &dbus-time;
82 </para>
83 </listitem>
84 </itemizedlist>
85
86 <bridgehead renderas="sect3">D-Bus Dependencies</bridgehead>
87
88<!--
89 <bridgehead renderas="sect4">Required</bridgehead>
90 <para role="required">
91 <xref linkend="expat"/>
92 </para>
93-->
94 <bridgehead renderas="sect4" revision="systemd">Required</bridgehead>
95 <para role="required" revision="systemd">
96 <xref linkend="systemd"/>
97 </para>
98
99 <bridgehead renderas="sect4">Recommended</bridgehead>
100 <para role="recommended">
101 <xref linkend="xorg7-lib"/> (for <command>dbus-launch</command> program)
102 </para>
103
104 <bridgehead renderas="sect4">Optional</bridgehead>
105 <para role="optional">
106 For the tests:
107 <xref linkend="dbus-glib"/>,
108 <xref linkend="dbus-python"/>,
109 <xref linkend="pygobject3"/>,
110 and <xref linkend="valgrind"/>;
111
112 for documentation:
113 <xref linkend="doxygen"/>,
114 <xref linkend="xmlto"/>,
115 <ulink url="https://pypi.python.org/pypi/mallard-ducktype">Ducktype</ulink>,
116 and
117 <ulink url="http://ftp.gnome.org/pub/gnome/sources/yelp-tools/">Yelp Tools</ulink>
118 </para>
119
120 <para condition="html" role="usernotes">User Notes:
121 <ulink url="&blfs-wiki;/dbus"/>
122 </para>
123 </sect2>
124
125 <sect2 role="installation">
126 <title>Installation of D-Bus</title>
127
128 <para revision="sysv">
129 If they do not already exist,
130 as the <systemitem class="username">root</systemitem> user, create a
131 system user and group to handle the system message bus activity:
132 </para>
133
134<screen role="root" revision="sysv"><userinput>groupadd -g 18 messagebus &amp;&amp;
135useradd -c "D-Bus Message Daemon User" -d /var/run/dbus \
136 -u 18 -g messagebus -s /bin/false messagebus</userinput></screen>
137
138 <para>
139 Install <application>D-Bus</application> by running the following
140 commands (you may wish to review the output from <command>./configure
141 --help</command> first and add any desired parameters to the
142 <command>configure</command> command shown below):
143 </para>
144
145<screen revision="sysv"><userinput>
146./configure --prefix=/usr \
147 --sysconfdir=/etc \
148 --localstatedir=/var \
149 --disable-doxygen-docs \
150 --disable-xml-docs \
151 --disable-static \
152 --docdir=/usr/share/doc/dbus-&dbus-version; \
153 --with-console-auth-dir=/run/console \
154 --with-system-pid-file=/run/dbus/pid \
155 --with-system-socket=/run/dbus/system_bus_socket &amp;&amp;
156make</userinput></screen>
157
158<screen revision="systemd"><userinput>./configure --prefix=/usr \
159 --sysconfdir=/etc \
160 --localstatedir=/var \
161 --enable-user-session \
162 --disable-doxygen-docs \
163 --disable-xml-docs \
164 --disable-static \
165 --docdir=/usr/share/doc/dbus-&dbus-version; \
166 --with-console-auth-dir=/run/console \
167 --with-system-pid-file=/run/dbus/pid \
168 --with-system-socket=/run/dbus/system_bus_socket &amp;&amp;
169make</userinput></screen>
170
171 <para>
172 See below for test instructions.
173 </para>
174
175 <warning revision="systemd">
176 <para>
177 Installing the package will override all files installed by
178 <application>D-Bus</application> in LFS. It is critical that
179 nothing uses <application>D-Bus</application> libraries or
180 programs during the installation. The best way to ensure that these
181 libraries are not being used is to run the installation in rescue mode.
182 To switch to rescue mode, run the following command as the
183 <systemitem class="username">root</systemitem> user (from a TTY):
184 </para>
185
186<screen role="root"><userinput>systemctl start rescue.target</userinput></screen>
187
188 </warning>
189
190 <para>
191 Now, as the <systemitem class="username">root</systemitem> user:
192 </para>
193
194<screen role="root"><userinput>make install</userinput></screen>
195
196 <para revision="systemd">
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 revision="systemd" 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 <para>
209 If you are using a DESTDIR install,
210 <command>dbus-daemon-launch-helper</command> needs to be fixed
211 afterwards. Issue, as <systemitem class="username">root</systemitem>
212 user:
213 </para>
214
215<screen role="root"><userinput>chown -v root:messagebus /usr/libexec/dbus-daemon-launch-helper &amp;&amp;
216chmod -v 4750 /usr/libexec/dbus-daemon-launch-helper</userinput></screen>
217
218 <para revision="sysv">
219 If you are still building your system in chroot or you did not start the
220 daemon yet, but you want to compile some packages that require
221 <application>D-Bus</application>, generate
222 <application>D-Bus</application> UUID to avoid warnings when compiling
223 some packages with the following command as the
224 <systemitem class="username">root</systemitem> user:
225 </para>
226
227<screen role="root" revision="sysv"><userinput>dbus-uuidgen --ensure</userinput></screen>
228
229 <para revision="systemd">
230 If not in chroot, at this point, you should reload the systemd daemon,
231 and reenter multi-user mode with the following commands (as the
232 <systemitem class="username">root</systemitem> user):
233 </para>
234
235<screen role="root" revision="systemd"><userinput>systemctl daemon-reload
236systemctl start multi-user.target</userinput></screen>
237
238 <para>
239 The dbus tests cannot be run until after <xref linkend="dbus-glib"/> has
240 been installed. They must be run as an unprivileged user from a local
241 session with bus address. To run the standard tests issue
242 <command>make check</command>.
243 </para>
244
245 <para>
246 If you want to run the unit regression tests, configure requires
247 additional parameters which expose additional functionality in the
248 binaries that are not intended to be used in a production build of
249 <application>D-Bus</application>. If you would like to run the tests,
250 issue the following commands (for the tests, you don't need to build the
251 docs):
252 </para>
253
254<screen><userinput>make distclean &amp;&amp;
255./configure --enable-tests \
256 --enable-asserts \
257 --disable-doxygen-docs \
258 --disable-xml-docs &amp;&amp;
259make &amp;&amp;
260make check</userinput></screen>
261
262 <para>
263 The test <command>test-bus.sh</command> is known to fail. There has also
264 been reports that the tests may fail if running inside a Midnight
265 Commander shell. You may get out-of-memory error messages when running
266 the tests. These are normal and can be safely ignored.
267 </para>
268
269 </sect2>
270
271 <sect2 role="commands">
272 <title>Command Explanations</title>
273
274 <para>
275 <parameter>--disable-doxygen-docs</parameter>: This switch disables
276 doxygen documentation build and install, if you have
277 <application>doxygen</application> installed. If
278 <application>doxygen</application> is installed, and you wish to build
279 them, remove this parameter.
280 </para>
281
282 <para>
283 <parameter>--disable-xml-docs</parameter>: This switch disables html
284 documentation build and install, if you have
285 <application>xmlto</application> installed. If
286 <application>xmlto</application> is installed, and you wish to build
287 them, remove this parameter.
288 </para>
289
290 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
291 href="../../xincludes/static-libraries.xml"/>
292
293 <para revision="sysv">
294 <parameter>--disable-systemd</parameter>: This switch disables systemd
295 support in <application>D-Bus</application>.
296 </para>
297
298 <para revision="sysv">
299 <parameter>--without-systemdsystemunitdir</parameter>: This switch
300 prevents installation of systemd unit files.
301 </para>
302
303 <para revision="systemd">
304 <parameter>--enable-user-session</parameter>: This parameter enables
305 per-user DBus sessions with <application>systemd</application>.
306 </para>
307
308 <para>
309 <parameter>--with-console-auth-dir=/run/console/</parameter>: This
310 parameter specifies location of the
311 <application>ConsoleKit</application> auth dir.
312 </para>
313
314 <para>
315 <parameter>--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>: Build 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>: Build 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>: Enable 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>xdm</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 <listitem>
487 <para>
488 A hint has been written that provides ways to start scripts
489 using the KDM session manager of KDE. The concepts in this hint could
490 possibly be used with other session managers as well. The hint is
491 located at <ulink
492 url="&hints-root;/downloads/files/execute-session-scripts-using-kdm.txt"/>.
493 </para>
494 </listitem>
495
496 </itemizedlist>
497
498 </sect3>
499
500 </sect2>
501
502 <sect2 role="content" revision="sysv">
503 <title>Contents</title>
504
505 <segmentedlist>
506 <segtitle>Installed Programs</segtitle>
507 <segtitle>Installed Library</segtitle>
508 <segtitle>Installed Directories</segtitle>
509
510 <seglistitem>
511 <seg>
512 dbus-cleanup-sockets, dbus-daemon, dbus-launch, dbus-monitor,
513 dbus-run-session, dbus-send, dbus-test-tool,
514 dbus-update-activation-environment, and dbus-uuidgen
515 </seg>
516 <seg>
517 libdbus-1.so
518 </seg>
519 <seg>
520 /etc/dbus-1,
521 /usr/{include,lib}/dbus-1.0,
522 /usr/share/dbus-1,
523 /usr/share/doc/dbus-&dbus-version;, and
524 /var/{lib,run}/dbus
525 </seg>
526 </seglistitem>
527 </segmentedlist>
528
529 <variablelist>
530 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
531 <?dbfo list-presentation="list"?>
532 <?dbhtml list-presentation="table"?>
533
534 <varlistentry id="dbus-cleanup-sockets">
535 <term><command>dbus-cleanup-sockets</command></term>
536 <listitem>
537 <para>
538 is used to clean up leftover sockets in a directory.
539 </para>
540 <indexterm zone="dbus dbus-cleanup-sockets">
541 <primary sortas="b-dbus-cleanup-sockets">dbus-cleanup-sockets</primary>
542 </indexterm>
543 </listitem>
544 </varlistentry>
545
546 <varlistentry id="dbus-daemon">
547 <term><command>dbus-daemon</command></term>
548 <listitem>
549 <para>
550 is the <application>D-Bus</application> message bus daemon.
551 </para>
552 <indexterm zone="dbus dbus-daemon">
553 <primary sortas="b-dbus-daemon">dbus-daemon</primary>
554 </indexterm>
555 </listitem>
556 </varlistentry>
557
558 <varlistentry id="dbus-launch">
559 <term><command>dbus-launch</command></term>
560 <listitem>
561 <para>
562 is used to start <command>dbus-daemon</command> from a shell
563 script. It would normally be called from a user's login
564 scripts.
565 </para>
566 <indexterm zone="dbus dbus-launch">
567 <primary sortas="b-dbus-launch">dbus-launch</primary>
568 </indexterm>
569 </listitem>
570 </varlistentry>
571
572 <varlistentry id="dbus-monitor">
573 <term><command>dbus-monitor</command></term>
574 <listitem>
575 <para>
576 is used to monitor messages going through a
577 <application>D-Bus</application> message bus.
578 </para>
579 <indexterm zone="dbus dbus-monitor">
580 <primary sortas="b-dbus-monitor">dbus-monitor</primary>
581 </indexterm>
582 </listitem>
583 </varlistentry>
584
585 <varlistentry id="dbus-run-session">
586 <term><command>dbus-run-session</command></term>
587 <listitem>
588 <para>
589 start a process as a new <application>D-Bus</application> session.
590 </para>
591 <indexterm zone="dbus dbus-run-session">
592 <primary sortas="b-dbus-run-session">dbus-run-session</primary>
593 </indexterm>
594 </listitem>
595 </varlistentry>
596
597 <varlistentry id="dbus-send">
598 <term><command>dbus-send</command></term>
599 <listitem>
600 <para>
601 is used to send a message to a <application>D-Bus</application>
602 message bus.
603 </para>
604 <indexterm zone="dbus dbus-send">
605 <primary sortas="b-dbus-send">dbus-send</primary>
606 </indexterm>
607 </listitem>
608 </varlistentry>
609
610 <varlistentry id="dbus-test-tool">
611 <term><command>dbus-test-tool</command></term>
612 <listitem>
613 <para>
614 is a <application>D-Bus</application> traffic generator and test
615 tool; it is a multi-purpose tool for debugging and profiling
616 <application>D-Bus</application>.
617 </para>
618 <indexterm zone="dbus dbus-test-tool">
619 <primary sortas="b-dbus-test-tool">dbus-test-tool</primary>
620 </indexterm>
621 </listitem>
622 </varlistentry>
623
624 <varlistentry id="dbus-update-activation-environment">
625 <term><command>dbus-update-activation-environment</command></term>
626 <listitem>
627 <para>
628 is used to update the environment used for
629 <application>D-Bus</application> session services;
630 it updates the list of environment variables used by
631 <command>dbus-daemon --session</command> when it activates session
632 services without using systemd.
633 </para>
634 <indexterm zone="dbus dbus-update-activation-environment">
635 <primary sortas="b-dbus-update-activation-environment">
636 dbus-update-activation-environment</primary>
637 </indexterm>
638 </listitem>
639 </varlistentry>
640
641 <varlistentry id="dbus-uuidgen">
642 <term><command>dbus-uuidgen</command></term>
643 <listitem>
644 <para>
645 is used to generate a universally unique ID.
646 </para>
647 <indexterm zone="dbus dbus-uuidgen">
648 <primary sortas="b-dbus-uuidgen">dbus-uuidgen</primary>
649 </indexterm>
650 </listitem>
651 </varlistentry>
652
653 <varlistentry id="libdbus-1">
654 <term><filename class="libraryfile">libdbus-1.so</filename></term>
655 <listitem>
656 <para>
657 contains the API functions used by the
658 <application>D-Bus</application> message daemon.
659 <application>D-Bus</application> is first a library that provides
660 one-to-one communication between any two applications;
661 <command>dbus-daemon</command> is an application that uses this
662 library to implement a message bus daemon.
663 </para>
664 <indexterm zone="dbus libdbus-1">
665 <primary sortas="c-libdbus-1">libdbus-1.so</primary>
666 </indexterm>
667 </listitem>
668 </varlistentry>
669
670 </variablelist>
671
672 </sect2>
673
674 <sect2 role="content" revision="systemd">
675 <title>Contents</title>
676
677 <para>
678 A list of the installed files, along with their short
679 descriptions can be found at
680 <ulink url="&lfs-rootd;/chapter06/dbus.html#contents-dbus"/>.
681 </para>
682
683 </sect2>
684
685
686</sect1>
687
Note: See TracBrowser for help on using the repository browser.