From: Mikhail Kolesnik <mike@openbunker.org>
To: linux-hotplug@vger.kernel.org
Subject: Some rules do not work in udev 131 and 132
Date: Wed, 12 Nov 2008 19:00:52 +0000 [thread overview]
Message-ID: <20081112210052.6e7d8bb8@amilo> (raw)
Hello.
udev was built from sources with no patching or very special rulesets
installed. After a simple update from 130 to 131 some of my custom rules
stopped working. And I can't find information about syntax change in
git log.
In the example below the first rule creates a symlink, but the second
one creates none. It works with 130 but does not work on 131 and 132.
The same results for another device (and partitions are there
untouched).
BUS="usb", ATTRS{serial}="A500000000025423", KERNEL="sd?", NAME="%k", SYMLINK+="usbflash", GROUP="cdrom"
BUS="usb", ATTRS{serial}="A500000000025423", KERNEL="sd?[1-3]", NAME="%k", SYMLINK+="usbflash%n", GROUP="cdrom"
Target: i686-pc-linux-gnu
Configured with: ../gcc-4.2.4/configure --prefix=/usr --libexecdir=/usr/lib --enable-languages=c,c++,objc --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-shared --disable-nls --with-x=no
Thread model: posix
gcc version 4.2.4 (CRUX)
libtool 2.2.6
Linux amilo.home 2.6.26.1-mk38 #1 Sun Aug 3 17:08:19 EEST 2008 i686
Intel(R) Pentium(R) M processor 1.73GHz GenuineIntel GNU/Linux
next reply other threads:[~2008-11-12 19:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 19:00 Mikhail Kolesnik [this message]
2008-11-12 20:31 ` Some rules do not work in udev 131 and 132 Kay Sievers
2008-11-12 22:37 ` Mikhail Kolesnik
2008-11-12 22:55 ` Kay Sievers
2008-11-13 11:50 ` Mikhail Kolesnik
2008-11-13 17:13 ` Kay Sievers
2008-11-14 16:38 ` Mikhail Kolesnik
2008-11-14 17:42 ` 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=20081112210052.6e7d8bb8@amilo \
--to=mike@openbunker.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 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.