blob: 1e35eb6f4c927ae41462ffbdc8fd7538b79f3c68 (
plain)
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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <showard314@gmail.com>) id 1TCL9d-0005vB-KB
for bitcoin-development@lists.sourceforge.net;
Fri, 14 Sep 2012 01:57:13 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.175 as permitted sender)
client-ip=209.85.220.175; envelope-from=showard314@gmail.com;
helo=mail-vc0-f175.google.com;
Received: from mail-vc0-f175.google.com ([209.85.220.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1TCL9b-0005X9-6C
for bitcoin-development@lists.sourceforge.net;
Fri, 14 Sep 2012 01:57:13 +0000
Received: by vcdm8 with SMTP id m8so4667801vcd.34
for <bitcoin-development@lists.sourceforge.net>;
Thu, 13 Sep 2012 18:57:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.58.32.233 with SMTP id m9mr758663vei.23.1347587825354; Thu, 13
Sep 2012 18:57:05 -0700 (PDT)
Received: by 10.58.226.225 with HTTP; Thu, 13 Sep 2012 18:57:05 -0700 (PDT)
Date: Thu, 13 Sep 2012 21:57:05 -0400
Message-ID: <CANg8-dCUC=qEqBSay5VKdqZOwEnx_UxYrT2LbV+20Vb1FbCJ1A@mail.gmail.com>
From: Scott Howard <showard314@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.0 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(showard314[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (showard314[at]gmail.com)
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
0.3 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1TCL9b-0005X9-6C
Subject: [Bitcoin-development] separate out blockchain db and wallet to two
dirs?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 14 Sep 2012 01:57:13 -0000
This idea is from a Debian user [1].
What do you think of moving the > 2 GB db to $HOME/.cache/bitcoin and
leaving the wallet and other config files in $HOME/.bitcoin? This is
so backups can skip the .cache directory and the proposal follows the
freedesktop.org XDG Base Directory Specification [2]. Personal
info/settings stays in .bitcoin/ and everything that can be rebuilt
goes to .cache/bitcoin/ I know users can do a work around and set it
up themselves with symlinks, but interested in what you guys think.
Cheers,
Scott (Debian Developer but new to bitcoin)
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660286
[2] http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
|
