From: Andrew Zaharov <zav@unitel.su>
To: linux-hotplug@vger.kernel.org
Subject: openvpn wrongs
Date: Tue, 21 Feb 2006 12:07:16 +0000 [thread overview]
Message-ID: <1140523636.2861.5.camel@andy.unitel> (raw)
Feb 21 11:06:23 comp wait_for_sysfs[2098]: either wait_for_sysfs (udev
039) needs an update to handle the device '/class/net/tun0' 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>
FC3 kernel-2.6.9-1.667
openvpn-2.0.2-1.0.rh9.rf
udev-039-8.FC3
Thanks
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
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:[~2006-02-21 12:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 12:07 Andrew Zaharov [this message]
2006-02-21 12:10 ` openvpn wrongs 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=1140523636.2861.5.camel@andy.unitel \
--to=zav@unitel.su \
--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.