Date: Thu, 21 Jan 1999 11:13:49 -0800 From: Mike Smith <mike@smith.net.au> To: paul@originative.co.uk Cc: julian@whistle.com, mike@smith.net.au, ck@adsu.bellsouth.com, obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: KLD naming Message-ID: <199901211913.LAA10340@dingo.cdrom.com> In-Reply-To: Your message of "Thu, 21 Jan 1999 17:59:05 GMT." <A6D02246E1ABD2119F5200C0F0303D10FDC7@OCTOPUS>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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. I've thought about this, and I think it would be a very bad idea. We want to keep this *simple*. In the case of, eg. OSS, one might expect: dev_oss.ko oss_yamaha.ko oss_sb16.ko ... There's no need to add extra crap just to identify the vendor. It doesn't serve any really useful purpose - we will have metainformation elsewhere that can be used to link modules comprising a product together - there's no need to duplicate it in the filename. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com 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?199901211913.LAA10340>