asciilifeform: that being said, you can use 'wire' with anything that can maintain a ciphered tcp pipe between two boxes. dun have to be ssh.
asciilifeform: if i had a ticket to the mythical planet where programmers aren't retarded and 'the shame of poverty' is not smelled, we would not even be having the trb conversation.
asciilifeform: trinque: don't put wire-trb on your icbm-controller box. the skull is there for a reason.
asciilifeform: because ssh is a product of 'satoshis', people who were dropped as children, and cannot be made to self-reignite.
asciilifeform: you gotta have something that will re-ignite ssh if it drops.
asciilifeform: ( re the recipe : 'autossh' is a c proggy, from heathendom, i have not audited it. this is one of the reasons for the skull'n'crossbones. there is a similar utility called 'RSTunnel' that consists solely of bash script. but i have not tested it . )
asciilifeform: true, it opens you up to 'hm which one do i have on THIS box' etc. which is why i like to keep the buildtron on each.
asciilifeform: there's nothing promisetronic re copying a static bin that you built ~yourself~ to >1 box. (for one thing, it demonstrates that it is genuinely static and will run on heterogeneous boxen.) but you can do it either way.
asciilifeform also likes to keep the whole orchestra on his nodez
asciilifeform: then you can. (and for bonus point, compare the binaries, they oughta be exactly same)
asciilifeform: (and on any other box that will be a wire slave)
asciilifeform: (at the risk of pedantry) first put the newly-build 'bitcoind' binary, on the box that will become the first slave.
asciilifeform: !~later tell phf i was thinking' of buying that 'ivory' and making a signal interposer . any idea whether the magic cpu was soldered down, or LIF socketed..?☟︎
asciilifeform: anyway it's entirely a timesaving measure, you entirely can load them from somebody else each time, the thing won't proceed unless the hashes match
asciilifeform: and you aint backing up 'this box' but the trb deps. that got frozen 4evah.
asciilifeform: mircea_popescu: 'lazy man does the work twice' or how did it go
asciilifeform: mircea_popescu: once you have the contents of 'deps' again, i recommend to back it up to another dir, and to burn a cd, those turds ain't ever changing -- there will only get ~fewer~ (when we ditch, e.g., bdb)
asciilifeform: (for some reason mod6 put them inside the dir that gets pressed)
asciilifeform: if you still have the deps somewhere, copy'em over, otherwise gotta download'em
asciilifeform: mircea_popescu: now all you gotta do is to move the subdir 'bitcoin' inside this 'trbfoo' to replace the 'bitcoin' dir in trb54
asciilifeform: mircea_popescu: looks like this worked. confirmed that mod6's vtron doesn't check for file-exists, appends. (i won't even blame him, as such, this is the default idiot behaviour of gnudiff !)
asciilifeform: mircea_popescu: you pasted the .gitignore from inside the resulting dir 'trbfoo' ? make sure this was so ?
asciilifeform: it can, but that doesn't fix whatever resulted in it being appended to itself during the press
asciilifeform: your copy of this turd (quite unnecessary in trb, in fact, but that's besides the point, we inherited it in genesis) consists of the original concatenated to itself !
asciilifeform: mircea_popescu: this looks like a bug in mod6's vtron :
asciilifeform: now they go in patches and seals, respectively ;
asciilifeform: mircea_popescu: iirc it also produces repeatable (bitwise) binary.
asciilifeform: ( you have a .wot, .seals, .patches, these can be named something else, but these are their conventional names; out of these, vtron 'presses' a particular tree that you want.)
asciilifeform: i assumed (apparently wrongly) that mircea_popescu remembered basic vtronics .
asciilifeform: ty phf . but it was not clear to me what piece mircea_popescu had the problem with, was it where to get the patch, or where to put it.
asciilifeform: that's where all of the patches from which trb is made, live.
