List of Archived Posts

2002 Newsgroup Postings (04/06 - 04/27)

Computers in Science Fiction
Blade architectures
Increased Paging in 64-bit
Increased Paging in 64-bit
Blade architectures
Blade architectures
Blade architectures
Blade architectures
Is AMD doing an Intel?
PKI / CA -- Public Key & Private Key
Least folklorish period in computing (was Re: IBM Mainframe at home)
Blade architectures
looking for information on the IBM 7090 instruction set
Hardware glitches, designed in and otherwise
Mail system scalability (Was: Re: Itanium troubles)
Mail system scalability (Was: Re: Itanium troubles)
Blade architectures
Blade architectures
Mail system scalability (Was: Re: Itanium troubles)
When will IBM buy Sun?
Blade architectures
When will IBM buy Sun?
Biometric Encryption: the solution for network intruders?
Computers in Science Fiction
Computers in Science Fiction
When will IBM buy Sun?
Blade architectures
Security Issues of using Internet Banking
Security Issues of using Internet Banking
Computers in Science Fiction
Computers in Science Fiction
Security and e-commerce
Biometric Encryption: the solution for network intruders?
Security and e-commerce
Security and e-commerce
Security and e-commerce
Blade architectures
Playing Cards was Re: looking for information on the IBM 7090
Playing Cards was Re: looking for information on the IBM
Playing Cards was Re: looking for information on the IBM
e-commerce future
Blade architectures
Blade architectures
Foreign Cars (was: Computers in Science Fiction)
Blade architectures
Biometric Encryption: the solution for network intruders?
Security Issues of using Internet Banking
How Long have you worked with MF's ? (poll)
How Long have you worked with MF's ? (poll)
Blade architectures
Blade architectures
markup vs wysiwyg (was: Re: learning how to use a computer)
Mainframes and "mini-computers"
WATFOR's Silver Anniversary
WATFOR's Silver Anniversary
Security Issues of using Internet Banking
crypto processor activity
IBM competes with Sun w/new Chips
Security Issues of using Internet Banking
Blade architectures
Mainframes and "mini-computers"

Computers in Science Fiction

Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Computers in Science Fiction
Newsgroups: alt.folklore.computers
Date: Sun, 07 Apr 2002 06:38:45 GMT

jmfbahciv writes:

Sure.  They didn't need to buy five systems to service 10,000
accounts.  And don't underestimate one mainframe on site.
In the late 70s or early 80s, a study was done at DEC.  I

more drift ... from a 1988 IDC report:

              VAX INVENTORY
              -------------

SYSTEM       US       NON-US    TOTAL
--------- --------- --------- ---------
11/725         950       550     1,500
11/730       4,100     2,950     7,050
11/750      12,230     9,370    21,600
11/780      14,280     9,660    23,940
11/782         190       120       310
11/785       2,460     1,590     4,050
MVI          1,840       960     2,800
MVII        41,000    23,900    64,900
82XX         2,800     1,870     4,670
83XX           900       600     1,500
85XX         1,200       905     2,105
86XX         2,360     1,240     3,600
8700           400       270       670
8800           300       200       500
           --------  --------  --------
TOTAL       85,010    54,185   139,195

                 VAX SHIPMENTS
                 -------------
                                           NO. OF VAX
YEAR         US       NON-US    TOTAL    MODELS SHIPPED
--------- --------- --------- ---------  --------------
 1978          312        78       390          1
 1979          627       313       940          1
 1980        1,512     1,038     2,550          2
 1981        1,979     1,726     3,705          2
 1982        4,129     2,794     6,923          4
 1983        6,178     4,384    10,562          5
 1984       11,703     8,227    19,930          7
 1985       17,600     7,300    24,900          8
 1986       19,190    12,840    32,030         12
 1987       21,780    15,485    37,265         12
           --------  --------  --------
TOTAL       85,010    54,185   139,195

                 VAX SHIPMENTS - NON US
                 ----------------------

             1978-
SYSTEM       1984      1985      1986      1987     TOTAL
--------   --------  --------  --------  --------  --------
11/725         450       100         0         0       550
11/730       2,350       600         0         0     2,950
11/750       7,040     1,700       430       200     9,370
11/780       7,700     1,500       270       190     9,660
11/782         120         0         0         0       190
11/785          40     1,100       350       100     1,590
MVI            860       100         0         0       960
MVII             0     1,900    10,000    12,000    23,900
82XX             0         0       725     1,145     1,870
83XX             0         0       200       400       600
85XX             0         0       305       600       905
86XX             0       300       470       470     1,240
8700             0         0        60       210       270
8800             0         0        30       170       200
           --------  --------  --------  --------  --------
TOTAL       18,560     7,300    12,840    15,485    54,185

                        VAX SHIPMENTS - US
                        ------------------
             1978-
SYSTEM       1984      1985      1986      1987     TOTAL
--------   --------  --------  --------  --------  --------
11/725         650       300         0         0       950
11/730       3,200       900         0         0     4,100
11/750       9,300     2,200       560       170    12,230
11/780      11,500     2,200       400       180    14,280
11/782         190         0         0         0       190
11/785         260     1,600       500       100     2,460
MVI          1,340       500         0         0     1,840
MVII             0     9,000    15,000    17,000    41,000
82XX             0         0     1,150     1,650     2,800
83XX             0         0       300       600       900
85XX             0         0       420       780     1,200
86XX             0       900       730       730     2,360
8700             0         0        80       320       400
8800             0         0        50       250       300
           --------  --------  --------  --------  --------
TOTAL       26,440    17,600    19,190    21,780    85,010

                 VAX SHIPMENTS - WORLD-WIDE
                 --------------------------
             1978-
SYSTEM       1984      1985      1986      1987     TOTAL
--------   --------  --------  --------  --------  --------
11/725       1,100       400         0         0     1,500
11/730       5,550     1,500         0         0     7,050
11/750      16,340     3,900       990       370    21,600
11/780      19,200     3,700       670       370    23,940
11/782         310         0         0         0       310
11/785         300     2,700       850       200     4,050
MVI          2,200       600         0         0     2,800
MVII             0    10,900    25,000    29,000    64,900
82XX             0         0     1,875     2,795     4,670
83XX             0         0       500     1,000     1,500
85XX             0         0       725     1,380     2,105
86XX             0     1,200     1,200     1,200     3,600
8700             0         0       140       530       640
8800             0         0        80       420       500
           --------  --------  --------  --------  --------
TOTAL       45,000    24,900    32,030    37,265   139,195

... also 1988

 6,500 clusters installed, From 14,000 DEC VAX sites:

Percentage of VAX processors clustered

15% - 1985
21% - 1986
26% - 1987

--
Anne & Lynn Wheeler   | lynn@garlic.com -  http://www.garlic.com/~lynn/

Blade architectures

Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Blade architectures
Newsgroups: comp.os.vms,comp.arch,alt.folklore.computers
Date: Sun, 07 Apr 2002 19:42:22 GMT

Anne & Lynn Wheeler writes:

The DBMS vendors that used/supported the HA/CMP DLM had description
and it was fairly straight-forward stuff. I believe that these same
DBMS vendors had been making the same suggestions for a number of
years to the original makers.

slightly related from 80s (vax thread drift in a.f.c.):
http://www.garlic.com/~lynn/2002e.html#74 Computers in Science Fiction
http://www.garlic.com/~lynn/2002e.html#75 Computers in Science Fiction
http://www.garlic.com/~lynn/2002f.html#0  Computers in Science Fiction

various quotes/pieces from dec professional 1/88, pg 44, "OLTP on the
VAXcluster" (i started work on HA/CMP DLM prototype not too long
later):

Digital offers the VAXcluster as an easily managed computing
environment that gives incremental expandability, extensive and
flexible resource sharing, highly available resources, extensive data
storage flexible configurations and support for balanced interactive
workloads.  However, the cluster's Distributed Lock Manager introduces
overhead that can make this environment unsuitable for high-volume
transaction processing.  It is possible for application software (and
I assume that Sybase incorporated these ideas into their database) to
eliminate this overhead penalty and permit the successful
implementation of OLTP applications on the VAXcluster.

1.  The  benefit of expandability, however, is offset substantially by
    the overhead imposed by the cluster itself.

2.  Lock management may be as much as 20% for each  processor  in  the
    cluster,  reducing the actual throughput achieved to approximately
    80% for each additional cluster member.

3.  One RDBMS vendor (Sybase?) estimates that the VAXCLUSTER software,
    using the Lock Manager for all remote locks in a two-CPU  cluster,
    might achieve a throughput gain of 1.8 for a select (READ?) trans-
    action  and only 1.3 for a short update transaction over that of a
    single CPU.

4.  Lock management also makes recovery unacceptably lengthy  for  ap-
    plications requiring high system availability.

    When  a cluster node fails, processors on all nodes stop until the
    VMS connection manager re-establishes a quorum.   Then,  the  Dis-
    tributed  Lock  Manager  must release all locks held by the failed
    process, re-establish the Resource Manager for all resources  held
    by  the  failed  processor,  and re-establish the local and remote
    lock databases for each resource in use at the time of  the  fail-
    ure.  While this activity is in progress, all nodes in the cluster
    are unavailable

    Recovery  time  for  the  cluster is proportional to the number of
    locks in use and may take 5 to 8 minutes or longer.

Because the Lock Manager is responsible for these drawbacks,
application software that reduces its overhead is required to provide
an environment for OLTP.

A DBMS that can run as a efficient database machine on one processor
in a cluster can eliminate a great deal of overhead.  This requires a
requester/server architecture:

   The server must run as a single process on a  dedicated  processor
    with  its  own memory management and memory resident locking mech-
    anism,

   The server must manage data for all users with one dedicated image
    and one shared data cache so hundreds of users can be  handled  in
    4-6 Mbytes of storage,

   The applications would run on other processors.

The requester/server architecture in a VAX cluster has the following
benefits:

   A server running as  a  single  process  doesn't  require  context
    switching,

   Its own memory management eliminates page faults,

   A shared data cache minimizes disk I/O

   Because  all  data is managed by a single server on one processor,
    locking can be handled simply by reading  and  updating  a  memory
    resident  table.    Memory resident lock management eliminates the
    VMS locks that the Lock Manager establishes for concurrent users.

--
Anne & Lynn Wheeler   | lynn@garlic.com -  http://www.garlic.com/~lynn/

Increased Paging in 64-bit

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Increased Paging in 64-bit
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Mon, 08 Apr 2002 04:06:43 GMT

aw288@OSFN.ORG (William Donzelli) writes:

"Junk? JUNK!?"

I have to get in touch with these people to catch some of these old boxes
they are replacing. You would not want to go to the computer
museums, loaded with DEC stuff, and walk away with the idea that a KL10
was the ultimate big computer...now would you?

random online refs:
http://www.geocities.com/SiliconValley/Lakes/5705/1401.html The IBM 1401
http://www.beagle-ears.com/lars/engineer/comphist/ Computer History
http://www.beagle-ears.com/lars/engineer/comphist/ibmmodel.txt
http://www.cbi.umn.edu/collections/inv/corpman.htm Computer Product Manuals Collection

--
Anne & Lynn Wheeler   | lynn@garlic.com -  http://www.garlic.com/~lynn/

Increased Paging in 64-bit

Refed: **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Increased Paging in 64-bit
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Mon, 08 Apr 2002 15:18:38 GMT

Rick.Fochtman@BOTCC.COM (Rick Fochtman) writes:

If you'd ever seen one working, you'd immediately understand how it got that name.  I don't think that even Rube Goldberg could have dreamed it up.  <G>

(I suspect that the tape in the 3851 cartridges was the same as that used for the 'noodles' in the 2321.)

there was also the aspect of a washing machine as the drum rotated and placed
different cartridges under the picker. there was also the crumbling problem
if the gap didn't open correctly trying to stuff a strip back into the cartridge
it sort of did a fan-fold crumple.

note also that the 2321 was responsible for the BB in BBCCHHR
seek/search argument ... i.e. the BB rotated the 2321 washing machine
to place the correct bin/cartridge under the picker.

