Everybody Staze...

Nobody leavz...

You are here: Home / Archives for 2011

Archives for 2011

RHEL 6 genkey

By

genkey in RHEL 6 seems to be broken, or at least it is in vSphere. Generating an SSL key takes forever, and then it fails at the end of the process with a non-descript error.

The fix, after futzing for a bit was to run it with the “–test” option. When run that way, it doesn’t try to use the kernel’s random number generator, but instead uses random keyboard input to generate the randomness for the key.

Looking online for info with regards to this turned up nothing, so I thought I would post the solution here. Good luck!

UPDATE:So after receiving a signed cert back from ipSCA using a CSR generated with the above process, I found the CRT doesn’t work. I don’t know if this is because of the process, or whether ipSCA made a mistake in creating the CRT. I have instead generated the key and csr manually using the openssl utility and submitted that CSR to ipSCA. We will see if they send me back a valid CRT. Will update again once I know.

Facebook’s crappy RSS/Atom Feed

By

We are building a new website at work using Drupal 7, and one of the requirements is integration of work’s Facebook and Twitter streams. The easiest way to do this, of course, is with the Drupal Aggregator and the RSS/Atom feeds both Facebook and Twitter provide.

The problem is, while Twitter’s RSS/Atom feed is standards compliant, Facebook’s is not, by any stretch. The main problem for us being, Facebook provides relative URLs linking to posts rather than Absolute URLs, as required by the RSS standard. The relevant part being here:

RSS places restrictions on the first non-whitespace characters of the data in <link> and <url> elements. The data in these elements must begin with an IANA-registered URI scheme, such as http://, https://, news://, mailto: and ftp://. Prior to RSS 2.0, the specification only allowed http:// and ftp://, however, in practice other URI schemes were in use by content developers and supported by aggregators. Aggregators may have limits on the URI schemes they support. Content developers should not assume that all aggregators support all schemes.

Others have also had this problem (the problem being URLs that should be “http://www.facebook.com/USER/post/xxxxxxx” turn into “http://www.mysite.com/USER/post/xxxxxxx”), and rather than resign to the fact that it’s just not going to work, I decided to spend some time to actually make it work for me.

[Read more…]

iDentify

By

iDentify LogoTime was, my media library was populated with lots of files with inconsistent titles, and worse, TV episodes like “Showname_S01E05.mp4”. This is great if you know “episode name -> episode number”, but that usually required me to get online, and look that info up. Worse, DVD’s don’t necessarily have episodes in the same order they were aired (like, Firefly’s DVDs). The thing is, my media collection is rather large, and I REALLY didn’t want to go through and name all the episodes by hand. And it really came to a head when I bought my new AppleTV (Gen 2). So, I did some searching online, and found the answer in a software product called iDentify, by Justin Pulsipher.

One word comes to mind: genius! I could suddenly drop all my TV shows, and movies into the program, and it would look up the title, and cover art online, and rename the file using variables that I set (in my case, “Showname – SxxExx – Episode Title.m4v”. And if you/I wanted, it’d then add them to my iTunes library. It does this all extremely well, and the new version adds a few other nice touches. It adds the ability to name episodes in aired or DVD order (see Firefly comment above), and the ability (thought I haven’t tested it yet) to name files based on DVD numbering. So, using the default Handbrake naming scheme for TV series encodes, iDentify should be able to chew through those and name them appropriately.

My only complaint, and I thought it was something with iDentify, but in fact it’s an Apple issue, is you can’t have colon’s in the filename. I thought that Apple had removed this restriction, but it appears this is not the case. iDentify replaces colon’s with two asterisks. I think I’d prefer just omitting the offending character, but I’d guess there are reasons for not.

The app is extremely easy to use, and with the latest feature improvements (like being able to say which service to use for TV show lookups (I’ve had very mixed results with tagChimp, but TVDB works very well)) it’s a rock solid app. Is it worth the $9.95 that is charged for the file naming feature? Absolutely! Some people have called it crippleware, but that’s a joke. The app works great in it’s free version, it just doesn’t do renaming, which is largely what I wanted. I gladly paid the $9.95, and it is probably worth more than that.

My only real complaint, is the name. Unfortunately, the name is also a commonly used english word (that says what it does). Googling for the app name can be rather difficult because of that. The author is trying to get the app into the Mac App Store, and when that happens, I’d imagine he’ll see a significant boost in sales due to exposure.

If you have a media library (of mp4’s) that you’ve ripped from your DVD collection, and haven’t already named, or filled in metadata info for, I’d highly recommend the application. Download it, use it, love it.

[xrr rating=5/5]