lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 14 May 2014 11:23:47 +0200 From: Jean Delvare <jdelvare@...e.de> To: Mike Waychison <mikew@...gle.com>, Bjorn Helgaas <bhelgaas@...gle.com> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, linux-kernel@...r.kernel.org Subject: Purpose of dmi-sysfs kernel module Hi Mike, Bjorn, Sorry for joining the party a little late but I am just discovering the dmi-sysfs kernel module. I have to admit that I am very curious about why it was needed. What does it let you achieve that you couldn't already do with dmidecode [1]? I read on LWM [2] that you were mostly interested in type 15 records, to gain access to the System Event Log information. Well, "dmidecode -t 15" does exactly that. It may be a bit late now but if anything is missing from dmidecode, I would rather add it there than implement a separate solution. [1] http://www.nongnu.org/dmidecode/ [2] http://lwn.net/Articles/429427/ Thanks, -- Jean Delvare SUSE L3 Support -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists