From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Udev and Mylex Dac960
Date: Wed, 11 Feb 2004 23:49:44 +0000 [thread overview]
Message-ID: <20040211234944.GA15183@kroah.com> (raw)
In-Reply-To: <4022CB7D.4010505@snscrew.net>
On Fri, Feb 06, 2004 at 03:40:28PM +0100, claude wrote:
> Greg KH wrote:
> >On Fri, Feb 06, 2004 at 12:02:21AM +0100, claude wrote:
> >
> >Depends, do you like that name? :)
> >
> I can't say :). I just want to have right naming. Devices list at
> lanana.org is pretty old, and things change too quickly. I wanted
> to know which name is the right today.
>
> >Can you give me the output of 'tree -d /sys/block' on your system? I
> >think udev just needs to change that '!' character to a '/' to make it
> >correct.
> >
> Yes, the output is below, and I think you're right too ;)
Thanks for the output. I've fixed this in the current udev tree, so the
next release should work just fine for this kind of device.
Please let me know if it doesn't.
Thanks again for reporting this.
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-11 23:49 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 [this message]
2004-02-12 1:41 ` Greg KH
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=20040211234944.GA15183@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).