(English) Fedora Core 18 chroot install on existing LVM/dmraid

申し訳ありません、このコンテンツはただ今 English のみです。

(English) SSD acceleration support on Linux

申し訳ありません、このコンテンツはただ今 English のみです。

Centos on BrandZ lx zones benchmarked

Centos 5.4 i386

minimal install

(English) HomeMade Antifreeze Glass Cleaner

申し訳ありません、このコンテンツはただ今 FrançaisEnglish のみです。

(English) Geiger counters and dosimeters price craziness

申し訳ありません、このコンテンツはただ今 English のみです。

(English) (Français) Tunnels IPv6 et smtp.free.fr

申し訳ありません、このコンテンツはただ今 Français のみです。

(English) (Français) Ergonomie Voyages SNCF, toujours sur la mauvaise voie

申し訳ありません、このコンテンツはただ今 Français のみです。

Extracting the dialed number from phone record

I ran into a prank call today on youtube, and the authors didn’t care about removing the sound of the dialed number. Comments were arguing that the number could be retrieved. Of course it can: Everyone knows you can simply play that record to redial the number and generating DTMF tones is easy (I wrote my own phone-book application when 15, dialing numbers from my soundblaster card). What about the reverse process then ? Let’s try:

Extracting and locating the DTMF tones within the record. I used Audacity:

According to Wikipedia, here’s the matrix for the DTM Frequencies:

DTMF keypad frequencies (with sound clips)
1209 Hz 1336 Hz 1477 Hz 1633 Hz
697 Hz 1 2 3 A
770 Hz 4 5 6 B
852 Hz 7 8 9 C
941 Hz * 0 # D

Using the Spectrum analysis module on the selected sample and with the appropriate parameters, you can clearly see the two tones pikes:

Here, we can identify the 770Hz + 1336Hz dual tones revealing the ‘5’ number. Getting the full number is just a matter of minutes :)

I used the Barlett Window with 512 Bytes sample and displayed using the logarithmic scale (as we look for low freq pikes).

Don’t let low priority jobs throttle up your cores

On laptop, low priority background processes can kill your battery really fast even if you’re using the ‘ondemand’ cpu frequency scaling. This remark also applies to saving power on desktop.
With lowest priority, any intensive process will still throttle up your cpu frequency. You usually want it to take only the remaining cpu cycles, not caring about how long this task takes.

You can solve this problem by asking the ondemand cpu governor to ignore tasks with nice values higher than default.
To apply this on every core on the system:

echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/ignore_nice_load

For permanent use, as it’s done though the /sys/, you’ll need to add it to your rc.local or a custom init.d script ( sysctl.conf can’t be used here ).

Sixxs.net tunnel endpoint easy selection

申し訳ありません、このコンテンツはただ今 English のみです。