J
jmfbahciv
Actually, he doesn't know what a zero bit is.Roland said:You've never actually worked with actual core, have you, Grasshopper?
/BAH
Actually, he doesn't know what a zero bit is.Roland said:You've never actually worked with actual core, have you, Grasshopper?
Kim said:Are you certain about that?
Today we have possibility to add millions
of gates just to protect the chips from unexpected events, radiation
for example. Altough the chips contain more and more transistors, the
FIT rates have not exploded. This has been achieved by designing
redundancy to the chips and also by fine-tuning the silicon process,
and better materials control (less alpha radiation).
The only catastrophic event from cosmic radiation is a latchup in the
cells, but that is very rare event, or nonexistent depending on the
process, wafer type and chip design.
And of course you could run two kernels in parallel, and switch from
active to passive if the active one notices problems in its environment.
This has been done for decades in telecoms equipment. Often it is
easier to notice the problem early enough to recover from it by doing
active/passive switchover than to fix the problem in HW for the active
kernel.
Greegor said:G > Either approach can work if properly executed.
G > Wouldn't it already be difficult to find a new
G > PC that isn't a dual or quad processor?
G > The genie's already out of the bottle.
jmfbahciv > I played with one on a retail shelf. Managed
jmfbahciv > to kill it within 3 minutes.
Could you please be more specific?
Are you talking about one of those tiny
$300 notebook PC's running an Atom processor?
JosephKK said:You are more discussing a single system, i was discussing a
heterogeneous mixture of systems.
It included PCs, Unix based
engineering workstations, an IBM 3090 600J, dedicated text processors
based on i never knew what hardware, and making it all work together
around 1990 or so.
JosephKK said:Yes you have. I basically come from the nuxi model.
It is kernel space in the *nix world.
MS got Cutler's flavor of VMS and called NT. They started out withTerminology is failing here.
It's not a confusion of terminology. It's more a confusion of
the software level a piece of code is executing. I run into
this confusion all the time. I think it's caused by people
assuming that Windows is the monitor. It never was.
MSwin never was much of a proper OS. Just remember that there are
more things claiming to be an OS besides Multics, RSTS, TOPS-10, VMS,
MVS, VM-CMS, Unix(es), and MSwin.
a somewhat [emoticon's bias alert here] proper monitor but spoiled
it when Windows' developers had to have direct access to the
nether parts of the monitor.
/BAH
Yep, just like the ruined win 3.1 by insisting on embedding the 32-bit
mode within the GUI, and insisting on internals access.
More yet of the tiny basic mentality.
JosephKK said:Please, i am still trying to work my way through the references you
have already provided. And i still have a day job.
On Mon, 01 Jun 2009 22:00:14 -0500,
Should have said:
And SEMICONDUCTOR memory may well come up in a random state.
RAM is just a bit generic.
Greegor said:G > Either approach can work if properly executed.
G > Wouldn't it already be difficult to find a new
G > PC that isn't a dual or quad processor?
G > The genie's already out of the bottle.
jmfbahciv > I played with one on a retail shelf. Managed
jmfbahciv > to kill it within 3 minutes.
Could you please be more specific?
Are you talking about one of those tiny
$300 notebook PC's running an Atom processor?
jmfbahciv said:Nope. The extra pluses are to fool you into thinking it's faster...
than molasses in January in the Northern Hemisphere.
JosephKK said:I suspect you and i are talking past each other. Expand some more on
the distribution thing. Especially, clarify how it is different from
the marketeering thing. I sure do not follow you yet.
jmfbahciv said:Actually, he doesn't know what a zero bit is.
Anne & Lynn Wheeler said:i've been blamed for computer conferencing on the internal network in
the late 70s and early 80s ...
the internal network was larger than the arpanet/internet from just
about the beginning until possibly late '85 or early '86 ... misc. past
posts
http://www.garlic.com/~lynn/subnetwork.html#internalnet
some old pictures including online at home between 77 & mid-80s (still
haven't found any pictures of online at home from early 70s):
http://www.garlic.com/~lynn/lhwemail.html#oldpicts
jmfbahciv said:Nope but I was thinking about all the scanning that gets done
for security.
Will this gear survive a vacuum running near it?
jmfbahciv said:My observation is that the computing biz has cycles. What
I'm seeing now is what we saw in the 70s. The hardware
is too slow for customer needs so the software has to
compensate. Since hardware speeds were increased over
nobody had to write software well. Now that the hardware
is hitting a silicon ceiling, the focus is slowly, IMO,
going back to using software solutions to squeeze out
the extra performance.
Since you submitted a timely correction, we'll also overlook that "RAM
memory" is a parallel construction to "PIN number", "TCP protocol" or
"LED diode".
Peter Flass said:As did OS/2 years ago. I think the file systems run in ring 2.
John Larkin said:True, I've only done RTOSs and embedded systems. But timesharing is
dead.
jmfbahciv said:Nope. The extra pluses are to fool you into thinking it's faster...
than molasses in January in the Northern Hemisphere.
John Larkin said:I will assume you're not enchanted with the present gear. So what do
you think OS architectures will be like ten or 20 years from now, when
multi-core is the norm?
On Mon, 01 Jun 2009 19:45:50 -0700, Archimedes' Lever
Nope.One instruction? - Pull Power Cord.
ALL ZEROS.
I win.
True CORE memory holds its state across power failures.
And RAM memory may well come up in a random state.
--
ArarghMail905 at [drop the 'http://www.' from ->] http://www.arargh.com
BCET Basic Compiler Page: http://www.arargh.com/basic/index.html
To reply by email, remove the extra stuff from the reply address.