From: Brian Warner Date: Sun, 30 Oct 2011 17:44:11 +0000 (-0700) Subject: quickstart.rst: remove trailing whitespace X-Git-Tag: allmydata-tahoe-1.9.0~9 X-Git-Url: https://git.rkrishnan.org/vdrive/%22news.html/module-simplejson-index.html?a=commitdiff_plain;h=b952d9dc1b755e33da94a12a0acac060a613e6f3;p=tahoe-lafs%2Ftahoe-lafs.git quickstart.rst: remove trailing whitespace --- diff --git a/docs/quickstart.rst b/docs/quickstart.rst index 6ecc987f..35d44761 100644 --- a/docs/quickstart.rst +++ b/docs/quickstart.rst @@ -2,40 +2,40 @@ Getting Tahoe-LAFS ================== -Welcome to `the Tahoe-LAFS project `_, a secure, -decentralized, fault-tolerant storage system. `About Tahoe-LAFS +Welcome to `the Tahoe-LAFS project `_, a secure, +decentralized, fault-tolerant storage system. `About Tahoe-LAFS `_. How To Get Tahoe-LAFS ===================== -This procedure has been verified to work on Windows, Mac, OpenSolaris, -and too many flavors of Linux and of BSD to list. It's likely to work +This procedure has been verified to work on Windows, Mac, OpenSolaris, +and too many flavors of Linux and of BSD to list. It's likely to work on other platforms. In Case Of Trouble ------------------ -There are a few 3rd party libraries that Tahoe-LAFS depends on that -might not be easy to set up on your platform. If the following -instructions don't Just Work without any further effort on your part, -then please write to `the tahoe-dev mailing list -`_ where -friendly hackers will help you out. You might also find clues in the +There are a few 3rd party libraries that Tahoe-LAFS depends on that +might not be easy to set up on your platform. If the following +instructions don't Just Work without any further effort on your part, +then please write to `the tahoe-dev mailing list +`_ where +friendly hackers will help you out. You might also find clues in the `Advanced Installation`_ section described below. Install Python -------------- -Check if you already have an adequate version of Python installed by -running ``python -V``. Python v2.4 (v2.4.4 or greater), Python v2.5, -Python v2.6, or Python v2.7 will work. Python v3 does not work. On -Windows, we recommend the use of Python v2.6 (native, not Cygwin). If -you don't have one of these versions of Python installed, then follow -the instructions on `the Python download page -`_ to download and -install Python v2.6. Make sure that the path to the installation -directory has no spaces in it (e.g. on Windows, do not install Python +Check if you already have an adequate version of Python installed by +running ``python -V``. Python v2.4 (v2.4.4 or greater), Python v2.5, +Python v2.6, or Python v2.7 will work. Python v3 does not work. On +Windows, we recommend the use of Python v2.6 (native, not Cygwin). If +you don't have one of these versions of Python installed, then follow +the instructions on `the Python download page +`_ to download and +install Python v2.6. Make sure that the path to the installation +directory has no spaces in it (e.g. on Windows, do not install Python in the "Program Files" directory). Get Tahoe-LAFS @@ -49,39 +49,39 @@ Set Up Tahoe-LAFS Unpack the zip file and cd into the top-level directory. -Run ``python setup.py build`` to generate the ``tahoe`` executable in a -subdirectory of the current directory named ``bin``. This will download +Run ``python setup.py build`` to generate the ``tahoe`` executable in a +subdirectory of the current directory named ``bin``. This will download and build anything you need from various websites. -On Windows, the ``build`` step might tell you to open a new Command -Prompt (or, on XP and earlier, to log out and back in again). This is -needed the first time you set up Tahoe-LAFS on a particular +On Windows, the ``build`` step might tell you to open a new Command +Prompt (or, on XP and earlier, to log out and back in again). This is +needed the first time you set up Tahoe-LAFS on a particular installation of Windows. -Optionally run ``python setup.py test`` to verify that it passes all -of its self-tests. +Optionally run ``python setup.py test`` to verify that it passes all of +its self-tests. -Run ``bin/tahoe --version`` (on Windows, ``bin\tahoe --version``) to +Run ``bin/tahoe --version`` (on Windows, ``bin\tahoe --version``) to verify that the executable tool prints out the right version number. Run Tahoe-LAFS -------------- -Now you are ready to deploy a decentralized filesystem. The ``tahoe`` -executable in the ``bin`` directory can configure and launch your -Tahoe-LAFS nodes. See `running.rst `_ for instructions on +Now you are ready to deploy a decentralized filesystem. The ``tahoe`` +executable in the ``bin`` directory can configure and launch your +Tahoe-LAFS nodes. See `running.rst `_ for instructions on how to do that. Advanced Installation --------------------- -For optional features such as tighter integration with your operating -system's package manager, you can see the `AdvancedInstall -`_ wiki page. -The options on that page are not necessary to use Tahoe-LAFS and can be -complicated, so we do not recommend following that page unless you have -unusual requirements for advanced optional features. For most people, -you should first follow the instructions on this page, and if that -doesn't work then ask for help by writing to `the tahoe-dev mailing +For optional features such as tighter integration with your operating +system's package manager, you can see the `AdvancedInstall +`_ wiki page. +The options on that page are not necessary to use Tahoe-LAFS and can be +complicated, so we do not recommend following that page unless you have +unusual requirements for advanced optional features. For most people, +you should first follow the instructions on this page, and if that +doesn't work then ask for help by writing to `the tahoe-dev mailing list `_.