From: Tony Breeds <tony@bakeyournoodle.com>
To: Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.2: "-" or "_", thats the question
Date: Thu, 19 Feb 2004 05:58:46 +0800 [thread overview]
Message-ID: <20040218215846.GI2681@bakeyournoodle.com> (raw)
In-Reply-To: <40306F65.8060702@t-online.de>
On Mon, Feb 16, 2004 at 08:21:09AM +0100, Harald Dunkel wrote:
> I know. But this requires some very ugly workarounds outside
> of module-init-tools. For example, if you want to check
> whether a module $module_name has already been loaded, you
> cannot use
>
> grep -q "^${module_name} " /proc/modules
>
> Instead you have to use a workaround like
>
> x="`echo $module_name | sed -e 's/-/_/g'`"
> cat /proc/modules | sed -e 's/-/_/g' | grep -q "^${x} "
>
> This is inefficient and error-prone.
>
> Maybe somebody has another idea for the workaround,
> but I like the first version.
just run modprobe? Then you don't have to care.
IN_KERNEL=$(/sbin/modprobe -vn "${module_name}")
if [ -z "${IN_KERNEL}" ; then
/bin/echo "Module: ${module_name} is in the kernel"
else
/bin/echo "Module: ${module_name} would need to be loaded"
/bin/echo "${IN_KERNEL}"
fi
Or similar. Yeah it's a little ugly but only as prone to failure as
module-init-tools
Yours Tony
linux.conf.au http://lca2005.linux.org.au/
Apr 18-23 2005 The Australian Linux Technical Conference!
next prev parent reply other threads:[~2004-02-18 22:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1o903-5d8-7@gated-at.bofh.it>
[not found] ` <1pkw6-3BU-3@gated-at.bofh.it>
[not found] ` <1prnS-4x8-1@gated-at.bofh.it>
2004-02-15 15:02 ` 2.6.2: "-" or "_", thats the question Ryan Reich
2004-02-16 7:21 ` Harald Dunkel
2004-02-16 8:48 ` Måns Rullgård
2004-02-16 11:11 ` Harald Dunkel
2004-02-16 14:13 ` Ryan Reich
2004-02-16 14:22 ` Ryan Reich
2004-02-16 19:01 ` Harald Dunkel
2004-02-18 21:58 ` Tony Breeds [this message]
[not found] <1pw4i-hM-27@gated-at.bofh.it>
[not found] ` <1pw4i-hM-29@gated-at.bofh.it>
[not found] ` <1pw4i-hM-31@gated-at.bofh.it>
[not found] ` <1pw4i-hM-25@gated-at.bofh.it>
[not found] ` <1pLmG-4E7-5@gated-at.bofh.it>
[not found] ` <1pRLz-21o-33@gated-at.bofh.it>
[not found] ` <1pRVi-2am-27@gated-at.bofh.it>
[not found] ` <1pWi8-65a-11@gated-at.bofh.it>
2004-02-16 23:28 ` Ryan Reich
2004-02-17 6:09 ` Harald Dunkel
2004-02-17 16:02 ` Sam Ravnborg
2004-02-17 16:01 ` Arjan van de Ven
2004-02-17 19:49 ` Harald Dunkel
2004-02-11 19:54 Harald Dunkel
2004-02-15 2:38 ` Coywolf Qi Hunt
2004-02-15 9:58 ` Harald Dunkel
2004-02-17 7:41 ` Rusty Russell
2004-02-18 1:28 ` Wakko Warner
2004-02-18 8:46 ` Harald Dunkel
2004-02-18 17:25 ` Wakko Warner
2004-02-19 1:52 ` Randy.Dunlap
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=20040218215846.GI2681@bakeyournoodle.com \
--to=tony@bakeyournoodle.com \
--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