Re: patch - RFC 4638 increased MTU support for pppoe(8) w/ ppp(8)

2012-01-31 Thread Stuart Henderson
On 2012/01/31 23:53, Ben Gould wrote: > I couldn't get the pppoe server to work on -current, rebuilt -current > yesterday and it now works - user error. > > The following works in all the combinations 5.0 client/server > userland and with -current client/server and with -current pppoe(4). > > --

login_yubikey manpage missing stuff

2012-01-31 Thread Rod Whitworth
Curiosity made me look at login_yubikey and so I looked at its manpage. The synopsis says: login_yubikey [-d] [-s service] user [class] Nowhere was an explanation of -d. Guessing that it was debug I went looking at the source and saw that there was yet another flag unmentioned, to wit, -v. This

Re: patch - RFC 4638 increased MTU support for pppoe(8) w/ ppp(8)

2012-01-31 Thread Ben Gould
I couldn't get the pppoe server to work on -current, rebuilt -current yesterday and it now works - user error. The following works in all the combinations 5.0 client/server userland and with -current client/server and with -current pppoe(4). -- ben Index: client.c =

Re: patch - RFC 4638 increased MTU support for pppoe(8) w/ ppp(8)

2012-01-31 Thread Stuart Henderson
On 2012/01/29 14:18, Ben Gould wrote: > Hi All, > > The following is tested with: > > Stock 5.0 as client & server. > These modification to 5.0 client & server. > Recent pppoe(4) patches for RFC 4638 support applied to 5.0 as the client. > > It appears to be broken in with -current from a few da

Re: man segfault diff

2012-01-31 Thread Tobias Ulmer
Fix my own 'emtpy' typo, spotted by Theo. Index: config.h === RCS file: /home/vcs/cvs/openbsd/src/usr.bin/man/config.h,v retrieving revision 1.5 diff -u -p -r1.5 config.h --- config.h15 Sep 2004 22:20:03 - 1.5 +++ config.

Re: ALPS Touchpads and "pms0: not in sync yet"

2012-01-31 Thread Martin Pieuchot
On 31/01/12(Tue) 16:52, Martin Pieuchot wrote: > Diff below add support for the missing ALPS Dualpoint touchpads to the > pms(4) driver. Most of the work has been done by shadchin@ and should > fix issues you may have seen since pms(4) supports others ALPS devices > (2011/10). > > It adds support

Re: tcpbench: setpgid

2012-01-31 Thread Henning Brauer
* Erik Lax [2012-01-31 16:51]: > I noticed that tcpbench tries to setpgid() for no obvious reason (to > me) since it's not forked anymore. Previously, 2 years ago it was > fork()ed and utilized killpg() etc. Could this be a leftover? I'm > running into issues spawning tcpbench since my parent proc

El Credito y la Cobranza... Una Actividad de Exito en MEX - GDL - MTY

2012-01-31 Thread Obteniendo Grandes Utilidades
CURSO TALLER El Credito y la Cobranza... Una Actividad de Exito Duracion: (1 dia) 8 hrs. Inversion: $4,150 pesos mas IVA Objetivo: Conocer por medio de practicas vivenciales las razones por las que una empresa tiene ixito al otorgar cridito de forma sana acompaqada de una buena administracisn

Re: tcpbench: setpgid

2012-01-31 Thread Christiano F. Haesbaert
On 31 January 2012 13:50, Erik Lax wrote: > Hi, > > I noticed that tcpbench tries to setpgid() for no obvious reason (to me) > since it's not forked anymore. Previously, 2 years ago it was fork()ed and > utilized killpg() etc. Could this be a leftover? I'm running into issues > spawning tcpbench s

add missing ipad usbdevs entries + quirks.

2012-01-31 Thread Brynet
Allows gphoto2 for PTP transfers, plus other libusb stuff in the future. -Bryan. Index: uaudio.c === RCS file: /cvs/src/sys/dev/usb/uaudio.c,v retrieving revision 1.94 diff -u -p -u -r1.94 uaudio.c --- uaudio.c26 Jan 2012 09:00:3

Re: tcpbench: setpgid

2012-01-31 Thread Christiano F. Haesbaert
On 31 January 2012 13:50, Erik Lax wrote: > Hi, > > I noticed that tcpbench tries to setpgid() for no obvious reason (to me) > since it's not forked anymore. Previously, 2 years ago it was fork()ed and > utilized killpg() etc. Could this be a leftover? I'm running into issues > spawning tcpbench s

ALPS Touchpads and "pms0: not in sync yet"

2012-01-31 Thread Martin Pieuchot
Diff below add support for the missing ALPS Dualpoint touchpads to the pms(4) driver. Most of the work has been done by shadchin@ and should fix issues you may have seen since pms(4) supports others ALPS devices (2011/10). It adds support for a slightly different version of the ALPS protocol, whic

tcpbench: setpgid

2012-01-31 Thread Erik Lax
Hi, I noticed that tcpbench tries to setpgid() for no obvious reason (to me) since it's not forked anymore. Previously, 2 years ago it was fork()ed and utilized killpg() etc. Could this be a leftover? I'm running into issues spawning tcpbench since my parent process uses setsid(). I attached

Re: Keycode print mode (-r) for wsconsctl(8)

2012-01-31 Thread Steffen Daode Nurpmeso
Tobias Stoeckmann suggested off-list to keep explicit state of wether rawmode is enabled or not, so that the signal handler doesn't perform useless (and wrong, strictly speaking) work. He also suggested to integrate keycode.c into wsconsctl.c (if i understood correctly ;), but i was unsure about th

Re: diff: fix LCP keepalive failures on L2TP.

2012-01-31 Thread YASUOKA Masahiko
Hi, On Tue, 31 Jan 2012 13:59:17 +0100 "Sebastian Reitenbach" wrote: > However, I noted with tcpdump, listening on tun0: > # tcpdump -n -i tun0 > tcpdump: listening on tun0, link-type LOOP > 13:51:15.354776 > tcpdump: WARNING: compensating for unaligned libpcap packets > 13:51:15.354795 10.66.66

Re: diff: fix LCP keepalive failures on L2TP.

2012-01-31 Thread Sebastian Reitenbach
On Tuesday, January 31, 2012 10:02 CET, "Sebastian Reitenbach" wrote: > On Monday, January 30, 2012 15:43 CET, YASUOKA Masahiko > wrote: > > > On Mon, 30 Jan 2012 22:49:22 +0900 (JST) > > YASUOKA Masahiko wrote: > > > pipex hook in udp_usrreq() mistakenly assumed that `inp' is > > > conn

Re: diff: fix LCP keepalive failures on L2TP.

2012-01-31 Thread Sebastian Reitenbach
On Monday, January 30, 2012 15:43 CET, YASUOKA Masahiko wrote: > On Mon, 30 Jan 2012 22:49:22 +0900 (JST) > YASUOKA Masahiko wrote: > > pipex hook in udp_usrreq() mistakenly assumed that `inp' is > > connected. The hook could not use the destination address properly, > > so it failed to find