From owner-freebsd-hackers Wed Jan 11 13:08:03 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA10645 for hackers-outgoing; Wed, 11 Jan 1995 13:08:03 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id NAA10638 for ; Wed, 11 Jan 1995 13:08:00 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA24285; Wed, 11 Jan 95 14:02:07 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501112102.AA24285@cs.weber.edu> Subject: Re: sys/netipx To: supervisor@alb.asctmd.com Date: Wed, 11 Jan 95 14:02:06 MST Cc: freebsd-hackers@FreeBSD.org In-Reply-To: from "supervisor@alb.asctmd.com" at Jan 11, 95 11:00:20 am X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > I am working on a hacked version of the netns code in order to conform > more to IPX (ethernet frame type 8137). I am interested in being able to > support IPX and SPX connections using the BSD sockets interface. > THESE CHANGES ARE NOT YET COMPLETE... > > What is an appropriate method to make these changes available for > inclusion into the FreeBSD source tree? Maybe now would be a good time to generalize the protocol family registration mechanism and provide a function interface to do it, as well as getting rid of the #undef UNIX and the word 'UNIX' in referring to socket domains? It would be natural to use an LKM to load a protocol family. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.