Archive for June, 2007

LXer Article

It has been a while since my last installment because events have transpired that have kept me from finishing it, some happy and some sad. With a fair amount of procrastination sprinkled throughout I had begun to write this article off and on after work, between band practices and playing gigs with my band. I would try to meet up with my friend in IRC to pick his brain but our conversations became fewer and far between.

The friend I speak of is Jim Farnsworth (aka R0nin) who passed away in late May. After his death I avoided even looking at this article because I didn’t know how to continue and I would end up just missing him all over again. It hit me just the other day that if Jim were still around he would have long since started riding me about finishing it up and starting work on another. Well Jim, I heard you and I am dedicating this entire series to you my friend, even though you made me promise not to tell anyone it was you who was helping me.

At the end of the last installment I had just gotten Synaptic re-installed and configured after unintentionally removing it. Since then it has worked perfectly and I have been updating and adding and removing software without incident. I even upgraded to the 2.6.21 kernel which has since made my computer boot up significantly faster than any other previous kernel.

During what was to be one of our last conversations I asked Jim why Firefox was called IceWeasel with a different icon and everything under Debian and his response was, plus an expletive or two “I’m not going to waste time explaining it to you, go find out for yourself if means that much to you.” So with a swift kick to the behind from Jim I went and found out why.

I thought it was stupid that it had to be called IceWeasel and before even looking into it I assumed that someone from either Debian or Mozilla was being a control freak or stubborn about something. I would come to find out I was right and wrong at the same time which was new for me, since I am used to just being wrong most of the time.

It seems that Mozilla has an interesting trademark policy regarding the use of the Firefox name. Even after you get permission to use it they can decide to revoke your right at any time, and without much notice either. Now that issue aside Debian has a strict policy of not including non-free software in their distribution and Firefox includes proprietary artwork along with their “Talkback” crash reporting system and the Firefox plugin finder that includes non-free plugins which conflicts with Debian policy.

So between Mozilla’s right to revoke usage and Debian’s non-free software exclusion, something had to be done if a Mozilla flavored browser was going to be available for Debian users. What happened was Debian Developers came up with a different name and removed and/or changed all the proprietary components in Firefox so that people like me wouldn’t cry about not being able use their favorite browser.

I want to commend the Debian Developers who did all the work in making it possible to include IceWeasel in the Debian repositories. I would thank the Mozilla people too but I am not sure exactly what for, except maybe for not making it impossible for the Debian people to make the necessary changes.

Well, I feel better knowing all that, don’t you? I understand and agree with the Debian stance on not including proprietary software and not budging on it but the Mozilla infinite right to revoke usage sounds like something they got from the Microsoft EULA or something. You were right to not waste your time trying to help me wrap my head around this one Jim. I think I feel a headache coming on..

I got the opportunity at work recently to use Free Software to solve a problem with a faulty DVR, save my boss some serious cash in the process and help a coworker pull some music files and stuff off a bad Hard Drive using Knoppix in what I like to call, “How My Big Mouth Finally Paid Off”. Trust me, my mouth still got me into trouble but that’s only because I don’t know my own strength..”Its not my fault, that thing was going to come off anyway..”

Don’t worry, I’ll explain everything.

Read Full Post »


The GNU General Public License is a free, copyleft license for software and other kinds of works.

The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program–to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them 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.

To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it.

For the developers’ and authors’ protection, the GPL clearly explains that there is no warranty for this free software. For both users’ and authors’ sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.

Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users’ freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users.

Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.

The precise terms and conditions for copying, distribution and modification follow.


0. Definitions.

“This License” refers to version 3 of the GNU General Public License.

“Copyright” also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.

“The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations.

To “modify” a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a “modified version” of the earlier work or a work “based on” the earlier work.

A “covered work” means either the unmodified Program or a work based on the Program.

To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.

To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.

An interactive user interface displays “Appropriate Legal Notices” to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.

1. Source Code.

The “source code” for a work means the preferred form of the work for making modifications to it. “Object code” means any non-source form of a work.

A “Standard Interface” means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.

The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A “Major Component”, in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.

The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work’s System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.

The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.

The Corresponding Source for a work in source code form is that same work.

2. Basic Permissions.

All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.

You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.

Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.

3. Protecting Users’ Legal Rights From Anti-Circumvention Law.

No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.

When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work’s users, your or third parties’ legal rights to forbid circumvention of technological measures.

4. Conveying Verbatim Copies.

You may convey verbatim copies of the Program’s source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.

You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.

5. Conveying Modified Source Versions.

You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:

a) The work must carry prominent notices stating that you modified it, and giving a relevant date.

