Re: cwm bind changes

On 2016/11/26 14:57, Okan Demirmen wrote: > > In addition, I've changed the 'bind' and 'mousebind' config options to > 'bind-key' and 'bind-mouse', respectively. The 'unmap' option is replaced by > 'unbind-key' and 'unbind-mouse'. By popular request by those who customize > everything, one can

Re: dhcrelay: allow it to work as part of a chain

Patrick Wildt writes: > Hi, > > DHCP requests can be relayed through multiple relays. There are two parts in > the RFC that we don't oblige and thus make dhcrelay impossible to use through > multiple relays. > > The BOOTREQUEST message has a gateway ip addr attribute

Re: cwm bind changes

On 2016/12/05 21:38, Stuart Henderson wrote: > On 2016/11/26 14:57, Okan Demirmen wrote: > > > > In addition, I've changed the 'bind' and 'mousebind' config options to > > 'bind-key' and 'bind-mouse', respectively. The 'unmap' option is replaced by > > 'unbind-key' and 'unbind-mouse'. By popular

Re: cwm bind changes

On Mon 2016.12.05 at 22:16 +, Stuart Henderson wrote: > On 2016/12/05 21:38, Stuart Henderson wrote: > > On 2016/11/26 14:57, Okan Demirmen wrote: > > > > > > In addition, I've changed the 'bind' and 'mousebind' config options to > > > 'bind-key' and 'bind-mouse', respectively. The 'unmap'

[PATCH] softraid.4 move wd(4) examples to sd(4)

In responding to a post on misc@, I noticed that bioctl(8) uses all sd(4) devices in the examples sections while softraid(4) uses wd(4) devices for the chunks. This patch updates softraid.4 to use sd(4) devices as well. I have not used a wd(4) device in years and I think it more confusing to use

ripd(8) fails on P2P links

Hi, I dislike cross-posting/repeated posting but I was advised to do so by mpi@. I just want to make sure my previous mail sent to bugs@ hasn't gone unnoticed. The problem is that ripd(8) is unable to determine the interface on which a RIP packet was received when the source and destination

Re: ripd(8) fails on P2P links

For P2P links, the destination address should be configured as the peer. If so, perhaps this works? Index: packet.c === RCS file: /cvs/src/usr.sbin/ripd/packet.c,v retrieving revision 1.12 diff -u -p -u -r1.12 packet.c --- packet.c

Re: ripd(8) fails on P2P links

Piotr Durlej [pi...@durlej.net] wrote: > > And here is a patch: > Whoops, I missed this part...And unlike mine it is correct, as there may not be a destination configured. I think this is the right way to go. > diff --git a/usr.sbin/ripd/packet.c b/usr.sbin/ripd/packet.c > index

Re: ntpd(8): use stack instead of heap

OK bcook@ On Fri, Dec 2, 2016 at 10:29 AM, Rafael Zalamena wrote: > On Sat, Oct 01, 2016 at 07:05:51PM +0200, Rafael Zalamena wrote: > > The ntpd(8) constraint fork+exec diff changed the way the constraint > > processes are created, but then it introduced new calloc()s to

Re: doas.conf(5): clarify args

Hi Ted, Ted Unangst wrote on Sun, Dec 04, 2016 at 07:52:38PM -0500: > i guess. Thanks for having a look; committed. > What does No do? I don't see any difference. It is useful on two different levels: 1. Semantic: Currently, the word "..." is inside the .Ic macro. So it means "you

Re: update Mesa to 13.0.2

On Sun, Dec 04, 2016 at 10:45:34PM +1100, Jonathan Gray wrote: > cd /usr/xenocara/lib > ftp https://mesa.freedesktop.org/archive/13.0.2/mesa-13.0.2.tar.gz > tar zxf mesa-13.0.2.tar.gz > patch -p0 < /path/to/mesa.diff > > sed -i 's/mesa$/mesa-13.0.2/' Makefile > > build xenocara as normal >

Re: update Mesa to 13.0.2

On Mon, Dec 05, 2016 at 12:20:59PM +0100, Matthieu Herrb wrote: > On Sun, Dec 04, 2016 at 10:45:34PM +1100, Jonathan Gray wrote: > > cd /usr/xenocara/lib > > ftp https://mesa.freedesktop.org/archive/13.0.2/mesa-13.0.2.tar.gz > > tar zxf mesa-13.0.2.tar.gz > > patch -p0 < /path/to/mesa.diff > > >

Re: BFD: route get and route monitor

On 2016 Sep 30 (Fri) at 10:16:19 +0200 (+0200), Peter Hessler wrote: :This diff makes route get and route monitor work. sockaddr_bfd is so we :can play like the other RTAX_* indexes in rti_info of route messages. : :OK? : : :$ route -n monitor :got

Re: ospfd - handling mtu changes

On Tue, Nov 29, 2016 at 12:14:40PM +0100, Jeremie Courreges-Anglas wrote: > Remi Locherer writes: > > > On Sat, Nov 26, 2016 at 09:39:40AM +0100, Jeremie Courreges-Anglas wrote: > >> Remi Locherer writes: > >> > >> > Hi, > >> > > >> > I ran into