It's Just this Little Chromium Switch Here

Weblogging and commentary by Chip Rosenthal

NetworkManager and the Ubuntu Upgrade

in
screenshot of KNetworkManager

Some time back I upgraded hepcat, a Dell Inspiron 600m laptop, from Ubuntu Dapper to Ubuntu Feisty, skipping over the Ubuntu Execrable release. I've been pleased with how Feisty runs on my laptop with one exception: I didn't understand the big deal about NetworkManager. Seems like DoNothingManager might be a better name.

Then based on a comment I saw over at the Ubuntu Forums site, I edited the /etc/group and manually added myself to the netdev group. (Also powerdev for good measure.)

Once I did, I was amazed. The NetworkManager is awesome. Not only does it make it easy to lock onto and log into the wireless network of your choice, it even switches over to the wired network when you dock. This facility runs rings around the Windows network managers I've seen.

I don't know if this group file change is documented anywhere, but it's really important. Without it you could be missing out on one of the best parts of the Feisty upgrade.

Spiderman 3 is Meh

So I made this total tease posting about Spiderman earlier in the week. I feel somewhat obligated to go back now and give an opinion.

And that opinion is: meh.

I think one of the reasons why I enjoyed Casino Royale so much is that it took an overwrought, bloated franchise and brought it back to earth with interesting and somewhat believable characters and situations.

I fear that with Spiderman 3, Sam Raimi has taken a long stride down the well-tread path to franchise failure.

Sure, the movie is action packed and the effects are striking. But that's about all it has going for it. Spiderman deserves better.

As far as characters, this movie favors quantity over quality. The Sandman was one of my favorite villains from the Spiderman comic. I was particularly disappointed with the movie version. The origin scene was fantastic, and I think it would have worked if he had been portrayed as a human-sized creature made of sand. Instead, the movie turned him into the Stay-Puft Sandman.

I think what was most frustrating for me was the lazy writing. The Harry Osborne story arc whipsaws around when the butler drops a comment, for no purpose other than the plot required it. That was too gratuitous and deserved more care.

I thought the final fight scene, which coalesced many of the fragmented plot pieces and had a grace and style not seen in the earlier fights, was somewhat redeeming.

The non-plot bits with the regular ensemble were tremendously fun. Watching J. Jonah Jameson trying to rein in his blood pressure was a hoot. It was fun to see Bruce Campbell, who played the snooty usher in the last installment, in another "service industry" role.

If you like Spiderman, go ahead and see it. You'll have a good time. But if you love Spiderman then go watch the second one again.

Circumvention in 16 Bytes

See this 16-byte hex string:

09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0

It an HD-DVD processing key. It's a code that allows software to unlock the content on an HD-DVD. With this code (and the right software) you can do forbidden and illicit things, like watch a movie you bought on your Linux workstation.

The industry is not pleased and is trying to get this information suppressed. They say that under the DMCA, those 16 bytes should be suppressed as an illegal circumvention device.

Their effort is absurd. Even more, it's not working.

Doest this stupidity remind anybody else of the old export-a-crypto-system one line perl script?

Update: Ed Felten wonders how an industry that has failed to suppress the copying of multi-gigabyte files could possibly believe they could succeed at suppressing a 16 byte string.

Spiderman 3 is (Embargoed)

I've been thinking since last Thursday how I could write this blog entry in some way that doesn't sound braggy or snotty. I cannot, because I've realized the purpose of this blog entry is to be braggy and snotty. So, here goes.

I saw Spiderman 3 last week.

One of the perks of being married to a professional film journalist is that she sometimes sneaks me into free movie screenings. I've been warned, however, under penalty of severe spousal disfavor, that information about the movie cannot be printed until it's released. So, I won't say anything about the movie other then, yep, I saw it.

I supposed I could discuss the event, but even there caution is advised. I heard a story about a guy who went on a studio junket and wrote about the junket experience and ended up getting banned from all that studio's film screenings. I'd hate to get my wife in trouble by talking about how they gave us free food from the concession (whatever we wanted), or that the reels were shown out of order (which some people are describing as a "true grindhouse" experience).

Come back Friday. Maybe I'll post an opinion then.

Music Industry Self-Immolation

I'm working from home today. Earlier in the week, I got a wild hair to buy a pile of CDs from Amazon. I've done that a couple of times since I unloaded my vinyl on Craig's List. I find myself, in equal measure, replacing missed favorites and acquiring classics that escaped my collection. So I've been multitasking between my day work and the occasional trip to the living room to switch a CD in the ripping tray.

