source: general/sysutils/dbus.xml@ 3b40dbb3

10.0 10.1 11.0 11.1 11.2 11.3 12.0 12.1 8.4 9.0 9.1 bdubbs/svn elogind kea ken/TL2024 ken/inkscape-core-mods ken/tuningfonts lazarus lxqt 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 3b40dbb3 was 3b40dbb3, checked in by Douglas R. Reno <renodr@…>, 5 years ago

Update to dbus-1.12.12
Update to polkit-0.115

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

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