Gradually as Google has risen, so has the popularity of SEO. However, along with them, misuse of SEO has also risen substantially. I remember a few months back I was looking for some organization and the organization's webpage was listed in Google's second page while related articles and some unnecessary pages were listed on the first page.
Obviously, you can argue that those articles were more important the page of the organization. Well since I dont have any screenshots I can't prove much. You have the choice of not trusting me in that case. However, I could not find much important materials in the webpages pointed to by the links on the first page.
Such instances of hoax results are uncommon; but their number is growing. One of the major reasons is misuse of SEO. Recently, I found another instance of SEO misuse. The tags on the article and the content are obviously unrelated.
Google depends heavily on SEO techniques. I hope it improvises on this soon.
Friday, 29 May 2009
Wednesday, 27 May 2009
Saturday, 23 May 2009
The changing web
We all know the web is changing and along with it our lives as well (though the extent and kind of change is determined by the our own decisions). While surfing I found this. I was impressed to see the way it responded to mouse gestures. The design is intuitive. Developments like these are welcome. They make proper use of the power of current technologies. I could see Google's philosophy playing a role. The interface was not coming in the way.
Tuesday, 19 May 2009
Ida
Ida is the nickname of a fossil (Well there are stranger things in this world; no need to wonder so much about a fossil having a nickname.) found in the US. It is considered to be an essential connection between modern higher primates - monkeys, apes and humans - and more distant relatives.
Monday, 11 May 2009
irc problem
I use BSNL dataone service. Today, after connecting to the internet, I when I fired up Kopete to connect to IRC, I was not able to. I checked my connection with a ping to www.google.com and found my connection to be working fine. So, I checked my Kopete settings to ensure they were alright and so they were. Kopete does not show messages from the server. So, I came back to command line and fired up irssi. I got the following messages:
Irssi: Looking up irc.freenode.org
Irssi: Connecting to irc.freenode.org [213.232.93.3] port 6667
Irssi: Connection to irc.freenode.org established
*** Looking up your hostname...
*** Checking ident
*** Couldn't look up your hostname
*** No identd (auth) response
*** Banned: You have a host listed in the DroneBL.
For more information, visit
dronebl.org/lookup_branded.do?ip=59.93.128.10 Please contact
kline@freenode.net with questions. (2009/05/11 08.32)
ERROR Closing Link: 127.0.0.1 (Banned)
Irssi: Connection lost to irc.freenode.org
I visited the site indicated and found that it had been banned for running an insecure SOCKS server. Now, BSNL assigns a different IP each time you connect. So the obvious solution was disconection and reconnection thereafter.
I requested for removal of the ban because whoever caused the ban is no longer on that IP(, though he may return on it).
Irssi: Looking up irc.freenode.org
Irssi: Connecting to irc.freenode.org [213.232.93.3] port 6667
Irssi: Connection to irc.freenode.org established
*** Looking up your hostname...
*** Checking ident
*** Couldn't look up your hostname
*** No identd (auth) response
*** Banned: You have a host listed in the DroneBL.
For more information, visit
dronebl.org/lookup_branded.do?ip=59.93.128.10 Please contact
kline@freenode.net with questions. (2009/05/11 08.32)
ERROR Closing Link: 127.0.0.1 (Banned)
Irssi: Connection lost to irc.freenode.org
I visited the site indicated and found that it had been banned for running an insecure SOCKS server. Now, BSNL assigns a different IP each time you connect. So the obvious solution was disconection and reconnection thereafter.
I requested for removal of the ban because whoever caused the ban is no longer on that IP(, though he may return on it).
Sunday, 3 May 2009
Adventure of a Gentoo install
My first Gentoo install was on an x86 laptop. It worked fine. I wouldn't say it was a piece of cake as I would say for a SuSE install. However, it was pretty much close. I was trying to get the GUI installer to work but realized gradually that it was broken and I should try my hands on the command line. After few years of linux experience, I wasn't scared of the shell. The install completed fine. I successfully configured a dual boot system. I liked Gentoo's performance and ease of tweaking. So, I decided to try Gentoo on my old desktop at home.
Now that I am enjoying vacation at home, I decided to embark on the Gentoo installation adventure (I wont be calling it an adventure, were it not in retrospection.). Recently, the desktop was upgraded to an core 2 duo processor (E7200). So, I thought of giving the amd64 version a shot. I started from the command line. Everything went fine till the grub installation. I configured my bsnl broadband to work with it. I shall write about it in my next post.
The minimal install cd kernel showed the partitions as /dev/hdbx (x being the numbers differentiating partitions). So following the instructions of the handbook, I decided that hdb7, my root partition which contained /boot folder (I do not use a separate /boot partition.) translates to (hd1,6) in grub terminology. I created grub.conf with hdb7 as root and tried install grub with root on (hd1,6). However, I was surprised when an error message told me that no such device existed. I cross checked the handbook and found I was doing as it said. I decided to get some expert opinions on this. So, I switched another virtual terminal and fired up irssi. I talked to people in the #gentoo channel. They also confirmed that I was doing fine and I didn't get any reason for such behaviour. Then I was suggested to try grub-install. I thought lets give it a shot. There were more surprises to come. The device map showed the following translations.
/dev/fd0 -->> (fd0)
/dev/hdb -->> (hd0)
/dev/sda -->> (hd1)
/dev/sdb -->> (hd2)
I reported back at #gentoo and people there were surprised too. I thought I should try in #grub channel as well.
After joining the channel, I read the channel topic. They were basically focusing on grub 2. After confirming that I could about previous grub versions, I put forth my situation. They told me that the device map isn't much predictable as it depends on the BIOS. They also told me that grub is designed such that almost always the device from which the system can boot is (hd0), as happened with me: grub-install made the / partition as (hd0) as it was going to boot from it.
Now that I had understood why and how grub was translating my partitions, (unlike as described in the Gentoo handbook,) I edited my grub.conf to reflect the changes and installed grub manually. After successful install, I was happy to see the splash image and multi-boot options; but the adventure was far from over.
First, I checked if my windows partition was okay. It was relieving to find that it was perfectly alright. Then rebooted again to resume my adventure and headed straight into the next hurdle. I started my newly installed Gentoo system only to run into a kernel panic. The error message came from VFS telling me that it could not find the root partition /dev/hdb7. The first thought that came to my mind was: probably I was right in the beginning in suspecting about the success of the install when I saw hdb instead of sdb. My doubt was based on the fact that irrespective the disk drive being ATA or SATA, newer kernels use to refer to them as /dev/sdx, where x is a letter differentiating drives. The kernel panic message also told me that I should try with /dev/sdxN format. The reason I had not done it before was because I trusted the live cd kernel's behaviour. As the minimal install cd was burnt from an iso generated by the latest autobuild, I did not think that the live cd kernel would be outdated or behave like an outdated one. I checked at #gentoo and was advised to file a bug (my first bug report) after double checking.
I used the minimal install cd again and chrooted to my root partition. I editted my grub.conf and fstab to suit newer kernels' format. After a reboot, I was happy to have successfully installed Gentoo.
Now that I am enjoying vacation at home, I decided to embark on the Gentoo installation adventure (I wont be calling it an adventure, were it not in retrospection.). Recently, the desktop was upgraded to an core 2 duo processor (E7200). So, I thought of giving the amd64 version a shot. I started from the command line. Everything went fine till the grub installation. I configured my bsnl broadband to work with it. I shall write about it in my next post.
The minimal install cd kernel showed the partitions as /dev/hdbx (x being the numbers differentiating partitions). So following the instructions of the handbook, I decided that hdb7, my root partition which contained /boot folder (I do not use a separate /boot partition.) translates to (hd1,6) in grub terminology. I created grub.conf with hdb7 as root and tried install grub with root on (hd1,6). However, I was surprised when an error message told me that no such device existed. I cross checked the handbook and found I was doing as it said. I decided to get some expert opinions on this. So, I switched another virtual terminal and fired up irssi. I talked to people in the #gentoo channel. They also confirmed that I was doing fine and I didn't get any reason for such behaviour. Then I was suggested to try grub-install. I thought lets give it a shot. There were more surprises to come. The device map showed the following translations.
/dev/fd0 -->> (fd0)
/dev/hdb -->> (hd0)
/dev/sda -->> (hd1)
/dev/sdb -->> (hd2)
I reported back at #gentoo and people there were surprised too. I thought I should try in #grub channel as well.
After joining the channel, I read the channel topic. They were basically focusing on grub 2. After confirming that I could about previous grub versions, I put forth my situation. They told me that the device map isn't much predictable as it depends on the BIOS. They also told me that grub is designed such that almost always the device from which the system can boot is (hd0), as happened with me: grub-install made the / partition as (hd0) as it was going to boot from it.
Now that I had understood why and how grub was translating my partitions, (unlike as described in the Gentoo handbook,) I edited my grub.conf to reflect the changes and installed grub manually. After successful install, I was happy to see the splash image and multi-boot options; but the adventure was far from over.
First, I checked if my windows partition was okay. It was relieving to find that it was perfectly alright. Then rebooted again to resume my adventure and headed straight into the next hurdle. I started my newly installed Gentoo system only to run into a kernel panic. The error message came from VFS telling me that it could not find the root partition /dev/hdb7. The first thought that came to my mind was: probably I was right in the beginning in suspecting about the success of the install when I saw hdb instead of sdb. My doubt was based on the fact that irrespective the disk drive being ATA or SATA, newer kernels use to refer to them as /dev/sdx, where x is a letter differentiating drives. The kernel panic message also told me that I should try with /dev/sdxN format. The reason I had not done it before was because I trusted the live cd kernel's behaviour. As the minimal install cd was burnt from an iso generated by the latest autobuild, I did not think that the live cd kernel would be outdated or behave like an outdated one. I checked at #gentoo and was advised to file a bug (my first bug report) after double checking.
I used the minimal install cd again and chrooted to my root partition. I editted my grub.conf and fstab to suit newer kernels' format. After a reboot, I was happy to have successfully installed Gentoo.
Subscribe to:
Posts (Atom)