Somehow, this whole process is making me feel dated and archaic. Little discs of aluminum—how precious!

It's clear that the days of CD purchasing, let alone CD ripping are numbered. Some recent articles in the news suggest the process is hastening.

First, there is the big, recent news that EMI is going to allow their catalog onto iTunes with higher fidelity and no DRM, albiet at a higher price. I'm unwilling to purchase digital music that's licensed and tethered to a device. This, suddenly, makes things interesting. I'd be curious to hear how the higher fidelity recordings (256-bit AAC) compare to the (FLAC) lossless compression I'm using. And I'd need a web-based iTunes store, so I can access it from my Linux workstation. If those happen, I'll be ready to start buying digital downloads instead of the aluminum discs.

Then, there is this op-ed in the Times that lays out just how bad and stupid the music industry is being.

The major labels wanted to kill the single. Instead they killed the album. The association wanted to kill Napster. Instead it killed the compact disc. And today it's not just record stores that are in trouble, but the labels themselves, now belatedly embracing the Internet revolution without having quite figured out how to make it pay.

The final thing, not related to CD marketing but to general music business stupidity, is the new royalty scheme that threatens independent net-based radio. This is one of the last remaining ways for me to discover new music. I think once that's gone, it's game over.

All this makes me wonder what the hell I'm doing still buying and ripping CDs. What's the sense when the music enjoyment comes wrapped in such a crappy experience?

5:15pm update: Christopher Beam at Slate weighs in on the 256-bit AAC issue and suggests it's mostly not noticable. I'll believe it when I hear it. Sure, it probably makes little difference when you are listening on a portable player with $12 ear buds. I want digital tracks that are good enough to play on my home stereo.

Hello from Denny's

I'm posting this blog entry from the Denny's at Burnet and Anderson—simply because I can. Isn't free wifi great?

I haven't been here in a long time. I was surprised to find they recently added free wifi service.

That's timely, because we needed a late night wifi option in the neighborhood. Many months back, the Jim's at Burnet and Research used to have wi-fi. Then, at some point, there was a signal but no connectivity to the net. Then it just went away.

I'm probably going to eat at Jim's less and Denny's more because of this.

Business owners take note. I just spent $8 on a chef salad. An AT&T business class DSL line can be had for under $50/month. It doesn't take very many chef salad sales to pay for this amenity.

Ubuntu Feisty Fawn Looks Promising

in

For the past couple weeks, I've been running Ubuntu Feisty Fawn, the version of Ubuntu Linux scheduled for release next month. Actually, I'm running Kubuntu—the flavor with a KDE desktop. So, just mentally add the "K" throughout this post.

Earlier this month, the hard drive on my primary workstation chinacat developed some bad blocks in critical areas. I replaced the drive and bravely decided to go ahead and load the pre-release version of Ubuntu. Fortunately, it's been remarkably robust. The system has been in heavy use I've only found a few minor bugs—which is remarkable for pre-beta software. The Ubuntu developers have responded quickly to my bug reports.

I've been impressed at how robust the Feisty applications and controls seem to be. Especially the desktop and system adminstration. One of the most difficult Linux administrative chores is adding printers. It can be bad enough just trying to add a simple printer hanging off a USB. My situation is even more difficult. I've got a couple of printers on a dedicated server, I want to use the lpd protocol to connect to the server, and I want to provide two queues for each device (one that processes the printing and one that provides a raw device). The GUI administration tool handled all this with ease.

I'm beginning to think the Ubuntu project may have taken a bad turn a year ago and Feisty represents a turn to recovery. A year ago, Ubuntu Dapper Drake was issued as a Long Term Support (LTS) release. They promised this release would have a longer lifetime, with full patch and security bugfix support through 2009, instead of the usual 18 months.

I realize that in retrospect there were two problems with this LTS release. First, LTS targets data centers more than desktops. One signficant part of this release was enhanced server support. This all sounds great, but it's not the Ubuntu sweet spot. If I want a robust, stable server, I'm going to choose Debian or Red Hat Linux, not Ubuntu. I understand that the Dapper release was an attempt to address that, but I think that's a poor choice. Ubuntu shines on the desktop, and given limited resources, maybe Ubuntu leaders should focus there instead of trying to be all things to all applications. I fear that the LTS effort may have been a distraction from providing a good desktop release.

