All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
To: Christian Kujau <evil@g-house.de>
Cc: "Michał Piotrowski" <piotrowskim@trex.wsi.edu.pl>,
	linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] ORT - Oops Reporting Tool
Date: Sun, 26 Jun 2005 20:58:30 +0200	[thread overview]
Message-ID: <4d8e3fd305062611586bda6c30@mail.gmail.com> (raw)
In-Reply-To: <42BDD3FC.8090706@g-house.de>

2005/6/26, Christian Kujau <evil@g-house.de>:
> Paolo Ciarrocchi wrote:
> >
> > The commands that are requiring root capabilties are:
> > lspci -vvv
> > lsusb -v
> 
> i still dislike the idea being forced to be root, does the attached patch
> looks ok?

Just for my understanding, why do you dislike to be forced to be root ?
You are reporting a kernel problem, I don't see any problem in being
root, but I donìt have a clear understing of pro and cons.

> --- ort/ort.sh.orig     2005-06-25 23:42:22.000000000 +0200
> +++ ort/ort.sh  2005-06-25 23:54:32.000000000 +0200
> @@ -34,7 +34,6 @@ EM_CLI=mutt
> 
> help() {
>     echo "Usage: [root@mylinuxbox ~]$ ./ort.sh oops.txt"
> -    echo "You need to be root [uid=0] to run the script"
>     exit 1
> }
> 
> @@ -53,7 +52,12 @@ cmd_line() {
> check_uid() {
>     if [ $UID != "0" ]
>        then
> -           help
> +           echo -n "You should be root [uid=0] to run the script, continue? [y,n]  "
> +           read c
> +           if [ "$c" != "y" ]; then
> +               echo "Aborted."
> +               exit 1
> +           fi
>     fi
> }

This is fine with me.
 
> @@ -274,7 +278,7 @@ point_7_4() {
> 
> point_7_5() {
>     echo -e "\n[7.5.] PCI information" >> $ORT_F
> -    lspci -vvv >> $ORT_F
> +    env PATH=/bin:/usr/bin:/sbin:/usr/sbin lspci -vvv >> $ORT_F

What's the benefit of this change ?

> }
> 
> point_7_6() {
> @@ -286,7 +290,7 @@ point_7_6() {
> 
> point_7_7() {
>     echo -e "\n[7.7.] USB information" >> $ORT_F
> -    lsusb -v >> $ORT_F
> +    env PATH=/bin:/usr/bin:/sbin:/usr/sbin lsusb -v >> $ORT_F
> }
> 
> point_7_8() {
> 
> 


-- 
Paolo

  parent reply	other threads:[~2005-06-26 18:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24 10:50 [ANNOUNCE] ORT - Oops Reporting Tool Michał Piotrowski
2005-06-24 13:42 ` Christian
2005-06-24 15:45   ` randy_dunlap
     [not found]   ` <4d8e3fd3050624085929581341@mail.gmail.com>
2005-06-25 22:00     ` Christian Kujau
2005-06-25 20:19       ` Michał Piotrowski
2005-06-26 18:58       ` Paolo Ciarrocchi [this message]
2005-06-25 14:33 ` Michał Piotrowski

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=4d8e3fd305062611586bda6c30@mail.gmail.com \
    --to=paolo.ciarrocchi@gmail.com \
    --cc=evil@g-house.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piotrowskim@trex.wsi.edu.pl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.