From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eugene Crosser Date: Wed, 07 Sep 2005 09:09:29 +0000 Subject: Where are block@... database entries? Message-Id: <431EAE49.2000800@average.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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