112100+ entries in 0.911s

ben_vulpes: heh
i am still snickering about that one
ben_vulpes: all that aside, when
i finally ditch this thing,
i will preserve the shit that's already on disk.
ben_vulpes:
i do not see what relationship the directory structure has to the things
i have said, other than they expose the retarded toolchain
i used to get them on the public net in the first place.
ben_vulpes:
i thought la serenissima's webfacists hated linkrot
ben_vulpes: so what,
i ditch current shitty static site generator and tell everyone who linked to shit previously to get fucked and find the new linxz?
ben_vulpes: why? people's links will break if
i go back and add intervening footnotes.
mod6: anyway, yah, its not like it called malloc or whatever, its on the stack.
i am retard.
mod6: maybe
i was just remembering this: "Most machine architectures provide a contiguous virutal address space for processes. Some machine architectures, however, choose to partition visibly a process's virtual address space into regious termed segments [intel, 1984].
mod6: ya,
i think
i was just confusing some kern shit that
i'd read.
mod6:
i gotta read up on paging again
i guess.
mod6: the only place
i can find that is in util.cpp:ShrinkDebugFile()
mod6: no,
i use /mnt/btc-dev/.bitcoin since mine is in an attached volume.
polarbeard: lol,
I'm following the rabbit hole and it seems pszSetDataDir is not set if -datadir not given
assbot: Logged on 24-01-2016 02:05:25; ben_vulpes:
i thought there'd be about another 5 years before things got this nutso
mod6:
i could be wrong here.
polarbeard: well,
I use logrotate, but
I'm a linux-lowlife
mircea_popescu: fwiw
i have a lot more faith in code someone read than in code someone wrote.
polarbeard:
I'm building better logging in two steps, first
I lay out better and prefixed messages, people can review that
polarbeard: mircea_popescu: good because
I'm removing it
mod6:
i think it could be pretty neat, in the end.
mod6: yah,
i still think this might be a resonable path. but lot of thought still must go into this whole thing. tonight was a great discussion on it tho.
ben_vulpes: this is a wonder
i would greatly like to see myself
mod6: this is perhaps were a seperate branch of V for bsd only comes in. or maybe
i misunderstand.
mircea_popescu: asciilifeform yeah
i guess most of the problem comes from that chasm. we're not the first to meet it.
polarbeard: bitcoinos would be based on what?
I think that's the interesting part
mod6: <+mircea_popescu> mod6 here's the problem with "Bitcoinos" : you will want it adapted for bitcoin needs, which necessarily means it won't be your tool of choice for doing almost anything else, which necessarily means maintaining it will be a pain in the ass. << agree.
I think that what
I'm getting at is maybe it ends up being like cisco ios.
mircea_popescu: but
i'm discussing YOUR HOME BOX. not some rando box you run.
mircea_popescu: so
i'm not terribly interested in that line of thought.
mod6:
i guess my thought is, if we wanna make bitcoinos - we will end up forking either SVR4 or BSD, and then getting married.
mircea_popescu: mod6 to my mind it's almost as if we bit a recursion girder over here. "v presses source". "ok how do
i build it ?" "uh...
i guess you need a v-make genesis and follow that for your os." "ok... how do
i do that ?" "well... get v-make-make and..."
mircea_popescu: anyway.
i suppose this entire compatibility general issue will need more thinking about.
BingoBoingo: mircea_popescu: So that
I don't have to link fiat uni web sites.
mod6: because they can not use buildroot... at least,
I don't *think* they can, easily at lesat. they could turn on Linux Binary Comapt mode and perhaps some other kernel tweeks. would need to be looked a.t.
BingoBoingo: <asciilifeform> (~different~ braindamage than in linux, and this is appealing to some people) << This is pretty much its appeal to me.
I have modest needs as far as necessary hardware and necessary software go.
mircea_popescu:
i suspect it'd be a horrid mistake to try and merge the notion of a press and the notion of a makefile.
mod6: however, if he and
I work together, we could possibly get some patches in place that would check to see what the local environment is and if __BSD__, then apply, otherwise, do not.
ben_vulpes:
i thought there'd be about another 5 years before things got this nutso
☟︎ BingoBoingo: Seriously been a while since
I posted a really bad one
shinohai:
i just have it cat the latest blkxxx.dat over once every 12 hours.
mod6: <+shinohai> mod6:
i am fully synced nau ^^ << ^6
mod6: having an alternate to linux is important to me. and
i was able to build a static binary, but obviously this doesn't work with the rotor (linux only buildroot).
i did build it with the stator.
shinohai: mod6:
i am fully synced nau ^^
mod6: yeah,
i think
i need to walk you through the exact steps.
i did get it to build, and fully sync a chain even. was very happy about that.
ben_vulpes: but
i probably hosed something on that machine way before ever making it to building tri.
ben_vulpes: fwiw
i completely failed to get the openbsd patch to work.
mod6: <+ben_vulpes> mod6:
i do believe that
i understand now. << cool!
mod6: phf: your patch(s) did work for me on openbsd.
i think, once we have all of trinque's makefiles ready to go with the new (forthcoming) version of V, you and
I should work together to get a new vpatch of your openbsd changes submitted.
ben_vulpes: danielpbarron:
i swear that
i'm referencing something mircea_popescu said with that line, but
i'll be damned if
i can find the original.
ben_vulpes:
i'd have probably done something ham-handed and just set the order for the given flag, which would be a bigger change to life-fire use than
i think would be warranted.
ben_vulpes: 'tis a very surgical strike, if
i'm reading correctly. only if the flag is set and the sig does not bear the correct order is order enforced.
ben_vulpes: mod6:
i do believe that
i understand now.
phf: fwiw openbsd didn't make it through v-ification either, it was designed to work cross platform, but
i believe there were makefile modifications since, that didn't include it.
i don't actively run openbsd, so can't integration test the result
phf:
i can bring it forward, it wasn't included in the v release, nor did anybody ask about it, so
i assumed it's not needed
mircea_popescu: hanbot should be universal. if
i find any thing worse than in the time of the predecessors
i'm bringing out the machine guns and fire throwers as a matter of principle. and
i want the skies bathed in the screams of the innocent and the blood of gutted babes, also as a matter of principle.
hanbot:
i wonder how often that's more tolerable than eg cazalla's worse-off-than-grandpa plight.
phf: so only thing
i did with timestamps in logs is add milliseconds to the log printer (to add necessary precisions to graphs).
i'm pretty sure
i discovered that blockchain height served as well in my case (produced similar shapes with none of the "laptop went to sleep" noise), but
i was looking specifically at the number of block send/recv retries
hanbot: admittedly
i was looking moar at the "quality of life" bit