This idea has been around for well over a decade. Maintaining a discrete list of what is allowed which can be completely enumerated with a great level of confidence and block the rest. Badness cannot be enumerated completely. Blacklists will always be missing important aspects. Expecting that all people are good and don’t do bad things will always turn bad.

Patches released for DNS services that are vulnerable do not fix the root cause. It can’t be fixed because it is part of the original specification and migrating away from it will be equally as painful as the migration to IPv6 is. These patches only implement other kinds of mitigation for the exploit. The best form of mitigation comes in the form of implementing standard best practices that have been around for many years.

DNS servers should carefully control who is allowed to ask questions about non-authoritative zones (recursion). DNS servers at ISPs should limit recursion to customers only. Corporations should run internal recursive DNS servers with access restricted to internal users only. This will severely isolate any damage caused by cache poisoning.

I am not saying nobody needs to patch their servers. In fact the patches should be applied quickly because it does help quite a bit. I am just saying that if you have already implemented best practices you shouldn’t have to worry very badly. And if you haven’t implemented them, do it now!

I really like my AT&T BlackBerry 8820 a whole lot. I really hate Windows Mobile devices, and dislike the Treo line. But I still want an iPhone really badly. This article makes it sound like BlackBerrys are better. I disagree.

10. The iPhone’s Not Designed for One-Handed Operation

Duh, I call this a feature, not a problem. Even when I am not driving, I still hate typing with one hand. I could care less.

9. Every iPhone is Created Equally–At Least on the Outside

Again, so what. The one model of iPhone is the model I would want.

8. No Removable Battery, No Backup Power Supply for the iPhone

Based on my BlackBerry usage, the removable battery is completely unnecessary. I generally only charge it once every 2 - 3 days. I have never replaced a battery on a cell phone ever. I usually replace the phone before the battery dies. Even if the iPhone’s battery doesn’t last 3 days, charging it once a day is not a problem.

7. The iPhone Has No Native Video Recording Capabilities

And neither does my BlackBerry! I have an 8820, no camera at all. I mean WTF?! I have to step down to the Curve which is a rickety P.O.S. to get a camera? No way.

6. The iPhone Is Too Darn Expensive

Considering I didn’t pay for my BlackBerry (my company did), this doesn’t apply to me again. Plus the difference between an 8820 and an iPhone is worth the benefits.

5. The iPhone Doesn’t Support VoWi-Fi–Even Though It Could and Should

And neither does my AT&T BlackBerry! Not that I really care though since I am on my company plan with huge voice and data discounts.

4. iPhone User? No GPS for You

Ok, this point isn’t completely negligible. I did run TeleNav on my BB for a while. It is incredibly cool, and does some very awesome things with GPS. But in truth I never really used it. GPS for Google Maps was plenty for my usage.

I’d miss the GPS in Google Maps on an iPhone but not seriously enough to not buy one.

3. Want an iPhone? Hope You’re Ready to Switch Wireless Carriers…

Wrong again! I’m already on AT&T. I’m already suffering with Edge (no 3G on AT&T BlackBerrys).

2. No Physical Keyboard? No Thanks.

I am pretty good with the BB keyboard. I will concede that using a virtual keyboard will suck for quite a while. But I will get over it. I am flexible and adjust quickly. The increased screen size is worth the short period of adjustment.

1. The iPhone Third-Party Apps Debacle

The only apps I would miss, that either don’t already exist, or don’t have a webapp replacement, is my Google Talk or an IRC client. There are ways around both via Webapps, though not quite so pretty. Oh well. not a big deal.

In summary, BlackBerry has GPS, better 3rd party app support (for now), and a physical keyboard. iPhone has a camera, huge screen, total hawtness, awesome mobile web browser, media player that doesn’t totally suck. I can certainly say I’m going to get an iPhone as soon as I can.

First I want to say thank you to everyone that showed interest. Apparently this type of plugin is desperately needed. My initial version was just a quick hack to transfer meta data to and from my iPod. Note the extremely hackish nature of the link between iPod and rhythmbox tracks (filename only).

1. The most common complaint was the rhythmbox crashing bug (Segmentation Fault). This is caused by the gpod module when it attempts to locate and read the itunes database on the iPod. My fix was to just check if gpod found the itunes directory, print an error to the console, and skip any processing at all. This will prevent killing rhythmbox, but doesn’t actually fix anything.
2. More intelligent rating updates. I used mockenh’s idea to compare last played dates to determine which rating to use in case of a conflict.

I don’t really have the desire to implement playlist, or podcast synchronization since I have very little time, and I am only a mediocre programmer at best. If someone wants to swipe my code to build on, they are more than welcome to.

1. I just use a periodic rsync to copy music from my iPod to my PC. rsync -av /media/BFUNGUS/iPod_Control/Music/ ~/Music/ Change any paths as necessary.
2. Since I don’t copy songs to the iPod using Linux, I didn’t write that support into it
3. The detection of the iPod mount location is dependant upon the GnomeVFS module. It must correctly recognize your iPod as a Music Player
4. The python gpod module must be installed. Debian users can apt-get install python-gpod

ipodsync v0.2

Powered by Twitter Tools.

Powered by Twitter Tools.

Powered by Twitter Tools.

@mollywood It’s better too look good dead, than to be alive and ugly. #

Powered by Twitter Tools.

Theo: “Since both emacs and gcc contain code inside them which permit them to compile and run on commercial operating systems which are non-free, you are a slimy hypocrite.”

RMS: “I see you are being your usual friendly self ;-}.”

Much of it was very thought provoking, but the majority was just bickering. The biggest point of the whole war being that RMS had specifically recommended against OpenBSD because it “included” non-free software, referring to the ports system. Theo and others took offense at this because the ports system doesn’t “include” any external software, it is only a framework of Makefiles that make installing lots of software packages, Free and Non-Free, easy. And the entire ports system is 100% Free-Software.

IMHO, the saddest part of this whole debacle is the fact that besides the extremely obscure gNewSense pet project of RMS, there is no other operating system, or distribution of an operating system more Free than OpenBSD. Both RMS and Theo have similar goals with Free Software, but have radically different tactics and personalities.

Those opposed to granting marriage licenses to others based on the choice of partner often spew forth ideas based on religion. I have no desire to legislate religion, but the marriage license is not only a religious idea, it is deeply intertwined with government processes, rights, and privileges, making it a civil right.

I can think of two possible solutions to this violation of rights. Remove the marriage license as a government document and tool to determine ones rights. Or the easier alternative to remove the immoral, discriminatory restrictions for getting said marriage license. Religions can continue to decide which marriages they accept or not.

I once saw an article describing this dilemma. Basically all tasks can be broken into categories based on the difficulty of the task and the frequency of the task. Steps to reduce the time and effort to do these tasks should be prioritized by category. Tasks that are easy to do, that you do frequently, should have shortcuts applied when possible. An example might be using your shell’s alias feature. Tasks that are easy, that you do rarely, don’t bother over complicating it yet. Hard stuff that you do frequently should be automated as much as possible. Perhaps you could try your hand at Shell or Perl scripting. Those rare tasks that take some time on your part should be clearly documented to take out the guess work, perhaps even include copy/paste’able code fragments as well.

I highly suggest these two books by Thomas Limoncelli. The Practice of System and Network Administration, and Time Management for System Administrators. The first book covers a lot of general theory of system administration, not necessarily platform specific but there is lost of unix information. The second book offers excellent ideas and tips on managing your time better, reducing distractions, and getting rid random people interrupting you to ask why their email is slow.