>>
>> Originally, Unionfs was created using FiST, but since then it has been
>> heavily modified - so much so that the task of making it work on
>> Solarismight take more effort than reimplementing it (not
>> necessarily from
>> scratch.) Of course, since Unionfs is GPL, you are free to use the
>> source according to the rules stated in the license. This is
>> virtually a
>> non-issue if you are working on an academic or purely open source
>> project.
>
>Unfortunately the GPL will probably be a problem. The GPL is incompatible
>with the CDDL (the open source license that (open) solaris is under). I'm
>not a lawyer but I think that means that I can't use GPL kernel modules
>with Solaris. I guess it also means I can't look at the source if I want
>to create a CDDL'ed kernel module for Solaris.
License poking and circumvention is practiced everywhere. Though it's
mostly not distributed with the core kernel.
- NVIDIA container module ("source available but proprietary"),
loads some prop binary fluff
- ndiswrapper container module ("basically GPL"),
loads some prop windows binary fluff
So... just
- "gpl" container module (licensed CDDL)
loads some binary fluff of gpl'ed code
(Though, the Advanced User would just patch it right in without the
indirection through a module - after all, source is there, which is not
the case with the first two.)
Heh.
Jan Engelhardt
--
| Software Engineer and Linux/Unix Network Administrator
| Alphagate Systems, http://alphagate.hopto.org/
| jengelh's site, http://jengelh.hopto.org/
_______________________________________________
unionfs mailing list
[email protected]
http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
