lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070216154031.GR7584@csclub.uwaterloo.ca>
Date:	Fri, 16 Feb 2007 10:40:31 -0500
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	v j <vj.linux@...il.com>
Cc:	Trent Waddington <trent.waddington@...il.com>,
	David Lang <david.lang@...italinsight.com>,
	Scott Preece <sepreece@...il.com>,
	Miguel Ojeda <maxextreme@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: GPL vs non-GPL device drivers

On Thu, Feb 15, 2007 at 10:25:12PM -0800, v j wrote:
> Please point me to where it says I cannot load proprietary modules in
> the Kernel.

Some people consider modules derivative works, since they link with
pieces of the kernel.  Distributing derivative works are considered
distributing the original work, which means the GPL applies to the
result.

> I know his opinion. I don't debate his opinion. It is his code. I
> choose not to use his code because of the license issue.
> 
> No, just that the trend is disturbing. If enough Kernel Developers
> choose to write their Software in a way that prevents others from
> using it freely, then that is troubling. Especially when these Kernel
> Developers are substituting existing interfaces in the Kernel with
> ones that are NEW and require specific licenses.

devfs had issues.  Someone (Greg) provided something better.  devfs went
away when nothing in the kernel needed it anymore.  That something
outside the kernel was using devfs, well who cares.  That is the outside
code's problem if they don't keep up.  If they happen to have any issues
with the replacement system, then that too is their problem and only
their problem.

--
Len Sorensen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