All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nigel Kukard <nkukard@lbsd.net>
To: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.3] Sysfs breakage - tun.ko
Date: Tue, 2 Mar 2004 08:02:51 +0200	[thread overview]
Message-ID: <20040302060251.GG21950@lbsd.net> (raw)
In-Reply-To: <40439B03.4000505@backtobasicsmgmt.com>

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]


Nothing said solves the problem, the problem has got nothing to do with
devfs (only for compat reasons), the problem is that "net/tun" breaks
sysfs.
                                                                                                                                                                      
-Nigel


On Mon, Mar 01, 2004 at 01:20:19PM -0700, Kevin P. Fleming wrote:
> Nigel Kukard wrote:
> 
> >--- drivers/net/tun.c.old   2004-02-27 18:18:55.000000000 +0200
> >+++ drivers/net/tun.c       2004-02-27 18:19:02.000000000 +0200
> >@@ -605,7 +605,7 @@
> >
> > static struct miscdevice tun_miscdev = {
> >        .minor = TUN_MINOR,
> >-       .name = "net/tun",
> >+       .name = "tun",
> >        .fops = &tun_fops
> > };
> 
> This changed back and forth since the tun driver was added to the 
> kernel; making this change will cause the devfs path to the tun node to 
> change, and userspace applications expect it to be at /dev/misc/net/tun, 
> whether that's right or wrong.


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-03-02  6:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-01 19:48 [2.6.3] Sysfs breakage - tun.ko Nigel Kukard
2004-03-01 20:20 ` Kevin P. Fleming
2004-03-01 20:24   ` Nigel Kukard
2004-03-01 20:47   ` Chris Wright
2004-03-01 21:08     ` Kevin P. Fleming
2004-03-02  0:32   ` H. Peter Anvin
2004-03-02  6:02   ` Nigel Kukard [this message]
2004-03-03  2:28     ` Chris Wright
2004-03-04  5:25       ` Nigel Kukard

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=20040302060251.GG21950@lbsd.net \
    --to=nkukard@lbsd.net \
    --cc=kpfleming@backtobasicsmgmt.com \
    --cc=linux-kernel@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.