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
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
|
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 <laanwj@gmail.com>) id 1TCORX-0004hA-35
for bitcoin-development@lists.sourceforge.net;
Fri, 14 Sep 2012 05:27:55 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.217.175 as permitted sender)
client-ip=209.85.217.175; envelope-from=laanwj@gmail.com;
helo=mail-lb0-f175.google.com;
Received: from mail-lb0-f175.google.com ([209.85.217.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1TCORW-0008TK-4b
for bitcoin-development@lists.sourceforge.net;
Fri, 14 Sep 2012 05:27:55 +0000
Received: by lban1 with SMTP id n1so2522504lba.34
for <bitcoin-development@lists.sourceforge.net>;
Thu, 13 Sep 2012 22:27:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.9.3 with SMTP id v3mr677410lba.32.1347600467569; Thu, 13
Sep 2012 22:27:47 -0700 (PDT)
Received: by 10.112.47.231 with HTTP; Thu, 13 Sep 2012 22:27:47 -0700 (PDT)
In-Reply-To: <CANg8-dCUC=qEqBSay5VKdqZOwEnx_UxYrT2LbV+20Vb1FbCJ1A@mail.gmail.com>
References: <CANg8-dCUC=qEqBSay5VKdqZOwEnx_UxYrT2LbV+20Vb1FbCJ1A@mail.gmail.com>
Date: Fri, 14 Sep 2012 07:27:47 +0200
Message-ID: <CA+s+GJChAYSDTV1GTKq+cqygyt1=DRdDsyaPbyNXpTiG51f1cw@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Scott Howard <showard314@gmail.com>
Content-Type: multipart/alternative; boundary=e0cb4efe2b182b2ab704c9a2af0b
X-Spam-Score: -0.6 (/)
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
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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
X-Headers-End: 1TCORW-0008TK-4b
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [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 05:27:55 -0000
--e0cb4efe2b182b2ab704c9a2af0b
Content-Type: text/plain; charset=UTF-8
On Fri, Sep 14, 2012 at 3:57 AM, Scott Howard <showard314@gmail.com> wrote:
> 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.
>
This is currently not feasible due to BerkelyDB limitations. All the
databases are within one 'environment', which is necessarily one directory
(it can probably be hacked around, but obviously we're really careful).
When LevelDB for the block chain and the custom format for the wallets is
introduces, various new configurations will be possible: Multiple wallets,
wallet in block chain in separate dirs, etc.
Wladimir
--e0cb4efe2b182b2ab704c9a2af0b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<br><br><div class=3D"gmail_quote">On Fri, Sep 14, 2012 at 3:57 AM, Scott H=
oward <span dir=3D"ltr"><<a href=3D"mailto:showard314@gmail.com" target=
=3D"_blank">showard314@gmail.com</a>></span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
This idea is from a Debian user [1].<br>
<br>
What do you think of moving the > 2 GB db to $HOME/.cache/bitcoin and<br=
>
leaving the wallet and other config files in $HOME/.bitcoin? This is<br>
so backups can skip the .cache directory and the proposal follows the<br>
<a href=3D"http://freedesktop.org" target=3D"_blank">freedesktop.org</a> XD=
G Base Directory Specification [2]. Personal<br>
info/settings stays in .bitcoin/ and everything that can be rebuilt<br>
goes to .cache/bitcoin/ I know users can do a work around and set it<br>
up themselves with symlinks, but interested in what you guys think.<br></bl=
ockquote><div><br></div><div>This is currently not feasible due to BerkelyD=
B limitations. All the databases are within one 'environment', whic=
h is necessarily one directory (it can probably be hacked around, but obvio=
usly we're really careful).</div>
<div><br></div><div>When LevelDB for the block chain and the custom format =
for the wallets is introduces, various new configurations will be possible:=
Multiple wallets, wallet in block chain in separate dirs, etc.</div><div>
<br></div><div>Wladimir</div><div><br></div></div>
--e0cb4efe2b182b2ab704c9a2af0b--
|
