On Tue, Jun 26, 2018 at 7:05 PM Edgar Pettijohn III
wrote:
>
>
>
> On 06/26/18 13:50, Raul Miller wrote:
> > Personally, I can't totally figure out what this policy would be.
> >
> > My current best approximation is: there's a period of time when
> > pkg_add and syspatch are running and that is a
On 06/26/18 13:50, Raul Miller wrote:
Personally, I can't totally figure out what this policy would be.
My current best approximation is: there's a period of time when
pkg_add and syspatch are running and that is a time when writes are
allowed, other than that, not.
I could maybe rig up some
Personally, I can't totally figure out what this policy would be.
My current best approximation is: there's a period of time when
pkg_add and syspatch are running and that is a time when writes are
allowed, other than that, not.
I could maybe rig up something more complicated using inherited
cryp
Hello,
As a user i come across one use case
where i m thinking : i do not want any program/exec
to modify base or local base ( (/usr and /bin /bsd etc.. )
except syspatch and pkg_add -u.
Please stop and tell if it does not make sense.
I did look at pledge(2) and mount as pledge may force rdonl
4 matches
Mail list logo