random refs:
http://www.garlic.com/~lynn/2000.html#9 Computer of the century
http://www.garlic.com/~lynn/2000b.html#41 How to learn assembler language for OS/390 ?
http://www.garlic.com/~lynn/2001.html#17 IBM 1142 reader/punch (Re: First video terminal?)
http://www.garlic.com/~lynn/2001.html#51 Competitors to SABRE?
http://www.garlic.com/~lynn/2001l.html#63 MVS History (all parts)
http://www.garlic.com/~lynn/2002.html#16 index searching
http://www.garlic.com/~lynn/2002.html#22 index searching

--
Anne & Lynn Wheeler   | lynn@garlic.com -  http://www.garlic.com/~lynn/

Blade architectures

Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Blade architectures
Newsgroups: comp.os.vms,comp.arch,alt.folklore.computers
Date: Mon, 08 Apr 2002 22:23:31 GMT

KeithParris_NOSPAM@yahoo.com (Keith Parris) writes:

But of course such an approach runs the risk of poor scalability when
the "single server on one processor" becomes a bottleneck for the
entire cluster, and its node-dependent approach falls short when it
comes to dealing gracefully with a node failure.

Interestingly, starting with VMS version 7.3, a system manager has the
option of running the VMS Lock Manager on a dedicated CPU within an
SMP system if they wish.

as mentioned (and one of the reasons a.f.c. was added) was this was
from dec professional 1/88 ... circa about VMS version 5.0. It was
respect to earlier thread about original input from some of the DBMS
vendors regarding "what was wrong" in VMS DLM ... and requirements for
HA/CMP DLM as to what needed to be different. As referenced in earlier
threads, it was assumed that VMS got better over the last 15 years.

as part of the HA/CMP effort we coined the term disaster
survivability to distinquish from disaster/recovery and ability to
survive local problems (aka as hardware & software reliability got
better, larger percentage of outages were from 1) various kinds of
local disasters and 2) human mistakes).

at the time we were doing HA/CMP ... we also got a chance to author
part of the corporate continuous availability strategy document
... but the section got pulled because of non-concurrance by POK and
Rochester.

one of the earlier (mainframe) efforts to expand from local clusters
was an internal online service that supported all the sales and field
service people located in silicon valley ... it was eventually
replicated in Dallas and Boulder in the late '70s (in part because of
seismic event concerns).
http://www.garlic.com/~lynn/98.html#23 Fear of Multiprocessing?
http://www.garlic.com/~lynn/2000c.html#30 internal corporate network, misc.
http://www.garlic.com/~lynn/2000g.html#27 Could CDR-coding be on the way back?
http://www.garlic.com/~lynn/2001.html#26 Disk caching and file systems.  Disk history...people forget
http://www.garlic.com/~lynn/2001.html#36 Where do the filesystem and RAID system belong?
http://www.garlic.com/~lynn/2001g.html#46 The Alpha/IA64 Hybrid
http://www.garlic.com/~lynn/2001i.html#43 Withdrawal Announcement 901-218 - No More 'small machines'
http://www.garlic.com/~lynn/2002c.html#30 OS Workloads : Interactive etc
http://www.garlic.com/~lynn/2002c.html#39 VAX, M68K complex instructions (was Re: Did Intel Bite Off More Than It Can Chew?)
http://www.garlic.com/~lynn/subtopic.html#hone

random refs:
http://www.garlic.com/~lynn/98.html#23 Fear of Multiprocessing?
http://www.garlic.com/~lynn/99.html#71 High Availabilty on S/390
http://www.garlic.com/~lynn/99.html#128 Examples of non-relational databases
http://www.garlic.com/~lynn/99.html#145 Q: S/390 on PowerPC?
http://www.garlic.com/~lynn/99.html#184 Clustering systems
http://www.garlic.com/~lynn/aadsm9.htm#pkcs12 A PKI Question: PKCS11-> PKCS12
http://www.garlic.com/~lynn/aepay2.htm#cadis disaster recovery cross-posting
http://www.garlic.com/~lynn/2000g.html#27 Could CDR-coding be on the way back?
http://www.garlic.com/~lynn/2001.html#33 Where do the filesystem and RAID system belong?
http://www.garlic.com/~lynn/2001.html#41 Where do the filesystem and RAID system belong?
http://www.garlic.com/~lynn/2001g.html#46 The Alpha/IA64 Hybrid
http://www.garlic.com/~lynn/2001i.html#41 Withdrawal Announcement 901-218 - No More 'small machines'
http://www.garlic.com/~lynn/2001i.html#43 Withdrawal Announcement 901-218 - No More 'small machines'
http://www.garlic.com/~lynn/2001i.html#48 Withdrawal Announcement 901-218 - No More 'small machines'
http://www.garlic.com/~lynn/2001i.html#49 Withdrawal Announcement 901-218 - No More 'small machines'
http://www.garlic.com/~lynn/2001j.html#23 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/2001n.html#47 Sysplex Info
http://www.garlic.com/~lynn/2002.html#44 Calculating a Gigalapse
http://www.garlic.com/~lynn/2002c.html#39 VAX, M68K complex instructions (was Re: Did Intel Bite Off More Than It Can Chew?)
http://www.garlic.com/~lynn/2002e.html#67 Blade architectures
http://www.garlic.com/~lynn/2002e.html#68 Blade architectures

--
Anne & Lynn Wheeler   | lynn@garlic.com, http://www.garlic.com/~lynn/

Blade architectures

Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Blade architectures
Newsgroups: comp.os.vms,comp.arch,alt.folklore.computers
Date: Mon, 08 Apr 2002 22:58:28 GMT

Anne & Lynn Wheeler writes:

as mentioned (and one of the reasons a.f.c. was added) was this was
from dec professional 1/88 ... circa about VMS version 5.0. It was

another '88 vax/vms tidbit ... the previous were
http://www.garlic.com/~lynn/2002f.html#0 ... vax machines shipped thru '88
http://www.garlic.com/~lynn/2002f.html#1 ... vms cluster DLM discussion

VMS SOFTWARE DEVELOPMENT
________________________

DEC description so that customers could understand the operating
system software development process inside Digital Equipment.

The planning function provides focus for:

 Strategy - defined with development and management and accepted by
  the corporation after assigned "consultants" concur that is meshes
  with overall corporate strategy
 Vision - as defined by programs (see below)
 Requirements - as segmented into programs (see below)

Programs are defined as:

 an  area  of focus that may cross organizational boundaries
 includes requirements that look 2 to 5 years ahead
 VMS has 8 programs and 5 engineering groups, including:
  -   production systems (OLTP)
  -   desktop systems
 each driven by a team that includes:
  -   product management to look after  customer  requirements
  -   VMS  engineering to look at feasibility and internal requirements
 reviewed by planning and management of the 5 engineering groups
 a vision is developed by upper management (addresses why a program
  is selected)

If a program is approved, it becomes a project.  Line development
managers develop a project plan based on the program requirements.
The 5 VMS development line managers involved are:

 network and clusters
 system resources (RMS, etc.)
 low end systems
 high end systems
 system management.

Project plans are reviewed and a functional specification is written.
The first pass of release planning is also done by the project
managers.  Milestones and end dates for 30 to 50 project plans are
prioritized.  When the functional specification is completed the
content of a release of VMS is defined.

There are multiple versions (threads) of VMS in existence at any point
in time. VMS, as a project, includes:

 400 engineers that are geographically split
 8 concurrent development threads in parallel, including:
  - maintenance release
  - functional release
  - hardware support (for newly developed hardware)
  - layered software support
 9000 modules
 400 MB of source code, including:
  - a 2 volume RA81 Shadow Set
  - 36% BLISS
  - 31% Macro
  - 20% other (mostly C and Fortran)
  - 13% procedural and build files
  - 6 million lines of code (not including DECwindows)

DEC is using a DEC layered product, Code Management System (CMS), to
control the development process.  They feel that this has helped CMS
to evolve by feeding requirements back into the CMS development group.
A few additional tools were built to allow coordination between
physical locations.  Called CHARON (the gate-keeper of hell, a
creature of Greek mythology), is provides a shell over CMS to control
release classes and variants.

There exists only one "master pack" that is accessed across the
network within the DEC worldwide development community.

A system build is done in 9 sequential phases.  As VMS has grown over
time the rule of thumb is that it should run overnight on the fastest
processor available and the resultant code should reside on a single
disk.  Some examples provided were:

   V1.0 - 12.5 hours on VAX 11/780 (2,356 files)
   V2.0 - 17 hours on a VAX 11/780
   V3.0 - 12 hours on a VAX 11/782
   V4.0 - 7.5 hours on a large cluster
   V5.0 - 12 hours on a  cluster  with  VAX  8840s  (18,022 files)

--
Anne & Lynn Wheeler   | lynn@garlic.com, http://www.garlic.com/~lynn/

Blade architectures

Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Blade architectures
Newsgroups: comp.os.vms,comp.arch,alt.folklore.computers
Date: Tue, 09 Apr 2002 03:50:19 GMT

KeithParris_NOSPAM@yahoo.com (Keith Parris) writes:

But IBM was so scared of DLM overhead that they chose a
hardware-centric approach to locking (Coupling Facility) that is now
complicating things for them when they try to geographically
distribute a cluster for disaster tolerance.  Geographically-dispersed
Parallel Sysplex clusters stretch to what, 10 km?  VMS clusters have
stretched to more than 200 km.

the escon technology for mainframe was knocking around since the '70s.
in the '80s it was used to increase the data-rate (to about
17mbytes/sec) and the distance for the bus&tag (400ft). the 10km was
the escon distance in the '80s ... in part because it was still being
used with half-duplex device i/o protocol.

SJR had done a cluster locking protocol over trotter/3088 in 1980 that
syncronised in few seconds (effectively a simulated broadcast
full-duplex logic). They were convinced to remap the protocol on top
of LU6.2 (which has half-duplex semantics) ... and the same
syncronization over the same hardware that had been a few seconds
became several minutes running with LU6.2 semantics.

the issue going past 10km with any sort of performance is asynchronous
for both disk/file operations as well as low-level locking support.

i believe the coupling facility is actually a stripped down operating
system for pathlength reasons as well as a dedicated processor (real
&/or LPAR).

