451500+ entries in 0.287s
decimation: might need
to start at
that level I guess.
decimation: even
the severable bits
that bitcoind really needs?
trinque: munches a queue of
that-which-must-be-done with 1-n workers
trinque: decimation: sounds kinda like what I understand nginx
to be
decimation: well, until
the book is printed, studied, underped
decimation: well, it seems
to me
that
there ought
to be a definable spec between "talk
to peers" and "maintain database of blocks"
mod6: asciilifeform: mine looks exactly
the same.
mod6: what does
tr look like?
decimation: or
there's a dysfunctional router somewhere
mod6: nice. you
think it's being packeted
though?
trinque: this I
think has something
to do with
the political problems
throughout
time
trinque: ok portland, you win
this round
trinque: ben_vulpes: y'know no sooner do I even consider relocating
to
the land of capitalism and Portland's like "but dude! an army of
titties on bikes!"
☟︎ ben_vulpes: sleep? when all
these
titties are biking by?
mod6: get some rest.
tomorrow we can keep on.
mod6: I can work on
that and see where I can get with it;
then I have
to start working on
the SoBA for June.
mod6: asciilifeform:
thanks a lot for your work
tonight on
the Static Builder. I'm a bit zapped
to start getting into
that
tonight. Is it cool with you if I start
testing it out
tomorrow morning?
mod6: I remember from
the block 168`001 issue (tx verification failed)
that it would start dumping
tons of errors if
truly stuck.
mod6: hmm. give it 10 minutes
to be sure... unless it's
taking on
those weird errors
trinque: there are
things
to like about
this communist land
trinque lawls at
the naked folks biking past him
mod6: yeah,
they were pretty blown away when I just came and
told 'em i was gonna scrap it.
decimation: mod6: mechanics are famous for exploiting folks in what
they
think are vulnerable situations
mod6: oh, forgot
to mention.
the place wanted $500
to replace
the springs. which is what prompted me
to `mv posCar /dev/scrap`
mircea_popescu: if nothing else
then because "don't fuck with shit
that works"
mircea_popescu: anyway, ima keep it locked
to your ip
till
tomorro
then
mod6: you got connected
to mp's blockchain milk? or -connect worked for you?
mod6: so now I've got
this company
to pay $185 and
take it off my hands for scrap. hahah
mircea_popescu: asciilifeform anyway, ok if i move back
to public access for
this ?
mod6: only
to find out
that both front springs are broken (lol) and
that's what caused
the
tire
to blow out.
assbot: Logged on 28-06-2015 02:47:49; asciilifeform: (though i'd like
to shoot
that 'gconv-modules.cache' and 'locale-archive' crud in
the head...)
mod6: my pos car got a flat
today, so I limped it up
to
the station
to get a new
tire & walked
the ~3 miles back.
mod6: If you stripped out all of
the DNS stuff and
then did a build with gcc/glibc I'm
thinking
that would get us where we want
to be; sounds like you've done
that!
mod6: <+asciilifeform> now what i can't remember is whether mod6 already had
this orchestra working <+asciilifeform> (with glibc+static) << v0.5.3.1-RELEASE basically is not
true "static" build because of
the gethostbyname() (DNS/libnss) calls in
there. but was
trying
to build static bitcoind with uclibc/gcc on gentoo, was hitting a problem described here before. If you stripped out all of
the DNS stuff and
then did a build with gcc/glibc I'm
thinkin
mod6: wow, just getting caught up here. have been afk for a while here
today...
mircea_popescu: asciilifeform
tell you what, if you don't get
to
the bottom of it, ima make you an account on
the server
tomorrow, copy over
the blockchain and you can compile your own or w/e.
trinque: and even ufw runs afoul of
the "natural language" == easy
trinque: the ufw
thing at least gives you a semi-sane "ufw allow from 1.2.3.4
to any port 8333"
trinque: pf is marginally better, but
that's about it
trinque: firewall configuration should be a function you write
that
the network stack runs on every packet
trinque: beatings for everyone
that decides
to introduce his own grammar
to describe some problem space (firewalls one of many examples)
decimation: I kinda get
the impression
that about 99% of iptables implementations out
there are 'cut n paste' from what someone else posted on some website
decimation: iptables, like most of
the kernel, is undocumented as fuck
mircea_popescu: because everyone
trying
to get in is now stuck on LAST ACK
mircea_popescu: honestly, i don't
think
that iptables
thing actually works.
trinque: seems
to be
the mechanism by which you call a bunch of asynchronous happenings one "thing", and can
therefore act upon
those "things" all being available
mircea_popescu: asciilifeform
they must have if
they were moving bytes neh
trinque: strikes me as "promises"
to indicate
the braindamaged programming environments I've sued
trinque: asciilifeform: am I in
the ballpark... having
the vague notion
that c-gates would be used
to indicate whether
the inputs necessary
to perform a computation are available?
trinque: mircea_popescu: because layering another
turd atop iptables is surely what you want... I find ufw a nice
tool
to deal with
trivial firewall setups
mircea_popescu: iptables -I INPUT -p
tcp ! -s <permittedIP> -j DROP << is
that it ?
ben_vulpes: are
they also /programatically/ nested?
ben_vulpes: why are
these critical sections lexically nested?
mircea_popescu: fully expecting he will have
to install vanrish, uninstall alsa, recompile
the kernel and fix glibc.
mircea_popescu goes
to read
the manual for iptables now,
to find how you do "open port only for x ip"