bobpeers -> blog

I don’t understand why there are both gnome-appearance-properties and gnome-display-properties. I think that gnome-display-properties should just be another tab on the gnome-appearance-properties.

Since you can open the gnome-appearance-properties using the context menu from the desktop I really think that you should be able to change the display properties at the same time (plus coming from Windows it’s the expected behaviour).

Plus I think it’s overkill having an extra menu entry just to change the screen resolution.

While we’re reducing the menu clutter I can’t see why gnome-screensaver-preferences can’t also be included as an extra tab. I think for most people changing all settings to-do with the screen and desktop in one place makes sense.

In an attempt to fix the slow booting problem I have with Fedora 12 running in a virtual machine I decided to compile the latest stable kernel, 2.6.32.

Compiling went fine but I cannot get it to boot as it hangs at the line ‘Creating initial device nodes’. There’s plenty of people with the same problem it seems, but no solution that works for me. I’ve compiled many kernels before and never had a booting problem so this is pretty annoying, maybe it’s because it’s the first 64bit kernel I’ve tried compiling.

One thing that puzzles me is why Linux (specifically Fedora) doesn’t have native support for NTLM proxy servers. The Gnome proxy settings do allow for authenticated proxies but if you are stuck behind a Microsoft ISA server then you are out of luck.

Actually this isn’t quite correct as you can download ntlmaps and then set your proxy setting to point to this which then authenticates your connections.

But I don’t understand why this can’t be included as standard. It occurred to me that there could be licensing issues but Firefox does have native support and that’s open source (even though the license is different, Mozilla Public License vs GPL V2).

Yesterday I had a problem with the shared folders when running 64bit Fedora 12 in Virtualbox. When I ran the command to mount the share

# mount -t vboxsf sharename mountpoint

it just returned the error ‘command not found’. It turns out the the command is actually a symlink called /sbin/mount.vboxsf that points to /usr/lib/VBoxGuestAdditions/mount.vboxsf.

My symlink was broken due to the fact that on 64bit systems the program is actuallly located in /usr/lib64/VBoxGuestAdditions/mount.vboxsf. To fix I simply deleted and recreated the symlink to point to the correct location.

# cd /sbin
# rm mount.vboxsf
# ln -s /usr/lib64/VBoxGuestAdditions/mount.vboxsf mount.vboxsf