141800+ entries in 1.081s
trinque: which
I do habitually, as if trying to climb across the desk with the mouse
trinque: ah yeah,
I've had mine move suddenly if
I lifted the mouse while using it for that reason
mod6: sometimes a hair gets stuck in mine, and
I have to pull it out.
mod6: and if that doesn't work, maybe
I can give 'hardened/linux/musl/amd64' (
i don't see a non-hardened one available atm)
trinque: mod6:
I'm going to re-run it with the "vanilla" gcc now
mod6: trinque: sometime this month
I'll try to pay with 'default/linux/uclibc/amd64' instead.
mod6: <+trinque> suggests it's maybe a matter of the hardened toolchain eh? << yeah,
i think this is a clue
mod6: weird. that's basically the same problem
i had with uClibC [ libpthread.a(pthread_cond_wait.o): relocation R_X86_64_32 against `__gcc_personali
kakobrekla: when this happens there already is such condition as
i described give or take
decimation:
I find the probability of that happening to be very low
mircea_popescu: last
i heard davout was looking for ways to programatically exploit the shitcoin
kakobrekla:
i cant have blockchain dead for a month
mircea_popescu: anyway,
i am very excited about this actually happening.
mircea_popescu:
i imagine so would you : a bankrupt field of miners best chance to buy cheap mining rigs for a long time
mircea_popescu: kakobrekla
i welcome the verification of this theory in the field.
mircea_popescu:
i would expect a stuttering engine to go on stuttering until discarded.
shinohai: No, mircea_popescu it has actually been faster than when
I previously synced, less memory footprint ramwise
mircea_popescu: ascii_field get a load of this : three days of random, odd internet behaviour, discussed here publicly, which then went away by itself.
i did nothing to the server,
i asssume neither did you.
mircea_popescu:
i think
i said this before, but in any case bears repeating insistently : larger blocks are a complex discussion that will involve many and numerous benchmarking. it's not the simple matter idiots make it out.
decimation: anyway, my earlier meta-point was that
I theorize that many voted for obama because he was black but 'not that kind of black'
mircea_popescu:
i do know it is upon the proponent to ~prove~ rather than just assert that the tools we developed to discuss and analyse the "terra irredenta" movements in italy cca 1800 are also applicable or meaningful in black africa.
mats:
i speak mandarin influently. my cantonese is pretty good, though.
mircea_popescu: decimation
i am broadly unconvinced the concept of ethnicity makes any sense in africa.
mircea_popescu:
i guess she does look distinctive enough, and since presidents are more about looks than actors... myeah ok
mircea_popescu: mats
i mean
i could see it in usage like "e transilvanean de-ai nostri", ie, "he's one of ours". but that's for a minuscule and very culturally coherent ethnic group.
mats:
i mean, she's yellow. kinda asian.
mircea_popescu:
i gotta say
i absolutely am loving the choices of women to put "in tech" the enema's makin'.
mod6: not that
I have any better ideas at this point.
mod6: oh yeah, now that page was the one
i was referring to;
i find it pretty unhelpful at all unless you're looking for just who submitted/signed & the sig.
phf:
i was actually taking a harder position, if somebody wants to follow along they should read the mailing list from the beginning, and having it all accessible in one place for offline reading helps
phf: jurov:
i don't think there's complete understanding as to what should go into patchlist yet. the one we have now is fine, and
i'm sure it will be improved
shinohai:
I have little better that piques the imagination
mod6: but pre-milestone release, it does get hard to follow. and since
I do believe it'll still be some time before we get the next milestone cut,
I should prepare some sort of document so individuals can help test. (we very much appreciate the enthusiasm and the help!)
ascii_field: mod6:
i kinda assumed you and ben_vulpes would roll the patch sequence docs into releases
mod6:
i'm not sure what to do about this as far as the email list is concerened, yet.
mod6: there are a number of different directions these emails go in; patching for v0.5.3.1, pogotronic, gentoo, etc, etc. so
I'll try my best to make this apparent when
I write up a patch list, etc.
mod6: and trinque, did you hvae that -fPIC issue on gentoo with uClibC? that's the same error
I was talking about all last month and in the SoBA
trinque:
I wanna do some gcov work this weekend
mod6: ascii_field:
i did have a problem with it a number of days ago when
I first tried it, but it was just an environment related issue. this build,
I literally just did it, worked fine.
ascii_field: last night
i looked into doing a 'buildroot' with it
mod6:
i saw that comment yesterday,
I briefly looked at it's page ascii_field,
I'll take a deeper look at musl soon. hopefully that'll get us further?
phf: jurov:
i'm not in a position to make suggestions to the way things are done in the republic :)
i used patches.html,
i found some issues with it from the perspective of figuring out what transpired before
i started paying attention, so
i did extra work on top. cura te ipsum.
i figured having mailbox available will make the works of others after me easier
ascii_field: presently
i suspect that 'musl' is the only glibc replacement that has any promise
trinque:
I'll restart from the beginning and paste the whole thing
Jautenim:
I coaxed it to compile the turd but segfaults straight away
phf: ascii_field: having a turnkey solution is not the intent behind my request (though
i prefer tools in my mail client to messing around with lynx/wget.)
i'm interested in having a "take to mars" copy of bitcoind history. right now it's a bit all over the place. patches here, email text there, etc.
trinque: but
I see the point clearly
jurov:
i have nothing against publishing the mailbox
☟︎ shinohai:
I don't think
I would want an automatic solution in that regard.
phf: jurov:
i only joined the conversation recently, so
i don't have a complete history of emails. of course
i'm getting complete emails now, but not the past ones
ascii_field: the point, which
i've been trying and apparently failing to make for ages, is that if you are thinking about automating this, you are 'doing things wrong'
assbot: Logged on 03-07-2015 19:44:53; phf: mod6: well, lets say you have something like mutt open with the current email. it's pretty easy to write a script that takes current email and feeds it to an external script, that splits out patch, verifies it with the provided sig, and then applies it to the codebase (or pushes it into some queue of patches as a case may be).
i.e. you read the email, push "p" to do everything for you, and then move on to the n
shinohai: ikr,
I get it all in the mailing list, no confusion there.
jurov:
i don't understand, either
assbot: Logged on 03-07-2015 18:52:21; mats: 'pramfs' looked furthest along when
i last checked
phf: mod6: sorry,
i wasn't really prepared to explain what
i mean,
i thought you would just grok the request as an obvious one. we probably just have very different workflows
☟︎ shinohai: mod6: if you want another auto.sh,
I'll try and help you when
I understand this new build xD
☟︎☟︎ mod6: But as
I get through more of these and test more of these,
I'll put something together to make this process easier.
mod6: But
I've only started scratching the surface with alf's latest, so this hasn't been done yet. All of these are still in my "Highly Experemental" category. AKA: use at your own risk.
mod6: basically, instead of me making a whole bunch of different one-off scripts for peoples seperate clients and whatever stack they've got,
I just create one script that will patch in & verify all the scripts at once. usually after
I've tried and tested them all myself, peronsally.
phf: mod6: well, lets say you have something like mutt open with the current email. it's pretty easy to write a script that takes current email and feeds it to an external script, that splits out patch, verifies it with the provided sig, and then applies it to the codebase (or pushes it into some queue of patches as a case may be).
i.e. you read the email, push "p" to do everything for you, and then move on to the next email
☟︎ mod6: <+phf> mod6: no no each email.
i thought that was the whole point of ascii's approach,
i.e. linux kernel style "read email, think, apply the patch" << im not sure what their process is.
mod6: <+phf> the process was needlessly complicated since my mail client lets me do a bunch of those steps (patching, gpg verifying, etc) with a single key, so if
i had an mbox,
i could just import it, and then use a more familiar interface << so, what
I've done in the past was; create a perl script that pulls down and verifies all the patches and applies them to a common baseline.
phf: mod6: no no each email.
i thought that was the whole point of ascii's approach,
i.e. linux kernel style "read email, think, apply the patch"
mod6: ahh. im not sure
i remember mbox. and yeah, the whole thing is a bit... unwieldly
phf: the process was needlessly complicated since my mail client lets me do a bunch of those steps (patching, gpg verifying, etc) with a single key, so if
i had an mbox,
i could just import it, and then use a more familiar interface
phf: mod6:
i don't necessarily have problems,
i have a bitcoind with all the patches up to eatblock (haven't looked at stator yet, but then
i'm building with enemy tools). the way
i assembled patches is by reading through web archive and saving/verifying each patch as
i saw it
shinohai: Then when
I get this new build up,
I can sync up to the correct nodes, and .torrent dat chain.
mod6: heh, this boost compile is taking a while, because
i'm also syncing at the same time haha
mod6:
I'm creating a log of this, and will post for everyone to look at once complete.
BingoBoingo: On that note,
I'll brb in a few units of time.
mod6:
I'll work on something for that within the next week probably.
mod6:
I will work on a patch list and maybe a script later this month. It is a bit hard to follow.
☟︎ phf: trinque: tbh
i thought it was broken, since it's missing chicken, gui, etc. only once
i went through the exercise of making my own did
i realize that those are not part of mailing list history
trinque:
I didn't know the patches page existed til today
mod6: punkman: ok.
i thought we had decided to leave the miner in there for now. but yeah, thanks
I'll let ya know.
trinque: (not that
I don't like secret clubs)
trinque:
I went from 100s of spamz a day to 0 with this one weird trick.
trinque: jurov: could the btc-dev mailing list send mail via tls? requiring that on my mailserver's end has drastically cut down on spam, but
I think that's causing me to miss mailing list messages
mod6: lemme give it a shot on my end first, see what happens so
I can give you valid help