my wife did the precursor work (for parallel sysplex) in the '70s when
she did her stint in POK and was responsible for loosely-coupled
architecture (POK'ese for cluster) ... and authored/invented
peer-coupled shared data ...

random refs:
http://www.garlic.com/~lynn/94.html#16 Dual-ported disks?
http://www.garlic.com/~lynn/98.html#30 Drive letters
http://www.garlic.com/~lynn/98.html#35a Drive letters
http://www.garlic.com/~lynn/98.html#37 What is MVS/ESA?
http://www.garlic.com/~lynn/98.html#40 Comparison Cluster vs SMP?
http://www.garlic.com/~lynn/98.html#57 Reliability and SMPs
http://www.garlic.com/~lynn/99.html#71 High Availabilty on S/390
http://www.garlic.com/~lynn/99.html#77 Are mainframes relevant ??
http://www.garlic.com/~lynn/99.html#92 MVS vs HASP vs JES (was 2821)
http://www.garlic.com/~lynn/99.html#100 Why won't the AS/400 die? Or, It's 1999 why do I have to learn how to use
http://www.garlic.com/~lynn/99.html#128 Examples of non-relational databases
http://www.garlic.com/~lynn/2000.html#13 Computer of the century
http://www.garlic.com/~lynn/2000.html#78 Mainframe operating systems
http://www.garlic.com/~lynn/2000c.html#45 Does the word "mainframe" still have a meaning?
http://www.garlic.com/~lynn/2000c.html#47 Does the word "mainframe" still have a meaning?
http://www.garlic.com/~lynn/2000e.html#22 Is a VAX a mainframe?
http://www.garlic.com/~lynn/2000f.html#28 OT?
http://www.garlic.com/~lynn/2000f.html#29 OT?
http://www.garlic.com/~lynn/2000f.html#30 OT?
http://www.garlic.com/~lynn/2000f.html#37 OT?
http://www.garlic.com/~lynn/2000f.html#54 360 Architecture, Multics, ... was (Re: X86 ultimate CISC? No.)
http://www.garlic.com/~lynn/2001b.html#73 7090 vs. 7094 etc.
http://www.garlic.com/~lynn/2001c.html#69 Wheeler and Wheeler
http://www.garlic.com/~lynn/2001d.html#70 Pentium 4 Prefetch engine?
http://www.garlic.com/~lynn/2001d.html#71 Pentium 4 Prefetch engine?
http://www.garlic.com/~lynn/2001e.html#2 Block oriented I/O over IP
http://www.garlic.com/~lynn/2001e.html#44 Where are IBM z390 SPECint2000 results?
http://www.garlic.com/~lynn/2001f.html#21 Theo Alkema
http://www.garlic.com/~lynn/2001g.html#44 The Alpha/IA64 Hybrid
http://www.garlic.com/~lynn/2001g.html#46 The Alpha/IA64 Hybrid
http://www.garlic.com/~lynn/2001g.html#49 Did AT&T offer Unix to Digital Equipment in the 70s?
http://www.garlic.com/~lynn/2001h.html#76 Other oddball IBM System 360's ?
http://www.garlic.com/~lynn/2001i.html#41 Withdrawal Announcement 901-218 - No More 'small machines'
http://www.garlic.com/~lynn/2001i.html#52 misc loosely-coupled, sysplex, cluster, supercomputer, & electronic commerce
http://www.garlic.com/~lynn/2001j.html#23 OT - Internet Explorer V6.0
http://www.garlic.com/~lynn/2001k.html#13 HP-UX will not be ported to Alpha (no surprise)exit
http://www.garlic.com/~lynn/2001k.html#14 HP-UX will not be ported to Alpha (no surprise)exit
http://www.garlic.com/~lynn/2001k.html#18 HP-UX will not be ported to Alpha (no surprise)exit
http://www.garlic.com/~lynn/2001l.html#47 five-nines
http://www.garlic.com/~lynn/2001n.html#3 News IBM loses supercomputer crown
http://www.garlic.com/~lynn/2001n.html#47 Sysplex Info
http://www.garlic.com/~lynn/2001n.html#85 The demise of compaq
http://www.garlic.com/~lynn/2002b.html#37 Poor Man's clustering idea
http://www.garlic.com/~lynn/2002b.html#54 Computer Naming Conventions
http://www.garlic.com/~lynn/2002e.html#25 Crazy idea: has it been done?
http://www.garlic.com/~lynn/2002e.html#71 Blade architectures

--
Anne & Lynn Wheeler   | lynn@garlic.com, http://www.garlic.com/~lynn/

Blade architectures

Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Blade architectures
Newsgroups: comp.os.vms,comp.arch,alt.folklore.computers
Date: Tue, 09 Apr 2002 18:00:53 GMT

"Bill Todd" writes:

Distance adds about 10 us/mile (each way) to comm latency.  For actual disk
operations, anything much under 100 mile separation is measurable but not
noticeable.  Lock activity can be more sensitive to distance depending on
how intense it is, which to a significant degree depends on how suavely both
DLM implementors and application designers avoid the need for it.

problem with original bus&tag at 200ft was that it was half-duplex
synchronous per byte, in the 70s, data streaming channels (still big
thick bus&tag) raised the transfer rate from 1.5mbyte to 3mbyte, the
distance to 400ft and effectively relaxed the syncronicity to
8bytes. escon raised the distance limit by further relaxing the
syncronicity but still half-duplex and syncronicity is much lower unit
than full disk record ... and so there would be multiple round-trip
latencies per disk record transfer (aka are you assuming comm latency
per byte or per disk record?).

getting escon out into product (after 10+ years) was something of a
matter of the load bearing weight of the bus&tag cables (for large
configurations) as well as some customers having to address problems
with positioning all devices within a circular 400ft radius by
migrating to a 400ft radius sphere (i.e. device spread across multiple
floors) ... it wasn't really targeted as a disaster backup scenario.

I think capability for disaster backup scenario was demonstrated with
full-duplex terrestrial T3s & HYPERChannel at the 1989 (1990?)
Supercomputer conference held that year in austin. In the mid-80s, we
did some T2 disaster/backup work ... but had round-trip latencies on
the order of 88,000 miles.
http://www.garlic.com/~lynn/subtopic.html#hsdt

random early NAS/SAN, hyperchannel, a51x references:
http://www.garlic.com/~lynn/94.html#23 CP spooling & programming technology
http://www.garlic.com/~lynn/94.html#24 CP spooling & programming technology
http://www.garlic.com/~lynn/94.html#43 Bloat, elegance, simplicity and other irrelevant concepts
http://www.garlic.com/~lynn/94.html#55 How Do the Old Mainframes Compare to Today's Micros?
http://www.garlic.com/~lynn/96.html#14 mainframe tcp/ip
http://www.garlic.com/~lynn/96.html#27 Mainframes & Unix
http://www.garlic.com/~lynn/99.html#119 Computer, supercomputers & related
http://www.garlic.com/~lynn/2000b.html#38 How to learn assembler language for OS/390 ?
http://www.garlic.com/~lynn/2000c.html#65 Does the word "mainframe" still have a meaning?
http://www.garlic.com/~lynn/2000c.html#66 Does the word "mainframe" still have a meaning?
http://www.garlic.com/~lynn/2000c.html#67 Does the word "mainframe" still have a meaning?
http://www.garlic.com/~lynn/2000c.html#68 Does the word "mainframe" still have a meaning?
http://www.garlic.com/~lynn/2000d.html#12 4341 was "Is a VAX a mainframe?"
http://www.garlic.com/~lynn/2000f.html#30 OT?
http://www.garlic.com/~lynn/2000f.html#31 OT?
http://www.garlic.com/~lynn/2001.html#4 Sv: First video terminal?
http://www.garlic.com/~lynn/2001.html#19 Disk caching and file systems.  Disk history...people forget
http://www.garlic.com/~lynn/2001.html#20 Disk caching and file systems.  Disk history...people forget
http://www.garlic.com/~lynn/2001.html#21 Disk caching and file systems.  Disk history...people forget
http://www.garlic.com/~lynn/2001.html#22 Disk caching and file systems.  Disk history...people forget
http://www.garlic.com/~lynn/2001.html#55 FBA History Question (was: RE: What's the meaning of track overfl ow?)
http://www.garlic.com/~lynn/2001d.html#63 Pentium 4 Prefetch engine?
http://www.garlic.com/~lynn/2001e.html#52 Pre ARPAnet email?
http://www.garlic.com/~lynn/2001f.html#49 any 70's era supercomputers that ran as slow as today's supercompu
http://www.garlic.com/~lynn/2001f.html#66 commodity storage servers
http://www.garlic.com/~lynn/2001g.html#33 Did AT&T offer Unix to Digital Equipment in the 70s?
http://www.garlic.com/~lynn/2001g.html#34 Did AT&T offer Unix to Digital Equipment in the 70s?
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/2001m.html#19 3270 protocol
http://www.garlic.com/~lynn/2001n.html#3 News IBM loses supercomputer crown
http://www.garlic.com/~lynn/2001n.html#26 Open Architectures ?
http://www.garlic.com/~lynn/2002.html#10 index searching
http://www.garlic.com/~lynn/2002e.html#25 Crazy idea: has it been done?
http://www.garlic.com/~lynn/2002e.html#46 What goes into a 3090?

--
Anne & Lynn Wheeler   | lynn@garlic.com, http://www.garlic.com/~lynn/

Is AMD doing an Intel?

Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Is AMD doing an Intel?
Newsgroups: comp.arch
Date: Tue, 09 Apr 2002 22:30:51 GMT

"Fred Kleinsorge" writes:

In any case, I can show you devices, drivers and applications that can
easily saturate the busses they are on - we can get high utilization.  Of
course, you can explain to me why a typical UNIX TCPIP stack ends up doing
1-2 buffer copies - it's not like this has only just been noticed as
something stupid.

I'm a little to young to be able to detail 1960's mainframes (although my
first computer job was as a 360 operator), but I'll wager that they had very
complex I/O subsystems that offloaded much of the processing from the CPU,
I'd guess that a PDA has more CPU horsepower than a 1960s mainframe.  Where
you do the processing very much would seem to be where the last bottleneck
was - the old wheel of reincarnation.  CPUs are slow, offload to the I/O
subsystem, CPUs get faster and the complicated I/O is too slow, use the CPU
resources to make it faster.  Right now, CPUs are fast, but not cheap.  Make
CPUs so cheap that a 256 CPU system does't beak the bank - then dedicating
CPUs for I/O becomes reasonable in a general computing environment.

old mainframes didn't have much real storage ... so that possibly was
at least part of not doing buffer copies ... doing i/o directly
into/outof application address space.

old mainframes also didn't have much real storage ... so there was at
least some paradigm that traded off outboard processing for memory
tables. rather than having memory tables ... like btrees of record
locations ... 1960s mainframe count-key-data architecture had simple
parameter in real storage ... and the disk controller would
continually scan until it found matching record i.e. multi-track
search. furthermore, since old mainframes didn't have much real
storage ... the i/o subsystem didn't cache the argument outboard of
the mainframe memory ... everytime a record spun under the head ... it
would (re)fetch the matching data. This had the effect of dedicating
the complete I/O path to the operation until it found the matching
record.

An instance of this in the '70s was a 3330 drive, with 19 platters
spinning at 3600rpm, 60rps, or a (multi-track) search/scan took about
1/3rd of a second real time. In this particular instance at a large
customer, two or three such scans could be needed before the correct
record was found.

now, many of the mainframes had "integrated i/o" ... the processor
engine had two different microcode programs that it time-shared
... one microcode program provided for the CPU architecture
... i.e. 360/370 ... while the other microcode program implemented the
channel I/O operation (aka the native processor engine would split its
time between executing the processor microcode and the I/O microcode).

A simple example can be seen in the 370 to 303x migration during the
later '70s. The 370/158 had two sets of microcode running on the same
processor engine ... one set was the 370 processor implementation
... the other microcode was the integrated channel i/o implementation
... with the native 158 microcode engine time-shared between the two
sets of microcode.

The next generation 303x series introduced the "channel director"
which was a dedicated I/O processor. The "channel director" was
actually a 370/158 native processor that only had the channel i/o
processor microcode. The 3031 was a 370/158 repackaged with only the
370 microcode and configured to use a separate 158 processor engine as
a dedicated channel director. The 3032 was a 370/168 repackaged to
work with a channel director. Only the 3033 was a "new" processor.

158 & 3031 (& 4341) benchmark number
http://www.garlic.com/~lynn/2002b.html#0 Microcode?

random channel director refs
http://www.garlic.com/~lynn/97.html#20 Why Mainframes?
http://www.garlic.com/~lynn/98.html#23 Fear of Multiprocessing?
http://www.garlic.com/~lynn/99.html#7 IBM S/360
http://www.garlic.com/~lynn/99.html#176 S/360 history
http://www.garlic.com/~lynn/99.html#187 Merced Processor Support at it again
http://www.garlic.com/~lynn/2000.html#78 Mainframe operating systems
http://www.garlic.com/~lynn/2000c.html#69 Does the word "mainframe" still have a meaning?
http://www.garlic.com/~lynn/2000d.html#7 4341 was "Is a VAX a mainframe?"
http://www.garlic.com/~lynn/2000d.html#11 4341 was "Is a VAX a mainframe?"
http://www.garlic.com/~lynn/2000d.html#12 4341 was "Is a VAX a mainframe?"
http://www.garlic.com/~lynn/2000d.html#21 S/360 development burnout?
http://www.garlic.com/~lynn/2000g.html#11 360/370 instruction cycle time
http://www.garlic.com/~lynn/2001b.html#83 Z/90, S/390, 370/ESA (slightly off topic)
http://www.garlic.com/~lynn/2001c.html#3 Z/90, S/390, 370/ESA (slightly off topic)
http://www.garlic.com/~lynn/2001c.html#6 OS/360 (was LINUS for S/390)
http://www.garlic.com/~lynn/2001i.html#34 IBM OS Timeline?
http://www.garlic.com/~lynn/2001j.html#3 YKYGOW...
http://www.garlic.com/~lynn/2001j.html#14 Parity - why even or odd (was Re: Load Locked (was: IA64 running out of steam))
http://www.garlic.com/~lynn/2001l.html#24 mainframe question
http://www.garlic.com/~lynn/2001l.html#32 mainframe question
http://www.garlic.com/~lynn/2002.html#36 a.f.c history checkup... (was What specifications will the standard year 2001 PC have?)
http://www.garlic.com/~lynn/2002.html#48 Microcode?
http://www.garlic.com/~lynn/2002d.html#7 IBM Mainframe at home

random multi-track search
http://www.garlic.com/~lynn/93.html#29 Log Structured filesystems -- think twice
http://www.garlic.com/~lynn/94.html#35 mainframe CKD disks & PDS files (looong... warning)
http://www.garlic.com/~lynn/97.html#16 Why Mainframes?
http://www.garlic.com/~lynn/97.html#29 IA64 Self Virtualizable?
http://www.garlic.com/~lynn/99.html#75 Read if over 40 and have Mainframe  background
http://www.garlic.com/~lynn/2000f.html#18 OT?
http://www.garlic.com/~lynn/2000f.html#19 OT?
http://www.garlic.com/~lynn/2000f.html#42 IBM 3340 help
http://www.garlic.com/~lynn/2000g.html#51 > 512 byte disk blocks (was: 4M pages are a bad idea)
http://www.garlic.com/~lynn/2000g.html#52 > 512 byte disk blocks (was: 4M pages are a bad idea)
http://www.garlic.com/~lynn/2001c.html#17 database (or b-tree) page sizes
http://www.garlic.com/~lynn/2001d.html#60 VTOC/VTOC INDEX/VVDS and performance (expansion of VTOC position)
http://www.garlic.com/~lynn/2001d.html#64 VTOC/VTOC INDEX/VVDS and performance (expansion of VTOC position)
http://www.garlic.com/~lynn/2001l.html#40 MVS History (all parts)
http://www.garlic.com/~lynn/2002.html#5 index searching
http://www.garlic.com/~lynn/2002.html#6 index searching
http://www.garlic.com/~lynn/2002.html#10 index searching
http://www.garlic.com/~lynn/2002d.html#22 DASD response times

--
Anne & Lynn Wheeler   | lynn@garlic.com, http://www.garlic.com/~lynn/

PKI / CA -- Public Key & Private Key

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: PKI / CA -- Public Key & Private Key
Newsgroups: comp.security.misc
Date: Wed, 10 Apr 2002 02:03:46 GMT

"Ingmar" <w i z a r d _ o z @ g m x . n e t> writes:

This is what I think is going on:
) The public key is contained in the certificate
) The private key is only available to the user
) The CA does not have any private keys (except for it's own)

business processes can use (the same) PKI (technology) for two
distinctly different business purposes:

1) authentication
2) confidentiality

