log
500+ entries in 0.026s
a111: Logged on 2019-06-15 19:14 asciilifeform: aim is a 'mips 4000' compat. item (for ease of hardwarization, when time comes) if anyone cares. and at some pt will also have to port gnat, cuntoo... to it.
asciilifeform: aim is a 'mips 4000' compat. item (for ease of hardwarization, when time comes) if anyone cares. and at some pt will also have to port gnat, cuntoo... to it. ☟︎
asciilifeform: would be a mighty useful thing, tho, 'drop coin in this-here slot and get root on a mips cuntoo'
diana_coman: indeed; I suppose there might be a case for keeping the production server only and then getting the test/cuntoo one only when there is finally what to put on it
diana_coman: to answer the q directly: not permanently, I'd hope! But it does seem to be rather long term since atm I have my hands full with SMG Comms on both client+server and otherwise we don't yet have a full Cuntoo setup to deploy and say that's fixed
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. ☝︎
BingoBoingo: asciilifeform: The dulap spare was yet another monthly, that one strictly billed as a colo, which hanbot played with cuntoo and then the subscription was canceled when that experiment was aborted. The S.NSA spare is cold at present.
asciilifeform: oughta be doable on any linuxism with relatively recent (3+) kernel, iirc. incl. the cuntoo draft.
feedbot: http://blog.mod6.net/2019/05/building-trb-on-cuntoo-part-1/ << mod6's Blog -- Building TRB on Cuntoo: Part 1
asciilifeform: cuntoo, per my current understanding, obsoletes 'rotor' entirely (by doing same thing to ~entire system~ right off the bat)
asciilifeform: mod6: plox to detail ( e.g. if on musltronic cuntoo, why needs 'rotor' system ? it existed only to build musltronic gcc 1st, and ~then~ trb, on heathen envirs , recall )
mod6: Evenin'. I've built trb on cuntoo with ave1's 20180924 tools, with rotor only. Quick test shows pulls connects, pulls blocks.
asciilifeform: http://edgecase.net/articles/offline_installation_of_a_c_compiler_on_centos_69_minimal_on_kalkin << tried 'cuntoo' yet ?
asciilifeform: mp_en_viaje: are you thinking of planting cuntoo ?
billymg: anyways, ty, going to do some shopping for a future cuntoo box
BingoBoingo: Ah, thought this may be Cuntoo related
Mocky: http://btcbase.org/log/2019-05-01#1910435 << using gns as proposed, I don't see any other way than passing out ip based links. I can't send a blog link to a slut on fetlife who doesn't have cuntoo, nor can i send a link to cuntoo guide. The whole thing seems like tree forts connected with tin cans and string. For gossipd I have no objection, for name resolution of published material? How is it even published if 'must be this tall to ☝︎
diana_coman: asciilifeform: that was a proto-cuntoo, essentially not exactly the current cuntoo
asciilifeform: iirc diana_coman built the cuntoo that runs on the 2nd s.mg box, on this gentoo.
asciilifeform: if you want another s.mg-style box, can be baked very quickly. but it does not reduce the amount of sweat needed to install cuntoo at later point.
diana_coman: yes but I struggle to understand why was it that hanbot struggled so much with getting a cuntoo first since apparently there is actually this image that is frozen and usable
asciilifeform: there is not however a mechanism for 'convert from stone age gentoo to cuntoo w/out nuking disk', afaik .
diana_coman: asciilifeform: re dulap-tarball, does that mean that it's in fact *that* the gentoo image hanbot was looking for as stepping stone towards cuntoo? i.e. deploy that first and then from there move on to cuntoo?
asciilifeform: that'd be cuntoo, as i understand. sorta whole pt.
asciilifeform: ( and gotta be replaced with cuntoo )
asciilifeform: http://btcbase.org/log/2019-05-02#1910633 << there's actually not 1 but 2 'standard os' available in piz ( 'rk' and 'dulap' tarballs ) but both are stone age gentoos, they are obsoleted by cuntoo (when the latter is pronounced baked, but really even nao, it is impossible to e.g. 'emerge' packages on the vintage gentoo, the upstream package repos went full tard year ago ) ☝︎
mircea_popescu: it historically worked -- eg trinque birthed cuntoo etc.
BingoBoingo: Have you baked yourself a cuntoo yet?
asciilifeform: BingoBoingo: currently i'm thinking, 2 x dulap-style, 2 x 1u w/ ea. 4 x apu1 'amd g' where cuntoo in write-protected rom . ( i have a rom booter for the latter, built on ancient 'coreboot' )
asciilifeform: iirc BingoBoingo has performed a successful beta-cuntoo installation , for own needs. you may choose to delegate the task to him.
BingoBoingo: diana_coman: Hanbot was also working off of a Cuntoo live image without any persistence. You may have better outcomes starting from an installed system software where changes you make persist.
asciilifeform: afaik 100% of hanbot's problem was in the experimental (cuntoo) soft
a111: Logged on 2019-05-01 08:59 diana_coman: BingoBoingo, asciilifeform I'm looking for a machine to use as experimentation-ground for all sorts of republican software (e.g. cuntoo, logbot); my rockchip fine as it is at doing its blog-hosting job, turns out to be essentially the wrong architecture for this sort of use so I need something else; what can Pizarro offer (even in medium term, it's not something burning)?
diana_coman: BingoBoingo, asciilifeform I'm looking for a machine to use as experimentation-ground for all sorts of republican software (e.g. cuntoo, logbot); my rockchip fine as it is at doing its blog-hosting job, turns out to be essentially the wrong architecture for this sort of use so I need something else; what can Pizarro offer (even in medium term, it's not something burning)? ☟︎
a111: Logged on 2019-03-09 00:51 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-04-25 15:09 asciilifeform: e.g. an auto-installable cuntoo that runs on commonplace irons and includes working gnat, vtron, etc. would save massive amount of work, vs. current situation where 'oh you bought a new box? here's a buncha toothpicks and glue'
a111: Logged on 2019-04-25 10:19 mircea_popescu: http://btcbase.org/log/2019-04-24#1909943 << so far, "cuntoo" is the name we use for the republican os. this item will exist ; the question reduces to "how much work should i put into the framewire model of the future house". by this or some other name, all work we will ever put into tmsr os will go into wjat would currently be called "cuntoo"
bvt: http://btcbase.org/log/2019-04-25#1909969 << that clarifies the issue, thanks. i got momentarily confused because imho cuntoo (as gentoo repo snapshot) is too large to pull off http://btcbase.org/log/2019-04-24#1909621 - i see no way to replace gcc with tcc and 'rebuild world' without rewriting ebuilds/getting a ton of errors; but should be realistic with something smaller (which i plan to do). ☝︎☝︎
asciilifeform: ( consider, for instance, how hanbot's cuntoo experiment ended )
asciilifeform: e.g. an auto-installable cuntoo that runs on commonplace irons and includes working gnat, vtron, etc. would save massive amount of work, vs. current situation where 'oh you bought a new box? here's a buncha toothpicks and glue' ☟︎
a111: Logged on 2019-04-24 20:47 bvt: http://btcbase.org/log/2019-04-23#1909552 << i grok this. the question is, how much work should go into cuntoo?
mircea_popescu: http://btcbase.org/log/2019-04-24#1909943 << so far, "cuntoo" is the name we use for the republican os. this item will exist ; the question reduces to "how much work should i put into the framewire model of the future house". by this or some other name, all work we will ever put into tmsr os will go into wjat would currently be called "cuntoo" ☝︎☟︎
bvt: http://btcbase.org/log/2019-04-24#1909614 << i can do some experiments with tcc-based linux; this may be a too big chunk if i start with cuntoo, but should be possible with some very minimal linux. ☝︎
bvt: http://btcbase.org/log/2019-04-23#1909552 << i grok this. the question is, how much work should go into cuntoo? ☝︎☟︎
a111: Logged on 2019-04-23 19:44 bvt: http://btcbase.org/log/2019-04-23#1909396 << do you mean going [preinstalled gcc6] -> tcc -> gcc2.95 -> gcc4.7 -> gcc4.9 for cuntoo? or drop gcc entirely, try to get as much as possible running on tcc?
a111: Logged on 2019-04-23 20:01 bvt: PeterL: binary ave1gnat is already hosted by asciilifeform; but it's integration into cuntoo is an open problem that ave1 should be best equipped to handle
a111: Logged on 2019-04-23 19:44 bvt: http://btcbase.org/log/2019-04-23#1909396 << do you mean going [preinstalled gcc6] -> tcc -> gcc2.95 -> gcc4.7 -> gcc4.9 for cuntoo? or drop gcc entirely, try to get as much as possible running on tcc?
bvt: PeterL: binary ave1gnat is already hosted by asciilifeform; but it's integration into cuntoo is an open problem that ave1 should be best equipped to handle ☝︎☟︎
bvt: http://btcbase.org/log/2019-04-23#1909396 << do you mean going [preinstalled gcc6] -> tcc -> gcc2.95 -> gcc4.7 -> gcc4.9 for cuntoo? or drop gcc entirely, try to get as much as possible running on tcc? ☝︎☟︎☟︎
spyked: meanwhile, asciilifeform's lappie arrived last week, I'ma encuntooate it soon. I expect it'll be a bit of a challenge to compile on 1GB of RAM: cuntoo bootstrapping sadly requires building gcc-5, which iirc asks for more than that. either way, I'ma put this on the list as the next item to document.
mod6: Did build keccak vtools on cuntoo, whole ffa tree verifies there. pressed just through chapter 1, did a gprbuild on that first chapter, no errors, works great.
mod6: http://btcbase.org/log/2019-04-16#1908650 << Hi there! A brief synopsis of what I've been working on with my limited time over the last couple of weeks here; Read-up about ave1's GNAT, built it, deployed to cuntoo successfully, a blog post is forthcoming as a bit of a summary of what I did there. ☝︎
BingoBoingo: Well, they tend to build on each other. The Linux (dubbed Cuntoo) is to escape all of the distributions constantly changing the base and tools.
BingoBoingo: In other updates, cuntoo takes less than 12 hours to compile on new rig. Gotta fuck the kernel config and details to get it to boot.
lobbes: http://btcbase.org/log/2019-03-10#1901346 << I can also confirm: I made this change, mounted my cuntoo usb to the build directory and reran ./scripts/make_portage_tree.sh. Sig verified on the resulting genesis ☝︎
a111: Logged on 2019-03-20 01:38 hanbot: btw trinque anything grab you re the patchlessness/lack of portage dir in http://thewhet.net/2019/03/hanbots-cuntoo-bake-test-notes-part-iv/ ?
a111: Logged on 2019-02-03 17:20 mircea_popescu: hanbot pick a laptop, bake the man's cuntoo. (principal issue, that gentoo->cuntoo "bridge", see if his sig matches).
BingoBoingo: And no, I have no recieved my Cuntoo test subject yet. Seller promised a tracking number tomorrow morning, El Código de Comercio was a good purchase.
mircea_popescu: hanbot confirmed. http://thewhet.net/2019/03/hanbots-cuntoo-bake-test-notes-part-iv/comment-page-1/#comment-55201 was "No it <a href=.' target='_blank'>http://btcbase.org/log/2019-03-20#1903776>didn't</a>." ☝︎
hanbot: btw trinque anything grab you re the patchlessness/lack of portage dir in http://thewhet.net/2019/03/hanbots-cuntoo-bake-test-notes-part-iv/ ? ☟︎
mod6: I've been working, in the recent few days since "irc-server!!1", on just shaving the yak of my cuntoo-kernel.
BingoBoingo: asciilifeform: Cool. Once the test subject gets here I'll start working on learning Cuntoo through practice.
BingoBoingo: <asciilifeform> i cannot speak for others, but from my pov cuntoo is a wartime t34 , and defo not something i like to picture myself using 20y from nao << Someone's probably sealing Cuntoo'd devices in cement within 5 years
asciilifeform: i cannot speak for others, but from my pov cuntoo is a wartime t34 , and defo not something i like to picture myself using 20y from nao
bvt: well, the question is then, whether we want to do this for cuntoo -- this work will need some resources dedicated to it.
feedbot: http://thewhet.net/2019/03/hanbots-cuntoo-bake-test-notes-part-iv/ << The Whet -- hanbot's Cuntoo Bake Test Notes - Part IV
a111: Logged on 2019-03-13 21:29 PeterL: trinque: so I am running the cuntoo build script, it seems to have stopped doing anything, the end of the build log http://p.bvulpes.com/pastes/whbcf/?raw=true , not sure what to do next here?
PeterL: trinque: so I am running the cuntoo build script, it seems to have stopped doing anything, the end of the build log http://p.bvulpes.com/pastes/whbcf/?raw=true , not sure what to do next here? ☟︎
PeterL: trinque: I am looking at building Cuntoo. Quick question: would there be anything detrimental to having MAKEOPTS set too high? (I see it is set to -j8 at one point in the script, but I only have 2 processors?)
trinque: /cuntoo/portage/profiles/root/cuntoo << and you built this in /root/cuntoo eh?
bvt: ls -R /cuntoo http://wotpaste.cascadianhacker.com/pastes/hHbuq/?raw=true find /cuntoo http://wotpaste.cascadianhacker.com/pastes/gAtS2/?raw=true
bvt: as i mentioned, currently i can show results only from live cuntoo
mod6: I also have tar'd up the entire cuntoo build directory, but have not posted it. It's like 1.7G, but will send it somewhere if someone wants it.
mod6: I have also posted the entire typescript (47Mb WARNING) of the build to my website: http://www.mod6.net/cuntoo-blog-2/nomods.cuntoo.build.typescript
trinque: anyhow, bvt, can I get you to paste an ls -R starting from build/cuntoo ?
mod6: trinque: aha. yeah, powered down, plugged my gentoo SSD back in, and am booted into gentoo where i've built cuntoo.
mod6: I've looked at the genesis.vpatch that was genereated ( http://www.mod6.net/cuntoo-blog-2/nomods.genesis.vpatch ), and at first glance I don't see these files in their paths. (even if I remove the preceeding 'a/').
mod6: trinque: Ok, immediately I notice that in my /home/mod6/cuntoo/nomods/cuntoo working directory, from which I ran `./bootstrap.sh -k config/cuntoo-test1 -d /dev/sdb` there is currently nothing in the 'build' directory.
diana_coman: trinque, bvt put clearly what I was trying to say: here I have the same: the full directory structure inside /cuntoo/portage/profiles
bvt: i.e. there is really directory structure /cuntoo/portage/profiles/root/cuntoo/build/...
bvt: i confirm that it is both in genesis and is a valid path. i'm testing live cuntoo though, have no access to bootstrap env currently
bvt: something like i.e. /cuntoo/portage/profiles/root/cuntoo/build/usr/portage/profiles/features/musl/use.mask
bvt: trinque: i also confirm that under /cuntoo/portage/profiles there is a directory structure that corresponds to my bootstrap environment
trinque: diana_coman: there oughta be a cuntoo/portage dir inside the build dir
mod6: Ok, I'm gonna shutdown the cuntoo box, and boot my original gentoo ssd (where I built cuntoo from). I'll see what I can find out from the genesis.vpatch thing.
diana_coman: mircea_popescu, this is a different machine, the cuntoo-guinea pig
a111: Logged on 2019-03-09 22:43 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
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 ☟︎
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.
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, ☝︎☟︎
mod6: hanbot: I did see these questions pop up too while doing the cuntoo bootstrap. This in particular happened to me after I copied my working gentoo kernel from /usr/src/linux/.config to cuntoo/myCopiedConfig, then replaced all of the =m with =y ( sed -i 's/=m/=y/' myCopiedConfig).
lobbes_field: Fwiw, the same happened to me with all my cuntoo runs that used my own 'custom' kernel config (versus trinque's provided config).
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: 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
hanbot: woke up to my latest cuntoo boostrap.sh tryout to find it hanging on this input request: "Gentoo Linux support (GENTOO_LINUX) [Y/n/?] (NEW)", this after "Restart config...". I take it this is some sorta flag, but what am i yes/no-ing here? what kinda question is that?!
feedbot: http://thewhet.net/2019/03/hanbots-cuntoo-bake-test-notes-part-iii-with-prep-script/ << The Whet -- hanbot's Cuntoo Bake Test Notes - Part III, with Prep Script
BingoBoingo: hanbot: Do you anticipate needing a reset on your cuntoo box soon?
a111: Logged on 2019-02-07 16:49 asciilifeform: in other cuntooisms : if anyone is short a x64 box to test-fire cuntoo with, asciilifeform has a surplus disposable box, 'lenovo s10-3' , with that same chipset as in x60 etc period ( https://archive.is/Dny84 ) , if anyone in l1 wants, it's yours for the cost of postage ( has a mechanical hdd in it, i fughet of what size )
spyked: asciilifeform, is http://btcbase.org/log/2019-02-07#1893396 still available? I'm looking for a small machine to (ab)use for cuntoo install and IMHO this is a good alternative to scavenging the local junkyards for usable hw. ☝︎
hanbot: trinque, /sys fails with "/usr/gnat/vtoolsp1/vtools/cuntoo/build/sys: target is busy." lsof doesn't match anything tho.