Rename binaries with dashes instead of underscores.

1 files changed, 16 insertions, 16 deletions

diff --git a/README b/README
index 7aa2be4..492790e 100644
--- a/README
+++ b/README
@@ -27,10 +27,10 @@ configure options:
 	events which will likely flood the log.
 
 --enable-socket (default: n)
-	Causes linpicker_server to listen on a local socket and enables
-	compilation of linpicker_cli which can be used to send commands to
-	linpicker_server.  Currently there is only one command which causes
-	linpicker_server to dump information about all views into the log.
+	Causes linpicker-server to listen on a local socket and enables
+	compilation of linpicker-cli which can be used to send commands to
+	linpicker-server.  Currently there is only one command which causes
+	linpicker-server to dump information about all views into the log.
 
 
 SETTING UP THE ENVIRONMENT AND GUESTS
@@ -63,19 +63,19 @@ this package does not currently include any as the ones used by the author are
 still under development.
 
 To use the "combined desktop" mode in which windows from multiple guests are
-combined, the "linpicker_track" program needs to be installed in each guest
+combined, the "linpicker-track" program needs to be installed in each guest
 and run as part of the guest X session; see below.
 
 RUNNING LINPICKER
 
-Linpicker consists of three parts, linpicker_monitor, linpicker_server, and
-the optional linpicker_track.
+Linpicker consists of three parts, linpicker-monitor, linpicker-server, and
+the optional linpicker-track.
 
-linpicker_monitor is a non-graphical program that waits for new guests to
+linpicker-monitor is a non-graphical program that waits for new guests to
 start and sets up the backend information in XenStore.  This program needs to
 be started before any guests that are intended to be used with Linpicker.
 
-linpicker_server is the actual display server that maps the guest framebuffers
+linpicker-server is the actual display server that maps the guest framebuffers
 and provides the user interface.  It can also detect new guests starting up,
 but it does not write XenStore at all, it just listens passively.
 
@@ -84,20 +84,20 @@ Both programs have no command line arguments.  They will create log files in
 This is for two reasons, 1) /dev/fb0 typically needs root permission to open,
 and more importantly, 2) most of the Xen operations such as mapping grant
 references, touching XenStore, etc. require root.  Moving to a model in which
-linpicker_monitor handles _all_ Xen operations should allow linpicker_server
+linpicker-monitor handles _all_ Xen operations should allow linpicker-server
 to be unprivileged; this is on the TODO list.
 
-The typical way to run Linpicker is to run linpicker_monitor at boot time
-(before xendomains) and then run linpicker_server from the command line.
-To get back to the command line once linpicker_server is run one can either
-ssh from one of the guests, or exit linpicker_server and then re-run it.
+The typical way to run Linpicker is to run linpicker-monitor at boot time
+(before xendomains) and then run linpicker-server from the command line.
+To get back to the command line once linpicker-server is run one can either
+ssh from one of the guests, or exit linpicker-server and then re-run it.
 
-linpicker_track provides the extra information needed to use the combined
+linpicker-track provides the extra information needed to use the combined
 desktop mode with X-Windows guests.  It needs to be run as part of the guest
 X session, unfortunately, in order to communicate using Xen primitives it
 needs to be run as root!  This could be done using setuid or sudo.  It works
 by passively tracking window position and location and forwarding this
-information to linpicker_server using a ring buffer.
+information to linpicker-server using a ring buffer.
 
 
 HISTORY OF LINPICKER