Initial v0.1.0 public commit. Everything works. :)

git-svn-id: https://logkeys.googlecode.com/svn/trunk@2 c501e62c-e7d1-11de-a198-37193048d1ed
kernc · Dec 13, 2009 · 045803af65866862b42fea3fb33cde61b3ec408f · 045803a
1 parent ec16a28
commit 045803af65866862b42fea3fb33cde61b3ec408f
diff --git a/COPYING b/COPYING
@@ -0,0 +1,15 @@
+  
+            DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
+  
+                    Version 2, December 2004
+  
+
+  
+ Copyright (C) 2004 Sam Hocevar
+  
+  14 rue de Plaisance, 75014 Paris, France
+  
+
+  
+ Everyone is permitted to copy and distribute verbatim or modified
+  
+ copies of this license document, and changing it is allowed as long
+  
+ as the name is changed.
+  
+
+  
+            DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
+  
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+  
+
+  
+  0. You just DO WHAT THE FUCK YOU WANT TO.
+  
+
diff --git a/INSTALL b/INSTALL
@@ -0,0 +1,41 @@
+  
+===============================================================================
+  
+ logkeys keylogger - instalation instructions
+  
+===============================================================================
+  
+
+  
+Provided your GNU/Linux distribution doesn't include logkeys package in its
+  
+repositories, manual installation of logkeys from source is as easy as:
+  
+
+  
+ $ tar xvzf logkeys-0.1.0.tar.gz   # to extract the logkeys archive
+  
+
+  
+ $ cd logkeys-0.1.0/build  # move to build directory to build there
+  
+ $ ../configure            # invoke configure from parent directory
+  
+ $ make                    # make compiles what it needs to compile
+  
+ ( become superuser now )  # you need root to install in system dir
+  
+ # make install            # installs binaries, manuals and scripts
+  
+
+  
+That's it. If everything went through fine, you can probably start using it.
+  
+
+  
+See README file for usage instructions and notes.
+  
+
+  
+
+  
+To install the binaries in path other than /usr/local/bin, use configure with
+  
+--prefix switch, for example:
+  
+
+  
+ $ ../configure --prefix=/usr
+  
+
+  
+Along with other standard configure options, you can also use:
+  
+
+  
+ $ ../configure --enable-evdev-path=PATH
+  
+
+  
+to have logkeys look for input event devices in PATH ( $(PATH)/eventX ) instead
+  
+of preconfigured default /dev/input (/dev/input/eventX), and
+  
+
+  
+ $ ../configure --enable-evdev=DEV
+  
+
+  
+to have logkeys define static event device DEV (i.e. /dev/input/eventX) instead
+  
+of looking for it in default /dev/input path or custom evdev-path.
+  
+
+  
+The input event device we are referring to, here, is the kernel event interface
+  
+echoing keyboard events. If using either of these two --enable-evdev*
+  
+switches, make sure you provided correct PATH/DEV.
+  
+
diff --git a/Makefile.am b/Makefile.am
@@ -0,0 +1,3 @@
+  
+AUTOMAKE_OPTIONS = foreign
+  
+SUBDIRS = src man scripts
+  
+EXTRA_DIST = build man/logkeys.8 scripts/lkl scripts/lklk