This may be a well-worn topic here, and if so I apologize... What about GPL-licensed code using proprietary (closed) instructions and hipervisor features (DIAG, etc)? Aren't micro/millicode and zVM hipervisor vectors "the new OCO" with respect to Linux and Solaris on z?
I can guess what RMS would say, but IMO kernel modules that use closed instructions should be considered "non-free". This would have nasty implications. Kirk Wolf Dovetailed Technologies http://dovetail.com On Tue, Mar 31, 2009 at 9:24 PM, John Summerfield < [email protected]> wrote: > > However, sometimes licence conflicts determine what can be done. > GPL-licence code cannot be mixed with code released under other licences > - any that keep source code secret for starters. It is not open to > Oracle to incorporate code from bash into Oracle. It's not permissible > to alter the Linux kernel and release the result without source code, > and companies have been sued sucessfully for this violation. Ask Dlink. > > Its also possible for a licence to prohibit release of source code. MS > owns large parts of OS/2. > > -- > > Cheers > John > > -- spambait > [email protected] [email protected] > -- Advice > http://webfoot.com/advice/email.top.php > http://www.catb.org/~esr/faqs/smart-questions.html<http://www.catb.org/%7Eesr/faqs/smart-questions.html> > http://support.microsoft.com/kb/555375 > > You cannot reply off-list:-) > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
