From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Blacklistiing modules
Date: Sun, 04 Dec 2005 12:21:00 +0000 [thread overview]
Message-ID: <20051204122100.GA18992@vrfy.org> (raw)
In-Reply-To: <43914216.2070403@pcuf.fi>
On Sun, Dec 04, 2005 at 12:38:10PM +0200, Jar wrote:
> >
> > My box has this:
> > $ grep "blacklist orinoco" /etc/modprobe.d/*
> > /etc/modprobe.d/prism2:blacklist orinoco_cs
> > /etc/modprobe.d/prism2:blacklist orinoco_pci
> > /etc/modprobe.d/prism2:blacklist orinoco_plx
> >
> > The blacklist is a native feature of module-init-tools now.
>
> Oh thanks. I can't find modprobe.d directory enywhere. It sems that my Ferora 4 has
> only /etc/hotplug/blacklist and that doesn't work any more with 2.6.14 kernel.
>
> Does anybody know how to do this in Fedora4?
>
> My module init tools version is: module-init-tools-3.1-4
$ cat /etc/fedora-release
Fedora Core release 4 (Rawhide)
$ rpm -qf /etc/modprobe.d
module-init-tools-3.2-0.pre9.1
$ rpm -qf /etc/modprobe.d/blacklist
hwdata-0.172-1
Kay
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2005-12-04 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-03 6:58 Blacklistiing modules Jar
2005-12-03 23:51 ` Kay Sievers
2005-12-04 10:38 ` Jar
2005-12-04 12:21 ` Kay Sievers [this message]
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=20051204122100.GA18992@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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 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.