Both of these create errors when copy pasting to follow the instructions:
- Remove smart quotes from around "HassOS default"
- Changing typo of 'system_connections' to 'system-connections'
With this change, hassos can have USB devices passed into a guest VM
with the hypervisor emulating an XHCI controller. QEMU recommends using
XHCI whenever possible, as it offers a much more virtualization-friendly
architecture than its [EO]HCI predecessors (which are already support by
the hassos kernel).
On systems where ACPI support is present as inidcated by the presence of
/proc/acpi (e.g. on OVA compatible hypervisors), we want to properly
shut down the system when the power button is pressed (or the hypervisor
simulates this kind of event to the guest machine that executes hassos).
This changeset provides the following basic infrastructure for this
feature to work as expected:
* a systemd service to start acpid, if ACPI support can be assumed
* an acpid configuration directory
* a trivial shutdown script to invoke when a PWR event is registered
* Update documentation for a static IPV4 address via nmcli
This update documents a method to change to a Static IPV4 address using the NetworkManager CLI (nmcli).
Happy for the formatting to be modified to suit local convention.
I cannot be more specific about how to get into the base OS as I don't know!
* Additional nmcli commands for dns and gateway
I found that there is a need to add in the dns and gateway IP addresses otherwise there was no route out. I note there are a number of issues alive re this routing problem e.g. https://github.com/home-assistant/home-assistant/issues/15221
* Update network.md
When booting the HassOS VMDK appliance disk image on QEMU with OVMF UEFI
firmware, barebox numbers devices differently from other environments.
This patch makes the barebox `sh` implementation expand a pathname
wildcard at runtime, so that assigned disk indices != 0 will also work.
This fix introduces a potential (but most likely irrelevant)
bug/problem: If there is more than one disk connected to the system with
a matching name assigned, the wildcard will expand to two or more
pathnames, breaking the resulting `mount` command.
