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
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mith@jrbobdobbs.org>) id 1QvbHs-0005MV-Vv
for bitcoin-development@lists.sourceforge.net;
Mon, 22 Aug 2011 20:40:00 +0000
X-ACL-Warn:
Received: from mail-bw0-f47.google.com ([209.85.214.47])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1QvbHr-0004sg-Sg
for bitcoin-development@lists.sourceforge.net;
Mon, 22 Aug 2011 20:40:00 +0000
Received: by bkbzu17 with SMTP id zu17so6093450bkb.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 22 Aug 2011 13:39:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.204.143.130 with SMTP id v2mr1041104bku.18.1314043935553; Mon,
22 Aug 2011 13:12:15 -0700 (PDT)
Sender: mith@jrbobdobbs.org
Received: by 10.204.55.83 with HTTP; Mon, 22 Aug 2011 13:12:15 -0700 (PDT)
Received: by 10.204.55.83 with HTTP; Mon, 22 Aug 2011 13:12:15 -0700 (PDT)
In-Reply-To: <201108221549.44440.luke@dashjr.org>
References: <4E52A7BA.1030208@trucoin.com>
<CAPiTikVrw9QZAdmNwa5RCik+O4QvM4nGMZZx9Xc9L+XmtgX23w@mail.gmail.com>
<201108221549.44440.luke@dashjr.org>
Date: Mon, 22 Aug 2011 15:12:15 -0500
X-Google-Sender-Auth: yL1s_ScPgN8ahoNA6LXshcp-dso
Message-ID: <CAPiTikUaZbp0t2aYBoJ4w+uvEh=PHorXXLtzkATaOvbUt9qTtw@mail.gmail.com>
From: Douglas Huff <dhuff@jrbobdobbs.org>
To: Luke-Jr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=0015175caa56ff778704ab1db148
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1QvbHr-0004sg-Sg
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Introduction
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: Mon, 22 Aug 2011 20:40:01 -0000
--0015175caa56ff778704ab1db148
Content-Type: text/plain; charset=ISO-8859-1
I don't think you're actually familiar with either of those tools. A run
script is not much different than an init script?
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
--0015175caa56ff778704ab1db148
Content-Type: text/html; charset=ISO-8859-1
<p>I don't think you're actually familiar with either of those tools. A run script is not much different than an init script?</p>
<p>Those who live in tonal caves shouldn't crap on themselves, or something.</p>
<p>On Aug 22, 2011 2:49 PM, "Luke-Jr" <<a href="mailto:luke@dashjr.org">luke@dashjr.org</a>> wrote:<br>
><br>
> On Monday, August 22, 2011 3:30:04 PM Douglas Huff wrote:<br>
> > On Aug 22, 2011 2:26 PM, "Fred Concklin" <<a href="mailto:fconcklin@trucoin.com">fconcklin@trucoin.com</a>> wrote:<br>
> > > I'm also interested in work to daemonize bitcoin on boot and furthering<br>
> > > work to bring bitcoin into general coding and implementation paradigms<br>
> > > seen on GNU/Linux platforms.<br>
> ><br>
> > What? It already works fine in this regard using standard tools. Especially<br>
> > easy with daemontools/runit.<br>
><br>
> He said standard *coding and implementation paradigms*. This has nothing to do<br>
> with integration with some non-standard "init replacement" that goes against<br>
> the whole design of Unix.<br>
><br>
> What I understand this to mean, is properly abstracting the components such<br>
> that the node, wallet, and GUI can work together while being distinct parts.<br>
> In this sense, Fred, you may be interested in working on coming up with a<br>
> standard for a <a href="https://en.bitcoin.it/wiki/Wallet_protocol">https://en.bitcoin.it/wiki/Wallet_protocol</a></p>
--0015175caa56ff778704ab1db148--
|
