Re: Removal of deprecated implied connect for TCP

2010-08-31 Thread Robert Watson
On Sun, 29 Aug 2010, Andre Oppermann wrote: When T/TCP RFC1644 support was introduced in r6283 by wollman 15 years ago the semantics of sendto(2) with regard to TCP sockets were changed. It became possible directly do a sendto(2) call with the target address in the *to argument instead of do

Re: Removal of deprecated implied connect for TCP

2010-08-31 Thread Michael Tüxen
On Aug 31, 2010, at 12:04 PM, Robert Watson wrote: > > On Sun, 29 Aug 2010, Andre Oppermann wrote: > >> When T/TCP RFC1644 support was introduced in r6283 by wollman 15 years ago >> the semantics of sendto(2) with regard to TCP sockets were changed. >> >> It became possible directly do a sendt

Re: Removal of deprecated implied connect for TCP

2010-08-31 Thread Andre Oppermann
On 31.08.2010 12:04, Robert Watson wrote: On Sun, 29 Aug 2010, Andre Oppermann wrote: When T/TCP RFC1644 support was introduced in r6283 by wollman 15 years ago the semantics of sendto(2) with regard to TCP sockets were changed. It became possible directly do a sendto(2) call with the target

Re: Removal of deprecated implied connect for TCP

2010-08-31 Thread Andre Oppermann
On 31.08.2010 15:01, Michael Tüxen wrote: On Aug 31, 2010, at 12:04 PM, Robert Watson wrote: On Sun, 29 Aug 2010, Andre Oppermann wrote: When T/TCP RFC1644 support was introduced in r6283 by wollman 15 years ago the semantics of sendto(2) with regard to TCP sockets were changed. It became pos

Re: Removal of deprecated implied connect for TCP

2010-08-31 Thread Garrett Wollman
In article <4c7d02bb.40...@freebsd.org> an...@freebsd.org writes: >sendto() will not be touched or modified. It's just that on a TCP socket >the tcp protocol will not perform an implied connect anymore. The only thing >that changes is TCP dropping a deprecated and experimental extension and >beh

Re: Removal of deprecated implied connect for TCP

2010-08-31 Thread Robert Watson
On Tue, 31 Aug 2010, Andre Oppermann wrote: I'm not entirely comfortable with this change, and would like a chance to cogitate on it a bit more. While I'm not aware of any applications depending on the semantic for TCP, I know that we do use it for UNIX domain sockets. I don't have any plan

Re: kern/150052: wi(4) driver does not work with wlan(4) driver for Lucent Orinoco Cards

2010-08-31 Thread remko
Synopsis: wi(4) driver does not work with wlan(4) driver for Lucent Orinoco Cards Responsible-Changed-From-To: freebsd-i386->freebsd-net Responsible-Changed-By: remko Responsible-Changed-When: Wed Sep 1 05:49:49 UTC 2010 Responsible-Changed-Why: reassign to networking team http://www.freebsd.or