121900+ entries in 0.069s
NoSatoshisHear: then
they put
the bastard in everything, moved from NB
to CPU, and you know
the rest...
NoSatoshisHear: yup, every engineer who heard of
the system hated it, and
the vp++ loved
the idea, gave control
to corporate overlords of your work machine.
NoSatoshisHear: I worked on ICH7 and ICH8, fugging bugs out
the ass in ICH7...
NoSatoshisHear: yup...
that is it. Started in 2004, was designed
to access memory, drive, and ethernet while main cpu was asleep...
NoSatoshisHear: I'll be damned if
they didn't put
that bastard into my sacred north bridge!
The intel management engine...
NoSatoshisHear: was pretty cool getting
to be in
the architect meeting.
They introduced
the FU chip in 2004 as a seperate processor. I so voted it down. It sounded like a spy chip and it was.
NoSatoshisHear: left, was not happy with
the system,
thought it was not conducive
to making new wares, but great for maintaining older established platforms.
NoSatoshisHear: you get a percent of
the profit every quarter, I started at 25% of salary, and got a 10% bump at 1 year, some 20 year+ doods have 2000% multipliers.
ben_vulpes: "dump
trucks of money every
two weeks" is how i heard it described one
time.
NoSatoshisHear: I have, came last summer, fugged around, left with a copy of
trb
to play with, will make a real name and gpg id in
the near future....
ben_vulpes: didja at least keep
the options in
the divorce?
NoSatoshisHear: ex game engineer, ex intel architect, now
too old
to get hired. life summary.
☟︎ mircea_popescu: you can sorta guess when exactly
the "strong independent woman" will start bawing like a little girl on
the basis of
the displayed priors.
mod6: <+asciilifeform>
to me it looks completely indefensible. <+asciilifeform> WHY should boot
time be special ? << aha,
to me your change
there seems like
the Right
Thing
mircea_popescu: the
thought was
that
this runs for a coupla hours after hours on uni computer
diana_coman: asciilifeform, no "advocate", more like explain: probably
the
thought was
that after it starts it remains (magically!) always at
the
top
mod6: so im fairly confident
to get it resolved here with a simple email. will report back one way or another.
mod6: but,
their site says
they will do hardware mods via request.
mod6: if for some reason DC won't
throw in a SSD, even if extra fee is paid, will find a new DC.
mod6: so im sure
that ssd will give me a huge perf boost
to stay up
to HEAD
mod6: for instance, i have a R610 running with ssd, and when doing eatblock (sucking in all
the blocks cut up via cutblk), I can process like 15k-20k blocks per day. more importantly,
the IO
timings are WAAAAAY lower.
mod6: My node got with 140 blocks,
then promptly fell back behind about 400-500. but
this is caused by my dedicated node running on spinning rust it appears. when i get a moment, I'm gonna call
the DC and see if
they'll
throw in an ssd in
there for me.
that should cure it.
mircea_popescu: 2 was not actually stated by anyone, i'm just saying for
the record.
a111: Logged on 2018-01-25 19:12 ben_vulpes: suresure. what even means "a release"
though, in a world where each patch now
touches
the changelog file.
that eg ben_vulpes produces a patch
that *only*
touches
the changelog, saying "the foundation makes of
this link in
the chain a checkpoint"?
trinque: because human brains balk at a 500k scroll, so
they chop
the
thing into bits
trinque: a C++ program is not reducible
to particular files sliced out of it. it's
the whole, and
the filesystem state is a lie.
mircea_popescu: both 1 and 2 seem a rather "we'll fix
the car by retrofitting horse carriage
to it"
mircea_popescu: 1.
the idea
to have "changelog only" patches as a signature device is a major departure from how v worked previously, it semanticizes an item
that we only recently even introduced ; 2.
the idea
to have patches
that are deliberately non-compliant so "they won't be mainline" is a solution
to what i
thought an inexistend problem -- why not maintain special "experumental" keys for
the purpose instead, l;ike sane people ?
ben_vulpes: makes for a neat delineation between patches baked in an angry stew and
those selfsame patches read in
the cold light of morning and possibly even reground by others as "this works, and i propose it for inclusion in
the
trunk"
trinque: experimental patches meanwhile wouldn't, and
the operator is invited
to regrind
the experimental item into a patch which edits changelog, if it's graduating out of "experimental"
trinque: editing
the changelog, "mainline" would not ever have multiple leafs, aside intentional forks
mircea_popescu: i suppose
the idea here is
to
turn
this into a semantic device ?
mircea_popescu: trinque if
they don't
touch changelog
they'll have
to be reground
then
ben_vulpes: that
the world promises
to deliver me a regrinding nightmare out of stitching
together
ten patches
that all descend from
the release patch
ben_vulpes: i'd rather have people chose which node on which
to base
their patches
themselves, based on
their own judgement of
the quality of
the priors, otherwise
there's a new axis of promisetronix in play
trinque: I was supposing
that experimental patches would not
touch changelog, patches meant for release would edit changelog
ben_vulpes: suresure. what even means "a release"
though, in a world where each patch now
touches
the changelog file.
that eg ben_vulpes produces a patch
that *only*
touches
the changelog, saying "the foundation makes of
this link in
the chain a checkpoint"?
☟︎ trinque: ben_vulpes: macroexpand my statement
to "I am not adding maintaining my own wad of chosen experimental patches, regrinding
them each
time
there is a mainline release"
ben_vulpes: more of a
tumor hanging off
the infant's face, but yeah
ben_vulpes: given
the evolution of 'v', and
that
the act of pressing is a private, intimate one, does "current
trb's behavior" make much sense anymore?
trinque: I intend for deedbot's node
to always reflect current
trb's behavior
trinque will be happy
to start using
the mainline version.
trinque: wasn't
that patch marked experimental?
trinque: this is
the node we were discussing, makefiles.vpatch + polarbeard
trinque: nope,
this was
the deedbot node. each
time it happens,
there are many external connections, and each
time a restart brings it back
to
the
top.
a111: Logged on 2018-01-25 18:03
trinque: what a
terrible error message.
trinque: I just fired a garden variety
tx and it confirmed in
the next block, 0.0005 fee
trinque: heh, 0.0005 confirms instantly now. aren't we all glad
the shitheads got
their gigablocks
trinque: mhm, and
this is an input
that was change more recently
than 3k blox