Messages in this thread | | | Subject | RE: GPL and NON GPL version modules | Date | Mon, 15 May 2006 19:30:55 +0530 | From | "Nutan C." <> |
| |
As I said, I haven't started any development and wouldn't want to proceed unless and until I am sure of not violating GPL. I am working on a proprietary OS and I have a module which can talk to the OS through remote mechanism. However, since the interface is susceptible to be used by other OS as well, I wanted to make sure of it. I am not an expert in Linux. And, that's the reason; I am seeking your opinion, so that I don't falter at a later stage.
Regards, Nutan
-----Original Message----- From: Steven Rostedt [mailto:rostedt@goodmis.org] Sent: Monday, May 15, 2006 7:19 PM To: Nutan C. Cc: Jan Engelhardt; linux-kernel-Mailing-list; Fawad Lateef; jjoy@novell.com; Mukund JB.; gauravd.chd@gmail.com; bulb@ucw.cz; greg@kroah.com; Shakthi Kannan; Srinivas G. Subject: RE: GPL and NON GPL version modules
On Mon, 15 May 2006, Steven Rostedt wrote:
> > On Mon, 15 May 2006, Nutan C. wrote: > > > Ok, so now, I have a new doubt :-) Forgive me, if I am asking a lot, but > > I really don't want to move ahead with the development, until and unless > > I am sure I am not violating GPL. So, please bear with me. Here's the > > question: > > > > 1. I developed a code which interfaces well with a proprietary OS. Now, > > somebody else feels to use the same module in his Linux Kernel. So, he > > comes up with a patch, which interfaces and talks to my module with my > > interfaces and then makes a release with the patch. And, I would have no > > idea of my module being really compatible/used in Linux Kernel. One fine > > day, I would get a mail saying that I need to make my code open source. > > What would be my reply? > > > > Big fat answer is No! You are not distributing GPL code. Just because > someone made GPL code that interacts with your module, doesn't make you > responsible for it. (OK now for a IANAL disclaimer) I'm not a lawyer, but > I would bet my career on this one (at least in the US). > > You cant be held responsible for someone else's actions. > > So your reply is simple: > > I'm sorry, but I don't distribute GPL code, please see your distributor.
One more note. The person that distributed the GPL code with your module may be the one in the "grey area". But then again, how can your module be a derived work if the author didn't even intend on having it work with Linux?
-- Steve
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |