List of Archived Posts
2002 Newsgroup Postings (7/11 - 8/8)
- HONE was .. Hercules and System/390 - do we need it?
- HONE was .. Hercules and System/390 - do we need it?
- HONE was .. Hercules and System/390 - do we need it?
- HONE, Aid, misc
- HONE, ****, misc
- HONE, xxx#, misc
- HONE was .. Hercules and System/390 - do we need it?
- HONE, ****, misc
- "Clean" CISC (was Re: McKinley Cometh...)
- "Clean" CISC (was Re: McKinley Cometh...)
- "Clean" CISC (was Re: McKinley Cometh...)
- "Clean" CISC (was Re: McKinley Cometh...)
- "Clean" CISC (was Re: McKinley Cometh...)
- Unisys A11 worth keeping?
- Symmetric-Key Credit Card Protocol on Web Site
- Unisys A11 worth keeping?
- Ever inflicted revenge on hardware ?
- CDC6600 - just how powerful a machine was it?
- Symmetric-Key Credit Card Protocol on Web Site
- ITF on IBM 360
- MVS on Power (was Re: McKinley Cometh...)
- basic smart card PKI development questions
- Computer Terminal Design Over the Years
- Symmetric-Key Credit Card Protocol on Web Site
- Definition of Non-Repudiation ?
- MVS on Power (was Re: McKinley Cometh...)
- LSM, YSE, & EVE
- Unisys A11 worth keeping?
- ibm history note from vmshare
- mailing list history from vmshare
- Weird
- Unisys A11 worth keeping?
- Latency benchmark (was HP Itanium2 benchmarks)
- VT50, VT51, VT52, VT55, VT61, VT62 terminals (was Re: Weird...)
- ...killer PC's
- Latency benchmark (was HP Itanium2 benchmarks)
- Difference between Unix and Linux?
- HONE was .. Hercules and System/390 - do we need it?
- MITM solved by AES/CFB - am I missing something?!
- Beginner question on Security
- Beginner question on Security
- Transportation
- Transportation
- Killer Hard Drives - Shrapnel?
- Funeral for a friend - Infiniband
- M$ SMP and old time IBM's LCMP
- M$ SMP and old time IBM's LCMP
- M$ SMP and old time IBM's LCMP
- SHARE Planning
- Funeral for a friend - Infiniband
- SHARE Planning
- Next step in elimination of 3270's?
- "Slower is more secure"
- SHARE Planning
- MIT says I don't live in the USA
- AADS, ECDSA, and even some TCPA
- Server and Mainframes
- Server and Mainframes
- SSL integrity guarantees in abscense of client certificates
- SSL integrity guarantees in abscense of client certificates
- How to map a user account to a digital cert?
- SSL integrity guarantees in abscense of client certificates
- Server and Mainframes
- SSL integrity guarantees in abscense of client certificates
- vm marketing (cross post)
- Total Computing Power
- vm marketing (cross post)
- Total Computing Power
- Killer Hard Drives - Shrapnel?
- Killer Hard Drives - Shrapnel?
- hone acronym (cross post)
- history of CMS
- help: Thinking with Meat
- How to map a user account to a digital cert?
- Itanium2 power limited?
- 30th b'day
- Difference between Unix and Linux?
- IBM 327x terminals and controllers (was Re: Itanium2 power
- Future interconnects
- Q: Trust in an X.509 certificate
- Difference between Unix and Linux?
- Q: Trust in an X.509 certificate
- formal fips186-2/x9.62 definition for eal 5/6 evaluation
- Summary: Robots of Doom
- formal fips186-2/x9.62 definition for eal 5/6 evaluation
- Summary: Robots of Doom
- formal fips186-2/x9.62 definition for eal 5/6 evaluation
Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: HONE was .. Hercules and System/390 - do we need it?
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Thu, 11 Jul 2002 15:43:05 GMT
jcmorris@mitre.org (Joe Morris) writes:
>A minor question that's been on my mind for several years: was the
>official name of the system "Hands-On NEtwork"? I've seen this given
>as the origin of the acronym HONE but never from an official source.
Hands-On Networking Environment
^ ^ ^ ^
>Another nagging question: why APL, both in the sense of "why at all"
>and (especially) why "total dependency?" Was there a directive that
>only APL was to be used, or was it just that at the time APL, despite
>its resource consumption, was still seen as the best available tool?
the padded cell environment was first built in APL and lots of the
delivery tools were written in APL. Way back when ... in the origin
(some memory fade) ... cp/67 services were put up in some of the
regions for field people support ... including being able to run some
370 testing (aka they were provided with a special modified version of
cp/67 that emulated virtual 370 rather than virtual 360, "cp67h"). This
was part of the effort that had a modified cp/67 (cp67i) that would
run on a real 370 hardware with relocate support a year before the
hardware was built:
http://www.garlic.com/~lynn/2002h.html#50 crossreferenced program code listings
Some applications were written in APL and I believe the group doing
some of the applications had chosen APL and they just grew. It
eventually became a whole "padded-cell" envrionment (sequoia). This
then drove a lot of the applications ... included some "foreign"
applications that were recoded in fortran because of extreme
performance issues. I believe that as the body of APL applications
grew, it just built up a sort of legacy momentum. One of the extensive
uses of APL at the time were the various what-if things that you see
done in spreadsheets today.
>And some customer shops were given access to the configurator programs,
>although (obviously) not to the ordering tools. I recall using them,
>for example, to develop a viable configuration for our 3725, a task
>made more difficult than it should have been because we got no
>documentation at all except for the online help -- and this over a
>2400 bps (+/-) dialup circuit.
I also used 3725 configurator to validate numbers used in comparing
large configuration implemented using the S/1 SSCP/NCP emulator:
http://www.garlic.com/~lynn/99.html#67 System/1 ?
http://www.garlic.com/~lynn/2001.html#4 Sv: First video terminal?
http://www.garlic.com/~lynn/2001i.html#21 3745 and SNI
http://www.garlic.com/~lynn/2001k.html#21 OT: almost lost LBJ tapes; Dictabelt
http://www.garlic.com/~lynn/2001n.html#9 NCP
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: HONE was .. Hercules and System/390 - do we need it?
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Thu, 11 Jul 2002 15:49:51 GMT
"Russell P. Holsclaw" writes:
After the outbreak of the HIV virus, these tools went by another name,
but I don't recall what it was. ISTR that the impetus for renaming
them came about as the result of some embarrassment in which the
authors of many of these tools were brought together for some sort of
awards banquet at a hotel in San Francisco. The upshot of this was
that many programmers were turned loose on the streets of San
Francisco wearing baseball caps that said "AIDS" on the front. This
created a minor disturbance.
one of my favorite stories of renaming was the santa teresa
lab. Normally labs will get the name of the local post office/town
(aka like Meyers Corner). I was on vacation in Wash DC the week before
the santa teresa lab was to be dedicated and there was a group from
san francisco demonstrating on the steps of the capital; these were
some professional ladies that had a group name the same as the closest
post office to the santa teresa lab. In a very short time, a new name
was selected.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: HONE was .. Hercules and System/390 - do we need it?
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Thu, 11 Jul 2002 16:32:27 GMT
jcmorris@mitre.org (Joe Morris) writes:
Another nagging question: why APL, both in the sense of "why at all"
and (especially) why "total dependency?" Was there a directive that
only APL was to be used, or was it just that at the time APL, despite
its resource consumption, was still seen as the best available tool?
another even earlier kickstart for APL .... was that some group was
supporting the business people in armonk and dp hdqtrs (1133). They
were writing apl models that were allowing these people to do various
what-if & other kinds of business analysis.
this was when cms\apl was first created (port from phili's apl\360 to
cms environment and making available up to 16mbyte workspaces instead
of just 16k or 32k workspaces). there was an enhanced sense of
security when all the most valuable corporate data was loaded onto the
cambridge system so these guys could run their financial & business
analysis applications. eventually these guys got their own cp/67
systems down and new york. random past ref:
http://www.garlic.com/~lynn/2002h.html#34 Computers in Science Fiction
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: HONE, Aid, misc.
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Thu, 11 Jul 2002 19:37:00 GMT
ok, didn't found a HONE reference card (yet) ... but digging thru some
old stuff did find an Aids Reference card.
also, somebody pointed out that my prior use of Myers Corner as an
exmaple was a poor choice ... it was the intersection not a post
office.
Note in the attached, consolidation of the (US) regional HONE systems
to California didn't occur until 1977. At this time in 1973 there HONE
regional centers in Los Angeles, Chicago, Washington DC, and New York.
This is also before Sequoia and the automatic "padded-cell" (aka
people logging in found themselves automatically placed in the
Sequoia padded-cell (didn't have to "IPL CMS", start APL, etc).
Other stuff, not exhaustive but
VMSHARE Users Guide card (dated January 1980)
... online reference now at
http://vm.marist.edu/~vmshare
REX Reference Summary First Edition (Nov. 1980) - for REX version 2.08
(before product release and name changed to REXX)
Several System/360 Model 67 Reference Data (one of them stamped Edward
J. Mosher, aka the "M" in GML, SGML, HTML, XML, etc).
Orange cover The SHARE Songbook
Several copies of the (reprinted) 1931 IBM Songbook
===============================================
(small part of the card transcribed)
IBM Aids Reference Summary, ZZ20-2341-4 Fifth Edition (January 15, 1973)
The reference summary supersedes the previous edition and will be
updated from time to time. Copies of this publication are distributed
to IBM Marketing Representatives and System Engineers. Additional
copies are available from the IBM Distribution Center, Mechanicsburg,
Pa. Comments about this publication may be sent to the address
below. All comments and suggestions become the property of IBM.
IBM Aids Usage Guidelines
New IBM Aids
Configurators available via
- APL Library 810
- SECOM TOOLS
- PID
Design Aids available via
- APL Library 820
- SECOM TOOLS
- PID
- HONE
The MINIPERT System in APL Library 835
- MINIPERT User Aids
- MINIPERT Processing Programs
- MINIPERT Standard Networks
Management/Financial Aids available via
- APL Library 850
Installation Aids from PID
Performance Aids from PID
Other SECOM Applications
Special Aid - System/7
IBM Aid Publications
Instructions for accessing or ordering IBM
Aids available via
- HONE
- SECOM
- PID
- IBM Distribution Center (Mechanicsburg)
IBM Aids Announcement Procedures
NOTE: New IBM Aids have been made available since September 1,
1972 are listed on pages 2 and 3.
----
Instructions for accessing or ordering IBM Aids
Accessing from HONE Systems
All IBM Aid APL Libraries are available on your regional HONE system
via APL (CMS). Other non-APL IBM Aid Programs implemented on HONE are
accessed via CMS. Obtain the phone number of your regional HONE
system, your location's ID and current password from your HONE
coordinator.
On a 2471 terminal proceed as follows:
1. Dial your regional HONE system.
2. Press ATTN, when the keyboard unlocks.
HONE will type CP/67 on-line
3. Press ATTN
4. Type LOGIN xxxx (your user ID)
HONE will type ENTER PASSWORD:
5. Type: xxx (your password)
HONE will type: enter: mannumber, last name,
initial, position, purpose, facility
6. Type (the requested information including a position
code 0 to 9; purpose code, m; facility code, 5)
Note: See HONE log-in procedure card for position code
selection
HONE will respond with a LOGON message.
Your are now under control of CP/67.
7. Type: IPL CMS
CMS will respond and you will be under control of CMS.
To access an APL IBM Aid
8. Type: APL (Use APL type element)
APL (CMS) will respond with the status of your P-disk.
You are now under control of APL (CMS) and may load
any of the IBM Aid APL workspaces. For example:
9. Type: )LOAD 820 TPNET
To access a non-APL IBM Aid Program
8. Type xxxxxx (The CMS name for the program)
For example:
Type: AIDEX
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: HONE, , misc.
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Fri, 12 Jul 2002 01:28:37 GMT
well the previous post got subject to all sorts of delays and other
things ... apparently because of the four letters that appeared
frequently in the post.
i've just about run out of places to look for the HONE reference card.
Did find
a reference card for VS/APL applications that customers could
order dated 1979.
a 3270 fullscreen editor user's guide printed 5/18/77 at HONE1 on the
backside of greenbar paper. There were a number of 3270 editors
developed internally around the company for CMS during the '70s
... this particular one was RED (for raleigh editor).
a printout done at HONE1 on 4/15/77 of the internal network ... also
on the backside of greenbar paper. This is in two parts, 1)
"graphical", little boxes with the node name and lines connecting to
other little boxes and 2)actual node list giving nodid, "index" (in
the graphical ... majority of nodes didn't show in the graphical),
location, (machine) model, type of system, and operator/contact phone
number. Slightly different format to one used later:
http://www.garlic.com/~lynn/99.html#112
The (US) HONE consolidation process had just started at this point and
would grow extremely rapidly over the next two years.
There were the DEMO centers in the list ... which had slipped my mind.
In addition to HONE operation for things like configurators and ****,
there were also education center machines and "DEMO" machines in each
of the regions (for use by people in the respective regional and
branch offices). HONE had started trying to shutdown all general use
of CMS and just restrict things to the padded-cell environment. The
"DEMO" machines provided more of a native CMS time-sharing capability
to the people in the branch offices.
DEMO1 Boston
DEMO2 New York
DEMO3 New York
DEMO4 Philadelphia
DEMO5 Washington, DC
DEMO6 Atlanta
DEMO7 Cincinnati
DEMO8 Detroit
DEMO9 Chicago
DEMO10 Minneapolis
DEMO11 St. Louis
DEMO12 Dallas
DEMO13 San Francisco
DEMO14 Los Angeles
and
DEMOPKG Wash DC (g'burg)
John Godwin supported all the DEMO systems from DEMOPKG in g'burg. At
the time of the listing, all of the DEMO machines were 370/145s except
for Boston which was a 370/148. The DEMO machines might be considered
the leading edge of the 4341 "departmental computer" wave ...
http://www.garlic.com/~lynn/2001m.html#15 departmental servers
http://www.garlic.com/~lynn/2002.html#7 The demise of compaq
http://www.garlic.com/~lynn/2002i.html#30 CDC6600 - just how powerful a machine was it?
Somewhat aside, Peterlee (science center) was also on the network
list. One of the people at Peterlee had written an email client called
VMSG. At about internal development release 0.6, somebody in the PROFS
group had co-opted the (limited function) source to use as the core of
PROFS implementation. After that, the VMSG source distribution was
limited to John, one other person and me.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: HONE, xxx#, misc.
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Fri, 12 Jul 2002 14:27:01 GMT
Mike Hammock writes:
With all the talk about HONE and "market aids", I had to get my
$.02 (USD) worth in here... About the time of the consolidation
Lynn mentions below, the IBM division I was in at the time, GSD, was
positioning itself as a almost totally independent business unit in case
of a goverment or business induced splitting apart of IBM. Part of this
inluded us 'picking up' the HONE system and running a copy of it,
with specific GSD configurators, on our own systems in Atlanta.
We started off with a 370/145 running VM/370 Rel 3. (We actually
started with Rel 2, but went to 3 before going 'production'.)
I'm pushing my memory here, but I believe that the 145 has some very
effective microcode assist for VM. However, turns that the use of
this microcode was mutually exclusive with some of the performance
assists in Sequoia so we could choose one or the other untill some
changes were made. We had to limit the concurrent logged on
users to 10 for a while... But considering that was a 512K
system doing all that APL work, even that it pretty amazing!!
Oh yes, the name of the system was MAS: "Market Aids System".
cambridge science center had done the apl\360 to cms\apl port
... including the rewrite of garbage collection for (large) virtual
memory (aka running to the end of a 32kbyte workspace in real stroage
wasn't bad ... but always running thru a 16mbyte (virtual) workspace
had all sorts of downside effects on paging). cambridge also put in
functions for making system calls ... which got lots of people upset
as violating apl purity.
palo alto science center then did apl\cms and the 145 apl microcode
(145 w/apl m'code had apl thruput compareable to 168). The system call
violation was removed and replaced with the "shared variable"
construct (that was used to implement access to system functions).
Since Sequoia was becoming a system unto itself .... Sequoia was
getting a lot of performance optimization.
My memory is hazy here, i was at some of the sequoia optimization
meetings ... and there were things like adding custom assembler
sequences to the APL supervisor specific for enhancing sequoia thruput
... which would have perturbed the ability for using the apl m'code.
HONE was running clusters of 168s upgraded to clusters of 168SMP and
tweaking wasn't done with thot of 145 apl m'code compatibility
(although HONE looked at if there was any way of leveraging farms of
145s for any of their workload).
I'm pretty sure the Sequoia/configurator group stayed in LA when the
HONE consolidation took place. In any case there were meetings between
the Sequoia group and the guy at PASC that was responsible for 145 apl
m'code (he later was also responsible for much of the high performance
fortran hx work).
There was a separate significant m'code assist for 138/148 called ECPS
that dropped a lot of the cp kernel (pathlength) into m'code ... but
that would have had little effect on CPU utilization that was nearly
all APL (and a majority of that was the apl Sequoia application). ecps
reference:
http://www.garlic.com/~lynn/94.html#21 ECPS VM microcode aasist
in the above, there were two methods used for identifying kernel
hotspots, the kernel call trace and special microcode 145 load that
did instruction address sampling. The person that was responsible for
the apl m'code also implemented the m'code address sampler.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: HONE was .. Hercules and System/390 - do we need it?
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Fri, 12 Jul 2002 17:35:05 GMT
jcmorris@mitre.org (Joe Morris) writes:
<chuckle> I presume that there was a nearby post offic3 named Coyote?
95013
old 101, monterey highway ... just north of the bailey T (i.e. bailey
runs west from old 101 crosses santa teresa, past STL lab and up into
the hills to the calero reservoir).
http://claraweb.co.santa-clara.ca.us/parks/prkpages/calero.htm
random refs:
http://www.garlic.com/~lynn/2000b.html#56 South San Jose (was Tysons Corner, Virginia)
http://www.garlic.com/~lynn/2001g.html#34 Did AT&T offer Unix to Digital Equipment in the 70s?
http://www.garlic.com/~lynn/2001g.html#37 Thread drift: Coyote Union (or Coyote Ugly?)
http://www.garlic.com/~lynn/2001i.html#11 YKYGOW...
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: HONE, , misc.
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Fri, 12 Jul 2002 19:04:58 GMT
Anne & Lynn Wheeler writes:
John Godwin supported all to the DEMO system from DEMOPKG in
g'burg. At the time of the listing, all of the DEMO machines were
370/145s except for Boston which was a 370/148. The DEMO machines
might be considered the leading edge of the 4341 "departmental
computer" wave ...
http://www.garlic.com/~lynn/2001m.html#15 departmental servers
http://www.garlic.com/~lynn/2002.html#7 The demise of compaq
http://www.garlic.com/~lynn/2002i.html#30 CDC6600 - just how powerful a machine was it?
HONE kept a pretty low profile that one of my hobbies was supplying
them with heavily customized operating system and other technology.
Finally after nearly 15 years, some executive in DPD (HONE was part of
the sales & marketing division, aka Data Processing Division - DPD)
figured it out. The reaction sort of was:
1) he hasn't had management direction to do this
2) HONE doesn't have an MOU (memorandum of understanding) from his management
commiting his time for this purpose
3) what happens if he gets hit by a bus
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: "Clean" CISC (was Re: McKinley Cometh...)
Newsgroups: comp.arch
Date: Sat, 13 Jul 2002 14:25:55 GMT
"Stephen Fuld" writes:
All true, but I want to add another determinant. Back then, the speed of
main memory was very slow and there weren't any caches. So it made sense to
have a small amount of very fast memory (usually ROM, but occasionally
writable) in the processor that could hold "instructions" that could be
fetched in one cycle. This was called microcode. Being able to fetch one
instruction from main memory that caused the execution of N actual processor
operations (micro- operations if you will) was a performancee win. Once
main memory get faster and the technology of caches became available, the
advantage of that dedicated memory disappeared and it made sense to
"execute" the micro-operations directly - thus RISC. There were several
technology factors that lead to the "risc revolution".
actually i've claimed that probably the first "big" project applying
RISC had the objective of replacing all the (smaller) corporate
micro-engines ("every S/360 and S/370 compatible processor except the
S/370 Model 75, is microcoded") with 801s (and had fairly good-size
staff-up). after that got killed, you started seeing 801 engineers at
other companies. Skill-base might also be considered a contributing
factor.
associated with activities for the low/mid range 370s also had
projects looking at JIT-like activities for 370 code. this was 20+
years ago. I got contacted, in part because I had done a PLI program
that analyzed and attempted translation/restructure of 360/370 code
nearly 10 years earlier.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: "Clean" CISC (was Re: McKinley Cometh...)
Newsgroups: comp.os.vms,comp.arch
Date: Sat, 13 Jul 2002 14:48:16 GMT
"Stephen Fuld" writes:
It has been far too long, but can't you use a Translate and Test instruction
to do the equivalent (copy until a zero byte is found), at least for up to
256 bytes per instruction?
TRT just looked for the value ... no copy.
tr/translate has a 256-byte table and takes an operand length up to 256
bytes ... it does a byte-by-byte replacement ... taking the byte
from the operand, using that value to index the table and replacing
the operand byte with the byte indexed in the table.
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/7.5.96?DT=19970613131822
translate&test has 256-byte table and an operand length up to 256
bytes ... it tkaes an operand byte and indexes the table and stops
if the table entry is non-zero. to search for just a zero has a 256-byte
table that is all zeros except for the first byte.
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/7.5.97?DT=19970613131822
neither did copies.
now for newer string instructions
move string
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/7.5.60?DT=19970613131822
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/A.3.28?SHELF=&DT=19970613131822
search string
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/7.5.70?DT=19970613131822
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/A.3.35.1?SHELF=&DT=19970613131822
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: "Clean" CISC (was Re: McKinley Cometh...)
Newsgroups: comp.arch
Date: Sat, 13 Jul 2002 15:03:01 GMT
Anne & Lynn Wheeler writes:
S/370 Model 75, is microcoded) with 801s (and had fairly good-size
oops (finger slip) s/360 Model 75
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: "Clean" CISC (was Re: McKinley Cometh...)
Newsgroups: comp.arch
Date: Sat, 13 Jul 2002 15:36:37 GMT
"Stephen Fuld" writes:
main memory get faster and the technology of caches became available, the
advantage of that dedicated memory disappeared and it made sense to
"execute" the micro-operations directly - thus RISC. There were several
technology factors that lead to the "risc revolution".
and right up their with (hardware) skill base was compiler & operating
system technology. one of the reasons for (nearly) every 360/370 being
m'code was to have broad range of hardware implementations and
capabilities while preserving programming compatibility.
riscs moved into a market segment that had a large software portable
technology base (unix & c) that was working hard on being hardware
architecture agnostic.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: "Clean" CISC (was Re: McKinley Cometh...)
Newsgroups: comp.os.vms,comp.arch
Date: Sat, 13 Jul 2002 16:44:41 GMT
JF Mezei writes:
Seems to me that this instruction is very different from the basic 360/370
architecture in terms of philosophy of arguments.
relatively recent "string" support instructions.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Unisys A11 worth keeping?
Newsgroups: alt.folklore.computers
Date: Sun, 14 Jul 2002 23:15:57 GMT
Charles Richmond writes:
To start, how about: Java, C++, PHP, ASP, J2EE, CORBA,
Bongo, Castinet, Director, XML, VB.Net, Java Beans, and
on and on and on and on and on...
fairly widespread might throw in SQL as a language (at least as per
database)?
how 'bout the original GML ... circa 1970?
both got standardized in ISO ... i don't know about the ISO status of
many of the others.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Symmetric-Key Credit Card Protocol on Web Site
Newsgroups: sci.crypt
Date: Mon, 15 Jul 2002 15:59:12 GMT
jsavard@ecn.ab.ca () writes:
The protocol proceeds as follows:
The user sends N to the merchant in the clear.
The merchant generates a random number R and sends it to the user.
The user sends E( R xor M, E(N,K) ) to the merchant (xor might really be
noncarrying decimal addition or Vigenere; whatever has similar
properties).
The merchant supplies N, R, and E( R xor M, E(N,K) ) to a black box
provided by the credit card company which knows K.
The user's program and the merchant's black box both calculate some
function f( N, R, E(N,K), M ) which is used as the secret key for
communications between the user and the merchant. The user's program does
this by being given the user's password, which contains E(N,K); the black
box does not require E(N,K) because it contains K; thus, disassembling the
program given to allow people to use their credit cards on the Internet
doesn't make the system insecure (only cracking open one of the black
boxes does).
having worked on the original some:
http://www.garlic.com/~lynn/aadsm5.htm#asrn2
http://www.garlic.com/~lynn/aadsm5.htm#asrn3
I also worked on x9.59
http://www.garlic.com/~lynn/subtopic.html#x959
there were a couple requirements laid down in the x9a10 standards
commitee for x9.59 ... 1) was preserve the integrity of the
financial infrastructure for all electronic retail payment
transactions (agnostic with respect to kind of payment and environment
of payment) with only authentication and 2) perform the payment in a
single round-trip.
One of the issues for end-to-end authentication is that the
information hiding techniques tending to only be applicable for very
transient periods during transmission while the data continues to
remain vulnerable the rest of the time (lots of stories about fraud as
the result of leakage of merchant transaction log files)
http://www.garlic.com/~lynn/subtopic.html#fraud
basically x9.59 follows somewhat an existing iso8583 message
.... except it adds a digital signature and a couple other fields
... and sends it off. The purchase could be traditional web browsing
and sending off a request with an x9.59 payment message. The purchase
could also be from a cdrom and sending off a order in a email with a
x9.59 payment message attached. The puchase could also be at POS and a
x9.59 message signed with a smartcard. There is no requirement for any
real-time protocol chatter.
x9.59 defines a business rule that account numbers used in x9.59
authenticated transactions should not be valid in non-authenticated
transactions. effectively in the non-authenticated payment
transactions, the account number (& other data) exists in a large
number of places and any leakage of that information can result in
fraudulent transactions .... aka the information needs to be treated
as shared-secret ... since just knowing the information can enable
fraudulent transactions. Furthermore, any use of encryption for
information hiding tends to be while data is in flight ... not
typically while at rest (creating a large number of vulnerability
opportunities ... both for outside attacks as well as for insiders).
The merchant is also taken out of the loop of having to protect the
consumer's account number and related information
http://www.garlic.com/~lynn/2001h.html#61 Net banking, is it safe???
(or security proportional to risk)
Rather than transient hiding of the vulnerable information while in
transit, x9.59 defines end-to-end authenticated transaction where
the party (financial institution) responsible for authorizing and
executing the transaction .... is also performing the authentication
(it also eliminates a lot of widely distributed data as fraud
vulnerabilities).
Part of the x9.59 issue was that the current infrastructure using SSL
for information hiding while data was in motion on the internet
addressed only a small piece of the business vulnerabilities (and
fraud opportunities) involved.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Unisys A11 worth keeping?
Newsgroups: alt.folklore.computers,comp.sys.unisys
Date: Mon, 15 Jul 2002 18:36:12 GMT
"Stephen Fuld" writes:
Not quite. Firewire and USB at at a different level of the protocol than
SCSI or ATA. While both of the latter do define a physical interface, SCSI
has morphed into more of a high level interface that can run on multiple
underlying interfaces. (Originally SCSI was both, but since SCSI 3, the
upper layers are defined independently from the lower ones, and parallel
cables is just one physical medium supported, along with various serial
schemes such as Fibre Channel.) So when you attach a disk to USB, you are
running SCSI over USB. For example, there is no definition in USB that
specifies how to send a disk block adddress to a disk. That is provided at
the SCSI level. ATA has historically provided both the physical and the
upper layers, but that is changing more toward the newer SCSI model with the
two separate.
One certainly could define a way to run ATA over USB or firewire, but
without some notion of disk commands, just USB or Firewire by themselves are
insufficient.
9333 from the late '80s was effectively SCSI commands over simplex
serial copper (similar to FCS but copper instead of fiber-optics).
That morphed into SSA standard. I would have preferred that 9333 had
morphed into serial copper with some FCS compatability ... aka being
able to plug SSA cables into FCS switches (operating at fractional FCS
speeds).
http://www.garlic.com/~lynn/95.html#13 SSA
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Ever inflicted revenge on hardware ?
Newsgroups: alt.folklore.computers
Date: Tue, 16 Jul 2002 13:26:07 GMT
"Rupert Pigott" <dark.try-eating-this.b00ng@btinternet.com> writes:
Actually I did give in to the urge to inflict a gruesome
revenge on a piece of hardware that let me down... My expensive
monitor failed just out of warranty (good work whoever designed
it). The sad thing is, one I bought 7 years earlier for 1/4 the
price is STILL working and has had for more use anyways.
the 1052-7 (operator's) console on the 360/67 in cambridge would
periodically get an fist sized indention in the keyboard. they kept a
spare around so the 1052-7 could be easily swapped. I was only
responsible for one of the indentions.
one of the frustrated failure modes was that the end of the last sheet
would feed past the paper sense finger ... but not far enuf so that it
would completely feed out and you would realize it was out of
paper. the only indication was that the it just stopped
working. hitting it hard would sometimes joggle the paper enuf that it
would slip further and then you would realize that it was out of
paper.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: CDC6600 - just how powerful a machine was it?
Newsgroups: alt.folklore.computers,comp.sys.cdc
Date: Tue, 16 Jul 2002 13:36:12 GMT
ctill@nc.rr.com (Chuck Till) writes:
Sounds like PR fluff in retrospect. It didn't take much to
double CDC's data service business, and I wonder how many
SBC customers in 1969 were still using CDC/SBC a few years
later.
i don't know the circumstances ... but ibm real estate retained the
SBC building out in burlington mall ... and the vm/370 group moved out
there when the outgrew the space on 3rd floor 545 tech. sq. the cp/67
group had split off from CSC and sometime in the time-frame of
starting the morph of cp/67 to vm/370 they started rapid growth
... including essentially absorbing the (ibm) boston programming
center on the 3rd floor (bpc had maybe 3/4ths of the 3rd floor, csc
was about 2/3rds of the 4th floor with the csc machine room taking
about 1/2 the 2nd floor).
the boston programming center was responsible for cps (conversational
programming system ... interpreted pl/i ran under os/360 ... and there
was special microcode available for 360/50 that made it run faster).
Jean Sammet, Nat Rochester, couple others had their offices in the
boston programming center (so the vm/370 group sort of absorbed them
also). When vm/370 group moved out to sbc bldg. in burlington mall
they stayed in 545 tech. sq.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Symmetric-Key Credit Card Protocol on Web Site
Newsgroups: sci.crypt
Date: Tue, 16 Jul 2002 14:03:59 GMT
jsavard@ecn.ab.ca () writes:
Certainly, one could print a second account number on each credit card for
use with electronic transactions, or just make the password thirty
characters long. (But if one did _that_, then the password by itself,
mailed in one envelope, contains all the information needed for an
electronic transaction... unless, of course, the account number on the
credit card has to get sent after encryption is initiated.)
sorry, i somewhat got carried away ... from the original e-commerce
stuff ... the business fraud problem IS the treatment of the account
number as a shared-secret even tho it has to be available in
clear-text in a large number of places (there are large number of
places where the account number has to be used in the clear and as a
result it can leak out ... more like a giant sieve with encryption
only covering up a few of the openings).
as an aside there is already support for mapping multiple different
numbers to the same account ... even with multiple different tokens
(magstripe or otherwise) ... aka spouse cards, etc. also from
electronic perspective ... the typical magstripe carries room for five
different account numbers (when you put a debit/atm card in an atm
machine ... the selection of which account you want to use can be
driven off the account number data on the magstripe).
x9.59 was to enable transition from a shared-secret paradigm to a
public key end-to-end authenticated transaction paradigm (possibly
deployed first in e-commerce with alternate account number)
.... eliminating knowing the account number as a fraud vulnerability
(and the necessity for information hiding).
In effect the current payment cards are two different devices ... the
physical embossed plastic that can be used in paper transactions and
the magnetic stripe for electronic transactions; these two different
devices just happened to be carried on the same card. It is possible
to package a chip for x9.59 public key operations on the smae or
different plastic. If packaged in the same plastic ... you could treat
it has three different logical devices (in the same physical
housing). There is nothing that would mandate that the chip's account
number be the same as the magstripe's account number or the plastic
embossed account number. The "correct" account number could then be
chosen based on what transaction paradigm is used ... and then apply
appropriate risk & fraud rules.
It wouldn't be necessary for somebody to write the alternate account
number on the plastic (assuming single physical housing) ... the chip
just supplies the correct value (in much the same way the magstripe
can supply up to five different account numbers w/o any of them having
to be written on the card).
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: ITF on IBM 360
Newsgroups: alt.folklore.computers
Date: Wed, 17 Jul 2002 12:37:31 GMT
Jonathan Griffitts writes:
Back in the early 1970s I used an obscure IBM product that I've never
heard of since. It was called "ITF" for "Interactive Terminal
Facility", ran on IBM 360. It provided time-sharing access using
interpreted BASIC and a PL/I subset called IPLI.
I don't remember the name ITF ... although it may be lost in memory
someplace. The ibm boston programming center (3rd floor 545 tech sq)
had done something called CPS (conversational programming system) that
matches that description. There was also a 360/50 microcode
accelerator for CPS. It is possible that CPS was renamed(?) ITF at
some point (or CPS was also called ITF)?
quicky search engine on cps
http://rivendell.uchicago.edu/cps.html
http://gopher.wvnet.edu/EVENTS.HTML
somewhat random ref:
http://www.garlic.com/~lynn/2002j.html#17 CDC6600 - just how powerful a machine was it?
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: MVS on Power (was Re: McKinley Cometh...)
Newsgroups: comp.arch
Date: Wed, 17 Jul 2002 13:06:10 GMT
gah@ugcs.caltech.edu (glen herrmannsfeldt) writes:
I don't know how much is in assembler. I would hope that PL/S would
be high enough level that such programs could be ported without
completely rewriting them. Probably it would be hard, but then
that might have been said of MacOS and VMS before they did it.
there was jokes (or at used to be) that pl/s, pl/x, etc ... was hardly
more than structured assembler.
amdahl gave a talk at mit in the early '70s ('72?) about the business
plan for clone mainframes .... saying that there were something like
$100b worth of assembler software or executables that no longer had
source ... that wouldn't get replaced at least before the end of the
century (so there would be plenty of market for his mainframes,
regardless of what ibm might do). also during the talk there were some
very pointed questions about the amount of foreign investment he had
taken.
i would expect that the amount/value of such software has grown many
times since then ... with possibly only small effect by all the y2k
work.
... however this has all been looked at several times before; during
FS in general (<25 years ago) ... and during Fort Knox specifically
with respect to 801 (20 or so years ago) ... and as already noted
... been accomplished for as/400.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: basic smart card PKI development questions
Newsgroups: alt.technology.smartcards
Date: Wed, 17 Jul 2002 13:23:12 GMT
john.veldhuis writes:
The only thing that browsers directly support, using CSP or PKCS#11, is
the Client Authentication part of an SSL connection.
So you'll need some kind of plug-in. This might be a transaction client
plug-in, which could digitally sign whatever has been posted.
some example code for ec/dsa (fips186-2) chipcard is on
www.sourceforge.net (do search on ecdsa).
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Computer Terminal Design Over the Years
Newsgroups: alt.folklore.computers,comp.terminals
Date: Thu, 18 Jul 2002 13:35:20 GMT
jeffj@panix.com (Jeff Jonas) writes:
1) the IBM system 1130 had a CRT option but it required
most of the computer to run it. The system 1130 was pre-IC,
it used little metal cans with several transistors and components inside.
or 2250m4. somebody at cambridge had done port of spacewars to to
2250m4 by the early '70s. also the initial/original/geneiss code for
the internal network was some stuff between the 1130 (aka 2250m4) and
the 360/67.
2250m1 had its own channel controller directly attached to 360
channel. I got to use one at the university. lincoln labs had done a
fortran graphics library for cms that drove the 2250m1. I modified the
cms editor to use the lincoln labs 2250 library for a simple
full-screen editor (circa late '68).
boeing huntsville had large 360/67 duplex with some number of 2250m1
running version of mvt/r13 (aka running 360/67 in '65 mode). An issue
with mvt and single flat, real, linear address space with multiple
long running programs was storage fragmentation (i.e. space for single
program needed to be contiguous ... a single 2250 program tended to
run for long periods of time). they modified mvt/r13 to use the
hardware relocation of the 360/67 to address storage fragmentation
i.e. no paging or page faults were supported ... but they used the
virtual storage mechanism to provide the appearance of contiguous
program storage).
About the time BCS (boeing computing services/systems) was formed in
late '68/early '69 ... the boeing huntsville machine was shipped to
seattle.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Symmetric-Key Credit Card Protocol on Web Site
Newsgroups: sci.crypt
Date: Thu, 18 Jul 2002 13:50:47 GMT
jsavard@ecn.ab.ca () writes:
Ah. I misunderstood; and I was disappointed when your URLs led to news
archives rather than a complete description of the protocols in question,
having misunderstood your posts.
the
http://www.garlic.com/~lynn/subtopic.html#x959
contains pointer to the ANSI bookstore for getting copy of the x9.59
standard that describes the protocol(?). there is the small issue of
standards being copyrighted and rules about ordering them from the
standards organization.
it also contains a pointer to a detailed description of mapping x9.59
to iso8583 (8583 is the internal standard for payment network
messages).
in effect, x9.59 basically describes a signed payment message. The
mapping of x9.59 to iso8583 is from the standpoint of providing
end-to-end message integrity and authentication.
a large percentage of other payment messages that have used encryption
or other forms of digital signature ... have been implemented with the
encryption and digital sigatnures being stripped off at "boundary
nodes". this results in very simple violation of basic security
principles, no end-to-end security, integrity and/or authentication.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Definition of Non-Repudiation ?
Newsgroups: comp.security.misc
Date: Thu, 18 Jul 2002 13:58:57 GMT
Ian Wade writes:
Agreed, but everything you have said relates to the originator. My
concern is to do with the recipient being able to deny receiving a
message. "Proof of existence ofa a message" will manifest itself when a
message is sent (through its accompanying signature), but has nothing
to do with acknowledging receipt of the message.
i've merged definitions from (at least) rfc2828, nsa instrusion, and
sc27 glossaries at
http://www.garlic.com/~lynn/secure.htm
the tendency is towards services that validate a lot of this stuff.
some past discussions (especially ref the last; aadsm11.htm#14):
http://www.garlic.com/~lynn/aadsm11.htm#5 Meaning of Non-repudiation
http://www.garlic.com/~lynn/aadsm11.htm#6 Meaning of Non-repudiation
http://www.garlic.com/~lynn/aadsm11.htm#7 Meaning of Non-repudiation
http://www.garlic.com/~lynn/aadsm11.htm#11 Meaning of Non-repudiation
http://www.garlic.com/~lynn/aadsm11.htm#12 Meaning of Non-repudiation
http://www.garlic.com/~lynn/aadsm11.htm#13 Words, Books, and Key Usage
http://www.garlic.com/~lynn/aadsm11.htm#14 Meaning of Non-repudiation
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: MVS on Power (was Re: McKinley Cometh...)
Newsgroups: comp.arch
Date: Thu, 18 Jul 2002 16:23:45 GMT
J Ahlstrom writes:
These are MILLSTONE code and MILLSTONE applications
pure and simple.
while a lot might be MILLSTONE code ... a lot of the applications are
like payroll, funds transfers, financial networks, check processing,
air traffic control systems, reservations, etc ... aka the nitty
gritty of business operations around the world.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: LSM, YSE, & EVE
Newsgroups: comp.arch
Date: Thu, 18 Jul 2002 21:18:01 GMT
cecchi@signa.rchland.ibm.com (Del Cecchi) writes:
Another critical area of John's work is "logic simulation." John invented a
generalized special-purpose logic simulator, which runs many orders of
magnitude faster than conventional simulations. In the 1980's a special
purpose simulation machine known as the Yorktown Simulation Engine (built
to John's design) was used to simulate an entire computer at the logic gate
level. The logic gate simulation produced answers faster than older
computers executing programs in the machine's basic instruction set. Many
of these simulation engines and their descendants are in use today. They
enable the designer to verify and fix logical design before committing it to
silicon. This substantially shortens VLSI (very large scale integration)
development times, and such special simulation engines are widely used
within the industry.
I believe the LSM (los gatos simulation/state machine ... later the
logic simulation/state machine) predated YSE (although john may have
had lots of influence on the LSM). I believe the LSM was unique in
that it included time support and could handle both asynchronous chips
and digital/analog chips (aka use for things like disk read/write
heads).
I'm not sure how many YSE actually got built ... the machine after
the LSM was EVE (endicott verification engine).
http://www.garlic.com/~lynn/2002d.html#3 Chip Emulators - was How does a chip get designed?
http://www.garlic.com/~lynn/2002g.html#55 Multics hardware (was Re: "Soul of a New Machine" Computer?)
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Unisys A11 worth keeping?
Newsgroups: alt.folklore.computers
Date: Fri, 19 Jul 2002 19:51:02 GMT
"Rupert Pigott" <dark.try-eating-this.b00ng@btinternet.com> writes:
a "Do this" it's a "Polite request", which the VM system can
ignore if it so chooses (a la Lynn's do nothing tuning
parameters). There are definately some apps which do need this
level of control, and they are a nightmare under systems that
don't give you that level of control.
one was real-time tuning parameters .... the code could monitor and
tune faster than a human could reduce data for the day and set some
parameters for the next day .... even tho a day's average data didn't
re-act to moment instantaneous changes.
i also have done a paged-mapped file system ... allowing the
application to give hints ... and then the actual system looked at the
hints vis-a-vis real time information and attempted to recouncile the
hints with real time information. this is different than a system
programmer trying to represent tuning parameters as real time
information ... when the system could do real, real time information
and tuning.
there are a lot of os/360 apps that did really good job with the
asynchronous & direct mapped I/O facilities of maximizing thruput with
lots of buffering and overlapped operation. this was a "real storage"
and "real i/o" paradigms .... mapping that capability into a virtual
memory & page-mapped filesystem offered some interesting challenges.
one of the original tss/360 operations was to try and implement
one-level store with no hints .... just map the complete file to
virtual memory and fetch a page as the page faults occured. This is
one of the things that gave tss/360 such poor thruput ... the page
mapping of both data and executables and then let the pages be fetched
synchronously a single (4k) page fault at a time.
At the simplest level ... remapping the os/360 compiler executable
overlays into paged mapped ... you could get hints on approx. what all
was going to be needed when ... and when it was no longer needed;
hints about intelligent throwing away of pages no longer needed was
almost as useful as hints about multi-page fetch and/or overlapped
fetch hints.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: ibm history note from vmshare
Newsgroups: alt.folklore.computers
Date: Sat, 20 Jul 2002 15:28:48 GMT
was doing search on vmshare some some model numbers and ran across old
IBMHIST NOTE from '87 (taken from 85 computerworld article with
misc. updates)
http://www.marist.edu/~vmshare/browse?fn=IBMHIST&ft=NOTE
vmshare currently online at:
http://vm.marist.edu/~vmshare/
in the IBMHIST NOTE file ...
SABRE ... morphed into ACP, TPF, etc ... although AA/AMR still refers to
their service as SABRE.
little side-note on the 8100 ... was the uc.5 microprocessor ... same
processor used in the 3705 and the service processor for 3081 (among
other things). while it includes 8100 ... it doesn't say anything on
the s/32, s/34, s/38 (as/400), etc.
308x project was originally referred to as "811" ... for nov. '78
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: mailing list history from vmshare
Newsgroups: alt.folklore.computers
Date: Sat, 20 Jul 2002 15:54:56 GMT
attached from
http://vm.marist.edu/~vmshare/browse?fn=LISTSERV&ft=MEMO
Append on 10/27/93 at 11:03 by Larry Chace ( LC6 at CORNELLA.BITNET ):
I've heard some strange rumblings about the author of Bitnet LISTSERV
threatening to trademark the name "LISTSERV" (and perhaps "listserver"
and other variants) and also threatening to sue people who use those
terms "inappropriately". There also seems to be "warfare" between the
Bitnet LISTSERV camp and the Unix(tm!) listserv camp. (I hear this
from folks who monitor various Internet newsgroups.) Does anyone know
about this? It seems mighty bizzare!
Larry Chace, Cornell Information Technologies
APPENDED 10/27/93 11:03:07 BY CUN/CHACE
Append on 10/27/93 at 13:54 by David Boyes ( DBOYES@RICEVM1 ) Rice University:
It's true. L-soft (Eric Thomas' new company) is making requests that
the Unix LISTSERV-wannabees call themselves something different to
prevent confusion with the real thing. Not too unreasonable a request,
considering the extremely poor quality and reliability of the Unix
imitators. I certainly wouldn't want my product named the same as
most of them.
APPENDED 10/27/93 13:54:51 BY RIC/DBOYES
Append on 10/27/93 at 13:55 by Mark A. Stevens, ECN, 708-235-2204:
To add to the rumors (to get clarification) CREN is trying to get a
person(s) to write a full-featured listserv for Unix(tm) toward the
removal of BITNET?
I'd sure like to know what's going on. Thanks.
Mark A. Stevens
APPENDED 10/27/93 13:55:41 BY ECE/MARK
Append on 10/27/93 at 15:12 by Richard Wiggins ( RWWMAINT@MSU, 517-353-4955 ):
At least one Unix wannabe, written by Anastasios Kotsikanos, has been
renamed; he is now calling it the Unix List Processor. One problem is
that many folks have gotten used to using variants of "LISTSERV" as
the generic term (e.g. listserve, listserver, list server). To
compound the confusion, many people use "listserv" as the generic for
"mailing list" -- ie both to refer to the software and to the
discussion groups it supports. So far no replacement generic has been
universally agreed upon. "Mailing list processors" seems good to me.
Even with the rename of Tasos' (his nickname) tool, many sites still
use "listserv" as the name of the user ID to send mail to in order to
subscribe to a mailing list or change options. And Tasos still has
people visit a /listserv directory on his FTP server to fetch his
code. So there's lots of opportunity for confusion.
Eric Thomas has announced intent to deliver a Unix version of
LISTSERV, which should go a long ways towards lessening confusion. As
David says it seems the Unix wannabes are notquitethereyets.
APPENDED 10/27/93 15:12:23 BY MSU/RICHARD
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Weird...
Newsgroups: alt.folklore.computers
Date: Sun, 21 Jul 2002 13:47:59 GMT
Charles Richmond writes:
At my college, when computer usage figures came out for the
mainframe (an IBM 370/155), the chemistry department was far
and away the largest user of computer time... I assume that
this is probably typical.
something similar for sjr 195 ... that and some of the floating head
simulation work (modeling the air bearing effect). also facilitated
geting time on the 3033 in the product test lab (bldg. 15) for
additional time for some of the chemistry work (aka disk engineering
and product test lab processors were being used for i/o testing of new
disks ... so cpu use was almost negligible ... if you weren't
interferring with their official use ... certain arraingments could be
made).
http://www.garlic.com/~lynn/subtopic.html#disk
the kingston engineering and science center (lots of FPS boxes and
vector pocessing) was I believe predominantly chemistry.
http://www.garlic.com/~lynn/2000c.html#5 TF-1
http://www.garlic.com/~lynn/2000c.html#61 TF-1
http://www.garlic.com/~lynn/2001m.html#25 ESCON Data Transfer Rate
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Unisys A11 worth keeping?
Newsgroups: alt.folklore.computers
Date: Mon, 22 Jul 2002 00:47:05 GMT
"Rupert Pigott" <dark.try-eating-this.b00ng@btinternet.com> writes:
Now you bring up the idea of hinting which pages are "finished with"
it might well be the better of the two halves of the same coin to
implement... Beats relying on LRU & pseudo LRU to get it right every
time. :)
LRU ... "least recently used" replacement .... based on assumption
that any location recently used is likely to continue to be used
(typical virtual memory, processor caches, etc).
under various kinds of heavy & pathelogical loads ... straight LRU
(and straight WSCLOCK) tends to degenerate to FIFO. I did a variation
on 2-bit, 2-handed clock that instead of degenerating to FIFO would
degenerate to RANDOM (if there otherwise wasn't useful information on
which to make a reasonable decision ... making a random ... quick ...
choice is better).
random refs:
http://www.garlic.com/~lynn/2000f.html#9 Optimal replacement Algorithm
http://www.garlic.com/~lynn/2000f.html#10 Optimal replacement Algorithm
http://www.garlic.com/~lynn/2000f.html#32 Optimal replacement Algorithm
http://www.garlic.com/~lynn/2000f.html#33 Optimal replacement Algorithm
http://www.garlic.com/~lynn/2000f.html#34 Optimal replacement Algorithm
http://www.garlic.com/~lynn/2000f.html#36 Optimal replacement Algorithm
http://www.garlic.com/~lynn/2001i.html#20 Very CISC Instuctions (Was: why the machine word size ...)
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Latency benchmark (was HP Itanium2 benchmarks)
Newsgroups: comp.arch
Date: Mon, 22 Jul 2002 14:05:30 GMT
"Norbert Juffa" writes:
I can certainly agree with the undesirability of random replacement. But
what's wrong with LRU (or pseudo-LRU)? It let's one control what's in
the cache precisely. Or am I missing something?
Which replacement strategy do you consider the most desirable?
optimal replacement strategy ...
LRU ... least recently used ... is based on assumption that any data
recently used by a program is likely to continue to be used by a
program ... and that data that hasn't been used for a while, won't
likely to be used for a while. That is just a general assumption. For
one thing, LRU degenerates to FIFO under all sorts of situations.
long ago, and far away ... did a psuedo-LRU (variation on wsclock)
that under situations where normal LRU degenerated to FIFO ... it
would degenerate to RANDOM (and that in detailed simulations, normal
psuedo LRU tended to get within 10-20 percent of the performance of
true LRU while the random variation tended to beat true LRU by 10
percent).
thread on this yesterday in a.f.c.
http://www.garlic.com/~lynn/2002j.html#31
more general discussion from the past
http://www.garlic.com/~lynn/subtopic.html#wsclock
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: VT50, VT51, VT52, VT55, VT61, VT62 terminals (was Re: Weird...)
Newsgroups: alt.folklore.computers
Date: Mon, 22 Jul 2002 14:18:07 GMT
jmfbahciv writes:
It was flat on top (for ones very important accessories: listings,
coffee mugs, and ashtrays), it had a little shelf one could but
a steno pad (that's when I switched to using steno pads to keep
notes and program snippets in), and it had a typable keys.
It was also "cheap" enough so that we could each have one
in our offices. I don't believe I ever had to call field
service due to breakage. VR05s were always testing one's
eyesight. I routinely dropped one before setting down to
do any work with it. It was a physical incantation that
usually worked.
when they instituted a rule that you needed VP-level sign-off for
3270s in your office ... we did the business analysis that the 3-year
amortized cost of 3270 was less per month than a telephone that
everybody got on their desk as a matter of course.
that was just about the same time that some middle management
discovered that a number of corporate executives had started using
email ... and in a number of cases a whole organization's year's quota
for 3270s for engineers and programmers got rerouted to middle
management so they could appear to be doing email also ... aka all of
a sudden it became a status symbol.
later on, such things became more institutionalized ... aka nearly all
the internal PS2m80s going to managers' offices even tho they never
used it for anything but 3270 emulation reading email.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: ...killer PC's
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Mon, 22 Jul 2002 17:21:48 GMT
ibmbama@YAHOO.COM (Howard Rifkind) writes:
The mainframe is dying and evolving at the same time. How many of
you folks have gone out lately looking for a mainframe systems
programmer or Cobol programming position? Find a position yet
within a reasonable distance from where you live? I work in
N.J. with a Systems Programmer for Canada. His commute is about
850 miles when he wants to go home for the weekend. How about
that. Yes, there will always be a mainframe of some sort because
of the types of data kept on them and the speed, but only with out
sources and very large orginizations. Start learning LINUX on the
mainframe...that's where things seem to be going.
at one point the only computers that existed were in the data center.
everybody brought their card deck to the data center to be executed,
regardless of the type or nature of the calculation to be performed.
introduction of departmental and personal computing allowed some
things to migrate off the mainframe ... that were much more of
departmental or personal computing type of tasks.
there were problems that some number of enterprise level tasks also
migrated to departmental or personal computing platforms ... in some
cases putting the enterprise at risk. part of the reason for this
migration was the difficulty and frequently long lead time of doing
any change/enhancement at the enterprise level ... no matter how
trivial.
Another contributing factor was the difficulty of implementing
local-domain applications that would access corporate data at the
mainframe. there was a legacy problem that initial PC success was
greatly facilitated by being able to do 3270 emulation ... but later
on when it came time to move on to more sophisticated operations
... there was something of battle with entrenced forces (business
units that had significant revenue from 3270 emulation products didn't
want to see replaced with peer-to-peer high-speed access
products). The resistance to introducing peer-to-peer high-speed
access products into the market place contributed significantly to
migration of enterprise data off the mainframe.
we got our hand-slapped for coming up with 3-tier architecture ...
when the whole SAA client/server effort was trying to significantly
reverse trends of applications to the PC (Lotus 123 running on the
mainframe?) ... and at the same time limiting things to effectively
3270 emulation products for access by the PC clients to mainframe data
(aka single t/r lan was more than "sufficient" for 300-500 PCs).
random refs:
http://www.garlic.com/~lynn/96.html#16 middle layer
http://www.garlic.com/~lynn/96.html#17 middle layer
http://www.garlic.com/~lynn/98.html#50 Edsger Dijkstra: the blackest week of his professional life
http://www.garlic.com/~lynn/99.html#123 Speaking of USB ( was Re: ASR 33 Typing Element)
http://www.garlic.com/~lynn/99.html#124 Speaking of USB ( was Re: ASR 33 Typing Element)
http://www.garlic.com/~lynn/99.html#202 Middleware - where did that come from?
http://www.garlic.com/~lynn/2000e.html#42 IBM's Workplace OS (Was: .. Pink)
http://www.garlic.com/~lynn/2000e.html#45 IBM's Workplace OS (Was: .. Pink)
http://www.garlic.com/~lynn/2000e.html#56 Why not an IBM zSeries workstation?
http://www.garlic.com/~lynn/2001b.html#83 Z/90, S/390, 370/ESA (slightly off topic)
http://www.garlic.com/~lynn/2001d.html#69 Block oriented I/O over IP
http://www.garlic.com/~lynn/2001j.html#20 OT - Internet Explorer V6.0
http://www.garlic.com/~lynn/2001k.html#18 HP-UX will not be ported to Alpha (no surprise)exit
http://www.garlic.com/~lynn/2001k.html#19 HP Compaq merger, here we go again.
http://www.garlic.com/~lynn/2001k.html#46 3270 protocol
http://www.garlic.com/~lynn/2001m.html#15 departmental servers
http://www.garlic.com/~lynn/2001n.html#23 Alpha vs. Itanic: facts vs. FUD
http://www.garlic.com/~lynn/2001n.html#34 Hercules etc. IBM not just missing a great opportunity...
http://www.garlic.com/~lynn/2001n.html#55 9-track tapes (by the armful)
http://www.garlic.com/~lynn/2002.html#2 The demise of compaq
http://www.garlic.com/~lynn/2002.html#7 The demise of compaq
http://www.garlic.com/~lynn/2002.html#11 The demise of compaq
http://www.garlic.com/~lynn/2002b.html#4 Microcode? (& index searching)
http://www.garlic.com/~lynn/2002b.html#37 Poor Man's clustering idea
http://www.garlic.com/~lynn/2002d.html#4 IBM Mainframe at home
http://www.garlic.com/~lynn/2002d.html#14 Mainframers: Take back the light (spotlight, that is)
http://www.garlic.com/~lynn/2002e.html#2 IBM's "old" boss speaks (was "new")
http://www.garlic.com/~lynn/2002h.html#52 Bettman Archive in Trouble
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Latency benchmark (was HP Itanium2 benchmarks)
Newsgroups: comp.arch
Date: Mon, 22 Jul 2002 17:31:37 GMT
... i used to have something posted to the effect (re LRU degenerating
to FIFO) that when you can't make a good decision ... make a RANDOM
one.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Difference between Unix and Linux?
Newsgroups: alt.folklore.computers
Date: Thu, 25 Jul 2002 22:04:18 GMT
"Alan T. Bowler" writes:
Only some mainframe terminals ran in block mode.
Dumb ASCII async terminals were the usual choice
for timesharing use on non-IBM hardware.
i added tty/ascii support to cp/67 back when undergraduate in late
'60s. IBM picked up the code and shipped it in the product. it had a
sort of design glitch ... and later when somebody at MIT modified the
code ... it resulted in numerous kernel crashes that day.
they were supported in half-duplex mode by the (ibm) 2702 terminal
controller which recognized certain line-end characters and generated
interrupt to the processor when those characters were encountered.
at the university, we ran into some issues with the 2702 terminal
controller and a couple of us started a project where we built a
terminal controller starting with interdata/3 and reverse engineering
the ibm channel interface and building our own board to interface to
the ibm mainframe channel ... supposedly credited with originated the
ibm pcm controller business:
http://www.garlic.com/~lynn/subtopic.html#360pcm
the interdata/3 supported the tty terminals in full duplex and then
played some games mapping that to half-duplex for the 2702 controller
emulation. later, it was enhanced to be a combination of interdata/4
with interdata/3 dedicated to line-scanner function.
I believe the use of the interdata as termianl controller was then
expanded to other mainframes (not just ibm). Also, perkin/elmer
eventually bought it up ... and they were sold under the perkin/elmer
brand. I ran into one 5-6 years ago in major transaction processing
datacenter still handling heavy traffic load.
there was the "yale iup" for the series/1 in the '80s which also
provided full-duplex ascii support for tty terminals to aix/370 (aka
the port of ucla locus to 370 and ps/2 and released as ibm product).
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: HONE was .. Hercules and System/390 - do we need it?
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Thu, 25 Jul 2002 23:12:06 GMT
Anne & Lynn Wheeler writes:
this was when cms\apl was first created (port from phili's apl\360 to
cms environment and making available up to 16mbyte workspaces instead
of just 16k or 32k workspaces). there was an enhanced sense of
security when all the most valuable corporate data was loaded onto the
cambridge system so these guys could run their financial & business
analysis applications. eventually these guys got their own cp/67
systems down and new york. random past ref:
http://www.garlic.com/~lynn/2002h.html#34 Computers in Science Fiction
there is some line about people who don't read history are doomed to
repeat the same mistakes over & over again.
about every two years some executive in the HONE chain of command or
somewhere else in DPD would make some statment about HONE being hosted
on MVS platform. Possibly 20-30 percent of the HONE staff would be
sent off to port HONE to MVS platform. After 4-6 months it was be
deemed an utter and total failure ... and the porting effort would
quietly fade away. The problem being that it wasn't politically
correct to point out that it was a utter and total failure to try and
get something working on MVS. Since it wasn't politically correct to
document it ... the whole issue would crop up in another 18 months or
so and the exercise would get repeated.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: MITM solved by AES/CFB - am I missing something?!
Newsgroups: sci.crypt
Date: Fri, 26 Jul 2002 13:03:08 GMT
Sam Simpson writes:
Surely just running CFB isn't sufficient to solve the MITM attack - you
need certification or similar technology - right?
depends on what specific attacks you are talking about.
If the situation assumes that keys have been securely exchanged
... and that given a secure, encrypted channel using AES CFB ... then
can a MITM modify data in the transmission that goes undetected?
In a public key exchange ,,, can a MITM substitute their own public
key undetected?
In the case of a public key exchange with certificates ... can a MITM
create a situation where a valid certificate is substituted aka there
has been lots of discussion regarding how a MITM would go about
getting a valid, acceptable certificate ... say a SSL domain name
server certificate.
one of the most recent has been in crypto mailing list regarding
buying a root key that is currently acceptable to a majority of
browsers, try search engine on: SSL Certificate "Monopoly" Bears
Financial Fruit.
part of the issue is that while you might use certificates to a
current real time public key exchange ... there is some kind of chain
of trust going back to some procedure where you have accepted one or
more "root key" by some method ... and all subsequent trust decisions
you make involving certificates involve both the method by which you
accepted that "root key" ... and all subsequent operations that the
owner(s) of that root key might have been involved in ... as well as
the method you use to protect and secure your list(s) of acceptable
root keys.
things like PGP just eliminate the chain of trust ... they maintain a
(secure) list of trusted keys and they use some out of band process
for introducing keys into that list of trusted keys.
certificate infrastructures, in effect operate the same way .... but
you might not even be aware of what your list of trusted keys are
and/or what processes that were used to establish them and/or maintain
them. These trusted keys then are used by entities that you may have
no idea about to generate certificates (as opposed to directly signing
pieces of email) ... which you then accept on complete faith. part of
this is a possible myopic focus on the bit-stream that composes a
particular public key certificate ... ignoring the whole rest of the
business processes involved in creating the infrastructure for the
operation of public key certificates ... certificates don't actually
eliminate any of the MITM attacks on public key exchange ... they are
just moved around ... at the same time adding a whole bunch of new
attacks.
random refs:
http://www.garlic.com/~lynn/subpubkey.html#sslcerts
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Beginner question on Security
Newsgroups: sci.crypt
Date: Fri, 26 Jul 2002 13:13:51 GMT
jonath-k writes:
Please help me to correct my understanding if I am wrong here.
Security = Authentication + Integrity + Encryption
security typically is business process ... with business processes
like authentication, integrity, and privacy, confidentiality,
availability, etc.
encryption nominally isn't a business process .... it is a technology,
that might be used to address things like integrity and privacy
... aka encryption can be used to keep information private
... encryption can also be used to recognize whether data has been
modified in transit (aka integrity).
misc ref:
http://www.garlic.com/~lynn/secure.htm
from above
security
(1) The combination of confidentiality, integrity, and
availability. (2) The quality or state of being protected from
uncontrolled losses or effects. Note: Absolute security may in
practice be impossible to reach; thus the security 'quality' could be
relative. Within state models of security systems, security is a
specific 'state' that is to be preserved under various
operations. [AJP] (I) (1.) Measures taken to protect a system. (2.)
The condition of system that results from the establishment and
maintenance of measures to protect the system. (3.) The condition of
system resources being free from unauthorized access and from
unauthorized or accidental change, destruction, or loss. [RFC2828] A
condition that results from the establishment and maintenance of
protective measures that ensure a state of inviolability from hostile
acts or influences. [NSAINT] All aspects related to defining,
achieving, and maintaining confidentiality, integrity, availability,
accountability, authenticity, and reliability. NOTE - A product,
system, or service is considered to be secure to the extent that its
users can rely that it functions (or will function) in the intended
way. This is usually considered in the context of an assessment of
actual or perceived threats. [ISO/IEC WD 15443-1 (11/2001)] [SC27] The
combination of confidentiality, integrity, and availability. [FCv1]
The quality or state being protected from uncontrolled losses or
effects. Note: Absolute security may in practice be impossible to
reach; thus the security 'quality' could be relative. Within
state-models of security systems, security is a specific 'state', that
is to be preserved under various operations. [JTC1/SC27/N734]
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Beginner question on Security
Newsgroups: sci.crypt
Date: Fri, 26 Jul 2002 17:48:58 GMT
Anders Thulin writes:
When you want to try a larger chunk of the sum, go for the
Common Criteria at http://www.commoncriteria.org/.
i've somewhat viewed the orange book and related specifications as
being applied to generalized, multipurpose computers .... which runs
into all sorts of problems. some of the common criteria has been
defining very targeted security specifications for specific
environments and operations .... aka a firewall might be implemented
using a multipurpose computer but because of lots of mitigating and
compensating procedures a large amount of the generalized security
specification may not be applicable to its operation.
the previously references security glossary at
http://www.garlic.com/~lynn/secure.htm
is a merge of glossaries from:
Terms merged from: AFSEC, AJP, CC1, CC2, FCv1, FIPS140, IATF V3,
IEEE610, ITSEC, Intel, JTC1/SC27/N734, KeyAll, MSC, NCSC/TG004, NIAP,
NSA Intrustion, RFC1983, RFC2504, RFC2828, TCSEC, TDI, TNI, and
misc. Updated 20020505 with NSA Intrusion glossary. Updated 20020511
with latest ISO SC27 definitions.
(including both common criteria "1" and "2" ... aka CC1, CC2)
repeat of the definion
security
(1) The combination of confidentiality, integrity, and
availability. (2) The quality or state of being protected from
uncontrolled losses or effects. Note: Absolute security may in
practice be impossible to reach; thus the security 'quality' could be
relative. Within state models of security systems, security is a
specific 'state' that is to be preserved under various
operations. [AJP] (I) (1.) Measures taken to protect a system. (2.)
The condition of system that results from the establishment and
maintenance of measures to protect the system. (3.) The condition of
system resources being free from unauthorized access and from
unauthorized or accidental change, destruction, or loss. [RFC2828] A
condition that results from the establishment and maintenance of
protective measures that ensure a state of inviolability from hostile
acts or influences. [NSAINT] All aspects related to defining,
achieving, and maintaining confidentiality, integrity, availability,
accountability, authenticity, and reliability. NOTE - A product,
system, or service is considered to be secure to the extent that its
users can rely that it functions (or will function) in the intended
way. This is usually considered in the context of an assessment of
actual or perceived threats. [ISO/IEC WD 15443-1 (11/2001)] [SC27] The
combination of confidentiality, integrity, and availability. [FCv1]
The quality or state being protected from uncontrolled losses or
effects. Note: Absolute security may in practice be impossible to
reach; thus the security 'quality' could be relative. Within
state-models of security systems, security is a specific 'state', that
is to be preserved under various operations. [JTC1/SC27/N734]
but also including related terms (these terms are hypertect linked at
the above glossary)
(see also BLACK, Generic Security Services API, IT security policy, IT
security product, Kerberos, National Computer Security Center,
National Computer Security Center glossary, National Security Decision
Directive 145, RED, benign environment, classification level,
clearance level, computer security technical vulnerability reporting
program, concealment system, information flow control, lock-and-key
protection system, multi-level secure, national computer security
assessment program, need-to-know, network reference monitor, no-lone
zone, overwrite procedure, permissions, personal security environment,
print suppression, privacy, privileged process, restricted area,
sanitize, secure configuration management, secure envelope, secure
hash algorithm, secure hyper text transfer protocol, secure single
sign-on, secure sockets layer, secure subsystem, security authority,
security certificate, security element, security information object,
security information object class, security policy information file,
signed applet, system integrity, systems security steering group,
trusted computer system, accreditation)
(includes Advanced Mobile Phone Service, Asynchronous Transfer Mode,
Authentication Header, Automated Information System security,
Automated Security Incident Measurement, CONcept of Operations, Common
Criteria, Common IP Security Option, Computer Security Objects
Register, Cryptographic Application Program Interface, Data Encryption
Standard, DoD Information Technology Security Certification and
Accreditation Process, Generic Upper Layer Security, Internet Protocol
security, National Information Assurance partnership, PKIX private
extension, SOCKS, Simple Distributed Security Infrastructure, Simple
Public Key Infrastructure/Simple Distributed Security Infrastructure,
Standard Security Label, TEMPEST, TOE security functions, TOE security
policy, Target of Evaluation, access control, access control list,
accountability, add-on security, administrative security, adversary,
anonymity, anti-jam, application program interface, application-level
firewall, assurance, asymmetric cryptographic algorithm, attack,
audit, authentication, authorization, automated data processing
security, automated information system, automated security monitoring,
availability, baseline, binding of security functionality, biometrics,
call back, call back security, certificate, certificate revocation
list, certification and accreditation, certification authority,
challenge/response, checksum, closed security environment, code
division multiple access, common data security, common data security
architecture, common security, common security services manager,
communication and data security architecture, communications security,
compartmented security mode, compromise, compromised key list,
computer emergency response team, computer intrusion, computer
operations, audit, and security technology, computer security,
computer security incident response team, computer security object,
computer security subsystem, confidentiality, configuration
management, contingency plan, control zone, controlled security mode,
corporate security policy, correctness proof, countermeasures, covert
channel, credential, crypto-ignition key, crypto-security,
cryptographic functions, data security, dedicated security mode,
defense in depth, defense-wide information assurance program, denial
of service, designated approving authority, developer security,
digital certificate, digital signature, discretionary access control,
downgrade, dual control, eavesdropping, economy of mechanism,
effective key length, electronic key management system, email security
software, emanations security, emission security, encapsulating
security payload, evaluation assurance level, external security
controls, file security, formal security policy model, frequency
division multiple access, front-end security filter, future narrow
band digital terminal, global command and control system, global
information grid, global network information environment, guard,
hacker, hash, host-based security, identification, identification and
authentication, information assurance, information security,
information system security officer, information systems security,
information systems security engineering, information technology,
insider attack, integrity, internal security controls, internet
control message protocol, intrusion detection, intrusion detection
system, key, key management, key management infrastructure, layered
solution, local area network, mandatory access control, mission needs
statement, motivation, multi-level security, multi- level security
mode, multipurpose internet mail extensions, mutual suspicion,
mutually suspicious, national telecommunications and Information
Systems Security advisory memoranda/instructions, national
telecommunications and information system security directives, network
security, network security architecture, network security officer,
non-discretionary security, non-technical countermeasure, open
security, open security environment, open system interconnection
model, open systems security, operational data security, operational
integrity, operations security, organisational security policy,
parity, partitioned security mode, password, perimeter-based security,
personnel security, physical security, pretty good privacy, privacy,
authentication, identification, integrity, non-repudiation, privacy,
authentication, identification, non-repudiation, procedural security,
protection needs elicitation, protection profile, proxy, public-key
infrastructure, residual risk, risk, risk management, risk plane,
robustness, rule-based security policy, sanitization, secret key,
secure multipurpose internet mail extensions, secure network server,
secure profile inspector, secure state, security architecture,
security class, security clearance, security compromise, security
environment, security event, security features, security filter,
security flaw, security flow analysis, security function, security
gateway, security incident, security intrusion, security level,
security management infrastructure, security mechanism, security
model, security objective, security officer, security parameters
index, security perimeter, security policy, security protocol,
security safeguards, security service, security situation, security
software, security specifications, security target, security testing,
separation of duties, session key, signature [digital, electronic],
simple security property, social engineering, software security,
strength of mechanisms, subject security level, symmetric algorithm,
system integrity service, system security authorization agreement,
system security officer, system security policy, system-high security
mode, tamper, technical countermeasure, technical security policy,
technology gap, term rule-based security policy, threat, time division
multiple access, token, top-level security objectives, transmission
security, trojan horse, trusted computing base, trusted operating
system, tunneling router, usage security policy, user, virtual network
perimeter, virtual private network, virus, vulnerability, wide area
network, worm)
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Transportation
Newsgroups: alt.folklore.computers
Date: Fri, 26 Jul 2002 19:56:35 GMT
"Rupert Pigott" <dark.try-eating-this.b00ng@btinternet.com> writes:
I don't want to stick up for Amtrak, god knows I don't, but I looking
after crumbling railway infrastructure ain't cheap. :)
part of the issue is the trucking infrastructure is heavily subsidized
just thru the road system .... aka nearly all the road infrastructure
costs are related to heavy trucking. the building of the original
railroad infrastructure was heavily subsidized by the large land
grants ... but that has essentially been pretty well bleed off over
the years. The issue now is the day-to-day operational revenues
vis-a-vis day-to-day operational & infrastructure costs (trucks
vis-a-vis railroads).
As a starting assumption that nearly all the road infrastructure costs
(original build, ongoing maint., etc) are almost totally heavy
trucking related ... then it would be logical(?) to start with all
fuel taxes supporting road systems be only applicable to heavy trucks
... in effect all the current fuel tax income currently spread across
the whole driving population but recovered solely from heavy trucking
activity).
I have no idea what the current percentage of total fuel consumption
is by heavy trucking ... just for argument sake lets assume three
percent. With fuel tax running around 40 cents (federal + state), then
if this was to be totally recovered by heavy trucking fuel consumption
... it would need to be raised by a factor of thirty to around twelve
dollars per gallon.
misc ref on fuel tax:
http://www.taxadmin.org/fta/rate/motor_fl.html
misc road construction ref:
http://www.dot.ca.gov/hq/oppd/hdm/chapters/t603.htm#i603-2
603.1 Introduction
The primary goal of the design of the pavement structural section is
to provide a structurally stable and durable pavement and base system
which, with a minimum of maintenance, will carry the projected traffic
loading for the designated design period. This topic discusses the
factors to be considered and procedures to be followed in developing a
projection of truck traffic for design of the "pavement structure" or
the structural section for specific projects.
Pavement structural sections are designed to carry the projected truck
traffic considering the expanded truck traffic volume, mix, and the
axle loads converted to 80 kN equivalent single axle loads (ESAL's)
expected to occur during the design period. The effects on pavement
life of passenger cars, pickups, and two-axle trucks are considered to
be negligible.
Traffic information that is required for structural section design
includes axle loads, axle configurations, and number of
applications. The results of the AASHO Road Test (performed in the
early 1960's in Illinois) have shown that the damaging effect of the
passage of an axle load can be represented by a number of 80 kN
ESAL's. For example, one application of a 53 kN single axle load was
found to cause damage equal to an application of approximately 0.23 of
an 80 kN single axle load, and four applications of a 53 kN single
axle were found to cause the same damage (or reduction in
serviceability) as one application of an 80 kN single axle.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Transportation
Newsgroups: alt.folklore.computers
Date: Fri, 26 Jul 2002 20:30:47 GMT
Anne & Lynn Wheeler writes:
misc road construction ref:
http://www.dot.ca.gov/hq/oppd/hdm/chapters/t603.htm#i603-2
603.1 Introduction
oops, the above html is gone missing (I had the url sitting around
from some time ago).
the new/current web page for the caltrans highway design manual
http://www.dot.ca.gov/hq/oppd/hdm/hdmtoc.htm
and it does point at a (large, 750kbyte) pdf file that is online.
http://www.dot.ca.gov/hq/oppd/hdm/pdf/chp0600.pdf
a little picking around and found html file online
http://www.dot.ca.gov/hq/oppd/hdm/c600.htm
but missing a lot of drawings found in the pdf version.
note the above also has section (606) that covers some of the issues
of things like frost heaves.
old roads postings:
http://www.garlic.com/~lynn/99.html#21 Roads as Runways Was: Re: BA Solves Y2K (Was: Re: Chinese Solve Y2K)
http://www.garlic.com/~lynn/99.html#22 Roads as Runways Was: Re: BA Solves Y2K (Was: Re: Chinese Solve Y2K)
http://www.garlic.com/~lynn/99.html#23 Roads as Runways Was: Re: BA Solves Y2K (Was: Re: Chinese Solve Y2K)
http://www.garlic.com/~lynn/99.html#27 Roads as Runways Was: Re: BA Solves Y2K (Was: Re: Chinese
http://www.garlic.com/~lynn/99.html#32 Roads as Runways Was: Re: BA Solve
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Killer Hard Drives - Shrapnel?
Newsgroups: alt.folklore.computers
Date: Sat, 27 Jul 2002 15:37:02 GMT
ab528@FreeNet.Carleton.CA (Heinz W. Wiggeshoff) writes:
Starting with artillery tables, it's hard to decide which general
area of engineering has taken up more CPU time within the realm of
a.f.c (i.e. 20 years ago). I believe it was McDonnell Douglas that
unloaded 6 high end IBM 91 or 95 or 195s in the early 70's at a time
that I was still mightily impressed with the 85. I guess that old
Nastran code could really crunch through the CPU cycles.
slightly related
http://www.garlic.com/~lynn/2000f.html#13 Airspeed Semantics, was: not quite an sr-71, was: Re: jet in IBM ad?
http://www.garlic.com/~lynn/subtopic.html#boyd
when i did stint at boeing for the BCS (boeing computing
system/services) startup (was one of the first couple dozen employees)
... renton had a really large datacenter ... joke about there
constantly being 2-3 360/65s boxed in the hallways waiting staging for
installation on the machine room floor.
for disaster recovery purposes, all of renton data center was later
duplicated in everett (one of the scenarios is mud-slide down the
nearby mountain; which they take seriously ... some of the small towns
nearer the mountain have sirens and drills).
one story they told is that the day after the 360 announcement
... boeing walked into their local salesman and placed an initial
order for something like twenty 360/65s (actually would have been
360/60s on announcement day). his commission exceeded the top
executive salary that year ... and as a result the next year corporate
hdqtrs created the quota plan (rather than straight commission). That
year, his commission also exceeded the top xecutive salary ... and
they up'ed his quota again. He then left and formed his own computer
consulting and services company (which much later got bought by GM,
and then he formed a new computer consulting and services company and
also ran for president).
random refs:
http://www.garlic.com/~lynn/99.html#32 Roads as Runways Was: Re: BA Solve
http://www.garlic.com/~lynn/99.html#130 early hardware
http://www.garlic.com/~lynn/2000f.html#66 360 Architecture, Multics, ... was (Re: X86 ultimate CISC? No.)
http://www.garlic.com/~lynn/2001b.html#8 "HAL's Legacy and the Vision of 2001: A Space Odyssey"
http://www.garlic.com/~lynn/2001b.html#9 "HAL's Legacy and the Vision of 2001: A Space Odyssey"
http://www.garlic.com/~lynn/2001b.html#23 Linux IA-64 interrupts [was Re: Itanium benchmarks ...]
http://www.garlic.com/~lynn/2001g.html#56 YKYBHTLW....
http://www.garlic.com/~lynn/2001m.html#55 TSS/360
http://www.garlic.com/~lynn/2002f.html#30 Computers in Science Fiction
http://www.garlic.com/~lynn/2002j.html#22 Computer Terminal Design Over the Years
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Funeral for a friend - Infiniband
Newsgroups: comp.arch
Date: Sat, 27 Jul 2002 15:45:26 GMT
rpw3@rigden.engr.sgi.com (Rob Warnock) writes:
Hardly. Look for Winsock Direct and friends (Sockets Direct, iWarp,
whatever) to start making noises about running (probably assuming
hardware "TCP/IP offload" support) on good ol' Ethernet...
its been 15 years or so since some SGI engineers were looking at
applying graphics engine pipelining to protocol engine for TCP/IP FDDI
offload (when FDDI was the only 100mbit/sec around, excluding multiple
parallel 50mbyte HYPERChannel).
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: M$ SMP and old time IBM's LCMP
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Mon, 29 Jul 2002 14:29:36 GMT
jfregus@ix.netcom.com (John F. Regus) writes:
Does Microsoft's Symetrical Multi Processing seem like IBM's 1970's Loosely Coupled Multi Processing?
my wife did a stint in POK responsible for loosely-coupled
architecture. while there she authored peer-coupled shared data
architecture ... which didn't see much use until sysplex, except for
possibly ims hot-standby.
at about the same time, HONE was centralizing and creating what I
believe was the largest single system complex in the world
... clusters of SMP.
http://www.garlic.com/~lynn/subtopic.html#hone
later we did an internal high-speed backbone and did some NSFNET
related work ... as well as HA/CMP and involved in both FCS and SCI
standards.
http://www.garlic.com/~lynn/95.html#13 SSA
http://www.garlic.com/~lynn/subtopic.html#hacmp
part of the reason was we were looking for scalable support and none
of the rios chips had support for consistent shared memory ... and the
power/pc with shared memory support was still years away (at the time
we started on high-availability/cluster multiprocessing in the late
'80s).
and then after both taking an early out in '92 ... spent some time
talking to sequent, convex, and tandem. both sequent and tandem
claimed to have done significant (shared-memory) parallization work on
the NT kernel in the early to mid 90s.
sequent had a snoopy bus with intel processors that went to 32-way
... but I believe those configurations were primarily supported by
dynix (sequent's unix) ... i believe the NT work was primarily on
4-way to 8-way processor shared memory configurations.
side note ... if anybody remembers the netscape downloads of the
mid-90s ... they had multiple large servers netscape1, netscape2,
netscape3, ... and it was suggested that people sort of randomly try
different nodes looking for lightest loaded. they eventually installed
a large sequent configuration as netscape20 ... and the problem sort
of just evaporated (as did most of the multiple servers). at the time,
sequent dynix had possibly the best scaling tcp/ip support around (at
least in terms of supporting large number of concurrent sessions, they
were also one of the first to have scalable solution to the dnagling
finwait opportunity; at the time there were some situations where
processors were spending >90percent of the cpu running the dangling
finwait list).
sequent and data general both did 256-way intel using SCI
... basically 4-way intel quad-board sharing local cache and 64-port
SCI configuration implementing 256-way global shared memory (sequent
took relatively standard intel 4-way SMP quad-boards and did the work
to make it work with 64-port SCI).
note that there are both lcmp clusters and shared-nothing clusters.
lcmp clusters typically have shared-access to disk (while not having
shared-memory). shared-nothing clusters (like wolfpack) rely on
network message passing ... to implement things like replicated data.
press release from 10/12/95 (remember AT&T was also NCR)
Companies Voice Support for Microsoft Clustering Strategy
AT&T Global Information Solutions welcomes the opportunity to
participate in providing customers with an industry standard for
clustering technology. AT&T has years of experience in delivering
clustering and fault-resilient technology with AT&T(R)
LifeKeeper. Through our collaboration with Microsoft, we plan to
protect and enhance our customers' investment in Windows NT Server
solutions from AT&T, and to continue to deliver superior
high-availability solutions that drive and utilize future
industry-standard clustering technology for Windows NT Server.`
extract from 8/96
http://www.winntmag.com/issues/Aug96/wolfpack.htm
What Is Wolfpack?
Several leading NT Server systems vendors, including Compaq, Digital
Equipment, HP, NCR, and Tandem, have been independently working on
clustering solutions for a few years. These vendors agreed to pool their
expertise with Microsoft in an initiative to produce a cross-vendor standard
for NT Server clusters. This group wanted to give NT Server customers the
greater choice and flexibility they wanted. So in October 1995, Microsoft
announced its intent to develop strategic partnerships to fashion a new
clustering standard with the code name Wolfpack.
This name and many of its technology goals derive from Pfister's book. In
Chapter 4, Pfister describes a cluster as a "pack of dogs." While searching
for a code name for the API, Microsoft came across this book and decided to
describe clusters with the name Wolfpack, which sounds a lot cooler than
Dogpack.
Wolfpack is an alias for clusters, and the six core vendors in Microsoft's
clustering project consider themselves members of the Wolfpack. These
members are Digital, Compaq, Tandem, Intel, HP, and NCR. Each partner
contributes key components of its existing technology. Other vendors,
including Amdahl, IBM, Octopus, Vinca, Marathon, Stratus, and Cheyenne, have
agreed to support the Wolfpack API. These vendors are part of Microsoft's
Open Process, which includes about 60 vendors and customers who are part of
design previews during various stages of Wolfpack development.
Wolfpack describes a set of cluster-aware APIs, NT cluster support, and a
clustering solution (which means a vendor can claim to be Wolfpack compliant
while competing with the Wolfpack solution on a different level--so if a
vendor claims to support Wolfpack, you need to ask how). Here's a detailed
explanation of each Wolfpack component.
<snip>
misc m'soft refs:
http://www.microsoft.com/WINDOWS2000/hpc/dsmperpec.asp
http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/windows2000serv/reskit/serverop/part2/sopch10.asp
random sci refs:
http://www.garlic.com/~lynn/96.html#8 Why Do Mainframes Exist ???
http://www.garlic.com/~lynn/96.html#25 SGI O2 and Origin system announcements
http://www.garlic.com/~lynn/98.html#40 Comparison Cluster vs SMP?
http://www.garlic.com/~lynn/2001b.html#39 John Mashey's greatest hits
http://www.garlic.com/~lynn/2001b.html#85 what makes a cpu fast
http://www.garlic.com/~lynn/2001f.html#11 Climate, US, Japan & supers query
http://www.garlic.com/~lynn/2001j.html#12 OT - Internet Explorer V6.0
http://www.garlic.com/~lynn/2001j.html#17 I hate Compaq
http://www.garlic.com/~lynn/2001l.html#16 Disappointed
http://www.garlic.com/~lynn/2002g.html#10 "Soul of a New Machine" Computer?
http://www.garlic.com/~lynn/2002h.html#78 Q: Is there any interest for vintage Byte Magazines from 1983
http://www.garlic.com/~lynn/2002i.html#83 HONE
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
Refed: **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: M$ SMP and old time IBM's LCMP
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Mon, 29 Jul 2002 14:49:01 GMT
Anne & Lynn Wheeler writes:
note that there are both lcmp clusters and shared-nothing clusters.
lcmp clusters typically have shared-access to disk (while not having
shared-memory). shared-nothing clusters (like wolfpack) rely on
network message passing ... to implement things like replicated data.
oops, pack of dogs ... is shared nothing with message
passing. wolfpack supports shared disk.
also from
http://www.winntmag.com/issues/Aug96/wolfpack.htm
Wolfpack: The Solution
Microsoft will deliver Wolfpack, the solution, in two phases.
Phase 1 is two-node availability and scaling clusters (a new version of SQL
Server will let you work on the same database from two servers at once).
Phase 2 will allow more than two nodes in a cluster.
Reread the first paragraph in this article. That scenario describes a June
1996 demonstration of a Wolfpack availability cluster solution at PC Expo in
New York City. This two-node failover capability is the basis for Phase 1 of
Wolfpack (early 1997 is the estimate for delivery). The price for Wolfpack's
Phase 1 release is not set, but one rumor is that NT Server will include
Wolfpack at no additional cost. As I write this article, Compaq, Digital,
HP, NCR, Amdahl, Stratus, and Tandem have all announced plans to OEM the
Wolfpack-based cluster solution.
The next step in Phase 1 (set for the second quarter of 1997) will be an
open certification program with the goal of expanding the market for
two-node cluster solutions and giving NT Server customers a greater
selection to choose from. Microsoft is also committed to making Wolfpack
available on Intel, Alpha, PowerPC, and MIPS chips.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: M$ SMP and old time IBM's LCMP
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Mon, 29 Jul 2002 20:14:34 GMT
"Rupert Pigott" <dark.try-eating-this.b00ng@btinternet.com> writes:
The wierd thing is : It all seemed to go very quiet after phase 1
(ie: basic fail-over). I was wondering if they renamed it or just
silently dropped it.
Stuff like Longhorn can't really help it much either (if you
believe that Bill is not implementation on backward compatability).
i thot that the microsoft terabyte satellite image internet server was
some sort of shared-disk clustering.
the big new thing in clustering seems to be the grid stuff that the
high-energy physics guys seemed to have started ... it was all over
supercomputer 2002 in denver at the start of the year ... and now
"grid" seems to be the new, in term.
--
Anne & Lynn Wheeler | lynn@garlic.com - http://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: SHARE Planning
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Mon, 29 Jul 2002 22:03:53 GMT
jmaynard@CONMICRO.CX (Jay Maynard) writes:
Assuming I can get from the airport to my hotel, t