From owner-freebsd-current Thu Jan 21 14:16:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05582 for freebsd-current-outgoing; Thu, 21 Jan 1999 14:16:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05566 for ; Thu, 21 Jan 1999 14:16:06 -0800 (PST) (envelope-from paul@originative.co.uk) From: paul@originative.co.uk Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Thu, 21 Jan 1999 21:58:51 -0000 Message-ID: To: mike@smith.net.au Cc: current@FreeBSD.ORG Subject: RE: KLD naming Date: Thu, 21 Jan 1999 21:58:50 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Mike Smith [mailto:mike@smith.net.au] > Sent: Thursday, January 21, 1999 8:25 PM > To: paul@originative.co.uk > Cc: current@FreeBSD.ORG > Subject: Re: KLD naming > ... > Ah, understood. I'd be inclined to use a suffix, so that our > prefix-based classification scheme still worked, eg. > > dev_ahc_Adaptec.ko > kern_descrypt_RSA.ko > > etc. Hmm, wouldn't this impose our kernel structure onto modules? This might not be desirable for external developers, they may just want to provide a single module rather than split the product into submodules that fit our categories. Why not allow SafeCo_firewall.ko rather than netif_foo_SafeCo.ko netproto_bar_SafeCo.ko etc. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message