if the arch can cope with prepending on an unaligned address in
vxlan, then let it do it.
this means less work if we can get away with it.
ok?
Index: if_vxlan.c
===
RCS file: /cvs/src/sys/net/if_vxlan.c,v
retrieving revision 1.49
di
> On 9 Oct 2016, at 09:35, Mike Belopuhov wrote:
>
> After looking into alignment and other issues with encapsulated
> Ethernet frames, turns out that not all our encapsulation drivers
> do a good job of performing header length checks and can
> potentially pass truncated packets into the ether_
Diff below implements the ${ */
- true, /* $< */
true, /* ${@F} */
true, /* ${@D} */
false, /* ${*F} */
@@ -177,6 +179,8 @@ static bool xtlist[] = {
false, /* ${!D} */
true, /* ${%F} */
true, /* ${%D} */
+ true, /* ${context.
Sorry - I responded to the wrong email!
Rob
Ok, thanks for the response. I will review your diff and see what I can do.
Original Message
From: Ingo Schwarze
Sent: Sunday, October 9, 2016 2:26 PM
To: Gleydson Soares
Cc: tech@openbsd.org; j...@kerhand.co.uk
Subject: Re: fix uname.3 manpage.
Hi Gleydson,
Gleydson Soares wrote on Sat, Oc
On Sun, Oct 09, 2016 at 02:32:12PM +0200, Matthieu Herrb wrote:
> Hi,
>
> while looking at what is needed to switch the xenocara build system to
> the same kind of scheme as base (no more SUDO, start as root and drop
> privs to $BUILDUSER), I figured out that the global 'includes' step
> done at t
On Sat, 8 Oct 2016, Gleydson Soares wrote:
> I stlumbled upon it, while reading uname(1) code.
...
> --- uname.c 24 Dec 2015 15:01:24 - 1.17
> +++ uname.c 9 Oct 2016 18:41:31 -
> @@ -101,7 +101,7 @@ main(int argc, char *argv[])
> print_mask = PRINT_SYSNAME;
> }
process_domem() and process_checkioperm() were used by systrace(4) and
procfs(4), so they needed to be present even in kernels without the PTRACE
option. Since systrace and procfs are both gone now, the odd conditional
dance in sys_process.c can be simplified.
ok?
Philip
Index: sys_process.
Philip Guenther writes:
>
> On Sat, 8 Oct 2016, Gleydson Soares wrote:
> > uname(3) function returns 0 on successful and -1 on failure.
> > "non-negative value" is wrong here.
>
> Hmm, that's a direct quote from the standard. While our implementation
> only returns zero on success, an applica
On Sat, 8 Oct 2016, Gleydson Soares wrote:
> uname(3) function returns 0 on successful and -1 on failure.
> "non-negative value" is wrong here.
Hmm, that's a direct quote from the standard. While our implementation
only returns zero on success, an application which checked for a return
value of
Hi Gleydson,
Gleydson Soares wrote on Sat, Oct 08, 2016 at 05:50:00PM -0300:
> uname(3) function returns 0 on successful and -1 on failure.
> "non-negative value" is wrong here.
It is not wrong. When uname(3) succeeds, it does return a non-negative
value, even though that may always be 0 depend
uname(3) function returns 0 on successful and -1 on failure.
"non-negative value" is wrong here.
Index: uname.3
===
RCS file: /cvs/src/lib/libc/gen/uname.3,v
retrieving revision 1.15
diff -u -p -r1.15 uname.3
--- uname.3 21 Jan 2
On my Olimex A10s-Olinuxino Micro, time drifts quite fast (something
of the order of a second per minute). The driver is written to use a
32kHz clock. The device tree on both sun4i and sun5i only references
the 24MHz clock though. And the A10s and A13 datasheets don't
document the settings for u
Hi,
while looking at what is needed to switch the xenocara build system to
the same kind of scheme as base (no more SUDO, start as root and drop
privs to $BUILDUSER), I figured out that the global 'includes' step
done at the begin of 'make build' is causing more trouble than it's
solving...
So as
14 matches
Mail list logo
