From: "Rafael E. Herrera" <raffo@neuronet.pitt.edu>
To: Matthias Juchem <juchem@uni-mannheim.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bugreporting script - second try
Date: Thu, 11 Jan 2001 09:14:20 -0500 [thread overview]
Message-ID: <3A5DBFBC.88DFEBD7@neuronet.pitt.edu> (raw)
In-Reply-To: <Pine.LNX.4.30.0101111300440.21849-100000@gandalf.math.uni-mannheim.de>
Matthias Juchem wrote:
> http://www.brightice.de/src/bugreport.sh
I have a suggestion, there is a kernel patch to add a config.gz entry in
the /proc fs. It reflects the configuration used in building the running
kernel, which may differ from the one you have in /usr/src/linux. It's
part of the suse distribution. The attached patch will use it, although
you may want to add code to ask the user which one to use.
--- bugreport.sh Thu Jan 11 09:09:00 2001
+++ bugreport.sh_orig Thu Jan 11 08:53:21 2001
@@ -478,16 +478,11 @@
# kernel config
- if [ -f "/proc/config.gz" ]
+ if [ -f "$krn_srcdir/.config" ]
then
- dot_config=`gzip -d < /proc/config.gz|grep -v "^#"|grep CONFIG`
+ dot_config=`cat $krn_srcdir/.config|grep -v "^#"|grep CONFIG`
else
- if [ -f "$krn_srcdir/.config" ]
- then
- dot_config=`cat $krn_srcdir/.config|grep -v "^#"|grep
CONFIG`
- else
- dot_config="not found"
- fi
+ dot_config="not found"
fi
}
--
Rafael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-11 14:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 20:43 Matthias Juchem
2001-01-10 21:18 ` Richard Torkar
2001-01-10 21:26 ` Richard Torkar
2001-01-10 21:33 ` Matthias Juchem
2001-01-11 12:12 ` Matthias Juchem
2001-01-11 14:14 ` Rafael E. Herrera [this message]
2001-01-11 14:27 ` Matthias Juchem
2001-01-11 22:28 ` David Ford
2001-01-10 21:47 ` Mr. James W. Laferriere
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=3A5DBFBC.88DFEBD7@neuronet.pitt.edu \
--to=raffo@neuronet.pitt.edu \
--cc=juchem@uni-mannheim.de \
--cc=linux-kernel@vger.kernel.org \
/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®