Some people complain how Gnome’s Keyring keeps asking them for password whenever they try to get connect to wireless router. Here is a trick of how to stop Keyring from bothering you for good. Go to System > Preferences > Startup Applications, disable the check box “Gnome Keyring Daemon.” That’s it, everything should go as plan if you done this correctly! I tested this trick on Fedora Core 11 and Ubuntu 9.04, both Linux distribution work fine with this trick.
How to reset Keyring’s password if you forgot it? Go to .gnome2/keyrings/ directory by type this little command inside your shell/terminal – “cd ~/.gnome2/keyrings/“ (without the double quotes), then you have to delete login.keyring or any other file that has unwanted Keyring’s encrypted passwords that you want to get rid of. Use command “rm filename” to delete a file in any Linux distribution! The next time you use something on your Gnome Desktop that requires Keyring’s password, you just have to enter a brand new password twice to reset your old password (you already delete your old password) — you only have to do this once unless you want to reset your Keyring’s password again.
As any other operating system, Linux comes with its own problems. Today I like to talk about how to umount your flash/usb drive from your Linux box (Linux computer). When everything is fine as the sky is blueish, no rain, and the sun is out shining brightly, you find that umount is working without complaining. The truth is that umount sometimes behave oddly, but not everyone using Linux will be the unlucky one that gets to experience this. I had! Umount complained that the device is busy and cannot be umount. I was freaking out, and of course, the logical thing to do is to get out of the directory that you want to umount, but when I did that the freaking Linux still complained that the device is busy.
To solve the problem like this, I had to search the web for an answer! I found the answer, and it was about a running process or a running file that failed to die and still used the mounting directory.
Let solve this! First you need to get out of the directory that you’re trying to umount. Type pwd to see what directory you’re in. You can also do mount -l to list the mounting devices/directories. By checking with mount -l you can see that the flash/usb drive is listed there as a mounting device/directory, and this assures you that the device is still busy. The easiest way is to see if one command line “umount -l /media/disk” (/media/disk is where my flash/usb drive mounts to, your can be named differently) solves the problem. After trying umount -l and you still see Linux complains about the device is busy, then you have to try the next method.
Alternative method is to kill the process that bothers the mounting device. To list the process that bothers your mounting device, you can try “fuser -m /media/disk” command line. This will show the process’s ID of the bothersome process/file. To kill the bothersome process/file, you need to do “kill -9 12345″ where as 12345 is the process’s ID. Each process has different ID number, and so number 12345 is just an example. After killing the bothersome process/file, you can try “umount -l /media/disk” again to see if umount is possible or not. You can also do “mount -l” to see the mounting device that you’re trying to get rid of is still hanging around or not.
Splog is a term for spam blogs. A spam blog is different from a blog that is being filled with spam comments. Splogs are usually set up by the spammers to attract search engines’ crawlers and to generate ad revenues from ad networks like Adsense, Adbrite, and others. Many splogs contain unoriginal contents that were scraped from other websites, and then the spammers insert huge amount of web links into splogs to attract search engines’ crawlers. Setting up splogs are easy for spammers since everything is automatic. Spammers use spam bots to scrape websites’ contents, change the contents, repost onto free web blog hosting services.
Web links inside a splog often take visitors to irrelevant websites. Search engines’ crawlers will crawl these web links inside splogs without knowing that splogs have little legitimate contents. Advertisements from ad networks are serving within splogs to generate ad revenues. Web links inside splogs lead visitors to websites that have other irrelevant promotional materials to generate even more ad revenues. Whenever a visitor visits a splog and clicks on an advertisement message, a splog generates some ad revenue.
Some free blog hosting services experience high number of splog registrations. Therefore it’s a headache for free blog hosting services to have to deal with splogs. There is no particular easy way to deal with splogs as each spammer sets up splogs differently. There are some common traits that most splogs have such as no comment, irrelevant contents, way too many web links, tons of advertisements, and no information about the blog owners. Even though we know these are the common traits of splogs, these common traits are also present in valid blogs. Some blog owners may turn off their blogs’ commenting feature, have poorly written contents that seem to be irrelevant, contain way too many web links to other online sources, posting way too many advertisements, and may provide very little or no information about the blog authors. Search engines and free web hosting services find it’s hard to get rid splogs, and there is a high possibility of get rid a valid blog. Identify each splog case by case is easy, but free web hosting services may have up to hundred millions of blogs for validation, therefore identifying a huge amount of splogs at one time won’t be an easy task. Automating the process of identifying splogs may lead to wrong validation by identifying valid blogs as splogs.
While we’re speaking, the web is being filled with millions of splogs, and the spammers are happy with their ad revenues. See if you can catch a splog in ten seconds when surfing the web! Have fun in identifying a splog, report it to the proper authority if you like, and remember not to click on the splog’s advertisements unless you want to make the splog’s owner a little richer.
Web designers know that it is tough to get a website to work with all browsers, and so it’s a daily procedure for web designers to test their newly designed websites with all browsers to see if things are in order. Instead of firing up different computers for different IE versions, or firing up different browsers(Firefox, Chrome, Safari) using different operating systems such as under Linux, Mac, and Vista, web designers can try one of those online services that provide the browser testing capability.
BrowserLab from Adobe is a new service that is not yet ready for everyone to use just yet, but they are accepting limited number of users to check the service out. But what is this? BrowserLab provides web designers with real time browser testing capability. This means web designers can use BrowserLab to see if their websites are working as they have intended with their targeted browsers.
Web designers can also check out Browsershots. Which one is better to use, BrowserLab or Browsershots? You can provide your answers by posting a comment. Have fun testing out BrowserLab and Browsershots!
Recent Comments