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) > vfs_ VFS layer (eg. vfs_nfs) > kern_ kernel infrastructure (eg. kern_vfs) > syscall_ loadable system calls (eg. syscall_sendfile) > > I don't think we want to make the mistake of being too specific about > what pigeonhole something falls into. In many cases, we might want new > categories when a new case arises, eg. for USB we might have: > > bus_usb.ko > usb_hub.ko > usb_mouse.ko > usb_keyboard.ko > usb_disk.ko > usb_scanner.ko > ... > > There's no ambiguity here, the names are simple and convey a direct > set of relationships. Your examples (except the first) do a pretty > good job of the same thing.
This is good. As far as I'm concerned, we should go with this. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
