From: Ryan Reich <ryanr@uchicago.edu>
To: Harald Dunkel <harald.dunkel@t-online.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.2: "-" or "_", thats the question
Date: Mon, 16 Feb 2004 17:28:37 -0600 [thread overview]
Message-ID: <40315225.3010104@uchicago.edu> (raw)
In-Reply-To: <1pWi8-65a-11@gated-at.bofh.it>
Harald Dunkel wrote:
> Ryan Reich wrote:
>
>> On Mon, 16 Feb 2004, Ryan Reich wrote:
>>
>> Sorry, I didn't realize that your problem was also the inconsistency
>> in module names. Someone else suggested using a shell expansion; you
>> could try
>>
>> cat /proc/modules | tr _ - | grep -q "^${module_name/_/-}"
>>
>> which is both short and works.
>>
> tr is usually in /usr/bin, which might not be available at boot time.
> And probably you mean 'grep -q "^${module_name//_/-}"'
>
> Did I mention that the inconsistency requires ugly and error- prone
> workarounds? QED
It's not THAT ugly, and it's also error-prone to type at the keyboard. The
only fundamental error in my suggestion was the location of tr.
Anyway, if you really want to correct the inconsistencies you need only
edit the sources for the modules in question; the names which appear in
/proc/modules appear to be defined in, for example,
drivers/usb/host/uhci-hcd.c, where the .description section of the module
is set. Or change the filenames, though I don't know how that will fly with
the make process.
--
Ryan Reich
ryanr@uchicago.edu
next parent reply other threads:[~2004-02-16 23:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2004-02-17 6:09 ` 2.6.2: "-" or "_", thats the question 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
[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 ` 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
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=40315225.3010104@uchicago.edu \
--to=ryanr@uchicago.edu \
--cc=harald.dunkel@t-online.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