Re: heads-up: planned changes in nvmm

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

And on top of this if one wants a member of nvmm group to be able to
run nvmmctl, then /dev/nvmm must be 660 ...

On Mon, 28 Oct 2019 at 23:13, Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote:
>
> And then one has to change the permissions of the tap device and the
> disk in use, e,g,
> ...
> chown root:nvmm /dev/tap3
> chmod 660 /dev/tap3
> chown root:nvmm /dev/zvol/rdsk/pail/openbsd
> chmod 660 /dev/zvol/rdsk/pail/openbsd
> ...
>
> On Mon, 28 Oct 2019 at 22:54, Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote:
> >
> > Thanks! Sorted.
> >
> > On Mon, 28 Oct 2019 at 21:04, J. Lewis Muir <jlmuir%imca-cat.org@localhost> wrote:
> > >
> > > On 10/28, Chavdar Ivanov wrote:
> > > > After the above message I rebuilt the system and got eventually
> > > > nvmmctl, which worked. I couldn't start any VM, though, so I proceeded
> > > > to rebuild wip/qemu-nvmm, although there were no changes since my
> > > > previous build. This time it worked; I also recreated /dev/nvmm (the
> > > > protection changed from 600 to 640). I haven't yet added a nvmm group
> > > > member; is there any specific group ID nvmm should be? ( I think I
> > > > missed the query about the merge of /etc/group during the system
> > > > upgrade. )
> > >
> > > See Maxime's post to tech-kern:
> > >
> > >   https://mail-index.netbsd.org/tech-kern/2019/10/25/msg025623.html
> > >
> > > Lewis
> >
> >
> >
> > --
> > ----
>
>
>
> --
> ----



-- 
----