asciilifeform: meanwhile, in 'men alone', https://www.floodgap.com/etc/machines.html ☟︎

asciilifeform: hanbot: it's a livecd, naturally regens host key erry time you revv it up

asciilifeform: hanbot: if you're concerned re mitm, ask BingoBoingo to log in via console and gpg you the current hostkey to

asciilifeform: morrow

asciilifeform: ( and/or log in via your shell acct , where you know the host key already )

asciilifeform: on the uy1, that is ^

asciilifeform bbl, meat

asciilifeform: in other noose, adlai apparently sobered up, and blogs, http://80.244.243.194:7421

asciilifeform: seems to be in medical school or sumthing like.

asciilifeform: humanitarian(tm)(r) democratic(tm)(r) sabotage

asciilifeform: 'US Secretary of State Mike Pompeo said Maduro’s government only has itself to blame for power shortages in Venezuela, noting sarcastically that “Maduro’s policies bring nothing but darkness.”' << lol!! ☟︎

asciilifeform: hanbot: i can tell you ~what~ you saw, tho not yet why : the linux kernel make starts asking itemized config q's if it sees sumthing in the given config that dun add up to something 'menuconfig' could have shat out, by its lights ( e.g. a module for $device is enabled, but 1 of its deps aint )

asciilifeform: hanbot: this also happens when you used a config baked for a certain kernel, but then feed it to another (usually moar recent) kernel's make

asciilifeform: it sees sumthing unexpected, and switches to manual derpery

asciilifeform: nao what i do not know, is how this scenario can play out using trinque's cuntoo kit -- iirc he includes both a particular kernel source and a config (for 1 of his irons) that was known to be edible by it

asciilifeform: hanbot: did you perchance hand-tune something in that config prior to building kernel ?

asciilifeform: 'found I could replicate mod6's process of copying the .config file in /usr/src/linux into the cuntoo/config directory' suggests that this build was using a non-trinqueian .config ?

asciilifeform: where did the copied one come from orig.?

asciilifeform: !!up lobbes_field

asciilifeform: lobbes_field: imho it's an asinine default behaviour of linus's builder ; tho the alternative ( build a ball of ??? that fails to boot ) may be equally asinine

asciilifeform: so he took the 'simpler evil'

asciilifeform: hanbot: that answers it then. that one contains some flag that trinque's kernel has nfi what to do with. ☟︎

asciilifeform: and, annoyingly, won't say which.

asciilifeform: ( this is to be brought up at linus's impalement )

asciilifeform: the way i handle this , is when building kernel with an older config, i use the menuconfig util, and have it eat the prev config

asciilifeform: then manually walk over the result

asciilifeform: this is prolly not an answr that will make hanbot happy. the only good news is, this only gotta be done 1ce per kernel-iron combo. ☟︎

asciilifeform: iirc trinque had an experimental proggy that takes a running kernel's lspci / lsmod output, and diddles an existing config so as to give a kernel that boots on $iron . but afaik not yet published. ☟︎

asciilifeform: ( if you were to take trinque's example config, your kernel will boot but will panic when looks for root partition, as it won't find that iron's raid card )

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 ☟︎

asciilifeform: ( trimmed manually )

asciilifeform: all pizarro-owned x86 boxen in the rack, are currently using this config

asciilifeform: ( and of course the snsa-operated dulap )

asciilifeform: hanbot: lemme know if you run into barf

asciilifeform: hanbot: if it ends up asking you q's , like prev. time, feel free to press 'enter' and let it give the default answers -- they come from the existing config (when available) and from default of the given kernel's (if not) . this generally gives bootable kernel, that you can trim later at your leisure.

asciilifeform: ( i.e. it ~may~ end up containing useless modules, that you will later want to cut out, but ~will~ contain the necessaries given in the supplied config )

asciilifeform: since mircea_popescu is asleep, i'ma 'fill in' for him and note ftr that the necessity for this process is indeed a warcrime of the gnutards, and really not how sane configurator of any kind oughta work

asciilifeform: sadly it's how the current ball o'crapola worx.

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: the obv hypothesis is that the gnutards ended up happy with the position where 'priesthood' builds kernels and users blindly eat the binaries, etc ☟︎

asciilifeform: guten tag mircea_popescu !

asciilifeform: http://btcbase.org/log/2019-03-08#1900962 << near as i could tell, subj is a kind of http://btcbase.org/log/2017-08-03#1693150 , i.e. junkyard dog ☝︎☝︎

asciilifeform: http://btcbase.org/log/2019-03-08#1900966 << not clear to me that 'isms' are in play : afaik it's moar of the thing where the anglos have same relation to other folx as worm to apple ☝︎

asciilifeform: oh hey BingoBoingo how didja get her out of vuvuzelistan ?

asciilifeform: lol she has mains current ? potato battery ?

asciilifeform: very korea

asciilifeform: ( how do you suppose korea ended up korea )

asciilifeform: prior to usg-engineered 'international' blockage, ~north~ was the industrial kr.

asciilifeform: *blockade