480900+ entries in 0.317s
mircea_popescu: polished all
the fucking knobs and hanged scented car
trees and chinatown windchimes from various nubbins is all.
mircea_popescu: three years later,
they have done NOTHING. nothing at all.
mircea_popescu: it's like a std, basically,
they get it around puberty
through apparent spontaneous generation.
mircea_popescu: every fucktarded girl i ever met growing up,
the sort
that never got anywhere either in
the bed or in
the forum,
their entire lives, and ended up settling down with an alcoholic bum, each and every one had, without exception,
the same answer
to any instance where
they had fucked up :
assbot: Logged on 06-05-2015 14:19:10; asciilifeform:
the imbeciles are phucked and
their only recourse, as is now
traditional, is
to fud and lawyering
assbot: Logged on 06-05-2015 14:10:21; asciilifeform:
takes some effort
to read
this correctly.
mircea_popescu: asciilifeform apparently
they're at 3s. longsoon
that is. ah, best laid out plans...
mircea_popescu: cheap and effectual
testing of critical stuff like
this.
ben_vulpes: asciilifeform: what does "in lockstep" mean when you
talk about running bitcoind and any potential replacements "in lockstep"?
ben_vulpes: | | | | ->08.68% (67,108,864B) 0x470070:
ThreadGetMyExternalIP(void*) (net.cpp:379) <<
that
this is a
thing cracks me up
☟︎ pete_dushenski: unkosher ostriches with
their heads in
the sand,
these guys.
ben_vulpes: davout:
there are buildroot scripts for
the cross-compile on
the mailing list
pete_dushenski: williamdunne: kakobrekla any guess why assbot isn't picking up new post
titles off of scoopbot_revived ??
assbot: Logged on 06-05-2015 05:09:26; BingoBoingo:
The fucking welterweight champion is known more for "defense"
than leaving welts?
davout: ok, i'm off for now, i'll get on cross-compiling bitcoind and getting it running on
the pogo later
danielpbarron: the abiltity
to audit
the
thing is one of
the most important features
davout: i guess it really depends on whether we want
to ship pre-configured units, or make an easy procedure available
danielpbarron: but you should be able
to ssh into a new unit, download
the image and flash it
danielpbarron: although
that might also be handy for making lots in one pass
davout: ah, so ultimately
the procedure would be "acquire pogo, burn image on USB stick, insert SATA drive, insert flashed USB stick, power unit on" right?
danielpbarron: i'm not sure if it can boot from sata out of
the box; it's uBoot should be able
to do it, but i don't know if it would need
to be reconfigured
danielpbarron: and you can boot from usb, it just has
to be
the USB2 port on
the
top of
the unit
danielpbarron: pre-configured
to look for a sata drive
to format and mount as
the datadir for bitcoind
danielpbarron: i would guess something like flashing
the memory with a ramdisk image
that has all
the kernel userland and bitcoind already in
there
davout: and since you mention
the final product, what would
the
target procedure look like
to configure a new pogo?
danielpbarron: i was able
to compile bitcoind for a pogo from my gentoo laptop using crossdev
davout: ok, where would i find directions
to compile it properly for
the pogo?
davout: so now do i compile bitcoind right
there? or should i somehow compile it on my local machine?
☟︎ danielpbarron: yeah, it's as insecure as could be, because
telnet shouldn't be enabled on
the final product anyway
danielpbarron: you should be able
to
telnet in as root, password is probably also root or something
davout: so now i guess i just need
to build
the bitcoind release and put it on
the pogo
danielpbarron: he decided
that since
the
thing has no RNG, ssh is a waste
davout: ah i see, i
tried SSH'ing into it
to no avail
danielpbarron: if you used ascii's
thing,
then it should have
telnet built in
davout: the pogo seems
to have a half green half red light
danielpbarron: netcat stops
there, you shouldn't see anything else
davout: yes, i got
the u-boot working, see
the output i get in netcat ^
danielpbarron: you used
the qnology guide
to get
the uBoot
thing working?
davout: danielpbarron: so looks like i managed
to get
the kernel loaded and starting
davout: aah, reading
the instructions once again, it starts
to make sense
davout: danielpbarron: but i'm slightly confused at
this whole
thing, say i manage
to flash
the new uboot on
the pogo, and set
the correct variables with
the new fw_printenv command
that comes with
the improved u-boot, and
that with
the correct settings
the pogo will look for a kernel on
the network at boot
time, what's netcat for?
davout: i assume i can use
the steps relevant
to u-boot from
there
to get
the correct version on
the pogo and resume your instructions when
that's done
mod6: oh cool, i guess my pogo will be delivered
tomorrow
danielpbarron: but it does not come with
the
tool needed
to do
this, which is fw_printenv
mod6: (and yeah,
that's on a deb6 - x86_64 env)
mod6: I can't really check from here, but later
tonight will give some updates as
to how my v0.5.3.1+OrphanageBurner build is running. last I saw, it was using quite a bit of available ram. was >200`000 blocks, and still running, but
that was lastnight.
☟︎ danielpbarron: it comes with its own uBoot, which can be configured
to load a kernel over
the network
davout: perplexed at
the u-boot step, how do i actually get
to asciilifeform's "(you -did- configure
the u-boot
to
tftp by default, aha?)" ?
davout: from what i understand i need
to replace u-boot on
the pogo so
that it'll load
this new kernel over
the network by using
tftp
mod6: <+asciilifeform> [BTC-dev] Full Orphanage
Thermonuke Massif Output (Theoretically, covers entire address space of process) << great work, asciilifeform.
thanks for putting
that
together :]
davout: i've built
the new kernel according
to asciilifeform's instructions, including
the v2 patches
davout: danielpbarron: looking at your pogo docs, not sure how
to perform step 4.1 u-boot compilation
lobbes: 'Parks Department officials were unable
to remove
the bust initially, but arrived at noon
to cover it with a
tarpaulin'
lobbes: or does anyone see same << heh, I see
the same
davout: so
the original behaviour was
to actually reverse-sync
davout: not sure i get "the
thing walks
the orphanage and finds
the start of
the chain"
davout: (it doesn't reverse-sync in
the sense
that it doesn't keep a partial
tree it
tries
to reconnect
to
the currency known best
tree)
davout: ah ok, so it doesn't reverse-sync per se, but instead
tries
to get better matches
davout: or does it simply drop any block it receives and
that doesn't chain on
top of
the current best?
davout: asciilifeform: am i correct in my understanding of
the
thermonuke patch
that it will
try
to reverse-sync starting from any arbitrary block it receives?
assbot: Logged on 06-05-2015 01:12:02; williamdunne: "France Restricts
the Movement of Gold, Cash, & Crypto-Currencies"