| |||||||||||
Does SCO own read-copy-update?Does SCO own read-copy-update?Posted Jun 13, 2003 16:23 UTC (Fri) by iabervon (subscriber, #722)In reply to: Does SCO own read-copy-update? by ssharkey Parent article: Does SCO own read-copy-update?
It's possible that the Monterey contract gives each participant the right to use the code developed in it, but not the right to transfer the license to this code to outsiders without the permission of the other participants. This would make sense for a partnership agreement between proprietary software vendors, as it would prohibit commoditization of the results if one of the participants lost interest while letting each of the participants get their money's worth.
(Log in to post comments)
Does SCO own read-copy-update? Posted Jun 13, 2003 16:50 UTC (Fri) by emk (subscriber, #1128) [Link] It's possible that the Monterey contract gives each participant the right to use the code developed in it, but not the right to transfer the license to this code to outsiders without the permission of the other participants. Possibly. But I get the impression that the consortium members frequently donated their own, in-house code to Monterey. And if some code was written for Dynix/ptx (on behalf of Sequent), it seems likely the Sequent would retain rights to use the code independently. Would IBM or Sequent really sign a contract which said, "SCO can veto how you use code that you wrote?" Maybe they would, but I'd expect IBM's lawyers to be a bit more cautious than that. The RCU code appears to have been written by one of the original RCU researchers for use in Dynix. IBM apparently now owns Dynix, and the RCU patent.
|
|||||||||||