source: general/sysutils/dbus.xml@ bc3bb455

10.0 10.1 11.0 9.0 9.1 ken/refactor-virt lazarus qt5new trunk xry111/git-date xry111/git-date-for-trunk xry111/git-date-test
Last change on this file since bc3bb455 was bc3bb455, checked in by Bruce Dubbs <bdubbs@…>, 2 years ago

Clarify order of dbus, elogind, an dxorg libs

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

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