source: general/sysutils/dbus.xml@ 07499ecc

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 07499ecc was 9eb7ee7, checked in by Bruce Dubbs <bdubbs@…>, 6 years ago

Update to bluez-5.50.
Update to libical-3.0.4.
Tags

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