20700+ entries in 0.041s
mod6: anyone see where the code serializes the magic number itself?
mod6: maybe i got a bad copy?
mod6: that's the first part of the block...
mod6: im looking at the block, i don't see the magic number in there.
mod6: is that what you saw in that block too?
mod6: magic number is not 0xD9B4BEF9 in 364671
☟︎ mod6: let's see if i can break diff...
mod6: <+trinque> if the seller is to be believed, this is the old kernel.org server... LOL?! << wat srsly?
mod6: 475M bitcoind-woNoShared.s << lol
mod6: well, at least `objdump -T bitcoind` shows: objdump: bitcoind-woNoShared: not a dynamic object \ DYNAMIC SYMBOL TABLE: \ no symbols
mod6: i have serached forward to SSL
mod6: so i've got the two binaries recompiled, not stripped. not exactly sure what i'm looking for in here. doing a diff with objdump.
mod6: BingoBoingo: i was kinda thinkin the same thing, could be a market for someone to just ship a drive ready to go.
mod6: 365261 = 909.83kB - 693 txs
mod6: 365260 = 249.83kB - 467 txs
mod6: 365259 = 908.97k - 1090 tx's
mod6: danielpbarron: ah ok
mod6: thestringpuller: ha
mod6: would be inetersting/nice to see the ms time on how long it takes to process blocks {365`251, 365`252}; blocks > 900kb
mod6: ok so you've moved up 5 blocks.
mod6: yeah, iirc keys will not be removed from the phuctor pool.
mod6: its purpose is to factor keys with GCD
mod6: danielpbarron: so you're like 50 blocks behind now?
mod6: (gentoo) turned mine on to try. node must be down or something.
mod6: ok, yeah, im getting the same thing.
mod6: i'll tackle that tomorrow i think.
mod6: yeah, i thought about that first actually. but gotta recompile since bins are striped
mod6: ok looking through the hexdump -C diff now....
mod6: ok, i was just gonna do a quick `xxd <file> | less` and look at 'em side by side.
mod6: welp, they do hvae differenet hashes. that at least is obv.
mod6: asciilifeform: ok, compile complete.
mod6: ok this build is just about done...
mod6: Someday, we're gonna get the kinks worked out of this system.
mod6: Anyway, yah, will take a look when search comes back.
mod6: They needed to basically have the same SHA1s as the originals, with my own detatched sig.
mod6: ah, yeah... hm. I believe when I went to sign all the patches from the last release, I had to pull the patches, and then sign them as if I had wrote them myself for them to be accepted.
mod6: and I'll find a new ascii art instead of the jolly roger ;)
mod6: I'll make an effort this week to sign the patches I've read and understand, even if still experimental at this time.
mod6: also more eyes help too. sometimes we all miss stuff.
mod6: it does help. i often have to come back to it like a day later and re-read my own stuff for the 9th time.
mod6: asciilifeform: point taken. glad we talked about it. and yeah, very much so read and examine every patch.
mod6: eh, that was poorly worded. I think you all understand my meaning.
mod6: i thought so too. and it's a credit to my trust of asciilifeform that I verify his signature, and we have a L1 trust between us.
mod6: <+trinque> I can see the point that two signatures would've communicated what you said, mod6 << in that it would have been 1/2 of the foundation's official seal?
mod6: asciilifeform: noted.
mod6: I'll give this some further thought going forward. I don't wanna hold off on pulling the trigger on this stuff if all I need is simple skull & cross bones.
mod6: I've tested it, trinque has tested it, but we need a third party to independantly verify so I know what I'm publishing there is as correct as it can be.
mod6: One of the resasons that I haven't even posted the gentoo build guide to the list either.
mod6: I see, we just have a bit different view of the thing. I only wanna send stuff in that I can pretty much stand behind.
mod6: less is more, as always. if there's too much in there, it's less likely to be read.
mod6: lol, guess I just didn't wanna clutter up the turdomatic or confuse anyone either.
mod6: That's fair if it has a disclaimer.
mod6: I emboss cryptographically, stating that I've read, comprehended, approved and would apply in my own battlestation.
mod6: <@asciilifeform> doesn't imply endorsement << ok. i was just under the impression that's excatly what it meant.
mod6: ok building again without 'no-shared' for binary examination
mod6: not taken that way :]
mod6: There are some very far reaching effects of the patches applied in these build logs. They appear to "work", but as of yet, they're basically untested.
mod6: I only stamp approval at release time.
mod6: this is for *Experimental* only.
mod6: sign the patches before pulling?
mod6: would be easy for me to try now though.
mod6: <@asciilifeform> might be interesting << i have not, as of yet.
mod6: statically built. but I recall going through this in march how we needed that in there... just maybe overly paranoid.
mod6: every time i've built the 'stator' before, the output binary was fine.
mod6: well, actually, I didn't /have/ to at all.
mod6: thx trinque, asciilifeform, mircea_popescu, et al. :]
mod6: Those were the only changes to stator that were required to make it fit with the release artifact.
mod6: <@asciilifeform> modified how ? << with stator, I needed to add back in 'no-shared', according to
http://wiki.openssl.org/index.php/Compilation_and_Installation this is required for us (probably). And I also needed to modify your line `cd bitcoin/bitcoin/src;` to `cd bitcoin/src;`. All of the things are in the build log, I tried not to leave anything out.
mod6: decimation: plugged into mp's node?
mod6: Anyway, working on it. :]
mod6: This is all leading up to a new "patching guide" that I'm working on. Which is basically finished, save the fact I've yet to decide which direction to go on the build script. On one hand, I really love how simple and clean stator.sh is, but with auto.sh, I like how it automatically pulls the archives for you and creates the directories. etc.
mod6: I have created a simple build script that will pull all of the patches, verify them, apply the patches at the top of the file. Along with anything else that was required.
mod6: (at the bottom of these sizeable files, you can see me run `ldd` and `readelf` against the output binaries)
mod6: mircea_popescu: it appears to me that they are. I have two build logs (one for with auto.sh and one with stator.sh). They can be found:
mod6: Upon successful compilation, both static builds were able to pull at least 150`000 blocks from mp's node.
mod6: So over the weekend and today, was working on building a new gentoo-amd64-nomultilib (glibc) instance to test out application of patches with v0.5.3.1-RELEASE as the base. Was able to build static binaries with gentoo & glibc just fine with both a modified auto-static (auto.sh) and with a slightly modified stator.sh script.
mod6: haha @ wlan_firmware.c