Free Essay

Freeimage Public License

In:

Submitted By karawaci
Words 2854
Pages 12
1. Definitions.

1.1. "Contributor" means each entity that creates or contributes to the creation of Modifications.

1.2. "Contributor Version" means the combination of the Original Code, prior Modifications used by a Contributor, and the Modifications made by that particular Contributor.

1.3. "Covered Code" means the Original Code or Modifications or the combination of the Original Code and Modifications, in each case including portions thereof.

1.4. "Electronic Distribution Mechanism" means a mechanism generally accepted in the software development community for the electronic transfer of data.

1.5. "Executable" means Covered Code in any form other than Source Code.

1.6. "Initial Developer" means the individual or entity identified as the Initial Developer in the Source Code notice required by Exhibit A.

1.7. "Larger Work" means a work which combines Covered Code or portions thereof with code not governed by the terms of this License.

1.8. "License" means this document.

1.9. "Modifications" means any addition to or deletion from the substance or structure of either the Original Code or any previous Modifications. When Covered Code is released as a series of files, a
Modification is:

A. Any addition to or deletion from the contents of a file containing Original Code or previous Modifications.

B. Any new file that contains any part of the Original Code or previous Modifications.

1.10. "Original Code" means Source Code of computer software code which is described in the Source Code notice required by Exhibit A as Original Code, and which, at the time of its release under this License is not already Covered Code governed by this License.

1.11. "Source Code" means the preferred form of the Covered Code for making modifications to it, including all modules it contains, plus any associated interface definition files, scripts used to control compilation and installation of an Executable, or a list of source code differential comparisons against either the Original Code or another well known, available Covered Code of the Contributor's choice. The Source Code can be in a compressed or archival form, provided the appropriate decompression or de-archiving software is widely available for no charge.

1.12. "You" means an individual or a legal entity exercising rights under, and complying with all of the terms of, this License or a future version of this License issued under Section 6.1. For legal entities, "You" includes any entity which controls, is controlled by, or is under common control with You. For purposes of this definition, "control" means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) ownership of fifty percent (50%) or more of the outstanding shares or beneficial ownership of such entity.

2. Source Code License.

2.1. The Initial Developer Grant.
The Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive license, subject to third party intellectual property claims:

(a) to use, reproduce, modify, display, perform, sublicense and distribute the Original Code (or portions thereof) with or without Modifications, or as part of a Larger Work; and

(b) under patents now or hereafter owned or controlled by Initial Developer, to make, have made, use and sell ("Utilize") the Original Code (or portions thereof), but solely to the extent that any such patent is reasonably necessary to enable You to Utilize the Original Code (or portions thereof) and not to any greater extent that may be necessary to Utilize further Modifications or combinations. 2.2. Contributor Grant.
Each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license, subject to third party intellectual property claims:

(a) to use, reproduce, modify, display, perform, sublicense and distribute the Modifications created by such Contributor (or portions thereof) either on an unmodified basis, with other Modifications, as Covered Code or as part of a Larger Work; and

(b) under patents now or hereafter owned or controlled by Contributor, to Utilize the Contributor Version (or portions thereof), but solely to the extent that any such patent is reasonably necessary to enable You to Utilize the Contributor Version (or portions thereof), and not to any greater extent that may be necessary to Utilize further Modifications or combinations.

3. Distribution Obligations.

3.1. Application of License.
The Modifications which You create or to which You contribute are governed by the terms of this License, including without limitation Section 2.2. The Source Code version of Covered Code may be distributed only under the terms of this License or a future version of this License released under Section 6.1, and You must include a copy of this License with every copy of the Source Code You distribute. You may not offer or impose any terms on any Source Code version that alters or restricts the applicable version of this License or the recipients' rights hereunder. However, You may include an additional document offering the additional rights described in Section 3.5.

