On Mon, Mar 20, 2017 at 01:35:04AM +0100, Mark Kettenis wrote:
> It turns out that pretty much all relevant aarch64 OSes use the same
> layout for transferring registers in their debug interfaces. Except
> for us. That doesn't make sense and would mean I'd have to do
> additional work in my lldb
Hello,
I've sent different patch [1], which was touching same functions some time ago.
The old patch [1] basically splits pf_test_rule() to two functions:
pf_test_rule()
pf_match_rule(), which walks anchor stack recursively. the recursion depth
is limited to 64.
the memory foot
It turns out that pretty much all relevant aarch64 OSes use the same
layout for transferring registers in their debug interfaces. Except
for us. That doesn't make sense and would mean I'd have to do
additional work in my lldb porting efforts.
Diff below revises "struct reg" for amd64 to be
Index: ifstated.c
===
RCS file: /cvs/src/usr.sbin/ifstated/ifstated.c,v
retrieving revision 1.41
diff -u -p -r1.41 ifstated.c
--- ifstated.c 30 May 2013 19:22:48 - 1.41
+++ ifstated.c 20 Mar 2017 00:19:52 -
@@ -50,28
Hi,
I have a question for this patch.
Do you refer to the document below ?
https://tools.ietf.org/html/draft-strombergson-chacha-test-vectors-01
Best regards,
Kinichiro Inoguchi
On Sat, Mar 18, 2017 at 07:56:19AM -0700, Steven Roberts wrote:
> TC3 contained the data for TC4.
> TC4 contained
No way. Building a release does not need doas. You've done something
wrong.
>Added small info to the release man page. Without this step building the
>system gives the error
>
>---
>test -z "doas" || doas rm -f /var/run/testdata_root /var/run/keycommand_root
>doas: Operation not permitted
>***
Hi,
we now have at least two parts of the build system depend on CROSSDIR to
check for a cross-compile environment (ld.so + binutils). Unfortunately
we never really exported CROSSDIR for those so the checks never worked.
This diff exports CROSSDIR for binutils, moves the CROSSDIR define
around
On Sun, Mar 19, 2017 at 03:05:37PM +0530, Hrishikesh Muruk wrote:
> Added small info to the release man page. Without this step building the
> system gives the error
>
> ---
> test -z "doas" || doas rm -f /var/run/testdata_root /var/run/keycommand_root
> doas: Operation not permitted
Thanks. I
> Date: Sun, 19 Mar 2017 20:47:14 +1100
> From: Jonathan Gray
>
> On Sun, Mar 19, 2017 at 05:01:07PM +1100, Jonathan Gray wrote:
> > On Sat, Mar 18, 2017 at 04:29:56PM +0100, Claudio Jeker wrote:
> > > The X270 seems to have a new I219-LM variant that em(4) doesn't know.
> > >
On Sun, Mar 19, 2017 at 05:01:07PM +1100, Jonathan Gray wrote:
> On Sat, Mar 18, 2017 at 04:29:56PM +0100, Claudio Jeker wrote:
> > The X270 seems to have a new I219-LM variant that em(4) doesn't know.
> > Adding it to the driver seems to be enough.
> >
> > OK?
>
> Can you also add the other
Added small info to the release man page. Without this step building the
system gives the error
---
test -z "doas" || doas rm -f /var/run/testdata_root /var/run/keycommand_root
doas: Operation not permitted
*** Error 1 in regress/usr.bin/ssh (Makefile:207 'clean')
*** Error 1 in regress/usr.bin
Nick wrote:
> I found that the current man pages and example file for acme-client
> are confusing and leave one with an imperfect certificate setup, with
> the intermediate certs missing. Doesn't generate an error on
> OpenBSD, but does on some other OSs.
Right. It took me some time to realize
Hello,
I find the openbsd "disk setup" FAQ to not be as helpful as it could
be because it does not mention newfs outside of the "Encrypting
external disks" section. Creating a filesystem with newfs is a step
most people will need to do as part of setting up a disk. Below is a
patch which adds a
On Sat, Mar 18, 2017 at 04:29:56PM +0100, Claudio Jeker wrote:
> The X270 seems to have a new I219-LM variant that em(4) doesn't know.
> Adding it to the driver seems to be enough.
>
> OK?
Can you also add the other variants we don't match and keep the same
name Intel uses?
At the moment we
14 matches
Mail list logo