Date: Thu, 21 Jan 1999 09:44:38 -0800 (PST) From: Julian Elischer <julian@whistle.com> To: Christian Kuhtz <ck@adsu.bellsouth.com> Cc: Doug Rabson <dfr@nlsystems.com>, Mike Smith <mike@smith.net.au>, "David O'Brien" <obrien@NUXI.com>, current@FreeBSD.ORG Subject: Re: KLD naming Message-ID: <Pine.BSF.4.05.9901210944200.703-100000@s204m82.isp.whistle.com> In-Reply-To: <19990121093631.A31170@oreo.adsu.bellsouth.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 21 Jan 1999, Christian Kuhtz wrote: > 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 > 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?Pine.BSF.4.05.9901210944200.703-100000>