Re: Where are block@... database entries?

[Kay Sievers <kay.sievers@vrfy.org>]

On Wed, Sep 07, 2005 at 05:26:10PM +0400, Eugene Crosser wrote:
> Kay Sievers wrote:
> 
> >>>Any advice/ideas how to make it work?
> >>
> >>You need to upgrade HAL.
> > 
> > Yes, see the RELEASE-NOTES for 061:
> >   http://www.kernel.org/git/gitweb.cgi?p=linux/hotplug/udev.git;a=blob;hb=HEAD;f=RELEASE-NOTES
> > 
> > At the same time HAL was changed and released to work with the new udev.
> 
> There is no indication in the release notes on which version of HAL is
> appropriate.  I am running 0.5.4, and it does not work, do I need to
> upgrade?

No, 0.5.4 should work. Here is the HAL ChangeLog:
  http://cvs.freedesktop.org/hal/hal/ChangeLog?rev=1.546&view=markup

> > Note:
> > Randomly upgrading critical parts of the system, without resolving all
> > package requirements for the  kernel, udev, hal, hal-susbsytem-managers
> > like NetworkManager, dbus, desktop-integration like gnome-volume-manager,
> > will probably break your setup.
> 
> It's hard to break what does not work anyway...  The problem is that
> udev is a part of slackware distribution, but hal is not, and it has to
> come with gnome (FRG in my case).  Now I am trying to figure a working
> setup, to be able to advice FRG folks after that.  Existing documents on
> the web are hopelessly out of date, so please bear with me.

Looking at the HAL debug output may show something:
  http://hal.freedesktop.org/wiki/Software_2fHalTraces

> >>>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?
> >>
> >>Yes. The file is also a real configuration file of the programs.
> > 
> > Right! All the binary udev tools parse this file. This is the primary
> > use of this file, while sourcing it in with a shell works too.
> > (UDEV_LOG is exported from the udev tools after reading it from the
> > config file, but with the log priority in its numerial representation
> > not the text used in the config.)
> 
> I just noticed that when I change udev_log in udev.conf, udevstart does
> *not* become more verbose as I expected.  When I set UDEV_LOG
> environment variable and then run udevstart, it *does* become verbose.
> I figured that this looks like a bug...

Yes, it's a special case for udevstart. Enabling debugging output in
udevstart may cause udevstart to take several minutes to finish on
systems with "sync" syslog configurations. That may lead to a system
unable to bootup correctly. udevstart ignores the setting from the config
file, you can only debug it on the commandline. All other udev tools don't
override the setting.

See line 351:
  http://www.kernel.org/git/?p=linux/hotplug/udev.git;a=blob;hÎ96f38879186c81d185f520393a2b18c4428166;hb=HEAD;f=udevstart.c#l351

Kay


-------------------------------------------------------
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