Re: ospfd: depend on interface (new feature)

2018-02-03 Thread Sebastian Benoit
Remi Locherer(remi.loche...@relo.ch) on 2018.02.04 00:42:22 +0100: > Hi > > This adds a new feature to ospfd: depend on interface. > > A ospfd.conf using it looks like this: > > --%<-- > redistribute default depend on carp0 > area 0.0.0.0 { > interface em2 { depend on carp0 } > [...]

Re: ospfd: depend on interface (new feature)

2018-02-03 Thread Claudio Jeker
On Sun, Feb 04, 2018 at 12:42:22AM +0100, Remi Locherer wrote: > Hi > > This adds a new feature to ospfd: depend on interface. > > A ospfd.conf using it looks like this: > > --%<-- > redistribute default depend on carp0 > area 0.0.0.0 { > interface em2 { depend on carp0 } > [...] > }

Re: Fix for vi(1) manpage Visual command

2018-02-03 Thread Anthony J. Bentley
Ingo Schwarze writes: > > and the USD docs to update. so a man page fix will not suffice. > > I wouldn't bother. They are not installed, and the base system > doesn't even provide tools to process them. If we ever decide > to do anything with them, they will require a full check of accuracy > any

Re: ospfd: depend on interface (new feature)

2018-02-03 Thread Kapetanakis Giannis
On 04/02/18 01:42, Remi Locherer wrote: Hi This adds a new feature to ospfd: depend on interface. A ospfd.conf using it looks like this: --%<-- redistribute default depend on carp0 area 0.0.0.0 { interface em2 { depend on carp0 } [...] } --%<-- This router would send out the d

Re: [PATCH] libexec/ld.so/dlfcn.c - fix column alignment

2018-02-03 Thread Raf Czlonka
Ping. On Mon, Jan 01, 2018 at 06:17:53PM GMT, Raf Czlonka wrote: > On Mon, Jan 01, 2018 at 08:56:18AM GMT, Mark Kettenis wrote: > > > Date: Mon, 1 Jan 2018 07:49:54 +0100 (CET) > > > From: Mark Kettenis > > > > > > > Date: Mon, 1 Jan 2018 04:20:35 + > > > > From: Raf Czlonka > > > > > > >

Re: Fix for vi(1) manpage Visual command

2018-02-03 Thread Raf Czlonka
On Sun, Feb 04, 2018 at 12:05:47AM GMT, trondd wrote: > On Sat, February 3, 2018 4:28 pm, Ingo Schwarze wrote: > > > >> a good way to do it without adding verbiage would be to not document it! > >> if it really is a crappy quirk, let's just leave it out then. > > > > I actually like that idea, it m

Re: Fix for vi(1) manpage Visual command

2018-02-03 Thread trondd
On Sat, February 3, 2018 4:28 pm, Ingo Schwarze wrote: > >> a good way to do it without adding verbiage would be to not document it! >> if it really is a crappy quirk, let's just leave it out then. > > I actually like that idea, it makes the long list of EX COMMANDS > a bit simpler, making the rele

ospfd: depend on interface (new feature)

2018-02-03 Thread Remi Locherer
Hi This adds a new feature to ospfd: depend on interface. A ospfd.conf using it looks like this: --%<-- redistribute default depend on carp0 area 0.0.0.0 { interface em2 { depend on carp0 } [...] } --%<-- This router would send out the default route and the em2 network with defa

Re: athn(4) USB open firmware support

2018-02-03 Thread Stefan Sperling
On Fri, Nov 17, 2017 at 12:28:35AM +0100, Stefan Sperling wrote: > This diff switches athn(4) USB devices to open source firmware. > > I only have an AR9271 device which I can test with: > athn0 at uhub1 port 2 configuration 1 interface 0 "ATHEROS USB2.0 WLAN" rev > 2.00/1.08 addr 3 > athn0: AR92

Re: Fix for vi(1) manpage Visual command

2018-02-03 Thread Jason McIntyre
On Sat, Feb 03, 2018 at 10:28:20PM +0100, Ingo Schwarze wrote: > > > a good way to do it without adding verbiage would be to not document it! > > if it really is a crappy quirk, let's just leave it out then. > > I actually like that idea, it makes the long list of EX COMMANDS > a bit simpler, mak

Re: Fix for vi(1) manpage Visual command

2018-02-03 Thread Ingo Schwarze
Hi Jason, Jason McIntyre wrote on Sat, Feb 03, 2018 at 08:52:16PM +: > hmm. not that i entirely agree with this sentiment but fair enough, > i will look at updating the USD docs. Thanks. Don't waste your time on that until after commit, of course. > a good way to do it without adding verbi

Re: Fix for vi(1) manpage Visual command

2018-02-03 Thread Jason McIntyre
On Sat, Feb 03, 2018 at 09:28:11PM +0100, Ingo Schwarze wrote: > Hi Jason, > > Jason McIntyre wrote on Sat, Feb 03, 2018 at 07:23:59PM +: > > On Sat, Feb 03, 2018 at 08:10:14PM +0100, Ingo Schwarze wrote: > >> Jason McIntyre wrote on Sat, Feb 03, 2018 at 05:41:01PM +: > > >>> can of worms

Re: Fix for vi(1) manpage Visual command

2018-02-03 Thread Ingo Schwarze
Hi Jason, Jason McIntyre wrote on Sat, Feb 03, 2018 at 07:23:59PM +: > On Sat, Feb 03, 2018 at 08:10:14PM +0100, Ingo Schwarze wrote: >> Jason McIntyre wrote on Sat, Feb 03, 2018 at 05:41:01PM +: >>> can of worms, there's still stuff like :exusage >> I think that can remain as it is. It

shutdown(8): fprintf(stderr -> warnx

2018-02-03 Thread Scott Cheloha
ok? -- Scott Cheloha Index: sbin/shutdown/shutdown.c === RCS file: /cvs/src/sbin/shutdown/shutdown.c,v retrieving revision 1.46 diff -u -p -r1.46 shutdown.c --- sbin/shutdown/shutdown.c3 Apr 2017 20:59:19 - 1.46 +++ sbi

Re: Fix for vi(1) manpage Visual command

2018-02-03 Thread Jason McIntyre
On Sat, Feb 03, 2018 at 08:10:14PM +0100, Ingo Schwarze wrote: > Hi Jason, > > Jason McIntyre wrote on Sat, Feb 03, 2018 at 05:41:01PM +: > > > personally i still think it would be simpler to only list these commands > > once, but note which subset can take a capital letter (and what that > >

Re: Fix for vi(1) manpage Visual command

2018-02-03 Thread Ingo Schwarze
Hi Jason, Jason McIntyre wrote on Sat, Feb 03, 2018 at 05:41:01PM +: > personally i still think it would be simpler to only list these commands > once, but note which subset can take a capital letter (and what that > means). I seems you are right, amybe i should believe you the first time yo

Re: Fix for vi(1) manpage Visual command

2018-02-03 Thread Jason McIntyre
On Sat, Feb 03, 2018 at 05:26:34PM +0100, Ingo Schwarze wrote: > Hi Jason, hi Anthony, > evening. > Jason McIntyre wrote on Sat, Feb 03, 2018 at 02:52:26PM +: > > > ok, but it does not currently say that. hence the original post: > > [Vi]i[sual] > > that seems an obvious mistake, as not

Re: sleep(1): better error messages

2018-02-03 Thread Ingo Schwarze
Hi Scott, Scott Cheloha wrote on Sat, Feb 03, 2018 at 10:08:46AM -0600: > This adds strtonum(3)-style error messages to sleep(1). They're > more informative than the usage statement and they're idiomatic > for numeric input. > > Exiting with EINVAL is really unusual. It went into r1.9. Unless

gem receive watchdog

2018-02-03 Thread Alexander Bluhm
Hi, I have seen some network hangs with my gem(4) interface on sparc64. Receiving packets stopped sometimes, ifconfig down/up made it work again. In the tick timeout handler refill the receive ring if it is empty. The logic is taken from hme(4). Also splnet() should protect the register access a

Re: Fix for vi(1) manpage Visual command

2018-02-03 Thread Ingo Schwarze
Hi Jason, hi Anthony, Jason McIntyre wrote on Sat, Feb 03, 2018 at 02:52:26PM +: > ok, but it does not currently say that. hence the original post: > [Vi]i[sual] > that seems an obvious mistake, as noted in the original post. That section of the manual is full of lies in multiple respe

sleep(1): better error messages

2018-02-03 Thread Scott Cheloha
Hi, This adds strtonum(3)-style error messages to sleep(1). They're more informative than the usage statement and they're idiomatic for numeric input. Exiting with EINVAL is really unusual. It went into r1.9. Unless I'm missing something I think we can just exit with 1, which is consistent wit

Re: Fix for vi(1) manpage Visual command

2018-02-03 Thread Jason McIntyre
On Sat, Feb 03, 2018 at 03:00:15AM -0700, Anthony J. Bentley wrote: > Jason McIntyre writes: > > On Fri, Feb 02, 2018 at 08:17:11PM -0700, Anthony J. Bentley wrote: > > > trondd writes: > > > > The manpage for vi(1) has a small error for the :Visual/:visual > > > > command. > > The > > > > 'V' c

Re: Fix for vi(1) manpage Visual command

2018-02-03 Thread Anthony J. Bentley
Jason McIntyre writes: > On Fri, Feb 02, 2018 at 08:17:11PM -0700, Anthony J. Bentley wrote: > > trondd writes: > > > The manpage for vi(1) has a small error for the :Visual/:visual command. > The > > > 'V' can be capital or lowercase, followed by an 'i' and optionally 'sual' > . Bu > > > t > > >