devnet, Author at Yet Another Linux Blog

What Is Unity Linux?

There’s been a lot of confusion about exactly what Unity Linux is.

I thought I’d talk today a bit about that. I’d like to talk a bit about what Unity uses for it’s ‘guts’. I’d also like to dispel some myths surrounding Unity. Lastly, I’d like to talk briefly about how Unity is doing all it can to further Open Source and Linux by contributing to projects it is involved with. The reason I know so much about this topic is that I’m the webmaster and host for the Unity Linux Project as well as one of the documentation team members. So, let’s take a look first at what Unity Linux is…

What is Unity Linux

Unity Linux is not a conventional distribution of Linux. It’s a core on which developers can build their own distribution of Linux. We’ve set out from the start to provide an excellent minimum graphical environment that gave developers “just enough graphics” for them to create something. The smaller, the better. We elected to go with Openbox because of it’s size and stability. We selected using Mandriva as our base because of the number of packages they provide and the quality of those packages. We pushed lxpanel as a minimal panel because it provides just enough functionality for distro developers to see what they’ve installed after they’ve installed it…it also is familiar to most people whereas Openbox right click menu’s may not be. All in all, our target for the core release is developers. We’re not designing this basic desktop to be used by end users. We’re not trying to win any awards with our awesome minimalistic desktop skills. Why would we do this? To answer this, you have to take a look at our developers.

One of our developers, Kdulcimer, is the lead developer of TinyMe Linux. A few years ago, he created a fantastic minimalistic “remaster” of PCLinuxOS. It was wildly popular and continues to be so today. Kdulcimer was one of the first developers that elected to go with Unity Linux for his core. Our other developers saw what Kdulcimer did with his distro and how small he made the core. They learned from how he did things and applied it to Unity. Thus, Unity has a small base…as evident by both the beta releases. Upcoming release candidates will be very much the same.

Lead developer gettinther does a good job explaining what Unity is:

One of the big issues facing small distros around is that there’s a limitation in the ability of each group to maintain a healthy up-to-date core. Most people prefer to focus on the DE / user interface, working on the look&feel rather the the internals. Those distros end up with stale core which in turn causes numerous “hard-to-find” issues.

Most of the distros with us existed before Unity, like Tinyme, Sam (abandoned project now), Granular, Synergy (formely eeepclos). The idea is to create distros only insofar as “presetting desktops by people who love those desktops”. Rather than having a “one shoe fits all”, we decided to provide a core module and look after maintaining it. Each branch distribution joins the team and has full developer access. For Unity to become a full fledged distro means favoring a DE over others. By limiting the scope to the core product (we maintain the various DE too but leave the DE specific changes to the branches). It makes it a little more difficult to install stuff but it also means that all DE are looked after.

As far as the user is concerned, it means the each branch has their word in the development of the core which ensures that the distro is well supported. It pools the efforts of each distro who would otherwise be on their own so means a large development team and as such better packages.

So Unity Linux is a base on which to build. A foundation for “remasters” to build from. But what is a remaster? What technologies does Unity use? Let’s take a look at the internals of Unity next.

Unity Linux Internals aka Guts

When we initially set out to not only have a small graphical base but also to wrap around the LiveCD project. For those of you who don’t know what LiveCD is..you can visit the old berlios.de project page:

The project features automatic hardware detection and setup, and utilises compression technology to build a LiveCD from a partition much larger than would typically fit on a CD. (Up to 2GB for a normal 650MB CD.) When booting from this LiveCD, the data is transparently decompressed as needed. LiveCD now supports udev.

Currently, Mandrakelinux and PCLinuxOS are supported as a host for creation of the LiveCD, i.e. we are only able to create LiveCD’s from a MDK or PCLinuxOS install. The LiveCD scripts are still beta, and bugs are being eliminated. Your help and feedback are appreciated!

The set of scripts allows a person to make a liveCD copy out of their desktop for backup purposes or as a standalone linux distribution. When you create that new ISO or backup ISO, you have ‘remastered’ the master copy. So the livecd scripts are really just a set of tools that allows a user to create something new or backup their existing desktop as a live CD.

The project at berlios was taken over by Didouph as lead developer just before Unity was formed. There hadn’t been much work after Tom Kelly left the project quite a long time ago, but Didouph was optimistic. When he joined Team Unity, he placed LiveCD development on the back burner and worked hard with the graphics team on logo development.

