Date: Thu, 21 Jan 1999 17:59:05 -0000 From: paul@originative.co.uk To: julian@whistle.com, paul@originative.co.uk Cc: mike@smith.net.au, ck@adsu.bellsouth.com, obrien@NUXI.com, current@FreeBSD.ORG Subject: RE: KLD naming Message-ID: <A6D02246E1ABD2119F5200C0F0303D10FDC7@OCTOPUS>
next in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: Julian Elischer [mailto:julian@whistle.com] > Sent: Thursday, January 21, 1999 5:39 PM > To: paul@originative.co.uk > Cc: mike@smith.net.au; ck@adsu.bellsouth.com; obrien@NUXI.com; > current@FreeBSD.ORG > Subject: RE: KLD naming > > Well whistle is giving htis away so we don'tthink it should > be whistle_xxx > any more than the kernel should be UCB/... > It occur to me that eventually every single device driver > will be a KLD > an also a lot of other things besides... > there are going to be a LOT of files in /modules.... Ok, in this case maybe it doesn't apply but in general we should determine what the guidelines for third party module developers should be to avoid namespace clashes. I though a FreeBSD prefix for modules shipped as part of FreeBSD would be useful to list all those modules that are *not* third party supplied when you've got a directory full of the things. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A6D02246E1ABD2119F5200C0F0303D10FDC7>