On 2020-Jul-27, at 18:44, John-Mark Gurney wrote:
> Mark Millard wrote this message on Mon, Jul 27, 2020 at 17:15 -0700:
>> On 2020-Jul-27, at 16:43, Mark Millard wrote:
>>
>>> On 2020-Jul-26, at 18:20, John-Mark Gurney wrote:
>>>
Mark Millard wrote this message on Sat, Jul 25, 2020 a
On 2020-Jul-27, at 16:43, Mark Millard wrote:
> On 2020-Jul-26, at 18:20, John-Mark Gurney wrote:
>
>> Mark Millard wrote this message on Sat, Jul 25, 2020 at 19:13 -0700:
>>> For reference for what applying the patch
>>> reported (see Hunk #14):
>>
>> Ok, updated it to be relative to r363583.
On 2020-Jul-26, at 18:20, John-Mark Gurney wrote:
> Mark Millard wrote this message on Sat, Jul 25, 2020 at 19:13 -0700:
>> For reference for what applying the patch
>> reported (see Hunk #14):
>
> Ok, updated it to be relative to r363583...
>
> I had made a white spcae commit to if_ure.c, b
On Fri, Jul 24, 2020 at 3:24 PM Kyle Evans wrote:
>
> Hello!
>
> Just a little bit ago, I committed an update[0] to the valgrind-devel
> port that updates it to Paul Floyd's branch, where he has rebased us
> forward to 3.17.0 and largely fixed valgrind operation on both 12.x
> and -CURRENT.
>
> He
Mark Millard wrote this message on Mon, Jul 27, 2020 at 17:15 -0700:
> On 2020-Jul-27, at 16:43, Mark Millard wrote:
>
> > On 2020-Jul-26, at 18:20, John-Mark Gurney wrote:
> >
> >> Mark Millard wrote this message on Sat, Jul 25, 2020 at 19:13 -0700:
> >>> For reference for what applying the pa
Andrew Gallatin wrote:
>On 2020-07-19 19:34, Rick Macklem wrote:
>> I spent a little time chasing a problem in the nfs-over-tls code, where it
>> would sometimes end up with corrupted data in the file(s) of a mirrored
>> pNFS configuration.
>>
>> I think the problem was that the code filled the dat
On Mon, 27 Jul 2020 15:49:46 -0700 bsd-li...@bsdforge.com said
On Mon, 27 Jul 2020 15:14:49 -0700 Michael Dexter edi...@callfortesting.org
said
> On 7/17/20 4:37 AM, Cristian Cardoso wrote:
> > I would like to know if by chance in freeBSD there is some kind of log
> > when the command freebsd-u
On Mon, 27 Jul 2020 15:14:49 -0700 Michael Dexter edi...@callfortesting.org said
On 7/17/20 4:37 AM, Cristian Cardoso wrote:
> I would like to know if by chance in freeBSD there is some kind of log
> when the command freebsd-update fetch / install is executed?
> I looked in the documentation and
On 7/17/20 4:37 AM, Cristian Cardoso wrote:
I would like to know if by chance in freeBSD there is some kind of log
when the command freebsd-update fetch / install is executed?
I looked in the documentation and found nothing about it.
There does not appear to be a log but running it with '--debu
Ganbold Tsagaankhuu wrote this message on Mon, Jul 27, 2020 at 18:29 +0800:
> On Mon, Jul 27, 2020 at 5:14 AM John-Mark Gurney wrote:
>
> > Ganbold Tsagaankhuu wrote this message on Sun, Jul 26, 2020 at 11:05 +0800:
> > > On Sun, Jul 26, 2020 at 7:13 AM John-Mark Gurney
> > wrote:
> > >
> > > >
> On Mon, Jul 27, 2020 at 04:23:22PM +0200, Emmanuel Vadot wrote:
> > On Mon, 27 Jul 2020 14:14:13 +
> > Glen Barber wrote:
> >
> > > On Sat, Jul 25, 2020 at 12:29:42PM +0200, Emmanuel Vadot wrote:
> > > > On Fri, 24 Jul 2020 22:28:39 +
> > > > Glen Barber wrote:
> > > >
> > > > > On Sa
On 2020-07-19 19:34, Rick Macklem wrote:
I spent a little time chasing a problem in the nfs-over-tls code, where it
would sometimes end up with corrupted data in the file(s) of a mirrored
pNFS configuration.
I think the problem was that the code filled the data to be written into
anonymous page
A base system OpenSSH update in 2016 or so removed a number of ciphers
from the default lists offered by the server/client (due to known
weaknesses). This prompted FreeBSD PR207679, and they were restored in
r296634.
It's time to retire this local change against upstream OpenSSH; the
ciphers shoul
On Mon, Jul 27, 2020 at 04:23:22PM +0200, Emmanuel Vadot wrote:
> On Mon, 27 Jul 2020 14:14:13 +
> Glen Barber wrote:
>
> > On Sat, Jul 25, 2020 at 12:29:42PM +0200, Emmanuel Vadot wrote:
> > > On Fri, 24 Jul 2020 22:28:39 +
> > > Glen Barber wrote:
> > >
> > > > On Sat, Jul 25, 2020 at
On Mon, 27 Jul 2020 14:14:13 +
Glen Barber wrote:
> On Sat, Jul 25, 2020 at 12:29:42PM +0200, Emmanuel Vadot wrote:
> > On Fri, 24 Jul 2020 22:28:39 +
> > Glen Barber wrote:
> >
> > > On Sat, Jul 25, 2020 at 12:14:52AM +0200, Emmanuel Vadot wrote:
> > > > On Fri, 24 Jul 2020 22:06:07 +0
On Sat, Jul 25, 2020 at 12:29:42PM +0200, Emmanuel Vadot wrote:
> On Fri, 24 Jul 2020 22:28:39 +
> Glen Barber wrote:
>
> > On Sat, Jul 25, 2020 at 12:14:52AM +0200, Emmanuel Vadot wrote:
> > > On Fri, 24 Jul 2020 22:06:07 +
> > > Glen Barber wrote:
> > >
> > > > On Fri, Jul 24, 2020 at
On 2020-07-25 21:21, John-Mark Gurney wrote:
Yeah, agreed. I think hselasky has a better fix:
https://reviews.freebsd.org/D24914
I just saw his e-mail in a different thread.
I'm testing out this patch now, and let people know how it goes.. It'll
be nice to not have to worry about these panics..
On 2020-Jul-26, at 18:20, John-Mark Gurney wrote:
> Mark Millard wrote this message on Sat, Jul 25, 2020 at 19:13 -0700:
>> For reference for what applying the patch
>> reported (see Hunk #14):
>
> Ok, updated it to be relative to r363583...
>
> I had made a white spcae commit to if_ure.c, b
On Mon, Jul 27, 2020 at 5:14 AM John-Mark Gurney wrote:
> Ganbold Tsagaankhuu wrote this message on Sun, Jul 26, 2020 at 11:05 +0800:
> > On Sun, Jul 26, 2020 at 7:13 AM John-Mark Gurney
> wrote:
> >
> > > Hello,
> > >
> > > I'd like people who have ure (RealTek) based USB devices to test
> > >
19 matches
Mail list logo