Later, it became apparent that in order to keep creating a great distribution that could remaster itself, we needed to make improvements to the code of LiveCD. First off, it needed 64bit support. Secondly, it needed better detection than what it had. Third, it needed to have internationalization work done. Fourth, it needed to support higher kernel versions than what it did. All those things have been accomplished with internationalization still being worked on.

When we initially took over the ‘modernization’ of LiveCD we didn’t all flock to berlios to do so. Work instead began when we gave a small sliver of our own SVN over to LiveCD. It made sense geographically for our developers to have the ability to commit code in the same place instead of at a third party (berlios); the reason being, we needed many commits fast and didn’t want to wait…we were ready to move forward with it immediately. We snagged the GPL’d LiveCD code and located it on our SVN.

Since Didouph was the maintainer of LiveCD, we felt it only natural that Unity would lend a hand to him and his project by taking over development. An entire team working on LiveCD would mean greater output and more advancement. Thus, Unity maintaining the LiveCD project was born. Anyone is welcome to take the code and use it how they seem fit. We’re working on getting LiveCD it’s own proper SVN or Git repository at a public site away from Unity Linux…if you’d like access (read only) to LiveCD SVN, drop Unity Linux a line via their contact page.

Common Myths Surrounding Unity Linux

Heard any good ones lately? If I don’t cover the ones you’ve heard here, please leave me a comment and I’ll address yours specifically.

Myth #1 – Unity Linux is just PCLinuxOS rebranded

Most of the developers of Unity Linux were contributors to PCLinuxOS during the time that Texstar had stepped away. As contributors, they were not part of the developer team. They had limited access to the core, iner-workings of PCLinuxOS. How do I know? I was a developer…the main web developer…for PCLinuxOS and I monitored all mailing lists, all websites, and even was chief of MyPCLinuxOS.com. There were very few people on the development team of PCLinuxOS that are now part of Unity Linux…because the PCLinuxOS development team was kept small.

When Unity Linux initially was started, the contributors and developers that were involved grabbed a ‘snapshot’ of the PCLinuxOS repositories and began working on bringing packages to updated versions. They quickly ran into trouble because PCLinuxOS used such an outdated toolchain that many new packages wouldn’t compile with it.

After some discussion, developers abandoned PCLinuxOS packages and instead worked with Mandriva packages. This allowed Unity to move forward sans old toolchain and outdated core. Now most of this stuff doesn’t matter to the end user…they just want a stable environment. But the Unity Linux developers wanted to push forward with the latest kernels, the latest rpm version, and the latest smart package manager versions. Doing so required massive leaps forward even from Mandriva.

As you can see, while Unity Linux originally started with a PCLinuxOS fork, they abandoned that fork and rebased on Mandriva. They now stay inline with Mandriva development. If you have Mandriva and Unity Linux questions, please stop into the Unity Linux chat channel on Freenode: #unitylinux and ask proyvind questions…as he is the Mandriva Linux representative that works with Unity Linux 🙂

Myth #2 – Unity Linux Stole mklivecd aka livecd from PCLinuxOS

This is a pretty funny one and I’ve seen quite a few references to ‘stealing’ GPL code. First things first: You cannot ‘steal’ GPL code. It just can’t be done. Secondly, the LiveCD project was stagnant and had a SINGLE developer working on it. That developer joined Unity Linux and all 25+ developers there decided to help him make some progress on it. In the meantime, they took the initiative to make improvements. For example, they gave it 64bit compatibility. They gave it have better detection. They took the code and gave it better international language support. All those things are made available for FREE to any distribution wanting to download a snapshot from SVN.

Now, if anyone has a claim to LiveCD as ‘theirs’ it would be Jaco Greefe who was the principal on the project LONG before any distributions other than Mandrake aka Mandriva even worked with it. Texstar grabbed what Jaco’s project mklivecd and used it to create the original PCLinuxOS 2003 release. This release was based on Mandrake 9.2 at the time and a few other Mandrake developers began to debug the script through the creation of PCLinuxOS. Mandrake was a trademarked name, so Texstar named it PCLinuxOS.

