Note: The advertising clause in the license that appeared in the BSD Unix file was officially revoked by the director of the Technology Licensing Office of the University of California on July 22nd 1999. He indicated that article 3 was hereby deleted in its entirety.
Please note that the new BSD license is therefore equivalent to the MIT license, except for the final terms without endorsement.
& lt Owner & gt Director, University of California
& lt Organization & gt University of California at Berkeley
& lt year & gt= 1998
In the original BSD license, the phrases copyright owner and contributor appearing in the disclaimer are both law enforcers and contributors.
The following are license templates:
Copyright (c)&; lt； Year and time. gt； ，& amplt； Owner and owner. gt；
property in copyright
Redistribution and use in source code and binary form (with or without modification) are allowed as long as the following conditions are met:
Redistribution of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistribution in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documents and/or other materials provided with the distribution.
Neither & Organization and management. gt； Without prior written permission, the names of its contributors shall not be used to endorse or promote the products derived from this software.
This software is provided by copyright owners and contributors as it is, and any express or implied warranty, including but not limited to implied warranties of merchantability and fitness for a particular purpose, is rejected. In any case, the copyright owner or contributor shall not be liable for any direct, indirect, incidental, special, punitive or consequential damage (including but not limited to the procurement of substitute goods or services; Loss of use, data or profit; Or business interruption) and any theory of liability, whether contractual liability, strict liability, tort liability (including denial or other liability), even after being informed of the possibility of such damages. The following is a BSD license template. To create your own license, you need to replace the owner, institution and year (see below) values in the original template with your own values.
Note: The disclosure clause in the BSD Unix document was abolished by the director of the Technology Licensing Office of the University of California on July 22, 1999 in the official name. He indicated that paragraph 3 was "hereby deleted in its entirety".
Please note that the new BSD license is the same as the MIT license, except for the final disapproval clause.
& lt everyone > = Director, University of California
& lt Institution > = University of California, Berkeley
& lt year > = 1998
In the original BSD license, the "copyright owner and contributor" in the disclaimer can also be understood as "director and contributor".
The following are license templates:
Copyright (c); Year; Everyone;
property in copyright
You may redistribute the software or use it in source code and binary form, with or without modification, provided that the following conditions are met:
Redistribution of source code must comply with the above copyright notice, this list of conditions and the following disclaimer.
Redistributing the software in binary form must copy the above copyright notice, this list of conditions, the disclaimer at the bottom of the document and/or other information provided when the code is published.
Without prior written approval, the name of the organization or the name of the contributor shall not be used to support or promote the derivative products of the software.
This software is provided by copyright owners and contributors "as is" without any express or implied warranty, including but not limited to the implied warranty of merchantability and fitness for a particular purpose. In any case, the copyright owner or its contributors shall not be liable for any direct, indirect, unexpected, special, typical or resulting losses (including but not limited to purchasing substitute products or services; Loss of use value, data or profit; Or business interruption) and assume any liability according to any liability theory, including contract, strict liability or tort (including negligence or otherwise), even if such losses have been warned. Long before the word "open source" was born, software was developed by a loose alliance of programmers and was freely interchangeable. Since 1950' s, SHARE and DECUS companies have developed a lot of software bundled with hardware. Computer companies at that time were all in the hardware business. Reducing software costs and increasing available software can make their hardware more competitive.
At the end of 1960, this pattern has changed. 1965, ADR company developed the software separated from the hardware company, competing with the software packages of some customers started by IBM company. 1968 ADR company obtained its own software patent right.
In order to prevent * * * from enjoying the software, they only provide the software under the following lease: the payment should cover the whole life cycle of the software product. Therefore, ADR retains the ownership of the software and can control the resale and reuse of the software.
1969 The US Department of Justice ordered IBM to stop bundling free software with its hardware. Since then, software has become a product independent of hardware.
1968, informatics companies first put forward killer applications, quickly established the concepts of software products and software companies, and achieved high returns. Informatics has formulated a standard perpetual license agreement, which has now spread all over the software industry. In this agreement, the ownership of the software will never be transferred to its customers. The original implementer of at & UNIX; T, due to the monopoly control of anti-monopoly law firms, software products cannot be legally sold, but unix can be provided to academic institutions under the condition of only charging media fees.
After its practicality was made public at an operating system conference, universities quickly accepted unix. It is very advantageous that unix runs on a very cheap 16-bit computer, PDP- 1 1, and is written in a high-level language that is really suitable for system programming. At that time, it was very common for DEC customers to write their own operating systems. DEC PDP- 1 1 discloses their hardware interfaces. Like Ken, the founder of DEC? Ken olsen claimed: "When you have good hardware, software is as good as coming from heaven".
1975, the author of Unix, Ken? Ken Thompson returned to his alma mater, University of California, Berkeley, and taught unix kernel source code line by line. This eventually led to the emergence of the famous evolution system unix-BSD (Berkeley Software Distribution Suite). University of California, Berkeley, converted unix into a 32-bit system, increased virtual memory, and realized the TCP/IP protocol stack necessary for establishing the Internet. The University of California, Berkeley, enables unix to use BSD at the cost of media under the famous BSD protocol. Customers from AT&; T buy unix, and then buy BSD tapes from the University of California, Berkeley.
From 65438 to the mid-1980s, the US government passed an antitrust law to break up AT & amp； T is over. At&T Company. T still owns unix and can sell it now. In terms of authorization, AT & amp； T has taken radical measures, so most commercial unix is based on AT & amp； T
1990s, at &；; T sued the University of California, Berkeley, BSD for infringement. University of California, Berkeley, found that at & amp； T integrates many improvements in BSD into AT&; Test the product. So, a game is mainly at at & amp； The marathon lawsuit between t and the university of California, Berkeley began. Meanwhile, some programmers at the University of California, Berkeley are writing about at & amp； T code project. This project finally produced a system called BSD4.4-lite. (Lite, clear, light, so called because this is not a complete system, lacking six AT &；; Test file)
Soon, a series of articles describing 386 personal computer versions of unix originated from BSD were published in Dr. dobbs magazine. This version of unix includes files authorized by BSD protocol to replace BSD4.4-lite. This 386BSD system should be attributed to the programmer outside the University of California, Berkeley-William? William joritz. Today, it has become the BSD source of all personal computers.
1In the mid-1990s, Novell Company purchased AT & amp； Unix ownership of t, and then secretly acquired the knowledge of terminating the lawsuit. The University of California, Berkeley, quickly stopped supporting BSD. The so-called new BSD protocol applied to FreeBSD in recent years actually allows you to do anything with the program or source code, but it contains the author's disclaimer (you can't sue anyone). This new BSD protocol tends to encourage the commercialization of products. Any BSD code can be sold or included in private products, which does not impose strict restrictions on the application of the code and your future behavior.
Don't confuse the new BSD protocol with those public domain services or products that can be obtained for free. Although those things can be used for any purpose for free, they have no owners. BSD open source protocol is a protocol that gives users great freedom. You can freely use and modify the source code, or redistribute the modified code as open source or proprietary software. When you publish code using BSD protocol, or develop your own products based on BSD protocol code, you need to meet three conditions:
1. If the redistributed product contains source code, the source code must contain the BSD protocol in the original code.
2. If only the binary class library/software is redistributed, the BSD protocol needs to be included in the original code in the document and copyright notice of the class library/software.
3. Do not use the name of the author/organization of the open source code and the name of the original product for marketing.
BSD code encourages code enjoyment, but it needs to respect the copyright of the code author. BSD is a protocol friendly to business integration, because it allows users to modify and redistribute codes, and also allows users to use or develop commercial software for distribution and sales on BSD codes. Many companies and enterprises prefer BSD protocol when choosing open source products, because they can completely control the code of these third parties and can modify or redevelop it when necessary.