On Sat, Jun 30, 2018 at 06:39:57PM +, Rick Macklem wrote:
> r335012 (the big patch that added the pNFS server support) revised the
> nfsd->kernel
> nfssvc(2) syscall interface.
> It has compatibility code, so that old nfsd binaries still work.
>
> I now need to revise this interface again to
On 2018-Jun-30, at 11:53 AM, John Baldwin wrote:
> On 6/30/18 10:19 AM, Mark Millard wrote:
>
>
> On 2018-Jun-30, at 10:04 AM, Mark Millard wrote:
>
>> On 2018-Jun-30, at 9:29 AM, John Baldwin wrote:
>>
>>> On 6/30/18 9:17 AM, Mark Millard wrote:
On 2018-Jun-30, at 7:51 AM, John Bal
On 6/30/18 10:19 AM, Mark Millard wrote:
>
>
> On 2018-Jun-30, at 10:04 AM, Mark Millard wrote:
>
>> On 2018-Jun-30, at 9:29 AM, John Baldwin wrote:
>>
>>> On 6/30/18 9:17 AM, Mark Millard wrote:
On 2018-Jun-30, at 7:51 AM, John Baldwin wrote:
> On 6/29/18 2:37 PM, Mark Millard
r335012 (the big patch that added the pNFS server support) revised the
nfsd->kernel
nfssvc(2) syscall interface.
It has compatibility code, so that old nfsd binaries still work.
I now need to revise this interface again to add a new pNFS server feature.
Since the revised interface is only in head
On 2018-Jun-30, at 10:04 AM, Mark Millard wrote:
> On 2018-Jun-30, at 9:29 AM, John Baldwin wrote:
>
>> On 6/30/18 9:17 AM, Mark Millard wrote:
>>> On 2018-Jun-30, at 7:51 AM, John Baldwin wrote:
>>>
On 6/29/18 2:37 PM, Mark Millard wrote:
> [I expect this is more than just amd64-
On 2018-Jun-30, at 9:29 AM, John Baldwin wrote:
> On 6/30/18 9:17 AM, Mark Millard wrote:
>> On 2018-Jun-30, at 7:51 AM, John Baldwin wrote:
>>
>>> On 6/29/18 2:37 PM, Mark Millard wrote:
[I expect this is more than just amd64-gcc related but that is all
that ci.freebsd.org normally b
On 6/30/18 9:17 AM, Mark Millard wrote:
> On 2018-Jun-30, at 7:51 AM, John Baldwin wrote:
>
>> On 6/29/18 2:37 PM, Mark Millard wrote:
>>> [I expect this is more than just amd64-gcc related but that is all
>>> that ci.freebsd.org normally builds via a devel/*-gcc .]
>>
>> As indicated by my other
On 2018-Jun-30, at 7:51 AM, John Baldwin wrote:
> On 6/29/18 2:37 PM, Mark Millard wrote:
>> [I expect this is more than just amd64-gcc related but that is all
>> that ci.freebsd.org normally builds via a devel/*-gcc .]
>
> As indicated by my other mail, this is i386 and amd64 specific as it
> o
On 6/29/18 2:37 PM, Mark Millard wrote:
> [I expect this is more than just amd64-gcc related but that is all
> that ci.freebsd.org normally builds via a devel/*-gcc .]
As indicated by my other mail, this is i386 and amd64 specific as it
only matters for float.h on i386 due to the disagreement on
L
On 30 Jun 2018, at 15:22, Mark Millard wrote:
>
> https://ci.freebsd.org/job/FreeBSD-head-aarch64-build/8358/consoleText
>
> --- all_subdir_armv8crypto ---
> /usr/src/sys/crypto/armv8/armv8_crypto_wrap.c:46:10: fatal error:
> 'arm_neon.h' file not found
> #include
> ^~~~
> 1 er
https://ci.freebsd.org/job/FreeBSD-head-aarch64-build/8358/consoleText
--- all_subdir_armv8crypto ---
/usr/src/sys/crypto/armv8/armv8_crypto_wrap.c:46:10: fatal error: 'arm_neon.h'
file not found
#include
^~~~
1 error generated.
*** [armv8_crypto_wrap.o] Error code 1
https://c
On 30 Jun 2018, at 04:03, Larry Rosenman wrote:
>
> I'm running Exim, with DNSSEC enabled, and my zone (lerctr.org) is
> DNSSEC signed, but my dyn.lerctr.org subdomain is NOT DNSSEC signed due
> to HE.net don't support DNSSEC.
>
> I get a ton of:
> Jun 29 20:12:53 thebighonker exim[37649]: getho
12 matches
Mail list logo