As you can see, if any one distribution has claim to mklivecd, it would be Mandrake aka Mandriva which was where the script creators came from. It’s also where the script was first made useable. However, claim that Texstar made it into a nice package with PCLinuxOS…that is totally true. What we’re doing now by developing it is making sure it continues to progress into the future with 64bit support and even when udev is dropped from Linux…no matter what, we’ll make sure it works…and hopefully it will work for more than just Mandriva derived distributions.

There have been many attempts by Unity Linux developers to get other distributions that use mklivecd involved with the development of it. That invitation is always open to any and all distributions that use it.

Myth #3 – Unity Linux wants to steal away users from other distributions of Linux

The main reason this isn’t true is that Unity Linux targets DEVELOPERS. We don’t target end users. If end users like Unity, GREAT! If not, we don’t worry about it. Unity Linux has derivative distributions called “branches” that work to target the end user. Unity Linux itself is targeted squarely at distribution developers and advanced users who want to be able to use the mklivecd scripts.

Myth #4 – Unity Linux DOESN’T use PCLinuxOS at all in development

This is half true. We don’t ‘use’ PCLinuxOS to create things…we use it as a mirror synch. Paul Grinberg, a developer on the team, has a PCLinuxOS box that he doesn’t use. During the initial setup of Unity Linux, we based things on PCLinuxOS before purging and switching to Mandriva. Since the developer mirror server (referred to on the mailing lists as the dev server) still ran PCLinuxOS and Unity Linux didn’t have a release yet, we saw no reason to change it.

As Unity Linux still has no stable release as of March 29, 2010, that developer mirror server still runs PCLinuxOS and pushes uploaded packages developed on a Unity Linux server to various mirrors for propagation.

In other words, the PCLinuxOS server Unity Linux uses is just a web server. It will be replaced with Unity Linux when 2010 is released. Until then, taking the time to wipe it out and repopulate it would throw a kink in the flow of package development so developers have put this ‘to-do’ item as something to be accomplished after stable release.

Unity Linux and Open Source

Unity Linux does a great job of contributing to projects upstream. As an example, David Smid, a Unity Linux developer, is also a Smart Package Manager (SPM) developer. This allows Unity the ability to test the latest and greatest SPM and get things quickly patched/fixed/redesigned. Other projects such as mklivecd are developed openly by Unity Linux and contributors are welcome. Unity Linux contributes bug finds to Mandriva through use of the Mandriva Cooker repository. Unity Linux developer Paul Grinberg contributed Google Map integration for MirrorMon, which you can view on our Mirror Status Page, back upstream to the creator of MirrorMon. Unity Linux also contributes upstream to rpm5.org.

Unity Linux also has a working partnership with Yoper Linux. Why? Because Yoper Linux uses many of the same core technologies (Smart, rpm5) that Unity Linux uses and because the lead developer, Tobias Gerschner, is an all around great guy :).

You can see everything that Unity Linux works on by visiting our repository: http://dev.unity-linux.org/projects/unitylinux/repository

Development is done in the open, not behind closed doors: http://groups.google.com/group/ul-developers

Unity Linux strives with an almost rabid will to keep everything in the open for users and branch developers so that they are not left wondering what’s going on with their distribution. The Developers continue to try and engage other distributions to work with them and will continue to do so in the future.

Closing Thoughts

Unity Linux doesn’t target the same users as your average distribution of Linux…they’re after the more savvy users out there. The ones that want to create something and make something from the core image. Users that like to tinker and mess and break things.

Unity got off to a rough start with much FUD slinging and accusations. Hopefully, the actions you see that Unity has taken to keep it’s project open will show the intent of the developers…to make a great core on which others can branch from all the while remaining open and free for everyone.

Do you…uh…Use Linux?

Do You Use Linux? — Use Whatever You Want

I ran across the flash video above (note: I’m not taking content and embedding it here…you’ll need to click on the image to be taken to the author’s site) a while back and have never posted a link to it. It’s pretty funny and if you look around on ubergeek’s site, you’ll find a couple of other interesting things like the awesome flash game “Penguin Blood Ninja Fiasco” which I think is just genius. So give this a look-see…you won’t be sorry. Guaranteed to brighten even the darkest open source supporter’s day.

Host Your Own Domain, Website and Webserver

This post was originally published on 13 July, 2006. This version has been updated.

