Demi Marie Obenour <demiobenour@gmail.com> writes:

> On 9/25/25 07:07, Alyssa Ross wrote:
>> Demi Marie Obenour <demiobenour@gmail.com> writes:
>> 
>>> diff --git a/host/rootfs/image/etc/s6-rc/vmm-env/contents b/host/rootfs/image/etc/s6-rc/vmm-env/contents
>>> deleted file mode 100644
>>> index 9a1aea63abd1b5c374e3ac9a9671e4c9341f8d16..0000000000000000000000000000000000000000
>>> --- a/host/rootfs/image/etc/s6-rc/vmm-env/contents
>>> +++ /dev/null
>>> @@ -1,9 +0,0 @@
>>> -# SPDX-License-Identifier: CC0-1.0
>>> -# SPDX-FileCopyrightText: 2021 Alyssa Ross <hi@alyssa.is>
>>> -#
>>> -core
>>> -kvm
>>> -# systemd runs systemd-udev-trigger.service before sysinit.target.
>>> -# Therefore, anything using libudev that isn't an early boot service
>>> -# might expect udev coldplug to have finished.
>>> -systemd-udevd-coldplug
>> 
>> I think it probably makes sense to keep a distinction between "user can
>> now start VMs" (vm-env) and "it is now possible to start a VMM, possibly
>> automatically" (vmm-env).  We can of course try to find better names,
>> though.
>
> can-start-vms-automatically and can-start-vms-manually?

"interactive" and "vmm-env"?