3.2. Availability of Source Code.
Any Modification which You create or to which You contribute must be made available in Source Code form under the terms of this License either on the same media as an Executable version or via an accepted Electronic Distribution Mechanism to anyone to whom you made an Executable version available; and if made available via Electronic Distribution Mechanism, must remain available for at least twelve (12) months after the date it initially became available, or at least six (6) months after a subsequent version of that particular Modification has been made available to such recipients. You are responsible for ensuring that the Source Code version remains available even if the Electronic Distribution Mechanism is maintained by a third party.

3.3. Description of Modifications.
You must cause all Covered Code to which you contribute to contain a file documenting the changes You made to create that Covered Code and the date of any change. You must include a prominent statement that the Modification is derived, directly or indirectly, from Original Code provided by the Initial Developer and including the name of the Initial Developer in (a) the Source Code, and (b) in any notice in an Executable version or related documentation in which You describe the origin or ownership of the Covered Code.

3.4. Intellectual Property Matters

(a) Third Party Claims.
If You have knowledge that a party claims an intellectual property right in particular functionality or code (or its utilization under this License), you must include a text file with the source code distribution titled "LEGAL" which describes the claim and the party making the claim in sufficient detail that a recipient will know whom to contact. If you obtain such knowledge after You make Your Modification available as described in Section 3.2, You shall promptly modify the LEGAL file in all copies You make available thereafter and shall take other steps (such as notifying appropriate mailing lists or newsgroups) reasonably calculated to inform those who received the Covered Code that new knowledge has been obtained.

(b) Contributor APIs.
If Your Modification is an application programming interface and You own or control patents which are reasonably necessary to implement that API, you must also include this information in the LEGAL file.

3.5. Required Notices.
You must duplicate the notice in Exhibit A in each file of the Source Code, and this License in any documentation for the Source Code, where You describe recipients' rights relating to Covered Code. If You created one or more Modification(s), You may add your name as a Contributor to the notice described in Exhibit A. If it is not possible to put such notice in a particular Source Code file due to its structure, then you must include such notice in a location (such as a relevant directory file) where a user would be likely to look for such a notice. You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Code. However, You may do so only on Your own behalf, and not on behalf of the Initial Developer or any Contributor. You must make it absolutely clear than any such warranty, support, indemnity or liability obligation is offered by You alone, and You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of warranty, support, indemnity or liability terms You offer.

3.6. Distribution of Executable Versions.
You may distribute Covered Code in Executable form only if the requirements of Section 3.1-3.5 have been met for that Covered Code, and if You include a notice stating that the Source Code version of the Covered Code is available under the terms of this License, including a description of how and where You have fulfilled the obligations of Section 3.2. The notice must be conspicuously included in any notice in an Executable version, related documentation or collateral in which You describe recipients' rights relating to the Covered Code. You may distribute the Executable version of Covered Code under a license of Your choice, which may contain terms different from this License, provided that You are in compliance with the terms of this License and that the license for the Executable version does not attempt to limit or alter the recipient's rights in the Source Code version from the rights set forth in this License. If You distribute the Executable version under a different license You must make it absolutely clear that any terms which differ from this License are offered by You alone, not by the Initial Developer or any Contributor. You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of any such terms You offer.

3.7. Larger Works.
You may create a Larger Work by combining Covered Code with other code not governed by the terms of this License and distribute the Larger Work as a single product. In such a case, You must make sure the requirements of this License are fulfilled for the Covered Code.

4. Inability to Comply Due to Statute or Regulation.

If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Code due to statute or regulation then You must: (a) comply with the terms of this License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be included in the LEGAL file described in Section 3.4 and must be included with all distributions of the Source Code. Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it.

5. Application of this License.

This License applies to code to which the Initial Developer has attached the notice in Exhibit A, and to related Covered Code.

6. Versions of the License.

6.1. New Versions.
Floris van den Berg may publish revised and/or new versions of the License from time to time. Each version will be given a distinguishing version number.

6.2. Effect of New Versions.
Once Covered Code has been published under a particular version of the License, You may always continue to use it under the terms of that version. You may also choose to use such Covered Code under the terms of any subsequent version of the License published by Floris van den Berg
No one other than Floris van den Berg has the right to modify the terms applicable to Covered Code created under this License.

