117300+ entries in 0.906s
ben_vulpes: pete_dushenski: is this
a 'freegan' thing?
assbot: Logged on 24-01-2016 02:10:26; ben_vulpes: "We DEMAND that the workload given to employees be reflective of their abilities...should not be given
a workload that they cannot handle."
assbot: Logged on 24-01-2016 01:51:14; adlai: fwiw friend who teaches classics at
a usg 'prep school' attests to having had
a student excused from any and all performance standards due to APD (which stands for 'auditory processing disorder')
ben_vulpes: for once in my short life i would like to not piss on
a fence.
ben_vulpes: hey does anyone have suggestions for
a non-retarded display manager?
BingoBoingo: Kinda why eventual #b-
a library where people put text from outside the wot for preservation from molestation would have some similarity to deeding.
assbot: Money, Trust, and the Wild Wild Web (
A socioeconomic history of SSL, or that green lock symbol in your browser) ... (
http://bit.ly/1NsN7n0 )
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].
assbot: Logged on 24-01-2016 03:45:09; mod6: <+asciilifeform> mod6: the principal obstacle is the lack of
a computer. << oh you're saying
a target arch here? or?
assbot: Logged on 24-01-2016 03:31:44; mircea_popescu: "never go to sea with two clocks. take one or three. so we're taking two but one has
a special button to press to ask it if it's really sure. if it is it squaks audibly."
mod6: <+asciilifeform> mod6: the principal obstacle is the lack of
a computer. << oh you're saying
a target arch here? or?
☟︎ mod6: which btw for testers is kinda nice -- you can make
a really large volume and attach to which ever instance at will and keep your OS small, or swap it out easily without ever having to clobber your build/sandbox area
polarbeard: surely was introduced for it, windows users see logs as
a feature
mircea_popescu: "never go to sea with two clocks. take one or three. so we're taking two but one has
a special button to press to ask it if it's really sure. if it is it squaks audibly."
☟︎ polarbeard: well, I use logrotate, but I'm
a linux-lowlife
polarbeard: it supposedly overwrites the log and (how considerate) leaves you
a few lines from the old one
mircea_popescu: fwiw i have
a lot more faith in code someone read than in code someone wrote.
mircea_popescu: to put it in you'll have to sign it. if it turns out later to have
a hole, people will negrate you.
☟︎ mod6: <+asciilifeform> we don't have
a computer. << well, this goes back to the same thing. currently we're married to some linux varient to do (future) building of flashable universe
mod6: you buy
a flash rom (from S.NSA? or from local place you trust??) then get V, build
a flashable universe, flash the card, drop it into some device and then you can talk to it over some wire from your work station
mod6: eh, sorry: does the idea of
a flashable universe built from rotor still make sense.
mod6: does anyone else think that this is *not*
a decent consideration at least? even taking into consideration the issues we ran into with pogo?
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.
mod6: asciilifeform: so are we basically, with rotor, able to not only build
a static bitcoind, but couldn't we also build
a flashable rom that contains said static binary -
a flashable universe so to speak?
mircea_popescu: understand mod6 : the thing that scared me above isnm't per se the fact that now we need 4, but that well... it grew. might be we're sitting on some unbounded complexity /
a loose recursion tail.
ben_vulpes: this is
a wonder i would greatly like to see myself
mircea_popescu: mod6 in the end we'll need
a v thread for the source, one for the manual, one for linux make one for bsd make etc ? like 4 ?
mod6: this is perhaps were
a seperate branch of V for bsd only comes in. or maybe i misunderstand.
mircea_popescu: (or from
a security perspective, esp the cpu and memory)
mod6: its
a thing, it gets flashed on to some firmware, and it basically just is, you can talk to it and use it, but it is its own thing.
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: wouldn't it be
a shitton cheaper to not need
a vm layer if at all avoidable ?
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.
mod6: so we may think of
a different way of doing something like this, maybe it's not
a full OS of sorts, maybe its
a embedded deal.
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..."
mod6: yeah, very much so.
a good conversation to have though, as our future roadmap depends on some early-on food for thought.
adlai is currently working on blockchain-databot or whatever's
a better name
mircea_popescu: BingoBoingo yeah the part where your otherwise reasonable idea breaks down is where deedbot is not really
a webservice
adlai notes that
a) archive.is works for backup b) deedbot provides verification alone c) the blockchain works for paranoid-max backup, if you pay your way
mircea_popescu: phf you seriously considering maintaining
a bsd rotor thing ?
mircea_popescu: and so then bsd support, like windows or crapple support, would be
a bolt-on ?
mircea_popescu: "bitcoinos" is
a symbol here. may mean linux, whatever the fuck it means.
mircea_popescu: asciilifeform so if someone has
a box that they're using, they can't run
a bitcoin node there unless they run it under bitcoinos ?
mircea_popescu: so then the model here is to have fundamentally speaking
a pogo/arm-ish level bitcoind/os, that doesn't really natively build on anything without
a laundry list of finicking ?
mircea_popescu: obviously, as
a general thing, people MIGHT consider running
a bitcoin node on any box they run.
mircea_popescu: asciilifeform logically :
a) you won't want to ssh into the node and do your bash there (providing it even has ssh). this means you'll be stuck using something else on top of bitcoin-os.
mircea_popescu: the problem with that is that well... nobody'd want to bash in bitcoinos. so we'll end up with
a very strange catamaran of
a stack.
assbot: You need an Ambien to sleep because you bought the trappings of power instead of the real thing. | Contravex:
A blog by Pete Dushenski ... (
http://bit.ly/1PuVgJ8 )
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.
mod6: so
a minor annoyance there. but alas.
mod6: and further, the changes that we wanted to make with V (where we mechanically check to see the patch was applied correctly by checking the hashes) also will not work on bsd unless
a bunch more alterations are made, but this is
a side issue.
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.
assbot: Logged on 24-01-2016 00:41:21; mod6: The hang up here is that, it basically can't be mirrored in the same place as the rest of the patches; simply because when one sync's up against
a mirror your changes will break the rest of the tree.
mod6: <+mircea_popescu>
http://log.bitcoin-assets.com/?date=24-01-2016#1383446 << wait, explain this to me ? << the idea is that our makefiles, or whatever build scripts will utilize V to build inside of the rotor (
a linux thing) - the source must be compatable with that. phf's openbsd scripts are not compatible with this.
☝︎☟︎ mircea_popescu: we can't be the first people doing
a multi-platform release.
assbot: Logged on 24-01-2016 00:41:21; mod6: The hang up here is that, it basically can't be mirrored in the same place as the rest of the patches; simply because when one sync's up against
a mirror your changes will break the rest of the tree.
ben_vulpes: "the immediate implementation of
a free bussing system"
ben_vulpes: "We DEMAND that Oberlin College stop functioning as
a gentrifying institution"
ben_vulpes: "We DEMAND that the workload given to employees be reflective of their abilities...should not be given
a workload that they cannot handle."
☟︎ ben_vulpes: "We DEMAND that each worker, temporary or permanent working for the College Dining Hall Services be given
a meal every work shift"
ben_vulpes: "We DEMAND that Black student leaders be provided
a[n] $8.20/hr stipend for their continuous organizing efforts around the well[-]being of Black people on Oberlin's campus, city and beyond" << man that is some low-dough shit
BingoBoingo: And seriously Oberlin historically has been
a trailblazer in surrendering to such demands