I have a problem with facebook, myspace, and other social networking websites out there. The problem is when I upload my data to their webservers….I don’t own it anymore. They do. And they can do whatever they want with it once it is there.

With this in mind, I’d rather setup my own twitter using Status.net or my own digg using Pligg. But I’d do it on MY OWN SERVER. That way, any content I upload is MINE. It doesn’t reside on some server in California or DC and get recycled to advertisements.

I like to control my own stuff. I don’t like to be cut out of the loop. If you’re like me, then you’ll want to host your own domain, website and webserver so that your friends/family/shrink can quickly and easily connect up to see new photos, find out the latest family developments, and understand why you wear tinfoil hats every Thursday after 4pm.

Normally, to host your own webpage you would need to spend around 7 bucks to purchase a domain. Next you would need a hosting plan that usually runs around 3-15 dollars per month to serve up your web pages.

What most don’t realize is that you can skip these steps all together…you don’t need to get dedicated hosting (this blog is hosted on dedicated hosting…but started out in my apartment!) to serve pages up to your friends and family. You absolutely do not need to get domain name services through a provider. You can even host your own webserver using a dialup connection (that’s right…I said dialup) although. I don’t recommend it (but I’ve done it using 56.6kbps).

Why would you want to do this? The answer might be to stay connected to friends and family…perhaps install a gallery so that your grandparents can see pics of your new dog/car/tinfoil hat. Sure, you could waste my time with MyWaste..er..space and facebook and be barraged daily by advertisers and solicitors and be inundated with the minutiae of what all your friends had to eat for the day …or you could roll your own web host, install a gallery or website, and provide media to your friends and family without costing yourself a dime. That’s right, NO COST (except time spent getting it running). Just remember, your website might not survive a digging or slashdotting if you run it yourself. Keep that in mind 🙂 So without more chatter, let’s get to the meat and potatoes of things:

Meat and Potatoes

If you have Cable or DSL at home (not a business account) you have something called a dynamic connection. Dynamic connection means that it can change every once in a while. DSL and cable ISP’s purchase blocks of IP Addresses in the dynamic range so that they can keep consumers separate from businesses. It’s also easier for them to manage dynamic pools of people than to have to remember static connections that don’t change for everyone.

Because of this problem…an ever changing connection for you at home…web servers and websites do not do very well. The reason for this is because when you visit a website on a dynamic connection one day, it might be different the next day. In order for visitors of a website to find you each and every single time, you need a “domain” or web name that points back to the address (IP Address) your internet service provider changes on a whim. You’ll also need an update service to update your website each time your ISP decides to change things on you.

Believe it or not, there are free services out there to do that for you. You just have to be willing to do a little extra work in the beginning to set things up. You can also do this without spending 20-40 bucks a month on DNS service.

I’ll divide this up into 2 sections. The first will deal with Linux hosting. The second, Windows hosting. This is only something that I’ve found easy to do and the price is just right (it’s free). The only thing that I recommend is a dedicated internet connection (cable, DSL) but even this is not necessary as dialup can be used. I recommend that you use the Linux way of doing things since it is more secure and doesn’t require a restart every time you patch it.

*note: I’m assuming that you aren’t behind a firewall/proxy of any kind and that your ISP doesn’t block port 80 traffic. If your ISP blocks port 80, see the appendix at the end of this article.

LINUX

No matter what version of Linux you run, chances are that you’ll be able to install the apache webserver. This is good news as over half the websites of the world are run by apache. I’m not going to address the specifics of how to set up your apache…only how to get it a fixed address without buying a domain. So, you have your html or php pages located into your webservers public directory…good…whatever application you have is installed on your server. Now, how to resolve your IP…lets say it is…25.24.4.166 (for our example) and you want it to have a host.name.com to bind to. Easy to resolve. Go to http://www.no-ip.com/index.ph p and sign up. You can get a site from noip that is like yourname.theirdomain.com/.net/.info. They have cool names like sytes.net and servebeer.org…even workisboring.com. Other services like dyndns.org also exist and provide the free service as well.

You’ll be able to choose your own top level name…for instance, Ithink.dnsiskinky.com could be your new domain name. Next download a client from the download tab: https://www.no-ip.com/downloads.php

