ben_vulpes: i have developed an allergy to bending myself to fit my tools over the last four years; ios is one of the last bits of sand in me gears
ben_vulpes: pretty tragic that one even has the basis to ask 'how bad is the t9', given how well it worked two decades ago.
ben_vulpes: how's the t9?
phf: jesus what the fuck is this
ben_vulpes: phf: rocking the 'mp01' or what
ben_vulpes: let's just continue with the apple idiocy: "try the new safari! fast, energy efficient, and with a beautiful new design."
asciilifeform: forget the street maps, speaking of raw photo
asciilifeform: ( and the oblig. terrain-tracking icbm... )
phf: because their maps are certainly shit for any kind of navigation that's not by road.
asciilifeform: there's no particular reason why one couldn't put it all on sd card and make passive pocket maptron.
phf: one thing i wrote that i was really happy with is a very simple gps coordinates to atlas grid mapper. the thing would basically draw a rectangle with atlas grid number, like p34 A7 and inside the rectangle it'll draw a large red dot which roughly indicates where in the quadrant you are. i was using it extensively on a trip through alaska, because the toy catches gps readily, but naturally can't catch internet connection. so it was a kind of navigation
asciilifeform: phf: i've always wondered if it is possible to make a 'programming toy' proggy for touchpnojes that actually makes productive use of the fingers , rather than torturing user with simulated kbd
phf: both times i wrote anything on pythonista was when i was traveling without a computer, and i do it semi-recreationally. with automatic indentation and completion it's not particularly painful, if the goal is to get some interesting computations going, rather then you know "programming environment". it's more of a turtle kind of exercise
phf: pythonista has been around for a while. it's literally the only useful application for the iphone
ben_vulpes: i guess this is new as of the lifted ban on interpreters and compilers?
phf: ben_vulpes: before i finally gave up my ios, i was using pythonista for almost everything, including totp. there's some python totp implementation that i lifted from somewhere, that can be easily ported. i gave up writing a barcode recognizer, though it's not a particularly daunting task with numpy
asciilifeform: ben_vulpes: why wouldja give all of the monkeys one shared key?!
asciilifeform: who the fuck 'backs up' per-luser pw.
asciilifeform: why would the admin want to back it up ? if luser luses his pnoje, he goes to beg and be issued new code, neh
ben_vulpes: or 'IT will want to know how to upgrade users devices without revoking every key and leaving accounts 'unsecured' during the TOTP rotation"
ben_vulpes: im astonished this idiocy made it past the enterprise sales people; 'IT will want to know how to back these codes up'
asciilifeform: ben_vulpes: naturally they'd rather lusers not have 'lift the seekrit out of the pnoje' button, or they'll push it and write on postitnote
ben_vulpes: asciilifeform: yr defectively steeped in security theater
ben_vulpes: in other top notch lolz, the redhat "totp" ios "app" does not provide for backing up the shared seeds.
ben_vulpes: the real fun is in asking "what word do you want me to use instead?" and then using it in such a way that all the partizans wince, knowing that word means The Bad Thing now.
asciilifeform: '...this linguistic battle is inherently non-winnable, as can be seen from how every term that was originally meant to be non-offensive, such as “moron”, “retarded” and “imbecile”, always became a schoolyard insult in short order. ... This is inevitable because the underlying reality that these words refer to is horrifying, and everyone can see how bad it would be to get hit on the head ...'
asciilifeform: ( there is not, notably, any possibility of a pill that dun force cpointerism ; as gnatv is at birth a cpointeristic turd )
asciilifeform: if anyone knows otherwise, plox to write in.
asciilifeform: it relies , as is obvious , on the guts of gnat's main() initializer, that sets the turds . but in so far as i can tell , it is the same in all known gnats
asciilifeform: ^ used in place of , rather than in addition to, Ada.Command_Line
asciilifeform: aaaaand here: http://wotpaste.cascadianhacker.com/pastes/tPv4l/?raw=true << is the tentative pill.
ben_vulpes: "humans can't be defective!" "well what do you call it when they're missing a chromosome, eh?"
ben_vulpes: it's wildly entertaining watching people thrash in their own contradictions
ben_vulpes: a few short seconds later the same person practically pulled a 'halt and catch fire' when attempting to use a word that doesn't mean broken to describe f. ex. chromosomal abnormalities
asciilifeform: and hats off to the 1st reader here who immediately thought, reading the ads earlier, 'wtf does it mean and who ever heard of ~removing~ arguments from cmdline ?!'
asciilifeform: ( the 2ndarystack is used to keep around the lengths of this variable-length turd that got thrown on the primary. )
asciilifeform: i'ma paste , for the hall of fame:
asciilifeform: here's the trisomy artifact itself : http://wotpaste.cascadianhacker.com/pastes/PlehJ/?raw=true
mircea_popescu: asciilifeform you're missing the point. perhaps the reason YOU didn't think about it before is that YOU are malicious ?
asciilifeform: here's the original, appreciate the horror : https://www2.adacore.com/gap-static/GNAT_Book/html/rts/a-comlin__adb.htm + https://www2.adacore.com/gap-static/GNAT_Book/html/rts/a-comlin__ads.htm
ben_vulpes: i had to laugh last night; someone at the table wanted to stake out the position that "people with downs syndrome aren't defective. you can't have defective humans!"
asciilifeform: it sits on the edge between outright wrecking and simple down's syndrome
asciilifeform: well i have nfi , but it entirely needlessly drags along the secondarystack thing
asciilifeform: just as easily it is possible to give it a 'here's an empty string of length L to take a shit into, for each cmdline param, and if the actual exceeds it, trigger constrainterror'
asciilifeform: and in the process discovered that the original was ~maliciously~ stupid, there is NO reason why it HAD to return an unknown-length string value
asciilifeform: in other noose, asciilifeform wrote a sane commandline-getter for gnat
phf: mp is quite dangerous with them bash scripts
BingoBoingo: In a bit under an hour, I visit la ciudad vieja for the first time and there spanish test
BingoBoingo: Outside of tourist and mega business areas the trend seems to polished interiors while letting exeteriors do as they do.
BingoBoingo: On la avenida, such a building would have been kept its bones and been given a new facade because gotta sell vacation homes. 2 blocks away? What tourist would go there?
BingoBoingo: mircea_popescu: Ah, there's a few of them scattered around my Barrio, but few and usually at least dos quadras off la avenida 26 de de Marzo
mircea_popescu: and in other vocational training, http://78.media.tumblr.com/563edda993665378ae74ec037dd28b6f/tumblr_nkd0rtUuuS1u06pkwo1_1280.jpg
asciilifeform: the surviving hruschebas asciilifeform saw in bucharest, however, looked quite like this
mircea_popescu: http://www.thedrinkingrecord.com/wp-content/uploads/2017/12/P1000071-1024x768.jpg << check out where 1980s moscow went!
asciilifeform: incidentally bellard's tcc is not in any simple way trimmable, no autoconf garbage or the like, in there.
asciilifeform: in other olds, asciilifeform found insinuations that gcc 4.7 was at some time built successfully using tcc. but no detail re how, in particular which tcc, where to get that
asciilifeform: and indeed 'daytime tv starlets' and 'fat brown women behind fast food counter' are far closer to owners , than the engineer.
mircea_popescu: and no, "everyone" is not a fucking answer. state exists to enforce priviledge against the mass. whose.
mircea_popescu: if you don't own it, who the fuck does ? daytime tv starlets ? fat brown women behind fast food counter ? who ?
mircea_popescu: phf basically, dedicatedly "we don't own the state" engineer-mind, the exact correlate of http://btcbase.org/log/2015-03-06#1043852
asciilifeform: phf: there is no amount of bending-over-backwards that is toomuch for these usefulidjits
asciilifeform: it isn't clear that it is even possible to carry out an intellectual exchange with such folx, who have 0 shared priors with actual people. the only conversation can then consist of the lime pit.
phf: i mean guy says so himself "Specifically, you never really get absolute proof. There’s always some innocent or coincidental explanation that could sort of fit the evidence — maybe it was all a stupid mistake."
asciilifeform: i was abouttosay, what good does 'proof' when reply is inevitably 'but where is the proof of yer proof's proofiness'
mircea_popescu: though ALL SORTS of rank imbeciles, such as that "pirate party" fucktard, had complaints of the proofy proof flavour.
mircea_popescu: "but we were never able to find it or prove it existed." << we still never found the gnupg culprit ; and most interestingly to my knowledge NONE of the idiots with broken keys put a post on their blog, "here is the software that made it"
mircea_popescu: btw that picture of matthew green is so ridoinculous...
phf: yeah, bill newman had to rip it out when he was doing the original bootstrapping work
phf: there's two sbcl apologists further in thread, one of them saying "I don't mind provocative /per se/, but what you were saying gives the a| impression that SBCL is willfully bad, as opposed to in development. But lumping it in with willfully noncompliant systems for this reason, | given it's version number, is inappropriate." and the other one is a core dev saying that they might add it. of course the expected behavior is still not there
phf: there's not a single article on the subject of compilation, but here's the complete thread https://www.xach.com/naggum/articles/search?q=recompile+reeval&sort=of specific test that he proposes is in https://www.xach.com/naggum/articles/3243682048034314@naggum.no.html and the "dun work" reaction https://www.xach.com/naggum/articles/3243737082731156@naggum.no.html
asciilifeform: the unix dir tree concept braindamage is a gift that keeps on givin', eh
phf: from location A to location B to location C where they are expected)
phf: fwiw bulk of these tools have been written through the 90s and what was worthwhile from orcland was published that way then. until silent takeover by latex & 1.8gb tex installations happened and none of these tricks work anymore (because the necessary hooks are so deep within the layer of cruft it's near impossible to get to them, and one way they did it is through standard file system lay out, that requires a chain of compilation stages to move files
mircea_popescu: no further "art" is needed in that context.
mircea_popescu: inferiority of inferior must be baked into every single UNIT of everything around them
mircea_popescu: then can resume smiley usage.
a111: Logged on 2017-12-20 19:00 trinque: then the kids can run wild with their UTF128s and nobody has to care
mircea_popescu: http://btcbase.org/log/2017-12-20#1755462 << because the stupid woman doesn't want to be on the reservation alone. she wants to live in your house and get in front of the tv while you're watching it.
a111: Logged on 2017-12-20 19:00 trinque: I dunno why orcograms aren't done the same way as image formats. doesn't need to be built into the OS.
asciilifeform: 1 of the very few antipoettering bugsprays available to the wotless -- writing 'into a desk'
asciilifeform: phf: i'ma guess this is 90% of the world of 'stfu, no , i won't publish it'
phf: heh, while looking for that rant "I have designed and implemented one for my own needs, but I find the number of disgusting losers who would benefit from it if I published my code to be too high."
a111: Logged on 2017-12-20 18:29 phf: the fact that macro evaluator inlines both compiled and non-compiled macros, which means that you have to manual track macro dependency and tediously reevaluate even when working in an interactive environment
phf: https://blog.cryptographyengineering.com/2017/12/19/the-strange-story-of-extended-random/ in unrelated
trinque: ah, my point was that the roman alphabet is sufficient for one of the most expressive languages to exist, so arguments that orcograms are needed would need to explain that.
asciilifeform: rather than in favour of 256bit or whatever chars.
asciilifeform: phf: strictly arguing against 'worked for the romans' mode of thinking
asciilifeform: they 'worked' in the sense that 'romans' were ok with overflows, crashes, never heard of what is exploitability
trinque: ah we're talking about linked-list strings then?
trinque: "neener, worked for the romans" ?
phf: trinque: ccl used to do it that way actually, interested parties might want to poach that code. they call the concept Rune and it's basically a way to support orcograms in a 8bit lisp
asciilifeform: trinque: is 'character' concept built in ? if yes, then you have what we have
trinque: I dunno why orcograms aren't done the same way as image formats. doesn't need to be built into the OS.
asciilifeform: then even 64bit per char beats utfism
phf: you kind of have to these days yes
a111: Logged on 2017-12-20 18:27 phf: the fact that character type is not dynamic (which to be fair is the property of all free lisps for some reason), so if you're dealing with text, you're forced into 32byte per character nonsense
asciilifeform: this is possible. when's the last time you saw a cpu-bound proggy in cl tho
a111: Logged on 2017-01-19 17:38 asciilifeform: also (and iirc i discussed this on my www at one point) the correct approach is to ditch the native compiler, in favour of the interpreter, hand-compiled to fit in L0 cache
phf: cmucl fwiw was designed like a lisp machine (though it had damage done to it by modernizers already), where the evaluator + vops was you primary interaction mode, and compilation was a way to evaluate a piece of code to a vop like status
asciilifeform: the wedge between cpu and ram clocks today would , i suspect, wipe out the performance difference for most problems
a111: Logged on 2017-12-10 15:41 asciilifeform: http://btcbase.org/log/2017-12-10#1749266 << asciilifeform has been chewing on this conundrum for a while. the inevitable pill is a minimal ( see also e.g. http://btcbase.org/log/2017-11-12#1736844 ) but reasonable microscopic interpreter ( likely schemelike ) in asm; and from it, to climb back up.
phf: none of these are properties of sbcl past certain vintage though though, sbcl is already a modernization of common lisp
phf: i think naggum has a rant about the last one
phf: the fact that macro evaluator inlines both compiled and non-compiled macros, which means that you have to manual track macro dependency and tediously reevaluate even when working in an interactive environment
phf: the fact that character type is not dynamic (which to be fair is the property of all free lisps for some reason), so if you're dealing with text, you're forced into 32byte per character nonsense
phf: the awfully pedantic defconstant behavior (which sbcl specific, and which requires packages like alexandria to have asinine define-constant, which for all practical purposes is what defconstant is supposed to be)
phf: but specifically it was small annoyances with "modern" enforcements. like style warnings, or my personal pet peeve, the fact that you can't shadow locked packages without having to unlock
phf: asciilifeform: you know after staring at a lot of bad c code and last two days worth of conversations, i don't think there's much wrong with sbcl, but then i haven't looked at sbcl code in about a year at this point. i think i was mostly objecting to overall trajectory of lisp ecosystem
trinque: nls, utf8, ipv6 support, all "lets bolt gendercommits to the side"
asciilifeform: ( at least as much so as my other gentoo boxen )
asciilifeform: fwiw the box appears to be stable, usable, nao.
phf: looking at their commit history there's a lot of "utf8 support in ..." and "nls ..." which is probably the proverbial fleas bringing dog
asciilifeform: ben_vulpes: ain't that the whole point of running a gox
asciilifeform: in other noose, asciilifeform found it impossible to rebuild http://btcbase.org/log/2017-12-20#1755200 under gcc 4.9
phf: i think he doesn't like that they keep poaching his changes back into official cvs
phf: unmodified Linux kernel (has made zero progress on this front in the
phf: source development in the slightest. He's putting out a windows-only
phf: in charge of the project, one who apparently does not understand open
phf: tinycc's maintainership. It has the tinycc.org domain, and Fabrice
phf: But these days, my complaint is that I have no confidence whatsoever in
mircea_popescu: is this like... V before V, ie, all-the-disadvantages-and-no-more ?
phf: "then told me that I had to abandon my cleanup work and start over on his tree, and explain everything to his satisfaction (as a Windows guy) before it could go in"
mircea_popescu: funny how the "days gone by" immediately reconstruct themselves just as soon as one ditches the rotten principles preventing them.
diana_coman: heh, in good old traditions of a long-gone world and age, eulorans are rather suspicious of change and they aren't old even!!
mircea_popescu: but look on the bright side danielpbarron : if that process ain't making you a scientist, nothing will.
mircea_popescu: i just get pissy when my brilliant ideas can't be implemented like, the next day.
asciilifeform: emerge -e world , on gcc4.9, did the trick.
mircea_popescu: "mp, why isn't your infinite world update, announced LAST YEAR, live yet ?!?!" "because ints don't work on computers. also because merely rewriting the crypto layer ain't fucking enough. and also because FUCK YOUR UGLY ASS MOTHER AND THE IDIOT DRUNKS SHE KEEPS FUCKING, FUCKO!"
diana_coman: in other words a whole new set of worms, veryverynice
diana_coman: thing is now I'm even *less* comfortable using that whole mpi thing... makes me wonder what else is in there and not yet spotted
diana_coman: for the very impatient: caller fails on the cases where it uses that broken macro i.e. any shift by a multiple of BITS_PER_MPI_LIMB; 0 is just one case, not the only one; further up, caller avoids the issue, as stated
a111: Logged on 2017-12-20 01:37 asciilifeform: http://btcbase.org/log/2017-12-19#1754868 << this wasnt finished. that thing does nuffin , regardless of the loop termination condition
diana_coman: http://btcbase.org/log/2017-12-20#1754999 <- it is broken anyway, yes; at the very top it works as I said: by avoiding it basically; in any case, hang on until tomorrow as next chapter will have to be patching this and sorting it out
BingoBoingo: cable, and satellite providers, as well as to consumer smartphones through the Wireless Emergency Alert system," reports Android Police. From the report"
BingoBoingo: First they make mantadory annoyance broadcast in old country when children go missing, now: "The FCC recently announced a new alert program called "Blue Alert" that will notify the public of threats to law enforcement in real time. "With the creation of a dedicated Blue Alert event code in the Emergency Alert System, state and local law enforcement will have the capability to push immediate warnings out to the public via broadcast,
jhvh1: BingoBoingo: (ticker [--bid|--ask|--last|--high|--low|--avg|--vol] [--currency XXX] [--market <market>|all]) -- Return pretty-printed ticker. Default market is Bitfinex. If one of the result options is given, returns only that numeric result (useful for nesting in calculations). If '--currency XXX' option is given, returns ticker for that three-letter currency code. It is up to you to make sure the code is a valid (1 more message)
mircea_popescu: and then we can play golf.
asciilifeform: how about it goes to oven. and the crapola that 'needs' it, also to oven.
phf: plan9 rewrote their soelim as a shell script..
trinque: ah the udev rules thing; asciilifeform's solution would be better
mircea_popescu: does gentoo bake dns into the kernel, debian style ?
trinque: asciilifeform: thought I touched something in there that does it
phf: mircea_popescu: well they've believed in the whole "single tool for a job" thing back then, and yes it was a hack (not in a sense that soelim is such a tool, but in a sense that tools that soelim is a glue between poorly designed tools)
asciilifeform: to disable the infuriating 'let's rename eth0 to asjtghuidfjhiuorhjgr0 ' item
trinque: (the other cut of the lilo thing is to simply say "thou shalt not have other drives plugged in when cuntoo is spawning)
trinque: if anybody knows the answer to that riddle, the rest of the "reproduction" is trivial copying of files
mircea_popescu: and ftr, there's no excuse to EVEN HAVE soelim at all ; let alone as a standalone wtf
phf: mircea_popescu: well, ~i've~ found something to hate, so i joined the fray
trinque: real quick, only serious thing missing from the cuntoo script is commanding lilo to ignore all devices but the target disk.
mircea_popescu: is the hate stirll travelling or is it merely a universe-zsized ball of hate ?
mircea_popescu: so i go to argue the point, fall upon https://www.latex-project.org/news/2017/12/15/github-move/ "news"
phf: what trinque said, there's no "straight latex", it's 1.6gb of liquishit
mircea_popescu: fuck, they could be html and it'd be better than this nonsense.
asciilifeform: troff, roff, groff, whatevertheeverlivignfuckroff.
asciilifeform: ( i fully believe that it -- out of the box -- won't )
asciilifeform: mircea_popescuL then THAT's what needs doctoring
phf: mircea_popescu: but the factuals are not necessarily under dispute (~soelim~ is not a phototypesetter is what i said). original hate was against "never seen this wrecker thing before", then when new fangled thing turned out to be an old tool, hate shifted to 1960 phototypesetters. methinks the point is a traveling one..
trinque: lacks the whole reproductive bit
asciilifeform: a 2002 kernel will neither boot nor run on extant iron. but userland can and must.
asciilifeform: ( also i'm beginning to suspect that i'm doing this all wrong. prolly what oughta be done is to track down freebsd circa 2002 , ALL of the necessary pieces, and work from THAT . )
mircea_popescu: phf let's stick to factuals. 1. is groff or is groff not a "free and open" gnu theft of troff ; 2. was or was not groff a thinly veiled excuse by at&t coders who wanted a pdp to get it, because "they'll make a patents editing system" ? 3. did they or did they not simply copy roff, 1960s era item ?
mircea_popescu: it's a fucking metal chain. they make industrial abrasives out of chain.
mircea_popescu: how the fuck can he do that ? does he have NO sensitivity whatsoever ?
mircea_popescu: and in other "please explain this to me"s, http://78.media.tumblr.com/9bdf3b8432f6eaee2cf4ea9bca9918de/tumblr_neb5lycylT1sqopubo1_400.gif
trinque: the ear on this guy
asciilifeform: why is this warcrime on the box.
asciilifeform: me neither
mircea_popescu: i honestly didn't even fish "soelim" out of the zsazsagabordaemon
mircea_popescu: you don't understand how the logic works.
asciilifeform: http://btcbase.org/log/2017-12-20#1755201 << i've never heard of, or seen , this item before, it ain't on any other box i have . and yet it breaks man pages -- all of them -- on the box.
asciilifeform: i can neither add to nor subtract from this.
mircea_popescu: the greatest trick the devil ever pulled was convincing people they can't possibly say "to hell with ye"
asciilifeform: Unicode has changed over the years. Unicode code points no longer fit into ...
mircea_popescu: https://archive.is/vVMM2#selection-1935.0-2097.0 << preserved for future generation lulz (the original dir was /torvalds/linux/blob/master/include/linux/nls.h )
a111: Logged on 2017-12-20 03:17 asciilifeform: trinque: forget autoconf flags. i want to disable the generation or loading of dyn libs, period.
mircea_popescu: there's literally an "utility" to munge dots into filenames.
asciilifeform: ( picture the elephantine drepper glibc in every bin )
asciilifeform: otherwise 0 point
phf: hah. well then
asciilifeform: trinque: forget autoconf flags. i want to disable the generation or loading of dyn libs, period.
trinque: of course, not everyone implemented the static use flag.
asciilifeform: 'The GNU C++ team works hard to avoid breaking ABI compatibility between releases, including between different -std= modes. But some new complexity requirements in the C++11 standard require ABI changes...' motherfuckers
asciilifeform: wonder if there's a way to ban it, for whole box. permanently.
trinque: asciilifeform: https://developers.redhat.com/blog/2015/02/05/gcc5-and-the-c11-abi/ << related.
asciilifeform: motherfucking dynamic linking.
trinque: aha, I had to build 5.x, gcc-config to switch to 5, then build 4.
asciilifeform: that's what was in the stage3
trinque: asciilifeform: I referred to the stairstep down to get gcc 4 earlier.
phf: asciilifeform: one property of the new vdiff already is that ---- situations work, e.g. http://p.bvulpes.com/pastes/0Niwr/?raw=true
asciilifeform: man-db dun re-emerge, either
phf: i wonder if we're just witnessing some sort of criticality point, where everything is starting to rapidly deteriorate under the weight of maggot work
asciilifeform: elsewhere on the net, 'We have received reports that the man-db package as supplied in Debian GNU/Linux 2.1 has a vulnerability in the zsoelim program: it was vulnerable to a symlink attack. This has been fixed in version 2.3.10-69FIX.1' << ahahahaha THAT's why it's in there.
phf: well, now comes the hard part :)
trinque: still helps narrow the "what might be interesting" a bit
trinque: mhm, I don't think the menuconfig step can be avoided for a serious kernel.
asciilifeform: ( goes blindly by what's loaded, but not all mods actually abort if they dunfind the iron )
a111: Logged on 2017-05-11 18:02 trinque: could build all video related modules, then reboot, modprobe them all, cd /usr/src/linux && make localyesconfig/localmodconfig
a111: Logged on 2017-05-11 17:43 asciilifeform: trinque: i'm particularly curious re how you trimmed modules. many crapolade modules don't give any obvious indication that they are useless, there is no mechanism for generating a list of 'THESE we actually need, because of the installed iron, and these -- not'
asciilifeform: in other finds, http://btcbase.org/log/2017-05-11#1654585 >>>> 'make localmodconfig' actually does it.
phf: my concern is post-trump their going to churn out stuff like dunkirk, men films about men bonding for men that are menly
mircea_popescu: i mean... they played house since they were 5yo and mom bought them a cubic metre of plastic, HOW HARD COULD MOVIES BE
mircea_popescu: it's this very fucking thick vein of ustardian dumb, with "strong" women of a very peculiar chimp-like sort, and token "men". i suspect the whole thing is a continuation into a thin pretense of adulthood of some idiot girls' ken-and-barbie pubescent fantasies.
mircea_popescu: in other isadumba heathcote highlights, "Christian and Ana decide to rekindle their relationship, except this time there are no more rules or punishments."
mircea_popescu: i was not inb the slightest appointed. i knew going in it's gonna be CGI-for-TV. with a cast of idiots...
mircea_popescu: oh, and the ATROCIOUS "computer enhanced" female actors. jesus god really, that untalented hack heathcote not only missed her only life's calling (which doubtlessly is playing the WAG for some retarded athletic team from aussieland) but actually looks like a whole filing cabinet's worth of anime fell on her ?
mircea_popescu: hanbot wtf was the canada castle vampires atrocity ?
hanbot: iirc he objected to the lack of trees in the landscape and said something about there not being any film for old men either and turned it off. but i could be misremembering...
mircea_popescu: it's not the usual "here's four dumb bitches on a TV show set" like that atrocity with johnny depp
mircea_popescu: it's a wonder he and norton didn't end up married. he could have implanted all the tit fat they scooped out of angelina jolie and adopted a buncha west african urchins.
mircea_popescu: in other not-really-news, 1408 (cussack, jackson) isn't even that terrible.
trinque: which doubtful they were all modified.
trinque: anyhow running digest on every single ebuild just means you're rehashing all the files for each ebuild.
trinque: as things get reposessed from the gentoo shitgnomes, can move their modified ebuilds from /usr/portage into /cuntoo or w/e
trinque: ah. there's a mechanism for this that might be cleaner than editing the portage dir. I intend to use it in the cuntoo thing.
trinque: I dunno where you got the "digest" step; it's something you'd be doing when heavily modifying or producing own ebuilds
trinque: you'll notice if you reinstall items, it's not downloading tarballs again; it's finding them in the distfiles folder.
trinque: literally only thing necessary to make this happen is to fill /usr/portage/distfiles (or wherever you've declared distfiles to reside) is filled with what the ebuilds you use will demand.
asciilifeform: they're what you get when you did emerge --sync
asciilifeform: there's one for every known 'gentootronic' item that one could build.