From: Jeff Dike <jdike@karaya.com>
To: Marek Zawadzki <mzawadzk@cs.stevens-tech.edu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: TUN/TAP driver doesn't work.
Date: Tue, 12 Feb 2002 10:49:37 -0500 [thread overview]
Message-ID: <200202121549.g1CFnb004555@karaya.com> (raw)
In-Reply-To: Your message of "Sun, 10 Feb 2002 22:17:19 EST." <Pine.NEB.4.33.0202102204200.21611-100000@courage.cs.stevens-tech.edu>
mzawadzk@cs.stevens-tech.edu said:
> Did they change values of #defines for TUN/TAP ioctls' numbers, or
> what?
Yup, they sure did.
> If so, that's quite bad in my opinion (what if somebody had
> binary-only version of his client?).
Yup, it sure is. It screwed UML over too.
BTW, if you (or anyone else) still needs to look at working TUN/TAP code,
UML has had a TUN/TAP network backend for a while. See
arch/um/drivers/tuntap*.
I've also got persistent TUN/TAP support mostly working in my private pool,
it will appear in a patch shortly.
Jeff
prev parent reply other threads:[~2002-02-12 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-10 21:44 Marek Zawadzki
2002-02-11 0:13 ` J Sloan
2002-02-11 3:17 ` Marek Zawadzki
2002-02-12 15:49 ` Jeff Dike [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=200202121549.g1CFnb004555@karaya.com \
--to=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mzawadzk@cs.stevens-tech.edu \
/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
all inboxes | Powered by JetHome®