in general, digital signatures can be created by using a private key
to sign a message hash/mac ... and then use the corresponding public
key to verify the digital signature ... verifying that a message
originated from a particularly entity.

for confidentiality ... the public key can be used for either directly
encrypting a message ... or using a random symmetric key to encrypt
the message and encrypting the symmetric key with the the public
key. then only the entity with the corresponding private key can
decrypt the message. the issue (especially for data at rest) is what
happens if the private key becomes unavailable (say because of some
sort of hardware failure), is all the corresponding encrypted data
lost? Frequently, for business continuity purposes (no single point of
failure, etc) ... private keys related to confidentially encrypted
data may be escrowed and/or archived.

The business requirements for authentication ... is that you really
would like to be assured that something originated only from a very
specific purpose. In this scenario, the private key is strongly
protected and may only exist in a single place.

The business requirements for confidentiality ... may require that
valuable corporate assets (data & information) is not lost because of
any sort of failure (including a single token housing a private key).

Business requirements associated with authentication may preclude a
private key ever existing outside a very specific hardware
token. Business requirements associated with confidentiality and
business continuity may require multiple copies of a private key be
kept.

basically, PKI is technology that can be used to address two different
kinds of business requirements (confidentiality and authentication)
which can result in the rules regarding the treatment of a private key
be different based on the different business requirements.

--
Anne & Lynn Wheeler   | lynn@garlic.com, http://www.garlic.com/~lynn/

Least folklorish period in computing (was Re: IBM Mainframe at home)

Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Least folklorish period in computing (was Re: IBM Mainframe at home)
Newsgroups: alt.folklore.computers
Date: Wed, 10 Apr 2002 15:49:22 GMT

Charles Shannon Hendrix writes:

I worked for a large bank and the stats said that most fraud came from the
national chains and local merchants, somewhat behind the straight-up ID
thieves which don't need to see your transactions at all.  Online ordering
wasn't really even in the noise yet.  Part of the reason is that once
they have your credit card information, it isn't transmitted again.
By contrast, every single time you use a gas pump or go to a local
merchant, there is a new transmission of the data.  Also, your card is
viewed and the number recorded by an army of underpaid clerks everywhere
you go.

slightly related:
http://www.garlic.com/~lynn/2001h.html#61 re: net banking, is it safe?? (or security proportional to risk)

x9.59 standard for all payments:
http://www.garlic.com/~lynn/x959.html#x959

misc. card fraud res:
http://www.garlic.com/~lynn/aadsm3.htm#cstech3 cardtech/securetech & CA PKI
http://www.garlic.com/~lynn/aadsm5.htm#shock revised Shocking Truth about Digital Signatures
http://www.garlic.com/~lynn/aadsm6.htm#terror7 [FYI] Did Encryption Empower These Terrorists?
http://www.garlic.com/~lynn/aadsm6.htm#terror14 [FYI] Did Encryption Empower These Terrorists? (addenda to chargebacks)
http://www.garlic.com/~lynn/aadsm6.htm#pcards2 The end of P-Cards? (addenda)
http://www.garlic.com/~lynn/aadsm7.htm#auth Who or what to authenticate?
http://www.garlic.com/~lynn/aadsm7.htm#auth2 Who or what to authenticate? (addenda)
http://www.garlic.com/~lynn/aadsm7.htm#rhose4 Rubber hose attack
http://www.garlic.com/~lynn/aadsm7.htm#rhose5 when a fraud is a sale, Re: Rubber hose attack
http://www.garlic.com/~lynn/aadsmore.htm#debitfraud Debit card fraud in Canada
http://www.garlic.com/~lynn/aadsmore.htm#scanon Smartcard anonymity patents
http://www.garlic.com/~lynn/aadsm10.htm#risks credit card & gift card fraud (from today's comp.risks)
http://www.garlic.com/~lynn/aadsm10.htm#tamper Limitations of limitations on RE/tampering (was: Re: biometrics)
http://www.garlic.com/~lynn/aadsm10.htm#bio2 biometrics
http://www.garlic.com/~lynn/aepay3.htm#disputes Half of Visa's disputes, fraud result from I-commerce (more)
http://www.garlic.com/~lynn/aepay3.htm#x959risk2 Risk Management in AA / draft X9.59
http://www.garlic.com/~lynn/aepay3.htm#smrtcrd Smart Cards with Chips encouraged ... fyi
http://www.garlic.com/~lynn/aepay4.htm#visaset2 Visa Delicately Gives Hook to SET Standard
http://www.garlic.com/~lynn/aepay6.htm#fraud Online Card Fraud Thirty Times That Offline
http://www.garlic.com/~lynn/aepay6.htm#ccfraud2 "out of control credit card fraud"
http://www.garlic.com/~lynn/aepay6.htm#ccfraud3 "out of control credit card fraud"
http://www.garlic.com/~lynn/aepay7.htm#nonrep1 non-repudiation, was Re: crypto flaw in secure mail standards
http://www.garlic.com/~lynn/aepay8.htm#ccfraud Almost Half UK E-Shopper's Fear Card Fraud (CC fraud increased by 50% in 2k)
http://www.garlic.com/~lynn/aepay8.htm#ccfraud2 Statistics for General and Online Card Fraud
http://www.garlic.com/~lynn/aepay8.htm#visapass VISA: All Your Password Are Belong to Us
http://www.garlic.com/~lynn/aepay9.htm#risks credit card & gift card fraud (from today's comp.risks)
http://www.garlic.com/~lynn/aepay9.htm#skim High-tech Thieves Snatch Data From ATMs (including PINs)
http://www.garlic.com/~lynn/ansiepay.htm#breach Security breach raises questions about Internet shopping
http://www.garlic.com/~lynn/ansiepay.htm#scaads X9.59 related press release at smartcard forum
http://www.garlic.com/~lynn/aepay10.htm#1 Identity theft tops Consumer fraud complaints
http://www.garlic.com/~lynn/aepay10.htm#3 High-tech Thieves Snatch Data From ATMs (including PINs)
http://www.garlic.com/~lynn/aepay10.htm#6 credit card & gift card fraud (from today's comp.risks)
http://www.garlic.com/~lynn/aepay10.htm#16 Worker Accused of Selling Colleagues' ID's Online (credit card scam)
http://www.garlic.com/~lynn/aepay10.htm#19 Misc. payment, security, fraud, & authentication GAO reports (long posting)
http://www.garlic.com/~lynn/aepay10.htm#25 Definese Dept Criticised on Internal Credit Card Fraud
http://www.garlic.com/~lynn/2000f.html#72 SET; was Re: Why trust root CAs ?
http://www.garlic.com/~lynn/2001c.html#73 PKI and Non-repudiation practicalities
http://www.garlic.com/~lynn/2001d.html#19 [Newbie] Authentication vs. Authorisation?
http://www.garlic.com/~lynn/2001f.html#24 Question about credit card number
http://www.garlic.com/~lynn/2001f.html#40 Remove the name from credit cards!
http://www.garlic.com/~lynn/2001h.html#37 Credit Card # encryption
http://www.garlic.com/~lynn/2001h.html#68 Net banking, is it safe???
http://www.garlic.com/~lynn/2001j.html#2 E-commerce security????
http://www.garlic.com/~lynn/2002.html#25 ICMP Time Exceeded
http://www.garlic.com/~lynn/2002c.html#22 Opinion on smartcard security requested
http://www.garlic.com/~lynn/2002c.html#23 Opinion on smartcard security requested
http://www.garlic.com/~lynn/2002d.html#41 Why?
http://www.garlic.com/~lynn/2002e.html#23 Opinion  on smartcard security requested
http://www.garlic.com/~lynn/2002e.html#40 Smart Cards

fraud related postings:
http://www.garlic.com/~lynn/subtopic.html#fraud

--
Anne & Lynn Wheeler   | lynn@garlic.com, http://www.garlic.com/~lynn/

Blade architectures

Refed: **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Blade architectures
Newsgroups: comp.os.vms,comp.arch,alt.folklore.computers
Date: Wed, 10 Apr 2002 16:02:43 GMT

Anne & Lynn Wheeler writes:

getting escon out into product (after 10+ years) was something of a
matter of the load bearing weight of the bus&tag cables (for large
configurations) as well as some customers having to address problems
with positioning all devices within a circular 400ft radius by
migrating to a 400ft radius sphere (i.e. device spread across multiple
floors) ... it wasn't really targeted as a disaster backup scenario.

an analysis is vaguely coming back to me about the bus&tag channel
connector space for the 3090 (nearly 20 some years ago & justification
for escon). standard bus&tag connector needed something like a minimum
of a sq. ft of panel space. nearly a hundred channels for the 3090
would have needed 100 sq ft. of panel space. Also the bus&tag cables
are rather bulky, being able to even manually get your hands around a
pair of bus&tag cables when there are a hundred pair in a small area
is not practical ... more realistic is to spread it horizontally so
there isn't more than 3-4 pairs veritically with maybe foot clearance
on each side ... needing maybe 50-100 feet horizonal ... say four foot
high by 50-100 feet wide for a connection panel.

escon/fiber connecter space was more on the order of 3270 cable
connector space (or say cat5).

--
Anne & Lynn Wheeler   | lynn@garlic.com, http://www.garlic.com/~lynn/

looking for information on the IBM 7090 instruction set

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: looking for information on the IBM 7090 instruction set
Newsgroups: alt.folklore.computers
Date: Thu, 11 Apr 2002 15:00:27 GMT

haynes@alumni.uark.edu (Jim Haynes) writes:

Well of course if you drop a roll of paper tape it doesn't get out of
sequence :-).  But the numbers are sorta both part of the language and

but it was a pain inserting or replacing a record.

--
Anne & Lynn Wheeler   | lynn@garlic.com, http://www.garlic.com/~lynn/

Hardware glitches, designed in and otherwise

Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Hardware glitches, designed in and otherwise
Newsgroups: alt.folklore.computers
Date: Fri, 12 Apr 2002 14:08:31 GMT

