Closed Source On Linux and BSD?

An anonymous reader writes "I want to start (very small) software/hardware business. The code in question will be closed source. I won't modify or use any GPL code or any 3rd-party sources. It will be my own handwritten C/C++ code from start to finish. I am planning to sell embedded-like boxes with an OS (Linux or BSD) and this code. I am more familiar with Linux but I am scared a little bit of Linux licensing, and also of Linux fanboy-ism: I personally got a 'go to hell with your @#$ closed code' slur on Slashdot. I am not a GPL guru and not a software freedom fighter. I just want to do my job and make a living." Read on for this reader's five particular questions.
My questions:

1. Can I do it with Linux today (GPL2) and tomorrow (GPL3)?

2. Can I statically link the code with Linux libraries? (My own experience shows that dynamic linking is too much to bear.)

3. Can I obfuscate my code (e.g. encode it)?

4. Could I be forced to publish this code by some 3-d party?

5. Am I correct that programming in and selling BSD-based boxes won't raise any of the above problems?

Comments

Answers

[cerberusss]

1. Can I do it with Linux today (GPL2) and tomorrow (GPL3)?

If you make modifications to GPL software (for example the kernel) with both GPL2 and 3, you must also make the source available. If you create your own software, that's not necessary. With GPL3, you're forbidden to create hardware obstacles for users to run modified GPL code. Search for 'tivo gpl 3' for an explanation.

2. Can I statically link the code with Linux libraries? (My own experience shows that dynamic linking is too much to bear.)

If you want to link without having to distribute your source code: only if the libraries are not GPL. But GPL, BSD licenses do the trick.

3. Can I obfuscate my code (e.g. encode it)?

That's a stupid way to try to work around the GPL. Don't do it. Just don't link in GPL code. Or modify it and distribute it without the source.

4. Could I be forced to publish this code by some 3-d party?

Not if you stick to the rules. I.e. don't modify GPL code and distribute it. Or link to it.

5. Am I correct that programming in and selling BSD-based boxes won't raise any of the above problems?

Well, if you stick to BSD-licensed software, of course. However, the Linux community is much larger and much more software comes out. Weigh the advantages and disadvantages yourself.

Don't think you'll have a problem.

[MadTinfoilHatter]

1. Can I do it with Linux today (GPL2) and tomorrow (GPL3)? Yes.

2. Can I statically link the code with Linux libraries? (My own experience shows that dynamic linking is too much to bear.) I think you could do it with BSD & LGPL:ed code, but not GPL:ed code. Not 100% sure on this one - someone please correct me if I'm wrong.

3. Can I obfuscate my code (e.g. encode it)? Sure, but why would you want to, if it's going to be closed source anyway?

4. Could I be forced to publish this code by some 3-d party? Only if you used other people's code in a manner that violates the licence. E.g. you used GPL:ed code in your software. Linux is however designed in such a fashion that it's quite possible to run both free and proprietary software on it side by side. (Proprietary kernel drivers are a different matter, but that's not what you're doing, right?)

5. Am I correct that programming in and selling BSD-based boxes won't raise any of the above problems? I don't think you'll run into problems in Linux either - but if you thought that the Linux-free-software-fanboys are bad, wait 'till you meet the BSD-ones... ;-)