6.3. Derivative Works.
If you create or use a modified version of this License (which you may only do in order to apply it to code which is not already Covered Code governed by this License), you must (a) rename Your license so that the phrases "FreeImage", `FreeImage Public License", "FIPL", or any confusingly similar phrase do not appear anywhere in your license and (b) otherwise make it clear that your version of the license contains terms which differ from the FreeImage Public License. (Filling in the name of the Initial Developer, Original Code or Contributor in the notice described in Exhibit A shall not of themselves be deemed to be modifications of this License.)

7. DISCLAIMER OF WARRANTY.

COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.

8. TERMINATION.

This License and the rights granted hereunder will terminate automatically if You fail to comply with terms herein and fail to cure such breach within 30 days of becoming aware of the breach. All sublicenses to the Covered Code which are properly granted shall survive any termination of this License. Provisions which, by their nature, must remain in effect beyond the termination of this License shall survive.

9. LIMITATION OF LIABILITY.

UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO YOU OR ANY OTHER PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE
EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THAT EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.

10. U.S. GOVERNMENT END USERS.

The Covered Code is a "commercial item," as that term is defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer software" and "commercial computer software documentation," as such terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquire Covered Code with only those rights set forth herein.

11. MISCELLANEOUS.

This License represents the complete agreement concerning subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. This License shall be governed by Dutch law provisions (except to the extent applicable law, if any, provides otherwise), excluding its conflict-of-law provisions. With respect to disputes in which at least one party is a citizen of, or an entity chartered or registered to do business in, the The Netherlands: (a) unless otherwise agreed in writing, all disputes relating to this License (excepting any dispute relating to intellectual property rights) shall be subject to final and binding arbitration, with the losing party paying all costs of arbitration; (b) any arbitration relating to this Agreement shall be held in Almelo, The Netherlands; and (c) any litigation relating to this Agreement shall be subject to the jurisdiction of the court of Almelo, The Netherlands with the losing party responsible for costs, including without limitation, court costs and reasonable attorneys fees and expenses. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not apply to this License.

12. RESPONSIBILITY FOR CLAIMS.

Except in cases where another Contributor has failed to comply with Section 3.4, You are responsible for damages arising, directly or indirectly, out of Your utilization of rights under this License, based on the number of copies of Covered Code you made available, the revenues you received from utilizing such rights, and other relevant factors. You agree to work with affected parties to distribute responsibility on an equitable basis.

EXHIBIT A.

"The contents of this file are subject to the FreeImage Public License Version 1.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://home.wxs.nl/~flvdberg/freeimage-license.txt

Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License.

Similar Documents

Premium Essay

Mozilla Firefox

...In today’s fast moving world it is important for every company to keep up with the pace of change and be innovative. This job can not be done by just a few people within the company. However companies need the help of everyone, especially the costumers, since they are the one who have the needs and buy or do not buy the product in the end. Useful knowledge is wide spread and hard to get. One possible avenue to collect as many new ideas and suggestions as possible – is to use the concept of Open Innovation. Open Innovations connect external ideas with the knowledge of the internal Research and Development division of a company (Chesbrough, 2003). It is difficult and costly to fully understand the costumers. Open Innovations give the companies a chance to let their customers participate in their innovation process (Thomke & von Hippel, 2002). Open Source is one of the most controversial phenomena of IT-industry nowadays. Confrontation of its supporters and opponents is perhaps the most noticeable trend in the soft world recent years. And it is not surprising because as soon as someone starts to speak about Open Source, the rest remember Microsoft and its products, which are common examples for proving inferiority and inadequacy of proprietary software (i.e. programs with closed-source) (Sharma, Sugumaran, & Rajagopalan, 2002). Open Source is a method of programs’ development and licensing, in which everyone is entitled to a free application use or sale...

Words: 387 - Pages: 2

Free Essay

Microsoft vs Foss

...In 2006, when Microsoft Corp. stated that the Linux kernel and other software’s violated their patents, deal has been struck between the FOSS community and Microsoft. Some customers actually entered into direct patent licenses with Microsoft and including some "major brand-name companies" in financial services, health care, insurance and information technology. (He says they don't want to be identified, presumably because they fear angering the FOSS community.) Others wanted Microsoft to work out the patent issues directly with the commercial distributors like Red Hat and Novell. (Red Hat has about 65 percent of the paid Linux server market, according to IDC, while Novell has 26 percent.) Microsoft and Novell agreed not to sue each other's customers for patent infringement. That would be okay, because it's something that the GPL does not address. On those terms, Novell agreed to give Microsoft a percentage of all its Linux revenue through 2011 (or a minimum of $40 million). The pact also included a marketing collaboration. Microsoft agreed to pay Novell $240 million for "coupons" that it could then resell to customers (theoretically for a profit), who would, in turn, trade them in for subscriptions to Novell's Linux server software. In addition, Microsoft gave Novell another $108 million as a "balancing payment" in connection with the patent part of the deal. It might seem counterintuitive that Microsoft would end up paying millions to Novell when Microsoft...

Words: 587 - Pages: 3

Free Essay

General Public License

...Option One GNU Introduction The GNU or General Public License plays a major role today in the way people think of programs. Richard Stallman of the Free Software Foundation (FSF) was who originally written the GNU or simply GPL. The case is, most software’s don’t want you to share or change the program. This means that they are trying to take away freedoms of having the program. What the GNU General Public License is designed to do is the opposite of that because it offers freedom to share and change the software and to make sure it is free for all of its users. This creation caused it to be the most widely used free software license. The GPL accounted for nearly 65% of the 43,442 free software projects listed on Freshmeat as of August 2007. Some believe that the copyleft provided from the GPL was crucial to Linux’s Success because it gave assurance that the work done by programmers who were involved in the kernel would remain free and benefit the world. After the first version of the GPL, more were made that followed. The first GPL was made in 1989. After that, another version was made with similar licenses but there was concern over problems in the GPLv2 so they made another one in June 2007. Preamble The General Public License was designed so that it meant that the people won’t think of a free software as related to its price but more to freedom. What this means is that people can do almost anything to the program including, making copies, giving away copies, selling...

Words: 632 - Pages: 3

Free Essay

Gnu General Public License (Gpl)

...The GNU General Public License (GPL) is a free, copy left license used primarily for software. The GNU GPL allows users to change and share all versions of a program. It’s provided through the Free Software Foundation, a nonprofit corporation that works to provide free software for the GNU Project. *** General Public License is intended to guarantee ones freedom to share and change free software and also to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. History The GNU Program was launched in 1984 for the express purpose of developing operating systems that are similar to Unix. Richard Stallman produced the first GPL through the GNU Program in 1989. Licensees must adhere to the designated terms and conditions of the GPLs and owners may sell copies of programs under GPL, or distribute them for free. With GPL owners are now allowed to modify digital materials as well. Role This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed...

Words: 501 - Pages: 3

Free Essay

Application Architecture and Process Design

...GNU Public License and its Role POS/355 July 21, 2014 GNU Public License and its Role The LINUX software and other products are restricted with a License or patents to keep individual from altering or modifying the software. Developers usually release their software programs the way they think it best suit the potential business owner or users. The General Public License (GNU) role is to ensure when new software is released that it remains free to everyone to use as they please. The GNU role is to remove any software that has no source code. The parts that do not contain a source code are called binary blob and firmware generally redistributable, do not give the user the freedom to modify or study them. General Public License know as (GNU) General Public License was created by Richard M. Stallman in 1970 when he was a programmer at MIT’s Artificial Intelligence lab. The General Public License (GNU/ GPL) is a copy left license for software and other kinds of work that are free to the public The General Public License is the most popular free and open source software (FOSS) license today. According to Ronald "free software and open source are often interchangeably used (and the respective movements share many common goals" (2006). The General Public License purpose is to guarantee individual or developers the freedom to share and alter any version of a program to ensure it remains free and available to every individual. The General Public License is used by...

Words: 519 - Pages: 3

Free Essay

Open and Close Source Systems Paper Pos/355

...Systems Paper POS/355 March 1, 2013 Bhupinder Singh Open and Closed Source Systems Paper GNU GPL (General Public License) defined as the copy left or free licensed software (GNU.org, 2007). When making an invention the creator must have copyrights to protect them from their inventions. No one wants their inventions taken from them. They can loss acknowledgement or worse the royalties not given to them. Copyrights mean the right to copy; generally, it gives the copyright holder many other rights to their software or products. Creators who work hard to make their software or products a reality, they want that accreditation for their works; and they can determine who can take the work and financially benefit for the use it. It is a form of intellectual property; like patent, trademark, and trade secret (copyright.gov, 2012). By contrast, the GNU GPL is freedom of a guarantee to change and share the versions of the programs or software’s (GNU.org, 2007). Most organizations use GNU GPL for their software and it with their authors also that release the work. The licenses are put in place for developer’s freedom and to change and share their work that they develop; this is GNU General Public License. There are steps that are taken to use GNU GLP. (1) assert copyright on the software, and (2) offer you this license giving you legal permission to copy, distribute and/or modify it, and this the developers that uses GNU GLP protect your rights with...

Words: 479 - Pages: 2

Premium Essay

Open and Closed Source Systems

...GNU GPL (General Public License) defined as the copy left or free licensed software (GNU.org, 2007). When making an invention the creator must have copyrights to protect them from their inventions. No one wants their inventions taken from them. They can loss acknowledgement or worse the royalties not given to them. Copyrights mean the right to copy; generally, it gives the copyright holder many other rights to their software or products. Creators who work hard to make their software or products a reality, they want that accreditation for their works; and they can determine who can take the work and financially benefit for the use it. It is a form of intellectual property; like patent, trademark, and trade secret (copyright.gov, 2012). By contrast, the GNU GPL is freedom of a guarantee to change and share the versions of the programs or software’s (GNU.org, 2007). Most organizations use GNU GPL for their software and it with their authors also that release the work. The licenses are put in place for developer’s freedom and to change and share their work that they develop; this is GNU General Public License. There are steps that are taken to use GNU GLP. (1) assert copyright on the software, and (2) offer you this license giving you legal permission to copy, distribute and/or modify it, and this the developers that uses GNU GLP protect your rights with these steps (GNU. org, 2007). When distributing copies of software for free, the creator must pass on the recipients and receiving...

Words: 438 - Pages: 2

Free Essay

Eula

...User License Agreements Microsoft Software License Terms User Rights Granted by Microsoft Write a paragraph defining the rights of the user in Microsoft’s EULA. Your paragraph must include what rights the user has to use, copy, and install the software. Can you sell or transfer the software to someone else? On how many devices may you install the software? Microsoft’s EULA states that the user has the right to install 1 copy of the software on 1 computer to be used by one person at a time. One cannot sell the software. They can however transfer it with seemingly strict guidelines. They may do so directly on a licensed computer with a COA. The user may reassign this software license to a different computer any number of times, but not more than one time every 90 days. You may not retain any copies. The software is also not licensed for commercial hosting Warranty with the Microsoft License Write a paragraph describing the warranty, if any, which comes with Microsoft Office. Microsoft does offer a limited warranty for this software. The warranty states that it is not responsible for any problems that the user causes due to not following instructions. The limited warranty starts when the user gets their copy and lasts for 1 year. If the user gets any updates or replacement software during that year, they are covered for the remainder of the year, or 30 days, whichever is longer. GNU General Public License User Rights Granted by GNU General Public License ...

Words: 656 - Pages: 3

Free Essay

Android

...Android operating system is also no exception. Along with its open source code released by Google under the Apache license, the security issue is becoming more and more significant and emergency. Whether or not the Android operating system is designed with any intrinsic security initially, from this article’s perspective, the author may state a negative answer of Android as a failure both the operating system and the hardware. We can get start from an overview about what the author listed through the beginning to end in the article. At first, the initial reason and environment about why Android developed appear to us along with the so called wrong policy-atypia at the beginning in the development cycle. It’s precisely because these non-mainstreams such as true multi-tasking that cause the current insecurity issues including multifariously malicious malware, e.g. Trojan-SMS, Fake Player, Droid Dream malware and so on. Meanwhile, the author listed the cause for concern, and also some tests on Android from the analyst view to test the security. There are two points in the article leave me a deep impression. The first one is a series of atypical and nonstandard design of Android. To come the first, its main kernel is just a branch of mainstream in Linux research and development. Besides, Android don’t give the support to the full set of standard General Public License. Last one but not the least one, Data storage is beyond standard using a lightweight relational database and also...

Words: 598 - Pages: 3

Free Essay

Ctera

...Quick Walkthrough CTERA CloudPlug Cloud Attached Storage May 2012 Firmware Version 3.1 Safety Precautions Warning Carefully read the Safety Instructions and the Installation and Operating Procedures provided in this User's Guide before attempting to install or operate the appliance. Failure to follow these instructions may result in damage to equipment and/or personal injuries, and will void your warranty. Safety Precautions This product contains no user-serviceable parts. Repair, maintenance and servicing of this appliance are only to be carried out by qualified CTERA personnel. This product may only be used for the applications described in the user guide, and only in connection with accessories which have been approved by CTERA. This product can only function correctly and safely if it is transported, stored, set up, and installed correctly, and operated and maintained as recommended. Operate this product only from the type of power source indicated on the product’s marking label. Overloaded AC outlets, extension cords, frayed power cords, damaged or cracked wire insulation, and broken plugs are dangerous. They may result in an electrical shock or fire hazard. Route power supply cords so that they are not likely to be walked on or pinched by items placed upon or against them. Slots and openings in the enclosure are provided for ventilation, to ensure reliable operation of the product and to protect it from overheating. Do not block or cover these openings. Never...

Words: 4880 - Pages: 20

Premium Essay

Free and Open Source Software (Foss)

...However, in 2006 Microsoft found that many of their patents had been infringed upon by several different aspects. The Linux kernel found in most servers was one of them. Microsoft took a big leap going after FOSS for 235 patents. FOSS is run by Stallman who was responsible for the GNU Manifesto also known to most as the GNU General Public License (GPL) . With Microsoft heading the full speed train against FOSS it took a demanding tire on both parties. While Microsoft, in the mean time was also striking a deal with Novell on its Linux based server support. FOSS was sure to go under as Linux was the base of all its open source used in many applications and the applications within Linux such as samaba or Open Office. The Deal with Novell was made to walk around the GPL of the GNU and expose loop holes for Microsoft’s gain but also creating a pressing dilemma for the GNU. The deal struck between Novell and Microsoft was a “we don’t sue you and you don’t sue us” which indicates that not only was FOSS involved in patent infringement but also Microsoft. The Deal included over 200 million dollars to Novell and 43 Million to Microsoft for “license distribution” of Novells’ Server software. The after effects of this deal resulted in a addition to the GPL from Stallman and his lawyer. This was meant to entrap Microsoft from making a deal like the one struck with Novell again and prohibit a resale effect of “coupons” that were redeemable for Novell products. FOSS has still...

Words: 419 - Pages: 2

Free Essay

Gnu Public License

...used with the Linux kernel. The Free Software Foundation’s GNU project, or GNU Not Linux, provides the necessary tools to developers and has approved the GNU Public License, or GPL (Stallings, 2012). According to Free Software Foundation, or FSF (2007), the GNU Public License discusses the freedom for designers to share and change all versions of the program. Linux is free software, as in free for anyone to use, modify, or copy without restraint. The GNU Public License, or GPL, provides a list of basic permissions, rights, and conveying verbatim copies (FSF, 2007). The main idea of publishing the GPL licensing terms is that no one who uses Linux and/or creates any Linux-derived copy can make the copy proprietary (Stallings, 2012). Under the GPL, basic permissions are granted to all who use, copy, or modify a GNU program. The basic permissions essentially grant unlimited permission to run an unmodified version of a program (FSF, 2007). According to the FSF (2007), permissions are also granted to convey a derivative of an unmodified program; however, the conditions listed below must be met: * The work must display a notice stating who modified and the date it was modified. * The work must display a notice that it is released under the GPL. * The entire work must be licensed under the GPL to ensure the license the whole work and its parts. * If the work has interactive interfaces for users, each must display the appropriate legal notices, Another item in...

Words: 540 - Pages: 3

Free Essay

Linux Ch 1

...1. What is free software? List three characteristics of free software. Free software is software that users can change and distribute without any repercussions. The characteristics of free software is that the software can be used for any purpose, can be studied and changed and can be distributed with the changes made. 3. What are multiuser systems? Why are they successful? Multiuser systems allows many people to use all of the resources of the system at the same time. This makes the system successful because the resources available can be used to its utmost potential so its growth is always on the rise. 5. In which language is Linux written? What does the language have to do with the success of Linux? Linux is written in C which means that that it is portable. In this way it makes it successful for it can be adapted to different machines and allows it to complete tasks on almost any platform. 9. What is a shell? How does it work with the kernel? With the user? A shell is a command interpreter which is the link between you and the operating system. Shells can arrange a file for later execution using scripts which help with operations and keep kernels on a priority list. This also makes it so users can issue short commands that perform highly complex operations. 11. Why is the Linux filesystem referred to as hierarchical? The filesystem of Linux is hierarchical due to its structure of arranging files under directories. These directories can hold other directories...

Words: 388 - Pages: 2

Premium Essay

Open and Closed Source Systems

...Close Source Systems Paper Pos 355 Open and Closed Source Systems Paper POS/355 Open and Closed Source Systems Paper GNU GPL (General Public License) defined as the copy left or free licensed software (GNU.org, 2007). When making an invention the creator must have copyrights to protect them from their inventions. No one wants their inventions taken from them. They can loss acknowledgement or worse the royalties not given to them. Copyrights mean the right to copy; generally, it gives the copyright holder many other rights to their software or products. Creators who work hard to make their software or products a reality, they want that accreditation for their works; and they can determine who can take the work and financially benefit for the use it. It is a form of intellectual property; like patent, trademark, and trade secret (copyright.gov, 2012). By contrast, the GNU GPL is freedom of a guarantee to change and share the versions of the programs or software’s (GNU.org, 2007). Most organizations use GNU GPL for their software and it with their authors also that release the work. The licenses are put in place for developer’s freedom and to change and share their work that they develop; this is GNU General Public License. There are steps that are taken to use GNU GLP. (1) assert copyright on the software, and (2) offer you this license giving you legal permission to copy, distribute and/or modify it, and this the developers that uses GNU GLP protect your rights with these...

Words: 482 - Pages: 2

Free Essay

Open and Closed Source Systems

...use free software. Not UNIX Linux is an operating system created based on the Unix operating system all of the improvements to Unix used GNU tools to create the kernel that would become Linux. GNU is an acronym that stands for “Not Unix” and is part of a project of people collaborating over the Internet, creating free to use software and source codes. According to Stallings, W. (2012) “Linus Torvalds, a Finnish student of computer science, wrote the initial version.” and “posted an early version of Linux on the Internet in 1991.". Since then, a number of people, collaborating over the Internet, have contributed to the development of Linux, all under the control of Torvalds. Seal of Approval GNU Public License (GPL) is the approval of the collaborated efforts of the developers of the free software and is approved by a specific foundation. The foundation that gives the seal of approval of the publicly created software is called Free Software Foundation...

Words: 399 - Pages: 2