Google Public DNS announced

Google announced a Public DNS service, which is extremely easy to configure and which will improve your web browsing speed and security.  This service is not revolutionary however.  There were a few ones before, and the one that seems most popular these days is OpenDNS.  In case you wonder what’s the difference between OpenDNS and Google Public DNS, take a look at this Google Groups discussion.

From the end-user point of view:

Right now the difference is that Google Public DNS does not use any sort of redirection or display any ads. If a host (domain name, web address, etc…) doesn’t resolve, it will just fail. With OpenDNS, they hijack these failures and redirect you to a search page that displays ads and makes them money.

From the administrator or customer point view there are things like stats, control panels, and more – all in OpenDNS.  Google Public DNS seems to be focused differently. At least for now.

Update: Jason Kottke explains why Google did it.

Fedora 12

I’ve upgraded my laptop to Fedora 12.  I know, that wasn’t the smartest move, since the conference which I am attending is not over yet.  But I just couldn’t wait.

The upgrade process was as simple as:

  • Open up the terminal, switch to root user, and run “preupgrade“.
  • Select Fedora 12 from the list of available options and click Next.
  • Watch the downloads in progress.  Or, as I did, go and have a few beers and socialize.
  • When you are back from the beers, before you crash into bed, click the Next button for the installation to start.
  • Go to sleep.
  • Wake up to a shiny Fedora 12 distribution on your computer.

The only thing that got me worried for a second was that after the laptop rebooted into Fedora 12, for some reason the resolution of the screen went down to 800×600 or something like that.  But all I had to do was login into Gnome, navigate to System / Administration / Display and switch resolution back to what it was before the upgrade.

I didn’t have much time to explore things yet, just read through release notes and features list.  However things do look to be faster and more polished.  I’ll have to use it for a few days to know for sure.

Another look at KDE 4

Last time I wrote about KDE 4, I said that it wasn’t very usable for me.  Recenlty, the much praised upgrade to KDE 4.2 became available via Fedora updates.  So I got it and switched to KDE for a couple of days.

What can I say?  Quite an improvement indeed.  Mostly stable, with only a few issues, which are nicely balanced out by nice desktop effects, overall graphics, and plasmoids.  A few things moved around and I had to look for them (such as keyboard shortcuts for switching between desktops), but overall it was a pleasant experience.

Why am I back to Gnome for now?  Because of the following:

  • couldn’t manage to make KDE 4.2 work properly with two monitors (major issue)
  • got a bit annoyed by KDE 4.2 not waking up properly from suspend  (not always, but often enough)
  • also got annoyed by it not always coming back properly from screensaver mode
  • couldn’t find graphical configuration for power managment (my laptop kept suspending when idle for 5 minutes with no power plugged in)
  • a few other minor things here and there

I’m sure I’ll be back to KDE very soon.  The progress between KDE 4 and KDE 4.2 is huge and if it goes like this, then I won’t have to wait long.

Fixing advanced search performance in RT3

It’s been bugging me for a while now that advanced search is extremely slow in our RT3.  I thought it was something related to the famous Perl bug, but apparently it wasn’t.  Then I was I waiting for Fedora 10 to come out, so that we’d upgrade our RT3 installation to version 3.8.  And that didn’t solve the problem either.  Finally, we got bored and annoyed enough by this problem to actually do soemthing about it.  The solution was, as often, just a Google search away.  Here is the quote from this discussion:

Faulty rights on a specific queue caused the owner list to be quite long, which RT didn’t like. (By mistake someone had given the own ticket right on the queue to all unprivileged users)

I went through all the queues to check the rights, and there it was – a test queue had “Own Ticket” assigned to “Everyone”.  Immediately, after remove this access levels things got back to normal.

Fedora 10 booting issues

If it so happens that your Fedora install suddenly fails to boot, giving some error messages or a simple “GRUB ” string, then I advise you to boot into rescue mode, install all updates, regenerate initrd image and reboot.  All should be nice and sweet now.

Those of you who need more info, scroll through Common Fedora 10 Bugs wiki page.