From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Problem with vpnc-0.3.2-2.1
Date: Wed, 23 Mar 2005 14:28:23 +0000 [thread overview]
Message-ID: <1111588103.4959.11.camel@localhost.localdomain> (raw)
In-Reply-To: <D1D49B61B5B64B4A8FB647B97BEC4ED901B71DDD@DCEVS1.tekelec.com>
On Wed, 2005-03-23 at 08:08 -0600, Hammond, Jeffrey wrote:
> I'm seeing the following log messages:
>
> Mar 16 14:45:43 kernel: Universal TUN/TAP device driver 1.5
> (C)1999-2002 Maxim Krasnyansky
>
> Mar 16 14:45:43 dhclient: tun0: unknown hardware address type 65534
>
>
>
> Mar 16 14:45:48 wait_for_sysfs[3851]: 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
>
>
> I'm running Fedora Core3 kernel 2.6.9.1.667. I'm assuming I've got
> something either not or incorrectly configured.
Install the available udev update package and this message will go away.
Kay
-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_idh82&alloc_id\x15148&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
prev parent reply other threads:[~2005-03-23 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 14:08 Problem with vpnc-0.3.2-2.1 Hammond, Jeffrey
2005-03-23 14:28 ` Kay Sievers [this message]
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=1111588103.4959.11.camel@localhost.localdomain \
--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