From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: why no "by-label" for removable?
Date: Mon, 31 Oct 2005 14:29:47 +0000 [thread overview]
Message-ID: <20051031142947.GB32463@vrfy.org> (raw)
In-Reply-To: <4365A883.7060105@magellan-technology.com>
On Mon, Oct 31, 2005 at 04:15:47PM +1100, Aras Vaichas wrote:
> I've just been pulling my hair out wondering why I could't create a
> "/dev/disks/by-label" when I finally noticed this common line in udev rules
> examples:
>
> KERNEL="*[!0-9]", SYSFS{removable}="1", GOTO="persistent_end"
>
> Is there a particular reason for this?
>
> The FAQ mentions using a /dev/disks/by-label entry for a PENDRIVE, but
> surely a PENDRIVE would be considered removable and thus the "by-label"
> would never be created?
This rule exists to prevent optical drives from beeing probed for its
filesystem, which doesn't make sense, cause they will not be updated on
media changes.
But right, we may want to identify an optical drive in some smarter way,
or all usb storage drives will need a partition table to work with that
rule. :)
Kay
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
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
prev parent reply other threads:[~2005-10-31 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 5:15 why no "by-label" for removable? Aras Vaichas
2005-10-31 14:29 ` Kay Sievers [this message]
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=20051031142947.GB32463@vrfy.org \
--to=kay.sievers@vrfy.org \
--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).