All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Steven Rostedt <srostedt@redhat.com>,
	linux-kbuild@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] kconfig: dont hardcode path to lsmod
Date: Tue, 19 Jan 2010 01:52:00 -0500	[thread overview]
Message-ID: <1263883920-17289-1-git-send-email-vapier@gentoo.org> (raw)

The lsmod utility has always been installed into /bin with the newer
module-init-tools package, so let lsmod be found via PATH instead of
hardcoding the old modutils /sbin path.

Signed-off-by: Mike Frysinger <vapier@gentoo.org>
---
 scripts/kconfig/streamline_config.pl |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/scripts/kconfig/streamline_config.pl b/scripts/kconfig/streamline_config.pl
index 0d80082..e1dfc8c 100644
--- a/scripts/kconfig/streamline_config.pl
+++ b/scripts/kconfig/streamline_config.pl
@@ -238,7 +238,7 @@ foreach my $makefile (@makefiles) {
 my %modules;
 
 # see what modules are loaded on this system
-open(LIN,"/sbin/lsmod|") || die "Cant lsmod";
+open(LIN,"lsmod|") || die "Cant lsmod";
 while (<LIN>) {
 	next if (/^Module/);  # Skip the first line.
 	if (/^(\S+)/) {
-- 
1.6.6


             reply	other threads:[~2010-01-19  6:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19  6:52 Mike Frysinger [this message]
2010-01-19 14:10 ` [PATCH] kconfig: dont hardcode path to lsmod Steven Rostedt
2010-01-19 14:25 ` Américo Wang
     [not found]   ` <520f0cf11001190822t6d3221bco20739d586608bfde@mail.gmail.com>
2010-01-19 16:29     ` John Kacur
2010-01-19 16:29       ` John Kacur
2010-01-19 16:37       ` Steven Rostedt
2010-01-19 17:37         ` John Kacur
2010-01-19 17:23   ` Mike Frysinger
2010-01-19 17:38     ` Steven Rostedt
2010-01-19 17:42     ` John Kacur
2010-01-19 17:54       ` Mike Frysinger
2010-01-19 18:12         ` John Kacur
2010-01-19 19:18           ` Mike Frysinger
2010-01-20  3:16             ` Américo Wang

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=1263883920-17289-1-git-send-email-vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srostedt@redhat.com \
    /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.