From: Anssi Saari <as@sci.fi>
To: linux-hotplug@vger.kernel.org
Subject: Re: NAME{all_partitions}, how does it work?
Date: Sun, 29 Feb 2004 06:02:53 +0000 [thread overview]
Message-ID: <20040229060253.GA24350@sci.fi> (raw)
In-Reply-To: <20040228194404.GA26312@sci.fi>
On Sat, Feb 28, 2004 at 09:19:50PM +0100, Kay Sievers wrote:
> please try:
>
> BUS="scsi", SYSFS_vendor="6-in-1 ", SYSFS_model="CF/MD ", NAME{all_partitions}="cf%n"
Thanks, it works now.
> The attribute belongs to the NAME field not to a format char.
> It's mentioned in the man page :)
Yes, I misunderstood the part saying this:
The NAME field given with the attribute NAME{all_partitions} will create
all 15 partitions of a blockdevice. This may be useful for removable
media devices.
I actually thought the NAME{all_partitions} referred to the device
name I had chosen. This was supported by the next part in the manpage,
"The NAME ,SYMLINK and PROGRAM fields support simple printf-like string
substitution".
Anyway, a working example is always the thing to avoid misunderstandings in
documentation.
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
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:[~2004-02-29 6:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 19:44 NAME{all_partitions}, how does it work? Anssi Saari
2004-02-28 20:19 ` Kay Sievers
2004-02-29 6:02 ` Anssi Saari [this message]
2004-02-29 13:39 ` 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=20040229060253.GA24350@sci.fi \
--to=as@sci.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.