On Sun, Nov 10, 2019 at 01:21:21AM -0600, Jason High wrote:
> For -U, that could work (was actually how we handled it in an earlier
> version). For -C, no. Our goal is to avoid cgd trying to configure a
> device, like those backed by USB drives, on boot when the backing
> device isn't attached.
For -U, that could work (was actually how we handled it in an earlier
version). For -C, no. Our goal is to avoid cgd trying to configure a
device, like those backed by USB drives, on boot when the backing
device isn't attached. But perhaps rather than changing the semantics
of -C, we could add a
jh...@netbsd.org (Jason High) writes:
>Hello NetBSD,
>When using cgdconfig in do_all mode (-C|-U), it will attempt to
>configure/unconfigure all devices specified in cgd.conf regardless of whether
>the device is attached or not (our use case is USB drives).
Wouldn't it be sufficient to just ig
Date:Sun, 10 Nov 2019 00:52:46 +
From:Jason High
Message-ID: <20191110005246.ga29...@homeworld.netbsd.org>
| When using cgdconfig in do_all mode (-C|-U), it will attempt to
| configure/unconfigure all devices specified in cgd.conf regardless of
| whether the
Hello NetBSD,
When using cgdconfig in do_all mode (-C|-U), it will attempt to
configure/unconfigure all devices specified in cgd.conf regardless of whether
the device is attached or not (our use case is USB drives). The below diff
gracefully skips over devices if they are not attached or not c
