Date: Mon, 26 Jul 1999 12:50:58 -0400 (EDT) From: Alfred Perlstein <bright@rush.net> To: Dag-Erling Smorgrav <des@flood.ping.uio.no> Cc: Brian Somers <brian@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/net if_tun.c Message-ID: <Pine.BSF.3.96.990726124834.20420E-100000@cygnus.rush.net> In-Reply-To: <xzphfmr8is3.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On 26 Jul 1999, Dag-Erling Smorgrav wrote: > Alfred Perlstein <bright@rush.net> writes: > > On Mon, 26 Jul 1999, Brian Somers wrote: > > > brian 1999/07/26 05:11:11 PDT > > > Log: > > > Don't complain if 0 bytes are written to the tun device, simply > > > do nothing. > > can you MFC this, there's no point in having current's and > > stable's API differ? > > Can you guarantee that it doesn't break anything? Before my patch it would panic both -current and -stable. > (BTW, this is semantics, not API, and I can think of a zillion other > ways in which the semantics of -CURRENT differ from those of -STABLE) yes, but my patch went in two days ago, and the API was changed just now. I still think it's an error to write a zero length packet to the tun device, but the API should be consistant. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.990726124834.20420E-100000>