Rename the script to slackupgrade

1 files changed, 14 insertions, 14 deletions

diff --git a/README b/README
index 243458d..fcd346c 100644
--- a/README
+++ b/README
@@ -1,18 +1,18 @@
 Overview
 ========
 
-This package provides slackware-upgrade-system, a script that performs
-a full upgrade of a Slackware distribution.
+This package provides slackupgrade, a script that performs a full
+upgrade of a Slackware distribution.
 
 Installation
 ============
 
-Run "make install" as root.  The slackware-upgrade-system will be
-installed to /sbin, and its man page, slackware-upgrade-system.8, to
+Run "make install" as root.  The slackupgrade script will be
+installed to /sbin, and its man page, slackupgrade.8, to
 /usr/man/man8.  These are most suitable locations for Slackware.  To
 install them elsewhere, use the following Makefile variables:
 
- SBINDIR  - Directory to install slackware-upgrade-system to.
+ SBINDIR  - Directory to install slackupgrade to.
  MANDIR   - toplevel directory for man page installation (/usr/man).
  MAN8DIR  - directory for the man page installation ($(MANDIR)/man8).
 
@@ -24,17 +24,17 @@ system.  When upgrading a remote machine, it advisable to have a KVM
 console attached to it, so that you can intervene if the box refuses
 to boot.
 
-Please read slackware-upgrade-system(8) to familiarize yourself with
+Please read slackupgrade(8) to familiarize yourself with
 the script and its options.
 
-Run slackware-upgrade-system in dry-run mode:
+Run slackupgrade in dry-run mode:
 
-  slackware-upgrade-system -n
+  slackupgrade -n
 
 This will look for the nearest next release available, create the list
 of packages to be upgraded, installed and removed and will print the
 results.  This run will not touch any files on your filesystem
-(excepting the slackware-upgrade-system logs, see below).  Instead it
+(excepting the slackupgrade logs, see below).  Instead it
 will verbosely print what would have been done during real upgrade.
 Inspect its output to see if it actually does what you need.  In
 particular, the upgrade will most likely decide to remove some
@@ -50,12 +50,12 @@ man page for details).
 To provide a replacement for a particular package, use the -p option.
   
 For your information, the list of removed packages is left in file
-/var/log/slackware-upgrade-system-<P>-<N>.removed (see below).
+/var/log/slackupgrade-<P>-<N>.removed (see below).
 
 When you are finished with the dry run, proceed to the actual upgrade.
 Run
 
-  slackware-upgrade-system
+  slackupgrade
 
 with any additional options you decided to give it after the dry run.
 After completion, the script will create three files for your
@@ -63,17 +63,17 @@ consideration.  In the discussion below, <P> stands for the original
 Slackware version number, and <N> stands for the new Slackware version
 number (the version you upgraded to):
 
-/var/log/slackware-upgrade-system-<P>-<N>.log
+/var/log/slackupgrade-<P>-<N>.log
   Log file.  Contains detailed transcript of all actions performed
   during the upgrade.
   
-/var/log/slackware-upgrade-system-<P>-<N>.removed
+/var/log/slackupgrade-<P>-<N>.removed
   A list of packages removed during the upgrade.  A package is removed
   if the new release does not provide a replacement for it.  This may
   not always be desirable, and you may reinstall some of them
   afterward.
   
-/var/log/slackware-upgrade-system-<P>-<N>.conffiles  
+/var/log/slackupgrade-<P>-<N>.conffiles  
   A list of configuration file replacements created during the upgrade.
   These are configuration files provided by the upgraded packages that
   are left in the filesystem along with your current file versions.