eephy(4)/msk(4) diff for testing

While looking at eephy(4) I noticed that we're toggling the wrong bit to enable auto crossover on the 88E3016 and 88E3082 PHYs. This diff fixes that, but since this changes the bits we set, I'd like some people to test this. Note that this only needs to be tested on machines with 100baseTX varian

anoncvssh.c not in src tree

Hi all, Just curious, is there any reason why anoncvssh.c isn't in the src tree? --patrick

Re: ksh vi mode werase (^W) handling

From dwchand...@stilyagin.com Wed Jun 3 22:45:13 2009 Here's a diff to make ksh vi mode handle werase more like vi. It's really irritating to have whole paths go away on ^W instead of just the last bit. Way cool. -- Aaron W. Hsu | "Gove

Re: Diff for ANSI and KNF on src/games/gomoku/main.c

Stuart Henderson wrote: User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) Content-Type: text/plain; charset=ISO-8859-1; format=flowed if you want to send diffs with thunderbird, you need to disable format=flowed. Darnit! I thought I did that, Sorry! I guess I will just use mutt then. Shou

Re: Diff for ANSI and KNF on src/games/gomoku/main.c

> User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) > Content-Type: text/plain; charset=ISO-8859-1; format=flowed if you want to send diffs with thunderbird, you need to disable format=flowed.

Diff for ANSI and style on src/games/gomoku/stoc.c

Index: stoc.c === RCS file: /cvs/src/games/gomoku/stoc.c,v retrieving revision 1.7 diff -N -u -p stoc.c --- stoc.c 10 Jul 2003 00:03:01 - 1.7 +++ stoc.c 4 Jun 2009 01:54:38 - @@ -61,45 +61,42 @@ static stru

Diff for ANSI and KNF on src/games/gomoku/main.c

Index: main.c === RCS file: /cvs/src/games/gomoku/main.c,v retrieving revision 1.21 diff -N -u -p main.c --- main.c 17 Mar 2008 09:17:56 - 1.21 +++ main.c 4 Jun 2009 01:37:44 - @@ -81,9 +81,7 @@ char *plyr[2];

Re: ksh vi mode werase (^W) handling

Mike Erdely wrote on Wed 3.Jun'09 at 21:29:57 -0400 > On Wed, Jun 03, 2009 at 06:19:15PM -0700, Darrin Chandler wrote: > > Hi, > > > > Here's a diff to make ksh vi mode handle werase more like vi. It's > > really irritating to have whole paths go away on ^W instead of just the > > last bit. >

Re: ksh vi mode werase (^W) handling

On Wed, Jun 03, 2009 at 06:19:15PM -0700, Darrin Chandler wrote: > Hi, > > Here's a diff to make ksh vi mode handle werase more like vi. It's > really irritating to have whole paths go away on ^W instead of just the > last bit. I'm very much in favor of getting this in. It's a major vi-mode anno

ksh vi mode werase (^W) handling

Hi, Here's a diff to make ksh vi mode handle werase more like vi. It's really irritating to have whole paths go away on ^W instead of just the last bit. --- /usr/src/bin/ksh/vi.c Mon Apr 10 07:38:59 2006 +++ vi.cWed Jun 3 16:54:07 2009 @@ -416,9 +416,9 @@ vi_hook(int ch)

diff on ANSI + Style + KNF for src/games/gomoku/bdisp.c

Index: bdisp.c === RCS file: /cvs/src/games/gomoku/bdisp.c,v retrieving revision 1.9 diff -u -p -r1.9 bdisp.c --- bdisp.c 14 Dec 2006 10:15:09 - 1.9 +++ bdisp.c 4 Jun 2009 00:17:36 - @@ -54,12 +54,12 @@ static

Ansi diff for games/gomoku/bdinit.c

Index: bdinit.c === RCS file: /cvs/src/games/gomoku/bdinit.c,v retrieving revision 1.5 diff -u -p -r1.5 bdinit.c --- bdinit.c3 Jun 2003 03:01:39 - 1.5 +++ bdinit.c3 Jun 2009 23:33:19 - @@ -43,8 +43,7 @@ static ch

Re: man page diff for bgpd.conf addressing the short version of network usage statement

Stuart Henderson wrote: On 2009/06/02 22:38, Daniel Ouellet wrote: +deny from any prefix { 192.168.0.0/16, 10/8 } deny from any prefix { 192.168/16, 10/8 } +good="{ 192.168.0.0/16, 172.16.0.0/12, 10/8 }" +bad="{ 224.0.0.0/4, 240/4 }" +ugly="{ 127.0.0.1/8, 169.254/16 }" good="{ 192.168/16,

Patch src/usr.bin/nc/socks.c to consume complete socks IPv6 reply.

I've just been trying to update a socks server to support IPv6 and found that nc wasn't consuming all of the socks connect reply. I think that this patch fixes this. Index: socks.c === RCS file: /cvs/src/usr.bin/nc/socks.c,v retrievi

Re: man page diff for bgpd.conf addressing the short version of network usage statement

On 2009/06/02 22:38, Daniel Ouellet wrote: > +deny from any prefix { 192.168.0.0/16, 10/8 } deny from any prefix { 192.168/16, 10/8 } > +good="{ 192.168.0.0/16, 172.16.0.0/12, 10/8 }" > +bad="{ 224.0.0.0/4, 240/4 }" > +ugly="{ 127.0.0.1/8, 169.254/16 }" good="{ 192.168/16, 172.16/12, 10/8 }" bad