linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.demarchi@profusion.mobi>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
	Richard Farina <sidhayn@gmail.com>,
	Hauke Mehrtens <hauke@hauke-m.de>,
	wireless <linux-wireless@vger.kernel.org>,
	Jon Masters <jcm@jonmasters.org>,
	linux-modules@vger.kernel.org
Subject: Re: [compat-wireless] modprobe -l is legacy compatibility mode and is being removed from some distros
Date: Sat, 4 Feb 2012 11:44:15 -0200	[thread overview]
Message-ID: <20120204134415.GB528@vader> (raw)
In-Reply-To: <874nv8k295.fsf@rustcorp.com.au>

* Rusty Russell <rusty@rustcorp.com.au> [2012-02-03 14:16:30 +1030]:

> On Tue, 31 Jan 2012 15:15:45 -0800, "Luis R. Rodriguez" <mcgrof@gmail.com> wrote:
> > On Tue, Jan 31, 2012 at 6:04 AM, Richard Farina <sidhayn@gmail.com> wrote:
> > > On 01/29/2012 04:39 PM, Hauke Mehrtens wrote:
> > >>
> > >> On 01/24/2012 08:35 PM, Richard Farina wrote:
> > >>>
> > >>> module-init-tools has been deprecated in favor of kmod in Arch Linux,
> > >>> and kmod doesn't have the legacy --list option for modprobe.
> > >>> This patch fixes the areas of the Makefile which actually needed the
> > >>> output of modprobe -l. The other 100's of uses are just to echo info to
> > >>> the screen which in this case will simply fail in an extremely noisy
> > >>> fashion yet non-fatal way.
> > >>>
> > >>> Please apply to all branches.
> > >>>
> > >>> Signed-of-By: Rick Farina<sidhayn@gmail.com>
> > >>>
> > >>> diff -Naur compat-wireless-3.3-rc1-2/Makefile
> > >>> compat-wireless-3.3-rc1-2-modinfo-migration/Makefile
> > >>> --- compat-wireless-3.3-rc1-2/Makefile    2012-01-21 02:00:21.000000000
> > >>> -0500
> > >>> +++ compat-wireless-3.3-rc1-2-modinfo-migration/Makefile    2012-01-24
> > >>> 14:27:20.000000000 -0500
> > >>> @@ -9,11 +9,6 @@
> > >>>  # Sometimes not available in the path
> > >>>  MODPROBE := /sbin/modprobe
> > >>>
> > >>> -ifneq ($(wildcard $(MODPROBE)),)
> > >>> -MADWIFI=$(shell $(MODPROBE) -l ath_pci)
> > >>> -OLD_IWL=$(shell $(MODPROBE) -l iwl4965)
> > >>> -endif
> > >>> -

Why do you need to know this? If you really need this, it can be well
accomplished by 'find'. That's the reason it was removed from modprobe
(and it was already deprecated in module-init-tools).

But what's the point in knowing where the file is?

> > >>
> > >> What happens if modinfo is not available? I do not know on what systems
> > >> this is the case, but I do not think that modinfo is available when
> > >> modprobe is not.
> > >
> > > AFAIK this is never the case.  modinfo is packaged with module-init-tools
> > > and on Arch module-init-tools has been replaced by KMOD which also includes
> > > modinfo.  It would seem to me that at this point modinfo is a required tool
> > > and is always packaged with modprobe.
> > 
> > Rusty, should all Linux distributions that carry modprobe also have modinfo ?
> 
> Yes, at least so far.  But you should make sure the kmod guys are in the
> loop, so they know exactly what you're trying to do.
> 

Yes, let us know what exactly you are trying to accomplish here.


Lucas De Marchi

  reply	other threads:[~2012-02-04 13:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-24 19:35 [compat-wireless] modprobe -l is legacy compatibility mode and is being removed from some distros Richard Farina
2012-01-29 21:39 ` Hauke Mehrtens
2012-01-31 14:04   ` Richard Farina
2012-01-31 23:15     ` Luis R. Rodriguez
2012-02-03  3:46       ` Rusty Russell
2012-02-04 13:44         ` Lucas De Marchi [this message]
2012-01-31 23:14 ` Luis R. Rodriguez
2012-02-03  2:50   ` Richard Farina

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=20120204134415.GB528@vader \
    --to=lucas.demarchi@profusion.mobi \
    --cc=hauke@hauke-m.de \
    --cc=jcm@jonmasters.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=rusty@rustcorp.com.au \
    --cc=sidhayn@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).