Open Source Exposure

[maoz]

Hi
I don't know if it's the right forum (If not get you send me a link to the relevant forum)

I have question regarding code exposure in Linux.

I work in a company which is currently developing a product based on the Linux OS.

We are developing both driver and user space applications.

Do we need to expose the following components:
1. Kernel Driver
2. User Space Application – (Communicates With The Driver)


What steps should I take in order not the expose the user space application? (If it is unavoidable, I am less concerned with exposing the driver code.)

Thank you

[Rubberman]

Presuming you are not incorporating GPL'd components that are covered under GPLv2 or GPLv3 (other than LGPL'd components) in your application code, then you should not have to "expose" anything. In any case, you need to understand the license of the various things you are using in your code, such as libraries. Using the standard gnu libraries, you have no obligation to expose your source code to anyone. If you incorporate other libraries, then you might, depending upon their license. If you modify any GPL'd code, then you need to make that code available, but not your own software outside of that component.

If you need better, or more answers then you should contact the Free Software Foundation.