log☇︎
29700+ entries in 0.017s
lobbes: however on second run-through I indeed went back to read the scripts in tandem with the gentoo handbook (so as to actually understand what was going on) and produced a bootable genesis that verified >> http://blog.lobbesblog.com/2019/02/a-bridge-to-cuntoo-for-the-lenovo-x61-x86_64/ ☟︎
lobbes will admit to committing cardinal sin of not fully reading the cuntoo bootstrap scripts before my first run-through (which trinque rightfully whacked me over the head for)
mircea_popescu: one somethong to do with trinque 's unhapiness with the cuntoo userbase ; the other something to do with wtf to do re v & portage/ebuilds.
mircea_popescu to bed. but ima try to be on tomorro (tho prolly on the viaje nick) because it seems to me there's two different layers of unhapiness preventing cuntoo from making meaningful progress, neither of which properly gotten to the bottom of.
a111: Logged on 2019-06-22 19:03 trinque: these communicating over gossipd makes a pretty clear picture
mircea_popescu: (tl;dc : decade-old, filesystem-driven thing)
a111: Logged on 2019-06-22 18:36 asciilifeform: i.e. connect to one, its state changes, and it sends message to others, which majoritate ?
mircea_popescu: http://btcbase.org/log/2019-06-22#1919322 << one of the corps red hat bought and buried was arguably getting close. ☝︎☟︎
a111: Logged on 2019-06-22 18:22 asciilifeform: cuz imho an envir where you can build yer os/proggies at home, then upload whole thing to piz (or even yer own box wherever) an' run, and then snapshot, download state, run again at home, or (exotica) sync 2 running instances -- would be a win
mircea_popescu: http://btcbase.org/log/2019-06-22#1919311 << i think this is running in the wrong direction. just more shit to break / require rubber bads / touching just so and etc. ☝︎☟︎
a111: Logged on 2019-06-22 18:17 trinque: perhaps all that's needed there is a cut ISO.
mircea_popescu: http://btcbase.org/log/2019-06-22#1919303 << this may work. my takeaway was that item could benefit from a little polish, a few choice one-liners added to documentation/comments, that sorta thing ☝︎
mircea_popescu: this isn't because "we're building housing for the sort of braindead morons who literally can not avoid walking into fire", but because "holy shit, spending life avoiding spurious pitfalls is such a sad way to go about things".
a111: Logged on 2019-06-22 18:09 trinque: and perhaps this is what's wanted, but the ubuntu-like installer that supports all hardware without anyone needing to learn to spin a linux kernel is a different kind of item
mircea_popescu: http://btcbase.org/log/2019-06-22#1919297 << there's an immense difference between usability and nurturing idiocy. yes, "not walking into open flame" is basic test of cns functionality ; nevertheless patterns of bursting flames on timers are found in video game platformers, not in between one's bedroom and bathroom. ☝︎
a111: Logged on 2019-02-06 04:21 trinque: hanbot: hm, this got right past me. the cuntoo builder is 64bit only at the present.
mircea_popescu: now, if you wish for your takeaway from this to be "hanbot is not cool enough to run cuntoo" that's your priviledge, but i tell you i don't see the wisdom. for the same money you could say you never read the damned scripts, and butress the claim on eg http://btcbase.org/log/2019-02-06#1893199 ☝︎
a111: Logged on 2019-06-04 12:12 diana_coman: http://btcbase.org/log/2019-06-04#1917013 -> until we change OS basically; the test one was step towards Cuntoo and that's pretty much the only real reason for having 2 since playing around with the OS on a production server is rather iffy.
a111: Logged on 2018-11-27 18:18 diana_coman: asciilifeform, smg's test machine is running proto-cuntoo so it's not just any gentoo really
a111: Logged on 2018-07-23 14:08 diana_coman: eulora server is happily compiling on proto-cuntoo with ave1's gnat+gcc; all tests passed so far, LOC greatly reduced too, loads of shit cleaned away and discarded; we are looking forward to move it to production, so any eta for cuntoo?
mircea_popescu: there's on one hand the http://btcbase.org/log/2018-07-23#1837434 / http://btcbase.org/log/2018-11-27#1875247 / http://btcbase.org/log/2019-06-04#1917021 story arch, spanning a year. there's also the http://thewhet.net/2019/02/hanbots-cuntoo-bake-test-notes-part-i/ http://thewhet.net/2019/02/hanbots-cuntoo-bake-test-notes-part-ii/ http://thewhet.net/2019/03/hanbots-cuntoo-bake-test-notes-part-iii-with-prep-script/ http://t ☝︎☝︎☝︎
a111: Logged on 2019-06-22 18:07 trinque: I noticed that not a soul read the scripts that bootstrap cuntoo
mircea_popescu: http://btcbase.org/log/2019-06-22#1919296 << how did you notice this ? ☝︎
a111: Logged on 2019-06-22 16:43 asciilifeform: re: loose ends: fwiw asciilifeform did in fact add the final missing piece to mipstron. BUT! can't test with the dummkopf's orig linux image as he... guess wat, his system had little-endian word accesses but big-endian byte read/write ! so his image in fact will boot on NO existing mips, nor any afaik other emulator.
mircea_popescu: http://btcbase.org/log/2019-06-22#1919282 << this is such sad nonsense... ☝︎☟︎
mircea_popescu: you don't mean "pls try again" as in, issue command again ? as opposed to "put !!v strings in again" ? do you ?
trinque: was little more than "pls try again"; I think you caught me before I updated records
mircea_popescu: trinque, do me a favour and also encrypt to http://wot.deedbot.org/208FE107E970F53262C4951232992F13CFA6CD06.asc so i don't have to wake up the girls to do ahlf hour of typing for me again
mircea_popescu: whereas if we decide we dislike the "packages" abstraction (and not merely dislike it a little bit, but quite a lot, enough to justify a lot of rewriting) then the available solution's to just make one big v tree. coming with the obvious problem that if indeed the whole world's just one tree, then trying to play BOTH duke nukem AND warcraft 2 will result in two copies of the kernel compiled, like if we were idiots.
mircea_popescu: in this context then, if we decide we like the "packages" abstraction, for whatever reason, the obvious solution would be to maintain ebuilds of various vtrees as packages, and emerge them into a desired pile together.
mircea_popescu: whereas implicit v-ism would be "all code is made one pile, then built once and linked, and that's it". ☟︎
mircea_popescu: i suppose the one true break here, is that portage system actually excepts to build and link by bits. "out of the codemass intended to be used, arbitrarily selected portion A is built and linked first, producing object files, then B is built and linked against those binaries"
mircea_popescu: well, in gentoo world. in tmsr world, what orchestrates that is v.
trinque: what orchestrates building A first, then B, and finally C that links A and B, is portage
mircea_popescu: does it have to be gprbuild specifically ?
trinque: moving every needed package to gprbuild will take years, and sure.
mircea_popescu: well, wouldn't this be better than just moving everything over to portage ?
trinque: yep, if it had a sensible build system, and the work was done to port needed items to that build system, portage would be obviated
mircea_popescu: so is rather the problem that v-tron doesn't come with the right toolkit ? should get a tar and an interface for make ?
a111: Logged on 2019-06-22 18:06 trinque: lmk if still not getting anything
trinque: the deal of portage is it does what'd otherwise be days of pointless labor untarring and making programs to stand up a new system
mircea_popescu: understanding's not a mechanical task.
asciilifeform: this resembles asciilifeform's orig. argument against having to write vtron -- 'just press the fucking patches by hand, lazy people'. but mircea_popescu didn't buy it then, so had to write vtron.
mircea_popescu: is there something mroe to this i'm missing ?
mircea_popescu: this seems a fundamentally bad deal to me.
mircea_popescu: at the very rock bottom of this : the ~deal~ of portage is that it installs things for you without you necessarily understanding why. this is the pay-off, yes, "you don't have to be concerned with every little detail" or however it goes. and the cost for this is, that you don't get to understand how it installs things for you. because ultimately, you don't, whether you want to or not entirely immaterial, ungermane an' spur
asciilifeform must go to a lengthy meat chore ; bbl
a111: Logged on 2019-06-22 22:00 mircea_popescu: i mitigate this problem by very pointedly only buying certain kinds / classes.
trinque: retrieving from power rangers can be snipped off trivially
trinque: this is why I packed every dep tarball into my snapshot
mircea_popescu: i mean, maybe all local wot failed to sign a patch portage deemed essential so it downloaded it from power-rangers.net. yes ?
mircea_popescu: that also wouldn't be a trb server, practically speaking.\
trinque: mircea_popescu: end up with a working trb-running server more quickly than I do today
asciilifeform: corollary to this q : how would a 'trb ebuild' differ from the trb vtree as it stands ?
mircea_popescu: trinque, let's go at this a different path. what would you even do with a trb ebuild ?
mircea_popescu: i evidently have, the damned story's in the recent logs.
trinque: my contention is there won't be gentoo to speak of in that world, which is desirable, and far ahead yet.
asciilifeform: what can i say, i cannot speak for mircea_popescu , but i have never bought a 'mystery pc' where i have nfi apriori what os to even attempt on it
mircea_popescu: so then don't go at me with "calibers" and other such selg-aggrandizing nonsense, mr alchemist man.
asciilifeform: notion is to do something about this, rather than simple lament, tho.
mircea_popescu: trinque, yes, but how about actually giving this teeth from the get go, in the sense of working out some sort of something that both conserves the gains and opens up gentoo to being raped raw
asciilifeform: (or, charitably, the old chinese 'leather cannon', 50% likelihood of nailing either artilleryman or enemy )
asciilifeform: mircea_popescu: if pc were a small arm, i'd say would be 'zip gun' made from old brass pipe and paperclip, at this pt in time
a111: Logged on 2019-06-22 22:01 mircea_popescu: trinque, if everyone includes ebuilds of everything and in a few years' time everyone's just doing portage because "it's easier, man" ima be very damn sad.
trinque: http://btcbase.org/log/2019-06-22#1919506 << this is understood ☝︎
mircea_popescu: you understand this, yes ? there's no definite utility to computers. for all the promises of grandeur and wunderbarness, a gun's a gun's a gun, and a computer's a smartphone's a tivo.
trinque: asciilifeform: heh, wealth opens up these approaches!!
asciilifeform: and this is when we learned that mircea_popescu dun have a scale in his toilet lol
mircea_popescu: i often take shits i do not know the mass of.
mircea_popescu: asciilifeform, there's nothing to do between a gun and a computer. a gun is a tool. a c omputer is a piece of shit.
asciilifeform: 'i'ma buy 9000 types of shell and try each' ?!
asciilifeform: do you also own e.g. pistols where you dun know the caliber ?
mircea_popescu: trinque, if everyone includes ebuilds of everything and in a few years' time everyone's just doing portage because "it's easier, man" ima be very damn sad. ☟︎
asciilifeform: lol, why, cuz they fell from airplane and not opened the crate yet ?
mircea_popescu: i mitigate this problem by very pointedly only buying certain kinds / classes. ☟︎
mircea_popescu: yes. about half of them.
asciilifeform: mircea_popescu: describe this to me plox.
trinque: implicit in this is no approval of staying still
mircea_popescu: the fundamental problem here is the implicit dwim-ism involved in "i don't have a vax/dec/cuisinart, i have a COMPUTER, as in the abstract"
trinque: that human forms only ever approximate the godly ones, even if always approaching
mircea_popescu: asciilifeform, suppose fellow wants ffa. how does he pick the one he needs ?
mircea_popescu: what'd the distinction be ?
trinque: possibly tangent, but imho there needs to be a distinction between the language of the gods (and the rules thereof) and handbook of suitable places to take a shit.
asciilifeform: so i tell the fella with the vax, 'go and make this its own tree, give it to fellow vaxers to sign, not to me'.
asciilifeform: the problem of 'ifdef' is the clusterfuck where i am given to sign a patch that includes '#ifdef vax' but i dun have a vax. and dun intend to.
mircea_popescu: just the "merely not liking rain doesn't turn off the storm" portion of it.
asciilifeform: rly, we gotta do the ifdef thread again entirely ?
mircea_popescu: both the mips and the x86 ffas pretend to ffa, do they ?
asciilifeform: it aint 'ifdefism' if you dun have two incompatible items which purport to inhabit the same vtree.
mircea_popescu: because it doesn't seem like so much of an idea to me.
mircea_popescu: so THIS is your idea, "ifdefism by hand only" ?
asciilifeform: could argue that this is 'ifdef by hand', i suppose
asciilifeform: when i pull disk out of binder to install os, already pick the 1 where wrote down the type of cpu for which it was, neh
mircea_popescu: don't tell me your idea is "ifdefism only acceptable if done by hand"
asciilifeform: which diverse at the point where you added asmism or whatever it is that marries it to given $irons
mircea_popescu: if tomorrow we have a ffa-for-pc and a ffa-for-mips alternative, there WILL BE AN IFDEF.
asciilifeform: mircea_popescu: yer card runs on closed vendorblob, neh. how would that even make it into a cuntoo-portage or vtree at all.
asciilifeform: mircea_popescu: i described this in the orig ifdefism thread. the solution is to stop pretending that coad worx on boxen where no one in living memory had ever tested it and signed. ☟︎
mircea_popescu: also managed to cut my video card.
asciilifeform: asciilifeform was able to cut several MB from ye olde gnu mpi (which today lives in diana_coman's 'eucrypt') simply by beheading the #ifdef dec_vax... and #ifdef xenix... etc