Diary of a Network Geek

It seems to be all the rage, but I think we’re going to do it anyway.

I killed “cable” television a number of years ago, after having lost it during Hurricane Ike in 2008.  I used Netflix, before streaming was really a thing people did, and binge-watched shows a disk at a time.  Lost made a lot more sense when I watched four episodes a night, and not one a week.  The plot continuity between episodes was a lot easier to follow and I really enjoyed it.  I found that I read more and wasted less time.  I was more productive and more relaxed than I had been in a long time.  And, I really didn’t miss having all those channels that I didn’t watch to surf endlessly, trying to find something “good to watch”.  In short, it was no loss to me, outside of the cost, to cut cable.
But, in early 2012, I met a girl and things changed.

Okay, so that’s a little poetic license.  She’s not “a girl”, but is, in fact, a woman my age.  However, like virtually all significant change that has occurred in my life, a woman, whatever her age, was at the heart of it.
Seriously, though, after four, solid years with nothing but books, the internet and Netflix for entertainment.  But, before my future wife moved in, I got the television service for AT&T’s U-Verse again.  I got the U-300 package to get her some specific channels that she wanted to watch.  Most important to her was Turner Classic Movies, because she is an old-film buff and part of several on-line old-movie communities.  To not have that would have been a “deal breaker” and, well, that wasn’t a deal I was willing to break.  So, in the spring of 2013, I got cable TV again and got two wireless DVRs as part of the package.  Wow, did she widen my horizons with the introduction to the DVR!  I don’t know how I managed to get by without one before.

In any case, all of that is to say, we’ve decided for various reasons, including costs, to cut cable again and go to streaming services.
And, I’ve decided to document the transition, outlining the choices we made and why we made them.  This post will anchor the series and give you a reference point for what we have now.  Specifically, we have AT&T U-Verse, with the 6 MBPS “Elite” internet package and the U-300 channel package with one wired DVR receiver and two wireless DVR receivers.  Additionally, we have Netflix streaming with HD and two-disks-at-a-time rental with the Bluray option.  Our current total is roughly $200/month or $2400/year.  I’m fairly confident that we can cut that in half with some judicious changes.  And, also because a handy savings calculator told me so.

Want to run the numbers for yourself?  Get your bills and click over to the “Should you cut the cord?” Calculator at Slate.com.  You may be surprised.
And, keep coming back here for details and updates on how we do what we do, saving money and gathering information as we go.
Just do be warned, this is primarily a blog by geeks for geeks, so at some point I’ll probably get into some technical stuff as I work to replace or improve some of the systems we’ve grown used to having.
The updates won’t come every week, but I’ll try to keep them regular.  And, they won’t normally come on Friday after this one, either.

Hurricane season started on Monday, June First. Are you ready?

Here in Texas, hurricane season is kind of a big deal.  Or, at least, it is to this kid from the Heartland.  Of course, most of the time, we have plenty of time to prepare because you see these things coming from a long, long way off.  Still, it’s better to be prepared early rather than competing with everyone for bottled water, bread and canned food.

So far, since I’ve been in…
Read More

Last year, I shared these tools to help people participating in NaNoWriMo and, since it’s that time of year again, I’m going to share them again.

Maybe one year, I’ll be able to get myself together again and give this a try.  Maybe this coming year, I’ll have all my regular posts queued up and ready to go and have a story idea and all the research done and have been practicing my writing and…  Well, maybe.  In any case, until…
Read More

Looks like the free LogMeIn option is going away.

It had to happen eventually, but it kind of sucks for those of us who relied on it to get certain things done.
They sent an email this morning, giving free users, like me, about a week to either pony up for a pro account or find another solution.  I figured I would have to search around for a while to find an alternative, but, thankfully, the folks over at Slashdot were already talking about it in the thread Short Notice: LogMeIn To Discontinue Free Access.  The ever helpful commenters had a lot of suggestions, with varying levels of snark and technical skill required and, you know, actual usefulness.  There were some interesting and baroque solutions to this pretty common problem.
Now, I’m a devote of Perl, so the idea that “there’s more than one way to do it” is near and dear to my heart, but some of those solutions on Slashdot were more hassle than they were worth!

