[BACK]Return to DESCR CVS log [TXT][DIR] Up to [cvs.NetBSD.org] / pkgsrc / sysutils / hal

File: [cvs.NetBSD.org] / pkgsrc / sysutils / hal / DESCR (download)

Revision 1.1.1.1 (vendor branch), Sat Nov 22 15:20:51 2008 UTC (10 years, 4 months ago) by jmcneill
Branch: TNF, MAIN
CVS Tags: pkgsrc-base, pkgsrc-2018Q4-base, pkgsrc-2018Q4, pkgsrc-2018Q3-base, pkgsrc-2018Q3, pkgsrc-2018Q2-base, pkgsrc-2018Q2, pkgsrc-2018Q1-base, pkgsrc-2018Q1, pkgsrc-2017Q4-base, pkgsrc-2017Q4, pkgsrc-2017Q3-base, pkgsrc-2017Q3, pkgsrc-2017Q2-base, pkgsrc-2017Q2, pkgsrc-2017Q1-base, pkgsrc-2017Q1, pkgsrc-2016Q4-base, pkgsrc-2016Q4, pkgsrc-2016Q3-base, pkgsrc-2016Q3, pkgsrc-2016Q2-base, pkgsrc-2016Q2, pkgsrc-2016Q1-base, pkgsrc-2016Q1, pkgsrc-2015Q4-base, pkgsrc-2015Q4, pkgsrc-2015Q3-base, pkgsrc-2015Q3, pkgsrc-2015Q2-base, pkgsrc-2015Q2, pkgsrc-2015Q1-base, pkgsrc-2015Q1, pkgsrc-2014Q4-base, pkgsrc-2014Q4, pkgsrc-2014Q3-base, pkgsrc-2014Q3, pkgsrc-2014Q2-base, pkgsrc-2014Q2, pkgsrc-2014Q1-base, pkgsrc-2014Q1, pkgsrc-2013Q4-base, pkgsrc-2013Q4, pkgsrc-2013Q3-base, pkgsrc-2013Q3, pkgsrc-2013Q2-base, pkgsrc-2013Q2, pkgsrc-2013Q1-base, pkgsrc-2013Q1, pkgsrc-2012Q4-base, pkgsrc-2012Q4, pkgsrc-2012Q3-base, pkgsrc-2012Q3, pkgsrc-2012Q2-base, pkgsrc-2012Q2, pkgsrc-2012Q1-base, pkgsrc-2012Q1, pkgsrc-2011Q4-base, pkgsrc-2011Q4, pkgsrc-2011Q3-base, pkgsrc-2011Q3, pkgsrc-2011Q2-base, pkgsrc-2011Q2, pkgsrc-2011Q1-base, pkgsrc-2011Q1, pkgsrc-2010Q4-base, pkgsrc-2010Q4, pkgsrc-2010Q3-base, pkgsrc-2010Q3, pkgsrc-2010Q2-base, pkgsrc-2010Q2, pkgsrc-2010Q1-base, pkgsrc-2010Q1, pkgsrc-2009Q4-base, pkgsrc-2009Q4, pkgsrc-2009Q3-base, pkgsrc-2009Q3, pkgsrc-2009Q2-base, pkgsrc-2009Q2, pkgsrc-2009Q1-base, pkgsrc-2009Q1, pkgsrc-2008Q4-base, pkgsrc-2008Q4, pkgsrc-, HEAD
Changes since 1.1: +0 -0 lines

Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now,
more to come soon.

What is the point of HAL?

To merge information from various sources such that desktop applications can
locate and use hardware devices. The point is that the exact set of
information to merge varies by device and bus type. In order to do this, we
need to define a format for the information, hence the HAL specification.

We may read some stuff from the hardware itself, then add some info provided
by the kernel, then add some metadata from some systemwide files, then add
some data that has been obtained by the desktop and stored per-user, then
look at some blacklist, and finally we have a complete picture of everything
known about that particular device.

An extra value is that we can do this in an operating system independent way.
Stuff like this is important to the major desktop environments.

What is the point of HAL?

To merge information from various sources such that desktop applications can
locate and use hardware devices. The point is that the exact set of
information to merge varies by device and bus type. In order to do this, we
need to define a format for the information, hence the HAL specification.

We may read some stuff from the hardware itself, then add some info provided
by the kernel, then add some metadata from some systemwide files, then add
some data that has been obtained by the desktop and stored per-user, then
look at some blacklist, and finally we have a complete picture of everything
known about that particular device.

An extra value is that we can do this in an operating system independent way.
Stuff like this is important to the major desktop environments.