Copyright question


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Copyright question
# 8  
Old 10-06-2011
Quote:
The GPL prohibits you from selling things derived directly from source using that license, it's no barrier to just using them. An important distinction that's occasionally forgotten.
It is more complicated that that. It depends on the particular version of the GPL license. For example, from Frequently Asked Questions about the GNU GPL v2.0 - GNU Project - Free Software Foundation (FSF)
Quote:
Does the GPL allow me to sell copies of the program for money?

Yes, the GPL allows everyone to do this. The right to sell copies is part of the definition of free software. Except in one special situation, there is no limit on what price you can charge. (The one exception is the required written offer to provide source code that must accompany binary-only release.)
 
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to update copyright header on a folder

Hi, I have multiple shell scripts in diffrent folders on server. Most of them contain copyright information like on the third line * Copyright © 2004, 2005, My Inc. All rights reserved. I need to change these headers to * Copyright © 2003, 2009, My Inc. All rights reserved. ... (2 Replies)
Discussion started by: neeto
2 Replies

2. Shell Programming and Scripting

How to append copyright to all files?

I have one file that contain copyright notice, that I would like to append to all files in our directory structure (excluding binaries). How can I do that? Thanks for your help! (3 Replies)
Discussion started by: SiftinDotCom
3 Replies

3. UNIX for Dummies Questions & Answers

Copyright Symbol?

Anyone know how to have the copyright symbol display without using the '@' sign or the '(c)' key combinations? Is it available? Not important, just my a... retentive side wishing to shore up some scripts with a true copyright symbol. (2 Replies)
Discussion started by: spieterman
2 Replies
Login or Register to Ask a Question
INTRO(9)						   BSD Kernel Developer's Manual						  INTRO(9)

NAME
intro -- introduction to system kernel interfaces DESCRIPTION
This section contains information about the interfaces and subroutines in the kernel. PROTOTYPES ANSI-C AND ALL THAT Yes please. We would like all code to be fully prototyped. If your code compiles cleanly with cc -Wall we would feel happy about it. It is important to understand that this isn't a question of just shutting up cc, it is a question about avoiding the things it complains about. To put it bluntly, don't hide the problem by casting and other obfuscating practices, solve the problem. INDENTATION AND STYLE
Believe it or not, there actually exists a guide for indentation and style. It isn't generally applied though. We would appreciate if people would pay attention to it, and at least not violate it blatantly. We don't mind it too badly if you have your own style, but please make sure we can read it too. Please take time to read style(9) for more information. NAMING THINGS
Some general rules exist: 1. If a function is meant as a debugging aid in DDB, it should be enclosed in #ifdef DDB #endif /* DDB */ And the name of the procedure should start with the prefix DDB_ to clearly identify the procedure as a debugger routine. SCOPE OF SYMBOLS
It is important to carefully consider the scope of symbols in the kernel. The default is to make everything static, unless some reason requires the opposite. There are several reasons for this policy, the main one is that the kernel is one monolithic name-space, and pollution is not a good idea here either. For device drivers and other modules that don't add new internal interfaces to the kernel, the entire source should be in one file if possi- ble. That way all symbols can be made static. If for some reason a module is split over multiple source files, then try to split the module along some major fault-line and consider using the number of global symbols as your guide. The fewer the better. SEE ALSO
style(9) HISTORY
The intro section manual page appeared in FreeBSD 2.2. BSD
December 13, 1995 BSD