From: meino.cramer@gmx.de
To: Gentoo <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Udev confusion: Rules for a mp3 player
Date: Sat, 28 Jun 2014 16:57:55 +0200 [thread overview]
Message-ID: <20140628145755.GB3881@solfire> (raw)
[-- Attachment #1: Type: text/plain, Size: 1881 bytes --]
Hi,
For my mp3-player I want to write udev rules to give better names
to the according entries under /dev
Problem is: Th eplayer has an internal flash, which only holds the firmware
(in my case) and a sd-card slot, in which you can insert a flash card
with music files.
The internal memory has a partition directly on - say - sdb and the
sd-card in the slot is regulary formatted and represents itsself as
sdc and sdc1.
With udevadm I determined the serial number of the device (to make it
unique) and the model ("Internal storage" and "SD card slot"), which
seems to make it easy to buit rules from.
The one and only reason for not being THAT happy is: The rules didn't work.
Here:
http://www.reactivated.net/writing_udev_rules.html
I read some instructions.
It is said that one should not combine elements of one device and more
than one parent.
Is "device" meant as "the entry under /dev" or is it to be understand
as "the electric entity on my desktop (the player)".
I want rules which also work, if another sdcard of a different size is
inserted into the player...
How can I write rules to map the internal storage, the whole device
(aka /dev/sdc) of the sdcard (for example for reformatting reasons)
and the partition of the sdcard (aka /dev/sdc1), which work?
To this email I have attached the gzipped outputs of the according
udevadm calls.
Thank you very much for any help in advance!
Best regards,
mcc
PS:
This is what I have tried and which does *NOT* work!
SUBSYSTEM=="block",ATTRS{model}=="Internal Storage",ATTRS{serial}=="1A8C518301403210B00000000",SYMLINK+="sansaclipzip_root"
SUBSYSTEM=="block",ATTRS{model}=="SD Card Slot ",ATTR{partition}=="1", ATTRS{serial}=="1A8C518301403210B00000000", SYMLINK+="sansaclipzip_data_1"
SUBSYSTEM=="block",ATTRS{model}=="SD Card Slot ",ATTRS{serial}=="1A8C518301403210B00000000", SYMLINK+="sansaclipzip_data"
[-- Attachment #2: sansadatadevice.txt.gz --]
[-- Type: application/x-gunzip, Size: 1457 bytes --]
[-- Attachment #3: sansadatapartition.txt.gz --]
[-- Type: application/x-gunzip, Size: 1531 bytes --]
[-- Attachment #4: sansainternal.txt.gz --]
[-- Type: application/x-gunzip, Size: 1447 bytes --]
next reply other threads:[~2014-06-28 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 14:57 meino.cramer [this message]
2014-06-28 17:43 ` [gentoo-user] Udev confusion: Rules for a mp3 player Jc García
2014-06-28 18:05 ` meino.cramer
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=20140628145755.GB3881@solfire \
--to=meino.cramer@gmx.de \
--cc=gentoo-user@lists.gentoo.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