log☇︎
800+ entries in 0.072s
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
mod6: Ok, so you're saying: Do all of the above steps, but instead of using a SATA SSD, inflate cuntoo onto a USB stick?
mod6: Right, well, cuntoo expands all of those things and build it, you just feed it a config. So if there is something that is "off" about my config with some other slightly different source version, then that might be a part of it.
mod6: certainly possible. seems totally wacky to me that the same kernel config would boot gentoo perfectly, but not cuntoo. note in the wotpaste above that I copied in my /usr/src/linux/.config from gentoo directly and build that config.
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: http://p.bvulpes.com/pastes/BoTML/?raw=true << Ok, so after installing Cuntoo, I did what I said I'd do, which was test editing the append section and throwing a UUID in there instead of 'root=/dev/sda3'. It didn't work, I did get a kern dump.
mod6: http://p.bvulpes.com/pastes/ht6ey/?raw=true << Ok, inflating /dev/sdb with cuntoo. Will report back more tomorrow after install is complete, and I update the lilo.conf via LiveCD chroot mount of cuntoo. Will post lilo.conf changes, and results.
mircea_popescu: trinque is it actually the case that cuntoo can't boot off a non-first drive ? if so easy enough to check.
a111: Logged on 2019-02-11 00:03 mod6: ok, that blog post is now: http://blog.mod6.net/2019/02/a-cuntoo-adventure
lobbes: btw, I managed to finally get a handrolled heathen gentoo installed the other day (my first one ever). Still wrestling with getting networking functional, but once I do I'ma get vtools set up, and then give the cuntoo bootstrap.sh another spin
lobbes: And the utility of reporting applies to oneself too; even though my flailings in http://blog.lobbesblog.com/2019/01/initial-cuntoo-testing/ may not be of use to anyone else, -I- now have a ready history of wtf I was thinking/doing years down the line, from which to diff
lobbes: http://btcbase.org/log/2019-02-10#1894807 << verily. And not even necessarily rocks he hit, but also rocks avoided that less experienced folx may hit (for e.g., I have never debugged a kernel before. Now, when my time to do that comes I know I can check http://blog.mod6.net/2019/02/a-cuntoo-adventure/ to re-read how mod6 did it). ☝︎
mod6: ok, that blog post is now: http://blog.mod6.net/2019/02/a-cuntoo-adventure ☟︎
feedbot: http://blog.mod6.net/?p=42 << mod6's Blog -- A Cuntoo Adventure
mircea_popescu: mod6 no man, the difference ain't that one's topic is ada and the other's topic is cuntoo. the difference is that she said "here's the top level problem, here's the list of possible solutions, here's the failure mode of each, let me know if either the list's missing an item or wtf." ; you said "here's an error message pasted and i've been having problems".
a111: Logged on 2019-02-10 20:14 mod6: So during this adventure, I initially bought a WD 250Gb SATA SSD, upon which I installed cuntoo. Which I never did get to work. Upon initial suspicion that disk might be bad, I bought another 250Gb WD SSD and installed cuntoo on that also. Same error. So I at least removed the variable of "disk is bad".
trinque: I'm certain the cuntoo script is *not done* which is why I'm having folks test it, but I want more out of these tests than "ow, it wasn't a debian installer"
a111: Logged on 2019-02-09 19:55 trinque: btw this means that e.g. what mod6 is experiencing are more likely to be "I need to go understand kernels and lilo better" than "cuntoo is broken"
mod6: But that's what I've got now. 2 250Gb SSDs with Cuntoo on them, neither boot, and now a 500Gb Gentoo disk that has worked perfectly up until just this very moment, which also doesn't boot.
mod6: So during this adventure, I initially bought a WD 250Gb SATA SSD, upon which I installed cuntoo. Which I never did get to work. Upon initial suspicion that disk might be bad, I bought another 250Gb WD SSD and installed cuntoo on that also. Same error. So I at least removed the variable of "disk is bad". ☟︎
mircea_popescu: asciilifeform so what is your idea here, "cuntoo comes with gtk 2 and firefox 40" ?!
trinque: recall the "gentoo" repository is still present on the build, though at lower priority than "cuntoo"
asciilifeform: ah q was re cuntoo per se ?
mircea_popescu: so who says cuntoo is for racked boxes only.
mircea_popescu: trinque i didn't suspect cuntoo was necessarily at fault there, no.
trinque: btw this means that e.g. what mod6 is experiencing are more likely to be "I need to go understand kernels and lilo better" than "cuntoo is broken" ☟︎
mircea_popescu: "this one crash that only happens twice every third saturday when running postgres on cuntoo in x mode with y switch doing z task" is still catastrophic, as these things go.
trinque: of /cuntoo/portage , the ebuild tree
asciilifeform: it gotta be done at any rate, currently asciilifeform is the tortoise in the cuntoo race fulla achileses
asciilifeform: mircea_popescu: i'd like to move ~all~ of asciilifeform-tended irons to cuntoo eventually.
mircea_popescu: speaking of which, hey asciilifeform do we have any plans to move phuctor to cuntoo ?
mircea_popescu: the pointers should point to cuntoo, once it's ready.
a111: Logged on 2019-02-09 18:37 asciilifeform: mircea_popescu: ideally would be 'download trinque's signed iso and boot from it, then install cuntoo'
BingoBoingo: mircea_popescu: Rather than a rk, shinohai cuntoo'd and AMD E-300 (AMD 64) laptop
hanbot: well my failed attempt isn't known to have anything to do with cuntoo, as i didn't touch it yet.
a111: Logged on 2019-02-03 17:19 trinque: diana_coman: might I get a tarball of your cuntoo build directory's present state?
shinohai: mircea_popescu: http://btcinfo.sdf.org/blog/cuntoo-a-linux-that-sucks-less.html <<< I will mention that the USB version won't boot yet, only useful as chroot device.
mod6: i should also mention that shinohai's working cuntoo is a APU box - not intel.
mod6: on the bright side, i thought that my inital new SSD i ordered for cuntoo was just bad in some way, so i went and bought another. so now i have a spare :]
mod6: i've actually been lucky enough to have shinohai's ear this whole time too, who actually has a working cuntoo.
asciilifeform: trinque: what's the obstacle currently in the way of a bootable cuntoo iso ?
mircea_popescu: won't be the end of the world if we manage to actually have a cuntoo in a few months.
asciilifeform: mircea_popescu: ideally would be 'download trinque's signed iso and boot from it, then install cuntoo' ☟︎
mircea_popescu: i'm guessing what we actually want here is to get cuntoo ready already and then just skip this step altogether ; meanwhile sit unprotected
a111: Logged on 2019-02-09 18:02 asciilifeform: BingoBoingo: imho there's not much educational value any moar in setting up ancient gentoo; it's obsoleted by cuntoo, and quite difficult to revv up on acct of the dead mirrors
mod6: right, i agree, so i don't think it's ~cuntoo~ per se... but imagine this. I've had gentoo running on that hardware for nearly a year since i bought it.
asciilifeform: cuntoo afaik is atm silent on the question of what goes in kernel.
asciilifeform: mod6: if yours panics, sounds like kernel (or even iron) problem , rather than cuntoo issue
mod6: fwiw, I've been working on trying to get cuntoo working for 10 days.
asciilifeform: a working cuntoo is the only path fwd for reproducible, reasonably-working unix box.
asciilifeform: i'd prefer to get the rk plant onto a working cuntoo as soon as it becomes practical.
asciilifeform: ( cuntoo was not available when i baked rk , and it was necessary to work around the sad state of the upstream mirrors, hence why bottled it )
asciilifeform: BingoBoingo: there is of course the bottled gentoo i baked for rk; but it is also arguably a technological dead-end, and eventually oughta be replaced with arm cuntoo