Mailinglist Archive: yast-devel (116 mails)

< Previous Next >
Re: [yast-devel] HAL vs hwinfo
  • From: Klaus Kaempf <kkaempf@xxxxxxx>
  • Date: Tue, 10 Jun 2008 13:37:14 +0200
  • Message-id: <20080610113714.GA8502@xxxxxxxxxxxxx>
* Duncan Mac-Vicar Prett <dmacvicar@xxxxxxx> [Jun 10. 2008 13:20]:
JP Rosevear wrote:
Why can't we just send patches for hal upstream that exposes this info
as hal properties? Or leverage the code in nm-tool which lists the link
status and driver at least.


Can anyone explain what is the DeviceKit stuff? and what are the
consequences for this hwinfo -> hal jump?

For DeviceKit see
Its mostly HAL-NG (next gen ;-))

For HAL see

HAL is more or less 'hwinfo via DBus' with plug-in notifications,
mostly driven from a desktop perspective. A lot of tools use HAL to
get hardware information nowadays.

The request, already a couple of years old, is to 'join forces' with HAL
upstream and extend it with hwinfo functionality.

To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >
This Thread