The solution I looked at and quickly tested today was the Chrome Remote Desktop plugin.
I chose this for a couple of reasons.  First, it was free.  Frankly, that was probably the most important requirement.  I don’t have a budget for a lot of things I don’t use everywhere or every day, so I need to be careful how I spend that money.  Secondly, it was easy to implement and use.  There were several options discussed on Slashdot, but most of them were going to take creating one or more accounts on services like DynDNS or something similar, or they would need a new server or other dedicated machine.  That wasn’t going to work for me either.  I need something simple to install and use.  Mostly because I’m lazy, but still, the requirement is there.  And, thirdly, there had to be some kind of security on it so random users couldn’t log into machines.
Now, the “down-side”, such as it is.  This solution requires that Chrome be installed on any machine you want to get access to or from.  This is a Chrome plugin, so, obviously, it won’t work without Chrome.  Secondly, to get it and install it, you need a Google account of some kind, even though it’s free.  Gmail will do, and in fact was what I used to get the plugin from the Google App Store.  And, yeah, that was pretty much the only “bad” thing about it.  Again, for me, it wasn’t a big deal because I tend to install Chrome on any machine I happen to work on for any length of time, but it could be a hassle for people who don’t use or know Chrome.

Setup was easy and prompted me to enable remote connections to my machine then immediately asked me to set a PIN to restrict access.  I like that it did that.  Also, the PIN is required to be at least six digits, which is decent enough security.  I, personally, made it seven digits, but for the truly paranoid, you can make it longer.  I first set the plugin up on my work machine and then set it up at lunch on my home PC.  Again, I was asked for a PIN.  I happened to make it the same, but I’m pretty sure that PIN was unique to each machine, so, again, for the truly paranoid, you can lock this down pretty well.  After that five minute install, I was able to take over my machine at work.  Boom!  Just that easy.

As a further test of the plugin’s ability, I checked the box that allowed for “off-line access”, then I shut down my Chrome browser at home.  Once I got back to work, I tried remotely accessing my home PC.  I was asked for the PIN and then I was right in!  Again, just that easy.
Also, I should note that my work PC has only one monitor, but my home PC has two and Chrome Remote Desktop plugin flawlessly displayed both monitors.  It was absolutely amazing!  And, the connection was fast!  Frankly, it was faster than LogMeIn was most of the time.  It was great!

So, I know that LogMeIn won’t miss my business, since I never really gave them any, but I cannot say that I’ll miss them.  This is a great solution to the problem of remote access and I cannot be happier with it.  We’ll see how things go over time, of course, but this looks like a great, easy and free replacement for LogMeIn.
If you all find other solutions or solutions that you think work better, leave the information in the comments!

And becomes completely irrelevant.

Apparently, I missed this last month, but Six Apart is changing their license so that Movable Type will no longer have a free version.  Now, when it was Ben and Mena Trott running Six Apart, when they made a mistake with licensing, which I think they did back in 2004, you can understand and forgive.
Ben and Mena were like us, just two fellow geeks out there coding and blogging.  They came up with a great idea and everyone loved it.  But, then, money got involved and things got complicated.  They did things to make money, and, honestly, I probably would have done the exact same things.  When they first changed things to make the license more restrictive back in 2004, I was, I admit, outraged.  How could they betray us like that?  They were like us!  How could they throw this all over to just make money!  In retrospect, the question is, how could they NOT?

But, then there was WordPress.  Many of us made the jump, including me.  WordPress was a new way of doing things.  This Open Source thing was new to many of us and it was exciting!  Software that was mostly free that the community built!  People who were just like us!  Code geeks and blog geeks and graphics geeks all coming together to make cool things happen.  What could be better?  And, from my perspective, WordPress was easier to extend and develop for in many, many ways.  Also, it seemed to have fewer resource issues than the Perl-based Movable Type.  Better still, as I understood the license, WordPress would always be free and if it stopped being free, we could fork the code and make it free again.

Somewhere back in there, after the 2004 license debacle, Movable Type added an Open Source version.  They tried to get us back, but, frankly, for most of us, it was too little, too late.  After one license change like that, how could we be sure that it wouldn’t happen again?  And what about charging money to be part of the developer’s group who had access to the documentation you really needed to understand Movable Type enough to develop for it?  I know I couldn’t afford that!  Besides, as Six Apart got more and more corporate, I just felt like something else bad was coming, if not soon, then eventually.

Now this.
Well, it actually happened in July, but I just read about it on Mark Jaquith’s blog.
So, finally, after nine years, that other shoe has finally dropped.  Of course, a lot has changed in those nine years.  For one thing, I’ve gotten both married and divorced and am getting ready to be married again.  Interestingly, to me, Ben and Mena who started Six Apart have gotten divorced, too.  Ben still seems to be involved in the day-to-day development of Movable Type and related stuff, but Mena seems less involved.  I can’t imagine the toll their meteoric rise took on their relationship.  It must have gotten truly unbearable after a while.
You know, I hope they made out well.  Sure, this latest license thing is, I think, a final nail in the coffin of Movable Type, but, damnit, Movable Type also launched the blogging era in many ways, and paved the way for WordPress.  And, it was two people who started it.  Just two.  Two good people.

