On Sat, Apr 18, 2020 at 10:10:41PM +0200, Olivier Antoine wrote:
> Hi,
>
> During the installation process with the latest available bsd.rd, at
> the step 'Making all devices nodes' I noticed the following error
> message twice:
> chgrp : group is invalid: _sndiop
>
> Saw that on bsd.rd amd64 17
On 2020/04/18 22:10, Olivier Antoine wrote:
> Hi,
>
> During the installation process with the latest available bsd.rd, at
> the step 'Making all devices nodes' I noticed the following error
> message twice:
> chgrp : group is invalid: _sndiop
>
> Saw that on bsd.rd amd64 17 Apr 2020 during a
Hi,
During the installation process with the latest available bsd.rd, at
the step 'Making all devices nodes' I noticed the following error
message twice:
chgrp : group is invalid: _sndiop
Saw that on bsd.rd amd64 17 Apr 2020 during a fresh install.
Didn't notice any problem after.
Cheers,
--
Salut Olivier,
Olivier Taibi wrote on Wed, Apr 15, 2020 at 07:52:21PM +0200:
> I believe there is a bug in gzopen(3) when opening an empty file. It
> can read both gzipped and uncompressed files, and obviously an empty
> file falls in the second category, but in this case the first read gives
>
Hi,
I encountered a reproducible kernel panic during an accidental IPv6
misconfiguration. In order to reproduce, the OpenBSD machine must be in
the same subnet as a router that has fe80::1/64 configured and sends
IPv6 route advertisements, for example with radvd using this config:
interface
On Tue, Apr 14, 2020 at 06:42:53PM +, Mikolaj Kucharski wrote:
> On Tue, Apr 14, 2020 at 11:06:00AM +0200, Patrick Wildt wrote:
> > On Mon, Apr 13, 2020 at 09:36:04PM +0200, Mark Kettenis wrote:
> > > Can you print the status (full 32 bits) of that particular QTD?
> >
> > Yeah, I wish I could