source: general/sysutils/dbus.xml@ 40c00c5

12.0 12.1 kea ken/TL2024 ken/tuningfonts lazarus lxqt plabs/newcss python3.11 qt5new rahul/power-profiles-daemon renodr/vulkan-addition trunk xry111/llvm18 xry111/xf86-video-removal
Last change on this file since 40c00c5 was 30b01dbd, checked in by Xi Ruoyao <xry111@…>, 15 months ago

dbus: Demote systemd dependency and clarify what it is for

  • Property mode set to 100644
File size: 25.2 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.xz">
8 <!ENTITY dbus-download-ftp " ">
9 <!ENTITY dbus-md5sum "e809d7aa905ad82adeaf1d59db5445b1">
10 <!ENTITY dbus-size "1.3 MB">
11 <!ENTITY dbus-buildsize "23 MB (add 20 MB for tests)">
12 <!ENTITY dbus-time "0.2 SBU (add 1.7 SBU for tests)">
13 <!-- The former value was 0.8 SBU, which was far more sensible. -->
14 <!-- I got 'real 0m14.355s' for make check at -j1; bdubbs dbus-1.14.2 -->
15 <!-- Now 'real 2m51.642ss' for make check at -j1; bdubbs dbus-1.14.6
16# TOTAL: 217
17# PASS: 217
18 -->
19]>
20
21<sect1 id="dbus" xreflabel="dbus-&dbus-version;">
22 <?dbhtml filename="dbus.html"?>
23
24
25 <title>dbus-&dbus-version;</title>
26
27 <indexterm zone="dbus">
28 <primary sortas="a-D-Bus">D-Bus</primary>
29 </indexterm>
30
31 <sect2 role="package">
32 <title>Introduction to D-Bus</title>
33
34 <para revision="sysv">
35 <application>D-Bus</application> is a message bus system, a simple way
36 for applications to talk to one another.
37 <application>D-Bus</application> supplies both a system daemon (for
38 events such as <quote>new hardware device added</quote> or <quote>printer
39 queue changed</quote>) and a per-user-login-session daemon (for general
40 IPC needs among user applications). Also, the message bus is built on top
41 of a general one-to-one message passing framework, which can be used by
42 any two applications to communicate directly (without going through the
43 message bus daemon).
44 </para>
45
46 <para revision="systemd">
47 Even though <application>D-Bus</application> was built in LFS, there are
48 some features provided by the package that other BLFS packages need, but
49 their dependencies didn't fit into LFS.
50 </para>
51
52 &lfs113_checked;
53
54 <bridgehead renderas="sect3">Package Information</bridgehead>
55 <itemizedlist spacing="compact">
56 <listitem>
57 <para>
58 Download (HTTP): <ulink url="&dbus-download-http;"/>
59 </para>
60 </listitem>
61 <listitem>
62 <para>
63 Download (FTP): <ulink url="&dbus-download-ftp;"/>
64 </para>
65 </listitem>
66 <listitem>
67 <para>
68 Download MD5 sum: &dbus-md5sum;
69 </para>
70 </listitem>
71 <listitem>
72 <para>
73 Download size: &dbus-size;
74 </para>
75 </listitem>
76 <listitem>
77 <para>
78 Estimated disk space required: &dbus-buildsize;
79 </para>
80 </listitem>
81 <listitem>
82 <para>
83 Estimated build time: &dbus-time;
84 </para>
85 </listitem>
86 </itemizedlist>
87
88 <bridgehead renderas="sect3">D-Bus Dependencies</bridgehead>
89
90 <bridgehead renderas="sect4">Recommended</bridgehead>
91 <para role="recommended">
92 <xref linkend="xorg7-lib"/> (for <command>dbus-launch</command> program)
93 <!-- elogind cannot be used by dbus: dbus only uses the systemd service,
94 not the logind one
95 <phrase revision="sysv">and <xref linkend="elogind"/> (These are
96 circular dependencies. First build without them, and then again after
97 both packages are installed.)</phrase>-->
98 </para>
99
100 <bridgehead renderas="sect4">Optional</bridgehead>
101 <para role="optional">
102 <phrase revision="systemd"><xref role="runtime" linkend="systemd"/>
103 (for registering services launched by D-Bus session daemon as systemd
104 user services);</phrase>
105 For the tests:
106 <xref linkend="dbus-python"/>,
107 <xref linkend="pygobject3"/>,
108 and <xref linkend="valgrind"/>;
109
110 for documentation:
111 <xref linkend="doxygen"/>,
112 <xref linkend="xmlto"/>,
113 <ulink url="https://pypi.python.org/pypi/mallard-ducktype">Ducktype</ulink>,
114 and
115 <ulink url="&gnome-download-http;/yelp-tools/">Yelp Tools</ulink>
116 </para>
117
118 <para condition="html" role="usernotes">User Notes:
119 <ulink url="&blfs-wiki;/dbus"/>
120 </para>
121 </sect2>
122
123 <sect2 role="installation">
124 <title>Installation of D-Bus</title>
125 <!--
126 <para revision="sysv">
127 If they do not already exist,
128 as the <systemitem class="username">root</systemitem> user, create a
129 system user and group to handle the system message bus activity:
130 </para>
131
132<screen role="root" revision="sysv"><userinput>groupadd -g 18 messagebus &amp;&amp;
133useradd -c "D-Bus Message Daemon User" -d /var/run/dbus \
134 -u 18 -g messagebus -s /bin/false messagebus</userinput></screen>
135 -->
136
137 <para>
138 Install <application>D-Bus</application> by running the following
139 commands (you may wish to review the output from <command>./configure
140 --help</command> first and add any desired parameters to the
141 <command>configure</command> command shown below):
142 </para>
143
144 <!-- Only usefull for systemd: it installs the services files in the
145 systemd/user
146 - -enable-user-session \ -->
147<screen revision="sysv"><userinput>./configure --prefix=/usr \
148 --sysconfdir=/etc \
149 --localstatedir=/var \
150 --runstatedir=/run \
151 --disable-doxygen-docs \
152 --disable-xml-docs \
153 --disable-static \
154 --with-systemduserunitdir=no \
155 --with-systemdsystemunitdir=no \
156 --docdir=/usr/share/doc/dbus-&dbus-version; \
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 --runstatedir=/run \
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-system-socket=/run/dbus/system_bus_socket &amp;&amp;
170make</userinput></screen>
171
172 <para>
173 See below for test instructions.
174 </para>
175
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
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<!-- FIXME: No longer needed with usr merge
200 <para>
201 The shared library needs to be moved to
202 <filename class="directory">/lib</filename>, and as a result the
203 <filename class="extension">.so</filename> file in
204 <filename class="directory">/usr/lib</filename> will need to be
205 recreated. Run the following command as the
206 <systemitem class="username">root</systemitem> user:
207 </para>
208
209<screen role="root"><userinput>mv -v /usr/lib/libdbus-1.so.* /lib &amp;&amp;
210ln -sfv ../../lib/$(readlink /usr/lib/libdbus-1.so) /usr/lib/libdbus-1.so</userinput></screen>
211-->
212
213 <para>
214 If you are using a DESTDIR install,
215 <command>dbus-daemon-launch-helper</command> needs to be fixed
216 afterwards. Issue, as <systemitem class="username">root</systemitem>
217 user:
218 </para>
219
220<screen role="root"><userinput>chown -v root:messagebus /usr/libexec/dbus-daemon-launch-helper &amp;&amp;
221chmod -v 4750 /usr/libexec/dbus-daemon-launch-helper</userinput></screen>
222
223 <para revision="sysv">
224 If you are still building your system in chroot or you did not start the
225 daemon yet, but you want to compile some packages that require
226 <application>D-Bus</application>, generate the
227 <application>D-Bus</application> UUID to avoid warnings when compiling
228 some packages with the following command as the
229 <systemitem class="username">root</systemitem> user:
230 </para>
231
232<screen role="root" revision="sysv"><userinput>dbus-uuidgen --ensure</userinput></screen>
233
234 <para revision="sysv">
235 If using <xref linkend="elogind"/>, create a symlink to the
236 <filename>/var/lib/dbus/machine-id</filename> file:
237 </para>
238
239<screen role="root" revision="sysv"><userinput>ln -sfv /var/lib/dbus/machine-id /etc</userinput></screen>
240
241<!--
242 <para revision="systemd">
243 If not in chroot, at this point, you should reload the systemd daemon,
244 and reenter multi-user mode with the following commands (as the
245 <systemitem class="username">root</systemitem> user):
246 </para>
247
248<screen role="root" revision="systemd"><userinput>systemctl daemon-reload
249systemctl start multi-user.target</userinput></screen>
250-->
251
252 <para>
253 The dbus tests cannot be run until after <xref linkend="dbus-python"/>
254 and <xref linkend="pygobject3"/> have
255 been installed. They must be run as an unprivileged user from a local
256 session with bus address. To run the standard tests issue
257 <command>make check</command>.
258 </para>
259
260 <para>
261 If you want to run the unit regression tests, configure requires
262 additional parameters which expose additional functionality in the
263 binaries that are not intended to be used in a production build of
264 <application>D-Bus</application>. If you would like to run the tests,
265 issue the following commands (for the tests, you don't need to build the
266 docs):
267 </para>
268
269<screen remap="test"><userinput>make distclean &amp;&amp;
270PYTHON=python3 ./configure --enable-tests \
271 --enable-asserts \
272 --disable-doxygen-docs \
273 --disable-xml-docs &amp;&amp;
274make &amp;&amp;
275make check</userinput></screen>
276
277 <para>
278 There have been reports that the tests may fail if running inside a
279 Midnight Commander shell. You may get out-of-memory error messages when
280 running the tests. These are normal and can be safely ignored.
281 </para>
282
283 </sect2>
284
285 <sect2 role="commands">
286 <title>Command Explanations</title>
287
288 <para>
289 <parameter>--disable-doxygen-docs</parameter>: This switch disables
290 doxygen documentation build and install, if you have
291 <application>doxygen</application> installed. If
292 <application>doxygen</application> is installed, and you wish to build
293 them, remove this parameter.
294 </para>
295
296 <para>
297 <parameter>--disable-xml-docs</parameter>: This switch disables html
298 documentation build and install, if you have
299 <application>xmlto</application> installed. If
300 <application>xmlto</application> is installed, and you wish to build
301 them, remove this parameter.
302 </para>
303
304 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
305 href="../../xincludes/static-libraries.xml"/>
306
307 <para>
308 <parameter>--enable-user-session</parameter>: This parameter enables
309 per-user DBus sessions with
310 <phrase revision="sysv"><application>elogind</application>.</phrase>
311 <phrase revision="systemd"><application>systemd</application>.</phrase>
312 </para>
313
314 <para revision="sysv">
315 <parameter>--with-systemd{user,system}unitdir=no</parameter>: These
316 switches disable installation of systemd units on elogind based systems.
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>: Builds 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>: Builds 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>: Enables 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>gdm</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-x11</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 <!-- KDM is no longer usable, SDDM is it's replacement
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
503 </itemizedlist>
504
505 </sect3>
506
507 </sect2>
508
509 <sect2 role="content" revision="sysv">
510 <title>Contents</title>
511
512 <segmentedlist>
513 <segtitle>Installed Programs</segtitle>
514 <segtitle>Installed Library</segtitle>
515 <segtitle>Installed Directories</segtitle>
516
517 <seglistitem>
518 <seg>
519 dbus-cleanup-sockets, dbus-daemon, dbus-launch, dbus-monitor,
520 dbus-run-session, dbus-send, dbus-test-tool,
521 dbus-update-activation-environment, and dbus-uuidgen
522 </seg>
523 <seg>
524 libdbus-1.so
525 </seg>
526 <seg>
527 /etc/dbus-1,
528 /usr/{include,lib}/dbus-1.0,
529 /usr/lib/cmake/DBus1,
530 /usr/share/dbus-1,
531 /usr/share/xml/dbus-1,
532 /usr/share/doc/dbus-&dbus-version;, and
533 /var/{lib,run}/dbus
534 </seg>
535 </seglistitem>
536 </segmentedlist>
537
538 <variablelist>
539 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
540 <?dbfo list-presentation="list"?>
541 <?dbhtml list-presentation="table"?>
542
543 <varlistentry id="dbus-cleanup-sockets">
544 <term><command>dbus-cleanup-sockets</command></term>
545 <listitem>
546 <para>
547 is used to clean up leftover sockets in a directory
548 </para>
549 <indexterm zone="dbus dbus-cleanup-sockets">
550 <primary sortas="b-dbus-cleanup-sockets">dbus-cleanup-sockets</primary>
551 </indexterm>
552 </listitem>
553 </varlistentry>
554
555 <varlistentry id="dbus-daemon">
556 <term><command>dbus-daemon</command></term>
557 <listitem>
558 <para>
559 is the <application>D-Bus</application> message bus daemon
560 </para>
561 <indexterm zone="dbus dbus-daemon">
562 <primary sortas="b-dbus-daemon">dbus-daemon</primary>
563 </indexterm>
564 </listitem>
565 </varlistentry>
566
567 <varlistentry id="dbus-launch">
568 <term><command>dbus-launch</command></term>
569 <listitem>
570 <para>
571 is used to start <command>dbus-daemon</command> from a shell
572 script. It would normally be called from a user's login
573 scripts
574 </para>
575 <indexterm zone="dbus dbus-launch">
576 <primary sortas="b-dbus-launch">dbus-launch</primary>
577 </indexterm>
578 </listitem>
579 </varlistentry>
580
581 <varlistentry id="dbus-monitor">
582 <term><command>dbus-monitor</command></term>
583 <listitem>
584 <para>
585 is used to monitor messages going through a
586 <application>D-Bus</application> message bus
587 </para>
588 <indexterm zone="dbus dbus-monitor">
589 <primary sortas="b-dbus-monitor">dbus-monitor</primary>
590 </indexterm>
591 </listitem>
592 </varlistentry>
593
594 <varlistentry id="dbus-run-session">
595 <term><command>dbus-run-session</command></term>
596 <listitem>
597 <para>
598 starts a process as a new <application>D-Bus</application> session
599 </para>
600 <indexterm zone="dbus dbus-run-session">
601 <primary sortas="b-dbus-run-session">dbus-run-session</primary>
602 </indexterm>
603 </listitem>
604 </varlistentry>
605
606 <varlistentry id="dbus-send">
607 <term><command>dbus-send</command></term>
608 <listitem>
609 <para>
610 is used to send a message to a <application>D-Bus</application>
611 message bus
612 </para>
613 <indexterm zone="dbus dbus-send">
614 <primary sortas="b-dbus-send">dbus-send</primary>
615 </indexterm>
616 </listitem>
617 </varlistentry>
618
619 <varlistentry id="dbus-test-tool">
620 <term><command>dbus-test-tool</command></term>
621 <listitem>
622 <para>
623 is a <application>D-Bus</application> traffic generator and test
624 tool; it is a multi-purpose tool for debugging and profiling
625 <application>D-Bus</application>
626 </para>
627 <indexterm zone="dbus dbus-test-tool">
628 <primary sortas="b-dbus-test-tool">dbus-test-tool</primary>
629 </indexterm>
630 </listitem>
631 </varlistentry>
632
633 <varlistentry id="dbus-update-activation-environment">
634 <term><command>dbus-update-activation-environment</command></term>
635 <listitem>
636 <para>
637 is used to update the environment used for
638 <application>D-Bus</application> session services;
639 it updates the list of environment variables used by
640 <command>dbus-daemon --session</command> when it activates session
641 services without using systemd
642 </para>
643 <indexterm zone="dbus dbus-update-activation-environment">
644 <primary sortas="b-dbus-update-activation-environment">
645 dbus-update-activation-environment</primary>
646 </indexterm>
647 </listitem>
648 </varlistentry>
649
650 <varlistentry id="dbus-uuidgen">
651 <term><command>dbus-uuidgen</command></term>
652 <listitem>
653 <para>
654 is used to generate a universally unique ID
655 </para>
656 <indexterm zone="dbus dbus-uuidgen">
657 <primary sortas="b-dbus-uuidgen">dbus-uuidgen</primary>
658 </indexterm>
659 </listitem>
660 </varlistentry>
661
662 <varlistentry id="libdbus-1">
663 <term><filename class="libraryfile">libdbus-1.so</filename></term>
664 <listitem>
665 <para>
666 contains the API functions used by the
667 <application>D-Bus</application> message daemon.
668 <application>D-Bus</application> is first a library that provides
669 one-to-one communication between any two applications;
670 <command>dbus-daemon</command> is an application that uses this
671 library to implement a message bus daemon
672 </para>
673 <indexterm zone="dbus libdbus-1">
674 <primary sortas="c-libdbus-1">libdbus-1.so</primary>
675 </indexterm>
676 </listitem>
677 </varlistentry>
678
679 </variablelist>
680
681 </sect2>
682
683 <sect2 role="content" revision="systemd">
684 <title>Contents</title>
685
686 <para>
687 A list of the installed files, along with their short
688 descriptions can be found at
689 <ulink url="&lfs-root;/chapter08/dbus.html#contents-dbus"/>.
690 </para>
691
692 </sect2>
693
694</sect1>
Note: See TracBrowser for help on using the repository browser.