Skip to contentSkip to conversation

ORT - Oops Reporting Tool v.b4

ANNOUNCE Michał Piotrowski 4 participants 6 messages Jul 3, 2005 – Jul 4, 2005

lore
Share & tools
lore
#0 lore 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-b4.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:
- Cal Peake (greate thanks for big patch ;)){
- remove the need to run the (whole) script as root
- add support for Pine MUA
- add support for nail MUA
- add pager selection
- whitespace cleanup
- user interface consistency
- code simplification
- some other small things
}

Todo before final version:
- more e-mail clients?
- nice ascii logo?

Regards,
Michał Piotrowski

#1 lore raw

Can you make a script that takes an OOPS and finds the right line in the kernel source? I can never remember how to make the kernel build system generate mixed C/ASM output for a specific file.

Signature · 2 lines
Jon Smirl
[email protected]
#2 lore raw

Hi,

Quoted 3 lines · Jon Smirl

Can you make a script that takes an OOPS and finds the right line in the kernel source?

No, because I don't know how.

Regards,
Michał Piotrowski

#3 lore raw
In reply to Michał Piotrowski
Quoted 4 lines · Michał Piotrowski

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-b4.tar.bz2

Quoted 8 lines

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.

Sorry to say that, but:

I definitely won't be interested in bug reports from an automated tool like this. I don't have the time to go through the heaps of information it collects - I need a short and to the point description of the problem from the user. Most of the time less is more, and if something is missing, asking is always an option.

As if bug reports filled exactly in accordance with the "Reporting Bugs" howto from Richard Gooch weren't bad enough.

Quoted 19 lines

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:
- Cal Peake (greate thanks for big patch ;)){
- remove the need to run the (whole) script as root
- add support for Pine MUA
- add support for nail MUA
- add pager selection
- whitespace cleanup
- user interface consistency
- code simplification
- some other small things
}

Todo before final version:
- more e-mail clients?
- nice ascii logo?

Signature · 2 lines
Vojtech Pavlik
SuSE Labs, SuSE CR
#4 lore raw

Hi,

Quoted 4 lines · Vojtech Pavlik

Sorry to say that, but:

Quoted 11 lines

I definitely won't be interested in bug reports from an automated tool like this. I don't have the time to go through the heaps of information it collects - I need a short and to the point description of the problem from the user. Most of the time less is more, and if something is missing, asking is always an option.

As if bug reports filled exactly in accordance with the "Reporting Bugs" howto from Richard Gooch weren't bad enough.

Maybe something like bug report profile:
- short bug report, without things like .config file, dmesg, sysctl
- full bug report
?

Regards,
Michał Piotrowski

#5 lore raw
Quoted 14 lines · Michał Piotrowski

Hi,

Quoted 10 lines · Vojtech Pavlik

Sorry to say that, but:

I definitely won't be interested in bug reports from an automated tool like this. I don't have the time to go through the heaps of information it collects - I need a short and to the point description of the problem from the user. Most of the time less is more, and if something is missing, asking is always an option.

Quoted 8 lines
Quoted 4 lines

As if bug reports filled exactly in accordance with the "Reporting Bugs" howto from Richard Gooch weren't bad enough.

Maybe something like bug report profile:
- short bug report, without things like .config file, dmesg, sysctl
- full bug report
?

- add handle some cmdl options set which will allow choose subset reports.

kloczek

Signature · 4 lines
-----------------------------------------------------------
*Ludzie nie mają problemów, tylko sobie sami je stwarzają*
-----------------------------------------------------------
Tomasz Kłoczko, sys adm @zie.pg.gda.pl|*e-mail: [email protected]*