From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Fwd: blkid descends into /dev/.udev/... and stucks.
Date: Thu, 26 Jan 2006 15:31:02 +0000 [thread overview]
Message-ID: <20060126153102.GA20616@vrfy.org> (raw)
In-Reply-To: <cfb54190601260717i39e89f58n973886ea65194091@mail.gmail.com>
On Thu, Jan 26, 2006 at 05:17:07PM +0200, Hai Zaar wrote:
> Message below is directly related to hotplug, but I've encountered the
> described problem while playing with 2.6.15 + new udev - and it took
> me decent amount of hours to find the problem.
Scanning /dev is evil and blkid is usually not used in udev context, cause
udev supplies the vol_id program. (On SUSE we even patch mount(8) to link
against the udev provided libvolume_id instead of libblkid.)
Use vol_id, it fits better on a udev system. Note, you may not need anything
custom here, if you use the persistent symlinks in /dev/disk, which almost
all distros have these days.
And please send the blkid patch to the e2fsprogs maintainer, as it would be good
to have this fixed soon. But I think it's better to ignore _any_ dot file in /dev
instead of the udev directory only.
Thanks,
Kay
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
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:[~2006-01-26 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 15:17 Fwd: blkid descends into /dev/.udev/... and stucks Hai Zaar
2006-01-26 15:31 ` Kay Sievers [this message]
2006-01-26 16:10 ` Hai Zaar
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=20060126153102.GA20616@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).