Added an INSTALL.Debian file with Debian-specific instructions on

how to build and install a package file.


git-svn-id: https://shellinabox.googlecode.com/svn/trunk@87 0da03de8-d603-11dd-86c2-0f8696b7b6f9

ChangeLog

@@ -1,3 +1,8 @@
+2009-03-23  Markus Gutschke  <markus@shellinabox.com>
+
+	* Added an INSTALL.Debian file with Debian-specific instructions on
+	how to build and install a package file.
+
 2009-03-21  Markus Gutschke  <markus@shellinabox.com>
 
 	* Possible fix for IE problems with horizontal positioning of

INSTALL.Debian

@@ -0,0 +1,62 @@
+You can build package files for Debian based distributions (including Ubuntu)
+by running the standard build commands:
+
+  # Install build dependencies
+  i="$(dpkg-checkbuilddeps 2>&1 | sed -e 's/.*dependencies: //;t;d')"
+  [ -n "$i" ] && sudo apt-get install $i
+
+  # Build package files
+  dpkg-buildpackage
+
+These commands replace "./configure" and "make", which you would run on
+non-Debian systems.
+
+If you have a very old Debian system, you might have to use "fakeroot
+dpkg-buildpackage", instead of just "dpkg-buildpackage".
+
+If you want HTTPS support, and if you want the ability to run "shellinaboxd"
+as a non-privileged user, you should now install these run-time libraries:
+
+  sudo apt-get install libssl0.9.8 libpam0g openssl
+
+Running "dpkg-buildpackage" puts package files into your parent directory.
+You can install them with:
+
+  sudo dpkg -i ../shellinabox_*.deb
+
+You can now connect to your new shell at:
+
+  http://localhost:4200
+
+In contrast to installation by "make install", this package file creates
+files that are manage by the system tools. This allows it to install
+configuration files in "/etc" and to automatically start the daemon.
+
+You can configure the daemon process by editing "/etc/default/shellinabox".
+
+You can also provide SSL certificates for your site by installing them in
+"/var/lib/shellinabox". By default, the system will install self-signed
+certificates for you. These certificates are likely to raise warnings when
+you point your browser to the site.
+
+At the very least, you need a file called "certificate.pem" that includes
+both the private key and the public certificate PEM (i.e. ASCII) format.
+Additionally, you should create files for each of the publically visible
+hostnames that your machine has. These are named "certificate-${FQDN}.pem".
+You probably also want "certificate-localhost.pem".
+
+After you make any configuration changes, you need to restart the daemon by
+running:
+
+  sudo /etc/init.d/shellinabox restart
+
+If you want to know which files were installed by the package, run
+
+  dpkg -L shellinabox
+
+If you want to uninstall it again, run:
+
+  sudo apt-get remove shellinabox
+
+For all other administrative tasks, refer to the documentation that came
+with your system.

config.h

@@ -95,7 +95,7 @@
 #define STDC_HEADERS 1
 
 /* Most recent revision number in the version control system */
-#define VCS_REVISION "86"
+#define VCS_REVISION "87"
 
 /* Version number of package */
 #define VERSION "2.5"

configure

@@ -2055,7 +2055,7 @@ ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $
 ac_compiler_gnu=$ac_cv_c_compiler_gnu
 
 
-VCS_REVISION=86
+VCS_REVISION=87
 
 
 cat >>confdefs.h <<_ACEOF

configure.ac

@@ -2,7 +2,7 @@ AC_PREREQ(2.57)
 
 dnl This is the one location where the authoritative version number is stored
 AC_INIT(shellinabox, 2.5, markus@shellinabox.com)
-VCS_REVISION=86
+VCS_REVISION=87
 AC_SUBST(VCS_REVISION)
 AC_DEFINE_UNQUOTED(VCS_REVISION, "${VCS_REVISION}",
                    [Most recent revision number in the version control system])