From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Udev and Mylex Dac960
Date: Thu, 12 Feb 2004 01:41:38 +0000 [thread overview]
Message-ID: <20040212014138.GB16340@kroah.com> (raw)
In-Reply-To: <4022CB7D.4010505@snscrew.net>
On Sat, Feb 07, 2004 at 08:04:32PM +0100, claude wrote:
> Hi,
>
> I have another question about Mylex Dac960.
>
> Is there any way for udev to create device only for existing array ?
>
> (eg : I only have /dev/rd!c0d0 but udev create /dev/rd!c0d[1-31]).
Well your kernel is saying that you really do have all of those other
devices. You might want to talk to the kernel driver about this...
But yes, you can ignore devices with the following rule:
KERNEL="*c0d[1-31]", NAME=""
The NAME="" section is optional, but a bit nicer to try to figure out
what is happening.
The ability to ignore devices is broken in udev 016, but is now fixed in
the current tree. Try this with the next release (hopefully in a few
days...)
thanks,
greg k-h
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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
next prev parent reply other threads:[~2004-02-12 1:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 23:02 Udev and Mylex Dac960 claude
2004-02-06 0:07 ` Greg KH
2004-02-06 14:40 ` claude
2004-02-07 19:04 ` claude
2004-02-11 23:49 ` Greg KH
2004-02-12 1:41 ` Greg KH [this message]
2004-02-12 2:02 ` claude
2004-02-13 21:05 ` Greg KH
2004-02-16 5:46 ` claude
2004-02-16 5:52 ` Greg KH
2004-02-16 7:35 ` claude
2004-02-16 18:22 ` Greg KH
2004-02-16 20:10 ` claude
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=20040212014138.GB16340@kroah.com \
--to=greg@kroah.com \
--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 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).