From: "Michael Yakorev" <michael@vinnitsa.com>
To: linux-hotplug@vger.kernel.org
Subject: How fix it?
Date: Fri, 11 Feb 2005 17:43:12 +0000 [thread overview]
Message-ID: <E1Czf3M-000FGo-00@aum.vinnitsa.com> (raw)
Feb 11 18:34:52 mha wait_for_sysfs[3870]: either wait_for_sysfs (udev 039)
needs an update to handle the device '/class/zaptel/zap
timer' properly (no device symlink) or the sysfs-support of your device's
driver needs to be fixed, please report to <linux-hotplug-
devel@lists.sourceforge.net>
Feb 11 18:34:52 mha wait_for_sysfs[3873]: either wait_for_sysfs (udev 039)
needs an update to handle the device '/class/zaptel/zap
channel' properly (no device symlink) or the sysfs-support of your device's
driver needs to be fixed, please report to <linux-hotplu
g-devel@lists.sourceforge.net>
Feb 11 18:34:52 mha wait_for_sysfs[3875]: either wait_for_sysfs (udev 039)
needs an update to handle the device '/class/zaptel/zap
pseudo' properly (no devicesymlink) or the sysfs-support of your device's
driver needs to be fixed, pleasereport to <linux-hotplug-d
evel@lists.sourceforge.net>
Feb 11 18:34:52 mha wait_for_sysfs[3876]: either wait_for_sysfs (udev 039)
needs an update to handle the device '/class/zaptel/zap
ctl' properly (no device symlink) or the sysfs-support of your device's
driver needs to be fixed, please report to <linux-hotplug-de
vel@lists.sourceforge.net>
How fix it?
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
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 reply other threads:[~2005-02-11 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 17:43 Michael Yakorev [this message]
2005-02-11 18:48 ` How fix it? Marco d'Itri
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=E1Czf3M-000FGo-00@aum.vinnitsa.com \
--to=michael@vinnitsa.com \
--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).