billymg: signpost: i tried out your pentacle thing, with it i was able to chroot in and build the vtools binaries. this time all of them built as static binaries, without me even needing to modify the orginal gpr files to add static flags
billymg: so now i have a working vtron on the host box
billymg: however, when not chroot'd in, but only with the path to pentacle's gnat added to my PATH (so that e.g. `which gnatmake` works in the host env), i received some errors when trying to build the vtools binaries
billymg: signpost: btw, did not use this, but rather mounted my primary drive inside the chroot, navigated to the files, and built with the standard e.g. `make vdiff`
dulapbot: Logged on 2021-09-03 15:03:09 signpost: to get a vtools in there, enter the `target` chroot after your build, and... `cd /src; ./layer install vtools`
billymg: not because i didn't want to but just because i forgot it was there until reading your notes on it again now
billymg: signpost: overall really cool, and i'm happy now that i finally have a vtron on this box
cgra: billymg: bitdash.io seems to somehow figure out what peers a node is connected to: like here, section "connected peers". how do you do it? or does it mean smth else?
cgra: so "connected nodes" here is more like "peers the node knows of"?
billymg: cgra: hrm, technically you might be right, i had always assumed before that meant the node was also connected to those peers
cgra: i might've overlooked something in trb code, last q now pending
billymg: or at least recently connected (though this would also mean it's a misnomer to refer to them as 'connected peers' as that implies currently connected)
billymg: cgra: i'm personally not familiar with the trb code at all, so quite possible it was a mistake in labeling on my part
billymg: !w peers 205.134.172.26
watchglass: 205.134.172.26:8333 : reported peers: 54.95.111.227 60.48.190.216 71.224.191.142 76.103.7.22 79.186.94.254 88.80.145.201 88.99.65.182:8343 96.225.66.73 125.120.88.191 152.231.121.118
watchglass: 205.134.172.26:8333 : reported peers: 208.94.240.42
billymg: cgra: ^ essentially that list, though asciilifeform's watchglass has a configurable knob for 'peershots', my crawler has that set to 5, not sure what alf's watchglass is set to
cgra: ah, yeah
cgra: billymg: sorry, i must go afk now. i intend to return tomorrow to finish my q or admit hasty conclusion
billymg: cgra: ttyl
dulapbot: Logged on 2021-09-04 12:19:19 billymg: so now i have a working vtron on the host box
signpost: http://logs.nosuchlabs.com/log/asciilifeform/2021-09-04#1056465 << I would not expect this to work, as gcc makes assumptions about where its components live
dulapbot: Logged on 2021-09-04 12:21:34 billymg: however, when not chroot'd in, but only with the path to pentacle's gnat added to my PATH (so that e.g. `which gnatmake` works in the host env), i received some errors when trying to build the vtools binaries
signpost: likely the errors are from mixing components from your outside env
signpost: http://logs.nosuchlabs.com/log/asciilifeform/2021-09-04#1056466 << you'll find /src/build/vtools does little other than this
dulapbot: Logged on 2021-09-04 12:31:30 billymg: signpost: btw, did not use this, but rather mounted my primary drive inside the chroot, navigated to the files, and built with the standard e.g. `make vdiff`
signpost: but yeah that should also work. idea is the /src tree is there, use it or not (not unlike a ports tree on bsd)
signpost: http://logs.nosuchlabs.com/log/asciilifeform/2021-09-04#1056469 << nice, should be able to carry the static binaries to w/e other boxes you like, too
dulapbot: Logged on 2021-09-04 12:36:06 billymg: signpost: overall really cool, and i'm happy now that i finally have a vtron on this box
jonsykkel: maby another note for ded tree ffa: W_NZeroP in ch4 vas alredy covred in ch2
jonsykkel: i guess its meant to be FZ_NZeroP
raw_avocado: Yo guys i finaly made a RNG
raw_avocado: Its a dumb man version, it has some biases, and i dont have enough data to do all the tests i want, but worx