Finally, the OS X has been removed from MSI Wind U100, and completely replaced by Debian (testing). Whenever the computer is idle, the hdd makes this weird clicking noise. To stop it, we can use hdparm to turn it off. kenno@tora:~$ sudo hdparm -B 254 /dev/sda</p> /dev/sda: setting Advanced Power Management level to 0xfe (254) APM_level = 254 Source: MSI Wind – Gentoo Linux Wiki
There are probably a gazillion ways to do this. I use FAAC, Freeware Advanced Audio Coder, to do this job. It works very well: <br /> faac originalfile.wav -o outputfile.m4a<br />
While reading Linux Journal Issue 181 today, I stumbled upon a section explaining about running Ruby on Rails on Apache using an Apache module called Phusion Passenger, also known as mod_rails. To install Passenger, I followed the instruction provided in the magazine: sudo gem install passenger Unxpectedly, I got the following error: Building native extensions. This could take a while... ERROR: Error installing passenger: ERROR: Failed to build gem native extension. /usr/bin/ruby1.8 extconf.rb extconf.rb:8:in `require': no such file to load -- mkmf (LoadError) from extconf.rb:8 Gem files will remain installed in /usr/lib/ruby/gems/1.8/gems/fastthread-1.0.7 for inspection. Results logged to /usr/lib/ruby/gems/1.8/gems/fastthread-1.0.7/ext/fastthread/gem_make.out What’s happening? What did I do wrong? ...
I fixed the Pidgin “Unknown Protocol” problem just five minutes after my previous post. I’m going to describe how I found the problem and how I fixed it. If you’re interested, keep reading. In the previous post, I mentioned that I would completely remove the Pidgin package, including its configuration files: # apt-get --purge remove pidgin I did that and then re-installed Pidgin, but unfortunately, it didn’t fix anything. Then I checked the About dialog (Help > About) and noticed it listed libpurple 2.5.4 under Pidgin 2.5.6. This had to be the source of the problem! I remembered that libpurple had been upgraded to 2.5.6, and Aptitude said so. So what could possibly be wrong? ...
Update: The problem has been fixed. Please see this post. A few weeks ago, Pidgin could not connect to the Yahoo! Messenger server because Yahoo! was changing its protocols. At the time, Pidgin was at version 2.5.5. Then that Yahoo! connection problem was fixed in version 2.5.7 and newer of Pidgin. Anyway, Pidgin is acting up again. This time I’m not sure what is going on, and it didn’t seem other people are experiencing the same problem – Protocol Unknown for all types of accounts. ...