From: "Riley Williams" <Riley@Williams.Name>
To: "Timothy Miller" <miller@techsource.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: RE: Bug reports: Making sure you provide all system info
Date: Thu, 29 May 2003 22:08:17 +0100 [thread overview]
Message-ID: <BKEGKPICNAKILKJKMHCAMECKECAA.Riley@Williams.Name> (raw)
In-Reply-To: <3ED63ECB.9040705@techsource.com>
Hi Timothy.
> Is there a script people can run which will dig all necessary
> system information out of /proc so that when one wants to report
> a bug, they just run the script and dump the output into the
> lkml email?
>
> I see lots of bug reports which provide very similar kinds of
> information. It seems to be so common a thing to do that it
> should be automated, no?
Back in the 2.2 kernel days, there was a script called ver_linux
that did precisely that. It's still in 2.5.69 but nobody appears
to make use of it any more.
For reference, here's what the one in 2.5.69 produces for one of
my systems:
Q> If some fields are empty or look unusual you may have an old version.
Q> Compare to the current minimal requirements in Documentation/Changes.
Q>
Q> Linux Consulate.LAN.MemAlpha.Co.UK 2.2.14-e2c #5 Tue Jan 25 21:06:15
Q> GMT 2000 i586 unknown
Q>
Q> Gnu C egcs-2.91.66
Q> Gnu make 3.78.1
Q> binutils 2.9.5.0.22
Q> util-linux 2.10f
Q> mount 2.10r
Q> module-init-tools /lib/modules/2.2.14-e2c/misc/appletalk.o
Q> e2fsprogs 1.18
Q> PPP 2.3.11
Q> Linux C Library 1.3.so
Q> Dynamic linker (ldd) 2.1.3
Q> Procps 2.0.7
Q> Net-tools 1.55
Q> Console-tools 0.3.3
Q> Sh-utils 2.0
Q> Modules Loaded slip slhc parport_pc lp parport tulip
Q> nls_iso8859-1 nls_cp437 vfat fat
Best wishes from Riley.
---
* Nothing as pretty as a smile, nothing as ugly as a frown.
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.484 / Virus Database: 282 - Release Date: 27-May-2003
prev parent reply other threads:[~2003-05-29 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 17:09 Timothy Miller
2003-05-29 21:08 ` Riley Williams [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BKEGKPICNAKILKJKMHCAMECKECAA.Riley@Williams.Name \
--to=riley@williams.name \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®