Re: [BUG?] vtund broken by tun driver changes in 2.4.6
Maksim Krasnyanskiy (maxk@qualcomm.com)
Fri, 13 Jul 2001 08:58:52 -0700
> >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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/