From owner-freebsd-hackers  Thu Apr 20 15:36:11 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id PAA12379
          for hackers-outgoing; Thu, 20 Apr 1995 15:36:11 -0700
Received: from inetgwy.asctmd.com (inetgwy.asctmd.com [198.59.170.33])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA12357
          for <hackers@freebsd.org>; Thu, 20 Apr 1995 15:33:42 -0700
From: SUPERVISOR@alb.asctmd.com
Received: from alb.asctmd.com (alb.asctmd.com [198.59.170.34]) by inetgwy.asctmd.com (8.6.8/8.6.6) with SMTP id RAA15300 for <hackers@freebsd.org>; Thu, 20 Apr 1995 17:41:48 -0600
Received: from ALBUQUERQUE-Message_Server by alb.asctmd.com
	with WordPerfect_Office; Thu, 20 Apr 1995 16:36:13 -0700
Message-Id: <sf968d7d.001@alb.asctmd.com>
X-Mailer: WordPerfect Office 4.0
Date: Thu, 20 Apr 1995 16:33:31 -0700
To: hackers@FreeBSD.org
Subject:  Re: Q: Does anyone know about implementing LAT support?
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

>>>>>>>>>>>>>>>
> I'm think I'm going to use the ifalias support and extend it to AF_LINK  >
sockaddrs.  So if SIOCAIFADDR fails, then I'll fall back to SIOCIFADDR.
>  > The worst thing is that this means all the drivers will have to change
> to support DECnet.  I'll be sure to make my drivers support DECnet
> but I'll leave the other drivers to others.
>  > My goal is to minimize the changes required to the system to support
DECnet.
You should be able to add it to the generic ethernet code...
<<<<<<<<<<<<<<<
Grab a copy of netipx.tar from the archive site (my XNS/IPX hacks to the
kernel) and you can take a look at the *.diffs necessary to add another
protocol family to the kernel. This might be a good starting point...