https://bugzilla.novell.com/show_bug.cgi?id=438867
User jsmeix@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=438867#c48
--- Comment #48 from Johannes Meixner 2008-12-04 03:20:48 MST ---
Thanks for the clarification in comment #46.
But as far as I understand it this even proves
that HAL is broken by design because its user interface
(e.g. the fdi files for me as a user of the HAL system)
depend on kernel-internal values which is in contradiction to
http://www.kroah.com/log/linux/stable_api_nonsense.html
where Greg K-H wrote
----------------------------------------------------------
Linux does not have a binary kernel interface,
nor does it have a stable kernel interface.
Please realize that this article describes
the _in kernel_ interfaces, not the kernel
to userspace interfaces.
The kernel to userspace interface is the one that
application programs use, the syscall interface.
That interface is _very_ stable over time,
and will not break ...
This interface is the one that users and application
programmers can count on being stable.
----------------------------------------------------------
When from the user's point of view HAL works on raw
kernel-internal values and when according to what
Greg K-H wrote kernel-internal values must be
intentionally unstable, it is obvious that also
the HAL user interface (e.g. the fdi files) must be
unstable which is a broken design because even the kernel
provides a stable interface for the user.
Here I am the user of HAL - or in other words:
From the HAL point of view I am HALs customer.
Probably I do not understand this all and I cannot
expect to have a piece of software which lets me do
hardware abstraction stuff in a stable and reliable way.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.