diff options
Diffstat (limited to 'pages/install/linux/en.text')
-rw-r--r-- | pages/install/linux/en.text | 67 |
1 files changed, 35 insertions, 32 deletions
diff --git a/pages/install/linux/en.text b/pages/install/linux/en.text index a300ced..05bda76 100644 --- a/pages/install/linux/en.text +++ b/pages/install/linux/en.text @@ -3,31 +3,24 @@ <%= render({:partial => 'common/notice'}, {:type => 'info', :text => '<b>NOTE:</b> Encrypted email support in Bitmask is still experimental.'}) %> -h2. Upgrading - -*From stand-alone bundles*: Bitmask should upgrade itself automatically (for versions equal or later than 0.7.0). If you are running a version prior to 0.7.0, you can download the new bundle and copy the "config" folder from the old bundle directory. +There are two ways to install Bitmask - via the stand-alone bundles or via packages. -*From packages*: If you are running from packages, then you can trigger an update like so: +h2. Download stand-alone bundle -bc. apt-get update -apt-get dist-upgrade - -NOTE: When upgrading Ubuntu from 14.10 (Utopic) to 15.04 (Vivid), you may need to run this command again: - -bc. sudo add-apt-repository "deb http://deb.bitmask.net/debian vivid main" +h3. 64 bit kernel -This is because the Ubuntu upgrade process probably commented out all your prior custom repository lines in @/etc/apt/sources.list@. +<%= render({:partial => 'common/download_button'}, {:link => 'https://dl.bitmask.net/client/linux/stable/Bitmask-linux64-latest.tar.bz2', :text => 'Download 64 bit'}) %> -h2. Install stand-alone bundle +[[Signature file => https://dl.bitmask.net/client/linux/stable/Bitmask-linux64-latest.tar.bz2.asc]] -Alternately, you can run Bitmask from a stand alone bundle. This is useful if want to run Bitmask from a thumb drive. The bundle should work on most recent Linux distributions that are derived from Debian (e.g. Ubuntu, Mint, Trisquel, etc). +h3. 32 bit kernel -There are two disadvantages to the stand-alone bundle: +<%= render({:partial => 'common/download_button'}, {:link => 'https://dl.bitmask.net/client/linux/stable/Bitmask-linux32-latest.tar.bz2', :text => 'Download 32 bit'}) %> -* The Bitmask app will be less well integrated with the desktop environment. -* Running from the bundle is slower to start than via packages. +[[Signature file => https://dl.bitmask.net/client/linux/stable/Bitmask-linux32-latest.tar.bz2.asc]] -Optionally, you can [[authenticate the signature => signature-verification]] for the Bitmask files before you run them. +If you want to make sure that the Bitmask wasn't messed with during download +you can [[authenticate the signature => signature-verification]]. How do you tell if you running a 32 bit or 64 bit kernel? Run the following command: @@ -39,34 +32,44 @@ If the result is: * @i686@, you have *32 bit* * @i386@, you have *32 bit* -h3. 32 bit kernel - -<%= render({:partial => 'common/download_button'}, {:link => 'https://dl.bitmask.net/client/linux/stable/Bitmask-linux32-latest.tar.bz2', :text => 'Download 32 bit'}) %> - -[[Signature file => https://dl.bitmask.net/client/linux/stable/Bitmask-linux32-latest.tar.bz2.asc]] - -h3. 64 bit kernel -<%= render({:partial => 'common/download_button'}, {:link => 'https://dl.bitmask.net/client/linux/stable/Bitmask-linux64-latest.tar.bz2', :text => 'Download 64 bit'}) %> +NOTE: + Stand-alone bundles are useful if want to run Bitmask from a thumb drive. Or from a distribution which we don't support with packages. + There are two disadvantages to the stand-alone bundle: + * The Bitmask app will be less well integrated with the desktop environment. + * Running from the bundle is slower to start than via packages. -[[Signature file => https://dl.bitmask.net/client/linux/stable/Bitmask-linux64-latest.tar.bz2.asc]] h2. Install as packages This is the recommended method of installing Bitmask. If installed as a package, Bitmask will run faster, be better integrated in the system, and will be kept up to date. +h3. Ubuntu 15.10 (Wily Werewolf) +<%= render({:partial => 'via_packages'}, {:distro => 'wily'}) %> + h3. Ubuntu 15.04 (Vivid Vervet) <%= render({:partial => 'via_packages'}, {:distro => 'vivid'}) %> -h3. Ubuntu 14.04 LTS (Trusty Tahr) +h3. Debian 8.0 (Jessie) -<%= render({:partial => 'via_packages'}, {:distro => 'trusty'}) %> +<%= render({:partial => 'via_packages'}, {:distro => 'jessie', :os => 'debian'}) %> -h3. Debian 7.0 (Wheezy) +h2. Upgrading -<%= render({:partial => 'via_packages'}, {:distro => 'wheezy', :os => 'debian'}) %> +*From stand-alone bundles*: Bitmask should upgrade itself automatically (for versions equal or later than 0.7.0). If you are running a version prior to 0.7.0, you can download the new bundle and copy the "config" folder from the old bundle directory. -h3. Debian 8.0 (Jessie) +*From packages*: If you are running from packages, then you can trigger an update like so: -<%= render({:partial => 'via_packages'}, {:distro => 'jessie', :os => 'debian'}) %> +bc. apt-get update +apt-get dist-upgrade + +NOTE: When upgrading Ubuntu from 14.10 (Utopic) to 15.04 (Vivid), you may need to run this command again: + +bc. sudo add-apt-repository "deb http://deb.bitmask.net/debian vivid main" + +Similar is needed for the upgrade from 15.04 to 15.10 (Wily): + +bc. sudo add-apt-repository "deb http://deb.bitmask.net/debian wily main" + +This is because the Ubuntu upgrade process probably commented out all your prior custom repository lines in @/etc/apt/sources.list@. |