508800+ entries in 0.318s
danielpbarron: the shortcoming is it's using ArchLinux, doesn't boot from eeprom, requires a great deal of user setup
to get working
mircea_popescu: i haven't seen asciiart
technical drawings in documents since
the 90s.
nubbins`: i have pogo x2 on
the way, i'm gonna dig into
this
mircea_popescu: danielpbarron link me
to your last version of "how
to" again plox ?
danielpbarron: i also had one going
that was using a USB3 stick -- stopped it after a week or so when it was clearly way
too slow
mircea_popescu: cool. so
then,
these
things are pretty much ready
to launch are
they ?
ascii_field: mircea_popescu: adding a problem++
to
the list at
the cost of a weekend is not on
this list << astute observation, which is why my patch was specifically labeled as a proof
to nail down
the locus of
the problem, and not an item
to be used on
the battlefield.
mircea_popescu: ascii_field
the way system engineering is done, is either do not fix a problem, or else fix
the problem. adding a problem++
to
the list at
the cost of a weekend is not on
this list.
mod6: yeah, im
talking about an all encompassing approach .. many small steps,
the former.
ascii_field: mod6, mircea_popescu: depending on what it means
to fix
the leak (total replacement for block sync mechanism and a mathematical proof for it? or something more like my patch ?) it could
take anywhere from a weekend
to maxint days
mod6: Yes, Sir. Should have responded lastnight, just got distracted hacking
together my obsd lappy.
mod6: Sorry! I'll get you something
tonight :)
mod6: Our goal is
to get
this resolved, but I
think it seriously is going
to
take some effort. Part of going forward from
this release is going
to be breaking down goals and getting
them lined up. I have high hopes
to discuss much of
this at
the Cnof.
mircea_popescu: yes and he's doing his job
to
the best of his abilities.
ascii_field: gavin or whoever - isn't he a full-time dev for
turdation ?
mircea_popescu: o look at
those kulaks over
there...
THEY have
to do
things right.
ascii_field: mircea_popescu: one of
these
things is not like
the other, i
think
mircea_popescu: or anything else for
that matter, deedbot, cardano, eulora, name it.
mircea_popescu: ascii_field you familiar with how long current foundation patch
took ?
mod6: For me, and I might be wrong here, but fixing
that is a huge chunk of work. I'd have
to break it down
to give a decent estimate. But I'd guess 6 months or more, easy.
ascii_field: anyone who wants an illustration of roughly what has
to be done, is invited
to read my skull&crossbones patch
mircea_popescu: danielpbarron what was
the current block count on
those
things ?
ascii_field: neh just something
that isn't guaranteed
to kark its breeks after 40min
mircea_popescu: apparently ascii_field wants a provably-correct stack of five layers of software before we ship out
ten dollar items.
mircea_popescu: ben_vulpes mod6 what do you
two figure is a realistic
timeline for "bitcoind version
that doesn't allocate memory without checks and so doesn't crash in
THAT particular way" ?
mircea_popescu: <ascii_field> (a passing draft will drop your channel capacity
to nothing ?) << BUT DRM IN AUDIO WORKS!!!
nubbins`: i recall you saying a bare bones install could be impossibly
tiny
ascii_field: but iirc
the device support of openbsd is a subset of netbsd's
danielpbarron: i got your netbsd kernel
to boot on
the pogo;
this is possible with openbsd as well?
ascii_field: i would do it pro bono but haven't
the
time
danielpbarron: i don't mind paying someone
to do it, but i probably can't afford whatever
that kind of work is worth
ascii_field: (no support for
the nand; bizarre bugs in other drivers)
danielpbarron: how hard would it be
to get OpenBSD on a pogo? I've been idling in
their channel but I'm not sure how productive it would be
to just go "hey someone should start supporting
this architecture for my pet project!"
nubbins`: wait,
that conversation was from somewhere else
ascii_field: (a passing draft will drop your channel capacity
to nothing ?)
ascii_field: noise sensitivity makes it hopeless in
the wild
ascii_field: 'The
two systems would
then engage in a handshake, involving a sequence of “thermal pings” of +1C degrees each,
to establish a connection. ' << stopped reading here
ascii_field: the receiver here is
the built-in
thermistor found in most servers
chetty: yeah old
tech, but showing up in more mainstream sorts of pubs is interesting
ascii_field: transmitted a few bytes with small variations in surface
temp
ascii_field: chetty: a certain semiconductor vendor had a heat-based
tattletale mechanism for detecting clones
danielpbarron: nubbins`> it comes with a bobbaing 3-foot cat5! << most do; not all --
the power supply also varies in shape
ascii_field: i meant
that it
trashes state unpredictably
ascii_field: i specifically mean
that a node running bitcoincrashcrashcrash is dangerous
to itself and others.
mircea_popescu: you can't postpone everything until everything else just like you can't have everything louder
than everything else.
ascii_field: mircea_popescu: if you ask me, releasing
the memleak version is lunacy
mircea_popescu: anyway, speaking of
this, what was
the status of
teh pogo project ? we ready
to bake ?
ascii_field: you can't get it without
the extra bells & whistles
nubbins`: ascii_field
that's what i'm wondering :0
mircea_popescu: ascii_field but
the 4gb is only because
they run crud.
ascii_field: and a socket on
the side for another identical unit, for when
the flash fills.
nubbins`: i obv have no idea as
to scale here
ascii_field: it holds
the heatsink in place, and cradles
the hdd
ascii_field: i'll add
that
the case is not merely decorative
nubbins`: so what i'm wondering is what you're looking at for, say, 10k units without all
that fluff
ascii_field: and don't forget
the steel heat sink in
there
mircea_popescu: nubbins`
the plastic casing is at least as valuable as
the boards.
nubbins`: lel. i know, i mean actually having just
the boards produced
ascii_field: nubbins`: probably ~19 usd forever until
they run out
ascii_field: but can be inferred from
the port layout and
the chipset in
the spec sheet.
ascii_field: not revealed in
the phoundation site, of course
nubbins`: ascii_field i
thought it was a raspi between
two sheets of acrylic at first
thestringpuller: just bad feeling seeing summer 2015 as
their schedule and
this aligns with gavin wanting
to have enough dick's sucked
to push his shit into github around
then as well
thestringpuller: ascii_field: snore for now, but if
they start selling,
they lower barrier
to fork.
nubbins`: i.e. 0.5.3.2 should patch just
the same
ascii_field: thestringpuller: if
they were passing
these out for
tenbux each,
then.
nubbins`: mod6 but FWIW
this process should generally be able
to be applied
to future releases as well
nubbins`: mod6 i should stress
that *none* of
the hardening options are included in
that makefile, and it really should not be used for anything other
than reference
ascii_field: doesn't cost any less
than a normal computer
BingoBoingo: asciilifeform: nubbins`: any changes -not- in common with openbsd << For versions earlier
than 5.7 and -current some wallet.cpp code needs changed
to use better random