Getting a license on this stuff

As a fan of huge digital rights activists like Cory Doctorow and Thomas Gideon I figured I would finally add my CC license to my blog content.   So, following in the footsteps of giants you will see the license badge at the end of each new blog post moving forward.

Keep watching.

--
CafeNinja


This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License.

Podcast Review: Linux Cranks

Right. In case the name was confusing, this is the Linux Cranks (and I do mean Cranks!!) Oggcast. No joke. And if you ask for the mp3 feed they might just DDoS you where you sit. The team of guys who have a very short talking points list manage to ramble for over an hour using curse words and inappropriate metaphors to explain the view of the world from pure geek eyes.

These guys will not accept "I don't want to use the command line." as an excuse to not hardwire your home automation and manage remote switches using only an ssh connection. Pretty hard core and geeky talk but when stretched out over an hour or two it sounds more like the weekly card game where everyone goes to smoke cigars and hide from the wives.

The entire crew has a very human sense of humour. There is no political correctness and they make no apologies for seeing the world over their keyboard. I really like listening to the guys and hanging out in IRC with them during the week even when they aren't doing the show. Actually, after listening to these guys for a few weeks, they start to feel like old friends and are just as approachable in IRC as they sound like on the show. These are in fact, my new "buds" and I hang out more with them in chat than I do with real people in real life.

The show technically comes out every other week as they alternate with TiT Radio, but it is also pretty much the same guys talking about the same stuff with a slightly different show format but about the same length. You can find all the info on the sister show at the Linux Cranks website.

--
CafeNinja

P.S. shout out to: Peter64, threethirty, artv61, snkmchnb, mesoDann, pegwole, jlindsay, Xoke & Mrs. Xoke, Klaatu, Azimuth. <--- not in any particular order.

(Update)
P.S.S - and a giant "atta-boy" for monsterb

One Mutt to rule them all.

This will be the explanation of how I (known mutt fan) have set up just a few small tools in order to have access to multiple email accounts at the same time using mutt. I am still sure that I process a great deal more email more efficiently than my peers because I am reducing my Internet world to the lowest common denominator -- text.

With just the rendering time enhancement of html/rtf formatted emails to text I have a 25% better visualization time of email. With the use of powerful text editors (in my case vim) my reply time is also quicker. I have yet to see an email interface that is as speedy. I have to say that the web interface on gmail is pretty snappy and offers threaded views inline thus speeding up the reading of conversations. I still find it falls short of the raw speed offered by mutt.

With this in mind, I even apply this to my personal email. One of the challenges that my counterparts complain to me about is that since their work day is consumed with email that they neither have time during working hours to look after their personal email accounts nor do they have the enthusiasm to check their personal during their private time. I find that with my ease of use, that I can apply all the attention needed to both either in the office or out.

First, I made a folder that will hold all of my mutt configuration files. Everything from my alias file (address book) to my mutt color file. All of the "dot" files and the individual muttrc files will go into one folder. This is not so terribly important for the function, but is important later as I integrate a backup/restore plan.

Second, multiple muttrc files should be prepared, one for each account. I will confess that in an effort to make my email OS ambiguous and accessible I am using IMAP with accounts that also offer a web interface. This is key to my explanation since it doesn't require the work of setting up fetchmail, or hassle with odd protocols (i.e. Exchange). I won't be going into the details of the options of the muttrc, if you have looked at them, there are a great many. But for sure a single file for a single account is important. In this manner, we can avoid mis-configuration of the profiles options and we don't end up with a config file that is 1 mb in size.

Lastly the commands. The command, being launched from the same folder as the config file should read "mutt -F muttrc-file-for-this-email". My little hack that makes this quite manageable is that I have set multiple alias's in my .bashrc file that make simple ways to remember the accounts. Let me give you examples. I have set in my .bashrc the following:

alias email-cafeninja="cd ~/mutt-conf && mutt -F muttrc-gmail-cafeninja"

This single line changes directory to the folder where all of my muttrc files are, and then executes mutt using the correctly named file. While the alias is auto completed using tab from the command line.

