380400+ entries in 0.254s
BingoBoingo: But seriously none of
the republicans are going
to stop before
the first primaries because
they gotta build
their profile in public
to become
TV hosts
BingoBoingo: George Clinton was well known at
the
time
though
trinque: Trump and Carson practically fist-bumped on stage in
that CNBC "debate"; I wouldn't be surprised
to see
them end up running
together
mircea_popescu: i would imagine
the republicans understand enough of
their small penis issues
to not imagine
they can pull democrat
tricks.
BingoBoingo: <mircea_popescu> who
the fuck are
they gonna pick ? jeb ?
the doc nobody heard of ? << Doctor Stoner is actually leading now. Rubio appears
to be
the establishment alternative now
that Jeb is dead in
the water
trinque: bragged about HP's role helping
the NSA under her watch,
too
mircea_popescu: who
the fuck are
they gonna pick ? jeb ?
the doc nobody heard of ?
liquidassets: Exactly BingoBoingo except I still have
to go back and read more
to get
the full context
BingoBoingo: For honeydicking, I am less certain
the proper course of action
BingoBoingo: <liquidassets> ... << full disclosure via logs is most correct
thing for honeytrapping no? << Yes, like
that
time I blogged
the FBI visit
to my front door
liquidassets: anytime you're opened up
to liability,
the one who documents best seems
to win
liquidassets: “only
the Übermensch will have
the strength
to fully accept all of his past life, including his failures and misdeeds, and
to
truly will
their eternal return” grepped straight from
the logz
trinque: whole
thing is a massive sin
assbot: Logged on 04-11-2015 18:50:13; *: asciilifeform would like input from his WoT re: what is
the correct
thing
to do with obvious usg honeytrapping as described earlier.
mircea_popescu: what
the fuck
these fucking idiots and
theyr css. should be hanged.
mircea_popescu: so
the fucking web idiots have come up with a novel css hell
that chokes my browsers.
trinque: asciilifeform:
thinking
the kernel's automount mech. for pogo's external disk slot?
mircea_popescu: back
to
tape : not
to mention
that since
these
these
things are virtualized, you could in principle specify how you wish
the available mem
to be split among
the various rotating
tapes.
mircea_popescu: kinda have a) a nix ; b) a bitcoin and c) an obvious pogo-merge for
these
two.
mircea_popescu: trinque
the eventual end goal is
to have bitcoinix. as alf says, no userland at all. nor really a kernel in
the common sense.
phf: mircea_popescu: i honestly
thought it was a
thin wrapper around call
to unix mkdtemp, glad i checked
trinque: I suppose given you can fire up networking entirely from within
the linux kernel, init=bitcoind may be all
that is needed at some point
mircea_popescu: and for
this same exact reason, as alf would say, "cement".
assbot: Logged on 05-11-2015 03:16:02; phf: mod6: you might be right not wanting
to `use`. i decided
to look at file::temp
to see how
they do ffi, but instead it's a custom perl written blob. probably reasonable
to use, but.. in any case i recommend at least conforming
to
the api of mkdtemp("/tmp/fooXXX") => /tmp/fooAj5. i
took a stab at a sample code,
http://paste.lisp.org/display/158520, but
there are some other
things
to keep in mind,
phf: system message buffer operates
that way (i.e. what you get with dmesg)
mircea_popescu: actually
the rotating
tape is not such a bad idea. not just for pogo-log, but in general. wild notion, but, asciilifeform how about memory allocator
that simply overwrites
the beginning ?
assbot: Logged on 05-11-2015 03:00:13;
trinque: no, but my shits do not flush
the
toilet for
themselves....
assbot: Logged on 05-11-2015 02:54:26; asciilifeform: on a machine like pogo it does not make sense
to produce
the log at all
trinque is curiously googling what init=bitcoind would
take
trinque: init on
the same device is
taking about 300kb more
than runit, as on
this
thing I have
the former starting
the latter
gribble: Bitfinex BTCUSD
ticker | Best bid: 445.21, Best ask: 445.3, Bid-ask spread: 0.09000, Last
trade: 445.2, 24 hour volume: 285121.27754096, 24 hour low: 366.66, 24 hour high: 504.0, 24 hour vwap: None
phf: in
that case you'd better
truncate it doing run
too, because if
that pogo doesn't go down,
there's no cap on
the log
trinque: bout
two orders of magnitude north of
that
phf: should
there even be logs on pogo?
trinque: one sec while I go find
the ram usage of runit on a similar device
trinque: runit runs
things in precisely
this manner, and is
the smallest init guy I know
phf: mod6: you might be right not wanting
to `use`. i decided
to look at file::temp
to see how
they do ffi, but instead it's a custom perl written blob. probably reasonable
to use, but.. in any case i recommend at least conforming
to
the api of mkdtemp("/tmp/fooXXX") => /tmp/fooAj5. i
took a stab at a sample code,
http://paste.lisp.org/display/158520, but
there are some other
things
to keep in mind,
☟︎ trinque: asciilifeform: why not have
the
thing barf everything
to stdout and stderr and let whatever's out
there do with it what it pleases; opposed
to unix-y small proggies
that do one
thing here?
trinque: I was
thinking of a lower log level
than whatever I'd expect from "debug" but in
that case yes
trinque: this log file is a small fraction of
the size of
the blockchain which is also constantly being written
trinque: no, but my shits do not flush
the
toilet for
themselves....
☟︎ trinque: when it is sitting on a system where
the user can decide
to do
this if he chooses
trinque: I am commenting on
the idiocy of a
thing *ever*
taking it upon itself
to erase
the history of its own operation
trinque: how does
the fact
that it was written for windows argue for
the retardation staying
trinque: if it were
the ADA version or even one written with as few deps as possible, I'd grant you're right
trinque: the rotation was put in
the debug log;
that is mega-autism
phf: mkdtemp is a canonical way of creating a
temporary directory on unix,
that'll also ensure a) no collisions b) proper permissions, i.e. 700
trinque: asciilifeform: yes I would prefer
that it only do one
thing, but you are correct
that it calls
this only if !fDebug