Date: Thu, 21 Jan 1999 12:11:28 -0800 From: Mike Smith <mike@smith.net.au> To: Christian Kuhtz <ck@adsu.bellsouth.com> Cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG Subject: Re: kld meta info (Re: KLD naming) Message-ID: <199901212011.MAA10797@dingo.cdrom.com> In-Reply-To: Your message of "Thu, 21 Jan 1999 15:10:44 EST." <19990121151044.B5050@oreo.adsu.bellsouth.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. There's not time to standardise this, so I would say that 3.x .ko files won't have metainformation internally, no. Certainly 4.x .ko files will carry a lot more metainformation with them, and that may include this, yes. > 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. ] -- \\ 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?199901212011.MAA10797>