4400+ entries in 0.003s
mp_en_viaje: \t should be used for
tabulature and \s for individual spaces.
ossabot: Logged on 2019-11-30 12:34:56 diana_coman: mircea_popescu:
trouble is
that it's *not* development
that is painful-er, not at all; it's...publishing
that is painfuller and I doubt
that has any merits.
diana_coman: as I ended up doing a long log-crawl on v-matters because
it's still bugging me, I found several discussions on spaces vs
tabs but overall I can't
tell what
the current conclusion is on
this: does anyone know?
mp_en_viaje: i know some rural dumb cunts very much like
the us. nobody outspends
them on kerngknekjvsdfks.
mp_en_viaje: "oh, we were worried china outspends us on $random-nonsense-we-made-up-specifically-so-as-to-have-it-all-to-ourselves" "why were you worried about
that ?" "so we have somtething
to
talk about" "ah, okay"
BingoBoingo: lol,
they'll
talk about anything but
the missile gap
that matters
mp_en_viaje: i
thought for a moment
they did
that artificial nacre
thing
ossabot: Logged on 2019-12-07 20:15:41 BingoBoingo: Breaking down
the Pizarro disks we discovered... Some platters don't shatter
BingoBoingo: drawing attention is
typical of a
Thursday night at
this hour. Meanwhile a number of
the smaller forgettable plaza have above average, but still unimpresive crowds.
BingoBoingo: Report on
the local kids: small but slowly growing crowd where crowds normally grow on
the Rambla. One 'Republicana' Police
tank parked near
the Montevideo sign. At least one helicopter flying low and angrily sweeping its spotlight all over with no apparent purpose other
than
to "be seen". Several pairs of motorcycle cops riding along
the side streets, also likely with
the "be seen" mission.
The amount of kids present in
the spot
BingoBoingo: As in all of
the platters from
the few spinnign rust drives in
the rack. After having been sanded
they are soaking in a
Tomato+ColaBlack sauce on
the camp stove.
BingoBoingo: Breaking down
the Pizarro disks we discovered... Some platters don't shatter
BingoBoingo: mp_en_viaje: Going well. Prepping drives for hammer
time right now.
ossabot: Logged on 2019-12-07 13:59:44 BingoBoingo: !!rate jfw 3 Met in person. We rolled servers on
the rambla.
mp_en_viaje: this spyked discussion's something
the fuck else lmao.
deedbot: BingoBoingo rated jfw 3 << Met in person. We rolled servers on
the rambla.
BingoBoingo: !!rate jfw 3 Met in person. We rolled servers on
the rambla.
BingoBoingo just assuming hardware is cheaper
than directed hands on a
task
spyked will admit he doesn't even know how reverse engineering costs can be estimated, most likely due
to lack of experience. will ask around, maybe someone in
the field can give an idea
BingoBoingo: spyked: My suspicion is
that
the cost of acquiring a
TMSRbootable board is almost aways going
to beat supporting new hardware, unless
the new hardware is *very* interesting.
spyked: anyway, I'ma sit on
this
thread for a while, will focus on getting uefi disentangled for now
spyked: urds is gruesome (read: both very risky and
time-consuming) enough
that doing it once will shift
the business
towards
tmsr hardware ossabot: Logged on 2019-12-05 06:33:41 spyked: also otoh, I'm not entirely sure custom biosen/chips are
the way
to go, since
they require a fair amount of reverse engineering, which is usually a massive
time sink. it'd certainly be an interesting research project, but it's not something I'd make
the delivery of
tmsr-os depend on.
ossabot: Logged on 2019-12-06 13:04:11 dorion_road: a V-ified cooreboot will provide more leverage in increasing hardware coverage. if a patron wants
to sponsor
the owner (or anyone else from his WoT)
to expand
the hardware coverage, having it V-ified forms a good foundation as I see it.
lobbes: My root issue is really
that I
haven't been optimizing for the best case in general. Completely separate from
that is
the issue of my general computer illiteracy. Both of
these I can work
to cure via diving into ebuilds, so I'll hold steady on
this course I reckon
dorion_road: while I understand you wanted
to
the logging project
to go smoother, but you were also picking up a new langauge for
the job.
ossabot: Logged on 2019-12-04 22:49:59 lobbes: and even
then, it has always been 'soft computering' like reporting, sql queries, excel jockying, etc.
The only programming language I really know is python (and
that I've only ever used here in
tmsr)
ossabot: Logged on 2019-12-04 22:32:39 lobbes:
though
tbh,
this whole experience makes me
think
that maybe computers just ain't my
thing. Perhaps I ought
to
think about BingoBoingo's writing for Qntra course a little more instead of
this
TMSR OS project
dorion_road: to summarize
then, having coreboot owned, even with minimal hardware coverage
to start, provides a long
term incentive
to have
this key piece well covered.
dorion_road: With
that being said,
the operator ought not ~have~
to use coreboot
to run
tmsr.os since so much extant hardware has yet
to be liberated from vendor control of
the bios.
dorion_road: a V-ified cooreboot will provide more leverage in increasing hardware coverage. if a patron wants
to sponsor
the owner (or anyone else from his WoT)
to expand
the hardware coverage, having it V-ified forms a good foundation as I see it.
dorion_road: If a
full process insurance business can be derived from
tmsr.os in
the longer
term, I'd expect
the bios
to be included (assuming bios as it's now referred is part of
the end process).
dorion_road: I'm sure many people here are doing
that as well,
these logs are where I first learned about it, afterall.
dorion_road: In my brush up of, now wtf again is SMM ?
this morning, I referred
to an old
article by
robert. r. collins on
the
topic. He's new
to me, but CV looks impressive, anyone here come across him ?
ossabot: Logged on 2019-12-06 05:17:15 spyked:
http://logs.ossasepia.com/log/trilema/2019-12-05#1954378 <-- it was part of a study on (or rather using) qemu,
to figure out how whatever software runs in SMM interacts with
the OS at boot/run-time. unfortunately it got piled under a bunch of other work and I never got it published.
ossabot: Logged on 2019-12-06 05:14:46 spyked:
http://logs.ossasepia.com/log/trilema/2019-12-05#1954376 <--
tyvm dorion_road! yup, I'll add uefi study
to saturday's plan,
the first step I have in mind is providing some context/rationale and making an estimate of how much
the study and mapping process is going
to
take.
ossabot: Logged on 2019-12-05 12:01:38 dorion_road: With
that being said, BIOS auditability and integrity is a key piece of
the pie and someone owning it and adding configs for
the set of supported boards would be a win
to my eye.
BingoBoingo finally applying
to places in Buquebus range (also Missouri en Argentina del Norte).
Trying not
to hold "No querés re-activar
tu proyecto de venta de servicios web? Nosotros para ayudarte podemos ofrecerte el servicio sin costo inicialmente..." against
them.
diana_coman: well,
they have actually developed a partnership
that works, certainly.
BingoBoingo: jfw has indeed. Publishing quite
the
treasure
trove.
The jfw/dorion pairing seems
to be a great benefit
to
the both of
them.
BingoBoingo: We appear
to be first outside of
the mailing list on
this, so
taking a bit of
time
to
try spreading
mircea_popescu: to
the attack, but
this was incorrect, at least regarding IPv4" <<
the moneyshot
there.
deedbot: 2018/11/30 04:54:33 <zx2c4> My "nice post" remark wasnt sarcastic, if
thats what youre responding
to
mircea_popescu: this is ~all~ obviously crypto-matter (which'd explain why
the forefuckwits managed it so poorly -- crypto is like
the intellectual antithesis of moronman)
mircea_popescu: i must know, at
the end of its run a)
that it optimally used
the bytespace by wringing out periodicity in
the input ; b)
that only
the designated keys can ever get
the input back out and c)
that a specific set of occurences will not harm
the contents. such as "two consecutive lost bytes once ; AND six independent lost bytes". or w/e it is. set percentually or w/e.
mircea_popescu: it's high fucking
time for a ~comprehensive~ archival-and-encryption util
that handles compression, encryption ~and error redundancy~!!!! correctly.
mircea_popescu: the WHOLE FUCKING POINT of "armored" mode is
to armor it, you're not wasting
those 40% extra bytes just for
the sake of wasting
them wtf.
mircea_popescu: so koch-gpg is, out of
the box, worse
than useless for archival :
tar / zip / etc as
they exist on unix-likes are fucked in
the head enough such
that if
there's a byte error, either
the remainder of
the archive or
the bytes past
that one in
the list are lost ; but
this can be mitigated at least by having multiple copies. gpg however, multiple copies are equally useless, if none make it intact
the contents is lost, because
mircea_popescu: in other "lulz", in
the sense
that koch & co are so fucking evil it boggles
the mind : gpg has an ascii armored mode, which however contains no error recovery.
ossabot: Logged on 2019-03-04 16:14:16 mircea_popescu: empire does not in any factual sense exist. man who works 70% of
the
time for idiots is ===
the remaining 30% of
that man.
ossabot: Logged on 2019-05-17 19:17:54
trinque: republic is scant of profit centers
dorion_road: I haven't developed it very far past what's in
those articles and what we've done
to develop
JWRD, but seems like
there is a medium
to long
term
profit center to establish.
dorion_road: spyked et. al, is ^
that a sensible approach
to you ?
dorion_road: With
that being said, BIOS auditability and integrity is a key piece of
the pie and someone owning it and adding configs for
the set of supported boards would be a win
to my eye.
ossabot: Logged on 2019-12-05 06:33:41 spyked: also otoh, I'm not entirely sure custom biosen/chips are
the way
to go, since
they require a fair amount of reverse engineering, which is usually a massive
time sink. it'd certainly be an interesting research project, but it's not something I'd make
the delivery of
tmsr-os depend on.
dorion_road: how about you outline your first steps
there in
the plan you'll be publishing saturday ?
dorion_road: the uefi 1/2 cleavage is a priority crevice
to map in detail.
ossabot: Logged on 2019-12-05 06:29:20 spyked:
http://logs.ossasepia.com/log/trilema/2019-12-03#1954183 <-- ftr, I'm not especially familiar with coreboot,
though I've swimmed for a while in
the SeaBIOS code a couple of years ago. but otoh
the uefi 1/2 cleavage is worth studying and documenting in detail and I'll
take
that up if you
think it's a priority.
spyked: also otoh, I'm not entirely sure custom biosen/chips are
the way
to go, since
they require a fair amount of reverse engineering, which is usually a massive
time sink. it'd certainly be an interesting research project, but it's not something I'd make
the delivery of
tmsr-os depend on.
ossabot: Logged on 2019-12-03 18:05:46 dorion_road: as it
turns out, it seems
to my eye
that it'd suit you well, given, e.g.,
the low level firmware work you're doing. do you want it ?
spyked:
http://logs.ossasepia.com/log/trilema/2019-12-03#1954183 <-- ftr, I'm not especially familiar with coreboot,
though I've swimmed for a while in
the SeaBIOS code a couple of years ago. but otoh
the uefi 1/2 cleavage is worth studying and documenting in detail and I'll
take
that up if you
think it's a priority.
spyked: in related news, my november review/december plan was also delayed because of
that, I'll have it published on saturday, along with my notes on current
tmsr-os status
lobbes: true. I'm gonna
take some
time
to absorb
that
trilema
lobbes: hm is
this something I can change,
though? Or am I doomed here
mircea_popescu: i dunno
this has anything
to do with computers per se, or in other words even if you decide you want
to write, or make pottery, or run an isp or whatever
the fuck else, you'll just meet
the same bugaboos in different skirts.