The linux client is a tar.gz source and is simple to install. Follow the instructions when installing. You may have to install compilation tools (devel packages like GCC) to install the client. You now are the proud owner of yoursite.theirsite.com and your IP will ALWAYS update (as long as noip.com is up) each time you log on/sign on/beam up or whatever it is you do.

How does this help you? Well, if you’re like me, you have a dynamic IP address. If you connect to the internet via cable, dialup, or dsl…you also have a dynamic IP address. Dynamic means that it will change from time to time without warning. So by binding yoursite.theirsite.com to your IP address…you don’t ever have to worry about what IP address you have anymore. Instead, you’ll always be able to connect using yoursite.theirsite.com. You can host a webserver using Apache and a virtual host in this style as well (look for another how-to on this subject later) so that everyone can visit a shiny website at yoursite.theirsite.com.

Now you can give your friends/family/dog walker/mailman the address to your new webserver…maybe it’s Ithink.dnsiskinky.com like we used in the example above. Now when they visit that address in their web browser, your application or web page displays for them. You also get bragging rights at being the most technical friend/relative/dog walker client/household that everyone knows. Now let’s cover Windows.

WINDOWS

First you need a free and clear webserver since one is not included by default with windows. You can download Apache for this as well OR try the Abyss Webserver.

Interestingly enough, Abyss is also free! I ran it while my linux machine was being worked on (bad hard disk…it was a Quantum 200MB drive from 1913…had to upgrade) and it worked just great off of Windows XP. Download that puppy and install it. Make sure you read all of the documentation and familiarize yourself with how Abyss does business.

The next step…getting a hostname… is even easier than the linux method because you don’t have to manually install the noip client…they have a windows installer. Go to http://www.no-ip.com/index.php and sign up. Choose the domain name you would like (see above examples in Linux section). Next, download the noip client from the download tab: https://www.no-ip.com/downloads.php but this time choose the windows client. From there, you’ll be able to install this with a simple double click. Fill in all of your information (pretty self explanatory) and make sure that it will run with each time you sign on. You’re set! Your IP will now resolve to the yourchoice.theirhostname.com

CONCLUSION

You don’t have to spend a dime to keep a domain bound to your IP. This is perfect for the home user who just wants a gallery or homepage. It’s even good for someone who has a weblog or enthusiast site. It’s good for someone who wants to be able to find their files and music…setup Jinzora and stream all your music library to yourself anywhere you are! Setup Amahi and have access to all the goodness it brings.

Please remember, this wouldn’t be good for a business to have. You will probably violate your ISP’s terms and conditions for using their connection if you tried to run a business this way.

It’s always good form to put a link of the stuff you are using on your website to direct traffic back to your software provider. When I used noip, I included a noip link on my main page and also an abyss webserver icon as well. It’s just good form and some companies/software providers necessitate the use of their logo or a link on sites that use their software/code. Just be a nice person and give a link back to them. Good luck! Have fun!

Also, please note that having hosted my own webserver for quite some time (circa 2001) I’ve found Linux and Apache as a combination to be more secure, faster, and more stable than any webserver I’ve hosted on the Windows Platform. I included information on Windows mainly to introduce you to the concept of free and open source software. If you thought getting a webserver for free was great, think about getting a whole operating system! Give it a try, you don’t even have to install it (use a Live CD).

APPENDIX

If your ISP blocks port 80 traffic, your webserver won’t work. Before deciding that your ISP is blocking however, make sure your firewall has the appropriate rules to allow incoming traffic. You can do a quick add to IPTABLES in the following manner:

iptables -A INPUT -p tcp --dport 80 -j ACCEPT

iptables -A INPUT -j DROP

If you’ve opened up the appropriate ports and things still don’t work, it will be safe to say that you’ve determined the ISP is blocking port 80. How you can get around this conundrum is to switch the listening port on the webserver to a different one and redirect traffic there.

See how to do this for IIS Webservers
See how to do this for Apache Webservers (normally in /etc/apache2/httpd.conf but your distro may vary.)
See how to do this for Abyss Webservers

If you still have problems, drop me a line in the comments section. I may not be able to answer all questions but I can most likely get you to a person/place/thing that can. Have fun and thanks for reading!

Unity 2010 Beta 2 Impressions