jdallen2000@yahoo.com (James Dow Allen) writes:

Here's a URL to three interesting IBM 370 bugs I posted 14 years ago:

http://groups.google.com/groups?selm=52277%40sun.uucp

These are more design bugs than glitches.
I hope they're interesting enough to warrant comment....

360s instructions would check both start & end bounds for storage
locations before starting an instructions. if start &/or end bounds
failed address, fetch or store protection ... the instruction wouldn't
be executed (protection exception or address exception). also, on
360/67 in virtual memory mode, if either start &/or end bounds
precheck for page available failed, an instruction wouldn't execute
(page fault).

370 introduced the "long" instructions. The "long" instructions were
defined to execute incrementally and be interruptable. The storage
bounds were only check for increment of execution (one byte) .. for
instance a "long" instruction could execute one byte at a time right
up to the boundary of a missing page ... and then interrupt with a
page fault. At the interrupt, the parameter registers of the "long"
instruction would be updated to reflect the current address(es) &
residual length(s). In the case of a page fault, the instruction would
be restarted when the page was available and the updated register
contents.

The 370/125 had a microcode bug where it prechecked the bounds and
wouldn't execute the instruction ... for all instructions and wouldn't
execute the instructions if the bounds precheck failed. The machine
was in customer shops for a year or two before it was realized and
fixed.

The 360/67 had a bug that never got fixed. The 360/67 hardware
translate utilized an 8-entry fully associated array of entries that
mapped virtual to real page numbers. In relocate mode, there was an
extra 150ns per address (normal address on 360/67 in non-relocate was
same as 360/65, 750ns ... however in relocate mode, there was an extra
150ns added to every address operation for translating virtual->real
... or a total of 900ns ... instead of 750ns). Anytime there was a
change in address space (by loading CR0 with a segment table address),
the associative array would have all its entries invalidated and
values reset to all zeros. The machine had been out several years
before it was discovered that on a page fault interrupt, all the
entries were being reset to zero but not flagged as invalidated. The
problem was masked because normal kernel page fault handling always
reloaded CR0 ... even if the virtual address didn't change. Charlie
(as in the person behind the compare and swap instruction ... the
mnemonic compare and swap was chosen specifically because CAS are
charlie's initials) was doing some kernel optimization and removing
redundant loading of CR0 when the virtual address had not changed
(trying to scavenge associative array entries). It took him (all of
us) awhile to realize that programs were failing after his
modifications ... because of a hardware bug.

random refs:
http://www.garlic.com/~lynn/93.html#14 S/360 addressing
http://www.garlic.com/~lynn/94.html#45 SMP, Spin Locks and Serialized Access
http://www.garlic.com/~lynn/95.html#3 What is an IBM 137/148 ???
http://www.garlic.com/~lynn/95.html#10 Virtual Memory (A return to the past?)
http://www.garlic.com/~lynn/97.html#19 Why Mainframes?
http://www.garlic.com/~lynn/98.html#8  Old Vintage Operating Systems
http://www.garlic.com/~lynn/98.html#16 S/360 operating systems geneaology
http://www.garlic.com/~lynn/98.html#46 The god old days(???)
http://www.garlic.com/~lynn/99.html#4 IBM S/360
http://www.garlic.com/~lynn/99.html#89 FIne-grained locking
http://www.garlic.com/~lynn/99.html#149 OS/360 (and descendents) VM system?
http://www.garlic.com/~lynn/99.html#176 S/360 history
http://www.garlic.com/~lynn/99.html#203 Non-blocking synch
http://www.garlic.com/~lynn/99.html#209 Core (word usage) was anti-equipment etc
http://www.garlic.com/~lynn/2000.html#11 I'm overwhelmed
http://www.garlic.com/~lynn/2000.html#12 I'm overwhelmed
http://www.garlic.com/~lynn/2000c.html#30 internal corporate network, misc.
http://www.garlic.com/~lynn/2000c.html#47 Does the word "mainframe" still have a meaning?
http://www.garlic.com/~lynn/2000c.html#49 Does the word "mainframe" still have a meaning?
http://www.garlic.com/~lynn/2000c.html#68 Does the word "mainframe" still have a meaning?
http://www.garlic.com/~lynn/2000d.html#11 4341 was "Is a VAX a mainframe?"
http://www.garlic.com/~lynn/2000e.html#6 Ridiculous
http://www.garlic.com/~lynn/2000e.html#25 Test and Set: Which architectures have indivisible instructions?
http://www.garlic.com/~lynn/2000g.html#7 360/370 instruction cycle time
http://www.garlic.com/~lynn/2000g.html#8 360/370 instruction cycle time
http://www.garlic.com/~lynn/2000g.html#9 360/370 instruction cycle time
http://www.garlic.com/~lynn/2000g.html#11 360/370 instruction cycle time
http://www.garlic.com/~lynn/2000g.html#16 360/370 instruction cycle time
http://www.garlic.com/~lynn/2001.html#7 IBM Model Numbers (was: First video terminal?)
http://www.garlic.com/~lynn/2001b.html#35 John Mashey's greatest hits
http://www.garlic.com/~lynn/2001b.html#40 John Mashey's greatest hits
http://www.garlic.com/~lynn/2001c.html#2 Z/90, S/390, 370/ESA (slightly off topic)
http://www.garlic.com/~lynn/2001c.html#23 Use of ICM
http://www.garlic.com/~lynn/2001f.html#41 Test and Set (TS) vs Compare and Swap (CS)
http://www.garlic.com/~lynn/2001f.html#43 Golden Era of Compilers
http://www.garlic.com/~lynn/2001f.html#69 Test and Set (TS) vs Compare and Swap (CS)
http://www.garlic.com/~lynn/2001f.html#70 Test and Set (TS) vs Compare and Swap (CS)
http://www.garlic.com/~lynn/2001g.html#9 Test and Set (TS) vs Compare and Swap (CS)
http://www.garlic.com/~lynn/2001h.html#69 Very CISC Instuctions (Was: why the machine word size ...)
http://www.garlic.com/~lynn/2001i.html#2 Most complex instructions (was Re: IBM 9020 FAA/ATC Systems from 1960's)
http://www.garlic.com/~lynn/2001j.html#48 Pentium 4 SMT "Hyperthreading"
http://www.garlic.com/~lynn/2001k.html#8 Minimalist design (was Re: Parity - why even or odd)
http://www.garlic.com/~lynn/2001k.html#12 Minimalist design (was Re: Parity - why even or odd)
http://www.garlic.com/~lynn/2001k.html#66 SMP idea for the future
http://www.garlic.com/~lynn/2001k.html#69 Programming in School (was: Re: Common uses...)
http://www.garlic.com/~lynn/2002.html#48 Microcode?

--
Anne & Lynn Wheeler   | lynn@garlic.com -  http://www.garlic.com/~lynn/

Mail system scalability (Was: Re: Itanium troubles)

Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Mail system scalability (Was: Re: Itanium troubles)
Newsgroups: comp.arch
Date: Fri, 12 Apr 2002 14:22:05 GMT

"del cecchi" writes:

Profs on a 36?  I don't remember that, and we designed and programmed
the S/36.  None of the IBM systems of that era were wysiwyg, pretty hard
to do on a 3277.

You wanted pretty you put in bookmaster or gml tags like god meant you
to do.
:p. how else would you do it

del cecchi (crosspost trimmed)

later when color 3279 came along ... you could do some pretty amazing
things with font loading (there was all the lightning flashes you had
to put up with with the font loading). somebody (possibly cowlishaw)
was able to get the color monkey picture (from cover of scientiifc
american) on a 3729.

from an email scalability ... possibly AOL ... 16 million (and
increasing) on one (maybe more than one) tandem machine (although
these may be the 1024 processor model).

the original core of PROFs had as its basis a pre-released, limited
feature version of VMSG that the PROFs group had scarfed up someplace.
When they possibility was raised that they had scarfed VMSG ... they
denied it ... but it was hard to refute when it was pointed out that
every PROFs message that ever existed in the world had the string
"H.S.L." in a non-displayed control field (aka the initials of the
VMSG author).

--
Anne & Lynn Wheeler   | lynn@garlic.com -  http://www.garlic.com/~lynn/

Mail system scalability (Was: Re: Itanium troubles)

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Mail system scalability (Was: Re: Itanium troubles)
Newsgroups: comp.arch
Date: Fri, 12 Apr 2002 15:02:30 GMT

"Tarjei T. Jensen" writes:

Are you sure that this is not SGI Origin 2000 servers?

sure? ... i heard 3rd hand that the "100ton" demo going in at
tandem/cupertino was duplicate of the aol installation. this was some
time ago at a meeting (on completely different topic) that happened to
be hosted by tandem.
http://www.garlic.com/~lynn/aepay3.htm#riskm

also some time ago i heard that tandem was using some flavor of MIPs
processor ... so possibly there is some simalarity between a tandem
config and an SGI config.

--
Anne & Lynn Wheeler   | lynn@garlic.com -  http://www.garlic.com/~lynn/

Blade architectures

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Blade architectures
Newsgroups: comp.os.vms,comp.arch,alt.folklore.computers
Date: Fri, 12 Apr 2002 17:00:30 GMT

"Russell P. Holsclaw" writes:

I never meant to imply that magnetic media (or some form of persistent
storage) were not needed. They will always be with us for obvious reasons. I
was just suggesting that we would see the disappearance of the use of such
media for data that doesn't require long-term persistence. Someday the big
"swap file" full of non-persistent data will be seen as an anachronism. It
only exists today because once it was prohibitively expensive to have a lot
of RAM, and much cheaper to have the same capacity in disk.

note that various persistent storage virtual memory mapping has been
done also (aka mmap) which includes both executable as well as data.

the technique has been used for transient snap-shots as well as
mechanism implementing process migration (between processes not
sharing memory).

A form of the transient snap-shots is effectively what is going on
today when a machine boots up and loads and initializes a large number
of applications ... frequently, in aggregate requiring more real
memory than available ... but never executing simultaneously.

there is a trade-off between utilizing traditional paging
infrastructure for this fast pre-initializing operation ... vis-a-vis
rewriting applications to be "fast-start". Of course, having to
single-page-fault such a fast-start application can offset the
benefits from using the page mapping system ... so something more
efficient than single (small, 4k) page fault operation is needed.

--
Anne & Lynn Wheeler   | lynn@garlic.com -  http://www.garlic.com/~lynn/

Blade architectures

Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Blade architectures
Newsgroups: comp.os.vms,comp.arch,alt.folklore.computers
Date: Fri, 12 Apr 2002 17:11:15 GMT

Anne & Lynn Wheeler writes:

the technique has been used for transient snap-shots as well as
mechanism implementing process migration (between processes not
sharing memory).

CP/67-based & VM/370-based service bureaus starting (at least) in the
early '70s used the technique to implement process migration between
different processors in the same data center/cluster (that had shared
disks) as well between waltham and san francisco data centers (aka the
pages were transferred as a file from one page system in waltham to a
page system in san francisco). Initially this technique was for
scheduled maintenance scenario in 7x24 oepration with online customers
world-wide.

random refs:
http://www.garlic.com/~lynn/97.html#14 Galaxies
http://www.garlic.com/~lynn/99.html#10 IBM S/360
http://www.garlic.com/~lynn/2000.html#64 distributed locking patents
http://www.garlic.com/~lynn/2000e.html#9 Checkpointing (was spice on clusters)
http://www.garlic.com/~lynn/2001.html#49 Options for Delivering Mainframe Reports to Outside Organizat ions
http://www.garlic.com/~lynn/2001b.html#15 Linux IA-64 interrupts [was Re: Itanium benchmarks ...]
http://www.garlic.com/~lynn/2001c.html#89 database (or b-tree) page sizes
http://www.garlic.com/~lynn/2001f.html#20 VM-CMS emulator
http://www.garlic.com/~lynn/2001g.html#52 Compaq kills Alpha
http://www.garlic.com/~lynn/2001m.html#51 Author seeks help - net in 1981
http://www.garlic.com/~lynn/2001m.html#55 TSS/360
http://www.garlic.com/~lynn/2002b.html#36 windows XP and HAL: The CP/M way still works in 2002

--
Anne & Lynn Wheeler   | lynn@garlic.com -  http://www.garlic.com/~lynn/

Mail system scalability (Was: Re: Itanium troubles)

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Mail system scalability (Was: Re: Itanium troubles)
Newsgroups: comp.arch
Date: Sat, 13 Apr 2002 01:11:45 GMT

johng@idiom.com (John A. Gregor) writes:

While it may still not be the case, at one point AOL email was
definitely done on SGIs.  Perhaps the Tandem stuff was for something
other than email or was part of a bid to replace the O2K servers.

my limited understanding is that it is a big database application that
leaves a single copy of the mail in place ... and keeps track of all
sorts of things ... like copy list, who has &/or has not read the
email, etc.

doing some web searching trying to find reference, didn't find any
sgi, but tripped over a tandem reference dated May 2001:
http://webserver.cpg.com/news/6.5/n4.shtml

from above

The Himalaya does figure prominently in one messaging environment: as
a component in Dulles, VA-based America Online Inc.'s messaging
infrastructure. The Himalaya plays an important role in delivering 150
million e-mail messages daily to and from AOL's 29 million users using
a proprietary messaging platform that runs under UNIX as well as on
"one of the largest Himalaya systems in existence," says Pauline Nist,
vice president and general manager for Compaq's Tandem Business Unit.

--
Anne & Lynn Wheeler   | lynn@garlic.com -  http://www.garlic.com/~lynn/

When will IBM buy Sun?

Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: When will IBM buy Sun?
Newsgroups: alt.folklore.computers
Date: Sat, 13 Apr 2002 01:30:09 GMT

ref:
http://techupdate.zdnet.com/techupdate/stories/main/0,14179,2860393,00.html

note when it was originally offered to ibm ... ibm declined (at least
in part because several internal organizations all claiming that they
would be producing something better) ref:
http://www.garlic.com/~lynn/96.html#4a John Hartmann's Birthday Party
http://www.garlic.com/~lynn/2000g.html#40 No more innovation? Get Serious

also in the above references ... is project that was designed and
funded by IBM (DataHub) and then ibm decided to walk away from
... leaving the organization that had been funded to do the
development with all the technology ... which lead to a new PC
server-related company.

--
Anne & Lynn Wheeler   | lynn@garlic.com -  http://www.garlic.com/~lynn/

Blade architectures

Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Blade architectures
Newsgroups: comp.os.vms,comp.arch,alt.folklore.computers
Date: Sat, 13 Apr 2002 19:08:32 GMT

nmm1@cus.cam.ac.uk (Nick Maclaren) writes:

We have one with 128 GB of memory and a total of 1 TB of disk; we
really DON'T want to allow swapping :-)

a "no-dup" page/swap allocation ... would only have page slots on disk
for pages that weren't resident in real storage. if there were
sufficient real storage to always contain all virtual pages ... then
there need not ever be any disk space allocated.

that is (somewhat) separate issue with regard to whether or not any
movement that might occur should be in units of 4kbytes at a time.

recent virtual memory semantics postings (in this thread):
http://www.garlic.com/~lynn/2002f.html#16 Blade architectures
http://www.garlic.com/~lynn/2002f.html#17 Blade architectures

misc dup/no-dup refs:
http://www.garlic.com/~lynn/93.html#12 managing large amounts of vm
http://www.garlic.com/~lynn/93.html#13 managing large amounts of vm
http://www.garlic.com/~lynn/94.html#9 talk to your I/O cache
http://www.garlic.com/~lynn/2000d.html#13 4341 was "Is a VAX a mainframe?"
http://www.garlic.com/~lynn/2001i.html#42 Question re: Size of Swap File
http://www.garlic.com/~lynn/2001l.html#55 mainframe question
http://www.garlic.com/~lynn/2001n.html#78 Swap partition no bigger than 128MB?????
http://www.garlic.com/~lynn/2002b.html#10 hollow files in unix filesystems?
http://www.garlic.com/~lynn/2002b.html#16 hollow files in unix filesystems?
http://www.garlic.com/~lynn/2002b.html#19 hollow files in unix filesystems?
http://www.garlic.com/~lynn/2002b.html#20 index searching

misc. big pages refs:
http://www.garlic.com/~lynn/2001k.html#60 Defrag in linux? - Newbie question
http://www.garlic.com/~lynn/2002b.html#20 index searching
http://www.garlic.com/~lynn/2002c.html#29 Page size (was: VAX, M68K complex instructions)
http://www.garlic.com/~lynn/2002c.html#48 Swapper was Re: History of Login Names
http://www.garlic.com/~lynn/2002e.html#8 What are some impressive page rates?
http://www.garlic.com/~lynn/2002e.html#11 What are some impressive page rates?

--
Anne & Lynn Wheeler   | lynn@garlic.com -  http://www.garlic.com/~lynn/

When will IBM buy Sun?

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: When will IBM buy Sun?
Newsgroups: alt.folklore.computers
Date: Sun, 14 Apr 2002 15:02:05 GMT

Taso Hatzi writes:

I think Sun and IBM have a lot more overlap in corporate
philosophy these days. My guess is that neither Sun's
people nor their customers would find the change too
shocking.

just like AT&T, apple & others got some dose of former ibm executives
... so has sun.

--
Anne & Lynn Wheeler   | lynn@garlic.com -  http://www.garlic.com/~lynn/

Biometric Encryption: the solution for network intruders?

Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Biometric Encryption: the solution for network intruders?
Newsgroups: comp.security.misc
Date: Sun, 14 Apr 2002 15:21:30 GMT

lajavakom@yahoo.com.au (Leela) writes:

From my opinion, I think we can't stop hijacking but we can protect
more secured.  Encryption is using a key derived from biometric
parameters in traditional encryption algorithms.  It is a mathematical
process helping to disguise the information contained in messages that
is either transmitted or stored in a database.

the problem with biometric derived keys is that almost all the
biometric authentication processes are essentially fuzzy ... that in
part is why there is all the stuff in biometrics about false positives
and false negatives. thresholds for a fuzzy match ... between some
biometric reference reading and a current reading can be down in the
30 percent area (even trying to match two succesive biometric
readings). try and imagine a encryption technology where it was
expected that only a random 30 percent of the bits matched between the
encryption key and the decryption key.

biometrics works somewhat better in a 2-factor authentication scheme than
it does in identification.
something you have (like a hardware token)
• something you know (like a pin or password)
• something you are (i.e. a biometric reading)

a hardware token woulc make a claim as to the entity and then the
biometric reading would be taken and attempt a close match for the
claimed entity. The thresholds for percent match may be chosen
differently from a scenario where there are biometric readings from
millions of entities and there needs to be a search for a good
match. A positive still may be possible with only a 50 or 60 percent
match ... just because there are nothing closer. However, (again)
imagine an encryption scheme where there only needs to be an
approximate correlation between the encryption key and the decryption
key.

--
Anne & Lynn Wheeler   | lynn@garlic.com -  http://www.garlic.com/~lynn/

Computers in Science Fiction

Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Computers in Science Fiction
Newsgroups: alt.folklore.computers,alt.history.future,rec.arts.sf.science,rec.arts.sf.written
Date: Sun, 14 Apr 2002 16:05:49 GMT

Charles R Martin writes:

Certainly that's not the way it really happens.  What _does_ happen is
that bug rates go down _immensely_ -- not to zero, but near
statistical zero in every example I've got the data for.  Including
things like misunderstanding of the API calls' real semantics, I have
seen < 0.2 defects per 1,000 SLOC, as compared with something in the
neighborhood of 3 per 1,000 SLOC that you'd normally expect in
reasonably clean industrial-strength code.  Given the variances
involved and the size of experiments I can point to, that's so small
as to make the defect rate statistically insignificant --- which is
not to say it goes away, just that attempts to measure it are
inherently very inaccurate.

three random drifts

1) for the resource manager, we defined an "envelope" of possible
configurations, types of workloads, and workload levels (n-dimensional
space). then something like 1000 benchmarks were defined that covered
the surface and the interior of the n-dimenisonal space along with
some outlyers that were possibly 10 times out. Some sample runs with
the 10 times stressing would fairly reliably result in system
failures.  As a result, I redesigned and rewrote the whole system
serialization code ... which not only eliminated all the system
failures under the stress condistions but had the side-effect of also
eliminating all zombie/hung processes. Finally there was an APL system
model that took the all the benchmarking information and results and
started generating parameters for new benchmarks (attempting to find
anomolous operating regions). The could also wasn't suppose to fail
but the resource manager was suppose to work as advertised ... exactly
controlling resource allocation under all possible configurations,
types of workloads and levels of workloads. Eventually over 2000
benchmarks were run taking three months elapsed time. As the rest of
the system "drifted" (i.e. non-resource-manager poritions of the
system were changed), a selected subset of the benchmarks were
repeated every three months after initial product release.

