Re: License Question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zbigniew Szalbot wrote: > Hello, > > 2008/1/21, Aryeh M. Friedman <[EMAIL PROTECTED]>: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> >> Free BSD wrote: >>> Hello, i have a question about licensing FreeBSD: i would be >>> like install freebsd in corporation on workstation (don't >>> servers). Its free ? Or FreeBSD free for individual using ? >> Yes > > Funny but this answer may not be helpful :) "Yes" meaning "free for > corporate environment" or "free for individuals"? > The (Free)BSD license specifically allows you to use FreeBSD how ever you see fit along you don't impede someone else's right to do the same. Since FreeBSD it is self is a free download you never have to pay for it i.e. it is 100% "free beer"... ironically there is nothing that prevents you from repacking and selling the repacking... if you really want to know the good, bad and ugly of the BSD license vs. other ones read the recent thread "freebsd problems as I see them" in -current (and the continuation of the licensing sub-thread in my private inbx if you really want to)... please note I think the BSD license under rates the true value of the work being done but since it is clear from the above sub-thread that I am in the minority I will not debate it. - -- Aryeh M. Friedman FloSoft Systems, Java Tool Developers Developer, not business, friendly http://www.flosoft-systems.com "Free software != Free beer" Blog: http://www.flosoft-systems.com/flosoft_systems_community/blogs/aryeh/index.php -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHlQ34Qi2hk2LEXBARApIZAJ96bGRI0HzvFtD9Ds+a6KS68SZFsQCfUflM 6/3ZriQHnJFMnmNXtQiWVis= =6Dx+ -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: License Question
On Mon, Jan 21, 2008 at 11:09:07PM +0300, Free BSD wrote: > Hello, i have a question about licensing FreeBSD: i would be like > install freebsd in corporation on workstation (don't servers). Its > free ? Or FreeBSD free for individual using ? http://www.freebsd.org/copyright/freebsd-license.html doesn't distinguish between individuals, corporations, hobby use, etc. -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: License Question
Hello, 2008/1/21, Aryeh M. Friedman <[EMAIL PROTECTED]>: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Free BSD wrote: > > Hello, i have a question about licensing FreeBSD: i would be like > > install freebsd in corporation on workstation (don't servers). Its > > free ? Or FreeBSD free for individual using ? > > Yes Funny but this answer may not be helpful :) "Yes" meaning "free for corporate environment" or "free for individuals"? Kind regards, Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: License Question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Free BSD wrote: > Hello, i have a question about licensing FreeBSD: i would be like > install freebsd in corporation on workstation (don't servers). Its > free ? Or FreeBSD free for individual using ? Yes -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHlQr1Qi2hk2LEXBARAv2zAJ4t+ELEXWBG96O1A+3MnUUF3SGmLgCggDEC Yarj3kpD8R1qweFtiFdhrIQ= =Gv5K -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: License Question
Manolo Fredricks wrote: [ ... ] If I make modifications to FreeBSD and then distribute it (the modified FreeBSD) to others: Note that the details depend upon what part of FreeBSD you change, but the two general licenses are /COPYRIGHT (aka the "new" or "modified" BSD license) and the GPL (/usr/src/gnu/COPYING and too many others). 1. Must I provide the source code or can I choose not to? BSD: no, GPL: yes, but see clause 3c: 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.) If you don't change the GPL'ed components of a FreeBSD release, you are allowed to point people back to the corresponding FreeBSD release sources. In other words, you can set up a shrinkwrapped appliance using third-party code and not have to provide the source code to your specific application. You might want to consider the Nokia firewall boxes as an example. 2. Must I license it under the FreeBSD license? The existing code already is under the BSD or GPL licenses. You can modify the code according to those licenses, and you can modify the code or combine it with external code which may result in the creation of a derivative work. 3. Can I license it under my own terms/license? If so, must I reproduce the FreeBSD copyright notice and the disclaimer and if so, where? You would probably need to talk to a laywer if you want to relicense the FreeBSD codebase, and I'm not one. Out of curiosity, what would be the terms of your license? (If you're not willing to answer publicly, OK, but see above.) 4. Who owns the copyright to my modifications, me or FreeBSD? You do. [1] 5. Must I contribute my modifications back to the FreeBSD project or can I choose not to? Nope-- you have the right to make private modifications of BSD code and redistribute them, or choose not to. For GPL code, see clause 3 a-c. Appreciate your feedback. Sure. Have fun, -- -Chuck [1] This is assuming your changes are significant enough to merit copyright protection in their own right; trivial changes like one-line patches, etc would not ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: License Question
>-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Manolo >Fredricks >Sent: Thursday, November 24, 2005 11:27 PM >To: freebsd-questions@freebsd.org >Subject: License Question > > > Hi All > > I'm new to this forum. I am a bit confused about the FreeBSD >license and keep getting conflicting answers from different >people. Would like to know you guys think. Here goes. > > If I make modifications to FreeBSD and then distribute it >(the modified FreeBSD) to others: > > 1. Must I provide the source code or can I choose not to? This depends. What do you mean by "FreeBSD" FreeBSD contains some programs that are not under the BSD license. For example the compiler. That is under the GPL. If you modify the compiler the GPL license says you must distribute the mods. Anyone doing what you propose would presumably be not so lazy that they would not actually read the source code they are working on, it will say at the beginning of the code what license it is under. Read the FreeBSD website it contains some text of some of the licenses. Read the text. The text will tell you what is allowable and what is not. If you still have questions about the licensing ON A SPECIFIC SOURCE FILE or questions on A SPECIFIC LICENSE then come here and ask. Otherwise, asking general questions like you are doing is just looking to cause trouble. There is no "get out of jail free card" in the FreeBSD licensing that covers every source file. You do indeed have to actually do the work of looking at everything you are linking into, the source files of it, and check their licenses. Effort has been made to try to get the base system as unencumbered as possible, but this has mainly been done with the idea of not causing problems for users when they compile programs and run them under FreeBSD for their organization or for other people, and not making companies selling FreeBSD binaries have to spend months rewriting critical parts of the system. It is a different ballgame when you are proposing taking source in the FreeBSD distribution and modifying it then distributing only the modified binaries. There are many companies doing this, but all of them had to vet their source the same way you are going to have to do. Sorry, but there is no free lunch here, you cannot just assume everything in FreeBSD is covered under the FreeBSD license. Ted PS Keep one other thing in mind. If you make mods to the FreeBSD files and do not contribute your changes back, you are going to have to be forever rewriting your mods when a new FreeBSD version comes out. If however you contribute your mods back, and they are accepted, (some mods are not accepted) then you will be freed from the burden of having to maintain them. What is more important is that you will get advice and direction from the core as to where they intended to go with FreeBSD, and this will help you to avoid writing mods that later have to be extensively rewritten. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"