As noted previously, I’ve been pretty hard pressed lately in my secular job due to migrations and other fun activities happening throughout the past few months. I did however, get the chance to download Unity 2010 Beta 2 and give it a go. I had some problems when booting because I was brought to a blank black screen with a mouse pointer no matter what options I passed during boot. To get by this, I had to follow some IRC advice on #unitylinux (thanks wile_netbook!) and change to a second tty, kill the Xserver and GDM, followed by executing do-vesa. It’s hard to try to do it quickly though because GDM will try and restart X and switch init levels on you back to a graphical one. To get by this, you’ll need to do the following:

Drop into a different tty. Login as root…if you’re on the liveCD, the password is root. Execute:

ps aux | more

Make note of the PID for X and GDM. Write them down…replace the terms below with your PID numbers:

kill -9 PID_for_X && kill -9 PID_for_GDM && do-vesa

You now should see something other than black screen with mouse cursor. I’m not sure how many systems this affects…but I know my Dell Latitude D630 laptop took it on the chin for this one. Not a huge problem for a Beta…I mean, a distro can’t be all things to everyone.

Overall though, Unity 2010 Beta 2 is much more solid than Beta 1 was for me after getting by the initial X problem. Everything works as it should as far as sound, Internet, and wireless are concerned. I quickly removed PCmanFM and replaced it with Thunar, my file manager of choice. I removed LXPanel and installed Tint2. Installed Nitrogen to manage wallpaper. Installed Parcellite to give me a clipboard, Installed volwheel to give me a volume applet to control volume. Installed Pragha to give myself a great music player. Installed Irssi to allow me to get my IRC fix and put pidgin in play to IM. I had a usable, customized desktop within about an hour. And it’s been really solid…just as solid as my Arch Openbox desktop I run at home…which makes me feel good about this Beta.

So what else have I been working on? I’ve been working on a large (VERY large) tutorial on file permissions and making use of groups for file/directory access to add to the tutorials section of YALB. This thing has been in work since last year and I’m attempting to finish it up before the months end to give a good representation of what file permissions in Linux are for and how they work with users and groups. I’m also going to write up a tutorial on how to customize Unity 2010 Beta 2 into a lightweight Openbox desktop. So, some good updates hovering on the horizon. Stay tuned 😀

Status Update for Devnet

For those of you who follow me here at Yet Another Linux Blog you might be wondering where I went the last month. I assure you I’m still here and I still use Linux every single day. I’m currently running both Arch Linux (32bit) and Unity Linux (64bit) on my main computer.

I’ve been working pretty hard through the holidays at my full time job where I am a server administrator for a medium sized hospital in the U.S. Recently (in December), I moved 2000+ users from Exchange 2003 to Exchange 2007. We considered farming out our Exchange environment to the cloud or perhaps going with Microsoft Exchange Hosting services but in the end, upper management decided they’d rather underpay someone to work exceedingly long hours with minimal training on a system not built by him. So, that’s why I’ve been pretty inactive as of late. As you can imagine working with Microsoft technologies…I always have something to fix and things are always unstable.

I know that some of you might be saying “why not use linux based exchange alternatives in your enterprise?” and I’d say, why indeed. But I inherited this beast and it’s been Exchange since Exchange came out. Not only that, but the primary application for all departments (ERM app) runs completely on Windows and plugs into Exchange and nothing else. Talk about vendor lock in eh? Well, it’s a job.

I used to work with Linux when I worked for rPath but parted ways with them about a year and a half ago when I had to move away to help out after a death in the family. I was very sad to leave but am very happy with the large pay increase that came with my current position. However, migrations do take their toll…lots of hours worked and frustrations vented. Now that I’m over the hump, I’ll be able to get back into a normal swing of things.

For those of you who might be Exchange administrators in your day to day work, I’ve begun blogging about my experiences and setup a community to share tips, tricks, powershell commandlets, and a place to talk shop. I figure if I have to work with closed source at least I can open source some help. Find my Exchange blog at http://teknologist.net

Thanks for hanging in there everyone, and sorry for the inactivity. Now that I’ve hit 6+ years blogging (in December) here I have even more incentive to continue sharing great Linux help with everyone. I’ve got some good tips directly in the pipeline and here’s to a great 2010!

Zealots and Narcissism

Many times in my journeys of distribution hopping, I’ve run across rabid fans and communities ^[1]

I’ve written a guide for new users on how to understand the vitrol that rabid zealots spew in Linux communities ^[2]

