|
|
-
-
- Many things in selfbondage can go wrong
but one the most common things that fail is the release method.
- The release method is the way that you
chose for delivering the keys to your hands so that you will
be able to free yourself. This text lists some of the computer
based release methods.
- There are no 100% safe releases.
- Micros*ft Media Player Release.
(It probably works with other player
too.)
Description: "Using windows media player you can
get your cd-rom to open after a random ammount of time when you
rip a cd. Just make sure you click the option to eject cd when
finished. The more songs on the cd the longer the time. Stick
a string in the cd rom so it will drop your keys when it opens.
Easy." /submitted by an anonymous user.
-
- Minuses:
Relying in a computer for delivering your release is very dangerous.
And combining that danger to that of using any software from
micros*ft will probably send shivers down the back of most people.
However, no release should ever be used alone and this is no
exemption. So perhaps it could be a good idea for a primary release
method. Just make sure you use a fail-safe secondary release.
-
- Linux CD Tray Release: (See below for improved versions)
For those who are running Linux on their PC there's a very nice
an simple release method. Open a terminal window and type for
example: sleep 600 && eject <ENTER> This means
that your PC waits a certain time 600 seconds in the example
shown above an then it ejects your CD drive. Nice an simple I
think. But before you use this release method make sure it works.
<ENTER> means press the enter key ;-) /submitted by an
anonymous user.
-
- Minuses:
See above.
-
- A reader sent me the folowing improvment.
- Hi Anna. Just wanted to suggest a modification
to your Linux CD Eject line. In your example: $ sleep 600 &&
eject cdrom
- It will only execute the eject if sleep
closes without error. If you mistype sleep, maybe forget the
space between the command and the variable, it won't execute
the eject sequence. Or for any other reason, highly unlikely,
that the sleep command fails. My suggestion:
- $ sleep 600 ; eject cdrom
- If the sleep command fails, eject will
still be executed.
-
- *Please note the $ sign indicates the
terminal prompt, and need not be typed in.
-
-
- Another reader sent me yet another
way of doing this:
- With the sleep command it might be better
to rely on the s, m, h, and d suffix's.
- Instead of using "$ sleep 600 ; eject
cdrom" you can use "$ sleep 10m ; eject cdrom".
- Which one requires less mental math? The
10m. This way you are less likely to put an unwanted additional
0.
- My next suggestion is a bit more complex
then the first two suggestions on your site, but it allow you
to set a random timer:
-
- Example 1:
$ sleep $[($RANDOM % 45)+15]m ; eject cdrom
- The above line will open the cd tray sometime
between 15 minutes and 1 hour.
- There are two timers you can adjust here:
the '15' (the minimum) and
the '45' (the maximum random), adjust them to your liking.
-
- Example 2:
$ sleep $[($RANDOM % 8)+4]h ; eject cdrom
- The above line will open the cd tray sometime
between 4 hours and 12
hours. The anticipation is amazing.
- Again, you can adjust the '4' and '8',
but if you carefully read the
line you'll notice that I put a 'h' in this time.
-
- *Please note the $ sign indicates the
terminal prompt, and need not be typed in.
-
- Disclaimer:
Test the above commands before relying on them. If you don't
understand them, don't use them.
It's extremely easy to type 60m and actually put 600m. That's
9 hours worth of a difference, always have a backup release.
It's extremely easy to type 60m and actually put 60h. That's
59 hours worth of a difference, always have a backup release.
It's extremely easy to type 60m and actually put 60d. That's
1,439 hours worth of a difference, always have a backup release.
Power and hardware failures happen, always have a backup release.
|
