Category: Tech

Posted on
by

Fedora LogoA few days ago, my Linux desktop at work popped up a message saying that Fedora 11 was available, and asking whether I wanted to upgrade automatically. Well, I didn’t have time to deal with it then, and in the past when I’ve upgraded Fedora (either from a CD or from a downloaded image), it’s been a big production, what with running the installer, rebooting, installing updates, updating third-party repositories, and finally rebooting again after all the updates are installed.

So I put it off for a few days.

Today I decided to try it.

The automatic upgrade program is called preupgrade, presumably because it downloads everything you need in order to prepare for the upgrade. It downloads everything while your system is up and running, then sets it up so that when you reboot, it will launch the installer. It installs everything, makes the changes, then reboots into the newly upgraded system.

And then it’s done.

It’s network aware, and works through yum, so it will actually take into account both third-party repositories and anything that’s been updated since the new release. It actually went out to livna.org RPM Fusion and picked up the appropriate NVIDIA display drivers.

Download while you work. Reboot. Wait. Done.

The only snafu I ran into was that it removed my copy of the Flash plugin, but I think I was using the experimental 64-bit one anyway, so it’s not terribly surprising.

I get the impression that Ubuntu has had a similarly smooth upgrade process for a while. And after my experiences moving from Fedora 9 to Fedora 10, I was seriously considering jumping ship. (Hazards of living on the bleeding edge.) But it looks like I won’t have to.

Now I just have to find time to play around and see what’s new!

Update: I’ve run into one snafu: xkb error popups every time I wake the computer from suspend. Resetting the keyboard worked.

Posted on
by

It’s a trending topic, but there’s a lot of misunderstanding about the Twitpocalypse. Here’s what’s going on, in layman’s terms (I hope).

What’s happening?

  1. Every Twitter post has an ID number that goes up by 1 each time.
  2. When a computer program stores a number, it sets aside a certain amount of space for it. Bigger numbers take more space because they have more digits.
  3. One common format is called a “signed integer.” It has 32 binary digits (1 or 0 only) with one digit set aside to indicate a minus sign. The biggest number it can store is 2,147,483,647.
  4. Twitter’s status IDs are approaching that number.

So what’s the likely impact?

  • Twitter itself can handle bigger numbers and will be fine.
  • Third-party apps that store the ID in a bigger format will be fine.
  • Third-party apps that store the ID as text instead of a number will be fine.
  • Third-party apps that store the ID in this particular format will end up with bad IDs as they try to cram a big number into a small space.

If I were to guess, the most likely breakage would be that replies might be attached to the wrong previous post — but again, only with apps that use this particular format for numbers.

Twitter itself will probably sail through cleanly (and has been planning to move up the schedule so that affected app developers don’t have to fix things in the middle of the night), so don’t expect any fail whales. Unless so many clients have problems that lots of people switch to the website.

Update: Not surprisingly, most Twitter clients are unaffected by the Twitpocalypse. I’ve used both Twidroid and Twhirl with no problems since Twitter passed the mark. I figured a few would get tripped up, but the real surprise is that it hit Twitterrific. One of the most popular clients on the iPhone? They do have an update, but a lot of people are unable to connect.

Posted on
by

I have to confess: I’ve started seriously thinking about a netbook.

Not that I actually need a netbook. I’d only really end up using it for conventions that I’d want to post live (which would probably boil down to Comic-Con International), and I have the ability to do that using either my G1 or the laptop.

Long-time readers (all five of you 🙂 ) may remember that last year I agonized over upgrading my phone to something with real web capability until they announced wifi, and I just lugged the laptop around. Which worked fine, but it was heavy, especially the day I was also carrying around Comic Book Tattoo.

Of course, now I can use the G1 to post to my blog, or Twitter, or Facebook, or (almost) anywhere else even without wifi.

Except…

  • Typing on that tiny keyboard is slow. Not as slow as the onscreen keyboard, but still a lot slower than typing on a full-sized keyboard. Then again, netbook keyboards are also smaller than standard, so it might not be much of an improvement.
  • There’s no easy way to transfer photos from another camera. I can only think of two ways other than using a computer as an intermediary: use a Micro-SD card with adapter in the camera, or get a card reader that will clone data from an SD to a Micro-SD.

The camera issue shouldn’t bother me. Chances are I’d just end up doing what I did for WonderCon this year: post the occasional phone pic to Twitter and then upload the good photos to Flickr each evening. Just like I’d mostly be writing brief posts from the convention and detailed posts at the hotel.

Not my book, but the same page that she signed in mine.But then I remember the post I made on the Tori Amos signing last year. After the signing I was so hyped that I found a table, set up the laptop, banged out a blog post, hooked up the camera and added a couple of photos…and the post ended up getting linked on a major Tori fansite, producing a traffic spike so big that not only is the following day still this blog’s busiest day ever, but that post, even though traffic fell off over time, is the 8th most-viewed post on the site over the past year.

Still, the promise of another 15 minutes of blogfame isn’t enough to justify several hundred bucks. (Though the < $200 models that pop up on Woot from time to time have been tempting.) So I’m making an effort to practice typing with the G1, both the physical and on-screen keyboards. I’ve got Twidroid and I Tweet for posting to two Twitter accounts. I’ve got wpToGo to simplify blogging. I’ve got a plugin that will automatically liveblog using Twitter, which I still need to test.

It’s just a matter of making full use of the tools I have, rather than running after the latest cool toy.

Update: I posted this last night, but somehow it ended up backdated to the day I started it on May 20. I think wpToGo must have set a publishing date when I posted the draft. Yes, I started this post on my phone.

»All pages site-wide with this tag