From: Mikhail Kolesnik <mike@openbunker.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Some rules do not work in udev 131 and 132
Date: Fri, 14 Nov 2008 16:38:52 +0000 [thread overview]
Message-ID: <20081114183852.465ccb12@amilo> (raw)
In-Reply-To: <20081112210052.6e7d8bb8@amilo>
Hello, Kay.
On Fri, 14 Nov 2008 14:04:28 +0100
"Kay Sievers" <kay.sievers@vrfy.org> wrote:
> [...]
> > I've upgraded to 2.6.27.5 and rebuild udev 131 to be sure. Same
> > symptoms.
> >
> > It just tries to readlink /sys/block/sdc entries. May be new udev
> > expects some more in kernel options enabled? The trace and kernel
> > config files are attached.
>
> We do not read that attribute at all. You run sysfs in the deprecated
> layout. Any reason for that? Only old distros with new kernels would
> need that.
I guess I've considered it a safe choice during a kernel upgrade at
some point.
> The current layout, which all more recent distros use is
> CONFIG_SYSFS_DEPRECATED=n. With the current layout you also get
> /sys/class/block/, which is much easier to handle for udev. You should
> see a warning printed from udev to the kernel log (dmesg) when udev
> starts up.
I was able to unset CONFIG_SYSFS_DEPRECATED_V2 from menuconfig, which
disabled invisible CONFIG_SYSFS_DEPRECATED too. Now recent udev
versions work with my rulesets. Thanks a lot.
I'm Cc'ing the linux-hotplug to be sure anyone with such a trouble can
find the answer.
next prev parent reply other threads:[~2008-11-14 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 19:00 Some rules do not work in udev 131 and 132 Mikhail Kolesnik
2008-11-12 20:31 ` 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 [this message]
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=20081114183852.465ccb12@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 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).