From: "Michał Piotrowski" <piotrowskim@trex.wsi.edu.pl>
To: linux-kernel@vger.kernel.org, Jesper Juhl <jesper.juhl@gmail.com>,
Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>,
Paul TT <paultt@bilug.linux.it>,
randy_dunlap <rdunlap@xenotime.net>
Subject: [ANNOUNCE] ORT - Oops Reporting Tool v.b3
Date: Sun, 26 Jun 2005 00:08:52 +0200 [thread overview]
Message-ID: <42BDD5F4.8090801@trex.wsi.edu.pl> (raw)
Hi all,
Here is our (see copyright section ;)) simple script that help to create
a bug report:
http://stud.wsi.edu.pl/~piotrowskim/files/ort/beta/ort-b3.tar.bz2
Why do we do this?
Because many people don't have time to prepare a good (with all
importrant pieces of information) bug report.
How does it work?
It creates file with information about your system (software, hardware,
used modules etc.), add file with oops into it and in the future sends
it to the chosen mainterner or lkml.
How can you help?
If you know something about bash scripting you can review it, add some
useful features and make some optimalisations. Or just send me an idea.
Changelog:
- point_7_9() (/proc copy) (tar.bz2 is toooo big...)
- point_7_10() (/sys copy)
- point_7_11() (sysctl -A)
- ort_sig() ;)
Regards,
Michał Piotrowski
reply other threads:[~2005-06-26 0:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=42BDD5F4.8090801@trex.wsi.edu.pl \
--to=piotrowskim@trex.wsi.edu.pl \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.ciarrocchi@gmail.com \
--cc=paultt@bilug.linux.it \
--cc=rdunlap@xenotime.net \
/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
Powered by JetHome