source: general/sysutils/hal.xml@ 50740915

10.0 10.1 11.0 11.1 11.2 11.3 12.0 12.1 6.3 6.3-rc1 6.3-rc2 6.3-rc3 7.10 7.4 7.5 7.6 7.6-blfs 7.6-systemd 7.7 7.8 7.9 8.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind gnome kde5-13430 kde5-14269 kde5-14686 kea ken/TL2024 ken/inkscape-core-mods ken/tuningfonts krejzi/svn lazarus lxqt nosym perl-modules plabs/newcss plabs/python-mods python3.11 qt5new rahul/power-profiles-daemon renodr/vulkan-addition systemd-11177 systemd-13485 trunk upgradedb xry111/intltool xry111/llvm18 xry111/soup3 xry111/test-20220226 xry111/xf86-video-removal
Last change on this file since 50740915 was 50740915, checked in by Alexander E. Patrakov <alexander@…>, 17 years ago

Made Python an optional dependency of HAL instead of a required one

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

  • Property mode set to 100644
File size: 24.9 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 hal-download-http "http://freedesktop.org/~david/dist/hal-&hal-version;.tar.gz">
8 <!ENTITY hal-download-ftp "ftp://ftp.fu-berlin.de/unix/linux/mirrors/gentoo/distfiles/hal-&hal-version;.tar.gz">
9 <!ENTITY hal-md5sum "d7a7741808ba130f8aff3f5d3b5689e4">
10 <!ENTITY hal-size "1.5 MB">
11 <!ENTITY hal-buildsize "19.0 MB">
12 <!ENTITY hal-time "0.5 SBU">
13]>
14
15<sect1 id="hal" xreflabel="HAL-&hal-version;">
16 <?dbhtml filename="hal.html"?>
17
18 <sect1info>
19 <othername>$LastChangedBy$</othername>
20 <date>$Date$</date>
21 </sect1info>
22
23 <title>HAL-&hal-version;</title>
24
25 <indexterm zone="hal">
26 <primary sortas="a-HAL">HAL</primary>
27 </indexterm>
28
29 <sect2 role="package">
30 <title>Introduction to HAL</title>
31
32 <para><application>HAL</application> is a hardware abstraction layer, which
33 is a piece of software that provides a view of the various hardware
34 attached to a system. In addition to this, <application>HAL</application>
35 keeps detailed metadata for each piece of hardware and provides hooks such
36 that system and desktop-level software can react to changes in the hardware
37 configuration in order to maintain system policy.</para>
38
39 <para>The most important goal of <application>HAL</application> is to
40 provide plug-and-play facilities for UNIX-like desktops with focus on
41 providing a rich and extensible description of device characteristics and
42 features. One example of the functionality provided by
43 <application>HAL</application> is when you plug in a USB storage device.
44 <application>HAL</application> can automatically create a mount point in
45 <filename class="directory">/media</filename> and mount the device.</para>
46
47 <bridgehead renderas="sect3">Package Information</bridgehead>
48 <itemizedlist spacing="compact">
49 <listitem>
50 <para>Download (HTTP): <ulink url="&hal-download-http;"/></para>
51 </listitem>
52 <listitem>
53 <para>Download (FTP): <ulink url="&hal-download-ftp;"/></para>
54 </listitem>
55 <listitem>
56 <para>Download MD5 sum: &hal-md5sum;</para>
57 </listitem>
58 <listitem>
59 <para>Download size: &hal-size;</para>
60 </listitem>
61 <listitem>
62 <para>Estimated disk space required: &hal-buildsize;</para>
63 </listitem>
64 <listitem>
65 <para>Estimated build time: &hal-time;</para>
66 </listitem>
67 </itemizedlist>
68
69 <bridgehead renderas="sect3">HAL Dependencies</bridgehead>
70
71 <bridgehead renderas="sect4">Required</bridgehead>
72 <para role="required"><xref linkend="glib2"/>,
73 <xref linkend="dbus"/> (see the <xref linkend="hal-requirements"/>), and
74 <xref linkend="perl-xml-parser"/></para>
75
76 <bridgehead renderas="sect4">Recommended</bridgehead>
77 <para role="recommended"><xref linkend="pciutils"/>
78 (with a current <filename>pci.ids</filename> file) and
79 <xref linkend="usbutils"/>
80 (with a current <filename>usb.ids</filename> file)</para>
81
82 <bridgehead renderas="sect4">Optional</bridgehead>
83 <para role="optional"><xref linkend="pkgconfig"/>,
84 <xref linkend="python"/>,
85 <xref linkend="intltool"/>,
86 <xref linkend="libusb"/>,
87 <xref linkend="doxygen"/>, and
88 <xref linkend="docbook-utils"/></para>
89
90 <para condition="html" role="usernotes">User Notes:
91 <ulink url="&blfs-wiki;/hal"/></para>
92
93 </sect2>
94
95 <sect2 role="installation">
96 <title>Installation of HAL</title>
97
98 <para>You must create a dedicated user and group before installing the
99 package. Though the default BLFS instructions run the
100 <application>HAL</application> daemon as the
101 <systemitem class="username">root</systemitem> user, a configuration file
102 is installed which has the dedicated user's name hard-coded in it. This
103 causes a confusing message to be generated when starting the
104 <application>D-BUS</application> daemon. Issue the following commands as
105 the <systemitem class="username">root</systemitem> user:</para>
106
107<screen role="root"><userinput>groupadd -g 19 haldaemon &amp;&amp;
108useradd -c "HAL Daemon User" -d /dev/null -u 19 \
109 -g haldaemon -s /bin/false haldaemon</userinput></screen>
110
111 <para>If you don't have <application>Python</application> installed,
112 suppress the installation of <command>hal-device-manager</command> and
113 the compile-time check for <application>Python</application>:</para>
114
115<screen><userinput>sed -i 's/device-manager//g' tools/Makefile.in &amp;&amp;
116PYTHON=false ./configure --prefix=/usr \
117 --sysconfdir=/etc \
118 --libexecdir=/usr/lib/hal \
119 --localstatedir=/var &amp;&amp;
120make
121</userinput></screen>
122
123 <para>Otherwise, install <application>HAL</application> by running the
124 following commands:</para>
125
126<screen><userinput>./configure --prefix=/usr \
127 --sysconfdir=/etc \
128 --libexecdir=/usr/lib/hal \
129 --localstatedir=/var &amp;&amp;
130make</userinput></screen>
131
132 <para>To test the results, issue <command>make check</command>.</para>
133
134 <para>Now, as the <systemitem class="username">root</systemitem> user:</para>
135
136<screen role="root"><userinput>make install &amp;&amp;
137install -v -m755 -d /var/run/hald</userinput></screen>
138
139 </sect2>
140
141 <sect2 role="commands">
142 <title>Command Explanations</title>
143
144 <para><parameter>--libexecdir=/usr/lib/hal</parameter>: This parameter
145 forces the installation of libexec files to
146 <filename class='directory'>/usr/lib/hal</filename> instead of
147 <filename class='directory'>/usr/libexec</filename>.</para>
148
149 <para><parameter>--localstatedir=/var</parameter>: This parameter forces
150 the creation of the <filename>pid</filename> file to
151 <filename class='directory'>/var/run/hald</filename> instead of
152 <filename class='directory'>/usr/var/run/hald</filename>.</para>
153
154 </sect2>
155
156 <sect2 id="hal-runtime-dependencies" xreflabel="GNOME-Python">
157 <title>Run-Time Dependencies</title>
158
159 <para>The <xref linkend="hal-device-manager"/> program requires several
160 additional packages to be installed before it will run. The list is
161 significant and requires a substantial commitment to install them. It is
162 left up to you to determine if the time and effort spent installing the
163 following packages is worth using the <command>hal-device-manager</command>
164 program.</para>
165
166 <para>Though the only requirement to run the
167 <command>hal-device-manager</command> program is installing
168 <ulink url="&gnome-download-http;/gnome-python/">
169 GNOME-Python</ulink>, the dependency list is staggering. The following
170 list does not include the dependencies already identified in the BLFS
171 book. For example, <application>libgnome</application> already lists
172 <application>GNOME VFS</application>, <application>GConf</application>,
173 etc., so they are not repeated here. Note that some of the dependencies
174 have their own dependencies, which have their own, and so forth and so
175 on.</para>
176
177 <itemizedlist>
178 <listitem>
179 <para><ulink
180 url="&gnome-download-http;/gnome-python/">GNOME-Python</ulink>
181 </para>
182
183 <itemizedlist>
184 <listitem>
185 <para><ulink
186 url="http://www.pygtk.org/">PyGTK</ulink> (required)
187 </para>
188
189 <itemizedlist>
190 <listitem>
191 <para><ulink
192 url="http://www.cairographics.org/pycairo">Pycairo</ulink> (optional)
193 </para>
194
195 <itemizedlist>
196 <listitem>
197 <para><ulink
198 url="http://www.cairographics.org/snapshots/">libsvg-cairo</ulink> (optional)
199 </para>
200
201 <itemizedlist>
202 <listitem>
203 <para><ulink
204 url="http://www.cairographics.org/snapshots/">libsvg</ulink> (required)
205 </para>
206 </listitem>
207 </itemizedlist>
208
209 </listitem>
210 <listitem>
211 <para><ulink
212 url="http://www.pygtk.org/">PyGTK</ulink> (optional, and circular)
213 </para>
214 </listitem>
215 <listitem>
216 <para><ulink
217 url="http://sourceforge.net/projects/numpy">Numerical Python</ulink> (optional)
218 </para>
219 </listitem>
220 </itemizedlist>
221
222 </listitem>
223 <listitem>
224 <para><ulink
225 url="http://sourceforge.net/projects/numpy">Numerical Python</ulink> (optional)
226 </para>
227 </listitem>
228 <listitem>
229 <para><xref linkend="libglade"/> (required)</para>
230 </listitem>
231 </itemizedlist>
232
233 </listitem>
234 <listitem>
235 <para><xref linkend="libgnomeui"/> (optional)</para>
236 </listitem>
237 <listitem>
238 <para><xref linkend="libgnome"/> (required)</para>
239 </listitem>
240 <listitem>
241 <para><ulink
242 url="&gnome-download-http;/pyorbit/">PyORBit</ulink> (optional)
243 </para>
244
245 <itemizedlist>
246 <listitem>
247 <para><xref linkend="ORBit2"/> (required)</para>
248 </listitem>
249 </itemizedlist>
250
251 </listitem>
252 </itemizedlist>
253
254 </listitem>
255 </itemizedlist>
256
257 <note>
258 <para>The dependency list is designed to start at the bottom and work
259 your way up until the last package to install is
260 <application>GNOME-Python</application>. Note that the dependencies
261 marked as <quote>required</quote> are required for the package it is
262 listed under. For example, you don't need to install
263 <application>ORBit</application> if you don't plan on installing
264 <application>PyORBit</application>. The minimum packages you could
265 install to support running <xref linkend="hal-device-manager"/> would be
266 (in this order): <xref linkend="libgnome"/>, <xref linkend="libglade"/>,
267 <ulink url="http://www.pygtk.org/">PyGTK</ulink> and <ulink
268 url="&gnome-download-http;/gnome-python/">
269 GNOME-Python</ulink>.</para>
270 </note>
271
272 </sect2>
273
274 <sect2 role="configuration">
275 <title>Configuring HAL</title>
276
277 <sect3 id="hal-config">
278 <title>Config Files</title>
279 <para><filename>/etc/dbus-1/system.d/hal.conf</filename>,
280 <filename>/etc/dbus-1/system.d/halusers.conf</filename> and
281 <filename>/etc/hal/*</filename></para>
282
283 <indexterm zone="hal hal-config">
284 <primary sortas="e-etc-dbus-1-system.d-hal.conf">/etc/dbus-1/system.d/hal.conf</primary>
285 </indexterm>
286
287 <indexterm zone="hal hal-config">
288 <primary sortas="e-etc-dbus-1-system.d-halusers.conf">/etc/dbus-1/system.d/halusers.conf</primary>
289 </indexterm>
290
291 <indexterm zone="hal hal-config">
292 <primary sortas="e-etc-hal-star">/etc/hal/*</primary>
293 </indexterm>
294 </sect3>
295
296 <sect3><title>Configuration Information</title>
297
298 <para>The default setup for <application>HAL</application> is to allow
299 only certain users to invoke methods such as Mount(). These are
300 the <systemitem class="username">root</systemitem> user and the user
301 determined to be at the active console using <ulink
302 url="&blfs-wiki;/linux-pam">pam_console</ulink>. If you are not set
303 up to use <xref linkend="linux-pam"/> and <ulink
304 url="&blfs-wiki;/linux-pam">pam_console</ulink>, create a group that
305 is allowed to invoke <application>HAL</application> methods with the
306 following commands:</para>
307
308<screen role="root"><userinput>groupadd -g 61 halusers &amp;&amp;
309cat &gt; /etc/dbus-1/system.d/halusers.conf &lt;&lt; "EOF"
310<literal>&lt;!DOCTYPE busconfig PUBLIC
311 "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
312 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd"&gt;
313&lt;busconfig&gt;
314
315 &lt;!-- Allow users in the halusers group invoke HAL methods --&gt;
316 &lt;policy group="halusers"&gt;
317 &lt;allow send_interface="org.freedesktop.Hal.Device.SystemPowerManagement"/&gt;
318 &lt;allow send_interface="org.freedesktop.Hal.Device.LaptopPanel"/&gt;
319 &lt;allow send_interface="org.freedesktop.Hal.Device.Volume"/&gt;
320 &lt;allow send_interface="org.freedesktop.Hal.Device.Volume.Crypto"/&gt;
321 &lt;/policy&gt;
322
323&lt;/busconfig&gt;</literal>
324EOF</userinput></screen>
325
326 <para>Now add the users you would like to the <systemitem
327 class="groupname">halusers</systemitem> group to use
328 <application>HAL</application>. Note that these users still need
329 to have appropriate permissions to access the devices that
330 <application>HAL</application> will invoke its methods on.</para>
331
332 <para>With the above configuration in place, authorized users now
333 have the ability to unmount disk partitions mounted at non-standard
334 locations such as <filename class='directory'>/pub</filename>. If
335 you'd like to restrict this policy to only drives which are considered
336 removable or hotpluggable, add the following configuration file as
337 the <systemitem class='username'>root</systemitem> user:</para>
338
339<screen role="root"><userinput>cat &gt; /etc/hal/fdi/policy/no-fixed-drives.fdi &lt;&lt; "EOF"
340<literal>&lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;!-- -*- SGML -*- --&gt;
341
342&lt;!-- Don't allow HAL methods on disks that are not
343 removable or hotpluggable --&gt;
344
345&lt;deviceinfo version="0.2"&gt;
346&lt;device&gt;
347 &lt;match key="@block.storage_device:storage.hotpluggable" bool="false"&gt;
348 &lt;match key="@block.storage_device:storage.removable" bool="false"&gt;
349 &lt;merge key="volume.ignore" type="bool"&gt;true&lt;/merge&gt;
350 &lt;/match&gt;
351 &lt;/match&gt;
352&lt;/device&gt;
353&lt;/deviceinfo&gt;</literal>
354EOF</userinput></screen>
355
356 <para><application>HAL</application> only provides the methods such
357 as Mount() to act on hardware. In order to take advantage of these,
358 a <application>HAL</application> event handler such as
359 <xref linkend="gnome-volume-manager"/> or <ulink
360 url="http://ivman.sourceforge.net/">Ivman</ulink> should be
361 installed.</para>
362
363 <!-- Following note is only relevant for HAL-0.5.7.x.
364 Fixed upstream. -->
365 <note>
366 <para><application>HAL</application> will ignore any devices listed
367 in <filename>/etc/fstab</filename> for the purpose of automounting.
368 You must remove any listings for devices that you would like
369 automounted such as CD-ROMs or USB keys.</para>
370 </note>
371
372 <!-- This section commented out for now until it is determined what should
373 be placed in this section
374
375 FIXME: I think this information is still relevant with the
376 exception of its interaction with /etc/fstab. Needs investigation.
377
378 <para>No configuration is necessary for the majority of installations
379 on systems configured with ISO-8859-1 compatible locales. The defaults
380 should work just fine. For some installations, tweaking of the various
381 policies may be required. One such configuration change necessary in some
382 locales is identifying the <option>iocharset</option> and
383 <option>codepage</option> variables in the
384 <filename>/etc/fstab</filename> entries created by the
385 <command>fstab-sync</command> program. If changes are required to the
386 configuration so that your locale is properly identified in the entries
387 created in <filename>/etc/fstab</filename>, issue the following commands
388 as the <systemitem class="username">root</systemitem> user (you must
389 substitute the proper data for the
390 <replaceable>&lt;iocharset&gt;</replaceable> and
391 <replaceable>&lt;codepage&gt;</replaceable> info):</para>
392
393<screen role="root"><userinput>install -v -m755 -d /etc/hal/fdi/policy/30user &amp;&amp;
394cat &gt; /etc/hal/fdi/policy/30user/30user-policy.fdi &lt;&lt; "EOF"
395<literal>&lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;!- -*- SGML -*- -&gt;
396
397&lt;!-
398This file is used to set custom options to the HAL policy settings.
399The default policy settings are defined in files contained in the
400/usr/share/hal/fdi/policy directories. User defined customizations
401should be in files contained in the /etc/hal/fdi/policy directories.
402-&gt;
403
404&lt;deviceinfo version="0.2"&gt;
405
406 &lt;device&gt;
407 &lt;match key="info.udi"
408 string="/org/freedesktop/Hal/devices/computer"&gt;
409
410 &lt;!- Set the iocharset variable in the /etc/fstab file entry -&gt;
411 &lt;merge
412 key="storage.policy.default.mount_option.iocharset=<replaceable>&lt;iocharset&gt;</replaceable>"
413 type="bool"&gt;true&lt;/merge&gt;
414
415 &lt;!- Set the codepage variable in the /etc/fstab file entry -&gt;
416 &lt;merge
417 key="storage.policy.default.mount_option.codepage=<replaceable>&lt;codepage&gt;</replaceable>"
418 type="bool"&gt;true&lt;/merge&gt;
419
420 &lt;/match&gt;
421 &lt;/device&gt;
422
423&lt;/deviceinfo&gt;</literal>
424
425EOF</userinput></screen>
426
427 <note>
428 <para>The previous commands created a file named
429 <filename>/etc/hal/fdi/policy/30user/30user-policy.fdi</filename>. To
430 ease readability of the file, put everything between the
431 &lt;angle brackets&gt; and &lt;merge&gt;&lt;/merge&gt; tags on one
432 line. You must have at least one space character
433 where the ends of the lines were. The file would then look like this
434 (trimmed at the top and bottom for brevity):</para>
435
436<screen><literal> &lt;device&gt;
437 &lt;match key="<replaceable>&lt;text&gt;</replaceable>" string="<replaceable>&lt;text&gt;</replaceable>"&gt;
438
439 &lt;!- Set the iocharset variable in the /etc/fstab file entry -&gt;
440 &lt;merge key="<replaceable>&lt;iocharset text&gt;</replaceable>" type="bool"&gt;true&lt;/merge&gt;
441
442 &lt;!- Set the codepage variable in the /etc/fstab file entry -&gt;
443 &lt;merge key="<replaceable>&lt;codepage text&gt;</replaceable>" type="bool"&gt;true&lt;/merge&gt;
444
445 &lt;/match&gt;
446 &lt;/device&gt;</literal></screen>
447
448 </note>
449
450 -->
451
452 </sect3>
453
454 <sect3 id="hal-init">
455 <title>Boot Script</title>
456
457 <para>To automatically start the <command>hald</command> daemon
458 when the system is rebooted, install the
459 <filename>/etc/rc.d/init.d/haldaemon</filename>
460 bootscript from the
461 <xref linkend="bootscripts"/> package.</para>
462
463 <indexterm zone="hal hal-init">
464 <primary sortas="f-haldaemon">haldaemon</primary>
465 </indexterm>
466
467 <!-- Not sure if this is still required any longer as the HAL daemon
468 used to hang if you didn't first restart the DBUS daemon. This is
469 not the case any longer, but it still seems that D-Bus should be
470 restarted, as the hald.conf file is read by the D-BUS daemon.
471 Leaving it in for now until it is positively confirmed it is not
472 required. -->
473
474 <important>
475 <para>If the system-wide <application>D-BUS</application> daemon was
476 running during the installation of <application>HAL</application>,
477 ensure you stop and restart the <application>D-BUS</application>
478 daemon before attempting to start the <command>hald</command>
479 daemon.</para>
480 </important>
481
482<screen role="root"><userinput>make install-haldaemon</userinput></screen>
483
484 </sect3>
485
486 </sect2>
487
488 <sect2 role="content">
489 <title>Contents</title>
490
491 <segmentedlist>
492 <segtitle>Installed Programs</segtitle>
493 <segtitle>Installed Libraries</segtitle>
494 <segtitle>Installed Directories</segtitle>
495
496 <seglistitem>
497 <seg>hal-device, hal-device-manager,
498 hal-find-by-capability, hal-find-by-property, hal-get-property,
499 hal-set-property, hald and lshal</seg>
500 <seg>libhal.{so,a} and libhal-storage,{so,a}</seg>
501 <seg>/etc/hal, /usr/include/hal, /usr/lib/hal,
502 /usr/share/doc/hal-&hal-version;, /usr/share/hal
503 and /var/run/hald</seg>
504 </seglistitem>
505 </segmentedlist>
506
507 <variablelist>
508 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
509 <?dbfo list-presentation="list"?>
510 <?dbhtml list-presentation="table"?>
511
512 <varlistentry id="hal-device">
513 <term><command>hal-device</command></term>
514 <listitem>
515 <para>is used to create, remove or show a
516 <application>HAL</application> device.</para>
517 <indexterm zone="hal hal-device">
518 <primary sortas="b-hal-device">hal-device</primary>
519 </indexterm>
520 </listitem>
521 </varlistentry>
522
523 <varlistentry id="hal-device-manager">
524 <term><command>hal-device-manager</command></term>
525 <listitem>
526 <para>shows a graphical representation of all the devices
527 <application>HAL</application> is aware of. This program requires
528 <xref linkend="hal-runtime-dependencies"/>. Here is a <ulink
529 url="http://cvs.freedesktop.org/*checkout*/hal/hal/doc/spec/hal-devices1.png">
530 screenshot</ulink> of <command>hal-device-manager</command>
531 communicating with the HAL daemon and displaying a tree of device
532 objects. The shown properties in the screenshot are for a device
533 object representing a hard disk.</para>
534 <indexterm zone="hal hal-device-manager">
535 <primary sortas="b-hal-device-manager">hal-device-manager</primary>
536 </indexterm>
537 </listitem>
538 </varlistentry>
539
540 <varlistentry id="hal-find-by-capability">
541 <term><command>hal-find-by-capability</command></term>
542 <listitem>
543 <para>prints the Unique Device Identifiers for
544 <application>HAL</application> device objects of a given
545 capability.</para>
546 <indexterm zone="hal hal-find-by-capability">
547 <primary sortas="b-hal-find-by-capability">hal-find-by-capability</primary>
548 </indexterm>
549 </listitem>
550 </varlistentry>
551
552 <varlistentry id="hal-find-by-property">
553 <term><command>hal-find-by-property</command></term>
554 <listitem>
555 <para>prints the Unique Device Identifiers for
556 <application>HAL</application> device objects where a given property
557 assumes a given value.</para>
558 <indexterm zone="hal hal-find-by-property">
559 <primary sortas="b-hal-find-by-property">hal-find-by-property</primary>
560 </indexterm>
561 </listitem>
562 </varlistentry>
563
564 <varlistentry id="hal-get-property">
565 <term><command>hal-get-property</command></term>
566 <listitem>
567 <para>retrieves a property from a device.</para>
568 <indexterm zone="hal hal-get-property">
569 <primary sortas="b-hal-get-property">hal-get-property</primary>
570 </indexterm>
571 </listitem>
572 </varlistentry>
573
574 <varlistentry id="hal-set-property">
575 <term><command>hal-set-property</command></term>
576 <listitem>
577 <para>attempts to set property for a device. Note that, due to
578 security considerations, it may not be possible to set a
579 property.</para>
580 <indexterm zone="hal hal-set-property">
581 <primary sortas="b-hal-set-property">hal-set-property</primary>
582 </indexterm>
583 </listitem>
584 </varlistentry>
585
586 <varlistentry id="hald">
587 <term><command>hald</command></term>
588 <listitem>
589 <para>is the <application>HAL</application> daemon program.</para>
590 <indexterm zone="hal hald">
591 <primary sortas="b-hald">hald</primary>
592 </indexterm>
593 </listitem>
594 </varlistentry>
595
596 <varlistentry id="lshal">
597 <term><command>lshal</command></term>
598 <listitem>
599 <para>shows all devices and their properties. If the --monitor option
600 is given then the device list and all devices are monitored for
601 changes.</para>
602 <indexterm zone="hal lshal">
603 <primary sortas="b-lshal">lshal</primary>
604 </indexterm>
605 </listitem>
606 </varlistentry>
607
608 <varlistentry id="libhal">
609 <term><filename class='libraryfile'>libhal.{so,a}</filename></term>
610 <listitem>
611 <para>contains the API functions required by the
612 <application>HAL</application> programs.</para>
613 <indexterm zone="hal libhal">
614 <primary sortas="c-libhal">libhal.{so,a}</primary>
615 </indexterm>
616 </listitem>
617 </varlistentry>
618
619 <varlistentry id="libhal-storage">
620 <term><filename class='libraryfile'>libhal-storage.{so,a}</filename></term>
621 <listitem>
622 <para>contains the API functions required by the
623 <application>HAL</application> storage and volume utility
624 programs.</para>
625 <indexterm zone="hal libhal-storage">
626 <primary sortas="c-libhal-storage">libhal-storage.{so,a}</primary>
627 </indexterm>
628 </listitem>
629 </varlistentry>
630
631 </variablelist>
632
633 </sect2>
634
635</sect1>
Note: See TracBrowser for help on using the repository browser.