From owner-freebsd-hackers Tue Dec 5 08:30:14 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA14271 for hackers-outgoing; Tue, 5 Dec 1995 08:30:14 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id IAA14232 for ; Tue, 5 Dec 1995 08:30:05 -0800 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA02695; Tue, 5 Dec 1995 11:29:21 -0500 Date: Tue, 5 Dec 1995 11:29:21 -0500 From: "Garrett A. Wollman" Message-Id: <9512051629.AA02695@halloran-eldar.lcs.mit.edu> To: Terry Lambert Cc: hackers@FreeBSD.org Subject: Re: ipx on 802.3 In-Reply-To: <199512051602.JAA01852@phaeton.artisoft.com> References: <9512051522.AA02613@halloran-eldar.lcs.mit.edu> <199512051602.JAA01852@phaeton.artisoft.com> Sender: owner-hackers@FreeBSD.org Precedence: bulk < said: >> > I believe it is possible to compare the address family in the file >> > /sys/net/if.c in the function ifioctl() for "case SIOCSIFFLAGS" >> > (at about line 531) to determin if AF_IPX is being used, and if so, >> > interpret the values of IFF_LINK[0-2] differently. >> >> Compare the address family of what? > Of the socket on which the ioctl call is being made. Probably have to > propagate a couple of fields on te dispatch. Ummm, the /protocol/ (nb: not address) family of the socket is totally irrelevant to all of the current ioctls /by design/; now you're proposing to undo that cleanup? -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant