In article <[EMAIL PROTECTED]>,
Chuck Wolber <[EMAIL PROTECTED]> wrote:
>> Does sed tell you who programmed it on startup?
>>
>> Awk?
>>
>> Perl?
>>
>> Groff?
>>
>> Gcc?
>>
>> See a pattern here?
>
>Yeah, the output of these programms are usually parsed by other programs.
>If they barked version info, that'd be extra code that has to go into
>*EVERY* script that uses them. You're not using the kernel in the same
>capacity.
A counter example that does both, bc does tell us who wrote it
every time we run it (most annoying) and is smart enough to know
when it is not talking to a tty.
% bc
bc 1.05
Copyright 1991, 1992, 1993, 1994, 1997, 1998 Free Software Foundation, Inc.
This is free software with ABSOLUTELY NO WARRANTY.
For details type `warranty'.
1+2
3
% bc > test
1+2
% cat test
3
%
I think listing driver versions on boot with perhaps some diagnostic info
if appropriate is useful. Names and copyrights should be in the source.
--
__O
Lineo - For Embedded Linux Solutions _-\<,_
PGP Fingerprint: 28 E2 A0 15 99 62 9A 00 (_)/ (_) 88 EC A3 EE 2D 1C 15 68
Stuart Lynne <[EMAIL PROTECTED]> www.fireplug.net 604-461-7532
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