Those problems are all very easy to see…but these articles deal with only the tangible problems in these areas. What are the reasons these problems exist? Is it because of one or two individuals? Is it mob mentality? Are people just waking up on the wrong side of the bed? I don’t think these reasons get down to the core of what the real problem is…the hidden problem…of zealots in the Linux community.

The Hidden Problem

The hidden problem is Narcissism…people think that what they have to say about a given subject makes the most sense and is 100% correct (or at least more correct than others’ POV) and it’s one that is hard for people to talk about…because anyone that writes or blogs has to be a little bit narcissistic. People don’t like talking about problems they’re guilty of. I know I am guilty of it…and I’m still going to talk about it.

With social networking riding a tidal wave right now, the era of the narcissist moves on, unhindered, on the interwebs. Subscribe to my twitter feed…what I have to says in 140 characters or less is a MUST READ! My facebook page will keep you updated on EVERY little thing I decide to post unless you edit me out of your news feed. Sites cater to the egocentric tendencies of anyone plugged in. So what happens when you get a bunch of narcissists together sharing a common goal? “My distribution is THE BEST out there and no other point of view matters!” That’s right, you get zealotry in the purest form.

This has slowly begun leaking into Linux communities during the past few years as Linux is tried out by more and more people and becomes more available to people who aren’t technologically advanced. Bottom line is, more people are trying Linux now than ever before. This makes the user pool larger and more diverse. Where there are more people though, there are more narcissists…and birds of a feather flock together.

Take narcissism with a twist of mob mentality and the powder keg in Linux communities is set to blow. The zealots seethe and team about in forums, IRC, and on blogs across the internet looking for a place to show how right they are and how wrong the person posting information is.

Oh, I admit it…I have a narcissist streak in me…I want people to read this blog. I want people to follow me on twitter. I want people to pay attention to what I say…it’s part of being a blogger…but I don’t think that my distribution of choice is any better than yours. In fact, I know it’s not. Just like my car isn’t any better than the one you drive and my clothes are so last year and aren’t as good as yours. I offset my narcissism with realism…I understand that what I think isn’t the only point of view out there…I don’t think I’m 100% right all the time.

I also don’t go out on the web and try to find others who think my view is the best view and then try to push my egocentric viewpoint to others. I don’t create a community of zombie thinkers who all believe my viewpoint is the best out there. I’m not forming any mobs for my mentality. I’m not flocking together with birds of a feather. I’m a part time ego-narcissist I guess.

The first step is admitting that you have a problem. The second step is having some good old fashioned manners, respect for others, and above all…tolerance and realism.

Solution to the Problem

When you’re standing in line at a bank, would you cut in front of someone in the line? Most likely you wouldn’t. Personal conflict is something we as humans avoid most of the time. So, why is it when you’re driving you don’t mind cutting someone off and do it regularly? It’s because the personal aspect of that motion has been replaced into an impersonal one…the car becomes a protection from that personal conflict that would happen if you had done the same thing in a bank line.

To fix the problem this presents on the web and in Linux communities, think about others (not yourself) and in doing so, become less narcissistic. Apply this thinking to commenting and blogging and facebooking and tweeting. Imagine that you are face to face with people saying the things you’re typing. If you wouldn’t say things like that in a face to face situation, don’t say them. Remember that tolerance of other viewpoints makes you a better person…AND smarter. How? Albert Einstein is largely considered one of the smartest humans to ever walk the earth. He often gathered with other intelligent people to debate and discuss various topics that interested him. In doing so, he caused those he debated with “to sharpen and refine their understanding of the philosophical and scientific implications of their own theory.” Remember that everyone does NOT have to share your viewpoint…what works for you may not work for them.

Lastly, no one cares if you sat down in your office or are eating a peanut butter sandwich. We subscribe to feeds and twitter accounts for meat and potatoes posts…not 1 liners that tell us you’re in the bathroom of a bakery on 96th street. So, you zealots out there…you know who you are…take this opportunity to reflect on yourself (your favorite subject) and try to replace your narcissism with realism, tolerance, and good old fashioned manners.

And no I don’t think any zealots will be converted by this post…it’s more of a rant than anything else…and rants are one of the reasons why I have a blog 🙂 Well that and because what I say is more important than anyone else and my viewpoint is 100% correct 100% of the time of course. 😉