there is a very good reasons you should not limit execution!
the GPL was written to make code free
limiting the execution the would prevent a user from using the code on a SCO system unless they modified it
not every user of GPL software knows how to do this as with most projects you only need to know how to type these two lines:./configure
make install
if this kind of attack was done to SCO on a large scale it would make it seem like it was ok to do so and therefore you would open the possibility for this to be done to any OS resulting in a really bug usability mess. If a end user can't get the sofware to run is it really free?
Slashdot Mirror
there is a very good reasons you should not limit execution! the GPL was written to make code free limiting the execution the would prevent a user from using the code on a SCO system unless they modified it not every user of GPL software knows how to do this as with most projects you only need to know how to type these two lines: ./configure
make install
if this kind of attack was done to SCO on a large scale it would make it seem like it was ok to do so and therefore you would open the possibility for this to be done to any OS resulting in a really bug usability mess. If a end user can't get the sofware to run is it really free?