From: Maksim Krasnyanskiy <maxk@qualcomm.com>
To: jreuter@suse.de (Joerg Reuter)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG?] vtund broken by tun driver changes in 2.4.6
Date: Fri, 13 Jul 2001 08:58:52 -0700 [thread overview]
Message-ID: <01071308585200.00792@btdemo1.qualcomm.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0107070058350.29490-100000@mackman.net.suse.lists.linux.kernel> <009601c106ff$a3cb2070$6baaa8c0@kevin.suse.lists.linux.kernel> <20010713133329.DDCEB19A57@lamarr.suse.de>
In-Reply-To: <20010713133329.DDCEB19A57@lamarr.suse.de>
> >Recompile your VTUND daemon with the new kernel headers (and also updated
> > to 2.5 vtund, it has some small patches) and you will be fine.
>
> Probably not:
>
> #define TUNSETNOCSUM _IOW('T', 200, int)
> #define TUNSETDEBUG _IOW('T', 201, int)
> #define TUNSETIFF _IOW('T', 202, int)
> #define TUNSETPERSIST _IOW('T', 203, int)
> #define TUNSETOWNER _IOW('T', 204, int)
>
> Which is (apart from some extensions) the same as it ever was. However adding a
Ioctls were defined _without_ IOW macros. And that was ugly. That's why I redifened them.
So, if you recompile everything will be fine.
> And BTW, you shouldn't include kernel headers from user space programs, should you.
That rule doesn't apply here.
Max
--
Maksim Krasnyanskiy
Senior Kernel Engineer
Qualcomm Incorporated
maxk@qualcomm.com
http://bluez.sf.net
http://vtun.sf.net
next prev parent reply other threads:[~2001-07-13 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0107070058350.29490-100000@mackman.net.suse.lists.linux.kernel>
[not found] ` <009601c106ff$a3cb2070$6baaa8c0@kevin.suse.lists.linux.kernel>
2001-07-13 13:33 ` [BUG?] vtund broken by tun driver changes in 2.4.6 Joerg Reuter
2001-07-13 15:58 ` Maksim Krasnyanskiy [this message]
2001-07-13 17:43 ` Joerg Reuter
2001-07-13 19:44 ` Maksim Krasnyanskiy
2001-07-07 8:02 Ryan Mack
2001-07-07 16:12 ` Kevin P. Fleming
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=01071308585200.00792@btdemo1.qualcomm.com \
--to=maxk@qualcomm.com \
--cc=jreuter@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox