linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [udev] updated man, subdirs, ownership, namedev enum patches
Date: Mon, 17 Nov 2003 17:33:32 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-106909081901262@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106860942327356@msgid-missing>

On Saturday 15 November 2003 17:09, Kay Sievers wrote:

> Oh, I see. Do you mean something like this:
>
> LABEL, BUS="usb", model="Creative Labs WebCam 3",
> NAME="webcam%n-%M:%m-test"

That would at least be part of the solution I'm looking for. How about
extra format characters for bus_id and for the result of a callout program?

What I really need is a way to generate names for my devices without
having to list each one in the configuration file in its own line. With 
the old devfs naming scheme, the dasda1 block device would become visible
as /dev/dasd/0.0.0203/part1, where 0.0.0203 is the bus_id. I've tried 
implementing at least autogeneration of /udev/dasd-0.0.0203p1, but I haven't
found an easy way to get from the partition's sysfs_class_device to the 
corresponding sysfs_device in get_attr().

Also, do I get problems with the database implementation when I try
to use the same configuration file entry for all devices using the same
driver or similar?

	Arnd <><



-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
_______________________________________________
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

  parent reply	other threads:[~2003-11-17 17:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-12  3:53 [udev] updated man, subdirs, ownership, namedev enum patches Greg KH
2003-11-12 13:23 ` Kay Sievers
2003-11-13  6:23 ` Greg KH
2003-11-13  8:30 ` Kay Sievers
2003-11-13 19:49 ` Greg KH
2003-11-15 16:09 ` Kay Sievers
2003-11-17 17:33 ` Arnd Bergmann [this message]
2003-11-18  1:00 ` Greg KH
2003-11-18  1:14 ` Greg KH
2003-11-18  3:15 ` Kay Sievers
2003-11-18 12:09 ` Arnd Bergmann
2003-11-18 12:17 ` Arnd Bergmann
2003-11-19  0:24 ` Greg KH
2003-11-19 23:40 ` Greg KH
2003-11-19 23:42 ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2003-11-05 19:38 Kay Sievers

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=marc-linux-hotplug-106909081901262@msgid-missing \
    --to=arnd@arndb.de \
    --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).