> > 1) Gather dmi, bios, i2c and other system information sources with > > kernel level drivers able to deliver this information via sysfs or some > > other mechanism.
> Isn't this possible today ? Sure, for dmi info you just have to read protected memory as root. But you have to know the deference between what hardware your running on. dmi only works on IBM bios based PCs, won't work on Macs or new fancy none bios motherboards. So something that can sort that info out despite what kind of hardware it's running on would be better. > As far as OEM mobos are concerned, have no idea. > > HAL's replacement being devicekit, I was writing it quite late, the name slipped my memory. sorry. > https://edge.launchpad.net/devicekit > http://hal.freedesktop.org/docs/DeviceKit/DeviceKit.7.html > > would that have any benefits in getting some of the issues > you talked about? Perhaps, but by this time, I'm sick of talking to brick walls. It's obvious that other developers don't care about none functional hardware information. Either that or they think they know best, and don't care to discuss it. > Thank you for taking time and explaining everything so well. > Would like to know a bit more about the project you tried > Martin Owens. Sure: https://launchpad.net/dohickey the python based client implements some very rough filtering and sorting logic to pick through the erroneous information. I was working against 530 computer profiles, sent to me by the community. So some things are fairly good at coping with missing info, others such as RAM type were quite hard to work out. Still, I consider the project put to bed since most of this stuff should go into devicekit. Regards, Martin -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