The last hack I did for this is a simple backup and restore script that makes a tarball of the entire folder and places that into my dropbox folder. The restore script copies the tarball to the home directory and extracts it overwriting the previous files. These two shell scripts I have placed in my ~/bin folder which is also in my path so that these scripts are also auto completed from the command line. With absolute path referenced, it does not matter where in the filesystem I am when I execute the email alias or the backup/restore process. Just to be sure it would be available, I placed a copy of the backup and restore script into the mutt-conf folder to be included in the mutt tarball that would sync on a new system. Of course, it would then need to be placed in the ~/bin folder on those systems as well for future use.

Here is my backup script:

#!/bin/bash

## Go home

cd ~

## make tar of ~/mutt-conf

tar pzcf ~/Dropbox/mutt-conf.tar.gz mutt-conf

Here is my restore script:

#!/bin/bash

## Go home

cd ~

## get tar and move to home dir

cp ~/Dropbox/mutt-conf.tar.gz .

## unzip tar

tar zxf mutt-conf.tar.gz

## remove copied tar once done

rm mutt-conf.tar.gz

I hope this might help anyone who is working with multiple email accounts on multiple systems who thought it might be difficult to get it all working. I'm sure there are more complex solutions available, I built mine with the idea that each email account was siloed and would not corrupt other email account setting should anything happen to a single file.

--

CafeNinja

Oops, windows again

Another reason, why I don't prefer windows. I had the simple task of adding a mouse to the laptop I was using. This particular laptop did not come with a function key that would disable the on-board mouse. after adding the external mouse, it was impossible in the operating system to disable the mouse easily from the mouse control panel.

This action, to disable the on-board mouse is a simple click on the mouse control panel in Ubuntu and one that I have used for years. My newest laptop offered the chance to dual boot with a legit copy of windows and enjoy both worlds on this newest device. As the activity of dual booting was proving to be it's own troublesome activity (Asus EEE PC 901 with two SSD's 1x4gb and 1x8gb) I have renewed frustration with windows again. I'm thinking I just might migrate this new netbook completely to Linux and just not give a care about windows...again!

Can it be that after all of this time even XP stinks this much. This netbook cannot support (nor would I want) vista. I could probably hold out for windows 7, however, my disdain for windows has yet again put the insistent idea of "why not just use Linux and be happy in my mind again.

It is such a simple thing, the mouse issue, you know on any laptop it makes sense to be able to disable the touchpad, but when the manufacturer of the laptop does not have the foresight to include a function button for this, I feel it is the operating system who should naturally pick up the gap.

--

CafeNinja

Software Freedom: Sentiment or Cause

So, I just wanted to take a moment to talk about all the issues going on recently in the Open Source community. Warning: this is a rant. If you don't want to read it please skip to the next article in your rss reader, or navigate away now. Last warning.

The most recent stir is Mono based applications, but previous discussions have hovered around binary blobs in Linux distributions, proprietary drivers, and pure free vs. quasi pure free vs. free-as-in-price.

I do have some opinions about this, but no firm convictions. I mean to say that I am moderately educated on both sides of the discussion but that the discussion itself has recently turned into a "pitch fork and torch" kind of affair. I am far more hurt by the conduct from groups talking about these points than the points themselves.

I've been a computer user for many years. Part of my interest in computers as a hobby was the hacking and tweaking to get things just working. It is surprising to me that the tone of voice used by these people is borderline zealot. It feels like most people are missing the forest for the trees because they are hugging them too tight. Let's remember that we can roll with this one of two ways. We ostracize the average user completely or we do what needs to be done to let most folks into the fold if they so choose.

I can honestly say that I don't have the resources to install asterisk boxes on two continents so that my mother and I may speak using home brew voice services. We can both, with relative ease install and use skype. I know that might disappoint a few out there, but if a binary blob in my distro prevents my computer from being an overheated paperweight, then I'll use it. If I rely on an application that is available in the repos of my distro, then I really don't monitor what language the thing is written in, so long as it works when I launch it.

We all have known people in our Linux lifetimes who would be happy to try and switch and give Linux the "old college try", but when they do so much of their hardware was unsupported that they could not justify the loss in functionality for the moral choice of open source software. Why should we condemn our own for something of less importance at the end of the day. I mean really, curse words are the correct way to respond to my choice of note taking application because some programmer used a different language? I know there are issues with this licensing and that, and even further discussions could be had with other programming languages (not mono) if you really wanted to make that such a point.

