Hi,
On Fri, Jun 03, 2011 at 08:11:11PM +0200, David Sommerseth wrote:
> Thanks! Yeah, this is just something I stumbled upon lately, but I saw
> that there are more stuff which can be cleaned up!
Indeed. I think this is actually something for the rest of the v2.3
preparation time... cleaning
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/06/11 19:22, Gert Doering wrote:
> Hi,
>
> On Fri, Jun 03, 2011 at 01:53:45PM +0200, David Sommerseth wrote:
>> Considering that the last Linux 2.2 update was released 25-Feb-2004
>> and the first Linux 2.4 release came 04-Jan-2001, there are no
Hi,
On Fri, Jun 03, 2011 at 01:53:45PM +0200, David Sommerseth wrote:
> Considering that the last Linux 2.2 update was released 25-Feb-2004
> and the first Linux 2.4 release came 04-Jan-2001, there are no
> reasonable reasons to help users to stay on outdated kernels.
> I consider this extra code
When configuring OpenVPN nowadays, the TUN/TAP configuration can
sometimes jump into the Linux 2.2 fallback code paths, which will
also fails. The reason it jumps into fallback mode is that the
tun/tap device already exists or that /dev/net/tun does not exist.
This can be very confusing, as /dev/t
