1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
|
@title = 'Bitmask for Linux'
@nav_title = 'Linux'
<%= 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.
*From packages*: If you are running from packages, then you can trigger an update like so:
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"
This is because the Ubuntu upgrade process probably commented out all your prior custom repository lines in @/etc/apt/sources.list@.
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.04 (Vivid Vervet)
<%= render({:partial => 'via_packages'}, {:distro => 'vivid'}) %>
h3. Ubuntu 14.04 LTS (Trusty Tahr)
<%= render({:partial => 'via_packages'}, {:distro => 'trusty'}) %>
h3. Debian 7.0 (Wheezy)
<%= render({:partial => 'via_packages'}, {:distro => 'wheezy', :os => 'debian'}) %>
h3. Debian 8.0 (Jessie)
<%= render({:partial => 'via_packages'}, {:distro => 'jessie', :os => 'debian'}) %>
h2. Install stand-alone bundle
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).
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.
Optionally, you can [[authenticate the signature => signature-verification]] for the Bitmask files before you run them.
How do you tell if you running a 32 bit or 64 bit kernel? Run the following command:
bc. uname -m
If the result is:
* @x86_64@, you have *64 bit*
* @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'}) %>
[[Signature file => https://dl.bitmask.net/client/linux/stable/Bitmask-linux64-latest.tar.bz2.asc]]
h3. Other options
You can [[browse all releases => https://dl.bitmask.net/client/linux/]] for old or experimental downloads.
You should install the latest stable release. Downloads tagged with "RC" are "Release Candidates" and receive frequent experimental updates that may break the application.
|
