PLEX86  x86- Virtual Machine (VM) Program
 CVS  |  Mailing List  |  Download  |  Newsgroups

Thou shalt have no other gods before the ANSI C standard 1568


Your Ad Here

Your Ad Here

Thou shalt have no other gods before the ANSI C standard 1570
How profound. :-) The idea that anyone could send you an email, with executable content inside has got to be one of the worst they have come up with, and that is saying...

there were several cambridge science center reports and a couple of SJR technical reports. then there is my marathon session at SEAS that i've recently referenced.

clock, resource management, etc ... was part of resource manager, before it was released, i had to write a specific manual (maybe 40-50 pages) for it and give clbuttes (i don't think the manual is still available ... and it carried copyright ... so you didn't see it leaking into academic press). this has transcription of the product announcement letter of the initial resource manager release:

there is the indirect publication of the stanford phd on clock (and global LRU) in the late 70s; there was an issue of opposition to granting the phd ... because of the diaagreement between local LRU and global LRU. I was asked to provide supporting evidence to break the deadlock. There had been a ACM article by the grenoble science center implementing the local LRU strategy on the same operating system and hardware (that i had done global LRU & clock in the 60s while undergraduate ... about the same time that the original ACM paper on local LRU was published). I had numbers that showed that my global LRU implementation from the 60s significantly outperformed the grenoble local LRU (on same operating system and platform) ... misc. past refs:

after i was at the science center ... lots of research resulted in code that was absorbed directly into products ... in one way or another. there was misc. stuff ... like gov. restrictions on pre-announcing products ... if it was being absorbed into product, talking about it could be considered violation until after it shipped (and that process could be a year or more). as code became less & less free, you started to see more & more concerns expressed about giving too detailed description about commercial products. of course when i was an undergraduate ... there was less concern about possibly proprietary code issues ... even when the code was being absorbed in distributed commercial product ... like extract from '68 share presentation i made as undergraduate:

i guess part of the issue ... was that while i spent a great deal of my career at the cambridge science center and san jose research, a lot of my research ... i also wrote product code for that was shipped in commercial product. a lot of time that might have gone into producing academic papers were instead spent on shipping commercial products.

there were half dozen or so SJR reports drafted that never received corporate approval for publication ... numerous references about the work being too close to commercial (primarily because i would write all the code and drop it into internal production systems ... and so it took on quite a bit the characteristic of being real and commercial ... as opposed to research).

Thou shalt have no other gods before the ANSI C standard 1571
Windows Server 2003 is the fastest, most reliable, most secure Windows server operating system ever offered by Microsoft. " .mspx "Microsoft's patch factory was running at full production...

there were also rumor that i was going to have harder time receiving publication approval after being blaimed for tandem memos (early online computer conferencing and other stuff). At one time, there was some claim that for specific months, I was some how responsible for as much as 1-3rd of all bits flowing that month across all of the internal network. note, from just about the beginning until mid-85 of so, the internal network was larger than all of the arpanet-internet ... misc past posts about the internal network:

random past refs to tandem memos: ttp:--www.garlic.com-~lynn-2001g.html#5 New IBM history book out

Thou shalt have no other gods before the ANSI C standard 1569
that is the story about problems with later shipping SMP support. up until that time, they were charging for application code ... but not kernel code. the original resource manager got selected...

--



Your Ad Here

List | Previous | Next

Thou shalt have no other gods before the ANSI C standard 1569

Alt Folklore Computers from Newsgroups

The #1 Usenet Provider on the Internet

Thou shalt have no other gods before the ANSI C standard 1567