random refs:
http://www.garlic.com/~lynn/2001e.html#45 VM/370 Resource Manager
http://www.garlic.com/~lynn/94.html#2 Schedulers
http://www.garlic.com/~lynn/94.html#52 Measuring Virtual Memory
http://www.garlic.com/~lynn/95.html#0 pathlengths
http://www.garlic.com/~lynn/2001c.html#13 LINUS for S/390
http://www.garlic.com/~lynn/2001f.html#56 any 70's era supercomputers that ran as slow as today's supercomputers?
http://www.garlic.com/~lynn/2001h.html#18 checking some myths.
http://www.garlic.com/~lynn/2001l.html#32 mainframe question
http://www.garlic.com/~lynn/2002c.html#45 cp/67 addenda (cross-post warning)
http://www.garlic.com/~lynn/2002d.html#0 VAX, M68K complex instructions (was Re: Did Intel Bite Off   MoreThan   It Can Chew?)
http://www.garlic.com/~lynn/subtopic.html#fairshare
http://www.garlic.com/~lynn/subtopic.html#wsclock

2) for the disk engineering lab ... the standard operating system had
a MTBF of 15 minutes with a single test cell (i.e. device under
development). I redesigned and rewrote the input/output supervisor so
that multiple test cells could be operated concurrently w/o any
operating system failure. A lot of the earlier failure modes were
people making assumptions about things always operating correctly
... as opposed to doing a detailed analysis of all possible
assumptions about correctness and then implementing code to handle all
the situtions where things didn't work correctly

random refs:
http://www.garlic.com/~lynn/subtopic.html#disk

3) for this thing called electronic commerce ... it needed a method of
executing payments.
http://www.garlic.com/~lynn/aadsm5.htm#asrn3
http://www.garlic.com/~lynn/aadsm5.htm#asrn2

the initial implementation/code was traditional straight line
operation implementing the function. however, moving into a "service"
environment involving large number of transactions and people all over
the world ... the environment is more like telco operation ... the
trouble desk has requirements on the order of being able pro-actively
recognize that there is some failure and be able to do 1st level
problem determination within five minutes. Traditional "straight line"
industrial strength code frequently doesn't take into account service
operation. My observation has been that there is on the order of four
to ten times as much code written to covert a "straight line"
application into a "service" application (as is in the original
application) ... and this code is frequently a lot more complex.

part of the assurance for this ... was after all the stress &
correctness testing of the base application ... a failure mode grid
was created of the possible states and failures that could occur in a
electronic commerce transaction ... and it was then necessary to show
that either that situation could be recovered from and/or that it
could be diagnosed within a very short period of time. The bare-bones,
straight line application can be proven to be correct ... and it still
wouldn't be satisfactory for real-life environment.

slightly related security proportional to risk
http://www.garlic.com/~lynn/2001h.html#61 Net banking, is it safe???
http://www.garlic.com/~lynn/2001j.html#5 E-commerce security????
http://www.garlic.com/~lynn/2001j.html#54 Does "Strong Security" Mean Anything?
http://www.garlic.com/~lynn/aadsm6.htm#terror3 [FYI] Did Encryption Empower These Terrorists?

