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! /
[EMAIL PROTECTED] `------------------------------'
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