So, it’s sad, to me, to see how things have gone.  I’m sad to have been right about Movable Type all those years ago.  I wish they had proven me wrong.
But, with this, I think they proved me right not to trust the Movable Type license any more.  And, honestly, they taught me something about how to treat my audience and my customers.
And, yes, it makes me sad.  It’s the end of an era, of sorts.
I’m sorry to see you go, old friend.

So, I’ve finally heard back from DataRetrieval.com!

(Actually, I heard back a couple weeks ago, but I’ve been a little busy and haven’t had a chance to write things up.)

After a couple days of trying to get a response from an actual human being as to what was going on with my drive, I finally got a quote.  Well, actually, two quotes, which was kind of confusing.  The first quote was for about $300 and the second quote was for $1800.  But, I got no explanation of what the two quotes meant!  After a whole lot of back and forth over the course of more than a week with what seemed like an email autoresponder, I finally got in touch with a customer service representative to find out what was going on.
As it turns out, the quote for $300 was the minimum price to just get started.  Let that sink in for a minute.  They wanted $300 up front before they even started working on this drive with no promise whatsoever of actually retrieving data.  The $1800 quote was an estimate of the entire cost for retrieving all my data.

Obviously, that wasn’t going to work for me and I told the service rep that.  Then, apparently, we started negotiations.
He came back with a counter offer price, which was still way too high and I told him so.
A day later, he came back again with another, lower offer.
In the end, that $1800 got cut down to about $500, which made me wonder just what they were charging me for in that first outrageous quote!

Finally, I convinced them that I wasn’t going to use their service and that I just wanted my drive back.  They charged me $25 for shipping, which I thought was fair enough, and they sent my drive back to me.  And here’s where they really lost me as a customer ever.  To the left, you see the box they sent my drive back to me in.  In case you forgot from the first post about this incident, since it was so long ago, I sent the drive to them in a larger box that was specifically designed to ship drives in, to keep them as safe as possible.

At the right, you see how they packed things inside the box.
After all the strongly worded warnings and disclaimers about making sure you ship your damaged drive to them well padded so they won’t be liable for any additional damage or data loss, they don’t return the drive with anything like that same consideration.  I suppose they don’t feel like they need to since they won’t be making money off the drive, but, damn, that kind of disrespect for potential customers really says something bad about them as a company, at least in my mind.  I mean, there wasn’t *any* padding whatsoever!  It was just wrapped in two plastic shipping bags and shoved into the box!
Thankfully, the drive doesn’t seem to be damaged at all, or any more than it was when it crashed, so I’m probably no worse off than I was before I sent it to them.  Still, it’s the idea that they’d show so little care with my data that makes me question their entire service.  I know that I, personally, won’t ever trust them to attempt a data retrieval again, that’s for sure!

Also, based on what I’ve read, the problem is most likely a bad board on the drive.  A board which I can get off eBay for about $40, replace myself, and quite likely retrieve all my old photos.  I haven’t actually decided if I’m going to try and run down the board that matches the BIOS on my particular drive, but I may.  Kind of a huge difference, though, between $1800 and $40, plus a little of my time, isn’t it?

In any case, if I decide to get the board and fix the drive myself, now that I finally have it in my possession again, I’ll post another follow up with how that went.  And, possibly, even a tutorial on changing out that board.

Advice from your Uncle Jim:
"A pessimist is one who makes difficulties of his opportunities; an optimist is one who makes opportunities of his difficulties."
   --Reginald B. Mansell

Naming kids is easy, but naming systems is hard!

And, no, I don’t mean giving your phone a pet name.

I have gone on at length in the past about the importance of naming systems.  It’s a big, big deal, especially if you ever have to go back and change any of those names!  Granted, it’s not as bad now as it was in the old days when you had to manually update dozens, or sometimes hundreds, of host files or configuration files, but, still, it’s a pretty big deal.  So, naming systems are often a topic of discussion, especially among hardcore network geeks.  I’ve been in more than one meeting about choosing a naming scheme that devolved into name calling.
So, there are many schools of thought on this.  One group of people think that the name should be meaningful, giving location and function information.  That’s a good idea, but it often results in names like HOUNOVFILESERV001.  (And, yes, that’s actually a name I used on a server once, for a company that no longer exists.  It stands for HOUston NOVell FILESERVer number 001.)  Sure, it tells you what you need to know, but they quickly become unwieldy to type and maintain.
Another group would say to name your servers, or routers, or what have you, after any group of things that will be easy to remember, like the names of the Seven Dwarves, or characters from the Dilbert cartoon, or, even, at one place I worked, the names of the old Space Shuttle fleet.  And, while I’m not a huge fan of that for many things at a business, it can be fun to ping a Cisco router named Elvis just to get the response “Elvis is alive”.  Certainly at home, I tend to favor a more fun approach using something light-hearted, like the names of cartoon characters or mythological beings or something similar.  But, my problem is always, which set of “things” to choose?

