ThinkWiki - User contributions [en]

Script for theft alarm using HDAPS

2010-02-11T18:36:32Z

Kiraven: /* Prerequisites */

==General==

Recent ThinkPad models include a built-in two-axis accelerometer, as part of the [[HDAPS]] feature. This accelerometer can be put to another use: as a laptop theft deterrent. The following scripts detect when the laptop is moved, and emits a loud audio alarm.

This alarm can be an effective deterrent against a casual laptop-snatcher in a populated environment (e.g., typical office space). It's also useful when you're across the room from the laptop and want to know if someone fiddles with it.

Note that the alarm is disabled when the laptop is suspended or powered off. You can buy external (hardware) motion detector alarms to handle those cases.

{{WARN|The audio alarm is played at a very high volume. Never enable the alarm while wearing headphones connected to the laptop's speaker output or when the laptop is connected to a high-power amplifier.}}

==A comprehensive script==

This Perl script periodically samples the tilt data reported by the accelerometer, computes the variance over recent samples, and triggers the alarm when the variance exceeds a given threshold.

On a ThinkPad with [[Active Protection System]] running a modern Linux installation with the [[HDAPS|hdaps]] kernel module loaded, the script should work as is. Just run {{cmdroot|tp-theft --arm}} and see (or rather, hear) what happens when you tilt your laptop.

The volume and alarm sound can be adjusted at the top of the script. On a ThinkPad {{T43}}, the synthetic siren at <tt>$alarm_volume=100</tt> (up from the default 70) is quite ear-splitting, and combined with <tt>$acpi_volume=15</tt> it is dangerously loud.

The script is designed to run continuously in the background, so by default the alarm will be activated only when the KDE screen saver is locked. If you you open the laptop lid (or press the lid button) shortly before or after the beginning of movement, the alarm will be suspended (except for a brief warning) and you will get a few seconds of grace to unlock the screen saver (preferably, [[How to enable the fingerprint reader|using the integrated fingerprint reader]]!). You can disable this functionality by passing the <tt>--arm</tt> parameter, by setting <tt>$use_kde=0</tt> and <tt>$use_lid=0</tt>, or by using the simpler script below.

There is also an option to track a BlueTooth device (e.g., a mobile phone). In this case, the alarm is activated (and optionally, the KDE desktop is locked) whenever the device is turned off or too distant for a given period, and deactivated when the BlueTooth device is nearby. You need to provide the device's BD address. If both KDE screen saver and BlueTooth checking are enabled, then the alarm will be activated when *either* the screensaver is enabled or the BlueTooth device is amiss.

===Prerequisites===

* ThinkPad with [[Active Protection System]]
* [[HDAPS|hdaps]] kernel module loaded (included in kernel 2.6.14 and later)
* Optional: [[ibm-acpi|ibm_acpi]] module loaded with the <tt>experimental=1</tt> parameter (included in kernel 2.6.14 and later; needed only for full volume control)
The following are included in all modern Linux distributions:
* ALSA sound system, <tt>alsactl</tt>, <tt>aplay</tt>, <tt>amixer</tt> )
* <tt>sox</tt> (SOund eXchange) sound utility

===The script===
{{CodeRef|tp-theft}}

==A basic script==

This is a simpler version of the above script, which omits the fancier functionality such as KDE screensaver detection, lid detection and state machine.

===Prerequisites===

* ThinkPad with [[Active Protection System]]
* [[HDAPS|hdaps]] kernel module loaded (included in kernel 2.6.14 and later)
* <tt>aumix</tt> mixer control utility (included in all modern Linux distributions)
* <tt>sox</tt> (SOund eXchange) sound utility (included in all modern Linux distributions, e.g. packages "sox" and "libsox-fmt-oss" in Ubuntu)
* in newer Versions of sox (e.g. shipped with current Ubuntu), the used parameters are no longer supported. You have to replace "-t nul /dev/null" with "-n" in line 19.

===The script===

{{CodeRef|tp-theft-basic}}

==Ideas for improvement==
Features awaiting contribution:

===Activation===
* Gnome and xscreensaver support (similarly to [http://fdd.com/software/radeon/lightwatch.pl lightwatch.pl]?)
* Monitor X server presence and make noise on sudden X server shutdown (i.e. catch {{key|ctrl}}{{key|alt}}{{key|backspace}} events).
* Monitor AC power and take it into account for alarm activation -- thieves seldom carry a UPS.
* Don't arm the alarm if movement of similar magnitude was happening also before the screensaver was auto-locked (the owner might be in a moving vehicle, etc.).
* Disarm the alarm (or hold it off for a few seconds, as already implemented for lid open) based on voice/sound recognition using the built-in microphone.
* Use fingerprint reader to disarm the alarm.

===Precaution===
* Disable the alarm when headphones are plugged in -- it may cause hearing damage (if the user ignores the initial warning), and won't be effective anyway. '''Can we detect whether the something is plugged into the headphones/line-out socket?'''
* Theft attempts may be accompanied by rough handling, especially when the siren kicks in. So when starting an alarm also park the disk heads. Release the parking when a key is pressed (according {{path|/sys/bus/platform/drivers/hdaps/hdaps/keyboard_activity}}) so that the login prompt can start up. This requires kernel support for disk head parking and queue freezing, currently developed for the (original) HDAPS functionality.

===Indication===
* Use XOSD to ivisually ndicate state changes.
* Use TrayIcon to indicate state changes.
* Use Notifications to indicate state changes.

===Lockdown===
* Disable the volume buttons when the script is running so that a thief can't just turn the volume down. (Not an issue when <tt>ibm_acpi</tt> volume control is available - see [[#Prerequisites|Prerequisites]].)
* Disable suspend and powersaving measures when armed.
* Disable poweroff (to the extent possible) when armed - or at least use the two seconds the power button acpi function comes active before poweroff to make as much noise as possible (it may take a while for a casual thief to actully remove the battery).

===Alert===
* Start out quietly, and increase siren duration and volume if movement persists. Reset after a period of no movement.
* Report theft via network (if you get a chance to):
**Check for presence of wired or open wireless network and connect if not already connected.
**Send eMail to email to sms gateway or use an online sms service.
**If builtin webcam is present, take shots and upload them to a server or send via email. (This could be activated over a reboot, so that even if the thief gets away with the laptop, it would still be somewhat traceable.)
**If WAN of GPS devices are present, use it to detect position to a web server.
* When the alarm is triggered, also show a visual warning on the display. Override screensaver/powersaving if necessary. I.e., inform the thief that the notebook has a power on password and is useless without it. (This can be done by selecting a dedicated screensaver for that purpose.)
* Eject optical drive to irritate and hence slow down the thief.

===Other===
* Implement this functionality in the embedded controller, so that the alarm will work even when the laptop is suspended. It may be possible to do so without IBM/Lenovo's involvement, using the [http://forum.thinkpads.com/viewtopic.php?t=20958 embedded controller disassembly].
* On Ubuntu, some of the paths don't work. alsactl is in /sbin, not /usr/sbin, and pidof is in /bin, not /sbin. These probably shouldn't be hardcoded paths. (Fix: create symlinks)

==Pitfalls (and solutions?)==
* The audible alarm can always be suppressed by plugging earphones into the audio-jack (could be dealt with if software override for the audio-jack diversion is possible).
* The power button can be held to hard poweroff the notebook (can be avoided by using usb/bluetooth detection, closing the lid and sounding alarm if lid is opened before the usb/bluetooth device is present).
* The thief can unplug the battery to hard poweroff the notebook (can't do anything about it, but to set the alarm settings so that it goes off quickly - i.e., when using bluetooth detection, disable grace-period if activated manually)

==Another Script (plugin-based)==
there's another script with the same intention available at http://www.informatik.hu-berlin.de/~pilop/HOWTO_Gentoo_T43/#TheftAlarm

it uses a plugin-architecture for different checks (HDAPS, ethernet, power, lid, ...)

==Yet another script (python/gtk based)==
You can find yet another version of this script at

http://r3blog.nl/index.php/thinkpad-theft
(source at https://bitbucket.org/trbs/thinkpad-theft/overview/)

It has almost the same features as the comprehensive script above, with a few improvements. It uses dbus to query the screensaver status and gconf for storing configuration value. To improve the delay before the alarm sounds, it has a built-in wav player, and it opens the file-descriptor of the wav at startup time (thereby removing the need to spawn an application to play the alarm; imagine someone stealing your laptop while you're doing heavy disk io). Furthermore, it has a trayicon allowing you to manipulate most settings stored in gconf aswell as showing you the current status of the alarm. The 0.2 release features activation on missing presence of a bluetooth or usb device.

There is a [https://bitbucket.org/trbs/thinkpad-theft/overview new repository] at BitBucket that has seen some patches to fix problems with the unstable dbus-screensaver api and more.

==Conceptional thoughts==
The above feature improvement suggestions partly require the theft protection software to be running as root (ACPI and hardware management), partly to be running as user (DBus SessionBus communications). Hence the following approach would be the one opening for the most coverage:
*theft-protection-daemon; run as root by init; controlling config, system related activation, lockdown and alarm
*theft-protection-trayicon; run in user-session; reporting desktop related activation criteria to the daemon and giving visual user feedback on the desktop
*theft-protection-properties; runnable as user; reporting configuration changes to daemon

Ideally, they would provide a plugin-system, with plugins consisting of a functional and a gui part.
With this scheme, the theft protection can't be circumvented i.e. by pressing {{key|ctrl}}{{key|alt}}{{key|backspace}}.

[[Category:Scripts]]

Installation instructions for the ThinkPad T400

2009-11-24T10:27:00Z

Kiraven: /* Distro specific instructions */

Specific installation notes for the ThinkPad {{T400}}.

==General Notes==

==Distro specific instructions==

*[[Install Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T400]]

*[[Install Ubuntu 9.04 (Jaunty Jackalope) on a ThinkPad T400]]

*[[Install Ubuntu 9.10 (Karmic Koala) on a ThinkPad T400]]

==External Sources==

* [https://wiki.debian.org/InstallingDebianOn/Thinkpad/T400/lenny Debian/Lenny on ThinkPad T400]

* [http://clemensfam.org/john/?p=42 "Mostly Harmless Blog - Ubuntu 8.10 T400 install tips"]

* [http://sudan.ubuntuforums.com/showthread.php?t=941792 "Using HDMI interface with ati card and fgrlx on linux"]

Installation instructions for the ThinkPad T400

2009-10-08T16:31:17Z

Kiraven: /* Distro specific instructions */

Specific installation notes for the ThinkPad {{T400}}.

==General Notes==

==Distro specific instructions==

*[[Install Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T400]]

*[[Install Ubuntu 9.04 (Jaunty Jackalope) on a ThinkPad T400]]

*[[Install Ubuntu 9.10 (Karmic Koala) on a ThinkPad T400s]]

==External Sources==

* [https://wiki.debian.org/InstallingDebianOn/Thinkpad/T400/lenny Debian/Lenny on ThinkPad T400]

* [http://clemensfam.org/john/?p=42 "Mostly Harmless Blog - Ubuntu 8.10 T400 install tips"]

* [http://sudan.ubuntuforums.com/showthread.php?t=941792 "Using HDMI interface with ati card and fgrlx on linux"]

Script for theft alarm using HDAPS

2009-08-06T10:54:40Z

Kiraven:

==General==

Recent ThinkPad models include a built-in two-axis accelerometer, as part of the [[HDAPS]] feature. This accelerometer can be put to another use: as a laptop theft deterrent. The following scripts detect when the laptop is moved, and emits a loud audio alarm.

This alarm can be an effective deterrent against a casual laptop-snatcher in a populated environment (e.g., typical office space). It's also useful when you're across the room from the laptop and want to know if someone fiddles with it.

Note that the alarm is disabled when the laptop is suspended or powered off. You can buy external (hardware) motion detector alarms to handle those cases.

{{WARN|The audio alarm is played at a very high volume. Never enable the alarm while wearing headphones connected to the laptop's speaker output or when the laptop is connected to a high-power amplifier.}}

==A comprehensive script==

This Perl script periodically samples the tilt data reported by the accelerometer, computes the variance over recent samples, and triggers the alarm when the variance exceeds a given threshold.

On a ThinkPad with [[Active Protection System]] running a modern Linux installation with the [[HDAPS|hdaps]] kernel module loaded, the script should work as is. Just run {{cmdroot|tp-theft --arm}} and see (or rather, hear) what happens when you tilt your laptop.

The volume and alarm sound can be adjusted at the top of the script. On a ThinkPad {{T43}}, the synthetic siren at <tt>$alarm_volume=100</tt> (up from the default 70) is quite ear-splitting, and combined with <tt>$acpi_volume=15</tt> it is dangerously loud.

The script is designed to run continuously in the background, so by default the alarm will be activated only when the KDE screen saver is locked. If you you open the laptop lid (or press the lid button) shortly before or after the beginning of movement, the alarm will be suspended (except for a brief warning) and you will get a few seconds of grace to unlock the screen saver (preferably, [[How to enable the fingerprint reader|using the integrated fingerprint reader]]!). You can disable this functionality by passing the <tt>--arm</tt> parameter, by setting <tt>$use_kde=0</tt> and <tt>$use_lid=0</tt>, or by using the simpler script below.

There is also an option to track a BlueTooth device (e.g., a mobile phone). In this case, the alarm is activated (and optionally, the KDE desktop is locked) whenever the device is turned off or too distant for a given period, and deactivated when the BlueTooth device is nearby. You need to provide the device's BD address. If both KDE screen saver and BlueTooth checking are enabled, then the alarm will be activated when *either* the screensaver is enabled or the BlueTooth device is amiss.

===Prerequisites===

* ThinkPad with [[Active Protection System]]
* [[HDAPS|hdaps]] kernel module loaded (included in kernel 2.6.14 and later)
* Optional: [[ibm-acpi|ibm_acpi]] module loaded with the <tt>experimental=1</tt> parameter (included in kernel 2.6.14 and later; needed only for full volume control)
The following are included in all modern Linux distributions:
* ALSA sound system, <tt>alsactl</tt>, <tt>aplay</tt>, <tt>amixer</tt> )
* <tt>sox</tt> (SOund eXchange) sound utility

===The script===
{{CodeRef|tp-theft}}

==A basic script==

This is a simpler version of the above script, which omits the fancier functionality such as KDE screensaver detection, lid detection and state machine.

===Prerequisites===

* ThinkPad with [[Active Protection System]]
* [[HDAPS|hdaps]] kernel module loaded (included in kernel 2.6.14 and later)
* <tt>aumix</tt> mixer control utility (included in all modern Linux distributions)
* <tt>sox</tt> (SOund eXchange) sound utility (included in all modern Linux distributions)
* in newer Versions of sox (e.g. shipped with current Ubuntu), the used parameters are no longer supported. You have to replace "-t nul /dev/null" with "-n" in line 19.

===The script===

{{CodeRef|tp-theft-basic}}

==Ideas for improvement==
Features awaiting contribution:

===Activation===
* Gnome and xscreensaver support (similarly to [http://fdd.com/software/radeon/lightwatch.pl lightwatch.pl]?)
* Monitor X server presence and make noise on sudden X server shutdown (i.e. catch {{key|ctrl}}{{key|alt}}{{key|backspace}} events).
* Monitor AC power and take it into account for alarm activation -- thieves seldom carry a UPS.
* Don't arm the alarm if movement of similar magnitude was happening also before the screensaver was auto-locked (the owner might be in a moving vehicle, etc.).
* Disarm the alarm (or hold it off for a few seconds, as already implemented for lid open) based on voice/sound recognition using the built-in microphone.
* Use fingerprint reader to disarm the alarm.

===Precaution===
* Disable the alarm when headphones are plugged in -- it may cause hearing damage (if the user ignores the initial warning), and won't be effective anyway. '''Can we detect whether the something is plugged into the headphones/line-out socket?'''
* Theft attempts may be accompanied by rough handling, especially when the siren kicks in. So when starting an alarm also park the disk heads. Release the parking when a key is pressed (according {{path|/sys/bus/platform/drivers/hdaps/hdaps/keyboard_activity}}) so that the login prompt can start up. This requires kernel support for disk head parking and queue freezing, currently developed for the (original) HDAPS functionality.

===Indication===
* Use XOSD to ivisually ndicate state changes.
* Use TrayIcon to indicate state changes.
* Use Notifications to indicate state changes.

===Lockdown===
* Disable the volume buttons when the script is running so that a thief can't just turn the volume down. (Not an issue when <tt>ibm_acpi</tt> volume control is available - see [[#Prerequisites|Prerequisites]].)
* Disable suspend and powersaving measures when armed.
* Disable poweroff (to the extent possible) when armed - or at least use the two seconds the power button acpi function comes active before poweroff to make as much noise as possible (it may take a while for a casual thief to actully remove the battery).

===Alert===
* Start out quietly, and increase siren duration and volume if movement persists. Reset after a period of no movement.
* Report theft via network (if you get a chance to):
**Check for presence of wired or open wireless network and connect if not already connected.
**Send eMail to email to sms gateway or use an online sms service.
**If builtin webcam is present, take shots and upload them to a server or send via email. (This could be activated over a reboot, so that even if the thief gets away with the laptop, it would still be somewhat traceable.)
**If WAN of GPS devices are present, use it to detect position to a web server.
* When the alarm is triggered, also show a visual warning on the display. Override screensaver/powersaving if necessary. I.e., inform the thief that the notebook has a power on password and is useless without it. (This can be done by selecting a dedicated screensaver for that purpose.)
* Eject optical drive to irritate and hence slow down the thief.

===Other===
* Implement this functionality in the embedded controller, so that the alarm will work even when the laptop is suspended. It may be possible to do so without IBM/Lenovo's involvement, using the [http://forum.thinkpads.com/viewtopic.php?t=20958 embedded controller disassembly].
* On Ubuntu, some of the paths don't work. alsactl is in /sbin, not /usr/sbin, and pidof is in /bin, not /sbin. These probably shouldn't be hardcoded paths. (Fix: create symlinks)

==Pitfalls (and solutions?)==
* The audible alarm can always be suppressed by plugging earphones into the audio-jack (could be dealt with if software override for the audio-jack diversion is possible).
* The power button can be held to hard poweroff the notebook (can be avoided by using usb/bluetooth detection, closing the lid and sounding alarm if lid is opened before the usb/bluetooth device is present).
* The thief can unplug the battery to hard poweroff the notebook (can't do anything about it, but to set the alarm settings so that it goes off quickly - i.e., when using bluetooth detection, disable grace-period if activated manually)

==Another Script (plugin-based)==
there's another script with the same intention available at http://www.informatik.hu-berlin.de/~pilop/HOWTO_Gentoo_T43/#TheftAlarm

it uses a plugin-architecture for different checks (HDAPS, ethernet, power, lid, ...)

==Yet another script (python/gtk based)==
You can find yet another version of this script at

http://r3blog.nl/index.php/thinkpad-theft
(source at https://bitbucket.org/trbs/thinkpad-theft/overview/)

It has almost the same features as the comprehensive script above, with a few improvements. It uses dbus to query the screensaver status and gconf for storing configuration value. To improve the delay before the alarm sounds, it has a built-in wav player, and it opens the file-descriptor of the wav at startup time (thereby removing the need to spawn an application to play the alarm; imagine someone stealing your laptop while you're doing heavy disk io). Furthermore, it has a trayicon allowing you to manipulate most settings stored in gconf aswell as showing you the current status of the alarm. The 0.2 release features activation on missing presence of a bluetooth or usb device.

There is a [https://bitbucket.org/trbs/thinkpad-theft/overview new repository] at BitBucket that has seen some patches to fix problems with the unstable dbus-screensaver api and more.

==Conceptional thoughts==
The above feature improvement suggestions partly require the theft protection software to be running as root (ACPI and hardware management), partly to be running as user (DBus SessionBus communications). Hence the following approach would be the one opening for the most coverage:
*theft-protection-daemon; run as root by init; controlling config, system related activation, lockdown and alarm
*theft-protection-trayicon; run in user-session; reporting desktop related activation criteria to the daemon and giving visual user feedback on the desktop
*theft-protection-properties; runnable as user; reporting configuration changes to daemon

Ideally, they would provide a plugin-system, with plugins consisting of a functional and a gui part.
With this scheme, the theft protection can't be circumvented i.e. by pressing {{key|ctrl}}{{key|alt}}{{key|backspace}}.

[[Category:Scripts]]

Talk:Script for theft alarm using HDAPS

2009-08-06T10:48:58Z

Kiraven:

Wonderful idea! And works perfectly on my T43p, scared the cat away. ;)

--[[User:Spiney|spiney]] 20:35, 12 Nov 2005 (CET)
----

Good, so it's at least a cat deterrant! A friend of mine had a nasty incident involving a laptop and a cat...
BTW, I'm the author (identifed by IP address again due the usual ThinkWiki autologin flakiness).

--[[User:Thinker|Thinker]] 20:52, 12 Nov 2005 (CET)
----
I had to tweak the line that reads the position file. My position file has - numbers in it for some reason, so:
m/^$-(\d+),-(\d+)$$/ or die "Can't parse $pos_file content\n";

After that change it works great.
It scared the dogs away here. ;)
--[[User:nirik|nirik]] 21:24, 12 Nov 2005 (CET)
----

Fixed. Which ThinkPad model, BTW?

--[[User:Thinker|Thinker]] 21:44, 12 Nov 2005 (CET)
----
Cool. Excellent. ;)

T42p here.

--[[User:Nirik|Nirik]] 21:45, 12 Nov 2005 (CET)
----

I love it! Great contributions, Thinker!

Of course, it is more proof-of-concept tough, as a thief can simply hit the "mute" button, or carry an old headphone plug with the actual headphones chopped off and stuff this quickly into the audio out jack. Don't leave your laptop unattended :) :)

--[[User:Gsmenden|Gsmenden]] 18:06, 28 Nov 2005 (CET)
----

Thanks! About muting, I'm not sure the mute button will work (I reset the mixer volumes every second), but the thief can certainly power off, or suspend, or pull out the AC and battery. But my hope is that the casual, uninformed laptop-snatcher will trigger the alarm for at least a few seconds, and if you're just down the hall or there are other people nearby, that's probably enough to save your laptop. Not as good as a real lock+alarm, but better than nothing, and pretty convenient when autoactivated by the screensaver (<tt>$use_kde=1</tt>).

--[[User:Thinker|Thinker]] 01:40, 29 Nov 2005 (CET)
----

someone asked if it's possible to watch out for gnome-screensaver.
- it is, using dbus-monitor (like explained on the gnome-screensaver faq page).

the following perl script

my $cmd = "dbus-monitor --session \"type='signal',interface='org.gnome.ScreenSaver',member='SessionIdleChanged'\"";

open (IN,"-|", "$cmd");

while (<IN>) {
if (m/^\s+boolean true/) {
print "screensaver is now active";
} elsif (m/^\s+boolean false/) {
print "screensaver is now inactive";
}
}

will print when gnome-screensaver goes active

The ugly part is

1. You can only find out once gnome-screensaver is going active or inactive, but not if it's active when the scripts is started.

2. I don't really know how to check if there is new output in <IN>, because something like my $cmdline=<IN>; will hang until there is new output (like when the screensaver is going (in)active).

--[[User:Mcgiver|Mcgiver]] 20:35, 12 Nov 2005 (CET)
----

==Usefulness for head parking==
Works great. Maybe we can the script for testing the disk park patches by Jon Escombe <lists@dresco.co.uk>
-- [[User:Ozi23]]
----

You can use it for testing, but note that the specific algorithm used in this script (threshold on standard deviation of samples during last second) is optimized for the theft deterrent situation. It is highly unsuitable for the head parking application, since it reacts too slowly -- by the it will recognize the movement, the disk heads will have already crashed. For head parking you'd need a low-latency algorithm, and preferably an in-kernel implementation to allow frequeny low-overhead polling, reduce latencies, and avoid accidentally spinning the disk ''up'' when loading or swapping in userspace stuff needed to spin the disk ''down''.

--[[User:Thinker|Thinker]] 20:20, 14 Nov 2005 (CET)
----

It's even worse that I thought. Check out the [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/aps2mst.pdf IBM white paper] - there's barely enough time to park the head, so in the Windows driver they're using some pretty fancy learning algorithm to deduce when movement deviates from "normal", to decide when to redefine "normal".

--[[User:Thinker|Thinker]] 19:08, 22 Nov 2005 (CET)
----

Good news every one .....
Just kidding. I've found the hdapsd package which acts as a deamon for the hdaps and uses the kernel patch by Jon Escombe. I havent tested it but some people
were able to get the protection system work. It seems to depend on the firmware of the harddrive. Its in early stage so be carefull.

http://lwn.net/Articles/154923/ (kernel patch)
http://bugs.gentoo.org/show_bug.cgi?id=100167 (hdapsd)

----

== Minor modifications ==

tp-theft.pl v0.33 is working fine here, but I have modified some parts:
* I made a change for kdesktop_lock since it is located in /usr/kde/<kde-version>/bin/ here (Gentoo-specific)
* I removed the check wether kdesktop is running. I start tp-theft.pl via inittab which will be up before I have logged in

-- satmd, 2005-12-25

What's Gentoo's way of finding out the KDE path? I suppose
my $bin = `which kdesktop_lock`;
won't work from an initscript because the PATH is not set up yet.

--[[User:Thinker|Thinker]] 23:38, 25 Dec 2005 (CET)

With Gentoo
/usr/bin/env kde-config --exec-prefix --expandvars
returns /usr/kde/3.5 . That looks general useable to me.
I do not use an initscript, but inittab
... with initscripts one could easily source /etc/profile or something.

-- satmd, 2005-12-25

Will an inittab script find <tt>kde-config</tt>, which is probably in {{path|/usr/kde/<kde-version>/bin/}} too? And if so, won't <tt>which kdedesktop_lock</tt> also work?

--[[User:Thinker|Thinker]] 00:56, 26 Dec 2005 (CET)

Did not work - both of them. Keeping my hardcoded value.
-- satmd, 2005-12-26 06:09 CET

== Is there a way do make something like this work on Windows? ==

see topic.

----
theoretically speaking yes, since the accelerometer must be readable in windows too.

But I doubt there is an easy way to find out how to read it.

You might want to decompile the ibm hdaps active protection script to find out.

--[[User:Mcgiver|Mcgiver]] 20:35, 12 Nov 2005 (CET)
----

== Debian/Ubuntu libsox dependencies ==

Just a little Debian/Ubuntu heads-up:

If you get this error:

''sox soxio: Can't open output file `/dev/dsp': unknown file type `ossdsp'''

...then try installing '''libsox-fmt-oss'''. This fixed the problem for me, on Debian Etch. I based this info off of an Ubuntu forum post... different problem, but the same error message:
http://ubuntuforums.org/showthread.php?t=740612

--[[User:ashank|Andy Shank]] 14:38, 13 Oct 2008 (MST)
----

== New Sox Version? ==

I got this error

''sox formats: no handler for given file type `nul'''

with current sox 14.2.0 in Debian unstable.

Replacing ''-t nul /dev/null'' with ''-t'' fixed it for me.
I'm not changing the script because I guess the majority is still using older sox.

--[[User:Defiant|Defiant]] 18:25, 23 April 2009 (UTC)

I have the same problem, but I don't understand your fix. ''sox -t -t ossdsp /dev/dsp synth 1.0 sine 2000-4000 sine 4000-2000
''→ ''sox formats: no handler for given file type `-t''
[[User:Kiraven|Kiraven]] 15:23, 1 May 2009 (UTC)

Any solution to this problem?

[[User:sigurd|sigurd]] 18:00, 19 May 2009 (UTC)

I replaced ''-t nul /dev/null'' with ''-n'', now, it's working. --[[User:Kiraven|Kiraven]] 10:48, 6 August 2009 (UTC)

Talk:Script for theft alarm using HDAPS

2009-05-01T15:23:33Z

Kiraven: