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 14:15:26 +0000 [thread overview]
Message-ID: <20050907141526.GA17122@vrfy.org> (raw)
In-Reply-To: <431EAE49.2000800@average.org>
On Wed, Sep 07, 2005 at 06:07:04PM +0400, Eugene Crosser wrote:
> Kay Sievers wrote:
>
> > No, 0.5.4 should work. Here is the HAL ChangeLog:
> > http://cvs.freedesktop.org/hal/hal/ChangeLog?rev=1.546&view=markup
> [...]
> > Looking at the HAL debug output may show something:
> > http://hal.freedesktop.org/wiki/Software_2fHalTraces
>
> Ok, at the very least, now I know where to look next. Thanks for that! :-)
Look with "lshal" if your cdrom is recognized by HAL. If not, but
udev has created a device node for it, post the debug HAL prints to the
console to:
hal@lists.freedesktop.org
I will, or somebody else will catch it there.
Good luck,
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 14:15 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
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 [this message]
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=20050907141526.GA17122@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 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.