3 ms·
Would the CDDL matter for a python implementation that will never become part of the kernel?
by newnewpdro 7y ago
Would the CDDL matter for a python implementation that will never become part of the kernel?
- dr0verride 7y agoIt's clear to me that the solution is to integrate python into the kernel.
- yjftsjthsd-h 7y agoI assume you mean this as a joke, but I would point out that at least one of the BSD family has gone and baked lua into their kernel. Granted, lua is rather meant for that kind of thing and python isn't, but it is entertaining to point out an interpreted language that has been stuck into a unix kernel:)
- riffraff 7y agothere was lua in linux too, with lunatik https://github.com/lunatik-ng/lunatik-ng https://github.com/lunatik-ng/lunatik-ng
- CaliforniaKarl 7y agoYou'd want a reverse-engineering lawyer, so be certain. But my (IANAL) guess is: If this is a proper reverse-engineered implementation, you could then convert _this_ implementation to C, and contribute _that_ into the kernel. Except, it seems this is BSD-licensed, so I'm not sure how that would work in the kernel (which is GPLv2).
- lunixbochs 7y agoBSD is a subset of GPL's restrictions, so you can include BSD-licensed code in a GPL work.
- loeg 7y agoSubset isn't quite accurate, but "GPL compatible" might be a good way to describe it.
- deleted 7y ago[deleted]
- loeg 7y agoBSDL code is fine in the GPLv2 kernel. E.g., most of the DRM drivers are dual BSD-GPL licensed.