342500+ entries in 0.216s
assbot: Logged on 30-01-2016 18:07:37; asciilifeform: but in all seriousness, a battlefield
trb oughta be built on a virginal airgapped box.
mircea_popescu: ben_vulpes i
think
they're going
to
try
the sit around and
talk about it while it goes away or whatever
trick
assbot: Logged on 30-01-2016 18:05:48; asciilifeform: and loading
them from
the jungle every
time, not nervous ?
ben_vulpes: think
they're going
to
try
the sterile males
trick?
assbot: Logged on 30-01-2016 17:51:53; mod6: i do a lot of
testing etc. often if I'm actually going
to change a line of code, i'll press out a seperate branch call it 'foo', go in
there copy a & b,
then make changes in b. make a vpatch. drop it in my live bitcoin branch, rebuild with
the rotor. bunch of stuff.
assbot: White House denies clearance
to
tech researcher with links
to Snowden |
Technology |
The Guardian ... (
http://bit.ly/1PHcyCJ )
phf: asciilifeform: right, it's a state
transition graph, with edges corresponding
to file changes
mod6: also, hehe, i downloaded
this scheme interpreter
to play with on my phone.
mod6: i'd like
to get
this into "battle-ready" shape once and for all.
☟︎ mod6: aside from
the sync/mirrors/init stuff?
mod6: asciilifeform: while i'm on
the subject (and anyone else for
that matter): is
there anything else
that should be excised from
the current V [v99996] ?
assbot: Logged on 30-01-2016 01:42:16; punkman: does
the
trb server have room for a buildatron
that eats patches and craps out bitcoind's?
mod6: actually, it might just elimiate a bunch of
tests.
mod6: i gotta re-write a lot of automated
tests and stuff
too.
mod6: so -- i might need several weeks at min
to
test out v99995 of V
☟︎ mod6: i just haven't focused on
that part as much for obv reasons.
mod6: alright, fwiw, it does work. could use some more colorization and attention
to details like you and Mr. P. have suggested.
mod6: is it worthwhile
to rip out my graphing stuff out of V?
☟︎ mod6: and seems
to work ok... but i'll hvae
to
test
this quite a bit.
mod6: ok, well i did just rip out all
the sync/init/mirrors parts of V
☟︎☟︎ ben_vulpes: phf: is
this mod6's svgerator or your own?
jurov: and i don't have anything
to say about non-nato computers3
jurov: <punkman> asciilifeform:
there are more "server ARM"
things coming out... << you really want like, 64 shitty cores on
the workstation instead of 4x x86?
☟︎ mod6: alright,
thanks, let us know.
mod6: it doens't
take long
to pass
that spot anyway.
TomServo: Negative. Was just going
to ask if
there is any value in keep it..
TomServo: or a nob
to include a local path, else procurement?
ben_vulpes: rather
than including procurement of deps in
the build scripts, force users
to actually download
the deps
themselves.
mod6: not sure i follow
there, what'd be
the
techincal purpose of
that?
ben_vulpes: a small step
to
the disc would be
to slam buildroot, openssl, bdb and boost into a
tar.gz and stick it on
the website.
mod6: i guess v99995 could rip all
that stuff out. certainly would condense
the code a bit.
mod6: <+asciilifeform> why
the hell not ? << because i
tried
to kinda sorta do
this already... buildroot is hardcoded
to download (rsync) all of its deps and stuff it needs from net. we'd have
to "hack" our own buildroot.
jurov: but
to hardwire it in
the build process and C library?
jurov: "the Emacs unexec() function
that converts
the running program into a new executable."
mod6: maybe in 6 months
to a year,
then we'll be in a spot where it's in a more hardened form.
takes some
time, and people using it
to flush some of
the shit out.
mod6: and
that's basically because it's not "ready" per-se.
mod6: someone asked me why I don't create vpatches of
the changes
to V.
mod6: we're
totally not going
to do
that btw.
mod6: ben_vulpes: heheh. its more like: here's
the source code, see what you can do with
this. unless .1,
then you can have CD and volla!
mod6: ok, we can revisit
this next week.
ben_vulpes: we should really do a bsd, and sell
the discs for a bitdime each.
mod6: the whole
thing maybe lol.
mod6: yeah...
there's a handful. i dunno, makes me nervous.
mod6: not only with
the makefiles, but are we actually
thinking about distributing all
the deps ON CD?
mod6: <+asciilifeform> in fact i
think it ought
to be abolished and replaced with pressed silver cd. << im not sure how
to build
this excatly.
this is part of what we wanna
talk about next week.
mod6: i use
the built
thing
to
test my code changes and other config changes.
mod6: but, i
typically don't hack straight on
the built
trb, ususally on a separate branch.
mod6: i just re-read what I
typed
there (sorry, just woke up, slept like
the dead), and i don't mean
to make it sound like a single line, even if sometimes it is! i just make
the changes i need,
the most minimal changes possible,
then drop 'em in and see.
ben_vulpes: (reminds me a bit of
the "check every return code" naggum line)
mod6: i do a lot of
testing etc. often if I'm actually going
to change a line of code, i'll press out a seperate branch call it 'foo', go in
there copy a & b,
then make changes in b. make a vpatch. drop it in my live bitcoin branch, rebuild with
the rotor. bunch of stuff.
☟︎ mod6: <+ben_vulpes> mod6 and
trinque as well << hacking
the codebase? << I just build
the statically linked bin with rotor via
the build-bitcoind script
that everyone uses.
mod6: i'll have
to check it out.
thanks for letting me know.
mircea_popescu: if what you mean is
that large buyers get volume discounts, well doh ?
mircea_popescu: your cut should be more or less
the coupla mil, minus cab fare.
mircea_popescu: at any rate,
the plan's very simple, go
to large nat'l retailer, load half a dozen disks, when
the cashier refuses
to sell
them sucker punch him, get
the police report
to say he wouldn't sell you
the drives, pay
the whatever it is
to have punched a dude and settle for whatever coupla mil
they're willing
to pay
to avoid discovery.
mircea_popescu: i don't live
there nor have i yet run into
the problem.