Tag: upgrade

Posted on
by

We finally replaced our 4-year-old Windows Me computer with a new Dell (I’d had enough of building computers a few weeks ago) and it arrived yesterday. Katie had already asked me to upgrade her Mac while she made pizza for an office party. I had planned to finish installing Tiger first, but once you get past a couple of options and the EULA it’s all a matter of waiting for it to finish.

There’s something oddly exhilarating about simultaneously setting up both a Mac and a PC.

Of course I spent the next few hours registering the pre-installed software and updating everything. Run Windows Update. Reboot. Run LiveUpdate for Norton Internet Security. Reboot. Run Office Update (twice). It’s nice that Dell will pre-install stuff for you, but given that the computer is built to order, you’d think they could apply the updates before shipping.

With today’s hostile internet, it would greatly benefit not just new computer owners but the world at large if Microsoft (and Apple and Red Hat, while we’re at it) would take a cue from SuSE and Mandrake and tie their update systems into the setup process.

To Microsoft’s credit, Windows XP setup gives you a chance to turn on automatic updates, and recommends it to the point of “Well, if you really want to turn it off, you can, but you’ll be sorry!” And I’m reasonably certain Windows Firewall was turned on by default (i.e. it’s on now, and I don’t remember turning it on), though Norton supersedes a lot of its functionality. Depending on the default firewall rules, that should mitigate the impact of any worms that happen to pick your IP address before you run Windows Update.

Correction: It seems Windows Firewall wasn’t on as I thought. Norton Personal Firewall kept asking me whether I wanted to disable redundant rules (makes sense) or disable Windows Firewall entirely (I told it no—twice), so I assumed it was running. I hope it was only off because Norton was pre-installed.

Posted on
by

Microsoft’s automatic update system is now offering an update to the Windows Installer. That’s the program that handles all those .msi files you use to install new applications, keeps track of what’s currently installed, and lets you uninstall them.

And it needs to reboot after installing?

WHY? What low-level system file did they have to change? There is a Windows Installer service, but it’s not running, and even if it were, they should just be able to restart the service. Why do I have to reboot the entire #@!$ computer because I agreed to install an update to something that isn’t running? Is the design so broken it can’t update itself?

I’ve never had to reboot a Linux box after upgrading RPM, Yum, or Apt (the equivalent software on many Linux systems). Never, in the seven years I’ve been using Linux.

And you know, it would have been nice to know that this update would require a restart before I decided, “what the heck, it doesn’t look like anything that’ll require me to restart, I might as well grab it now.” Telling me that some updates may require a restart is like labeling a box of cookies “Processed in the same state as a peanut farm.” It’s useless. It gets ignored. Kind of like this rant probably will.

Update 1: I’d love to make this change to the dialog box:

No, it’s not F*ing OK but you’re going to make me restart anyway!
Mouldypunk (link dead)

Update 2 (years later): “OK I guess” would have at least been amusing. And thank you sooooo much, Gnome Software, for bringing this behavior to Linux. There’s a reason I still use the command line to install updates.

Posted on
by

Something that could help with the ever-shrinking window between turning on a new (Windows) computer and getting hacked by some automatic probe is to just make downloading security updates part of the setup process. I installed two Linux distributions this weekend, Mandrake 10.1 and SuSE 9.2, and both did this.

What I liked about the SuSE installer was the way the option was worded. The setup utility asks you if you want to “test your Internet connection.” It tests the connection by downloading the latest release notes and checking for updates! (Unfortunately, it somehow chose an old mirror of the SuSE site—not the one I used during the installation—and the process failed.)

Posted on
by

I’ve been thinking about adding memory to the PowerBook for a while now, and for various other reasons we ended up at Fry’s last night. I figured, we’re here anyway, why not at least price the RAM?

Well, here’s a big fragging “Why Not:” I couldn’t remember the exact specs required. There was, however, a chart listing various laptop models, and the employees could look up requirements by model in the computer. The problem there was that I knew it as “the new 12″ PowerBook G4,” not as “Model A1010,” so they ended up (as near as I can tell) pulling up the specs for last year’s PowerBook (the 1 GHz instead of the 1.33 GHz). Naturally, the two models use different kinds of RAM.

When we got home last night, I cracked open the manual to compare the specs. Tonight, I waded through the Fry’s return line, and this time I brought the manual along — as I’d intended to do in the first place.

Everything went smoothly except for one glitch. The memory slot is covered by a panel with four size #0 Phillips head screws. I do have a size #0 screwdriver, and three of the screws came out easily. One of them refused to move, and the head ended up getting stripped somewhat. Eventually I was able to get it.

So, now the laptop has gone from having the smallest amount of memory at 256 MB (barring the ancient Mac clone in the closet) to having the most memory of all our computers at 1.25 GB.

Posted on
by

This morning I upgraded the mail servers at work. They were down for maybe two seconds each. I doubt anyone even noticed.

If you’re used to installing software on Windows, you probably think I’m kidding. Didn’t I have to shut the service down before installing the upgrade? Didn’t I have to reboot when it was done? Nope!

The reason you have to go through all that trouble when you install something on Windows is that it won’t let you change files that are in use. So you can’t install the new Exchange without closing down the old one. And some files aren’t completely closed until you shut down Windows.

On Linux (and possibly all Unix-like systems), if you delete or replace an open file, the system hangs onto it until the program using it is done. So if you need to upgrade Sendmail, you can go through the entire process while the old Sendmail is still running, then tell it to restart the service once it’s ready.

It’s not quite zero, but it’s close!