Here’s the list of removed packages but the good news is that gnome-applet-netspeed may be saved.

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.

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.

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).

# 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

I’ve cut the starting services right back to the basics and set it to autologin but it still takes ages. It seems that even getting to udev takes considerably longer than it used to, plus there’s a very noticeable delay before X starts and the desktop is displayed.

For comparison my Fedora 11 machine (32 bit) running the same services regularly boot in 23 to 30 seconds.

It could be to do with the virtual machine since I has to create an xorg.conf due to a problem with Virtualbox guest additions and Fedora 12 but I doubt that’s the sole cause. I did read a bug report about probing for the floppy drive but that’s not my problem.

I’ll just hope that either a new version of Virtualbox or a future Fedora 12 update fixes this.

After installing and rebooting, my X server wouldn’t start. I dropped into a virtual terminal only to see that Xorg could not find any screens to use (Fedora 12 has no xorg.conf, it use HAL to detect the displays instead). This happens in both 32 and 64 bit versions.

It seems this is a general problem that can be fixed by creating your own xorg.conf with the required settings. The second link I provided has the fix.

I haven’t tried it myself yet but hopefully a new version of Virtualbox will soon fix the problem. It did occur to me that it would be nice if there were an easy way to uninstall guest additions to fix problem like this, at least then I could make a temporary fix to investigate the problem.

It’s easy to use the file in Virtualbox using these instructions from Tech Crunch.

But also like many other people I was getting nowhere trying to log in using my Google Account username and password. The errors indicates that it’s a network problem so the comments suggest using bridged networking instead of NAT but that made no difference for me.

Finally I found a post telling me to use chronos as the username and a blank password, bingo now I could log in. When logged in found my networking was fine and it makes no difference at all if I use bridged or NAT, both work fine.

One final point is that the default keyboard is set to US so if you’re keyboard is set differently (mine is DA for Denmark) be aware of this.

I’ll leave most of the obvious comments on Chrome OS to others, as there’s plenty been said on the subject. But for those that dismiss the OS I think it’s way too early for that.

I may not want it on my main computer tomorrow but combine it with a new laptop running an ARM processor,16 GB flash drive and another year or so of development as well as an asking price that undercuts current netbooks by miles (maybe $100 in the US) and I think there will be a huge market.

Feature wise it’s the same as the Windows version but the performance is fantastic, it starts in under a second and page loads take fractions of a second. The whole browser feels incredibly fast, in fact faster than anything I’ve tried before.

I recommend that if you’re running Debian or Ubuntu you should give it a try and see what you think.