4 ms·

What does it mean to be "in Linus' tree" if it's already on Linux and everywhere else? Like it will be built in somehow?

tanderson92 7y ago
Not all linux kernel modules are in the main sources. Many projects begin outside the main tree and are pulled in later after they have proven themselves and have matured, responded to criticism, etc.
- teruakohatu 7y ago
  True but now they have to put some small effort into excluding it, rather than a reasonable amount of effort to include it.
MBCook 7y ago
It will now end up in all Linux distros by default. Instead of having to chase it down and apply a bunch of patches it’s now just a single config option away.
therealmarv 7y ago
Right now Wireguard is using DKMS which is like a external Kernel module which needs to be rebuild on every Kernel update. When WG is already inside the Kernel no dynamic created DKMS are needed anymore.
oarsinsync 7y ago
Right now, it is not part of the Linux kernel. It is just some random external software that you have you download and compile yourself against the source headers of the kernel you're currently running. It got merged into the net-next tree, which meant it has been approved by the maintainer of the Linux kernel net branch to be included into the kernel. Linus has now pulled it from net-next into his own tree, which means it'll be included in the next release of the Linux kernel. As far as that means as an end user, it means that you no longer need to recompile your wireguard module every time there's a kernel update, as now it will be handled by your distro. That said, given that Wireguard is packaged nicely already for most distros, the end effect for you is really pretty little, as you're probably unaware of all of this complexity that's going on right now, as it mostly just works.
- mekster 7y ago
  > As far as that means as an end user, it means that you no longer need to recompile your wireguard module every time there's a kernel update, as now it will be handled by your distro. That's not the important point. The point being, when merged as part of the kernel officially, you know it will get more support and eyes for stability and development power as the kernel wouldn't want to ship anything that's at some unstable state. So you can expect long term usage and maybe RedHat might pick it up as its official VPN solution instead of libreswan some day.
  - ryanlol 7y ago
    >you know it will get more support and eyes for stability and development power as the kernel wouldn't want to ship anything that's at some unstable state. This is a rather idealistic view on kernel development. But it is true that when wireguard is “ready” this could very well result in a bit more support as larger orgs will be more willing to start using wireguard.

tanderson92 7y ago

Not all linux kernel modules are in the main sources. Many projects begin outside the main tree and are pulled in later after they have proven themselves and have matured, responded to criticism, etc.

teruakohatu 7y ago
True but now they have to put some small effort into excluding it, rather than a reasonable amount of effort to include it.

MBCook 7y ago

It will now end up in all Linux distros by default. Instead of having to chase it down and apply a bunch of patches it’s now just a single config option away.

therealmarv 7y ago

Right now Wireguard is using DKMS which is like a external Kernel module which needs to be rebuild on every Kernel update. When WG is already inside the Kernel no dynamic created DKMS are needed anymore.

oarsinsync 7y ago

Right now, it is not part of the Linux kernel. It is just some random external software that you have you download and compile yourself against the source headers of the kernel you're currently running. It got merged into the net-next tree, which meant it has been approved by the maintainer of the Linux kernel net branch to be included into the kernel. Linus has now pulled it from net-next into his own tree, which means it'll be included in the next release of the Linux kernel. As far as that means as an end user, it means that you no longer need to recompile your wireguard module every time there's a kernel update, as now it will be handled by your distro. That said, given that Wireguard is packaged nicely already for most distros, the end effect for you is really pretty little, as you're probably unaware of all of this complexity that's going on right now, as it mostly just works.

mekster 7y ago
> As far as that means as an end user, it means that you no longer need to recompile your wireguard module every time there's a kernel update, as now it will be handled by your distro. That's not the important point. The point being, when merged as part of the kernel officially, you know it will get more support and eyes for stability and development power as the kernel wouldn't want to ship anything that's at some unstable state. So you can expect long term usage and maybe RedHat might pick it up as its official VPN solution instead of libreswan some day.
- ryanlol 7y ago
  >you know it will get more support and eyes for stability and development power as the kernel wouldn't want to ship anything that's at some unstable state. This is a rather idealistic view on kernel development. But it is true that when wireguard is “ready” this could very well result in a bit more support as larger orgs will be more willing to start using wireguard.