Language Selection

English French German Italian Portuguese Spanish

License issues roil Linux developer community

Filed under
Linux

Should the Linux kernel be licensed under the new version of the Gnu General Public License, or should it stick with the old version? The question has sparked a heated debate on the mailing list for Linux kernel developers. Hundreds of messages have zapped back and forth across the list debating the merits of the new open-source license, now in the final stages of preparation by the Free Software Foundation.

The copyright owner of the Linux kernel, Linus Torvalds, has stated that he would prefer to stick with the previous version of the kernel, Version 2. His chief lieutenants, Alan Cox and Andrew Morton, have sided with Torvalds. "I still think GPLv2 is simply the better license," Torvalds wrote.

Complicating the picture is that fact that Torvalds has said that if Sun Microsystems moves its open-source Solaris operating system — another version of Unix — he'd consider dual-licensing Linux so that the two projects could share code. "If we can avoid having two kernels with two different licenses and the friction that causes, I at least see the reason for GPLv3," he wrote.

Whether he could find agreement with the many coders who help write the Linux kernel is another matter.

More Here.




Law doesn't work like that

Contract law is fundamental to a functioning society and is one of the oldest parts of the law. However your analysis is overly simplistic because it doesn't acknowledge that as needs evolve, so must the law. If society decides, through the actions of the marketplace, that a new form of contract is needed, then the law will change to accommodate that and ensure that signatories uphold the contractual terms they have agreed to, so long as they are fair and reasonable.

In any event if you were right then all sorts of click-through licensing would be null and void. Yet the courts continue to uphold them.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Security Leftovers

10 hot Android smartphones that got price cuts recently

With numerous smartphone getting launched each month, brands always adjust prices to give slightly competitive edge to older smartphone models and also to clear inventories. Here are 10 smartphones that got price cuts recently. Read more

Debian and Ubuntu News

  • Debian Project News - July 29th, 2016
    Welcome to this year's third issue of DPN, the newsletter for the Debian community.
  • SteamOS Brewmaster 2.87 Released With NVIDIA Pascal Support
  • Snap interfaces for sandboxed applications
    Last week, we took a look at the initial release of the "portal" framework developed for Flatpak, the application-packaging format currently being developed in GNOME. For comparison, we will also explore the corresponding resource-control framework available in the Snap format developed in Ubuntu. The two packaging projects have broadly similar end goals, as many have observed, but they tend to vary quite a bit in the implementation details. Naturally, those differences are of particular importance to the intended audience: application developers. There is some common ground between the projects. Both use some combination of techniques (namespaces, control groups, seccomp filters, etc.) to restrict what a packaged application can do. Moreover, both implement a "deny by default" sandbox, then provide a supplemental means for applications to access certain useful system resources on a restricted or mediated basis. As we will see, there is also some overlap in what interfaces are offered, although the implementations differ. Snap has been available since 2014, so its sandboxing and resource-control implementations have already seen real-world usage. That said, the design of Snap originated in the Ubuntu Touch project aimed at smartphones, so some of its assumptions are undergoing revision as Snap comes to desktop systems. In the Snap framework, the interfaces that are defined to provide access to system resources are called, simply, "interfaces." As we will see, they cover similar territory to the recently unveiled "portals" for Flatpak, but there are some key distinctions. Two classes of Snap interfaces are defined: one for the standard resources expected to be of use to end-user applications, and one designed for use by system utilities. Snap packages using the standard interfaces can be installed with the snap command-line tool (which is the equivalent of apt for .deb packages). Packages using the advanced interfaces require a separate management tool.
  • Ubuntu 15.10 (Wily Werewolf) Reaches End Of Life Today (July 28)
  • Ubuntu MATE 16.10 Yakkety Yak Gets A Unity HUD-Like Searchable Menu
    MATE HUD, a Unity HUD-like tool that allows searching through an application's menu, was recently uploaded to the official Yakkety Yak repositories, and is available (but not enabled) by default in Ubuntu MATE 16.10.

Tablet review: BQ Aquaris M10 Ubuntu Edition

As employees have become more and more flexible in recent years thanks to the power and performance of mobile devices, the way we work has changed dramatically. We frequently chop and change between smartphones, tablets and laptops for different tasks, which has led to the growth of the hybrid market – devices such as Microsoft’s Surface Pro 3 and Apple’s iPad Pro – that provide the power and functionality of a laptop with the mobility and convenience of a tablet. Read more