davout: was there a discussion of the use case where one wishes to create, and sign transactions from an arbitrary set of unspent inputs?
davout: OSX, totally the platform sane people develop on "valgrind: This formula either does not compile or function as expected on macOS" hurrrr
ben_vulpes: either asciilifeform's or mine
davout: i have a recent prb node on the same machine, but i'm not sure it's going to work, re http://btcbase.org/log/2016-12-29#1592875
ben_vulpes: not that it cannot be done that way, but it is faster other ways.
ben_vulpes: otherwise trb may decide to ask utter randos for blocks
ben_vulpes: amusing innit that the father of the since-aborted 'blockchain spam' meme is now spamming irc
ben_vulpes: i see a new face at the back of the hall, i'm going to give them the opportunity to at least say hello and introduce themselves.
ben_vulpes: i will not spend the time to figure out how to mute everyone but noobs i've never seen before
ben_vulpes: for those who *still* miss the point, joining and parting is opening and closing the squeaky doors on a hall where 5 people are arguing and 500 muffling laughter and groans
ben_vulpes: a join and an up, which is predicated on the obvious
davout: luke-jr: it's not like you *have* to idle in the chan, logs are public and if you have something to say, it's a /join away
ben_vulpes: nah, park your boat on the lawn, who cares
ben_vulpes: top 10 in disconnects over the year? no problem?
luke-jr: I saw the link. didn't see a problem.
ben_vulpes: luke-jr: i know you're awake and reading this because you pm'd me. don't pretend otherwise, it's downright foolish.
ben_vulpes: one can patch an empty directory with an arbitrary patch and extract the filenames patch wanted to hit
ben_vulpes: phf: when it works, it outputs the list of patched files
phf: ben_vulpes: you mean like ~parse~ the output of patch?
ben_vulpes: !up luke-jr well did you read the link or what
ben_vulpes: wait phf hang on no i don't think i'm going to do the largest common, i think i'm just going to use the output of patch to figure out what was actually patched
phf: i noticed that btcbase supports filenames with spaces in them: if you start a filename with " it will read until a closing ". i have no idea where i got this from, because gnu diff/patch don't support spaces in names.
ben_vulpes: ^^ mircea_popescu asciilifeform mod6 trinque and any other vtronicists pls to opine
ben_vulpes: phf: when i crack my v again in the morrow, i'm going to implement hash-checking against longest common directory tree
a111: Logged on 2016-06-20 04:23 phf: which is handy if you're using something else to produce the patch, or if you need to use a non-trivial diff command. for example i sometimes need to exclude files from diffing, so a command might look like diff -x foo -x bar -x qux -ruN a b | grep -v '^Binary files ' | vdiff > foo.vpatch
phf: vdiff here http://p.bvulpes.com/pastes/r01nj/?raw=true it's the same old vdiff except if you pipe into it, it assumes you're piping in a patch, otherwise it acts as normal vdiff
ben_vulpes: i would also like to see the vdiff into which you're piping diff, mostly out of curiosity
ben_vulpes: "tee p" just papers your house with the output or what
phf: patch/diff lets you have a patch with --- foo +++ bar in which case it seems to ~check if foo exists, then try and press against foo, otherwise press against bar~
ben_vulpes: what's an insane input that breaks the shortest common substring test?
phf: that's what btcbase does basically. it finds position where common suffix starts and then works from there..
phf: i think it treats one of the names as canonical
trinque: patch will ignore the number of levels you specified with -p
deedbot: http://trilema.com/2016/disgrace-at-first-they-do-not/ << Trilema - Disgrace - At first they do not
phf: so the simplest solution would be to at least parametrize an equivalent of -p1 on lisp side
phf: ben_vulpes: well, we're kind of constrained by the hardcode -p1 behavior, but i've no idea if that's an implementation detail or a spec
ben_vulpes: the third approach is to apply each patch to an empty directory and determine what files would have been patched, had it applied cleanly.
ben_vulpes: the only other thing that i can think to do here is to grab the set of parents and children, match them up, and then get the lowest common denominator (if you will) file path for each patched file directly from the vpatch
ben_vulpes: c) hash that file and compare to the vpatch contents
ben_vulpes: b) when working through the list of each patch's children, search through the list of patched files until the patched filepath is a subsequence of the filename as recorded in the vpatch
ben_vulpes: http://btcbase.org/log/2016-12-29#1592918 << ftr i hate the solution for this that i have on disk
trinque: phf: when I brought to you "whence the disjunction between the practical and theoretical sides of subj" your output was "OP == faggot"
phf: also i learned long time ago that americans* aren't taught how to argue properly, so when they do they have a really hard time keeping the thread, keeping more than one point, developing an argument, bringing it back to original point, etc. consensus intelligentsia are all very civil, so when you do get them railed up, they just flail, sort of discourages from even trying
phf: hehe, as much? no. but that's only because if there's one lesson i learned from naggum, all this rage is not healthy.
mircea_popescu: phf for my own curiosity, does anything in the rest of your life piss you off as much in aggregate as one session with these assholes ?
asciilifeform: if drum printer dun go 'bang' when it gets the octet - it ain't 'printable.'
asciilifeform: then take standard reiser. but in that case you grunt under entirely arbitrary procrusting .
asciilifeform: picture reiserfs , but without the idiot fortranistic hard limits on nodes, lengths, etc
trinque: could be. I'd like to see the design for such a thing.
asciilifeform: yeah but one that doesn't motherfucking grind to a halt when read 1000/sec omfg
trinque: when I build things to ask the fs how many customers in new york placed orders on the weekend it starts to look quite like a relational db
asciilifeform: how much of 'what trinque wants here' is unobtainable by simply abusing the fs ?
trinque: and I'm tweaking the site generator
asciilifeform: mircea_popescu: no, it is specifically 'doesn't work because ~nearly there is a cock-shaped shadow~
asciilifeform: trinque: my understanding is that these ways typically involve clusters of machines, duplicate db, and very elaborate/failure-prone synchronizers
mircea_popescu: and gtfo with the inept simile, the correct comparison is "imagine if your cock didn't work if there was already one in the target woman". which i bet yours doesn't, so really.
mircea_popescu: asciilifeform there would be two trees not "two genesises" in his idea, he's making a tree for the site and a tree for the tooling.
a111: Logged on 2016-11-19 18:52 asciilifeform: Framedragger: db being hammered 24/7 with 'do we have this hash' 'do we have this fp' 'add this and this' 1000/sec is the bottle.
trinque: noobs can aspire to be named there
trinque: mircea_popescu: ah you know what, excluding nicks with no ratings breaks this, because writing the keyfile happens inside that logic.
asciilifeform: imagine your cock didn't work if 10,000 others in town were in use.
trinque: that sounds like a bug, really, but the kind of bug the complexity of the thing makes hard to remove
asciilifeform: all of the orthogonal tools must be mercilessly cut apart, yes.
trinque: recall I conceded in the bitcoinfs thread that what I consider to be "database" is actually many orthogonal tools related to data manipulation, atomicity of operations, adherence to type constraints ~if desired~
trinque: this is not the direction from which to come at this subject
trinque: but the right answer is as much or as little structure enforcement as you like.
asciilifeform: and why the FUCK is 10,000 writes/sec 'too much'
asciilifeform: why the FUCK should a READ block because ~wholly unrelated datum is being written~
trinque: I am not moving from it until I have another database in hand
asciilifeform: ben_vulpes: 'this shape' being 'html as-seen-by-reader as the only storage format'
asciilifeform: trinque: mircea_popescu will probably barf if the 2 genesisen get displayed on same screen. it isn't an eggog in vtronics, but is in his head.
trinque: wot.deedbot.org will likely result in two genesis patches down the line. one for the tool, other for the particular site
asciilifeform: i've seriously considered reimplementing phuctor in this shape. as it is, it loses more from the slow writes idiotically queuing up, and the wedged reads that result, than it wins from fast structured queries.
trinque: and the answer is don't
trinque: asciilifeform: the question answered here is "why regenerate the same idiot HTML every www request?"
trinque: I am not using html as a data storage format what the hell
ben_vulpes: trinque: just sed and awk the html you have in place to update ratings
asciilifeform: the mention of pg_notify
asciilifeform: so update the html?
trinque: asciilifeform: because people update their ratings
trinque: there's a listening process consuming these pg_notify events, of the form (gen-nick-page "trinque") which debounces them according to some sane interval, i.e. if a few updates hit the same user in a short span, it will result in one single rebuild
asciilifeform: trinque: why would you generate the site from a db? more than once, i mean
trinque: db operator has to go through and manually apply these triggers. for example, updates on either a "to" or "from" rating will require a rebuild of the nick pages in both directions.
trinque: ben_vulpes and I had an interesting conversation yesterday about how to handle static sites generated from a db. idea we ended up with was that we'd have triggers which emit a pg_notify signal when the "dirty bit" has flipped for any page.
trinque: gotta finish writing the thing that triggers granular (per-nick) updates, leaning on a full rebuild for now.
trinque: mircea_popescu: it'll be up there in a sec, let ya know
mircea_popescu: re octopus - no other effect individually ; but living long is bad for the species, as hillary well exemplifies.
mircea_popescu: phf i guess we will sooner or later have to actually formulate the patch format yeah.
mircea_popescu: asciilifeform no the classification proposed is quite serviceable.
mircea_popescu: like the golfer guy what's his name
mircea_popescu: it's the irony of all time that while the progre press was derping about how trump will lose the election and try to turn it around into a television show, the reality turned out to be he won the election AND OBAMA is trying to turn his losership into a tv personality
mircea_popescu: in other news, obama's been doing more reality tv work than the entire kardashian extended family these past few days.
phf: ffs, i resent being placed in a position of defending something that i'm not responsible nor care for. diff -e would've been closer to "teco macros", but it's the "sane teco macros" we're talking about here, etc. etc. etc.
asciilifeform 'can't even', takes break, off to play with 10kg joystick, and then with pet
asciilifeform: phf: USES nonprintables in the magic ?! even deeper retardation.
asciilifeform: one can debate whether the persians are right to cut hands off thieves. but the hands of folx who write programs like this, i cannot see any reason why they should stay attached.
asciilifeform: and THEY CAN BE ANY OCTET
asciilifeform: if there's a forbidden char or string --- that is called magic.
asciilifeform: phf: 'ed-style' diff outputs are the Right Thing, but done the ~proper~ way, with NO INBAND MAGIC, and not the monkey way.
phf: there's no "escape" as such. instead it generates an adhoc escape (say replace dot with ZZ or whatever) and then patches that one line using s///.
asciilifeform: (i did not have any lines beginning with '.', so i have nfi what the escape would have looked like. but there WOULD be one.)
asciilifeform: NO MOTHERFUCKING INBAND MAGICS
asciilifeform: phf: diff -e has own serious problems (it 'enmagics' the '.' character, for instance.)
phf: well, in the simplest case (i.e. if you're using gnudiff) you're still just going to get the diff's take on "delete this line, add this line", but the ~format~ would be an ed script out of the box, so can have pretty complex transforms
asciilifeform: in the case of the orphanages, they had 0 constructive purpose. they were like the 'death glands' on that one species of octopus. snip'em and you get octopus that lives for +2 yrs and no other effect.
asciilifeform: the important thing to observe , in each case, is whether it changed semantics in a way that can be ~understood~
asciilifeform: but some -- did. the orphanage removals certainly did.
asciilifeform: ben_vulpes: not each (nixing the win32 #ifdefs did not, for so long as nobody is dumb enough to try to build for win32)
ben_vulpes: asciilifeform: pedantically, each patch then produces semantically new program?
asciilifeform: (which, if it is left up to me, will look like teco macros. so if anyone does not like this shape, had better come up with another.)
phf: in the "command that was used..." line
asciilifeform: as soon as there is a viable replacement.
asciilifeform: ben_vulpes: semantics is , more or less, what the proggy ~is~
phf: fwiw patch format is super promisetronic. it's something along the lines of "command that was used to produce the hunks\nhunks..."
asciilifeform: ben_vulpes: same as in any other proggy
a111: Logged on 2016-12-29 23:32 ben_vulpes: http://btcbase.org/log/2016-12-28#1591573 << the diff line is distinct from the --- / +++ lines, does one ever see a patch file where the files compared aren't prefixed with a/ or b/ ?
asciilifeform: but it is also not clear to me whether this can be done and the result still referred to as 'trb'.
asciilifeform: one theoretical solution to every type of blackhole other than the (theoretical) 'nsa sprays shit directly into the pipe on the backbone' is to make trb actually multiprocess
asciilifeform: ben_vulpes: the 'a' and 'b' are historic artifacts from my torture room. but notice, gnudiff ignores the name.
pete_dushenski: asciilifeform: thoughts on resolution to directed type2 floods ? the ips drowing me atm are from all over the map - china, spain, verizon, mci - no aws to speak of.
a111: Logged on 2016-12-28 02:39 phf: http://btcbase.org/patches/hashes_and_errors#L118 you don't really want to do this. you're subseq'ing there to strip the a/ b/ but that's not at all a guarantee! i have a vpatch with `diff -ib -ruN /Users/pf/cmucl20d-build/src/hemlock/abbrev.lisp src/abbrev.lisp` in it for example. at the very least you want to abstract it away into its own function. that would correctly operate on a hashed-path datastructure.
ben_vulpes: http://btcbase.org/log/2016-12-28#1591573 << the diff line is distinct from the --- / +++ lines, does one ever see a patch file where the files compared aren't prefixed with a/ or b/ ?
asciilifeform: type3 (this taxonomy is strictly from asciilifeform's notes, and is no canonical animal of any kind) is the 'thinking man's shitflood', where requested inventory is not a DOS by virtue of ~quantity~, but ~quality~ (flood of questionable but not immediately/cheaply rejectable material)
asciilifeform: type2 ( pete_dushenski's ) is the garden variety shitflood. which is sometimes solved by ip ban, but only in the case of 'shrapnel addressed to occupant', i.e. idiot prb nodes wildly spamming crapolade, and not in the 'bullet with your name on it' case, where somebody actually has a sybil constellation drowning your trb node in liquishit, with no SINGLE ip misbehaving in any way
asciilifeform: and for so long as block verification is single-processor, there will remain type1
asciilifeform: (the one unattributable to overload of any type)
asciilifeform: mircea_popescu: ultimately for so long as peers are unauthenticated and speak unauthenticated plaintext , there will be type4 blackhole.
mircea_popescu: asciilifeform the idea, as idiscussed a few days ago, is to separate things and queue.
asciilifeform: and it is not in fact held up by the fs thing.
mircea_popescu: this'd make some fine subject of a priority work order, the only problem is that it's so intricate and we aren't fans of doing the work n times. but once trb sits down on a sql-fs it would all fall in place.
mircea_popescu: anyway - properly indexing txn so that we deliver the full data set ; properly handling the blackhole thing will actually ruin prb because nobody's fuycking migrating to their new protocol.
asciilifeform: one thing that palpably helps is the aws banhammer.
mircea_popescu: pete_dushenski looks like stock blackholing. ipban the offenders, see what happens.
asciilifeform: pete_dushenski: this'd be the genuine article
ben_vulpes: phf: moreover i'm too ferklempt over how the thing's changed since 10.2 to want much to do with it anymore
mircea_popescu: iirc this even made it to qntra, because the usg.dept of legal pretense's failure to act was exactly just as much damning of the whitehouse website based in maryland as of the bitfinex website based in nowhere.
mircea_popescu: davout the deep problem there, with kraken as well as with any other of these websites, which is to say scams, is that YOU DO NOT get to pocket anything. in your case this was a loss, but in the case of bitfinex running away with millions in "profits" its inept "users" were supposed to have accrued but never did, the mechanism was more clearly in view
asciilifeform: ben_vulpes: the thing phf refers to , is in use still, whenever i make (yes) xp box! < 400MB! (lighter weight than, e.g., africa-linux)
asciilifeform: and can you get a core dump out of the thing pete_dushenski
asciilifeform: pete_dushenski: from your telling, it seems that there was no 'after'. so let's have the 'before' and 'during'
phf: http://btcbase.org/log/2016-12-29#1592829 << you remember how they used to have those "stripping all the extras" hacks for windows. like a tool that would unpack windows xp installer, remove whatever shit author knew how to remove, and then repack it, so you get windows with random gunk. you know of anything like that for mac? i wonder if i can roll 10.9 without any of the /Applications/ etc.
asciilifeform: pete_dushenski: be so kind as to post plox some logs from your node during and immediately prior to and after the blackhole
ben_vulpes: pete_dushenski: you have to reboot the whole machine?
pete_dushenski: mircea_popescu: i don't disagree from a philosophical standpoint but nor can i tolerate having dead fucking trb nodes. that i should have to reboot a machine ~daily~ is the death of bitcoin. yukoners never had it so bad.
ben_vulpes: jurov: would you be so kind as to update the lxr with makefiles.vpatch ?
ben_vulpes: wait, what is the difference between mempool and relay set?
mircea_popescu: transactions, not in the memory pool or relay set
mircea_popescu: pete_dushenski there's really no good reason to not serve arbitrart txn data. the fact that "modern" prb nodes can't support this is entirely their doom.
pete_dushenski: in other inequalities, latest taleb : https://medium.com/@nntaleb/inequality-and-skin-in-the-game-d8f00bc0cb46#_edn3.14k1h647w
asciilifeform: ben_vulpes: nah, full of the previous installment of same
asciilifeform: also what is one to do with the list of internal usg names for various trojans
ben_vulpes: "obab demands we say something nasty about the russkies. so...hey php is vulnerable and shit"
asciilifeform: i can picture the intern who was ordered to produce this gem
ben_vulpes: in other unholy file formats: https://www.us-cert.gov/sites/default/files/publications/JAR_16-20296.pdf
asciilifeform: unlike the earlier film, klebanov -- afaik -- really ~did~ find this booby.
asciilifeform: maybe jurov , who saw it fit to share these with the heathens instead of with us, knows.
ben_vulpes: did ccc publish transcripts for these somewhere?
asciilifeform: in other lulz, https://media.ccc.de/v/33c3-8099-how_do_we_know_our_prngs_work_properly
ben_vulpes: shoulda said "looks like a variant on another classic retail scam"
ben_vulpes: davout: this is sop for american retail brokers as well. even were you to have the cash on hand to buy the underlying outright unless you jump through very specific and hard to find hoops retail brokerages will lend you the capital to take the position you intended to enter under your own steam
pete_dushenski: the latter
a111: Logged on 2015-07-02 20:44 ascii_field: 'getdata is used in response to inv... ...t can be used to retrieve transactions, but only if they are in the memory pool or relay set - arbitrary access to transactions in the chain is not allowed to avoid having clients start to depend on nodes having full transaction indexes (which modern nodes do not).'
davout is finally done writing the kraken's team indictment
shinohai: The guy that gave us the red cups that were prominently displayed in pr0n listings at one point this year.
a111: Logged on 2016-12-29 21:04 ben_vulpes: mod6: moreover the general case is looking to be "project-genesis.vpatch"
pete_dushenski: mircea_popescu: i have sincerely nfi why my node is asking for these. it's at ~full height.
mircea_popescu: shinohai the who ?!
mircea_popescu: pete_dushenski why is your node asking for these ? or is it ?
pete_dushenski: but ya, looks like ancient blocks in and around the 300k mark
pete_dushenski: the above is a snippet from the debug.log and the result is a ~frozen machine. doesn't respond to rpc commands the way machines blackholed by, say, 'askfor tx' does.
mod6: <+mircea_popescu> http://btcbase.org/log/2016-12-29#1592756 << that is historical nonsense that got hammered out in a large discussion when it was actually brought to the forum. << ok
mircea_popescu: http://btcbase.org/log/2016-12-29#1592756 << that is historical nonsense that got hammered out in a large discussion when it was actually brought to the forum.
mircea_popescu: which makes alf's objection to the mega discussion re antecedent enforcing etc weaker than he cares for it to be : turns out we ALREADY have the state machine.
mircea_popescu: no patch can be elevated to the status of genesis ; if it is a genesis of something it knows this, and the way it knows this is through the antecedent being false
mircea_popescu: the point where genesis has for an antecedent "false" and nothing else is imo controlling.
phf: mod6: we're on the same page
mod6: agree. just trying to be 100% positive I'm doing the right thing, before I do it. And it is discussion worthy imho.
phf: root is a compsci term for a the topmost element of a tree. genesis is a vtronic term for the origin. on imlementation level they are identical, and generally describe the same concept, but in general "root" being "genesis" is an implementation detail
phf: well, then alf is being sloppy with his terminology
phf: mod6: there's no such thing as "root". there's only genesis. you find all patches that satisfy the genesis requirement ("all antecedents are false") and you build your graph down from there
mod6: <+asciilifeform> mod6: 'genesis' means 'all antecedents are 'false'n rather than 'no valid antecedents' << just to re-iterate, does 'genesis' also apply to 'root' ?
mod6: im not sure that i get this ^ but... i think we're all saying the same thing.
mod6: ben_vulpes: so you think, what i'm calling the 'hack' to be just as good or more appropriate here? i'd rather check, personally.
phf: i don't mean that the patch is called "genesis", i mean that the concept is called genesis, so there's no need for new nomenclature like "true root"
mod6: asciilifeform: sweet! then i think im in good shape.
ben_vulpes: mod6: moreover the general case is looking to be "project-genesis.vpatch"
asciilifeform: mod6: 'genesis' means 'all antecedents are 'false'n rather than 'no valid antecedents'
mod6: Then he's got a problem. So i felt like this type of checking, is more strict. And if it is proper, I will proceed.
mod6: phf: ok, see, there is a hack i could have put in, instead. where i just ensure that my root is named like /genesis/. But what if someguy calls his root, 1000 years from now, xyz.vpatch.
mod6: one way, I've found, to solve this is to ensure that any root in my list of roots, must be a "true root", in such that if the vpatch's every 'a'='false', then it is a "true root".
mod6: the reason, I'm finding, that my previous patch still listed a->b->d in the flow, is because 'd' got picked up as a root. and the reason it does is because at this point, it has no antecedents.
mod6: so going back to our discussion regarding: a->b->c->d all signed by x, if 'c' is removed then the flow should be a->b and now 'd' has become orphaned. the correct strictness, 'v' (wot-variant) drops 'c' out all together.
mircea_popescu: i thought that was the obedience index.
asciilifeform: 'A Finnish court has sentenced the former head of Helsinki's anti-drugs police to 10 years in prison for drug-smuggling and other offences. ... It ranks as the second least-corrupt country, after Denmark, in the global index compiled by Transparency International.' << in other reich lulz.
mircea_popescu: he might be working off some notebook bush left stuffed between the actual books in the wh library, because i seem to recall a declassification of technical details pertaining to iraq's wmds also being in the works for lo these many ten+ years.
mats: the butthurt continues
asciilifeform: 'Mr Obama also announced the US will declassify technical information related to Russian cyber activity to "help network defenders in the United States and abroad identify, detect, and disrupt Russia's global campaign of malicious cyber activities".'
deedbot: http://trilema.com/2016/disgrace-what-he-throws-together/ << Trilema - Disgrace - What he throws together
shinohai: lo BingoBoingo ...latest Qntra. Bahamas gonna make the Bundy cows a Nashnul monument.
asciilifeform: now we know how spanish priests quit convertin' and joined in the target practice sport with the normal conquistadores.
mircea_popescu: but as you nobody gave much a shit, kraken always was the hollow pretense of nobody in particular.
mircea_popescu: kraken ? they were hacked, plenty, what are you talking about.
davout: i'll probably end up sentencing jesse powell to death, depending on the way they handle this
mircea_popescu: davout you had it right the first time : what you bought doesn't exist.
asciilifeform: (buying plane ticket, and visiting mircea_popescu , supposing that he is still buying usd for something, is probably in the end cheaper than 'goxing')
asciilifeform: 'i put my hand in bear trap. it snapped shut and hurt quite a bit. i reported bug. the trapper said 'feature'.'
davout: they fail to make the intellectual link between "software doesn't actually behave according to its documented behaviour" with "bug"
davout: when these monkeys get their shit rubbed in their face their answer is, I shit you not, "this isn't a bug, but we'll update our documentation to match the actual behaviour"
davout: it doesn't occur to their two-cans-and-a-string fork that it can use the same fucking 10kEUR to buy back the asset I borrowed
davout: somehow, i now need to "borrow" 10kEUR to liquidate the position, because somehow, the result of the sale doesn't exist!
davout: apparently these fucktards expect one to borrow assets to fucking close a position
davout: it is broken in such retarded ways i'm wondering whether i'd have been better off using bitstamp's string'd cans
asciilifeform: the 'riddle' unlocks very easily, scroll to the end of https://www2.adacore.com/gap-static/GNAT_Book/html/rts/g-socthi__ads.htm .
asciilifeform: davout: it was exactly the same snore as in early trb
a111: Logged on 2016-12-29 03:06 asciilifeform: socket.c:(.text.__gnat_gethostbyaddr+0x1a): warning: Using 'gethostbyaddr_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
deedbot: http://trilema.com/2016/disgrace-yet-neither-he-nor-she/ << Trilema - Disgrace - Yet neither he nor she
mircea_popescu: in all sense they're the same thing. once one's too poor for art, his house will be exactly like his neighbour's
asciilifeform: 'and now they come to tell us in which hole to fuck the goat, and to consider transition to sheep, and to send opium west, not east, ' etc.
asciilifeform: in the pashtun sense contemplated, they were exactly the same thing, 'they think they own the world because they can make jets'
mircea_popescu: the soviets were entirely not different.
mircea_popescu: you'll find a mini-empire, like that woman who left her infant daughter to sun on the porch and came back to discover the child covered in fireants.
asciilifeform: not everybody wants to be involved with mega-empires, on the giving or on the receiving end. in that light, the pashtun mountains are every bit a 'high-tech' deterrent as a SAM battery.
mircea_popescu: (which, truly, is what most engineers are doing with their lives, the engineering being just a pretext)
mircea_popescu: much like if a boy's mating strategy consists of seeking out the places where no other boys go and waiting for girls to straggle in.
asciilifeform: make sure to tell this to the pashtuns
mircea_popescu: here'\s the thing : if inhospitability to aircraft is a win, you have serious problems in other places that you should attend to.