log☇︎
129700+ entries in 1.025s
ascii_field: when a packet comes in over the wire, it gets thrown into a buffer pointed to by a particular register in the card's cpu, and the latter reads the addr of the next buffer from a pre-baked list
assbot: Logged on 05-11-2015 01:07:56; asciilifeform: at any rate, i (and $maxint others) will port $whateverthefuckyouwant to, e.g., cray II. for a fee.
PeterL: http://log.bitcoin-assets.com//?date=05-11-2015#1316588 << when I was in middle school we went on a field trip to the Warren (MI) Army Tank Plant, tour included the Cray II, cool looking room sized machine with liquid cooling fluid bubbling over its brain ☝︎
ascii_field: i'ma do a worked example for PeterL
phf: thestringpuller: it wasn't actually forced. started as a final project in william arbaugh's (the guy who did the smooth handover wireless implementation at umd) class, where we were writing a malloc for the teaching os as a final project, only three mallocs came anywhere near the spec, since mine was one of them i had the opportunity to say that the whole thing was a sham "shit code written by retards", etc. and that you can have orders
ascii_field: jurov: do i understand, this needs a heavily patched client ?
phf: ascii_field: that's the problem with a lot of lisp conversations here, your interlocutors have some vague idea about how things are done right now and in unix world. even unixisms are used not in their "pure form", but in their final gnu/linux state. there's complete lack of semantic match between that and historical lisp. ultimately debates are reduced to "macros are bad because cpp is bad" ☟︎
thestringpuller: phf: ugh they made you do that shit too? we had to write malloc for the game boy advance, or a game boy advance game for a final project for course in C
phf: ascii_field: my undergrad "thesis" was putting a malloc on a one of those teaching os's, it was interesting in that "wrestling with bare metal" sort of way, but then i learned how lispm does it, and realized that i was lied to
ascii_field: if you want to use it as a graphical terminal
mircea_popescu: punkman kinda what i was proposing, a progressive scale. imo the way i stated it is better pr, but whatevs.
punkman: why not a minimum bet amount, everything else gracious donation
phf: v6 is a beauty, but for the amount of stuff that's required to be written why not lisp os?
kakobreklaa: so you wanna make poorfags even poorer to a point where they no longer send a satoshi, is this the idea?
mircea_popescu: i suppose if you prefer i can instead make it a time rule, and be like "bets under 0.0001 are paid in a year. bets under 0.01 are paid in a week"
mircea_popescu: it is not worth my time to handle 10k satoshi txn for less than 10k satoshi. this is a fact.
kakobreklaa: if you leave dust sitting long enough and at some point flush all the dust in a single tx to a nondusty result ?
mircea_popescu: it's also a problem of cost. dust txn impose a cost on us.
mircea_popescu: no. speaking of catalythic chemistry. as a thing. which it is.
assbot: Logged on 05-11-2015 06:14:54; mircea_popescu: kakobrekla listen, im running into a whole fucking list of problems with all the shitty dust people send to bitbet. do you suppose we put in a progressive fee structure ? like "fee is a minimum of 0.0001, + 10% of everything under 0.01 + 1% of rest ?
mircea_popescu: "In its classical form the BZ reaction consist of a one-electron redox catalyst"
mircea_popescu: boi o boi am i hgonna have a fun
mircea_popescu: but by your very definition this is not a fundamental result.
ascii_field: (that energy is only conserved on a large enough time scale)
ascii_field: yesterday no one knew em wave was a thing. and then - it is.
ascii_field: poor old j.c.maxwell gets no rest when this comes up, but i'ma have to use him as example again. he didn't even bother ~trying~ to build a radio...
ascii_field: this is not a moral judgement, just an observation - you need different people for the foundation of a concept, than for 17th floor
ascii_field: bldg has a foundation. it is different from the other parts of the structure in that it lets you start having floors where prior you could only sit down in the dirt.
ascii_field: the 17th floor of empire state bldg is not a fundament.
ascii_field: 'fundamental' is an actual thing. it doesn't resolve to 'very spiffy', it has a meaning
ascii_field: PeterL: there is such a thing as invention.
ascii_field: but comes out of a nozzle in cn.
ascii_field: it'd be fundamental if it opens up a whole concept that was previously closed. e.g., if a catalyst were to be found that makes electrolysis of h2o reasonably efficient
mircea_popescu: how the fuck do you think you have genome sequencing, otherwise, and why the fuck do you think woman's stockings is a bigger deal.
PeterL: a bunch of small improvements adds up over time
mircea_popescu: what the fuck's gonna happen, invent a new electron load ?
ascii_field: PeterL: in so far as i can see from my perch, nothing fundamental has happened in at least a generation.
ascii_field: PeterL: most of what's happening in chem is a) usg grantsmanship b) monkey tricks to extend pharma patents. and most of what remains is being done by folks who grew up with hobby chemistry.
assbot: Logged on 04-11-2015 18:01:40; asciilifeform: which more or less died out as a scientific field in the 'civilized' world.
mircea_popescu: i wouldn't think it's worth a crap in absolute terms.
punkman: so according to that chart 11million btc moved in a day?
trinque: The Department of Defense's posture on cybersecurity ultimately affects national security. << There's a deep cultural flaw in this sentence emanating from the word posture.
mircea_popescu: <jurov> i tried to sync my 0.5.4 to core 0.11, it won't sync << this is a horribru error message.
assbot: Baidu found China’s “ghost cities,” but it is keeping their locations mostly a secret - Quartz ... ( http://bit.ly/1LRCXz2 )
punkman: http://qz.com/540571/baidu-found-chinas-ghost-cities-but-it-is-keeping-their-locations-mostly-a-secret/
shinohai: I can't say for certain until I clone my drive, had to idle it for a bit.
shinohai: ;;later tell SuchWow Your quit message is atrocious. "This too is temporary, as most things are" reduces your comma usage and makes you not sound like a hippy.
asciilifeform: ^ aha this is a good picture of www programming.
ben_vulpes: culture out here is such that you can skirt by for ~30/wk and a relatively cheap commute, with no "lifetime commitment".
assbot: 2 results for 'bezzlecorp' : http://s.b-a.link/?q=bezzlecorp
ben_vulpes: much like picking up chixx, it's easier if you have a few in tow already.
ben_vulpes: operating as a corporation rather than an individual has benefits like that.
ben_vulpes: 220V, 3 phase, a poured pad, and nobody would bat an eye if you weather-proofed the ADU.
ben_vulpes: as it stands, he hates the kind of work my shop does, and i have a list of people who also hate the kind of work that we do but also find the company company so beguiling that they're willing and sometimes even eager to do it anyways.
mircea_popescu: eh fuck him, what, he gets a say now ?
mircea_popescu: kakobrekla listen, im running into a whole fucking list of problems with all the shitty dust people send to bitbet. do you suppose we put in a progressive fee structure ? like "fee is a minimum of 0.0001, + 10% of everything under 0.01 + 1% of rest ? ☟︎
ben_vulpes: i pay technical staff hourly rates such that should staff choose to work a 35+ hour week, they'd make depending on their value to my org ±10% of a bigcorp salary.
ben_vulpes: "employ" in the states is a peculiar contractual arrangement where the employer agrees to remit taxes on behalf of the employed.
mircea_popescu: there should, i imagine, be a way to extract significant cheating out of the fact that we don't intend to support random gunk.
asciilifeform: and the only promising heuristic thus far is a somewhat mircea_popescuine one - namely, to de-generalize the problem
asciilifeform: this is one of the problems i've been fighting with for perhaps a year now.
asciilifeform: when you desperately need speed / compactness, you use 'cdr coding' which is a cheat whereby you set a bit in the former word which signifies 'next is not an address but actually the next word.'
mircea_popescu: but that aside : if you build your own allocator you can do a lot of things you wish you could have done.
asciilifeform: at any rate, the correct way to build memory is - cons cells. as in, every addressable unit actually contains a word followed by another which acts solely as an address of 'next word.'
mircea_popescu: like, a rowhammer immune one.
asciilifeform: and you need a memory allocator.
mircea_popescu: seems this v6 thing would be a great starting point for a great many things.
asciilifeform: ('can throw bytes from point a to point b and back and they get there in order')
asciilifeform: and it's still a mega-turd
asciilifeform: http://log.bitcoin-assets.com/?date=05-11-2015#1316953 << add a network stack, nic driver, disk caching (without which no real time bitcoin), then the unspeakable horror of even the smallest known incarnation of libc... ☝︎
mircea_popescu: " It compiles in a couple of seconds and is trivial to boot up in QEMU." o.O
assbot: US Navy Poised To Order New Boeing Fighters, F/A-18 Super Hornet Jets Could Be Ordered Soon ... ( http://bit.ly/1kcbejJ )
asciilifeform: which could handily compile itself in a few mSec on boot.
asciilifeform: because then it's a complete and almost usable os.
asciilifeform: isn't it a marvel, what these looked like before the cancer ?
asciilifeform: https://github.com/ahorn/xv6/blob/master/kill.c << example of why lions book was a thing
asciilifeform: all-process table. Similarly, there’s no malloc() in the kernel, but rather just a page allocator. The pipe implementation copies one byte at a time. Amazingly, even the bootloader is a pleasure to read. Another nice thing about Xv6 is that it comes with a short textbook that explains OS concepts in terms of their implementations in Xv6.'
asciilifeform: 'Xv6 is a rewrite of v6 UNIX in modern C that runs on multicore x86 chips. It compiles in a couple of seconds and is trivial to boot up in QEMU. It took me a while to see the genius of Xv6, which is that it is simpler than I would have thought a working multicore OS with shell and filesystem could be. For example, it lacks wait queues and ready queues — in Xv6, both wakeup and scheduling are accomplished by looping over the
BingoBoingo: <asciilifeform> BingoBoingo: i'm still waiting for the magical 1986 or so of our day, when thinking people stop even recreationally giving a shit about the stuffed shirts << Too late BitBet exists
asciilifeform: BingoBoingo: i'm still waiting for the magical 1986 or so of our day, when thinking people stop even recreationally giving a shit about the stuffed shirts
mircea_popescu: never in history has a nobody been elected before
liquidassets: honeydicking <<a bitch by definition
trinque: whole thing is a massive sin
mircea_popescu: your "formatting" does not work inline, go die in a fire.
mircea_popescu: so the fucking web idiots have come up with a novel css hell that chokes my browsers.
asciilifeform: (see old threads where we beat this to a liquid pulp)
asciilifeform: of a mechanism which ought to work this way
asciilifeform: mempool is a great example
asciilifeform: mircea_popescu: an allocator that knows that it is acceptable to lose some old bits is called a circular buffer and behaves like a looped tape, yes
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
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,
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 02:54:26; asciilifeform: on a machine like pogo it does not make sense to produce the log at all
asciilifeform: in fact, a battlefield bitcoinatron has no business having a conventional 'userland' at all.
asciilifeform: and it won't be a matter of a few changed lines, either.
asciilifeform: but it does NOT make sense for it to evolve in the direction of being 'a good unix util'
asciilifeform: moreover, since unix has no future, but unfortunately we are stuck with a junkyard of rusting x86 and arm boxes, it makes sense for bitcoin to evolve in the direction of being an os
asciilifeform: my argument here is not that the behaviour of the classic debug log is a beautiful thing, but that any change to bitcoin that MAKES MANDATORY the presence of so much as an 8kB proggy on the machine, is LETHAL