Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!bionet!hayes.ims.alaska.edu!casbah.acns.nwu.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: asuvax!proto17!williamsk@ncar.ucar.edu (Kevin W. Williams)
Newsgroups: comp.dcom.telecom
Subject: Re: Why Are They Called 'Generics'?
Message-ID: <15221@accuvax.nwu.edu>
Date: 1 Dec 90 22:20:08 GMT
Sender: news@accuvax.nwu.edu
Organization: gte
Lines: 24
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 10, Issue 865, Message 10 of 13


In article <14693@accuvax.nwu.edu>, foz@ihlpf.att.com (William F
Thompson) writes:

>  From article <14643@accuvax.nwu.edu>, by Jeff Wasilko <jjwcmp@
>  ultb.isc.rit.edu>:

> > As I was catching up on my Digest-reading, a thought occured to me --
> > why are switch programs called 'generics'?

> I always wondered that too (and I even develop software for them).
> But wonder no more - they're now called Software Releases.
> Bill Thompson   AT&T Network Systems    att!ihlpf!foz

Well, I also develop software for them, and still call them generics.
The "generic" portion of the load is that part which is identical in
all machines, i.e. it is generic. This contrasts with the "Office
Dependent" sections of the load, i.e. the database, and the "dynamic"
sections of the load, i.e stacks and other unprotected data. In common
usage, the new release of the program became a new generic.


Kevin Wayne Williams
     UUCP : ...!ames!ncar!noao!asuvax!gtephx!williamsk