From: patman@aracnet.com
To: linux-hotplug@vger.kernel.org
Subject: Re: new version of udev has different cd/dvd devices
Date: Thu, 05 Jan 2006 18:50:56 +0000 [thread overview]
Message-ID: <20060105185056.GA23095@aracnet.com> (raw)
In-Reply-To: <43B313ED.40402@bl.com>
On Thu, Jan 05, 2006 at 09:52:44AM -0800, Greg KH wrote:
> On Thu, Jan 05, 2006 at 09:34:02AM -0800, Patrick Mansfield wrote:
> > On Thu, Jan 05, 2006 at 09:03:17AM -0800, Greg KH wrote:
> >
> > > Exactly. The /dev/disk solution is now adopted by all distros that use
> > > udev, so there should not be any problems with this anymore.
> >
> > It does work but is unwieldly, dm and iscsi people have complained when
> > testing with many disks, I also find it unfriendly.
>
> Then propose an additional, friendly, way of doing things in a new
> subdir in /dev/disk to address these issues. I haven't heard of any
That was kind of what I'm doing on this thread. So, use /dev/disk/user
instead of /dev/user.
> complaints, why don't they make them on the linux-hotplug-devel mailing
> list where they might be listened to? :)
Because you'd flame them back to dm-devel ;-)
> > dm already has its own "workaround" to create fixed short (?) names based
> > on id/serial.
>
> Yeah, dm does it's own thing, separate from udev. But that's dm's
> issue, not udev's...
Yes, but they should be using udev.
Can't you NAK or flame their kernel code? :-(
[hopefully i can send email to the list via this address ...]
-- Patrick Mansfield
-------------------------------------------------------
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
next prev parent reply other threads:[~2006-01-05 18:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-28 22:38 new version of udev has different cd/dvd devices Moshe Yudkowsky
2005-12-28 22:50 ` Marco d'Itri
2005-12-28 23:29 ` Kay Sievers
2005-12-29 0:10 ` Moshe Yudkowsky
2005-12-29 0:22 ` Marco d'Itri
2005-12-29 0:44 ` Moshe Yudkowsky
2005-12-29 13:20 ` Phil Howard
2005-12-29 13:36 ` Marco d'Itri
2005-12-29 15:18 ` Phil Howard
2005-12-29 16:57 ` Kay Sievers
2005-12-30 7:46 ` Greg KH
2005-12-30 13:45 ` Phil Howard
2005-12-30 18:09 ` Marco d'Itri
2005-12-30 18:16 ` Darren Salt
2005-12-30 18:49 ` Kay Sievers
2005-12-30 18:56 ` Kay Sievers
2005-12-30 19:12 ` Darren Salt
2005-12-30 19:16 ` Kay Sievers
2005-12-30 19:47 ` Darren Salt
2005-12-30 20:34 ` Kay Sievers
2005-12-30 21:00 ` Darren Salt
2005-12-30 21:45 ` Kay Sievers
2005-12-30 21:58 ` Kay Sievers
2005-12-30 22:51 ` Darren Salt
2005-12-30 23:02 ` Darren Salt
2005-12-30 23:47 ` Marco d'Itri
2005-12-31 0:04 ` Kay Sievers
2005-12-31 0:20 ` Darren Salt
2005-12-31 0:39 ` Marco d'Itri
2006-01-02 10:35 ` Martin Schwenke
2006-01-04 18:48 ` Patrick Mansfield
2006-01-04 21:23 ` Darren Salt
2006-01-05 12:27 ` Marco d'Itri
2006-01-05 17:03 ` Greg KH
2006-01-05 17:52 ` Greg KH
2006-01-05 18:50 ` patman [this message]
2006-01-06 0:50 ` Greg KH
2006-01-06 3:40 ` patman
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=20060105185056.GA23095@aracnet.com \
--to=patman@aracnet.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).