lots of random assurance refs:
http://www.garlic.com/~lynn/aadsm10.htm#cfppki13 CFP: PKI research workshop
http://www.garlic.com/~lynn/aadsm10.htm#cfppki18 CFP: PKI research workshop
http://www.garlic.com/~lynn/aadsm10.htm#paiin PAIIN security glossary & taxonomy
http://www.garlic.com/~lynn/aadsm10.htm#keygen2 Welome to the Internet, here's your private key
http://www.garlic.com/~lynn/aadsm2.htm#privacy Identification and Privacy are not Antinomies
http://www.garlic.com/~lynn/aadsm2.htm#useire3 U.S. & Ireland use digital signature
http://www.garlic.com/~lynn/aadsm2.htm#stall EU digital signature initiative stalled
http://www.garlic.com/~lynn/aadsm2.htm#straw AADS Strawman
http://www.garlic.com/~lynn/aadsm2.htm#strawm2 AADS Strawman
http://www.garlic.com/~lynn/aadsm2.htm#strawm3 AADS Strawman
http://www.garlic.com/~lynn/aadsm3.htm#cstech4 cardtech/securetech & CA PKI
http://www.garlic.com/~lynn/aadsm3.htm#cstech5 cardtech/securetech & CA PKI
http://www.garlic.com/~lynn/aadsm3.htm#cstech9 cardtech/securetech & CA PKI
http://www.garlic.com/~lynn/aadsm3.htm#cstech10 cardtech/securetech & CA PKI
http://www.garlic.com/~lynn/aadsm3.htm#cstech12 cardtech/securetech & CA PKI
http://www.garlic.com/~lynn/aadsm3.htm#cstech13 cardtech/securetech & CA PKI
http://www.garlic.com/~lynn/aadsm3.htm#kiss2 Common misconceptions, was Re: KISS for PKIX. (Was: RE: ASN.1 vs XML (used to be RE: I-D ACTION :draft-ietf-pkix-scvp-00.txt))
http://www.garlic.com/~lynn/aadsm3.htm#kiss8 KISS for PKIX
http://www.garlic.com/~lynn/aadsm3.htm#kiss9 KISS for PKIX .... password/digital signature
http://www.garlic.com/~lynn/aadsm5.htm#asrn1 Assurance, e-commerce, and some x9.59 ... fyi
http://www.garlic.com/~lynn/aadsm5.htm#asrn2 Assurance, e-commerce, and some x9.59 ... fyi
http://www.garlic.com/~lynn/aadsm5.htm#asrn3 Assurance, e-commerce, and some x9.59 ... fyi
http://www.garlic.com/~lynn/aadsm5.htm#asrn4 assurance, X9.59, etc
http://www.garlic.com/~lynn/aadsm5.htm#shock revised Shocking Truth about Digital Signatures
http://www.garlic.com/~lynn/aadsm5.htm#shock2 revised Shocking Truth about Digital Signatures
http://www.garlic.com/~lynn/aadsm7.htm#rubberhose Rubber hose attack
http://www.garlic.com/~lynn/aadsm8.htm#softpki19 DNSSEC (RE: Software for PKI)
http://www.garlic.com/~lynn/aadsm9.htm#cfppki5 CFP: PKI research workshop
http://www.garlic.com/~lynn/aadsm9.htm#cfppki10 CFP: PKI research workshop
http://www.garlic.com/~lynn/aadsm9.htm#cfppki11 CFP: PKI research workshop
http://www.garlic.com/~lynn/aadsmore.htm#client3 Client-side revocation checking capability
http://www.garlic.com/~lynn/aepay10.htm#22 PKI: An Insider's View
http://www.garlic.com/~lynn/aepay3.htm#votec (my) long winded observations regarding X9.59 & XML, encryption and certificates
http://www.garlic.com/~lynn/aepay3.htm#x959risk1 Risk Management in AA / draft X9.59
http://www.garlic.com/~lynn/aepay3.htm#x959risk4 Risk Management in AA / draft X9.59
http://www.garlic.com/~lynn/aepay4.htm#comcert3 Merchant Comfort Certificates
http://www.garlic.com/~lynn/aepay6.htm#idf Intel Developer's Forum ... fyi
http://www.garlic.com/~lynn/aepay6.htm#ecom some electronic commerce discussion from dcsb & IDF
http://www.garlic.com/~lynn/aepay6.htm#cacr7 7th CACR Information Security Workshop
http://www.garlic.com/~lynn/aepay6.htm#asrn5 assurance, X9.59, etc
http://www.garlic.com/~lynn/ansiepay.htm#breach Security breach raises questions about Internet shopping
http://www.garlic.com/~lynn/96.html#18 IBM 4381 (finger-check)
http://www.garlic.com/~lynn/2000.html#39 "Trusted" CA - Oxymoron?
http://www.garlic.com/~lynn/2000b.html#40 general questions on SSL certificates
http://www.garlic.com/~lynn/2000g.html#33 does CA need the proof of acceptance of key binding ?
http://www.garlic.com/~lynn/2001.html#50 What exactly is the status of the Common Criteria
http://www.garlic.com/~lynn/2001c.html#34 PKI and Non-repudiation practicalities
http://www.garlic.com/~lynn/2001d.html#41 solicit advice on purchase of digital certificate
http://www.garlic.com/~lynn/2001d.html#58 Very CISC Instuctions (Was: why the machine word size ...)
http://www.garlic.com/~lynn/2001e.html#26 Can I create my own SSL key?
http://www.garlic.com/~lynn/2001e.html#35 Can I create my own SSL key?
http://www.garlic.com/~lynn/2001e.html#40 Can I create my own SSL key?
http://www.garlic.com/~lynn/2001e.html#59 Design (Was Re: Server found behind drywall)
http://www.garlic.com/~lynn/2001g.html#0 FREE X.509 Certificates
http://www.garlic.com/~lynn/2001h.html#7 PKI/Digital signature doesn't work
http://www.garlic.com/~lynn/2001h.html#16 D
http://www.garlic.com/~lynn/2001h.html#64 Net banking, is it safe???
http://www.garlic.com/~lynn/2001i.html#52 misc loosely-coupled, sysplex, cluster, supercomputer, & electronic commerce
http://www.garlic.com/~lynn/2001i.html#57 E-commerce security????
http://www.garlic.com/~lynn/2001n.html#71 Q: Buffer overflow
http://www.garlic.com/~lynn/2001n.html#91 Buffer overflow
http://www.garlic.com/~lynn/2002.html#28 Buffer overflow
http://www.garlic.com/~lynn/2002.html#29 Buffer overflow
http://www.garlic.com/~lynn/2002.html#32 Buffer overflow
http://www.garlic.com/~lynn/2002c.html#35 TOPS-10 logins (Was Re: HP-2000F - want to know more about it)
http://www.garlic.com/~lynn/2002d.html#16 Mainframers: Take back the light (spotlight, that is)
http://www.garlic.com/~lynn/2002e.html#17 Smart Cards
http://www.garlic.com/~lynn/2002e.html#58 O'Reilly C Book
http://www.garlic.com/~lynn/2002e.html#71 Blade architectures
http://www.garlic.com/~lynn/2002e.html#73 Blade architectures

--
Anne & Lynn Wheeler   | lynn@garlic.com -  http://www.garlic.com/~lynn/

Computers in Science Fiction

Refed: **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Computers in Science Fiction
Newsgroups: alt.folklore.computers,alt.history.future,rec.arts.sf.science,rec.arts.sf.written
Date: Sun, 14 Apr 2002 18:11:52 GMT

Anne & Lynn Wheeler writes:

the initial implementation/code was traditional straight line
operation implementing the function. however, moving into a "service"
environment involving large number of transactions and people all over

the end-to-end transport of a payment message was one thing ... having
an environment with lots of diagnostics oriented around end-to-end
circuit based paradigm, telco provisioning and even service level
agreements (SLA) and trying to translate that to a packet-based
internet anarchy was something totally different. the technology of
the bits on the wire was trivial ... compared to trying to translate
the whole telco provisioned end-to-end ciruit operation to the
internet anarchy.

--
Anne & Lynn Wheeler   | lynn@garlic.com -  http://www.garlic.com/~lynn/

When will IBM buy Sun?

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: When will IBM buy Sun?
Newsgroups: alt.folklore.computers
Date: Sun, 14 Apr 2002 18:19:51 GMT

cjt writes:

And for that matter, I think Dell is largely populated with former I've Been
Moved-ers.

we were in austin (for a while my wife was a manager of 6000
engineering architecture) in the late '80s and saw some significant
migration from the austin group to dell.

at least some number of the austin ha/cmp people went to the
austin/tandem/compaq group (may be still there).

--
Anne & Lynn Wheeler   | lynn@garlic.com -  http://www.garlic.com/~lynn/

Blade architectures

Refed: **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Blade architectures
Newsgroups: comp.arch
Date: Sun, 14 Apr 2002 21:22:46 GMT

JF Mezei writes:

Swap and page space should accomodate all of your virtual memory. If you want
your 16 meg RAM system to have 100 meg of virtual memory, then you would need
at least 100 meg of page/swap file space.

Consider the scenario where your hardware RAM is much smaller than the virtual
address space you need. In such a scenario, the "primary" storage is actually
the disk page files, and only the pages actually needed at the moment are
brought to RAM.

that is a "dup" or duplicate algorithm/implementation. It is possible
to have a no-dup implementation ... that a virtual page either resides
in real storage or on disk ... but never both. Since there is a
trade-off with write operations between a "dup" and "no-dup"
implementation ... you can actually have an implementation that
dynamically switches when disk space becomes constrained aka a dup
algorihtm can save write operations for pages brought in ... selected
for replacement ...  but not changed during their most recent stay in
storage. However other considerations having to do with disk arm
locality can justify an always write-out implementation ... further
tilting things towards a "no-dup" implementation.

recent refs on this thread in a.f.c.
http://www.garlic.com/~lynn/2002f.html#20 Blade architectures

--
Anne & Lynn Wheeler   | lynn@garlic.com -  http://www.garlic.com/~lynn/

Security Issues of using Internet Banking

Refed: **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Security Issues of using Internet Banking
Newsgroups: alt.computer.security,alt.folklore.computers
Date: Mon, 15 Apr 2002 03:34:41 GMT

ccsim@bigpond.net.au (Jasmine) writes:

Hi!

I wish to get some views and expertise on the security
issues of using Internet Banking.

As a user, I see the benefits of having the convenience of being able
to see my transactions online and paying my monthly bills without
physically leaving my home.

However, I know alot of people is still not be able to accept this
concept.  And I do understand their concerns on the security issue
that is involved.  I can roughly visualise how many people would be
involved in the process.  Many people would be able to view my
transactions such as employees from the bank and IT personnels. They
would also have access to my account. In fact, anybody just by calling
the bank on the phone, with my personal details would be able to
access my account over the phone. The idea of banking over the
Internet is scary.

One would like to think that it is safe to do my banking on the
Internet.  However, is it?  Is it safe for one to do banking over the
Internet? What are the security issues involved? What are the
measurements can one take in order to improve the security while doing
internet banking?

I would like to hear views or comments on the idea of using Internet
Banking.

internet technology has gotten something of a reputation for being
insecure.  however a lot of internet banking is just a internet spigot
that interfaces to some backend processor someplace, in some
implementations the internet spigot uses much the same interface to
the backends that a customer call center uses for implementing
telephone banking (or for that matter the same interface that an ATM
network uses for doing ATM banking).

The issue then is it is similar to ATM banking but the end-point is
your PC (instead of an ATM machine) and the transport is the internet
(instead of an encrypted private network). Well it is possible using
things like SSL to achieve similar encryption security for the data
being transported as an encrypted private network.

That leaves a couple of vulnerabilities:

1) your pc (compared to an ATM machine)
2) the internet gateway

An ATM machine pretty well restricts which buttons you can push and
what functions that might happen. A poorly implemented internet
gateway might allow "virtual buttons" to be pushed that wouldn't be
allowed if it was a real ATM machine (or internet viruses to be
introduced that capture transaction information). A poorly secured
personal PC might have viruses that capture keystrokes and contribute
to fraudulent transactions.

However, the number of types of people that can view transactions
(occuring at the back-end processor) would be approx. the same whether
it was internet, ATM, physical check, etc.

cross-posted to a.f.c where there has been a programming assurance
thread going on (aka what is the assurance of the internet gateway
that implements internet banking ... is it equivalent to the assurance
required for ATM software? ... also what is the assurance of a
personal PC?).

much of europe is using or moving towards hardware tokens of various
kinds (for financial transactions) because of issues with trust and
assurance of personal PCs ... i.e. it isn't sufficient for fraudulent
transactions to just capture keystrokes ... but access to the specific
hardware token is also required.

