Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am developing a GUI program, and I use as OS the linux kernel (it is for an embedded device). I am wondering if I have to make available the GNU license from the GUI itself?
I have a device with embedded linux and the GPL is at the back of the manual
does it say anything about which part is covered by GPL? common sense says Linux GPL does not concerns programs running under it and standard c libraries (c++ runtime, too) is LGPL. however in common law anything is possible
I am developing a GUI program, and I use as OS the linux kernel (it is for an embedded device). I am wondering if I have to make available the GNU license from the GUI itself?
I am a bit confused with the license stuff ...
Thanks,
Guillaume
I'm no lawyer, and I'm not familiar with your software, but I don't think you would have to display the GPLv2 license of the kernel in your GUI, as long as you haven't modified the kernel code. Everybody knows where to get the source of the Linux kernel. It'd be like saying that all web pages hosted on Linux servers should have a link to the GPLv2 text.
I would think, though, that somewhere you would want to make it clear that your device is running Linux. Say a note on your website.
If you end up running any GPLv3 software in the future, you should be aware of the "Tivoization" aspect of the newer license, which could actually affect how your device must be designed:
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
...
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
...
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
Your program is yours. The fact that it runs on Linux is irrelevant, unless you're modifying other Linux code as part of the installation of your program. If you are, then those pieces that you modified will have to be released under the GPL. Your program doesn't. However, you can't just make some changes to GPLed code and call it yours. No matter what changes you make to someone else's code, it remains their code, and not yours.
There is nothing special about the GPL. In spite of Stallman's protestations to the contrary, the GPL is just a license to use copyrighted material. A copyright gives authors specific legal rights. They may choose to modify those rights, and a common way to do that is to license them under the GPL. As stated above, if you don't GPL your code, then you don't have to make the source available, and you can charge what the market will bear on it. If you aren't installing Linux on your customer's machines, then you don't have to be bothered with the GPL in any aspect.
NOTE: I am not a lawyer, nor am I employed in any aspect or function in the legal field. This post is just an observation based on what I've seen over the years. If you aren't comfortable with any legal issue, you should always see a lawyer for clarification.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.