← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1852442] Re: ds-identify uses the /sys filesystem which is linux specific and non-portable

 

This bug is believed to be fixed in cloud-init in version 19.4. If this
is still a problem for you, please make a comment and set the state back
to New

Thank you.

** Changed in: cloud-init
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1852442

Title:
  ds-identify uses the /sys filesystem which is linux specific and non-
  portable

Status in cloud-init:
  Fix Released

Bug description:
  On FreeBSD, /sys is a convenient link to /usr/src/sys; the kernel
  source code.

  Especially for the DMI_ info, we should probably look into using
  `dmidecode` which at least on FreeBSD we already pull in as
  dependency:

      root@container-host-02:~ # pkg info -r dmidecode
      dmidecode-3.2:
      	py36-cloud-init-19.2

  
  The only problem i see is that many names don't map nicely.
  For instance, sys_vendor is (either bios-vendor or) system-manufacturer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1852442/+subscriptions


References