On Fri, Aug 14, 2020 at 09:24:35AM -0600, Theo de Raadt wrote:
> Christian Weisgerber wrote:
>
> > On 2020-08-14, Jason McIntyre wrote:
> >
> > > - i cannot work out what is with the \! examples. i know we try to make
> > > entries work for both csh and sh style shells, but stuff like this
>
On 13/08/20(Thu) 10:14, Brian Brombacher wrote:
>
>
> >> On Aug 9, 2020, at 6:29 PM, Chris Cappuccio wrote:
> > Brian Brombacher [br...@planetunix.net] wrote:
> >>
> >> I am wondering what approach the project is planning to use to modernize
> >> the congestion control algorithms. I'm
On Fri, Jul 31, 2020 at 06:28:32AM +0200, Klemens Nanni wrote:
> ifconfig(8) detects switch(4) through its unique SIOCSWSDPID ioctl and
> further does another switch specific ioctl for the default output
> regardless of configuration and/or members:
>
> SIOCSWSDPID struct ifbrparam
>
> Date: Fri, 14 Aug 2020 14:40:23 +0200 (CEST)
> From: Mark Kettenis
>
> I suppose a way to test this properly is to pick a system call and
> replace a copyin() with a direct access? That will succeed without
> PAN but should fail with PAN enabled right?
So that does indeed work. However, the
> It has occurred to me that we could do a trial copyout(9) in
> sys_setitimer() before entering the critical section. This is a *bit*
> wasteful, but is relatively inexpensive and narrows the behavior
> change I mentioned down to truly improbable cases involving multiple
> threads and munmap(2).
Fix append mode and expand regress. I've added an append flag to
the state but we could just as easily store the open flag instead.
- todd
Index: lib/libc/stdio/fmemopen.c
===
RCS file: /cvs/src/lib/libc/stdio/fmemopen.c,v
On Wed, Aug 12, 2020 at 01:58:08PM -0500, Scott Cheloha wrote:
>
> [...]
>
> There is one behavior change: in the setitimer(2) swap case it is now
> possible to EFAULT on copyout(9) *after* you have written the new
> timer value and (possibly) started the ITIMER_REAL timeout.
>
> For example,
On Wed, 12 Aug 2020 12:26:22 +0300
Vitaliy Makkoveev wrote:
> We destroy pppx(4) related sessions while we performing PIPEXDSESSION
> command. But with pppac(4) we set session's state to
> PIPEX_STATE_CLOSE_WAIT2 and we wait garbage collector to do destruction.
pppac's PIPEXDSESSION set the
On Fri, Aug 14, 2020 at 04:30:13AM +0100, ropers wrote:
> The find man page might benefit from adding a little bit more
> user-friendly hand-holding here:
>
> Index: find.1
> ===
> RCS file: /cvs/src/usr.bin/find/find.1,v
>
The previous change introducing the kqueue_scan_setup()/finish() API
required to switch poll(2) internals to use the kqueue mechanism has
been backed out. The reason for the regression is still unknown, so
let's take a baby step approach.
Diff below introduces the new API with only minimal
On 2020-08-14, Jason McIntyre wrote:
> - i cannot work out what is with the \! examples. i know we try to make
> entries work for both csh and sh style shells, but stuff like this
> works without escaping:
>
> $ find . ! -type f
Going through the CVS and SCCS history, I see that the
Christian Weisgerber wrote:
> On 2020-08-14, Jason McIntyre wrote:
>
> > - i cannot work out what is with the \! examples. i know we try to make
> > entries work for both csh and sh style shells, but stuff like this
> > works without escaping:
> >
> > $ find . ! -type f
>
> Going
Miod noticed that the powerpc64 version talked about AArch64. I don't
think the "for all XXX platforms" makes sense so simply drop it from
all three versions of this header.
ok?
Index: arch/arm/include/softintr.h
===
RCS file:
On Fri, Aug 14, 2020 at 02:33:10PM +0200, Mark Kettenis wrote:
> Miod noticed that the powerpc64 version talked about AArch64. I don't
> think the "for all XXX platforms" makes sense so simply drop it from
> all three versions of this header.
>
> ok?
>
ok patrick@
>
> Index:
> Date: Fri, 14 Aug 2020 12:29:51 +1000
> From: Jonathan Gray
>
> On Thu, Aug 13, 2020 at 09:17:41PM +0200, Mark Kettenis wrote:
> > ARMv8.1 introduced PAN (Priviliged Access Never) which prevents the
> > kernel from accessing userland data. This can be bypassed by using
> > special
Hi,
Recently I took over the old iMac11,2 of my son, and what else to do
with it other than installing OpenBSD and see what happens. The first
thing which happened after the installation was that the screen
remained dark after the radeondrm(4) KMS initialization.
After some painful debugging,
16 matches
Mail list logo
