From: Fred Concklin <fconcklin@trucoin.com>
To: Douglas Huff <dhuff@jrbobdobbs.org>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Introduction
Date: Mon, 22 Aug 2011 23:26:53 -0400 [thread overview]
Message-ID: <4E531DFD.1070407@trucoin.com> (raw)
In-Reply-To: <CAPiTikUaZbp0t2aYBoJ4w+uvEh=PHorXXLtzkATaOvbUt9qTtw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1652 bytes --]
Thanks for the warm welcome...
I was specifically referring to building with autotools as a starting
point. Primarily autoconf to ease the installation and testing process.
On 08/22/2011 04:12 PM, Douglas Huff wrote:
> I don't think you're actually familiar with either of those tools. A run
> script is not much different than an init script?
In this regard I was referring to running bitcoin in /etc/init.d on
Debian based systems. By init script, I was referring to making scripts
run at boot time.
> Those who live in tonal caves shouldn't crap on themselves, or something.
>
> On Aug 22, 2011 2:49 PM, "Luke-Jr" <luke@dashjr.org> wrote:
>> On Monday, August 22, 2011 3:30:04 PM Douglas Huff wrote:
>>> On Aug 22, 2011 2:26 PM, "Fred Concklin" <fconcklin@trucoin.com> wrote:
>>>> I'm also interested in work to daemonize bitcoin on boot and
> furthering
>>>> work to bring bitcoin into general coding and implementation paradigms
>>>> seen on GNU/Linux platforms.
>>> What? It already works fine in this regard using standard tools.
> Especially
>>> easy with daemontools/runit.
>> He said standard *coding and implementation paradigms*. This has nothing
> to do
>> with integration with some non-standard "init replacement" that goes
> against
>> the whole design of Unix.
>>
>> What I understand this to mean, is properly abstracting the components
> such
>> that the node, wallet, and GUI can work together while being distinct
> parts.
>> In this sense, Fred, you may be interested in working on coming up with a
>> standard for a https://en.bitcoin.it/wiki/Wallet_protocol
I'll check this out.
fpc
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-08-23 3:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 19:02 [Bitcoin-development] Introduction Fred Concklin
2011-08-22 19:30 ` Douglas Huff
2011-08-22 19:49 ` Luke-Jr
2011-08-22 20:12 ` Douglas Huff
2011-08-23 3:26 ` Fred Concklin [this message]
2011-08-23 3:42 ` Jay Weisskopf
2011-08-23 4:20 ` Fred Concklin
2011-08-22 20:45 ` Matt Corallo
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=4E531DFD.1070407@trucoin.com \
--to=fconcklin@trucoin.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=dhuff@jrbobdobbs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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