b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”.

c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.

d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.

A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation’s users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.

6. Conveying Non-Source Forms.

You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:

a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.

b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.

c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.

d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.

e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.

A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.

A “User Product” is either (1) a “consumer product”, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, “normally used” refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.

“Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.

If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).

The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.

Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.

7. Additional Terms.

“Additional permissions” are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.

When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.

Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:

a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or

b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or

c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or

d) Limiting the use for publicity purposes of names of licensors or authors of the material; or

e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or

f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.

All other non-permissive additional terms are considered “further restrictions” within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.

If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.

Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.

8. Termination.

You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).

However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.

Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.

Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.

9. Acceptance Not Required for Having Copies.

You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.

10. Automatic Licensing of Downstream Recipients.

Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.

An “entity transaction” is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party’s predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.

You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.

11. Patents.

A “contributor” is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor’s “contributor version”.

A contributor’s “essential patent claims” are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, “control” includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.

Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor’s essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.

In the following three paragraphs, a “patent license” is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To “grant” such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.

If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. “Knowingly relying” means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient’s use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.

If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.

A patent license is “discriminatory” if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.

Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.

12. No Surrender of Others’ Freedom.

If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.

13. Use with the GNU Affero General Public License.

Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.

14. Revised Versions of this License.

The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.

If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy’s public statement of acceptance of a version permanently authorizes you to choose that version for the Program.

Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.

15. Disclaimer of Warranty.


17. Interpretation of Sections 15 and 16.

If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.


How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found.

Copyright (C)

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see .

Also add information on how to contact you by electronic and paper mail.

If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:

Copyright (C) This program comes with ABSOLUTELY NO WARRANTY; for details type `show w’. This is free software, and you are welcome to redistribute it under certain conditions; type `show c’ for details.

The hypothetical commands `show w’ and `show c’ should show the appropriate parts of the General Public License. Of course, your program’s commands might be different; for a GUI interface, you would use an “about box”.

You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see .

The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read .


Copyright (C) 2007 Free Software Foundation, Inc. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below.

0. Additional Definitions.

As used herein, “this License” refers to version 3 of the GNU Lesser General Public License, and the “GNU GPL” refers to version 3 of the GNU General Public License.

“The Library” refers to a covered work governed by this License, other than an Application or a Combined Work as defined below.

An “Application” is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library.

A “Combined Work” is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the “Linked Version”.

The “Minimal Corresponding Source” for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version.

The “Corresponding Application Code” for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work.

1. Exception to Section 3 of the GNU GPL.

You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL.

2. Conveying Modified Versions.

If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version:

a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or

b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy.

3. Object Code Incorporating Material from Library Header Files.

The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following:

a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License.

b) Accompany the object code with a copy of the GNU GPL and this license document.

4. Combined Works.

You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following:

a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License.

b) Accompany the Combined Work with a copy of the GNU GPL and this license document.

c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document.

d) Do one of the following:

0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.

1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user’s computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version.

e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.)

5. Combined Libraries.

You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following:

a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License.

b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.

6. Revised Versions of the GNU Lesser General Public License.

The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation.

If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy’s public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.

Read Full Post »

LXer Article

The big stories this week include Bolivarian Computers made in Venezuela, an illuminating comparison of ODF and OOXML, Mandriva’s CEO says publicly that they will not sign a cross licensing deal with Microsoft, Miguel de Icaza shows off Microsoft’s Flash replacement and an “expert” on Innovation vacillates on his own definition in reference to Open Source software. All these stories and more for your reading enlightenment.

New Google Linux Apps Coming Soon: During their presentation at this years Linux Foundation Collaboration Summit the Google Linux Client Team announced that there are going to be new Google desktop applications coming out this year for Linux.

Venezuela Launches Sale of “Bolivarian” Computers: The Venezuelan government or should I say, The right arm of Hugo Chavez announced the launch of their “Bolivarian Computers” made with combination of Venezuelan and Chinese technology . Four different models that will all have Linux preinstalled. Hugo Chavez may be a power hungry dictator but at least he like Open Source software. Its not much, but its something.

Achieving Openness: A Closer Look at ODF and OOXML: Sam Hiser compares ODF and OOXML and discovers the difference between actually being open standard and saying its an open standard. Just because Micorsoft says its an open standard doesn’t necessarily mean it is, why am I not surprised.

Interview With Fred Miller – GNU/Linux Evangelist: Don Parris interviews Fred Miller, a prolific GNU/Linux evangelist and active member of the OpenSUSE community.

