From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Where are block@... database entries?
Date: Wed, 07 Sep 2005 11:53:23 +0000 [thread overview]
Message-ID: <20050907115323.GC14389@vrfy.org> (raw)
In-Reply-To: <431EAE49.2000800@average.org>
On Wed, Sep 07, 2005 at 11:11:35AM +0200, Marco d'Itri wrote:
> On Sep 07, Eugene Crosser <crosser@average.org> 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.
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.
We have complex interdependencies today and we will get even more of this
while moving forward providing a better hardware integration into the
whole system. We just started to move in that direction, so be prepared ... :)
Distros will need to have a well defined release cycle and package maintainers
which keep the package requirements up-to-date and make coordinated efforts
to synchronize the package versions, otherwise they may not be able to provide
a working setup.
HAL depends on a certain udev version and udev depends on a specific
kernel version. Upgrading only a subset of the packages may render
a part or the whole system unusable.
> > 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.)
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
next prev parent reply other threads:[~2005-09-07 11:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 9:09 Where are block@... database entries? Eugene Crosser
2005-09-07 9:11 ` Marco d'Itri
2005-09-07 11:53 ` Kay Sievers [this message]
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=20050907115323.GC14389@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).