log
500+ entries in 0.028s
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.
trinque: in related news, I have trashed my cuntoo build drive with repeated builds!
trinque: also congrats on your cuntoo boot
hanbot: continuing my mounting woes, i can't unmount sdb3 partition on target drive from initial cuntoo bootstrap.sh (target is busy); offending process from 'lsof | grep sdb3' looks like /proc/4693/exe ("txt, unknown"), no response from kill -9, no idea how it zombied out or why, what am i gonna do?
lobbes_field: To update: Now that I have a bootable Cuntoo, a hand-rolled Gentoo, and a proper keccak v setup (with ave1-gnat), the only item left in my 'remedial' hopper is to read and sign Spyked's keccak regrind of logbot_command_router_python >> http://blog.lobbesblog.com/2019/01/hopper-update-january-2019/
hanbot: so check this out: on new attempt to run cuntoo bootstrap.sh, i get this error: "umount: invalid option -- 'R'". whereas man umount shows no uppercase R option (lowercase r makes sense, remount read-only). and moreover, first bootstrap.sh run moved past this no prob, not like the script *changed*, wth?
feedbot: http://blog.mod6.net/2019/03/a-cuntoo-adventure-part-two/ << mod6's Blog -- A Cuntoo Adventure Part Two
mod6 booted Cuntoo
BingoBoingo: <hanbot> re my cuntoo-in': i ran bootstrap.sh, got trinque's smileyface, but then "cp: cannot stat '../config/4.9.94-apu2': No such file or directory". i'm having moar surgery tomorrow, but i'll dig into this again friday. << Let me know if you need brought back online then. I can't imagine hippos work weekends, if their build is still going on by then.
hanbot: re my cuntoo-in': i ran bootstrap.sh, got trinque's smileyface, but then "cp: cannot stat '../config/4.9.94-apu2': No such file or directory". i'm having moar surgery tomorrow, but i'll dig into this again friday.
feedbot: http://blog.lobbesblog.com/2019/02/a-bridge-to-cuntoo-for-the-lenovo-x61-x86_64/ << lobbesblog -- A bridge to Cuntoo: for the Lenovo x61 (x86_64)
asciilifeform: mircea_popescu: fg dun exactly require cuntoo tho. runs a++ with, e.g., my msdos box. ( via 'max232' ttl to rs232 transformer )
lobbes: However, I'm pleased to say I now have a bootable (and, this time, login-able!) cuntoo on my usb stick. I'll aim to get a post with all the details out this week
feedbot: http://thewhet.net/2019/02/hanbots-cuntoo-bake-test-notes-part-ii/ << The Whet -- hanbot's Cuntoo Bake Test Notes - Part II
mircea_popescu: i suspect the whole heathen->cuntoo environment building will require some more brush-up and tweaking. eventually we'll get it smooth but for now such attempts are indeed very useful globally, even if i imagine locally frustrating.
lobbes: However, I've got some detective work to do now; Last night I ran the Cuntoo script (using the same kernel used for the above functioning Gentoo, and aimed at a usb drive), however when building the kernel I saw a spew of "error: cannot read XYZ elf file" and then it drops me out of the bootstrap.sh
lobbes: good day, #t. Quick update on what I've been doing lately: I've been on a bridge-to-cuntoo quest. Firstly, I spent the last week or so successfully getting a hand-rolled classic Gentoo installed on my lappy; complete with alf's classic crapolade masks, functioning networking, gcc-musl, ave1's gnat, and diana_coman's v setup (tested and working splendidly, I will add).
hanbot: right right, i mixed 'em up. and yeah, i'm planning on grabbing phf's keccak v.py in step 3, if only because i've seen diana_coman's pop up in cuntoo tests so i'd like to test the ver less traveled.
feedbot: http://bvt-trace.net/2019/02/cuntoo-installation-report/ << bvt's backtrace -- Cuntoo Installation Report
a111: Logged on 2019-02-17 14:14 bvt: trinque: genesis (does not verify) from successful cuntoo deployment: http://bvt-trace.net/src/genesis-14.02.2019.vpatch
a111: Logged on 2019-01-15 15:32 asciilifeform: it is also time to speak of the next crate. and the customary four cargo slots. 1 is to contain a replacement for uy1 ( and ideally will run cuntoo . ) 1 will contain a 1u that holds rk's. this gives 2 1u slots remaining, they can be occupied by colo passengers, if these stand up and wish to ride , or pizarro irons, at BingoBoingo's option.
asciilifeform: mircea_popescu: fix of sjlj on arm64 is actually moar urgent than arm-cuntoo, cuz sanely build ( static-musl ) ~will~ run on glibcistic linux
asciilifeform: diana_coman: the caveat is that i still dunhave a working cuntoo for all asciilifeform-operated irons; e.g. rk is still running barbaric old glibc gentoo
mircea_popescu: diana_coman looks like it's going the way of cuntoo-ada-musl, no glibc.
asciilifeform: mircea_popescu: cuntoo is arguably a realtime test lab for 'what does removing glibc from ~errything~ cost'
bvt: trinque: genesis (does not verify) from successful cuntoo deployment: http://bvt-trace.net/src/genesis-14.02.2019.vpatch ☟︎
bvt: static version should be fine. then would also try it on cuntoo (have it running, the genesis signature still does not match).
mircea_popescu: well, if you don't have experience with it or anything, it's not urgent -- can continue with cuntoo, can switch to this, either way.
ave1: I was working on getting a cuntoo up (which is going slow, I need to relearn to build a kernel, this used to be a lot easier 20 years ago)
mircea_popescu: nevertheless, the point has legs -- what we've done here very much can be done ands re-done, and with cuntoo/ada-gnat/etc stack spitting out statics, it might even come close.
phf: i've been looking at getting x11 working for cp101a but not on top of cuntoo. i'm going to take a break and attempt a build myself. i might run into the issue also
mod6: http://www.mod6.net/cuntoo-blog-1/trb-test1-kernel-config << asciilifeform my trb-test1 kernel config
trinque: mod6: a/profiles/home/mod6/cuntoo/cuntoo/build/usr/portage/profiles/releases/17.0/package.use.mask << this for example is not a valid path for anything
mod6: trinque: http://www.mod6.net/cuntoo-blog-1/genesis.vpatch
trinque: http://trinque.org/2018/11/27/cuntoo-bootstrapper/#comment-52 << latest sig
mod6: you know, at one point i did actually handroll an initramfs on cuntoo, at which point I updated the /etc/lilo.conf and when I booted, and it panic'd, it did drop me into a shell.
trinque: I very much want you on an actual cuntoo because one of the immediate needs is a trb ebuild.
mod6: Ok, even if its not. I'm just saying I'd never expect anyone to follow the initramfs thing or any other thing. You know way more about what is kosher in gentoo/cuntoo than I do.
mod6: I don't quite see it that way, I'm just trying to do Foundation work, that does overlap with the Cuntoo work.
trinque: so your goal is to have a computer for mod6 on the back of my work, and if it incidentally helps get the cuntoo thing done, w/e
trinque: I highly encourage you to not accidentally haul in an artifact of "user can't be expected to" into cuntoo
a111: Logged on 2019-02-14 01:42 mod6: So I went to build one, but that was barfing on me. Which lead me to find this kernel option 'CONFIG_FIRMWARE_IN_KERNEL=y'. Which would help me complete the build of the initramfs. http://www.mod6.net/cuntoo-blog-1/genkern/genkern.jpg
mod6: Might take a bit, but I'll begin work on that tomorrow-ish. Should have something to look at hopefully by Friday evening-ish. I'll inflate an entirely fresh cuntoo.
mod6: so, `dd` the entire cuntoo ssd disk onto a usb, then attempt to boot the USB, and then do the lsmod diff between the USB cuntoo and the SSD cuntoo?
mod6: So next mission is to use a clean USB drive, and inflate cuntoo onto that, and then try?
mod6: asciilifeform: everything comes with trinque's cuntoo afaik