Slashdot Mirror
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?
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?
This is just going to stir up the hornet's nest and make Linux and OSS look bad to the outside world. How's about we all try and be nice, and show these shills that we can't be manipulated?
What is your motivation for closed source? And why do you feel you need to use all the benefits of open source yet keep your code under lock and key? Will you only use it yourself in a locked room and never allow it to be run by anyone else?
Perhaps you should look into DRM restrictions and lawyers. Lots of lawyers.
Only alchemists and very poor cooks feel the need to have secret recipes. Look how little mark they leave on the world.
You don't get basic stuff, consult your concerns with lawyer - that would be safer than asking on Slashdot but if you still wish to know my answers:
:))) BTW obfuscating has nothing to do with encoding. You don't get even basic stuff right.
> 1. Can I do it with Linux today (GPL2) and tomorrow (GPL3)?
Do what? Write closed source applications for Linux? No problem.
> 2. Can I statically link the code with Linux libraries?
WTF are Linux libraries? Linux is a kernel. Get more specific.
> 3. Can I obfuscate my code (e.g. encode it)?
Why not? And what for? You think it will be safer then?
> 4. Could I be forced to publish this code by some 3-d party?
Which code?
> 5. Am I correct that programming in and selling BSD-based
> boxes won't raise any of the above problems?
What are BSD boxes?
Ah, another AC with a well articulated argument against something said in the Parent. It is always a pleasure to meet such tolerance and understanding in a forum that is, quite honestly, not limited to F/OSS users. /sarcasm
Have a look at soylentnews.org for a different view
Yeah, so you want to build this embedded widget to sell to my company. Yet you are a one-man show intent on keeping all the secrets of how it works to yourself. What happens when it breaks down, or I just need it modified to fit some new requirement, and YOU *LONE* *RANGER* ARE NOT AROUND? I can't see any sane businessmen buying your product.