| 1 |
On 2013-08-28 7:12 AM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 2 |
> Whether the code is compile in or a module makes no difference wrt |
| 3 |
> licenses as far as I know. |
| 4 |
> |
| 5 |
> There's no limitation on*running* the code, you can fetch and patch and |
| 6 |
> edit and compile and run all you want and have it on as many of your (or |
| 7 |
> the company's) machines as you want - neither license interferes with |
| 8 |
> your right to do that. |
| 9 |
> |
| 10 |
> You may not redistribute the code though. |
| 11 |
|
| 12 |
So, can you answer me this... |
| 13 |
|
| 14 |
Why would there be a problem if someone decided to create a 3rd party |
| 15 |
overlay *not* part of the official gentoo portage tree that contained |
| 16 |
*only* the zfs stuff, and when this overlay was installed combined with |
| 17 |
a zfs keyword for the kernel, portage would then pull in the required |
| 18 |
files, and automagically build a kernel with an up to date version of |
| 19 |
zfs properly and fully integrated? |
| 20 |
|
| 21 |
Would this not work, *and* have no problems with licensing? |
Archives