From: Wladimir <laanwj@gmail•com>
To: Scott Howard <showard314@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] separate out blockchain db and wallet to two dirs?
Date: Fri, 14 Sep 2012 07:27:47 +0200 [thread overview]
Message-ID: <CA+s+GJChAYSDTV1GTKq+cqygyt1=DRdDsyaPbyNXpTiG51f1cw@mail.gmail.com> (raw)
In-Reply-To: <CANg8-dCUC=qEqBSay5VKdqZOwEnx_UxYrT2LbV+20Vb1FbCJ1A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1463 bytes --]
next prev parent reply other threads:[~2012-09-14 5:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 1:57 Scott Howard
2012-09-14 2:15 ` grarpamp
2012-09-14 2:18 ` Peter Vessenes
2012-09-14 2:59 ` grarpamp
2012-09-14 3:03 ` grarpamp
2012-09-14 5:27 ` Wladimir [this message]
2012-09-14 7:40 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+s+GJChAYSDTV1GTKq+cqygyt1=DRdDsyaPbyNXpTiG51f1cw@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=showard314@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox