Virtualbox + XP + Firefox = Netflix in GNU/Linux
4Having recently wrested control of my machine from Windows Vista, I’ve had to implement a workaround for Netflix streaming media. Netflix, unfortunately, has yet to see the mistake in building their streaming architecture on Microsoft’s near-dead Silverlight platform. Until they recognize the error of their ways, I need a workaround. I’ve settled on virtualizing XP, as Silverlight (and Moonlight, for that matter) will not successfully run Netflix in WINE. (As a side note, WINE runs Excel 2007 — one of my must-have Windows apps — flawlessly and, ironically, faster than my Windows installation used to.)
So, I installed VirtualBox OSE from the Lucid repo (a few versions behind current, but no worries) and installed my XP Pro SP3 image on a small virtual hard disk. It took entirely too long, although I had shortcut the process by ripping the CD to my hard disk using dd (+1 for GNU!):
$ dd if=/dev/cdrom of=~/home/captivus/win_xp.iso
(Seriously … dd is bloody brilliant. One of the most useful tools in the GNU suite.) Anyway, it works like a charm and I’m not without my new love, Archer, despite no longer running Windows.
The Liberation of My Workstation
1“DAMN you, Vista! I shall liberate my workstation from your death-grip forthwith!”
With this clarion declaration which, in my oppression-stoked rage, was made with all of the sentiment and perturbation of rebels and patriots gone before me, (is the analogy a bit Philistine? Certainly …) I threw off the chains of The Beast and replaced Windows forever with my favorite Linux distribution.
I’ve long since made Linux my sole operating system on nearly every box on my network. To date, though, I have retained Windows on my primary workstation, running both Debian and Ubuntu in virtual machines, due to my dependence on several software packages which are not available (either to me or at all) for Linux. I was determined this evening, however, to inch away from this by dual-booting Linux with Vista. Several hours later, to my fury, my plans were thwarted when, twice, the NTFS partition would not resize with gparted! This was particularly frustrating as I waited nearly 2 hours each time for gparted to fail on the resize operation. Bloody NTFS!
So, with Eddie Izzard’s beguiling comedy as a soundtrack, I dumped a back-up of my files onto my archive hard drive on the workstation, and deleted that bloody NTFS partition once and for all! Let the death knell for Windows ring out! I’d rather virtualize Windows on an as-needed basis than be strong-armed into what I can and cannot install on my own hardware.
Strange Days
0холна секцияJim Powell, Senior Fellow at the Cato Institute, contributed a timely and topical editorial to Investor’s Business Daily this week. Powell echoes a surging sentiment prevalent among the financial and economic “in crowds” that the Federal Reserve has done far more harm than good in its interventions to prop-up the flagging US (world) economy. From the editorial:
Intended to save our economy, the Fed has turned out to be perhaps the biggest single source of economic instability. It’s the big pig at the trough, and it’s unpredictable. It doesn’t follow any rules consistently. When it moves, everyone else can be badly knocked around.
The very unpredictability of the Fed causes uncertainty that discourages investors and employers from making commitments for the future — an important reason why we’re experiencing a sluggish, jobless recovery now.
…
It’s time to begin planning for an orderly dissolution of the Fed before it does us any more harm.
The piece is accessible and well-written and provides good context for the student of current affairs. As a side note, another interesting bit (albeit slightly differently themed) appeared at MarketWatch the other day. These notions are not at all unique. They have been, until recently, fairly clandestine though. The very appearance of editorials highlighting these themes in such mainstreams publications is foreboding evidence of strange days ahead.
Madigan, Begin Again
0Shortly before I left the house yesterday for the airport, the home line rang and displayed a nonsense phone number on the caller ID. (“100000000000″ was the number — clearly a spoofed number to obscure the identity of the caller.)
If I may digress, briefly, I find it particularly insidious that the campaigns of local and elected officials deliberately mask their efforts to telemarket the electorate in this manner. This is the most recent in a series of similarly obfuscated phone calls we have received — despite our private number and listing on the DNC registry. (It seems, however, that the DNC registry is only aimed at stopping for-profit telemarketing and provides a massive loophole for campaign calls from non-profit organizations.)
</tangent>
The caller identified herself as phoning from Illinois Attorney General Lisa Madigan‘s office. What followed was a surprisingly rude line of responses culminating in an insultingly xenophobic hang-up. I am shocked that the reelection campaign an accomplished politician like Lisa Madigan would have succumbed to such shoddy staff work. Lisa — whomever is running your campaign should be summarily flogged.
The content of the discussion is best relayed in conversational format.
CG: “Good evening?”
LM: <Protracted pause as the auto-dialer routes the answered call> “Uh … yes, may I speak with [my wife]?”
CG: “May I ask who is calling?”
LM: “Uh … this is from Attorney General Lisa Madigan’s office.”
CG: “Is this a campaign call?”
LM: “Umm … not really. We were just calling to see if she was going to vote this year.”
CG: “That sounds like something we’d probably classify as a campaign call and decline to receive it …”
LM: <Before I can complete my polite closure to the conversation> “Well, I’d need to hear that from her.”
CG: “No, you don’t. You’ve phoned my home, my phone number. I’m telling you that we are not interested in receiving campaign calls on this number.”
LM: “Well, she signed up to receive them.”
CG: <Growing vexed>”No, she certainly did not!”
LM: “Well, I’m looking at the details right here on her voter registration.”
CG: “Right — she registered to vote. She didn’t sign-up to be campaigned to.”
LM: “Well, I don’t know how this works, but …”
CG: <Interrupting>”I’m telling you that this is how this works.”
LM: “… And you’re from this country, and you know how this works?”
CG: <Stunned speechless for a moment> “Are you kidding me? This is Lisa Madigan’s office phoning, you say?”<My question was met by the silence of a dead line>
Troubling, indeed, to endure rudeness and ignorance of this magnitude from a woman who interrupted my evening by phoning my home. Hopefully Steve Kim has a more enlightened view on immigration, given his parents’ Korean background.
Superfluous fstab Entries After Upgrading to Lucid LTS
0A quick post to outline a stupefying problem I encountered after upgrading one of my machines to Ubuntu Lucid (10.04) this weekend. By way of background, I am anything but an early-adopter of OS releases — especially on my production hardware. I haven’t the time to debug network-critical software on systems on which I rely heavily, so I typically lag a major-version-release or so behind the “cutting edge”.
Yesterday I finally made the move to upgrade to Lucid LTS on one of my servers on my home network. The automatic upgrade apps downloaded and executed without a hitch, so I was optimistic upon reboot. For reasons which surpass understanding, however, I received an error indicating that the hard disk upon which I had installed the OS refused to mount at boot time — although, to Lucid’s credit, I was given an option to skip this mounting and continue with the boot.
The whole episode was absurd, as the disk was clearly mounted and booting — how else was the OS loading at all if the disk upon which it resides would not boot? Upon logging in, a quick cat /var/log/boot.log suggested that there was, indeed, an error in mounting /dev/sda1. cat /etc/fstab made clear what the problem was — somehow there were additional entries in the fstab file which tried to mount the partitions on /dev/sda subsequent to their initial mounting. I’ve not the slightest idea how these entries made their way into the file. I am, however, confident that they were not there prior to the upgrade as this error was entirely new. A few keystrokes in vim and I had commented-out the offending entries. Upon reboot, all was well with the server.
Most perplexing …
recently on cg.com