Greg Zuro
cfee6b9551
Detection of VirtualBox is accomplished in the existing code by *either* `innotek GmbH` or `Oracle Corporation` existing in any of: - /sys/class/dmi/id/product_name - /sys/class/dmi/id/sys_vendor - /sys/class/dmi/id/board_vendor - /sys/class/dmi/id/bios_vendor With Oracle's physical servers, both `/sys/class/dmi/id/sys_vendor` and `/sys/class/dmi/id/board_vendor` contain `Oracle Corporation`, so those servers are detected as `oracle` (VirtualBox). VirtualBox has the following values in the latest versions: - /sys/class/dmi/id/product_name: `VirtualBox` - /sys/class/dmi/id/sys_vendor: `innotek GmbH` - /sys/class/dmi/id/board_vendor: `Oracle Corporation` - /sys/class/dmi/id/bios_vendor: `innotek GmbH` Presumably the existing check for `innotek GmbH` is meant to detect older versions of VirtualBox, while changing the second checked value from `Oracle Corporation` to `VirtualBox` will reliably detect later and future versions.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.