From owner-freebsd-hackers Tue Oct 26 10:33:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from green.myip.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B8F5114D4E; Tue, 26 Oct 1999 10:33:12 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost ([127.0.0.1] ident=green) by green.myip.org with esmtp (Exim 3.02 #1) id 11gAT2-000GhY-00; Tue, 26 Oct 1999 13:33:04 -0400 Date: Tue, 26 Oct 1999 13:33:02 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: Kris Kennaway Cc: Pascal Hofstee , freebsd-hackers@freebsd.org, arch@freebsd.org Subject: Re: module names In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I, for one, like what was suggested a long time ago, by someone who I cannot really remember. It separated driver "classes" in /modules subdirectories. For instance, we could have a "net" for the if_foo drivers, "storage" for CAM/ATA/RAID/Vinum/CCD/etc., "periph" for various esoteric peripherals, "exec" for exec formats like svr4/linux/ ibcs2, "video" for vesa/*_saver, "fs" for filesystems (separate from storage), and "netsub" for ipfw/streams/loadable socket domains. I think that, perhaps, there should be a "bus" where pccard, usb, and SCSI cards would go (instead of "storage"). Currently, we don't have way too many modules, so I'm happy with what's here now. I definitely think there's room for improvement in how /modules is organized, but remember that the format came straight from what we used to have in /lkm. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message