log☇︎
▆▅▄▂▁▁▁▁▁▁▁▁⏐︎▁▁▁▁▁▁▁▂▁▁█▄ 1837
hanbot: so there i am merrily entering choices into the kernel config's endless querying on the tail of my cuntoo installation attempt, and i'm noting down all the modules it asks about that don't appear in http://btcbase.org/log/2019-03-08#1900940 for posterity, during which i ctrl + c on the wrong of the two keyboards i'm handling while trying to copy a module name and bam, make dies, which means kernel configuring dies, which means bootstrap.sh dies, ☝︎☟︎
a111: Logged on 2019-03-08 18:06 asciilifeform: hanbot: see if you can build using http://nosuchlabs.com/pub/conf_current.conf , it is an asciilifeform-sewn config for the specific iron you happen to be on
hanbot: which means i have yet another incomplete cuntoo install with no vpatch and yet no way to start again without another freakin' reboot. it's like walking a tightrope, here i was worried the power'd go out or w/e, but no, fingers got confused after 30m of back and forth, fuck me.
mircea_popescu: hanbot this sounds like EXACTLY what the problem has been, all these years.
mircea_popescu: there's a difference between selecting for intelligent users and selecting for inept hoop jumping acrobatic users -- and "foss" managed to implement the 2nd kind while loudly making postureclaims as to everything under the sun.
mircea_popescu: in this very specific sense, "free and open source" is WAY worse than microsoft apple etc.
mircea_popescu: but no, linux never worked.
hanbot: i dunno, shit's supposed to fail if you do the wrong thing. possibly i'm a moron for making it too easy to do the wrong thing, keyboards oughta be 10ft apart, give second to surgical assistant, whatever. but it is fucking frustrating.
asciilifeform: hanbot: mine are min. of 1m apart always, for this reason. this dun mean that mircea_popescu is wrong tho, re opensores.
asciilifeform: tho it aint clear to me than the e.g. crapple rituals, make any moar sense
asciilifeform: ( the subj of microshit, i'll spare, tho could expound.. )
asciilifeform: 'killer micro'(tm) never 'worked' arguably.
asciilifeform: most complicated mechanism i ever used that 'works' , in light of mircea_popescu's concept thereof, is.. idk, kalash
asciilifeform: errything else seems to require fiddling.
mircea_popescu: dude, this "x distance apart" is like the fucking speed bumps. brilliant fucking idea, "how about everyone pays a tax so that some edge cases benefit"
mircea_popescu: fuck that dumb shit.
mircea_popescu: in more practical sense : ctrl-C is broken-by-design, in that it is ambiguously used to either mean "kill this task" or "kill all tasks". note how ctrl-c doesn't kill THE TERMINAL. it needs ctrl-d for that.
mircea_popescu: which is JUST AS BROKEN BY DESIGN. ctrl-d will end a file AND kill a terminal, but not touch a task. ctrl-c will kill n levels of task depth, as in her example, FOUR. ☟︎
mircea_popescu: this is fucking stupid all through.
mircea_popescu: time and again we're back to ye olde "oh, line, you mean paragraph" pile of accidentally-grown-never-designed festering sores.
asciilifeform: whole concept of 'current task' is perlesque liquishit
asciilifeform: e.g. you ctrl-c and it nukes ~child~ of process however many layers deep, as in hanbot's example, and instead of propagating the kill up the tree, 'returns' barf uptree
asciilifeform: witness also, how unitardix makes 0 distinguish b/w operator- and mechanism- initiated processes
asciilifeform: 'ok, ctrl-c? i'll assume you meant the last of the 9000 jobs you just spawned, right'
asciilifeform: hanbot's ctrlc only propagated cuz script was linear.
asciilifeform: mircea_popescu: if some part of the shitstack 'was designed', i cannot say what it was
asciilifeform: it was 'designed' like dog 'designs' turd as it emerges from arse.
hanbot: BingoBoingo please reboot me yetagain, with my compliments to your soles.
BingoBoingo: hanbot: Is it alright if the reboot waits until morning?
BingoBoingo: Eh, I'm still up. Will put the shoes back on and remember to open the terminal before I take shoes off text walk
trinque: y'all are having hanbot work in a livecd?
trinque: this is cruel even by bdsm standards.
BingoBoingo: It's a gentoo liveusb, but yes it is seeming so
trinque: http://btcbase.org/log/2019-03-08#1900952 << he did, as I've said before http://btcbase.org/log-search?q=localyesconfig ☝︎
a111: Logged on 2019-03-08 18:15 asciilifeform: why linus et al did not supply a ready-built http://btcbase.org/log/2019-03-08#1900938 util, remains a mystery to asciilifeform , just as he found it mystery in '90s
asciilifeform: oh hm.
asciilifeform: gotta try this
trinque: http://btcbase.org/log/2019-03-08#1900931 << it's actualy the opposite. kernel makefile found that .config lacked a value for a *new* key present in the trinque-supplied kernel, so asked for a value, suggesting default. ☝︎
a111: Logged on 2019-03-08 18:01 asciilifeform: hanbot: that answers it then. that one contains some flag that trinque's kernel has nfi what to do with.
asciilifeform: trinque: outta curiosity, hiw didja deduce this ? afaik barf is same in both scenarios?
BingoBoingo: !Qlater tell hanbot http://p.bvulpes.com/pastes/yRAfP/?raw=true reset
lobbesbot: BingoBoingo: The operation succeeded.
trinque: asciilifeform: that gentoo-specific patchset question is because these patches are present in "gentoo sources"
trinque: your asking did however send me on a spelunk through scripts/kconfig/conf.c by way of ./scripts/kconfig/Makefile
hanbot: BingoBoingo tyvm!
lobbesbot: hanbot: Sent 13 minutes ago: <BingoBoingo> http://p.bvulpes.com/pastes/yRAfP/?raw=true reset
trinque: this some serious dick-cheese and cum-socks tier c, gotos and all.
mircea_popescu: asciilifeform myeah.
feedbot: http://thetarpit.org/posts/y05/088-gutenberg-iv.html << The Tar Pit -- Gutenberg ASCII archive updated, now with 0.5% less junk
asciilifeform: spyked: download link is broken, redirects to 404
asciilifeform: spyked: http://p.bvulpes.com/pastes/Jmgst/?raw=true
asciilifeform: trinque: deedbot wedged ?
spyked: asciilifeform, I applied mircea_popescu's pill to block spam-linkers. pl0x to set referrer to http://thetarpit.org or http://lucian.mogosanu.ro
asciilifeform: spyked: aaa, seems to work, ty
asciilifeform: meanwhile, in unixtardation : apparently there is no known way to change PATH envir. var. for ~running~ processes globally
asciilifeform: ( why ? asciilifeform , for instance, sometimes gotta switch gnats , and the emacsen dun see it )
mircea_popescu: spyked prolly should redirect to explanation tho. 404 is ambiguous here ☟︎
asciilifeform bbl : ffa room
diana_coman: http://btcbase.org/log/2019-02-07#1893431 -> kid settled atm on heroes of might and magic II and can think of nothing else! he choose Necromancer ("which one has stronger troops?") and so he is working out ...percentages to know how many skeletons he should get. ☝︎
a111: Logged on 2019-02-07 19:12 asciilifeform: diana_coman: np. lemme know which flavours the kid ended up liking, i may have moar in the depths of the warez chests along those lines.
feedbot: http://qntra.net/2019/03/sears-sued-by-stanley-black-and-decker-over-limited-line-clause-in-craftsman-sales-agreement/ << Qntra -- Sears Sued By Stanley Black And Decker Over "Limited Line" Clause In Craftsman Sales Agreement
asciilifeform: spyked et al : http://nosuchlabs.com/pub/gutentext.tar.xz << mirror (replaced the old tarball) ☟︎
asciilifeform: diana_coman: neato, i once spent half a summer in 'heroes 2' also
feedbot: http://bvt-trace.net/2019/03/ffa-chapter-9-homework-comba-in-x86_64-assembly/ << bvt's backtrace -- FFA Chapter 9 Homework: Comba in X86_64 Assembly
asciilifeform: !Q later tell bvt http://bvt-trace.net/2019/03/ffa-chapter-9-homework-comba-in-x86_64-assembly/comment-page-1/#comment-12
lobbesbot: asciilifeform: The operation succeeded.
mircea_popescu: diana_coman right on schedule!
mircea_popescu: ftr, warlock has the stronger troops for large maps ; sorceress for medium. if you're looking for a shortcut to beating his ass.
asciilifeform: was astonishingly well-balanced game, imho
asciilifeform played it with brother
asciilifeform: btw, bvt , rax etc. ~are~ encoded as 1-8, the iron dun see reg names at all, the classic names are a convention of the asmers and the vendor docs. and imho remains on acct of the asinine x86isms like MUL which use fixed input and output regs, makes'em slightly easier to remember. ☟︎
asciilifeform: if you ever wonder why your x64 iron draws 50x the wattage to do same thing as e.g. rk, wonder no longer -- the insanity where shit gets moved around to accomodate idjit instructions with fixed in/out hoppers, the insanity where you gotta set prefixes to specify what width ~each operand~ is (why this is needed ? srsly) , all of this adds up to 3bil transistors that heat the room ☟︎
asciilifeform: ( and this is not even touching the subj of the tlb cache, which is ~1/3 to half of those transistors , which we have on acct of the idjit paging scheme )
asciilifeform: when you build 1 of these things, there's a set of decisions that end up determining shape of whole thing; and it so happens that intel made ~all~ of the most retarded possible choices. ☟︎☟︎
asciilifeform: aaand this is not even to mention their seekrit 'optimizations' behind the scenes.
trinque: diana_coman, other folks that have cuntooed, can y'all confirm that the paths that ended up in your genesis.vpatch do not in fact exist? I'd like you to reproduce the commands starting at line 114 of scripts/make_portage_tree.sh in your build directories, i.e. cd ~/src/cuntoo/build/cuntoo and then run them, as root ☟︎
asciilifeform: it is such a retarded design that even intel and microshit ~tried to escape~, in 1990s. but nsa decided that it ~likes~ x86 , and for it to remain cemented standard , on acct of http://www.loper-os.org/?p=1299 .
trinque: the paths ending up in your genesis vpatches are hard to blame on my script, rather than a difference between our vdiff executables.
trinque: the remainder of work here is resolving this issue (I have not had) with paths, after which we can start producing ebuilds for novel republican work atop the genesis. ☟︎
trinque: http://btcbase.org/log/2018-12-03#1878057 << I am currently running a build with a vdiff pressed to same. The only difference is that I have altered the gpr files to statically link. ☝︎
a111: Logged on 2018-12-03 21:48 diana_coman: hm, if it's indeed the tmp thing, it might be worth a try to press vtools to current leaf (i.e. vtools_tempfile_standalone or _notmp) and see if that cures it; my archive contains pressed vtools to ksum patch only, not further
asciilifeform: in lulz inspired by bvt's article, asciilifeform went and dug re 'modern' cpu arithm instructions, and found https://lemire.me/blog/2018/04/19/by-how-much-does-avx-512-slow-down-your-cpu-a-first-experiment/ << intel's crud apparently ~drops frequency~ if you use'em , ultimately nuking all gains from doing so ( they want you to use, so as to shit out binaries that crash on amd, but really gains 0 )
asciilifeform: i.e. they can't stuff any moar transistors in there, and end up offering the equiv. of ye olde 'winmodem'
asciilifeform: where yes it'll do a e.g. 512-bit add, but -- evidently -- using ~existing~ regs, and putting out same (or greater) amt of heat, and locking up the pipe