You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

It's a sad fact that many GPL projects suffer from the fact developers get egotistical, uncaring, or downright lazy and refuse to listen to their users, and say stuff like, "if you want it, learn C++, and add it in yourself, otherwise, piss off".

It's worse than that. Try adding your code even if you know some C/C++.

It's worse than that. Try adding your code even if you know some C/C++.

I know exactly what you mean.

The SNES emulator ZSnes used to be a fairly decent pick amongst emulators in the retro-gaming community, but after several versions passed without the CVS/SVN being updated, we all kinda saw what was going on. Bugs were being ignored in favor of useless candy features, any good changes people wanted to submit or ask about got a heavy handed slap in the face, or the developers wanted money or donations to add certain features that would be private meaning no source code would be published which was a direct violation of the GPL which stated any changed made have to be publicly shown. Some people who asked about features to fix things got banned from their forums, their forum names changed to make fun of them, and then they were made fun of regularly and ridiculed by the developers.

It didn't take long sadly before ZSnes got tossed in the trash even by it's own developers and the source code was relicensed out of GPL to a private license and the SVN/CVS code was dumped and taken offline for private development which has not produced one ounce of new code or updates since it's last incarnation on Sourceforge. A few of the staff that still run the forums "claim" the project is being worked on, but the only proof positive SVN they have, leads to a password protected SVN that is not public.

This is proof positive that forking projects often is the best way to go to achieve goals when developers end up being nothing but ass-hats.

It's a sad fact that many GPL projects suffer from the fact developers get egotistical, uncaring, or downright lazy and refuse to listen to their users, and say stuff like, "if you want it, learn C++, and add it in yourself, otherwise, piss off".

I can't see how that in any way is related to the license, you will find this type of developers anywhere.

Actually, in a way it can be a perfect example of how things get held up not only by licenses, but by developers as well with agendas.

This can happen in any open source project and is not tied to the GPL. But that is the bright side of open source, if you don't like the direction the developers take then fork. Example: Gnome, with several forks.