Jesse Off wrote:
> /dev/random garbage is generated by what the kernel developers thought of as random
>events. The
> timing between keystrokes and interrupts (mouse) are used as a seed. While it does
>become active
> and spew out garbage when you hit the keyboard and mouse, I'm pretty sure thats not
>the only events
> that drive it. Besides, if you have a daemon process in the background with
>/dev/random open, I
> am not sure if another process can open it.
I was only using /dev/random as an example of a device file that has the ability
to tap into the input stream and make use of that.
To actually *USE* /dev/random, and just piggyback off of it's input tapping
capabilities for a screensaver would be extremely poor form / very bad design.
I was just saying that if /dev/random can tap into the input stream, why not
let's construct a device file called /dev/input-monitor that keeps tabs on the
last time an input event was generated by certain input devices.
Heh, a device file that keeps tabs on other device files :)
Watch out, the MCP is coming back...
Hey, and while we're at it, let's have a device file that does nothing but, when
read, spits out all the characters that are typed in... like "script" does.
Heheh, I know it might be unethical to actually monitor your "guests"
keystrokes, but hey, who said ethics has anything to do with the technical
ability to do something :)
Brock
+------------------------/----------------------------------------------------+
| R. Brock Lynn / My uptime is 20 days, what's yours? |
| [EMAIL PROTECTED] / http://www.kirch.net/unix-nt.html Live free or die. |
+---------------------/-------------------------------------------------------+
