On Thu, 18 Mar 2021, Stefan Sperling wrote:
> Our iwn(4) driver tries to be a bit smart and clears already acknowledged
> frames from Tx aggregation queues, even if those frames are still in the
> firmware's current block ack window.
>
> Instead, the driver can simply clear frames before the
On Sat, Feb 27, 2021 at 01:36:29PM +, Visa Hankala wrote:
> The kernel does not reschedule the timer when the user changes the
> timeout period. The new period will take effect only after the current
> period has expired. This is not explained in the manual page, though.
>
> With the recent
> Date: Sun, 21 Mar 2021 01:02:53 +0100
> From: Klemens Nanni
>
> apm(4/arm64) merely provides an all zero/unknown stub for those values,
> e.g. apm(8) output is useless.
>
> Hardware sensors however provide the information:
>
> $ sysctl hw.sensors
> hw.sensors.rktemp0.temp0=32.22
On Sun, Mar 21, 2021 at 02:38:42PM +0100, Florian Obser wrote:
>
> Don't warn that we can't form a temporary address when a router
> deprecates a prefix by sending a pltime of 0, this is normal.
> Continue warning when the pltime is smaller than 5 as this is almost
> certainly a configuration
On 21/03/21(Sun) 13:42, Mark Kettenis wrote:
> > Date: Sat, 20 Mar 2021 13:10:17 +0100
> > From: Martin Pieuchot
> >
> > On SP systems, like bluhm@'s armv7 regression machine, the kern/ptrace2
> > test is failing due to a subtle behavior. Diff below makes it pass.
> >
> >
On Sun, Mar 21, 2021 at 02:02:00PM +0100, Mark Kettenis wrote:
> > Date: Sun, 21 Mar 2021 01:02:53 +0100
> > From: Klemens Nanni
> >
> > apm(4/arm64) merely provides an all zero/unknown stub for those values,
> > e.g. apm(8) output is useless.
> >
> > Hardware sensors however provide the
On Thu, Mar 18, 2021 at 05:57:45PM +0100, Alexander Bluhm wrote:
> Since we stash log messages in the kernel, the timestamps added by
> syslogd are delayed. The kernel could add the timestamp when it
> receives the message by sendsyslog(2). This is more precise and
> can be expressed by more
> Date: Sat, 20 Mar 2021 13:10:17 +0100
> From: Martin Pieuchot
>
> On SP systems, like bluhm@'s armv7 regression machine, the kern/ptrace2
> test is failing due to a subtle behavior. Diff below makes it pass.
>
>
> Date: Sun, 21 Mar 2021 17:22:05 +0100
> From: Klemens Nanni
>
> On Sun, Mar 21, 2021 at 02:02:00PM +0100, Mark Kettenis wrote:
> > > Date: Sun, 21 Mar 2021 01:02:53 +0100
> > > From: Klemens Nanni
> > >
> > > apm(4/arm64) merely provides an all zero/unknown stub for those values,
> > > e.g.
The sensor framework generally does not know where a sensor is. A
sensor could reside on some device which has been plugged in, rather
than be the primary sensor.
But the users of apm are only hoping for best effort.
meaning "some information", not "perfect information". Many PC BIOS
have lied
I wanted to use httpd's fastcgi "socket" and "strip" options and based upon
the man page's brief text:
[no] fastcgi [option]
Enable FastCGI instead of serving files. Valid options are:
tried "obvious" permutations such as:
fastcgi strip 1 socket "..."
fastcgi socket "..."
Jason McIntyre wrote:
> On Sat, Mar 20, 2021 at 07:29:11PM -0600, Theo de Raadt wrote:
> > There is a pattern we've followed in the past, that when a manpage applies
> > to more than 2 (or 3?) architectures, then we simply make it MI.
> >
> > So MANSUBDIR would get deleted, and then the sets
Don't warn that we can't form a temporary address when a router
deprecates a prefix by sending a pltime of 0, this is normal.
Continue warning when the pltime is smaller than 5 as this is almost
certainly a configuration error.
OK?
diff --git engine.c engine.c
index 7b49b330328..94a4a232d6a
There's two things I'd like to know before going further with this:
1) according to RFC2578 section 3.6:
(1) registration: the definition of a particular item is registered as
a particular OBJECT IDENTIFIER value, and associated with a
particular descriptor. After such a registration,
I was using the send/dump feature and noticed that when restoring a
guest that the console connection would "stutter." (Wasn't printing
fully without hitting return.)
The following diff properly restores the vm_pipe structures for the
uart, pit, and rtc devices when using `vmctl receive`. The
On Sun, Mar 21, 2021 at 05:08:00PM GMT, Laurence Tratt wrote:
> I wanted to use httpd's fastcgi "socket" and "strip" options and based upon
> the man page's brief text:
>
> [no] fastcgi [option]
> Enable FastCGI instead of serving files. Valid options are:
>
> tried "obvious"
On Sun, Mar 21 2021, Mark Kettenis wrote:
>> Date: Sun, 21 Mar 2021 17:22:05 +0100
>> From: Klemens Nanni
>>
>> On Sun, Mar 21, 2021 at 02:02:00PM +0100, Mark Kettenis wrote:
>> > > Date: Sun, 21 Mar 2021 01:02:53 +0100
>> > > From: Klemens Nanni
>> > >
>> > > apm(4/arm64) merely provides an
I favour a fuller explanation, this one is fine by me.
On Sun, 21 Mar 2021 at 17:20, Laurence Tratt wrote:
>
> I wanted to use httpd's fastcgi "socket" and "strip" options and based upon
> the man page's brief text:
>
> [no] fastcgi [option]
> Enable FastCGI instead of serving
On Sun, Mar 21, 2021 at 10:58:02PM +, Raf Czlonka wrote:
Hello Raf,
> I'd simply use the existing wording, without getting into details.
>
> While there, "braces" dominate the manual page, with a single occurrence of
> "brackets" so let's change that too, for consistency.
That works for me!
Klemens Nanni wrote:
> > So which is better:
> >
> > (1) try to emit some information for the people who quicky-use the apm
> > interface
> >
> > (2) change apm to not print those lines on architectures where we are
> > unsure.
> >
> > I think (1) is acceptable for a tool which has never
On Sun, Mar 21, 2021 at 06:50:23AM +, Jason McIntyre wrote:
> On Sat, Mar 20, 2021 at 07:29:11PM -0600, Theo de Raadt wrote:
> > There is a pattern we've followed in the past, that when a manpage applies
> > to more than 2 (or 3?) architectures, then we simply make it MI.
> >
> > So MANSUBDIR
Hi,
When trying out veb(4), I ran into a situation where TCP sessions across a
veb(4) bridge stalled while the exact same config using bridge(4) worked fine.
After some investigation, it seems that veb(4) adds an FCS to the outgoing
frame, while bridge(4) doesn't. When this causes the outgoing
On Thu, Mar 18, 2021 at 05:57:45PM +0100, Alexander Bluhm wrote:
> Hi,
>
> Since we stash log messages in the kernel, the timestamps added by
> syslogd are delayed. The kernel could add the timestamp when it
> receives the message by sendsyslog(2). This is more precise and
> can be expressed by
On Sun, Mar 21 2021, Klemens Nanni wrote:
> apm(4/arm64) merely provides an all zero/unknown stub for those values,
> e.g. apm(8) output is useless.
>
> Hardware sensors however provide the information:
>
> $ sysctl hw.sensors
> hw.sensors.rktemp0.temp0=32.22 degC (CPU)
>
On Sun, Mar 21, 2021 at 11:56:42AM -0600, Theo de Raadt wrote:
> The sensor framework generally does not know where a sensor is. A
> sensor could reside on some device which has been plugged in, rather
> than be the primary sensor.
>
> But the users of apm are only hoping for best effort.
>
>
On Sat, Mar 20, 2021 at 07:29:11PM -0600, Theo de Raadt wrote:
> There is a pattern we've followed in the past, that when a manpage applies
> to more than 2 (or 3?) architectures, then we simply make it MI.
>
> So MANSUBDIR would get deleted, and then the sets would be updated.
>
> People with
26 matches
Mail list logo
