From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: Where are block@... database entries?
Date: Wed, 07 Sep 2005 09:11:35 +0000 [thread overview]
Message-ID: <20050907091135.GA5029@wonderland.linux.it> (raw)
In-Reply-To: <431EAE49.2000800@average.org>
On Sep 07, Eugene Crosser <crosser@average.org> wrote:
> Any advice/ideas how to make it work?
You need to upgrade HAL.
> 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.
--
ciao,
Marco
-------------------------------------------------------
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 9:11 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 [this message]
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=20050907091135.GA5029@wonderland.linux.it \
--to=md@linux.it \
--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.