CEO of Mandriva: We will not go to Canossa – No deal with Microsoft: The CEO of Mandriva goes on record to say that his company will not sign a cross licensing deal with Microsoft and in the process earns some respect from the Open Source community.

Ubuntu’d, you’re getting a Dell: Our own Lane Beneke (aka NoDough) writes about his experience of buying a new computer with Ubuntu preinstalled from Dell to give to his Daughter for college.

Adventures in Digital Photography With Linux: Carla Schroder shares some of the new tricks, tips and more that she learned from the Don Parris article From the Camera to the Web With Konqueror.

Silverlight To Run On Linux This Week: In Microsoft’s continuing onslaught on Adobe, VP of Novell Miguel de Icaza will demonstrate Microsoft’s Flash replacement at the Mix07 conference this week in Paris. I guess some of the money they gave to Novell gets you a couple of “stand next to our product” sessions by a VP too.

Don’t wait for Vista SP1, pleads Microsoft: I couldn’t help but post this story. It seems that the uptake of Vista is so bad that Microsoft has had to create a Vista version of the “Get The Facts” website to convince people to upgrade to Vista and not wait for an SP1 update because there will not be one. Vista is so good it doesn’t need an update, ever. Yeah, right.

Bad, Bad Reasons Not to Buy Open-Source Software: Steven J. Vaughan-Nichols responds to the eWEEK slide show, Ten Reasons Not to Buy Open Source which was based on “Microsoft.Net Creates End-to-End Framework That Offers Lower TCO”. The funny thing is, I cannot find either the slide show he references or the Microsoft article anywhere. If someone does, please let me know. I would love to read them.

What the “ultimate filesystem”, Sun ZFS, means for your desktop, in Plain English: Ashton Mills translates Sun’s ZFS filesystem jargon into plain English for the rest of us.

Xandros and Microsoft to build Open Source translator: Xandros announced this week that it will join Microsoft and others to build and ship open source translators between documents stored in Ecma Office Open XML and Open Document Formats. The translators will be made available to Xandros users via the Xandros Networks update facility.

Laura and Me – Updated: Pamela Jones talks about some of the history involving her, SCO, Laura DiDio and some of the things that have been said and done since she worked at SCO and the ensuing trial that Groklaw covers.

Will The Real Open Source CRM Please Stand Up?: Michael Tiemann responds to the many people who have asked “When is the OSI going to stand up to companies who are flagrantly abusing the term ‘open source’?” The answer is: starting today.

Open Source is Not Innovative: In the first of our two FUD articles this week Dr. R. Keith Sawyer who in his own words is “one of the country’s leading scientific experts on creativity” gets his definition of “Innovation” a little mixed up and decides that Open Source Software is, and is not innovative. Read for yourself and decide if he knows what he is talking about. Just how does someone become an expert on Innovation if they don’t know what it means anyway?

Is Open Source Dying?: Michael Hickins does his best to sow the seeds of despair in trying to convince us that despite the ever present and growing success of Open Source that it is actually slowly winding down and dying. And I thought I was crazy..

Read Full Post »

Today I was promoted to Editor-in-Chief for LXer Linux News. Here is the post on LXer.com.

Introducing Scott Ruecker

Read Full Post »

LXer Article

First off, Happy Fathers Day to all you Fathers out there, especially mine. It seems that Microsoft is all over the news this week. Between the Linspire deal, getting help from an old friend in the Justice Department to yet another one of their shills stating that OpenXML really is an open standard. Not to worry though, I have lots of other articles for you to check out.

Microsoft Finds Legal Defender in Justice Dept.: Thomas O. Barnett, top Justice Department antitrust official and former partner at a law firm that representing Microsoft in antitrust disputes, has recently rejected a complaint by Google and is urging state prosecutors to do the same.

Ubuntu 7.04 Feisty Fawn — Cool, Fresh and… Unstable: Borys Musielak writes “This will not be another “I just installed Ubuntu — it beats Windows — try it yourself” type of review. It is going to be rather a report from another successful upgrade, pointing out the biggest surprises and the most miserable failures of the latest release of Ubuntu Linux, codenamed Feisty Fawn.”

Microsoft Spits in GPL Creator Richard Stallman’s Eye: The GPL creator’s attempts to stop Microsoft from cutting any more of those patent-protection deals like the one it cut with Novell don’t quite seem to be working.

Linux Programmer’s Toolbox: What does it take to start writing programs for Linux ? Most people will guess a text editor, knowledge of a programming language and the compiler and libraries of that language would suffice. But ask a professional programmer who has been writing code for Linux and he will differ with you.

