From owner-freebsd-current  Wed Jan 20 22:04:21 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA18532
          for freebsd-current-outgoing; Wed, 20 Jan 1999 22:04:21 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18524
          for <current@FreeBSD.ORG>; Wed, 20 Jan 1999 22:04:20 -0800 (PST)
          (envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
	by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id WAA87470;
	Wed, 20 Jan 1999 22:03:45 -0800 (PST)
To: Mike Smith <mike@smith.net.au>
cc: Christian Kuhtz <ck@adsu.bellsouth.com>, "David O'Brien" <obrien@NUXI.com>,
        current@FreeBSD.ORG
Subject: Re: KLD naming 
In-reply-to: Your message of "Wed, 20 Jan 1999 21:56:52 PST."
             <199901210556.VAA06281@dingo.cdrom.com> 
Date: Wed, 20 Jan 1999 22:03:44 -0800
Message-ID: <87466.916898624@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 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)
> 	vfs_		VFS layer (eg. vfs_nfs)
> 	kern_		kernel infrastructure (eg. kern_vfs)
> 	syscall_	loadable system calls (eg. syscall_sendfile)

I like this.  It's the best alternative to an arbitrarily deep
(and much disputed) directory structure I've seen so far.

- Jordan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message