Software:HAL
 | This software needs to be updated. Please update this software to reflect recent events or newly available information. (January 2024) |
HAL (Hardware Abstraction Layer or rather Hardware Annotation Library) is a software subsystem for UNIX-like operating systems providing hardware abstraction.
HAL is now deprecated on most Linux distributions and on FreeBSD. Functionality is being merged into udev on Linux as of 2008–2010 and devd on FreeBSD.[citation needed] Previously, HAL was built on top of udev.[citation needed]
Some other operating systems which don't have an alternative like udev or devd still use HAL.
The purpose of the hardware abstraction layer was to allow desktop applications to discover and use the hardware of the host system through a simple, portable and abstract API, regardless of the type of the underlying hardware.[1]
HAL for Linux OS was originally envisioned by Havoc Pennington. It became a freedesktop.org project, and was a key part of the software stack of the GNOME and KDE desktop environments. It is free software, dual-licensed under both the GNU General Public License and the Academic Free License.[2]
HAL is unrelated to the concept of Windows NT kernel HALs, which handle some platform-specific core functionality within the kernel, such as interrupt routing.
Rationale
Traditionally, the operating system kernel was responsible for providing an abstract interface to the hardware the system ran on. Applications used the system call interface, or performed file I/O on device nodes in order to communicate with hardware through these abstractions. This sufficed for the simple hardware of early desktop computing.
Computer hardware, however, has increased in complexity and the abstractions provided by Unix kernels have not kept pace with the proliferating number of device and peripheral types now common on both server and desktop computers. Most modern buses have also become hotplug-capable and can have non-trivial topologies. As a result, devices are discovered or change state in ways which can be difficult to track through the system call interface or Unix IPC. The complexity of doing so forces application authors to re-implement hardware support logic.[1]
Some devices also require privileged helper programs to prepare them for use. These must often be invoked in ways that can be awkward to express with the Unix permissions model (for example, allowing users to join wireless networks only if they are logged into the video console).[1] Application authors resort to using setuid binaries or run service daemons to provide their own access control and privilege separation, potentially introducing security holes each time.
Design
HAL is a single daemon responsible for discovering, enumerating and mediating access to most of the hardware on the host computer. Applications communicate with HAL through the D-Bus IPC mechanism, which abstracts the hardware behind an object-based RPC mechanism.
Each logical hardware device is represented as a D-Bus object, and its bus address is used as a unique identifier. Devices include abstractions like disk partitions and visible wireless networks. The device's functionality is exposed through D-Bus interfaces, and its state accessed through properties, a set of key-value pairs.
HAL broadcasts hardware events as signals on these objects; applications can listen for signals and react to the hardware events that they signify—events such as a digital camera being plugged in, an optical disc spinning up or a laptop computer closing its lid.[3][4]
Implementations and obsolescence
On Linux, HAL uses /sys (a virtual file system for Linux systems) to discover hardware and listen for kernel hotplug events. Some Linux distributions also provide a udev rule to allow the udev daemon to notify HAL whenever new device nodes appear.
Deprecated
(As of 2011), Linux distributions such as Ubuntu,[5] Debian,[6] and Fedora and on FreeBSD,[7] and projects such as KDE,[8] GNOME and X.org are in the process of deprecating HAL as it has "become a large monolithic unmaintainable mess".[5] The process is largely complete, but some use of HAL remains – Debian squeeze (Feb 2011) and Ubuntu version 10.04 remove HAL from the basic system and boot process.[9] In Linux, it is in the process of being merged into udev (main udev, libudev, and udev-extras) and existing udev and kernel functionality. The replacement for non-Linux systems such as FreeBSD is devd.
Initially a new daemon DeviceKit was planned to replace certain aspects of HAL, but in March 2009, DeviceKit was deprecated in favor of adding the same code to udev as package udev-extras, and some functions have now moved to udev proper.
See also
References
- ↑ 1.0 1.1 1.2 Pennington, Havoc (2003-07-10), Making Hardware Just Work, http://ometer.com/hardware.html
- ↑ HAL source code license text, https://cgit.freedesktop.org/hal/tree/COPYING, "HAL is licensed to you under your choice of the Academic Free License version 2.1, or the GNU General Public License version 2"
- ↑ Zeuthen, David (2009-11-01), HAL 0.5.14 Specification, freedesktop.org, https://people.freedesktop.org/~dkukawka/hal-spec-git/git-head/hal-spec.html, retrieved 2017-01-15
- ↑ "hal: doc/spec". 2010-03-16. https://cgit.freedesktop.org/hal/tree/doc/spec. Retrieved 2017-01-15.
- ↑ 5.0 5.1 Halsectomy, ubuntu.com, 2013-05-10, https://wiki.ubuntu.com/Halsectomy, retrieved 2017-01-15
- ↑ "HALRemoval". debian.org. 2011-06-28. https://wiki.debian.org/HALRemoval. Retrieved 2017-01-15.
- ↑ "Features/HalRemoval". Fedora Project. 2012-01-09. https://fedoraproject.org/wiki/Features/HalRemoval. Retrieved 2017-01-15.
- ↑ "Revision 1206281: Features in KDE Base". KDE. 2010-12-19. https://commit-digest.kde.org/issues/2010-12-19/moreinfo/1206281/. Retrieved 2017-01-15.
- ↑ "TechnicalOverview: HAL removal". ubuntu.com. 2010-05-17. https://wiki.ubuntu.com/LucidLynx/TechnicalOverview#HAL_removal. Retrieved 2017-01-15.
External links
Free and open-source software projects hosted by freedesktop.org | ||
|---|---|---|
| OS components |  | |
| Libraries | ||
| Frameworks | ||
| Meetings | ||
 |
