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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <theodore.witkamp@gmail.com>) id 1QWtxN-0006yD-8I
for bitcoin-development@lists.sourceforge.net;
Wed, 15 Jun 2011 17:32:45 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.47 as permitted sender)
client-ip=209.85.213.47;
envelope-from=theodore.witkamp@gmail.com;
helo=mail-yw0-f47.google.com;
Received: from mail-yw0-f47.google.com ([209.85.213.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1QWtxM-0003kP-Ff
for bitcoin-development@lists.sourceforge.net;
Wed, 15 Jun 2011 17:32:45 +0000
Received: by ywg8 with SMTP id 8so499732ywg.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 15 Jun 2011 10:32:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.236.175.99 with SMTP id y63mr1392831yhl.155.1308159159035;
Wed, 15 Jun 2011 10:32:39 -0700 (PDT)
Received: by 10.236.208.73 with HTTP; Wed, 15 Jun 2011 10:32:39 -0700 (PDT)
In-Reply-To: <BANLkTikFaYqvO5=A-eJwR7aBqau+ba5r9Q@mail.gmail.com>
References: <BANLkTikOEWZQur8EqumWH0jU=07-4vAFhg@mail.gmail.com>
<1B652E42-B585-4F51-ABAD-A74B45492084@gmail.com>
<BANLkTikFaYqvO5=A-eJwR7aBqau+ba5r9Q@mail.gmail.com>
Date: Wed, 15 Jun 2011 10:32:39 -0700
Message-ID: <BANLkTinKvkGb4S__9fczOSWadtGZTL87og@mail.gmail.com>
From: Theodore Witkamp <theodore.witkamp@gmail.com>
To: Jeff Garzik <jgarzik@exmulti.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.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 freemail
(theodore.witkamp[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-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.0 RFC_ABUSE_POST Both abuse and postmaster missing on sender domain
X-Headers-End: 1QWtxM-0003kP-Ff
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Release priorities for v0.4?
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: Wed, 15 Jun 2011 17:32:45 -0000
On Wed, Jun 15, 2011 at 9:50 AM, Jeff Garzik <jgarzik@exmulti.com> wrote:
> On Wed, Jun 15, 2011 at 10:27 AM, Mark Visser <mjmvisser@gmail.com> wrote=
:
>> I humbly suggest allowing the wallet.dat location to be specified in the=
preferences. Being able to easily physically disconnect a wallet by unplug=
ging a USB key seems like a good idea.
>
> That's what -datadir is for. =C2=A0Unfortunately -all- databases must be =
in
> the datadir, because wallet.dat is a berkeley db, and we need a
> transactional environment. =C2=A0That makes it difficult to move just one
> file.
I am a Berkley DB ignoramus , but how is specifying the wallet file
path different than using a symlink?
Also I think that allowing the user to open more than one wallet helps
the user develop an intuition for the system.
A simple task like opening transferring coins from one to the other is
currently very awkward on the same installation.
Ted
|
