Actually its not the official Chrome, but the open-source development version, better known as Chromium. I installed chromium from aur as follows:
After trying it out for a few minutes, I knew it was going to replace Firefox as my default Web Browser. It has certainly improved quite a lot since I last tried it on Ubuntu. It used to crash a lot then. Now, it has become rock stable(well, almost). It’s fast and snappy. It has got some great themes. On first start, it imported all my Firefox bookmarks. Also, another thing that I liked was the Opera-style speed dial that I always longed for in Firefox (Opera never quite did it for me). Overall its great, though there is one thing from Firefox that I still require on Chromium – something like the DownloadThemAll! addon for firefox. Hopefully, it will be developed ASAP. Till then I’ll go back to “The Fox” for big downloads.
Here is a collage of various KDE 4 screenshots from my laptop:
I’m now enjoying beautiful splashes at boot on my Arch box. Yes, plymouth works quite well on Arch. To get it working well, execute the folowing steps:
1. First get KMS enabled in your kernel.
2. Next install plymouth-git from aur:
yaourt -S plymouth-git
3. Then edit /etc/mkinitcpio.conf and add ‘plymouth’ (without the quotes) in the HOOKS line after base, udev and autodetect.
4. Rebuild initrd using(as root):
mkinitcpio -p kernel26
5. To change themes, do:
sudo plymouth-set-default-theme --rebuild-initrd
You can find themes in /usr/share/plymouth/themes.
The only problem I have with this method is that plymouthd does not get stopped even after plymouth splash ends. For that I have to do (as root)
everytime I login(not a very viable solution). So, if you guys have any better solution, feel free to tell me.
I found out a way to increase boot-up speed in Arch. Previously, I used to load the ‘network’ daemon in /etc/rc.conf ‘Daemons’ array. The ‘network’ daemon used to take quite a bit of time to load and also sometimes fail killing splashy(giving a message: “Something failed, killing splashy”) and falling back to text mode. But now I replaced the ‘network’ daemon with ‘networkmanager’ daemon and it works like a charm. Boot-up speed has increased and splashy does not crash anymore. It’s great.
To manage network with networkmanager in KDE4, install ‘kdemod-networkmanager-git’ and ‘kdemod-networkmanagement-knetworkmanager-kde4’ and reboot. You’ll see the ‘knetworkmanager’ icon in the System Tray. That’s it.
But one thing which I don’t understand is why ‘network’ daemon takes so much time to load and ‘networkmanager’ lesser.
I’ve moved over to Arch Linux. A really short review follows:
Its awesome. Installation was easy and for configuring the system for audio, video etc, the Beginners’ Guide in the Arch Wiki is sufficient. It makes setting up an Arch system a breeze.
I’ve set up my archbox with KDEMod4 and I shoud say KDEMod 4.3.2 rocks!! Its stable and zippy especially when you use it in conjuction with Compiz Fusion.
Another thing I liked in Arch was the BSD-style init scripts. All my system’s settings are stored in one file – in /etc/rc.conf. And that’s awesome.
I’ve saved the best for the last. Pacman. Yes, Pacman is the best thing that has ever happened to my system. It is zippy, it is easy and it keeps rolling. That means all the latest and greatest software is available without doing any reinstallation, which I could not have on Ubuntu and others.
Well, that’s it for now. Till then keep rollin’ and rockin’.
I passed the SCJP exam with 93% marks. I’m awesomely happy about it. Right now I’m awaiting my certificate which I’ll be getting in a few months.
Other SCJPs share your experiences.