From owner-freebsd-hackers Mon Oct 25 15: 0:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id DFF3B14CC1 for ; Mon, 25 Oct 1999 15:00:37 -0700 (PDT) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1001) id DFBFA221; Tue, 26 Oct 1999 00:00:32 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by shadowmere.student.utwente.nl (Postfix) with ESMTP id 6607D20A for ; Tue, 26 Oct 1999 00:00:32 +0200 (CEST) Date: Tue, 26 Oct 1999 00:00:32 +0200 (CEST) From: Pascal Hofstee To: freebsd-hackers@freebsd.org Subject: module names 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 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 filesystem modules saver_* : For all screensavers (probably would prefer a shorter prefix) emu_* : For binary compatibilty modules like linux/ibcs2/svr4 of course this is just a suggestion ... just thought i would voice it here. -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message