I would like to make a formal request to the Linux community that if you have an opinion about programming languages or issues with certain licenses, please verbalize your opinion. You can even use words with more than two syllables. But don't make others in the community out to be a villain, or the embodyment of evil just because they don't agree with you. I like to think that we are one of the largest brain trusts on the planet, and it is more than a little disappointing when the best word you use in a debate is "sucks".

I hate to sound like everyone's mother, but grow up. You may be passionate about your cause, but be respectful of those who do not share your view. I think there are many good conversations to be had, as long as they are honorable and mature. In my heart of hearts I feel like we (as a community) come up with the best solutions when we try to solve a problem. But we are also the best at creating problems that aren't really that bad.

Now take a time out, and go sit in the corner while I cool off.

--
CafeNinja

USB Live install vs. Active Directory

Linux and OSS software is all about scratching itches with creative thinking and slightly different applications of previously created tools. Recent changes in my work space have me considering some creative technology options to separate us from closed source software tools.

Recently my office was severed from the corporate M$ domain server. With it we had some issues that the multiple users on multiple computers. As each user signed on again to another computer they had to create their local account on each machine. Each user had to find their own way to trying to synchronize their application settings and user data across all the machines and accounts. Some individuals were more creative than others, but it was a problem that the computer users should not have had to overcome by themselves.

The roamng profile was the service at the core of this that I feel I need to replace. In addition we are expanding our office to include another that is geographically diverse. As I was first looking at this I was thinking some sort of server deployment using OSS tools might be the solution that I needed. At first I looked at OpenLDAP + NFS mounted shares to create a /home/user that could be mounted on any machine they signed on and then the application settings and data would follow the user. Then I took a look at LTPS (thin client) which for what we do in my office would require high bandwidth connections from user to server.

Then I had a thought, what if the user could have a usb key and then just boot any of the machines available into a live linux distro with persistance. This would offer the user the ability for each to custom add software that they found useful, while keeping all of their application settings like email and bookmarks. Logistically, this seems to make sense also since then at any time you could do a backup image of the usb key that could be restored and with the known sizes of the space on the usb key could make the backup storage space a managable activity.

I have been on a quest for a process that would produce for me a usb key that would have a "live" version of a linux distro (to support the widest range of hardware). I also need to try and pay attention to security since if this key were to get lost, the important data needs to be in a mode/filesystem that protects it to the point that any theif would be faced only with the option to format the key to use it.

I plan on making additional posts on this as I try and try again. I have tried a few tools and how-to guides on how to produce the effects that I desire with no success. I will be back to detail how that goes and to post what is my success story when done.

--
CafeNinja

Podcast Review: The Command Line

The Command Line podcast is one of the most well rounded technology shows I've listened to. It is very well produced, arrives on time and is a very mature show. I have to say that my choice of "mature" is not by accident, let me explain.

This show concerns itself with complex issues such as copyright, tech topics including programing code while still taking some time to address the human side. With reflective episodes that take a step back from programming to look at the programmer himself, this is the first podcast that I have listened to that insists on remembering the humans who participate in the technology of today.

That does not mean that the tech doesn't get covered. The host Thomas Gideon a.k.a cmdln covers tech topics from code writing to the sciences. With a very grown up honest look at not just the need or desire of the tech but also the moral implications. Most impressive is that cmdln seems to be the only podcaster that I've heard who is not afraid to look at the analog version of things with respect enought to consider them relevant. He is one of the first ones who has taught me that I should measure the quality of analog vs. digital before getting into further discussion of which digital is best.

With episodes coming out normally 2 during a week with a duration of about 30 min but some special episodes a bit longer, this is a very sensible clear voice in the noise that is tech coverage.

The Command Line podcast also adds the interjection which is that of a insightful husband, father, person and programmer.

I highly recommend this podcast to your podcatching program if you feel like the news you are receiving could be a comedy show, this should be a refeshing mature view of the topics of the day. I've been listening to The Command Line for about a year and a half, and I've heard cmdln appear on some of my other podcasts and I have nothing but the highest respect for his work and his candid discussions of his family life

--

CafeNinja