The second problem is that it took a lot of work to get this LTS release out. Ubuntu normally runs on a six month release cycle. The Dapper release was slipped two months to get it all together. The next release, Edgy Eft, was done on a compressed four month schedule. Maybe that's why the Edgy release sucked so bad.

Every system that I upgraded to Edgy had significant problems. My workstation chinacat could not sync my calendar and contacts to my Samsung SPH-i500 PalmOS phone. My media computer coldsnap lost its wireless, and I had to build the network driver from source. The only Ubuntu computer I had that didn't have problems with Edgy Eft was my laptop hepcat—and that's because given the serial catastrophes of Edgy, I left it at Dapper.

All these problems had me concerned about the future of Ubuntu. Thanks to the promising results of Ubuntu Feisty Fawn, I'm a believer again.

Open Documents are Good for Texas

Currently if you get some document from a Texas office or agency, dollars to doughnuts it comes in some proprietary word processing format. If you want to use this document, you either have to purchase the software that matches that document, or gamble that the software you like may have reverse engineered the proprietary format and won't fumble the document too much.

I don't like it when the state tells me which software I should buy.

It would be wonderful if state used open, non-proprietary formats to store their documents. Instead of letting the state to dictate which software we should use, we could choose whichever product works best for our needs. Proprietary formats create an unfair state mandate. Open formats trust to markets to deliver the best solution.

All of us already know the benefits of open document standards. Every time we open a document on the web, we get a document in an open, standard format called HTML. Most recent versions of HTML are layered on a basic technology called the Extensible Markup Language, or XML. XML is a widely embraced, leading standard for storing structured documents.

Why can't we take the benefits that an open XML standard brings to web documents and apply them to word-processing documents?

The answer is, we can. There currently is a standard called OASIS Open Document Format for Office Applications or OpenDocument for short, or ODF for even shorter. I'm not endorsing ODF, but rather citing it as an example that works right now. Other standards are possible, and that wouldn't necessarily be a bad thing, just so long as they are open and vendors can make their products interoperable.

There currently is a bill in the Texas legislature that would require Texas use an XML-based, open, non-proprietary format for its documents. The bill does not mandate the ODF format—or any other particular format. Instead, it calls for open standards, and allows for markets to select the technologies and software that work best.

The Texas Open Document bill is called SB 446 in the Senate and HB 1794 in the House. The bills have been referred to committee and are scheduled for hearing this Tuesday Monday (corrected 3/26).

If you have a chance take a look at the following two committees:

If your state senator or representative sites on one of these committees, consider shooting them a quick fax or email this weekend to let them know that you think open document formats would be good for Texas.

CA City fines Time Warner

When Time Warner acquired Adelphia, many localities found themselves with a new cable provider. Moorpark, CA was one of them.

The problem in Moorkpark is that the cable franchise—the contract signed between a cable provider and the municipality—had service requirements that the new provider wasn't meeting. More specifically, the franchise requires that customer service phone calls are answered within 30 seconds and they weren't.

Local cable franchises typically contain service requirements—and enforcement provisions that can be invoked when the provider fails to meet them. The Moorpark City Council chose on a unanimous 4-0 vote to penalize the provider with a $25,000 fine.

This is interesting, because there is a national movement away from municipal franchises for video. Texas, has already done that. SB 5, passed two years ago, allows new video providers (basically AT&T and Verizon, the entitites that purchased this legislation) to skip local franchises.

The big problem with legislation such as SB 5 is that it does away with the build-out and service requirments typically found in a local franchise. The supporters claim that competitive markets will fix those problems, but, as this case shows, the video market must not be competitive because the problems still exist. Frankly, I'm not sure that a market where the customer choice is basically just between Brand A and Brand T can ever be competitive.

You can read more about the Moorpark, CA situation here.

Will TIF Fee Finally Die

Last month, I blogged about the State suing a phone carrier over bogus fees charged to phone users. I applauded the move, but pointed out that the biggest source of bogus phone fees is the state itself.

Turns out somebody at the Capitol must read my blog. This week the House passed a bill to drop the fee associated with the now-defunct Texas Infrastructure Fund. TIF was created in 1995 to put computers in schools and libraries, setup community networks, and the like.

In 2003, Governor Rick Perry declared "mission accomplished" and ended the TIF program. But the fee remained, and monies collected were passed on to the general fund. That's not right. If you are going to call it a TIF fee, then you'd best use it for "TI", not a general tax.

Oh my, Dick Armey and I agree on something. That's scary.