Linus Torvalds wrote:
> 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. But
> even that information you really get from a simple "uname -a".
>
> Do we care that when you boot kernel-2.4.5 you get "net-3"? No. Do we care
> that we have quota version "dquot_6.4.0"? No. Do we want to get the
> version printed for every single driver we load? No.
>
> If people care about version printing, it (a) only makes sense for modules
> and (b) should therefore maybe be done by the module loader. And modules
> already have the MODULE_DESCRIPTION() thing, so they should NOT printk it
> on their own. modprobe can do it if it wants to.
As Alan said, driver versions are incredibly useful. People use update
their drivers over top of kernel drivers all the time. Vendors do it
too. "Run dmesg and e-mail me the output" is 1000 times more simple for
end users.
> So let's simply disallow versions, author information, and "good status"
> messages, ok? For stuff that is useful for debugging (but that the driver
> doesn't _know_ is needed), use KERN_DEBUG, so that it doesn't actually end
> up printed on the screen normally.
Note that KERN_DEBUG appears in dmesg by default in 2.4, AFAICS. This
may be a big source of complaints, right there...
Jeff
-- Jeff Garzik | Andre the Giant has a posse. Building 1024 | MandrakeSoft | - 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/
This archive was generated by hypermail 2b29 : Sat Jun 30 2001 - 21:00:20 EST