From: Justus Ranvier <justusranvier@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] About the small number of bitcoin nodes
Date: Mon, 19 May 2014 09:25:07 +0200 [thread overview]
Message-ID: <5379B1D3.6070509@localhost.local> (raw)
In-Reply-To: <CAJHLa0ODAUCpG8D7AMpsmi5bL9r_7KS711OC7HSzeeyTKoheXg@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/19/2014 09:11 AM, Jeff Garzik wrote:
> Meh. I like example configs, perhaps tuned by the distro. If the
> distro (_not_ Bitcoin Core upstream) chooses to install a
> bitcoin.conf in the proper location, that's up to them.
>
>
>> - bitcoind and Bitcoin Core should be in Linux repos:
>
> Agreed with conditions: 1) The distro MUST let bitcoin devs dictate
> which dependent libs are shipped with / built statically into the
> bitcoin binaries/libs. 2) The distro MUST permit fresh updates even
> to older stable distros. 2) The maintainer(s) MUST be active, and
> follow bitcoin development, release status, etc. on a near-daily
> basis, be able to respond quickly if security issues arise, etc.
If we're talking about making bitcoind behave like a proper daemon,
then syslog support should be on the list.
Also, the option to store things in FHS-compliant directories (not
somewhere/.bitcoin)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTebHTAAoJEMP3uyY4RQ2170IIAMDcx5rj/ZlCTJTOJ2sFttFM
miK9t7oewJ73UpgvFniCUngfjk9Tt5knmskQYEMQ5C9Do/P3Deh1gF6MBBuuai5G
kDNDv51zMEqhwGcqGrPYFMV3NEnBEjullTMgJFvKJf1kZRo7uplwp+eUhILjgSY5
mZjLIUK8iKDNn+Pi8/2UetAvyaRibHAsAnkJnEeOoKAhxUbtzjgZsj08loCCmJrs
RleOTLgArdc33e1bwTTwsS9DDvF18RNTACglsc75Oz0ohHyc5U1A1hBfaRuyu6Fv
8BK+0KPg/zdBCnM1m3aueVukg9p3kIfB2VUVFBHBTo4CPMi91k6oldbfRHy8dXw=
=SjxO
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-05-19 7:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-18 17:43 Raúl Martínez
2014-05-18 20:15 ` Raúl Martínez
2014-05-19 7:11 ` Jeff Garzik
2014-05-19 7:25 ` Justus Ranvier [this message]
2014-05-19 14:02 ` Scott Howard
2014-05-19 8:48 ` Wladimir
2014-05-19 10:39 ` Wladimir
2014-05-19 10:47 ` Felipe Micaroni Lalli
2014-05-19 9:26 ` Bjørn Øivind Bjørnsen
2014-05-19 12:15 ` Mike Hearn
2014-05-19 12:24 ` Bjørn Øivind Bjørnsen
2014-05-19 12:28 ` Mike Hearn
2014-05-19 12:44 ` Wladimir
2014-05-19 12:53 ` Mike Hearn
2014-06-30 10:16 ` Wladimir
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=5379B1D3.6070509@localhost.local \
--to=justusranvier@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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