On Fri, Jun 11, 2021 at 09:16:46AM -0600, Theo de Raadt wrote:
> Dave Voutila wrote:
>
> > Theo de Raadt writes:
> >
> > > Regarding the vmm chunk -- as I said in my other reply, these
> > > explanations are too precise. They risk becoming outdated as things
> > > change. Furthermore, some of
Dave Voutila wrote:
> Theo de Raadt writes:
>
> > Regarding the vmm chunk -- as I said in my other reply, these
> > explanations are too precise. They risk becoming outdated as things
> > change. Furthermore, some of those ioctl may work in one way, but not
> > another way. Which would be
Theo de Raadt writes:
> Regarding the vmm chunk -- as I said in my other reply, these
> explanations are too precise. They risk becoming outdated as things
> change. Furthermore, some of those ioctl may work in one way, but not
> another way. Which would be too complicated to describe also.
Regarding the vmm chunk -- as I said in my other reply, these
explanations are too precise. They risk becoming outdated as things
change. Furthermore, some of those ioctl may work in one way, but not
another way. Which would be too complicated to describe also. I urge
simple messaging:
.It Va
Here's my take at documenting the missing pledge promises in pledge.2
and placing them in a reasonable order with the others. Each of these
just enabled various ioctl or sysctl interfaces.
I'm unhappy with the explanation for drm, but don't know how to
explain the purpose of these ioctls, and