public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Dominik Kubla <dominik@kubla.de>
Cc: linux-kernel@vger.kernel.org, linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [ANNOUNCE] udev 021 release
Date: Wed, 10 Mar 2004 14:53:41 -0800	[thread overview]
Message-ID: <20040310225341.GF24336@kroah.com> (raw)
In-Reply-To: <40482ACC.3070504@kubla.de>

On Fri, Mar 05, 2004 at 08:22:52AM +0100, Dominik Kubla wrote:
> >Permissions are based on the name of the device.
> >
> 
> Oh, i realized that. But my point is: shouldn't they be based on the 
> CLASS of the device rather than the name? After all the names are 
> changeable, but the class is not...
> 
> I checked the hotplug-devel archives and saw that somebody has already
> posted a patch doing that. So i guess the question boils down to:
> Will you accept it or not?

Ok, I'm convinced now.  I just took a patch that does this.

> >>Is there a way to distinguish between CD-ROM, DVD-ROM and writers? It is
> >>not unusual  these days to  have at least a  DVD-ROM and CD-Writer  in a
> >>desktop system. If you look at the  latest offers from Dell you will see
> >>that they tend to include a DVD-ROM  and a DVD+RW drive in at least some
> >>configurations. So  it would  be nice  if udev would  be able  to create
> >>links like "cdwriter", "dvd" and "dvdwriter" out of the box. (And assign
> >>the appropriate group to the device nodes...)
> >
> >
> >You can do that, just name them differently based on the type of device.
> >Also, try providing a symlink to "cdrom" to not break what users are
> >expecting.
> 
> Would you care to explain how to do it?

Is there some way that you can see in sysfs or in /proc that you can use
to detect these devices differently?

thanks,

greg k-h

  reply	other threads:[~2004-03-10 23:07 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03  0:09 [ANNOUNCE] udev 021 release Greg KH
2004-03-03  0:25 ` Greg KH
2004-03-03  9:56 ` Michael Weiser
2004-03-03 12:22   ` Ed Tomlinson
2004-03-03 15:14     ` Greg KH
2004-03-03 19:28       ` David Brownell
2004-03-03 22:53       ` Michael Weiser
2004-03-04  1:25         ` Greg KH
2004-03-04  3:58           ` Bill Nottingham
2004-03-04 18:26             ` Greg KH
2004-03-04 11:30           ` Romano Giannetti
2004-03-04  1:22       ` Marco d'Itri
2004-03-04  1:28         ` Greg KH
2004-03-04  9:27           ` Michael Weiser
2004-03-03 15:15   ` Greg KH
2004-03-03 23:56     ` Michael Weiser
2004-03-04  1:19       ` Greg KH
2004-03-04  6:37 ` Dominik Kubla
2004-03-04 18:44   ` Greg KH
2004-03-05  7:22     ` Dominik Kubla
2004-03-10 22:53       ` Greg KH [this message]
2004-03-04 17:48 ` Martin Schlemmer
2004-03-04 18:46   ` Greg KH
2004-03-04 18:56     ` Martin Schlemmer
2004-03-10 12:56 ` Prakash K. Cheemplavam
2004-03-10 22:51   ` Greg KH
2004-03-10 23:17     ` Prakash K. Cheemplavam
2004-03-11  1:21       ` Greg KH
2004-03-13  9:34         ` Prakash K. Cheemplavam
     [not found] <1vshj-2ou-9@gated-at.bofh.it>
     [not found] ` <1vBuj-3YL-17@gated-at.bofh.it>
2004-03-03 13:51   ` Pascal Schmidt
     [not found] <20040303153403.21649.81059.Mailman@linux.us.dell.com>
     [not found] ` <4048D503.10808@mail.ru>
2004-03-09  8:19   ` Greg KH
2004-03-09 10:16     ` rihad
2004-03-09 13:43       ` Alex Goddard
2004-03-10 22:52       ` Greg KH
     [not found] <fa.dbn18ei.1k46o3i@ifi.uio.no>
     [not found] ` <fa.afjk56q.t0ulic@ifi.uio.no>
2004-03-10 13:02   ` walt
2004-03-10 21:01     ` Prakash K. Cheemplavam
     [not found] <fa.fkf6pbs.vk4328@ifi.uio.no>
     [not found] ` <fa.aj3o3v7.pgqn9l@ifi.uio.no>
2004-03-10 23:01   ` walt
2004-03-11  0:11     ` Prakash K. Cheemplavam

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=20040310225341.GF24336@kroah.com \
    --to=greg@kroah.com \
    --cc=dominik@kubla.de \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@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