misc eu standards & internet banking discussions
http://www.garlic.com/~lynn/aepay7.htm#netsecure some recent threads on netbanking & e-commerce security
http://www.garlic.com/~lynn/aepay7.htm#3dsecure 3D Secure Vulnerabilities? Photo ID's and Payment Infrastructure
http://www.garlic.com/~lynn/aepay10.htm#17 Visa 3-D Secure vs MasterCard SPA Whitepaper (forwarded)
http://www.garlic.com/~lynn/aadsm10.htm#keygen2 Welome to the Internet, here's your private key
http://www.garlic.com/~lynn/2001g.html#57 Q: Internet banking
http://www.garlic.com/~lynn/2001g.html#60 PKI/Digital signature doesn't work
http://www.garlic.com/~lynn/2001g.html#61 PKI/Digital signature doesn't work
http://www.garlic.com/~lynn/2001g.html#62 PKI/Digital signature doesn't work
http://www.garlic.com/~lynn/2001g.html#64 PKI/Digital signature doesn't work
http://www.garlic.com/~lynn/2001i.html#25 Net banking, is it safe???
http://www.garlic.com/~lynn/2001i.html#26 No Trusted Viewer possible?
http://www.garlic.com/~lynn/2001k.html#0 Are client certificates really secure?
http://www.garlic.com/~lynn/2001k.html#55 I-net banking security
http://www.garlic.com/~lynn/2001m.html#6 Smart Card vs. Magnetic Strip Market
http://www.garlic.com/~lynn/2001m.html#9 Smart Card vs. Magnetic Strip Market
http://www.garlic.com/~lynn/2002c.html#10 Opinion on smartcard security requested
http://www.garlic.com/~lynn/2002c.html#21 Opinion on smartcard security requested
http://www.garlic.com/~lynn/subtopic.html#fraud Risk, Fraud, Exploits
http://www.garlic.com/~lynn/subtopic.html#assurance Assurance

--
Anne & Lynn Wheeler   | lynn@garlic.com, http://www.garlic.com/~lynn/

Security Issues of using Internet Banking

Refed: **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Security Issues of using Internet Banking
Newsgroups: alt.computer.security,alt.folklore.computers
Date: Mon, 15 Apr 2002 03:50:24 GMT

Jim Watt writes:

I'm quite happy to use it.  I do ask retailers whether they
retain my credit card details online and don't like it if they
do.  Retailers are not as security aware as banks.

The internet itself is of course NOT secure, however
there is more chance that someone who wants to find
out data about you will steal your PC than anything else.

Its all a matter of balance, standing in queues at the
bank costs money and tasks like settling credit cards
takes longer done over the counter incurring interest
charges when they could be done quicker online.

A computer transaction is cheaper than a teller transaction
so in the end the majority will be done online.

with respect to credit cards there is another issue ... the amount of
security a merchant can afford:
http://www.garlic.com/~lynn/2001h.html#61 Net banking, is it safe???

slightly related:
http://www.garlic.com/~lynn/aadsm5.htm#asrn3 Assurance, e-commerce, and some x9.59 ... fyi
http://www.garlic.com/~lynn/aadsm5.htm#asrn2 Assurance, e-commerce, and some x9.59 ... fyi
http://www.garlic.com/~lynn/aadsmore.htm#2527a RFC 2527 Physical Security Controls Question
http://www.garlic.com/~lynn/aadsm6.htm#websecure merchant web server security
http://www.garlic.com/~lynn/aadsm6.htm#terror [FYI] Did Encryption Empower These Terrorists?
http://www.garlic.com/~lynn/aadsm6.htm#terror3 [FYI] Did Encryption Empower These Terrorists?
http://www.garlic.com/~lynn/aadsm6.htm#terror4 [FYI] Did Encryption Empower These Terrorists?
http://www.garlic.com/~lynn/aadsm6.htm#terror5 [FYI] Did Encryption Empower These Terrorists?
http://www.garlic.com/~lynn/aadsm6.htm#pcards The end of P-Cards?
http://www.garlic.com/~lynn/aadsm6.htm#pcards3 The end of P-Cards? (addenda)
http://www.garlic.com/~lynn/aadsm7.htm#rubberhose Rubber hose attack
http://www.garlic.com/~lynn/aadsm8.htm#rhose17 [Fwd: Re: when a fraud is a sale, Re: Rubber hose attack]
http://www.garlic.com/~lynn/aadsm10.htm#cfppki13 CFP: PKI research workshop
http://www.garlic.com/~lynn/aadsm10.htm#tamper Limitations of limitations on RE/tampering (was: Re: biometrics)
http://www.garlic.com/~lynn/aadsm10.htm#bio8 biometrics (addenda)
http://www.garlic.com/~lynn/aepay7.htm#netbank2 net banking, is it safe?? ... security proportional to risk
http://www.garlic.com/~lynn/aepay7.htm#netsecure some recent threads on netbanking & e-commerce security
http://www.garlic.com/~lynn/aepay7.htm#3dsecure2 3D Secure Vulnerabilities? Photo ID's and Payment Infrastructure
http://www.garlic.com/~lynn/aepay7.htm#3dsecure3 financial payment standards ... finger slip
http://www.garlic.com/~lynn/aepay10.htm#20 Security Proportional to Risk (was: IBM Mainframe at home)
http://www.garlic.com/~lynn/2001d.html#42 IBM was/is: Imitation...
http://www.garlic.com/~lynn/2001h.html#53 Net banking, is it safe???
http://www.garlic.com/~lynn/2001h.html#58 Net banking, is it safe???
http://www.garlic.com/~lynn/2001h.html#62 Net banking, is it safe???
http://www.garlic.com/~lynn/2001h.html#64 Net banking, is it safe???
http://www.garlic.com/~lynn/2001h.html#67 Would this type of credit card help online shopper to feel more secure?
http://www.garlic.com/~lynn/2001h.html#68 Net banking, is it safe???
http://www.garlic.com/~lynn/2001h.html#70 Net banking, is it safe???
http://www.garlic.com/~lynn/2001h.html#75 Net banking, is it safe???
http://www.garlic.com/~lynn/2001i.html#9 Net banking, is it safe???
http://www.garlic.com/~lynn/2001i.html#10 Net banking, is it safe???
http://www.garlic.com/~lynn/2001i.html#16 Net banking, is it safe???
http://www.garlic.com/~lynn/2001i.html#25 Net banking, is it safe???
http://www.garlic.com/~lynn/2001i.html#26 No Trusted Viewer possible?
http://www.garlic.com/~lynn/2001i.html#35 Net banking, is it safe???
http://www.garlic.com/~lynn/2001i.html#36 Net banking, is it safe???
http://www.garlic.com/~lynn/2001i.html#53 Credit Card # encryption
http://www.garlic.com/~lynn/2001i.html#57 E-commerce security????
http://www.garlic.com/~lynn/2001i.html#57 E-commerce security????
http://www.garlic.com/~lynn/2001j.html#2 E-commerce security????
http://www.garlic.com/~lynn/2001j.html#5 E-commerce security????
http://www.garlic.com/~lynn/2001j.html#44 Does "Strong Security" Mean Anything?
http://www.garlic.com/~lynn/2001j.html#54 Does "Strong Security" Mean Anything?
http://www.garlic.com/~lynn/2001k.html#55 I-net banking security
http://www.garlic.com/~lynn/2001l.html#2 Why is UNIX semi-immune to viral infection?
http://www.garlic.com/~lynn/2002d.html#8 Security Proportional to Risk (was: IBM Mainframe at home)
http://www.garlic.com/~lynn/2002d.html#9 Security Proportional to Risk (was: IBM Mainframe at home)
http://www.garlic.com/~lynn/2002d.html#11 Security Proportional to Risk (was: IBM Mainframe at home)
http://www.garlic.com/~lynn/2002d.html#16 Mainframers: Take back the light (spotlight, that is)
http://www.garlic.com/~lynn/2002d.html#24 Security Proportional to Risk (was: IBM Mainframe at home)
http://www.garlic.com/~lynn/2002d.html#25 Security Proportional to Risk (was: IBM Mainframe at home)
http://www.garlic.com/~lynn/2002d.html#28 Security Proportional to Risk (was: IBM Mainframe at home)
http://www.garlic.com/~lynn/2002e.html#5 What goes into a 3090?
http://www.garlic.com/~lynn/2002e.html#18 Opinion  on smartcard security requested
http://www.garlic.com/~lynn/2002e.html#36 Crypting with Fingerprints ?
http://www.garlic.com/~lynn/2002e.html#37 Would the value of knowledge and information be transferred or shared accurately across the different culture??????
http://www.garlic.com/~lynn/2002f.html#10 Least folklorish period in computing (was Re: IBM Mainframe at home)
http://www.garlic.com/~lynn/2002f.html#23 Computers in Science Fiction

--
Anne & Lynn Wheeler   | lynn@garlic.com, http://www.garlic.com/~lynn/

Computers in Science Fiction

Refed: **, - **, - **, - **, - **, - **, - **, - **, - **
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Computers in Science Fiction
Newsgroups: alt.folklore.computers,alt.history.future,rec.arts.sf.science,rec.arts.sf.written
Date: Mon, 15 Apr 2002 15:45:33 GMT

Lee DeRaud writes:

Why am I even saying this? Because (in my experience) the concept of
"J. Random Programmer" just doesn't fit in the same sentence with "IBM
FSD": there really is such a thing as a corporate culture and FSD's
is not typical.

a large percentage of FSD people were GML programmers (aka the
precursor to SGML, HTML, XML, etc) ... who wrote documents that met
various federal criteria (aka their job was to word smith). another
large group was contract managers ... who managed contracts that were
then subcontracted out to a lot of other people.

they were also good at billing .. we once had a project review by FSD
.... and they eventually sent something like 20-30 people to a one
week meeting ... and the project got the bill for all of the peoples'
time ... but then a lot of the project was transferred to FSD and they
had to foot the bill. slightly related refs:
http://www.garlic.com/~lynn/2000c.html#6 TF-1
http://www.garlic.com/~lynn/2000d.html#27 Superduper computers--why RISC not 390?

there were some really good system design people as well as
programmers.  For instance the guy that headed up the original FAA air
traffic control system ... who then went on to be president of FSD (as
well as many of his team). The next couple rounds in the late '80s &
90s for the new & ever improved FAA air traffic control system didn't
do quite as well (although there were some excellent people working on
it also). slightly related refs:
http://www.garlic.com/~lynn/2001.html#3 First video terminal?
http://www.garlic.com/~lynn/2001d.html#77 Pentium 4 Prefetch engine?
http://www.garlic.com/~lynn/2001h.html#15 IBM 9020 FAA/ATC Systems from 1960's
http://www.garlic.com/~lynn/2002b.html#6 Microcode?
http://www.garlic.com/~lynn/98.html#23 Fear of Multiprocessing?

side note ... GML was original chosen because it is the first letters
of the late names of the three people that worked on it, random refs:
http://www.garlic.com/~lynn/94.html#11 REXX
http://www.garlic.com/~lynn/94.html#43 Bloat, elegance, simplicity and other irrelevant concepts
http://www.garlic.com/~lynn/94.html#55 How Do the Old Mainframes Compare to Today's Micros?
http://www.garlic.com/~lynn/96.html#24 old manuals
http://www.garlic.com/~lynn/97.html#9 HELP! Chronology of word-processing
http://www.garlic.com/~lynn/97.html#26 IA64 Self Virtualizable?
http://www.garlic.com/~lynn/98.html#16 S/360 operating systems geneaology
http://www.garlic.com/~lynn/98.html#21 Reviving the OS/360 thread (Questions about OS/360)
http://www.garlic.com/~lynn/99.html#42 Enter fonts (was Re: Unix case-sensitivity: how did it originate?
http://www.garlic.com/~lynn/99.html#43 Enter fonts (was Re: Unix case-sensitivity: how did it originate?
http://www.garlic.com/~lynn/99.html#91 Documentation query
http://www.garlic.com/~lynn/99.html#197 Computing As She Really Is. Was: Re: Life-Advancing Work of Timothy Berners-Lee
http://www.garlic.com/~lynn/2000.html#8 Computer of the century
http://www.garlic.com/~lynn/2000.html#34 IBM 360 Manuals on line ?