From owner-freebsd-hackers Sat May 29 17:47:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 0BE6514D36 for ; Sat, 29 May 1999 17:47:54 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id RAA12968; Sat, 29 May 1999 17:46:30 -0700 (PDT) Message-Id: <199905300046.RAA12968@implode.root.com> To: Brian Feldman Cc: Luigi Rizzo , hackers@FreeBSD.ORG Subject: Re: proposed socket change (IPFW too? :) In-reply-to: Your message of "Sat, 29 May 1999 10:19:56 EDT." From: David Greenman Reply-To: dg@root.com Date: Sat, 29 May 1999 17:46:29 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Sat, 29 May 1999, Luigi Rizzo wrote: > >> > I'd like to propose a change in struct socket, which should increase its >> > functionality. It should first be noted that, along with my IPFW UID/GID >> > code (which would be nice to have merged into HEAD too, and if I must, I'll >> > clean up the ugly switch part), I included this change. Implementation time >> > would be nil, as would testing. >> >> no objection on the struct socket change (but i just wonder, if there >> are side effects in changing the struct socket, perhaps one might put >> the same parameter in the struct tcpcb/udpcb/inpcb ? after all it is >> being used by ipfw only). > >It's only truly associative with the socket itself, if you think about it. > I'd like to see >what David thinks about this change, since networking is seemingly 'his' > where IPFW is >'yours'. I don't have a problem with it in principle. You should get Garrett's opinion as well, though, as I might be missing something. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message