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
Hi,
With the recent addition of more and more KLDs to the /modules directory i
was wondering if perhaps it would be a good idea to name these modules
more consistantly:
if_*: For all network modules (done already)
ng_*: For all netgraph related modules (done already)
fs_*: For all
On Tue, Oct 26, 1999, Pascal Hofstee wrote:
Hi,
With the recent addition of more and more KLDs to the /modules directory i
was wondering if perhaps it would be a good idea to name these modules
more consistantly:
if_*: For all network modules (done already)
ng_*: For all
On Mon, 25 Oct 1999, Chris Costello wrote:
I agree with the idea but some of the name ideas are a little
off. What would Vinum go under?
I also disagree with your usage of ``emu_''. I would prefer
``compat_''.
I agree the names were not choosen perfectly ... I agree on compat_
the
This kind of stuff is better suited to the arch mailing
list..cross-posting.
Kris
On Tue, 26 Oct 1999, Pascal Hofstee wrote:
Hi,
With the recent addition of more and more KLDs to the /modules directory i
was wondering if perhaps it would be a good idea to name these modules
more
5 matches
Mail list logo