lkml.org 
[lkml]   [2001]   [Jun]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Cosmetic JFFS patch.
On Thu, Jun 28, 2001 at 06:18:24PM +0100, David Woodhouse wrote:
>
>
> torvalds@transmeta.com said:
> > Things like version strings etc sound useful, but the fact is that the
> > only _real_ problem it has ever solved for anybody is when somebody
> > thinks they install a new kernel, and forgets to run "lilo" or
> > something.
>
> I can give counter-examples of times when it's been extremely useful to
> know exactly what version the user is running, and the info messages
> included in their first bug report have told me exactly what I needed to
> know.
>
> Only for code which is always distributed as part of the kernel, and where
> there are never any more up to date versions in the maintainer's tree, even
> temporarily.
Indeed, and even if you're talking about kernel x.y.z the
user might in fact be running a vendor-patched kernel with a newer
version of the driver (and the author would still have to find out
what version of the driver was included).

For other things the version string is pretty useless as it isn't ever
updated (e.g. networking), and there the kernel version is enough
information.

What I'd propose is a recommendation that modules in
addition to the "useful" information a module should print
a maximum of one line (80 chars), and the author gets to
choose what they want in there, version information, driver homepage,
copyright, sponsor, whatever.

I just hope we never get to the point of having a "Memory leak removal
sponsored by Tampax" boot message ;)

--
Pekka Pietikainen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:55    [W:0.110 / U:1.684 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site