There's a long standing request to extend the output of dmidecode to something that would be machine-readable. Something like an XML or JSON-based format. Unfortunately this can't be implemented right now because the output of dmidecode is generated by open-coded printfs as the DMI table is being parsed, with no intermediate structures nor temporary buffers.

While implementing a machine-parseable output is out of scope for a single hack week, let's remember that even the longest journey starts with a single footstep. I would like to try and rewrite the 5200 lines of code of dmidecode in such a way that printing the output would be somewhat separated from parsing the DMI table and done by a limited set of dedicated functions. Alternative output formats could later hook into such functions.

Looking for hackers with the skills:

dmidecode c

This project is part of:

Hack Week 19



  • bmwiedemann
    8 months ago by bmwiedemann | Reply

    I think there are tools parsing output of dmidecode: ohai and salt at least. Probably more. hwinfo?

    • jdelvare
      6 months ago by jdelvare | Reply

      hwinfo has its own DMI table decoder, it does not rely on dmidecode.

      I didn't know about ohai (I don't even know what it is) and salt. The output of dmidecode is plain text currently, it can be parsed if you are motivated enough, just you have to write your own parser and hope that the output format will never change in a way that will break your parser. I can understand why people would prefer a more structured output format.

  • jdelvare
    6 months ago by jdelvare | Reply

    Last week I posted preliminary clean-up patches that I came up with during the project:

    There were no objections, so I committed them yesterday.

  • jdelvare

Similar Projects

netlink interface for ethtool by mkubecek

There seems to be an overall consensus that the...

Improving picotm by tdz

Picotm is a system-level transaction manager. I...

ethtool ops for netdevsim by mkubecek

This can be seen as a subproject of [ethtool ne...

make "predictable network interface names" more predictable by mkubecek

Since the so-called "predictable names" for net...