On Mon, Jul 30, 2018 at 10:24:03AM -0600, Base Pr1me wrote:
> Sorry, this time with the correct diff.
>
> On 7/25/18 4:15 PM, Base Pr1me wrote:
> > Hi,
> >
> > I discovered that the wrong server configuration is evaluated in the
> > server_read_http function. Only the first server in httpd.conf
Diff below adds support to uvm to create wtite-combining mappings and
uses this to implement support for the I915_MMAP_WC flag in
inteldrm(4). With this diff I can re-enable support for the
I915_PARAM_MMAP_VERSION.
Please test.
Index: dev/pci/drm/i915/i915_dma.c
On 2018/10/26 18:15, Remi Locherer wrote:
> On Fri, Oct 26, 2018 at 06:01:40PM +0200, Florian Obser wrote:
> > This breaks usage of the "include" keyword. Something that all the parse.y
> > daemons support.
> >
>
> Oh, of course!
>
> I guess this is similar to unveil files based on a list of
On Fri, Oct 26, 2018 at 01:55:08PM +0200, Christian Weisgerber wrote:
> Move the calculation of the entry point to after the description
> of the .text section. LOADADDR(.text) is not available earlier
> with lld.
>
> With this, lld builds working kernels on i386.
>
> Also: Should this be
Remi Locherer wrote:
> On Fri, Oct 26, 2018 at 06:01:40PM +0200, Florian Obser wrote:
> > This breaks usage of the "include" keyword. Something that all the parse.y
> > daemons support.
> >
>
> Oh, of course!
>
> I guess this is similar to unveil files based on a list of command line args.
On Fri, Oct 26, 2018 at 06:01:40PM +0200, Florian Obser wrote:
> This breaks usage of the "include" keyword. Something that all the parse.y
> daemons support.
>
Oh, of course!
I guess this is similar to unveil files based on a list of command line args.
> On October 26, 2018 5:26:06 PM
This breaks usage of the "include" keyword. Something that all the parse.y
daemons support.
On October 26, 2018 5:26:06 PM GMT+02:00, Remi Locherer
wrote:
>Hi,
>
>this restricts ospfd's parent process to only read it's config file
>(reload)
>and unlink the control socket on exit. I added
Hi,
this restricts ospfd's parent process to only read it's config file (reload)
and unlink the control socket on exit. I added unveil after the setup of
the control socket is done since chmod is used in control_init.
OK?
Remi
Index: ospfd.c
> Date: Fri, 26 Oct 2018 16:38:03 +0200
> From: Christian Weisgerber
>
> Mark Kettenis:
>
> > I wonder though whether we can simply replace ENTRY(start_phys) with
> > ENTRY(start) like we do on amd64. The bootloader strips the high bits
> > from the entry point address already, so using the
I am a little surprised, but if it works..
> > I wonder though whether we can simply replace ENTRY(start_phys) with
> > ENTRY(start) like we do on amd64. The bootloader strips the high bits
> > from the entry point address already, so using the virtual address as
> > the entry point address
Mark Kettenis:
> I wonder though whether we can simply replace ENTRY(start_phys) with
> ENTRY(start) like we do on amd64. The bootloader strips the high bits
> from the entry point address already, so using the virtual address as
> the entry point address should work.
/me builds & boots kernel
> Date: Fri, 26 Oct 2018 14:01:07 +0200
> From: Christian Weisgerber
>
> Correct linker emulation name for lld when building i386 kernels
> on amd64.
ok kettenis@
>
> (Does anybody build i386 kernels on amd64? Apparently nobody has
> since the lld switch.)
Well, I did, and had the same diff
> Date: Fri, 26 Oct 2018 13:55:08 +0200
> From: Christian Weisgerber
>
> Move the calculation of the entry point to after the description
> of the .text section. LOADADDR(.text) is not available earlier
> with lld.
>
> With this, lld builds working kernels on i386.
>
> Also: Should this be
Correct linker emulation name for lld when building i386 kernels
on amd64.
(Does anybody build i386 kernels on amd64? Apparently nobody has
since the lld switch.)
Index: sys/arch/i386/conf/Makefile.i386
===
RCS file:
Move the calculation of the entry point to after the description
of the .text section. LOADADDR(.text) is not available earlier
with lld.
With this, lld builds working kernels on i386.
Also: Should this be __start_phys? It seems odd that we put a
non-reserved symbol into the kernel namespace.
This adds the memory consumed by any kind of as-set, prefix-set,
origin-set or roa-set to the output of show rib mem.
Here the output of a system that has RPKI ROA loaded.
RDE memory statistics
714982 IPv4 unicast network entries using 27.3M of memory
56393 IPv6 unicast network entries
For some reason I am having a hard time running mininet which produces the
forwarding rules.
Anyways here is my code:
import java.io.File;
import java.io.PrintWriter;
import java.io.FileWriter;
import java.util.Collections;
import java.util.LinkedList;
public class Forwarding {
static void
Found by accident or actually a tree where there is no struct aspath_queue
anymore. pathtable.path_hashtbl is a struct aspath_head.
OK?
--
:wq Claudio
Index: rde_rib.c
===
RCS file: /cvs/src/usr.sbin/bgpd/rde_rib.c,v
retrieving
18 matches
Mail list logo
