[ANNOUNCE] ORT - Oops Reporting Tool v.b4

[ANNOUNCE] ORT - Oops Reporting Tool v.b4

[Michał Piotrowski]

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

Re: [ANNOUNCE] ORT - Oops Reporting Tool v.b4

[Jon Smirl]

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.

-- 
Jon Smirl
jonsmirl@gmail.com

Re: [ANNOUNCE] ORT - Oops Reporting Tool v.b4

[Michał Piotrowski]

Hi,

Jon Smirl wrote:

>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

Re: [ANNOUNCE] ORT - Oops Reporting Tool v.b4

[Vojtech Pavlik]

On Sun, Jul 03, 2005 at 04:53:07PM +0200, Michał Piotrowski wrote:

> 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.

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.

> 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?

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: [ANNOUNCE] ORT - Oops Reporting Tool v.b4

[Michał Piotrowski]

Hi,

Vojtech Pavlik wrote:

>
>
>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.
>
>  
>
Maybe something like bug report profile:
- short bug report, without things like .config file, dmesg, sysctl
- full bug report
?

Regards,
Michał Piotrowski

Re: [ANNOUNCE] ORT - Oops Reporting Tool v.b4

[Tomasz Kłoczko]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1069 bytes --]

On Sun, 3 Jul 2005, Michał Piotrowski wrote:

> Hi,
>
> Vojtech Pavlik wrote:
>
>> 
>> 
>> 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.
>> 
>> 
> 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
-- 
-----------------------------------------------------------
*Ludzie nie mają problemów, tylko sobie sami je stwarzają*
-----------------------------------------------------------
Tomasz Kłoczko, sys adm @zie.pg.gda.pl|*e-mail: kloczek@rudy.mif.pg.gda.pl*