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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <grarpamp@gmail.com>) id 1TCMBl-0008QM-Ou
for bitcoin-development@lists.sourceforge.net;
Fri, 14 Sep 2012 03:03:29 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.175 as permitted sender)
client-ip=209.85.214.175; envelope-from=grarpamp@gmail.com;
helo=mail-ob0-f175.google.com;
Received: from mail-ob0-f175.google.com ([209.85.214.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1TCMBk-0000ZS-Og
for bitcoin-development@lists.sourceforge.net;
Fri, 14 Sep 2012 03:03:29 +0000
Received: by obblz20 with SMTP id lz20so5956233obb.34
for <bitcoin-development@lists.sourceforge.net>;
Thu, 13 Sep 2012 20:03:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.164.103 with SMTP id yp7mr1312438obb.26.1347591803184;
Thu, 13 Sep 2012 20:03:23 -0700 (PDT)
Received: by 10.76.152.129 with HTTP; Thu, 13 Sep 2012 20:03:23 -0700 (PDT)
In-Reply-To: <CAMGNxUt8ic39pdq1zobSF0khR_vOixTDZMSixAhWTLd2hLMVAg@mail.gmail.com>
References: <CANg8-dCUC=qEqBSay5VKdqZOwEnx_UxYrT2LbV+20Vb1FbCJ1A@mail.gmail.com>
<CAD2Ti28-gxXwJF4MXEHO9o4_4Z7hsNM7T9XQRX1K8Q2OLmB+mw@mail.gmail.com>
<CAMGNxUt8ic39pdq1zobSF0khR_vOixTDZMSixAhWTLd2hLMVAg@mail.gmail.com>
Date: Thu, 13 Sep 2012 23:03:23 -0400
Message-ID: <CAD2Ti2-2ObsR243OaH1uioUAURWZ4+aXUYq9kLpjyMoBpdm1AA@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=UTF-8
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
(grarpamp[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.6 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1TCMBk-0000ZS-Og
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 03:03:29 -0000
Linux typically uses the FHS, which various distros often bastardize:
http://www.linuxfoundation.org/collaborate/workgroups/lsb/fhs
BSD typically uses the traditional hierarchy, for which admins
often add /home and /opt:
http://svnweb.freebsd.org/base/head/share/man/man7/hier.7?revision=HEAD&view=markup
You'd have to read them both and decide which camp you're in.
https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard
Since bitcoin isn't really an X app at it's core, XDG doesn't really
apply.
http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
Further, bitcoin doesn't allow easy separation of the files without
detachdb (off by default), nor does it supply a user agnostic system
daemon to do the block processing separately from user wallet ops.
So I would suggest until then it remain split up somewhere under
.bitcoin rather than in /var or anywhere else.
And when you figure out where I should place my messages in
full the first time, please let me know because I obviously need help.
|
