10900+ entries in 0.019s
mod6: once fully sync'd they both could be masters ; helping avoid star topology.
mod6: then will probably get that setup and colocate it somewhere.
mod6: and I ordered a physical box that has the same 2 procs, but has 64gb of ram as opposed to 24gb. just needs few disks.
mod6: well, yeah, i've got a new dedicated box that is trb w/wires and currently syncing from thin air.
mod6: I hung my new 4'x6' whiteboard next to the battlestation last night. 'tis awesome.
mod6: well, not mad, more like disgusted
mod6: that made me so mad.
mod6: so, let the prototyping begin!
mod6: well, whatever we go with will be a solution driven by performance numbers and functional satisfaction.
mod6: The role was put on hold since I wrote `t', and 'tb0t', but might come back up again at a later date.
mod6: Framedragger: the stenographer role was proposed to be an actual job for the foundation, complete with pay and everything.
mod6: so a very exciting time, as far as I'm concerned.
mod6: <+mircea_popescu> also, we are not at wall : we saw ext4 ; did not see ext2 ; did not see reiserfs. << for sure. i think we're just getting started baselining these prototypes.
mod6: i started working on it very briefly ... maybe 7-10 days in like ... december. but haven't touched it since.
mod6: some sort of PGP based command system.
mod6: so that might help. i might write some sort of API also where project admins can interact with their projects without having to use IRC.
mod6: tb0t eventually will be upgraded to use the new system.
mod6: any ticketing thing is as useful as you make it. it takes effort to remember to keep it up and to ~use~ it. any thing we can do to make that a more automated process though, is nice.
mod6: and we could track things easier instead of having to have it be a formal role. but with the new version, seperate projects can have different users, so for instance, if UCI wants a stenographer, then the project admin can just add the steno to the UCI users table. volla.
mod6: yeah, there was this intial idea of a 'stenographer'.. and I think that's what drove me to just make the ticket system.
mod6: hopefully it'll be at least better than the first version, which is fine for now, but certainly could be better.
mod6: it's meant to be project cutomizeable per project... with like the ticket codes, etc. i'm building out the database now... and it's going well, just slowly.
mod6: there are project admins, and project users... etc. i should add the ability for rich or chained notes.
mod6: there can be public/private projects.
mod6: in the new version it's setup different.
mod6: no, not a list of notes per ticket in the original version.
mod6: <+asciilifeform> to n00bs i often recommend to have an analogue scope also << are these just a bit easer to learn on than their digital counterparts?
mod6: So I'll be getting into the thick of that very soon. Lot to do to get trb-i going.
☟︎ mod6: I dont need a ticket for this, but man, I really gotta get into the swing of Ada.
mod6: So we need some updated tracking to that effort.
mod6: There are some other cool side projects going on now too... such as the wallet-cut effort.
mod6: Would be really nice if we could get away from BDB.
mod6: It's important work.
mod6: Anyway, just as an example of side-projects that need tracking...
mod6: Gotta have a way to go back and check easily, and have a place for that.
mod6: Even if you think that we're at a wall, and we've seen all there is to see.. then we record those numbers. Or if we should try on baremetal with, reiserfs, and record those, or if even with those baselines, then someday we make our own filesystem and compare to those baselines.
mod6: There is some side project stuff too that I'd like to get organized and tickets entered for. For instance, you, Framedragger, did some work towards the filesystem idea. We aught to have a ticket for that and track the results.
mod6: I do want to outline more of the trb-i work in tickets, and do some clean-up/management of existing trb tickets.
mod6: Heh, I'm working on a major update to T, also. It's been a bit slow-going as that isn't obviously the most high priority item.
mod6: Yup, all the wot variant rules are in place. We now orphan vpatches from the flow where ~all~ antecedents are *not* present. Some other small changes, such as; When you press to a give output directory 'X', and then press to the same given output directory, we first remove 'X', then create & press.
mod6: <+Framedragger> anyway not sure how useful but you might want to take a look at
http://thebitcoin.foundation/tickets/ doppler (at *_tickets.html), not sure how up to date. (...) << Yeah, it needs some updating. The new V is going to be out in the next few days. Then will put some time into that.
mod6: Framedragger: thanks for the heads up
mod6: im a total n00b on this stuff, my apologies.
mod6: ahh, ok. i wasn't even totally aware that you needed software along with the tool. i thought that the sample was just fed back to you on the little screen...
mod6: do the tektronix ones only work with winblowz or something?
mod6: haha. i've never used one of these before. but im interested in learning how to use it.
mod6: shinohai: ah hey, no worries.
mod6: mircea_popescu: ah, cool thx :]
mod6: *any reccomendations
mod6: thanks for testing!
mod6: girls look hawt in snowpants.
mod6: it's either your knees or ass.
mod6: pete_dushenski: i never thought of it that way.
mod6: asciilifeform: heeey, thanks chief.
mod6: and pulling blocks from thin air ala genesis.
mod6: <+mircea_popescu> on occasion. yes with teeth. i also pluck their legs and let them die. in general i torture a good half of all mosquitoes. << i like his enthusiasm. im usually content to simply smash them like @ c3. but, hey, i gotta try this.
mod6: <+davout> it did not occur to these monkeys that somehow it might also make sense to ~not~ include a subject line reading "O HAI YOU HAZ X DEPOSIT KTHXBYE" << lol, huuurrrr
mod6: yup, still on target for this weekend.
mod6: There has been an automated test added for this as well.
mod6: Update from yesterday: The necessary change has been made to the forthcoming version of V (99994); if when pressing, the given output directory already exists, it will be removed, then will proceed to press new vtree.
mod6: <+mircea_popescu> mod6 no, JUST /deps/ << ok.
mod6: ok. i think we've got something we can work with. :]
mod6: so either user creates ~/trb-deps and then pulls all .asc's from deedbot manually in offline mode. or makefile creates ~/trb-deps and pulls .asc files in `make ONLINE=1` mode and dumps files in there.
mod6: so yeah, something other than what I did is preferred (at least to me).
mod6: but having it set up as i just did in the above paste is unpressable in current vtronics.
mod6: that's fine. could just reference something like: ../../../deps/*.asc or something
mod6: this would leave, for instance, a 'trb' output press directory along side of the above stated dirs. of which, all that would be contained in there is a bitcoin directory, and the underlying 'src' directory.
mod6: ('bin', 'build', 'deps', being adjacent, meaning, along side of 'patches', '.seals', 'v.pl', etc.)
mod6: so that'll be the next thing to take a look at.
mod6: problem will be with pressing and a vpatch. press wants to put everything underneath of the given press directory. not place contents adjacent to a press directory.
mod6: interestingly, i just tried moving 'bin', 'deps', and 'build' and all of their makefiles + a few small tweaks up ../../.. and was able to build.
mod6: anyway. ya, something to look at.
mod6: the harder part is trying to move 'deps' ..//..
mod6: this change is pretty trivial. probably will update V99994 before it comes out (was about to release this weekend). will need to add at least an automated test too. not a big deal.