Torvalds: Solaris could nudge Linux to GPL 3: Linux leader Linus Torvalds has finally found something that could convince him that the forthcoming version 3 of the General Public License is worth adopting: open-source Solaris.

Microsoft and Linspire Collaboration Promotes Interoperability and Customer Choice: Here is the press release announcing the Linspire-Microsoft deal. I keep hearing an old Queen song in my head, “and another one gone and another one gone, another one bites the dust”.

From the Camera to the Web With Konqueror: Our own Don Parris shows us how to get pictures from our cameras and onto the web without pulling your hair out in another one of our LXer Features.

Microsoft Will Help Deliver a “Better” Linux (Linspire announces deal with Microsoft): Here is the letter that Kevin Carmony wrote where he talks about why the deal with Microsoft is good for Linspire and Linux in general.

Tutorial: Protecting Data with Encrypted Linux Partitions: In this tutorial Carla Schroder shows us how to protect our data using encrypted partitions.

How To Compile A Kernel – Debian Etch: In this tutorial Falko Timme of HowToForge.com shows us the steps to be taken in compiling a kernel under Debian Etch.

Linux leaders plot counterattack on Microsoft: Eric Auchard likens the Open Source movement to a religious sect in his “slightly” slanted report on the recent get together of Open Source figures at Google headquarters.

Lessons from a Community Fundraising Project: D.C. Parris and Brian Proffitt publish their financial report and lessons learned on the Tux-500 campaign.

Microsoft Interoperability Team: Bring on Red Hat: Microsoft said the company hopes to strike a Linux pact with Red Hat similar to the partnerships it has forged with Linux vendors. So far Red Hat is not interested.

Mark Shuttleworth on Ubuntu and Microsoft — he’s not signing nothing: Steven Rosenberg found a post my Mark Shuttleworth on his blog concerning whether or not Ubuntu would be signing a deal with Microsoft. Mark has since expanded and reposted his thoughts on his blog.

Microsoft’s next Linux partner is…?: In the first of our two FUD articles of the week SJVN tries to convince us of his telepathic abilities because he knew that Linspire was going to be next to sign a deal with Microsoft. So Steve, can you tell what I am thinking right now?

Open standards advocate comes out in favor of Microsoft: Microsoft’s standards format has been misunderstood and being “pro Open XML” doesn’t make one “anti ODF”, claims Australian activist Rick Jelliffe. Hmm, I wonder who pays his bills..

Read Full Post »

LXer Article

The big news this week was Microsoft signing LG Electronics and Linux Distributor Xandros to cross patent licensing deals. We have several articles submitted by our readers and Don Parris talks about why those patent agreements are a search for Fool’s Gold.

“Eating Dog Food”: LXer reader Aladdin_Sane submitted this article talking about what happens when there’s no separation between Microsoft and the customers they care about.

Looking for a small Linux that will run with a GUI in 4MB of RAM: LXer, tracyannne posted a question about finding a small Linux Distro that would be small enough for what was needed and got quite the response from other readers.

Linux: making small businesses possible: Sander Marechal writes: “I have a small company that builds websites for equally small businesses in the area and it’s Linux that made this possible. If we would have been stuck on the Windows platform there is no way we could have done what we do because it would simply have been too expensive.”

Microsoft teams with Linux distributor Xandros: Microsoft and Linux distributor Xandros signed a deal very similar to the one signed between MS and Novell. Two down, 500 or so to go..

Former Microsoft Insider Speaks Out: A former Microsoft employee talks about the environment at MS and its evolution during his time there.

GPLv3 – Unforseen Consequences?: Kevin Carmony sound off on his concerns for the GPLv3, one wonders if he is trying to get in line for a deal with Microsoft or something else entirely.

Ultra-lite AntiX Linux targets obsolete PCs: Chris Preimesberger writes: “MEPIS today said that the RC of a community-built “ultra-lite” derivative of its own Linux distribution is ready for testing. AntiX (pronounced “Antics”) is the personal project of MEPIS community member “anticapitalista,” who wanted a MEPIS version that would work well on old PCs.”

Microsoft & Linux Vendors Trading in Patent Fool’s Gold: Our own Don Parris writes: “Well what do you know? Microsoft seems to be gaining ground with their “patent protection” scheme. But what if they discover they’ve only bought a few bricks of fool’s gold?”.

A guide to using PDFs on GNU/Linux: A really good overview of the different things you can do with PDF’s in Linux by Bruce Byfield.

The Daily Static: Check out User Friendly’s daily cartoon. After speaking with the “Smiling Man”, we thought it would be appropriate to link to User Friendly here at LXer.

