Date: Tue, 26 Oct 1999 13:33:02 -0400 (EDT) From: Brian Fundakowski Feldman <green@freebsd.org> To: Kris Kennaway <kris@hub.freebsd.org> Cc: Pascal Hofstee <daeron@Wit401305.student.utwente.nl>, freebsd-hackers@freebsd.org, arch@freebsd.org Subject: Re: module names Message-ID: <Pine.BSF.4.10.9910261323280.51807-100000@green.myip.org> In-Reply-To: <Pine.BSF.4.10.9910251528270.89815-100000@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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-arch" 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.10.9910261323280.51807-100000>