yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #80661
[Bug 1852442] [NEW] ds-identify uses the /sys filesystem which is linux specific and non-portable
Public bug reported:
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.
** Affects: cloud-init
Importance: Undecided
Status: New
--
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:
New
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
Follow ups