Date: Thu, 21 Jan 1999 15:10:44 -0500 From: Christian Kuhtz <ck@adsu.bellsouth.com> To: Mike Smith <mike@smith.net.au> Cc: current@FreeBSD.ORG Subject: kld meta info (Re: KLD naming) Message-ID: <19990121151044.B5050@oreo.adsu.bellsouth.com> In-Reply-To: <199901211913.LAA10340@dingo.cdrom.com>; from Mike Smith on Thu, Jan 21, 1999 at 11:13:49AM -0800 References: <A6D02246E1ABD2119F5200C0F0303D10FDC7@OCTOPUS> <199901211913.LAA10340@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Is there meta information in a .ko file? That way you could do a kldinfo to
find out where to go for more info, etc.
On Thu, Jan 21, 1999 at 11:13:49AM -0800, Mike Smith wrote:
> 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.
--
"Logic is a little bird, sitting in a tree; that smells *awful*."
-- /usr/bin/fortune
[Disclaimer: I speak for myself and my views are my own and not in any way to
be construed as the views of BellSouth Corporation. ]
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?19990121151044.B5050>