Inconvenient truths: PC vs. Mac, Windows vs. Linux, us vs. them, et al.: In our slanted article of the week Steven Rosenberg goes way out of his way be nice to Windows 2000 in comparing it favorably to specific Linux Distros.

Microsoft aims Linux patent FUD at devices: Microsoft signs a deal with LG Electronics that extends LG’s protection onto the embedded devices they make. Now if MS could just make it illegal to run Linux on computer hardware, Hmm.

The New Distro: I saved this article for last because it goes the real heart of the matter when it comes to Microsoft and their money. One of our regular forum members devnet asks: “How much does it cost to buy you? Do you have a price? Can you be paid off?

Read Full Post »

LXer Article

First off my apologies for delay in getting the “LXer Weekly Roundup” to you. Yesterday was my Birthday and I am also out of town visiting family. So between my celebrating and well, my celebrating its been an interesting “morning”. We have some great article selections this week for your reading pleasure.

A challenge to all Linux Users in the World: A recent posting by George Ou about Windows Home Server brought out a lot of responses from the Linux community. I think that Microsoft deserves to get some competition.

Of Insecurity Complexes and Other Great Adventures: Are we seeking “love” in all the wrong places? I don’t think so. I think everyone deserves a chance to take a look at Free and Open Source Software. Before moving on from TUX500, I am asking everyone here and other places to do one thing: don’t ever forget where it all came from!

Linux Distribution Guide: This is a brief 4 page guide to the world of Linux distributions, primarily aimed at individuals who are new to the Linux scene, and who are thinking about taking the plunge and trying Linux for the first time. It also has some gaping holes in the selections provided but it is not bad overall.

Eben Moglen: GPLv3 not about MS and Novell: Joe Barr writes “One of the highlights of my visit to San Diego for the Red Hat Summit was the opportunity to sit down one-on-one with Professor Eben Moglen. From that interview, we have selected six segments on various topics for your viewing pleasure, and will be publishing one each day this week. First up, an explanation of all the things that GPLv3 is about other than the MS/Novell deal.”

Microsoft’s scare tactics protecting profits, says Linux Foundation: The Linux Foundation’s Jim Zemlin says Microsoft’s recent patent claim against Linux and the open source community is a furphy, alleging it is a delaying tactic to merely help protect its profits, according to a column penned last Friday in Business Week.

A little history of Fuddenheim: Hans Bezemer does a great job of using a story where the names are changed but you still know who the characters are in this funny history of “Fuddenheim”.

Sun Microsystems Powers the First Productivity Suite in the Sky: Singapore Airlines, the First Airline to Offer a Productivity Suite while in the air, has chosen Sun Microsystems Star-Office as its software of choice.

Ronin: Logged Off (9 July 1943 – 27 May 2007) – Celebrating the Life of Jim Farnsworth: Jim Farnsworth, known to many as “jimf” or “Ronin”, logged off the IRC channel, #life, Sunday morning in a hospital in Kenosha, Wisconsin. As an active member of the LXer community, we’d like to help our readers celebrate Jim’s impact on all of us.

RPM Project Roadmap: RPM Package Manager (RPM) relaunched under rpm5.org with a roadmap towards RPM 5.0 http://rpm5.org/ — 2007-05-29 — at its 10th anniversary and together with a new roadmap towards version 5.0, the project environment of the popular Unix software packaging tool RPM Package Manager (RPM) was relaunched under the domain rpm5.org by the newly formed RPM project team, further on lead by RPM’s primary developer Jeff Johnson.

Why Novell Must Not Crash and Burn: Glyn Moody thinks that Novell crashing and burning would be very bad for the Open Source Community. Well Glyn, some of us think that it wouldn’t be so bad.

Sabayon’s Fabio Erculiani: “Users first and choice makes the tasty dessert among the distro’s”: Our Senior European Editor Hans Kwint interviews Fabio Erculiani of Sabayon Linux which is currently No.7 on Distrowatch.

You discover something new everyday: An LXer reader “tracyanne” writes about the joy of active desktops in KDE.

Novell, Heal Thy Self: Ken Starks writes: “They are purchasing software so that the software they’ve already bought will work. You have the answer to that problem right in the palm of your hand. Why haven’t you mortgaged the farm to advertise the obvious answer to their problem?”

The dark art of removing the Flash plugin from Firefox in Ubuntu Linux: Steven Rosenberg finds out the it is easy to get the plugin for Flash in Firefox but that getting rid of it is an entirely different story.

Windows – still the only way to go?: In our FUD article of the week the author decides that checking his facts was just a little too much trouble.

Read Full Post »