From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [udev] updated man, subdirs, ownership, namedev enum patches
Date: Thu, 13 Nov 2003 06:23:25 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106870484428329@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106860942327356@msgid-missing>
On Wed, Nov 12, 2003 at 02:23:30PM +0100, Kay Sievers wrote:
> On Tue, Nov 11, 2003 at 07:53:55PM -0800, Greg KH wrote:
> > On Wed, Nov 05, 2003 at 08:31:28PM +0100, Kay Sievers wrote:
> > > 04-namedev.c-cleanup.diff
> > > remove part of udev that appends the kernel enumeration to character devices
> > > in LABEL method: NAME="webcam" results in /udev/webcam0
> >
> > I think this patch breaks partition naming, did you try it on them?
> > Hm, are you sure this patch is correct?
>
> I think so, block devices are handled at line 580. At line 626 the last
> digit from kernel name is appended to _every_ device including char devs.
> Partition naming seems ok with the patch, but i may miss something here.
Hm, if you take those lines out, I can't name a partition with the
number at the end of the name. Yeah, that's a hack, and I need to fix
it up.
> > What happened to your other one
> > where you could put a '%' in the string to put the number into the name?
>
> Alternate patch is attached, but i don't know if it is really useful.
> It substitutes the '%' placeholder in NAME= with the kernel device
> number.
I think we need more than just a %. Users might care about a few things
for the name. Like major, minor, and kernel device number (but it's
tricky to figure out what a device number is, think of sdaa...) I'll
work on fixing this up next.
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
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:[~2003-11-13 6:23 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 [this message]
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
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-106870484428329@msgid-missing \
--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).