From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 007 release
Date: Mon, 24 Nov 2003 23:40:10 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106971797309954@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106963388124982@msgid-missing>
On Mon, Nov 24, 2003 at 04:19:45AM +0100, Arnd Bergmann wrote:
> On Monday 24 November 2003 01:29, Greg KH wrote:
>
> > I think with the ability to capture the output of the CALLOUT rule,
> > combined with the ability to put format modifiers in the CALLOUT program
> > string, we now have everything in place to emulate the existing devfs
> > naming scheme. Anyone want to verify this or not?
>
> I would prefer to have the ability of creating partition nodes in devfs
> style built-in to udev. Devfs used to call the whole disk e.g.
> "/dev/dasd/0123/disk" and the partitions "/dev/dasd/0123/part[1-3]".
> This can obviously be done with a CALLOUT rule, but its common enough
> to make it a format modifier. AFAIK, this scheme has been used for
> ide, scsi and dasd disks, which is about 99% of all disks ever connected
> to Linux.
Ok, that makes sense. I've applied this patch, but used the 'D'
modifier (for Devfs name). Is that ok with you?
> One thing that does not appear to be possible with udev but was common
> with devfs is to have multiple links for the same device node, e.g.
> /dev/hda1 as well as /dev/ide/host0/bus0/target0/lun0/part1 and
> /dev/disk/0/part1.
Yes, we need to add support for both multiple names, and symlinks. It's
on the TODO list I think (well the symlinks are, multiple names should
be if it isn't.)
thanks,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
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-24 23:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 0:29 [ANNOUNCE] udev 007 release Greg KH
2003-11-24 3:19 ` Arnd Bergmann
2003-11-24 23:40 ` Greg KH [this message]
2003-11-25 13:29 ` Marco d'Itri
2003-11-26 19:28 ` Greg KH
2003-12-01 10:51 ` Marco d'Itri
2003-12-02 0:55 ` Greg KH
2003-12-02 15:16 ` Kay Sievers
2003-12-02 16:27 ` Kay Sievers
2003-12-02 17:21 ` Marco d'Itri
2003-12-02 17:42 ` Kay Sievers
2003-12-02 17:54 ` Greg KH
2003-12-02 17:55 ` Greg KH
2003-12-02 18:04 ` Greg KH
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-106971797309954@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).