From: Eugene Crosser <crosser@average.org>
To: linux-hotplug@vger.kernel.org
Subject: Where are block@... database entries?
Date: Wed, 07 Sep 2005 09:09:29 +0000 [thread overview]
Message-ID: <431EAE49.2000800@average.org> (raw)
I run slackware-current, which keeps pretty much up to date with udev
(currently comes with udev 0.64). Since some time ago, maybe in Spring,
rc.udev/udevstart stopped creating block@... entries in the
/dev/.udev... database. Now, only class@... files are created by udevstart.
As a result of that (I think), HAL does not recognize CDROM drive as
such, and do not poll it. Consequently, gnome-volume-manager do not
automount an inserved disk.
On a system where there are old /dev/.udev.tdb/block@* entries lingering
since April, automount works.
Any advice/ideas how to make it work?
And BTW, I *think* that "udev_log" in udev.conf (and maybe other
entries?) should be uppercased. This file is sourced into shell
scripts, and then the binaries such as udevstart check for enviroment
variable UDEV_LOG, in uppercase. Do I miss something?
Thanks
Eugene
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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 reply other threads:[~2005-09-07 9:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 9:09 Eugene Crosser [this message]
2005-09-07 9:11 ` Where are block@... database entries? Marco d'Itri
2005-09-07 11:53 ` Kay Sievers
2005-09-07 13:26 ` Eugene Crosser
2005-09-07 13:42 ` Kay Sievers
2005-09-07 14:07 ` Eugene Crosser
2005-09-07 14:15 ` Kay Sievers
2005-09-07 16:30 ` Marco d'Itri
2005-09-09 14:56 ` Eugene Crosser
2005-09-11 20:54 ` Seth W. Klein
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=431EAE49.2000800@average.org \
--to=crosser@average.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.