>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 majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