Well, the Naming Schemes Wiki solves that particular problem.  Yes, someone has started a wiki that gathers all the different naming schemes you all can think of in one place for your viewing pleasure.  And, in spite of any protests from your significant other, you can select, at your leisure, a naming scheme to use on your network that makes you smile.  (And, stop looking at me that way!  I know I’m not the only person in the world with a home network big enough or complicated enough to warrant having to choose a naming system for it!)  The maintainer also encourages you to add your own scheme, if, somehow, it’s been missed on this site.  Or, to add to any of the existing pages if you have something to contribute.

So there you have it!  All the endless naming possibilities for your home networking project this weekend!
Y’all have fun!

No, not a long, melancholy post reviewing the past year’s emotional highs and lows.
Just a link to an autogenerated infographic summing up this blog’s traffic for 2012.
Enjoy!

I don’t know about you, but I love free stuff.

I do a lot of stuff on the web every day.  Yeah, I know you can’t tell that from how neglected this blog is these days, especially compared to the old days when I was posting pretty much every day, but, trust me, I’m always buzzing around the web doing something.  Sometimes, it’s building websites like this one.  Not very pretty, but pretty functional and sometimes, not even sites for me.  When I build a site, I generally leave it to the owners to come up with the actual content and just help them get the framework setup, including all the legalese that seems to be pretty much de rigueur these days.
Well, now, thanks to PriorityDigital.com, I think I have a slightly better solution.  They have a page of free utilities that include a Privacy Policy Builder, a Disclaimer Builder and a Non-Disclosure Agreement Maker, among others.  So now, you, or I, can go to these utilities and fill in a few relevant details and quickly get a fairly generic, but still useful, privacy policy, general website disclaimer or non-disclosure agreement without having to pay a lawyer!  Granted, they are pretty generic, but, still, for most of us, they’ll handily take care of our needs.

So, okay, yeah, kind of lame for a Friday, but, still it might give you a little something extra for your side project this weekend.
Enjoy!

So, in keeping with the theme this month of NaNoWriMo, I bring you creative time-wasters!

Okay, so maybe I call them “helpful utilities” when I use them, but, still…
Back in the day, I was much more of a Renaissance man that I am now.  I dabbled in all kinds of things not least of which was either writing or programming.  And, I tend to live by the dictum that one cannot really learn anything worthwhile without a project or goal.  When you combine those things, well, you get some interesting projects.
The first programming language of any real weight I taught myself was Perl.  Perl has sometimes been called the duct tape of the internet, because so many system administrators use it to keep old, clanky systems running.  That was also the reason I learned it, because I often found myself maintaining old, clanky systems!  But, mostly, I used it for my various webpages.  Then, of course, came WordPress which ran on a fancy new language called PHP.  Naturally, I set about teaching myself PHP.

Well, the projects I used were random generators, primarily to help people who were writing and needed a little help.  One of my earliest was a little tool, originally inspired by shareware, that let you randomly come up with what might be in fantasy character’s pockets.  If memory serves, the shareware program was developed as a utility for Dungeon Masters in AD&D campaigns that had a lot of thieves who were always wanting to pick the pockets of townsfolk!  But, it was fun and useful as an exercise.  You can find that one here: Fantasy Pocket “Litter” Generator.
Recently, after adapting that to the new PHP language I was mentioning, I got the idea to extend that idea to a more modern setting and came up with the Random Daily Carry Generator.  So, instead of having magic frying pans and enchanted daggers, a character may have an encrypted USB drive and a loaded Glock 21.  Just the thing to fill the pockets of random story characters, as needed!  Also, this one is still under development a bit, so as I think of things, I’m adding them in.  Visit often for new stuff!

And, of course, all those things and more can be found at my old World-Building page at my almost defunct writing site; Fantasist.net.
So, if you’ve hit that first week stumbling block on your NaNoWriMo project, go check these pages out and see if anything helps.  But, most of all, have fun!