Date: Thu, 21 Jan 1999 09:36:31 -0500 From: Christian Kuhtz <ck@adsu.bellsouth.com> To: Doug Rabson <dfr@nlsystems.com> Cc: Mike Smith <mike@smith.net.au>, Christian Kuhtz <ck@adsu.bellsouth.com>, "David O'Brien" <obrien@NUXI.com>, current@FreeBSD.ORG Subject: Re: KLD naming Message-ID: <19990121093631.A31170@oreo.adsu.bellsouth.com> In-Reply-To: <Pine.BSF.4.01.9901210933370.52892-100000@herring.nlsystems.com>; from Doug Rabson on Thu, Jan 21, 1999 at 09:34:28AM %2B0000 References: <199901210556.VAA06281@dingo.cdrom.com> <Pine.BSF.4.01.9901210933370.52892-100000@herring.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 21, 1999 at 09:34:28AM +0000, Doug Rabson wrote:
> On Wed, 20 Jan 1999, Mike Smith wrote:
>
> > I guess it depends on how fancy we want to get. Here are some examples
> > that I've been rolling around; some are fanciful, some practical)
> >
> > dev_ generic device (eg. dev_sio)
> > bus_ bus support (eg. bus_pci)
> > netif_ network interface (eg. netif_ed)
> > netproto_ network protocol (eg. netproto_arp)
> > netdomain_ network domain (eg. netdomain_ip)
How is the difference between netproto & netdomain defined? I'm running into
a case where I can easily turn the stack upside down (say, running frame-relay
over IP over MPLS in an IP tunnel over PPP -- that's almost working actually).
It sounds like netdomain is somehow higher up in the stack than netproto..
even though they're all protocols.
Comments?
Cheers,
Chris
--
"Logic is a little bird, sitting in a tree; that smells *awful*."
-- /usr/bin/fortune
[Disclaimer: I speak for myself and my views are my own and not in any way to
be construed as the views of BellSouth Corporation. ]
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990121093631.A31170>