Hi,
saw something like this missing:
diff --git a/sys/arch/arm/include/sysreg.h b/sys/arch/arm/include/sysreg.h
index c2aab7d6667..f41a3b362ec 100644
--- a/sys/arch/arm/include/sysreg.h
+++ b/sys/arch/arm/include/sysreg.h
@@ -269,4 +269,20 @@
*/
#define CP15_CBAR(rr) p15, 4, rr, c15,
5 weeks ago at d2k17 I started work on randomized kernels. I've been
having conversations with other developers for nearly 5 years on the
topic... but never got off to a good start, probably because I was
trying to pawn the work off on others.
Having done this, I really had no idea we'd end up wh
Hello,
I will brief the reason why I have written a minimal script that does the same
work as the program installboot(8) (at least what I needed).
I had compiled the boot(8) for i386, and I was wondering how to test it, but I
did not brave enough for testing in the hard disk of my computer (t
On Mon, Jun 26, 2017 at 02:35:55PM -0600, Theo de Raadt wrote:
> There is a diff in snapshots which does kernel relinking during
> install or upgrade.
>
> Really amazing...
This is now committed to the tree.
--
-=[rpe]=-
On Fri, Jun 30, 2017 at 04:43:06PM +0200, Claudio Jeker wrote:
> Would like to commit this so I can move on.
Just some remarks about variable naming. But please commit as it
is, cleanup on uncommited diffs is difficult.
> -struct pfkeyv2_socket {
> - LIST_ENTRY(pfkeyv2_socket) kcb_list;
On Fri, Jun 30, 2017 at 09:19:31AM -0600, Anthony J. Bentley wrote:
> Christian Weisgerber writes:
> > On 2017-06-29, "Anthony J. Bentley" wrote:
> >
> > > The vi manual is long enough. It doesn't seem very helpful to keep stubs
> > > that have been stubs for 20 years.
> >
> > Should we retain s
Christian Weisgerber writes:
> On 2017-06-29, "Anthony J. Bentley" wrote:
>
> > The vi manual is long enough. It doesn't seem very helpful to keep stubs
> > that have been stubs for 20 years.
>
> Should we retain some documentation along the lines of "nex/nvi
> does not implement the following o
On Tue, May 30, 2017 at 01:59:23PM +0200, Claudio Jeker wrote:
> This is a step I need to do to make progress on the PF_KEY cleanup I'm
> doing. Both PF_ROUTE and PF_KEY need to start to take care of their own
> PCB list and so move the LIST_ENTRY out of rawcb into routecb.
> This allows me to do t
On 2017-06-29, "Anthony J. Bentley" wrote:
> The vi manual is long enough. It doesn't seem very helpful to keep stubs
> that have been stubs for 20 years.
Should we retain some documentation along the lines of "nex/nvi
does not implement the following options from the original ex/vi:
..."?
--