From owner-freebsd-hackers Wed Oct 18 11:42:42 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA15878 for hackers-outgoing; Wed, 18 Oct 1995 11:42:42 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA15873 for ; Wed, 18 Oct 1995 11:42:40 -0700 Received: (from julian@localhost) by ref.tfs.com (8.6.11/8.6.9) id LAA20694; Wed, 18 Oct 1995 11:41:59 -0700 From: Julian Elischer Message-Id: <199510181841.LAA20694@ref.tfs.com> Subject: Re: IPX feedback request -Reply To: supervisor@alb.asctmd.com Date: Wed, 18 Oct 1995 11:41:59 -0700 (PDT) Cc: hackers@FreeBSD.ORG, jhay@mikom.csir.co.za In-Reply-To: from "supervisor@alb.asctmd.com" at Oct 18, 95 10:49:34 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2201 Sender: owner-hackers@FreeBSD.ORG Precedence: bulk I think the first suggestion was closer to the truth.. If you want I will take responsibility for puting these in the source tree.. (I can do both sets if they are compatible..) The only problem is that I don't know much about Novell protocols. Can the two of you make sure your patches don't clash, and are compatible, with each other? If you do I will guarantee that The resulting combined patch will get applied to the tree. This sort of 'falling through the cracks' is something we really have a problem with.. >From My own perspective, I'd say "hey that's great" when I see these patches, but I'd assume someone else will import them because I know nothing about Novell stuff. anyhow, if you two guys can get me patches relative to -current that don't collide. I WILL put them in.. OK? (after checking that they don't break anythign that I DO know about) julian > > >>>>>>>>>>>>>>> > I sent my announcement of IPX for the FreeBSD distribution 5 days ago > and > I haven't received any feedback yet. I know you are all busy and maybe > everyone thought someone else will look at it? :-) > > If I should mail somewhere else please tell me, but according to the > handbook -hackers is the place. > > In case anyone missed my announcement, I placed the file in: > ftp.FreeBSD.ORG/pub/FreeBSD/incoming/ipx-fbsd.tgz > > It supports ipx but not spx. There is diffs for ifconfig and netstat to > understand ipx. The only device driver that I changed was if_ed, > because that is the one we use here. > <<<<<<<<<<<<<<< > I modified netns for routing usage at the beginning of this year for > inclusion in the 2.0-RELEASE source tree. It was a series of patches to > be applied for IPX/SPX compatibility in the 2.0 kernel. > > I uploaded the changes as netipx.tar.z to a couple of archive sites > and sent out an announcement as well; don't get discouraged. There just > appears to be little interest in performing this kind of function. All of my > work on the code patches stopped when there was no feed back. > > For those that are interested: I can send you a copy of the diffs relative > to a 2.0-Release source tree... > > Mike Mitchell > AMTECH Systems Corp > 505-856-8000 > > >