From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: A future supercomputer Newsgroups: sci.crypt Date: Wed, 21 Mar 2001 21:01:21 GMT"JCA" <Jose_Castejon-Amenedo@hp.com> writes:
lots of innovation is going on with computers in the past ten years that wouldn't have happened in the 60s .... in large part because of the lack of computer resources. It isn't just a single supercomputer ... it is having lots & lots of them (i.e. the processing power of most PCs today are orders of magnitude larger than what was available in the 60s and a whole lot more numerous).
however, rate of innovation isn't necessarily linearly proportional to the huge amount excess disposalbe resources ... there is still a whole lot of brownian motion going on.
the ASCI stuff is just a lot of normal processors all ganged together
random refs:
https://www.garlic.com/~lynn/2001c.html#86
https://www.garlic.com/~lynn/2000d.html#2
https://www.garlic.com/~lynn/2000d.html#3
https://www.garlic.com/~lynn/95.html#13
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: SSL question Newsgroups: sci.crypt Date: Wed, 21 Mar 2001 22:06:41 GMTPaul Rubin <phr-n2001@nightsong.com> writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: "Bootstrap" Newsgroups: alt.folklore.computers Date: Wed, 21 Mar 2001 22:09:58 GMTdscheidt@tumbolia.com (David Scheidt) writes:
I remember when my kids were younger ... literally lifting them off the ground trying to pull their boots on by the bootstraps. Typically I would lean over and they would put their arm around my neck so they didn't fall over when they left the ground.
the problem i've got with some of the cowboy boots with the straps on the (inside) sides ... is some of them are sewn with very stiff nylon thread that abraids the skin ... unless you have particularly heavy socks. I always have to check the socks before putting on some of the boots.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Invalid certificate on 'security' site. Newsgroups: alt.computer.security,comp.security,comp.security.misc Date: Wed, 21 Mar 2001 23:05:45 GMT"Spock" writes:
the reason the weaker/browser model was implemented was what was what certificates were designed for ... being able to do authentication w/o having to resort to an online operation.
having direct online access for authentication information makes the use of certificates redundant and superfluous ... aka
1) it is weaker trust model to use certificates and be offline ...
2) it is a much weaker trust model to be offline and not have anyting
3) it is stronger trust model to be able to online authenticate the information
4) but the whole point of having a certificate was being able to do offline authentication when there wasn't online access for doing authentication
5) certificates and online may not quite be an oxymoron ... but it is definitly redundant and superfluous.
random refs:
https://www.garlic.com/~lynn/2001c.html#57
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: A future supercomputer Newsgroups: sci.crypt Date: Wed, 21 Mar 2001 23:16:45 GMT"JCA" <Jose_Castejon-Amenedo@hp.com> writes:
And while both of the above ... digital visualization and correlation & regression processing have been applied to large number of different areas of discovery ... they've also been used specifically in the area of brain research and activity (i.e. lots & lots of digital recording of brain physical operation ... and then being able to various sorts of analytical studies as well as digital visualization of the information).
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Unix hard links Newsgroups: comp.arch,comp.arch.storage Date: Thu, 22 Mar 2001 00:46:59 GMTPaul Repacholi writes:
as to bdam ... a couple years ago ... we visited what is (was?) probably the largest online managed information service. It was originally designed and implemented using bdam in the late '60s and continues to run production today serving customers all over the world. there supposedly is something like 40,000 trained proferssionals around the world adept in looking up information (as well as available to a large number of other people).
the interesting thing is that they keep trying to figure out an implementation more modern and efficient than their late '60s bdam implementation ... and have yet to do it.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: bunch of old RFCs recently went online Newsgroups: alt.folklore.computers Date: Thu, 22 Mar 2001 15:49:36 GMTbunch of old RFCs have just gone online in the past couple days
rfc22.txt rfc44.txt rfc91.txt rfc121.txt rfc128.txt rfc138.txt rfc160.txt rfc161.txt rfc162.txt rfc164.txt rfc166.txt rfc171.txt rfc184.txt rfc188.txt rfc189.txt rfc195.txt rfc225.txt rfc252.txt rfc255.txt rfc298.txt rfc300.txt rfc325.txt rfc343.txt rfc351.txt rfc353.txt rfc357.txt rfc367.txt rfc369.txt rfc378.txt rfc384.txt rfc392.txt
rfc384 is (aug. 1972)
OFFICIAL SITE IDENTS FOR ORGANIZATIONS IN THE ARPA NETWORK
http://tools.ietf.org/html/rfc384.txt
I know the LL-67 ... but not sure about the AMES-67. Lockheed (NASA?) had a special triplex 360/67 for manned orbital lab. project that was located in sunnyvale area.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Invalid certificate on 'security' site. Newsgroups: alt.computer.security,comp.security,comp.security.misc Date: Thu, 22 Mar 2001 17:00:21 GMT"Spock" writes:
the purpose of a certificate was so that an offline relying party could take the embedded public key, verify the digital signature offline and then use the credential information in the certificate as being trusted.
revokation was via certificate revokation lists ... the original idea would that they would be distributed monthly.
the target design point was for offline email, but the paradigm was somewhat the offline credit card operation from the 50s, 60s ... etc. before it went online. The CRLs were the monthly paper booklets of invalid credit card numbers.
The credit card infrastructure went to online where the information from the magstripe is used to look up the real information and then with the access to the account information the standard business process is performed.
By comparison, the certificate contains (effectively) a (possibly stale) copy of the online information that was built into a manufactured certificate and certified at some time in the past. The purpose of the certificate ... is being able to rely on (stale) certified copy of the online information ... when operating in an offline mode.
The public/private key pair is used to authenticate ... the certificate is used for distribution of certified stale, static copies of some online data that can be used in an offline mode when there isn't access to online information.
The most trivial flavor of such a certificate ... is a relying-party-only certificate that only contains some sort of domain specific ID ... like an account number of employee number. These are typically used because of either liability (allow others to rely on the certified information opens an organization to liability), privacy (an identify certificate can represent serious exposure of unnecessary privacy information), and/or trust (the types of things that a business may be concerned about may not be something that some other orgnaization can certify).
In any case, relying-party-only certificates with only an id/account number, transactions related to the certificate typically have to access the related online record to obtain the up-to-date information of interest ... (in a financial situation, the current, real-time credit-limit and/or account balance, something that would get stale fast if placed in a certificate manufactured & certified at some time in the past). However, it is trivial to show that accessing the online record makes also carrying a read-only, stale copy of possibly a subset of that information in a certificate, redundant and superfluous.
The issue in a certificate is that a copy of some (possibly subset) information from some account/ID record has been placed in a manufactured certificate at some time in the past and certified by some trusted party. The purpose of creating that certificate is so that relying parties can achieve some level of comfort when they don't have online access to the original, current & up-to-date account/ID record.
For all intents and purposes, a certificate is an implementation of a trusted distributed R/O caching database system. There is a master of the information someplace (analogous to the internet Domain Name System that is used for mapping things like www.abc.com domain name to an internet IP address of the form xx.xx.xx.xx). In the case of certificates, the Certificate Authority has the original master information and it manufactures certified R/O copies of that information for distribution ... typically at some time in the past ... which means that the information can easily become stale and/or out-of-date.
The issue is that if the information changes very infrequently and has a relatively low value ... some entity can rely on the "local" copy w/o having to resort to the original online copy (especially compared to not having any information at all when offline).
Various practical business problems for certificates have cropped up.
Identity certificates ... i.e. name & address ... represents a privacy exposure.
Access control certificates ... putting actual access control information can represent a security exposure
3rd party certificates ... may not have access to any information that a business unit is interested in having certified by other parties.
General certificates ... business units may not be interested in certifying information that may be used by an unknown number of relying-parties which opens them to unknown amount of liability
Stale information ... business units typically are interested in the timely, online information contained in the original record.
So businesses have tended to migrate towards relying-party-only certificates (privacy, liability, trust, availibiilty of the information, etc). But, in effect, such instruments basically only carry an index to the original online record (rather than carrying the information in the certificate, it just contains a pointer to where the information actually exists).
Now for the redundant and superfluous part. Unless somebody is doing authentication totally independent of any business process (i.e. doing authentication just for the sake of doing authentication operation with no associated business purpose &/or reason), the operation consists of some sort of transaction (financial, session initiation, request for access, etc). The transaction contains some amount of information, including thing like an account number, employee id, userid, etc. That transaction is then digitally signed. The business unit then looks up the master record based on information in the transaction, once it has the master copy of the data, verify the digital signature. Also having a stale, static copy of the public key and some sort of master record identifier in an appended certificate that has been also digital signed (which also has to be verified ... along with all the other things in the trust model) is redundant and superfluous.
The public/private key digital signature is sufficient for providing authentication. An appended certificate credential is required for providing authentication & certified information in an offline environment when it is not possible to access the original, timely, uptodate information/record.
Certificates are perfectly fine when the business operation doesn't need online access to original, timely, & uptodate information. Business operations that need access to original, timely, & uptodate information ... typically have online protocols that give them access to original, timely & uptodate information. Online protocols that access the orignal, timely & uptodate information only for the purpose of determining if stale, static copies from the past can be trusted are somewhat contrived.
Further contrived, are the relying-party-only certificates that force an access to the original, timely, & uptodate information ... it is possible for a business unit to access the original, timely & uptodate information w/o including a relying-party-only certificate as part of the protocol.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Invalid certificate on 'security' site. Newsgroups: alt.computer.security,comp.security,comp.security.misc Date: Thu, 22 Mar 2001 17:14:17 GMTalun+un@texis.com (Alun Jones) writes:
And of course, one of my favorite scenerios is the server SSL domain name certificates. One of the justifications for server SSL domain name certificates (I claim represent 99.99999999% of the current world-wide certificate authenticatione events) is that the domain name infrastructure has various integrity weaknessses.
However, what authoritative agency do the CAs have to go to in order to authenticate a domain name as part of manufacturing a server SSL domain name certificate? The very same domain name infrastructure.
So the proposal for improving the integrity of the domain name infrastructure (so that the CAs can rely on it for validating domain name information so they can issue a a server SSL domian name certificate) is to have people register their public key when they register their domain name.
Now, that opens up two issues
1) if the domain name infrastructure integrity is improved so that the CAs can trust them, then it is likely that level of integrity is also sufficient for everybody else (mitigating the issue of why do people think there is a need for SSL domain name certificates).
2) if the domain name infrastrucure has a registered copy of the public key, the domain name infrastructure has the option of distributing a real-time copy of the public key in the same process that does the hostname/domainname resolution to ip-address (i.e. rather than the client going thru the whole SSL certificate process to obtain stale information , the public key is obtained in real time in the same process that obtains the ip-address). SSL then can be modified to rather than being certificate based (with stale, static information) it can be real-time public key based.
i.e. SSL has two parts ... 1) the domain name authentication ... which can be done with a trusted domain name infrastructure and 2) session key exchange ... which can be done in a number of ways, including using the trusted public key supplied by the trusted domain name infrastructure.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Invalid certificate on 'security' site. Newsgroups: alt.computer.security,comp.security,comp.security.misc Date: Thu, 22 Mar 2001 17:40:07 GMT"Spock" writes:
GAO: Government faces obstacles in PKI security adoption<
at:
https://www.garlic.com/~lynn/aepay6.htm#gaopki
https://www.garlic.com/~lynn/aepay6.htm#gaopki2
https://www.garlic.com/~lynn/aepay6.htm#gaopki3
https://www.garlic.com/~lynn/aepay6.htm#gaopki4
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Simpler technology Newsgroups: alt.folklore.computers Date: Fri, 23 Mar 2001 13:46:26 GMTeugene@cse.ucsc.edu (Eugene Miya) writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: WCs Payment Processing Newsgroups: ibm.software.paytech Date: Fri, 23 Mar 2001 16:55:37 GMTLance D Bader writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: database (or b-tree) page sizes Newsgroups: comp.arch Date: Fri, 23 Mar 2001 18:15:07 GMThandleym@ricochet.net (Maynard Handley) writes:
random URL
https://www.garlic.com/~lynn/95.html#5
https://www.garlic.com/~lynn/2001c.html#84
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: on-card key generation for smart card Newsgroups: sci.crypt Date: Fri, 23 Mar 2001 19:36:24 GMTChenghuai Lu writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: on-card key generation for smart card Newsgroups: sci.crypt Date: Fri, 23 Mar 2001 22:20:42 GMTPaul Rubin <phr-n2001@nightsong.com> writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: on-card key generation for smart card Newsgroups: sci.crypt Date: Sat, 24 Mar 2001 16:23:32 GMTDaniel James writes:
typically the issues are 8bit chip or 16bit chip ... or in some cases newer 32bit chips, the speed the chip is running at (although frequently it is 3.?Mhz, although newer chips are sometimes 10-15mhz), whether there is a crypto accelerator and what kind, and the quality of the random number generator.
the vast majority of smartcards in the market are 8bit chips, 3.?mhz, no crypto-accelerator, very poor random number quality and 8mins for 1024bit key-pair.
the circuit size of a 1024bit rsa crypto accelerator giving a 10 speedup has been on the order or larger of many of the 8bit chips in the market.
I don't believe i've seen any such accelerator in 8bit chips ... so it is a higher end, more expensive chip. Furthermore, for keygen it doesn't do much good unless there is a relatively decent random number generator ... which also makes the chip more expensive.
Now, one of the interesting things in the arena of authentication with public key digital signatures is the trade-off of RSA digital signatures vis-a-vis DSS digital signatures.
Effectively, RSA digital signatures have relied on a random nonce in the data being signed. Smartcards have tended towards RSA digital signature implementations because the PC or other unit creating the message can be relied on having a much better random number generator ... so that the random nonce is done as part of composing the message (rather than in the card as part of generating the signature).
One of the reasons that you tend to see fewer DSS-based smartcard implementations is that DSS requires the random number as part of the digital signature process (in much the same way, oncard quality random number is needed for oncard keygen, DSS also requires oncard quality random number for signature ... aka ... rather than relying on outside agency to insert random number in the body of the message, DSS incorporates the random number into the actual digital signing process). DSS signed messages can be 20bytes shorter (no random nonce) but the resulting signature is 20bytes longer.
The 8bit chips with external keygen, no crypto accelerator, poor quality random number, could implement digital signature authentication functions ... relying on external agency to reliably provide random number in the body of the message (and reliably offcard do original keygen).
Given a quality number source on the card (needed in any case for oncard keygen), DSS becomes much more practical and also reduces a possible attack where a card is fed messages that don't have the requisite random nonce.
Also, having a chip with a quality random number (sufficient for doing on-card keygen) could also be used to shift from a RSA-based signature to a DSS-based signature (minimizing card's integrity dependency on external sources).
And finally, EC-DSS with eliptical curve keys ... doesn't need the huge circuit area needed for 1024bit crypto-accelerator function i.e. if you have quality on-card random number generator sufficient for on-card keygen ... that also makes the card practical for DSS (& possibly minimizing infrastucture dependency on having external source provide card with messages incorporating random nonce), having quality random number for DSS, also enables EC-DSS ... which can eliminate the requirement for the large circuit area for the 1024bit crypto accelerator.
random url:
https://www.garlic.com/~lynn/aadsm2.htm#straw
https://www.garlic.com/~lynn/99.html#224
http://lists.commerce.net/archives/ansi-epay/199912/jpg00000.jpg
https://web.archive.org/web/20020228233550/http://lists.commerce.net/archives/ansi-epay/199912/jpg00000.jpg
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Verisign and Microsoft - oops Newsgroups: sci.crypt Date: Sun, 25 Mar 2001 16:09:39 GMTvjs@calcite.rhyolite.com (Vernon Schryver) writes:
random refs:
https://www.garlic.com/~lynn/aepay2.htm#fed
https://www.garlic.com/~lynn/aadsm3.htm#kiss10
https://www.garlic.com/~lynn/aepay3.htm#openclose
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: "Bootstrap" Newsgroups: alt.folklore.computers Date: Sun, 25 Mar 2001 19:26:26 GMTAnne & Lynn Wheeler writes:
how many out there have boot-cut jeans?
how many have a boot-cut tux?
how many were married in a boot-cut tux (& boots)?
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Drawing entities Newsgroups: comp.arch,comp.arch.storage Date: Sun, 25 Mar 2001 20:48:28 GMTJohn Bayko <"jbayko "@sk.sympatico.ca> writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: [Newbie] Authentication vs. Authorisation? Newsgroups: comp.security.misc Date: Thu, 29 Mar 2001 16:21:16 GMT"Ian Graham" <egertona-a-a-remove_for_ real_address-a-a-a-agraham@sympatico.ca> writes:
identity ... like in identity certificates ... tend to have some set of characteristics that are independent of context ... like name, address, etc (tends to be independent of attributes of whether or not the entity is entitled to the service or function). especially in retail situations this represents serious privacy issues (i.e. push to remove names from payment cards ... so that electronic transactions are as anonymous as cash).
Because name/address/etc (identity) tend to be independent of whether or not the entity is actually entitled/authorized for the service/function (especially in retail and other settings) ... and there are technologies available for authenticating w/o having to identify, there is bigger & bigger pushes to eliminate such unnecessary compromises of privacy.
COnversely, part of the reason that identity theft is such an issue ... is the use of identity related information for use in making the implicit jump to assumed authorization ... w/o using technologies that more directly authenticate whether the entity is entitled to the service/function (harvesting identity information is sufficient for being able to fraudulently obtain access to services/functions).
Some of this goes back to various issues associated with 3-factor authentication: 1) something you have, 2) something you know, and 3) something you are. Identity theft is possible by harvesting identity related information and then being able to demonstrate it in something you know situations (a PIN may be unique something you know for accessing a specific service, but frequently "mother's maiden name" may surfice also ... which represents some generic identity-related information that can be more easily harvested).
Eliminating identity-related information for authentication 1) improves privacy and 2) minimizes the fraudulent benefits of harvesting such information.
--
Anne & Lynn Wheeler | lynn@garlic.com, https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: What is PKI? Newsgroups: comp.security.misc Date: Tue, 27 Mar 2001 16:16:04 GMTPeterson2 writes:
The issue in a PKI information is how to manage distributed public keys (the mechanism by which the server/relying party) reliably obtains the clients public key, that will be used in authenticating the client's digital signature (and therefor authenticating the client's transmitted message).
One of the ways of the server/relying party reliably obtains the client's public key is via a digital certificate created by a trusted third party. The trusted third party manufactures a digital certificate containing the client's public key along with some other information that is relivant to the particular situation and signs the digital certificate with the TTP's private key. The server/relying party has the TTP's public key on file in an account record someplace ... where the TTP's public key was obtained by some reliable process.
In this TTP/certificate authority mode of digital signatures, the client composes the message with some relavent information (like userid, account number, date/time, etc), digital signs the message with their private key, and then sends the message appended with the digital signature and the relavent digital certificate.
The server/relying party receives the combined message, verifies the digital certificate with the public key of the TTP/CA on file, extracts the public key from the certificate and verifies the signed message and then compares something in the signed message with something in the certificate as well as looking up some account record at the server having to do with the client (i.e. anybody in the world could send a client message to your server, correctly signed, with a valid digital signature ... and it might not still be a valid client, it just might be some random person someplace in the world, aka even after all the digital signature, TTP, certificate stuff ... there still has to be some indication that the request still corresponds to a valid client).
To make it a real PKI, the public keys still have to be managed ... i.e. whether the public key of the client is still acceptable, the public key of the certificate authority is still acceptable, the particular client is still acceptable, etc. The majority of the CAs actually aren't PKIs ... in the sense they actually don't provide for management of the public keys in the infrastructure ... they purely perform the role of digital signature manufacturing.
A simpler PKI for managing public keys is something that I refer to as account authority digital signature or AADS (as opposed to CADS or certification authority digital signature). This can be implemented in conjunction with something like RADIUS (there was a demo of an AADS RADIUS at PC/EXPO a couple years ago in NYC).
Possibly 99.99999% of client authentication that goes on around the world today involves RADIUS ... usually in userid/password form. However, standard radius stupports other forms of authentication and it is relatively straight-forward to modify RADIUS to support account authority digital signatures.
In a typical RADIUS scenerio, your ISP registers your userid and your selected password for valid clients. They manage the authentication material as to valid clients, valid passwords, etc. In the AADS scenerio, an account may be flagged as having a public key registered instead of a password. The same administrative interface for managing valid userids and valid passwords is then available for managing clients, userids, and public keys (aka a real PKI in that it has real administrtive support for management of public keys as opposed to simple certificate manufacturing).
In this AADS RADIUS scenerio, the client creates a message with userid, date/time, etc, digital signs the message with the client's private key and transmits the message with the appended digital signature (and no certificate) to the server. The server pulls the userid out of the message, requests the corresponding information from RADIUS, using the client's public key returned from RADIUS, validates the client's digital signature ... and it includes real key management support for a PKI.
--
Anne & Lynn Wheeler | lynn@garlic.com, https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: What is PKI? Newsgroups: comp.security.misc Date: Wed, 28 Mar 2001 00:07:15 GMTPeterson2 writes:
While RADIUS has been primarily used by ISPs for initial connection authentication ... it is a generalized IETF standard and could also be supported by webservers and any number of other infrastructures for managing authentication.
Typically web servers have stub interface for implementing client authentication. Frequently this has been done with local RYO software that accesses a "flat" userid/password (or account/password) file. A much better exercise would be to implement a webserver client authentication using the RADIUS protocol and then an operation could manage all of their authentication requirements within the same general framework ... allowing password, digital signature and other forms of authentication all to co-exist simultaneously side-by-side (within the same administrative infrastructure).
--
Anne & Lynn Wheeler | lynn@garlic.com, https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: why the machine word size is in radix 8?? Newsgroups: alt.folklore.computers Date: Sat, 31 Mar 2001 15:04:59 GMTab528@FreeNet.Carleton.CA (Heinz W. Wiggeshoff) writes:
65/67 & below, all the machines were microcoded and that made it relatively easy to implement such instructions ... it was the high-end machines ... 75 and above that tended not to have the full compliment of instructions and could require software trap/simulation (modulo the 360/44).
the lowerer end machines tended to be more commercial where cobol, ED, EDMK, decimal instructions, etc ... were more significant. The higher end machines ... 75 and above that tended to be more numerical intensive and tended to short-change some of the decimal & related instructions.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: why the machine word size is in radix 8?? Newsgroups: alt.folklore.computers Date: Sat, 31 Mar 2001 15:24:09 GMTAnne & Lynn Wheeler writes:
For another undergraduate activity, I had available all the source of an IBM operating system for the 360/67 and I extensively modified and rewrote major sections.
The only low-level trap software in that software that took a "PROG1" exception from the kernel (i.e. undefined instruction interrupt) and performed simulation was for the SLT RPQ instruction defined by Lincoln Labs. Lincoln Labs had defined a search list hardware instruction that was available as a special RPQ ... some version of the operating system kernel were modified to use the instruction and a simulator was provided for machines that hadn't installed the RPQ).
random refs:
https://www.garlic.com/~lynn/94.html#2
https://www.garlic.com/~lynn/2000d.html#47
https://www.garlic.com/~lynn/2001c.html#15
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: April Fools Day Newsgroups: alt.folklore.computers Date: Sat, 31 Mar 2001 15:37:01 GMTjones@cs.uiowa.edu (Douglas W. Jones,201H MLH,3193350740,3193382879) writes:
random refs:
https://www.garlic.com/~lynn/internet.htm#0
https://www.garlic.com/~lynn/internet.htm#22
https://www.garlic.com/~lynn/2000c.html#46
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
g
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Economic Factors on Automation Newsgroups: comp.robotics.misc,comp.ai.philosophy,sci.econ,alt.folklore.computers Date: Sat, 31 Mar 2001 22:30:09 GMTEdward Flaherty writes:
In that sense a lot of people have lost their jobs in the most basic forms of food production ... and at the same time there is significantly more food production.
I can't say that less people starve-to-death ... there have been some numbers that indicate that the human tendency is to always produce more people than there is food ... if there is significantly more food ... it just takes longer for there to be more people than there is food supply (resulting eventually in much larger number of people starving to death). The analogy is computer programs evolve to consume all available (hardware) resources.
In any case, most of the nearly 40+ out of 49 people that use to be involved in basic day-to-day food production seem to now being doing something else.
More recently, there have been more (relatively) short-term dislocations. The 80%-99% of the population that were dedicated to food-production for the past hundreds/thousands of years ... obviously had to learn some other occupation. Some of the more recent (industrial) occupations that might have only spanned tens of years (rather than thousands) would have necessitated retraining programs within generations (rather than across generations) ... aka employment obsolescence and corresponding retraining has more individual impact if it is occurring to same individuals within generations rather than different individuals across generations.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: why the machine word size is in radix 8?? Newsgroups: alt.folklore.computers Date: Sun, 01 Apr 2001 00:25:30 GMTCharles Richmond writes:
the "owners" of the 360/370 instruction architecture enforced a very strong disapline across the company with regard to consistency, applicability, useability, and justification.
for instance, in order to get compare&swap into the architecture they required that a paradigm be invented for compare&swap that made it applicable to uniprocessor operation as well as multiprocessor operation. That resulted in the paradigm compare&swap definition for multi-threaded/tasking critical code sections (even when running in single processor configurations).
random refs (compare&swap was chosen because the mnemonic was the person's initials primarily responsible for the instruction):
https://www.garlic.com/~lynn/93.html#0 360/67, was Re: IBM's Project F/S ?
https://www.garlic.com/~lynn/93.html#14 S/360 addressing
https://www.garlic.com/~lynn/93.html#22 Assembly language program for RS600 for mutual exclusion
https://www.garlic.com/~lynn/94.html#02 Register to Memory Swap
https://www.garlic.com/~lynn/94.html#28 370 ECPS VM microcode assist
https://www.garlic.com/~lynn/94.html#45 SMP, Spin Locks and Serialized Access
https://www.garlic.com/~lynn/95.html#8a atomic load/store, esp. multi-CPU
https://www.garlic.com/~lynn/97.html#10 HELP! Chronology of word-processing
https://www.garlic.com/~lynn/97.html#19 Why Mainframes?
https://www.garlic.com/~lynn/98.html#16 S/360 operating systems geneaology
https://www.garlic.com/~lynn/98.html#40 Comparison Cluster vs SMP?
https://www.garlic.com/~lynn/98.html#8 Old Vintage Operating Systems
https://www.garlic.com/~lynn/99.html#176 S/360 history
https://www.garlic.com/~lynn/99.html#203 Non-blocking synch
https://www.garlic.com/~lynn/99.html#88 FIne-grained locking
https://www.garlic.com/~lynn/99.html#89 FIne-grained locking
https://www.garlic.com/~lynn/2000.html#80 Atomic operations ?
https://www.garlic.com/~lynn/2000e.html#4 Ridiculous
https://www.garlic.com/~lynn/2000e.html#22 Is a VAX a mainframe?
https://www.garlic.com/~lynn/2000e.html#25 Test and Set: Which architectures have indivisible instructions?
https://www.garlic.com/~lynn/2000g.html#16 360/370 instruction cycle time
https://www.garlic.com/~lynn/2000g.html#32 Multitasking and resource sharing
https://www.garlic.com/~lynn/2001b.html#33 John Mashey's greatest hits
https://www.garlic.com/~lynn/2001b.html#35 John Mashey's greatest hits
https://www.garlic.com/~lynn/2001b.html#40 John Mashey's greatest hits
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Imitation... Newsgroups: alt.folklore.computers Date: Sun, 01 Apr 2001 00:33:08 GMTjeffreyb@gwu.edu (Jeffrey Boulier) writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Very CISC Instuctions (Was: why the machine word size ...) Newsgroups: alt.folklore.computers Date: Sun, 01 Apr 2001 17:24:44 GMTCharles Richmond writes:
woodrum's tree instructions for 360/370 descendent
sorting instructions
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/A.7
A.7.1 Tree Format
Two instructions, COMPARE AND FORM CODEWORD and UPDATE TREE, refer to
a tree -- a data structure with a specific format. A tree consists of
some number (always odd) of consecutively numbered nodes. Node 1 is
the root of the tree. Every node except the root has one parent node
in the same tree. Every parent node has two son nodes. Every
even-numbered node is the leftson of its parent node, and every
odd-numbered node (except node 1) is the rightson of its parent node.
Division by two (ignoring remainder) of the node number gives the
parent node number. Nodes with sons are also called internal nodes,
and nodes without sons are called terminal nodes. Figure A-5
illustrates schematically a 21-node tree with arrows drawn from each
parent node to each son node.
the whole set of authorization related instructions in the descendants
of 360/370.
The original 360/370 had SVC ... supervisor call instruction with a numeric parameter that interrupted into the kernel and branched into some service based on the numeric paramemter. This required a huge processing overhead ... but eventualy evolved into a strong domain seperation between non-privileged (aka "problem" state) mode and privileged (aka "supervisor" state) mode.
A lot of 360/370 operating system services were provided by library routines that the application would call with a simple branch&link.
The authorization infrastructure was to allow some level of granular
privilege levels for system services that could be defined such that
application programs could call the library system services with
nearly the overhead of simple branch&link call but yet providing
transition to/from different privilege levels. Things include
authorization access to multiple address spaces (i.e. possibly at
least different address space for the system services and application
program).
5.7.1 Summary
These major functions are provided:
A maximum of 16 address spaces, including the instruction space, for
immediate and simultaneous use by a semiprivileged program; the
address spaces are specified by 16 new registers called access
registers.
Instructions for examining and changing the contents of the access
registers.
In addition, control and authority mechanisms are incorporated to
control these functions.
access registers:
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/5.5
misc. related
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/5.4
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/5.5
the relatively recent introduction of linkage-stack to 360/370 decendents
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/5.10
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/5.11
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/5.12
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Economic Factors on Automation Newsgroups: comp.robotics.misc,comp.ai.philosophy,sci.econ,alt.folklore.computers Date: Sun, 01 Apr 2001 19:14:40 GMTjeffreyb@gwu.edu (Jeffrey Boulier) writes:
It is possible that the societies involving stable replacement rates account for much more than 10-15% of the total population.
united nations site on world population trends:
http://www.undp.org/popin/wdtrends/wdtrends.htm
https://web.archive.org/web/20010801215639/http://www.undp.org/popin/wdtrends/wdtrends.htm
revised 2000 year report
http://www.un.org/esa/population/wpp2000h.pdf
...
world population rached 6.1 billion in mid-2000 and is currently
growing at an annual rate of 1.2% or 77 million people per year. Six
countries account for half the annual growth.
...
basically predicting something like 10billion people.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Very CISC Instuctions (Was: why the machine word size ...) Newsgroups: alt.folklore.computers Date: Mon, 02 Apr 2001 01:35:26 GMTnospam@nowhere.com (Steve Myers) writes:
however, the amount of information SVC communicated to the kernel as to the requested service was minimal and so also involved a lot of kernel processing.
I believe that work on program call & access register architecture stuff first started in the late '70s ... in part getting library & misc. subsystem stuff out of address space of the application while nearly preserving the efficiencies of branch & link subroutine call ... as well as some additional levels of privlege control (w/o having to do various/full switch thru the kernel).
Some amount of the Unix-like stuff with different applications in different address spaces chained together with pipes and message passing ... is do'able with program call & access register stuff (i.e. subroutine linkage/call to application in another address space w/o having to go thru the kernel).
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Very CISC Instuctions (Was: why the machine word size ...) Newsgroups: alt.folklore.computers Date: Mon, 02 Apr 2001 03:51:42 GMTCharles Richmond writes:
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/7.5.97
TRT D1(L,B1),D2(B2) [SS] ________ ________ ____ _/__ ____ _/__ | 'DD' | L | B1 | D1 | B2 | D2 | |________|________|____|_/__|____|_/__| 0 8 16 20 32 36 47 The bytes of the first operand are used as eight-bit arguments to select function bytes from a list designated by the second-operand address. The first nonzero function byte is inserted in general register 2, and the related argument address in general register 1.--
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Imitation... Newsgroups: alt.folklore.computers Date: Tue, 03 Apr 2001 14:50:50 GMTeugene@cse.ucsc.edu (Eugene Miya) writes:
https://www.garlic.com/~lynn/2001b.html#56
Alliant 171 Celerity just shipping Convex 200 ELXSI 80 FPS 365 Gould 6 Multiflow 5 Scientific 25 Computing Supertek not shipping yet--
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Very CISC Instuctions (Was: why the machine word size ...) Newsgroups: alt.folklore.computers Date: Tue, 03 Apr 2001 14:54:46 GMTcjt & trefoil writes:
random refs:
https://www.garlic.com/~lynn/2001d.html#23
https://www.garlic.com/~lynn/2001c.html#15
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Very CISC Instuctions (Was: why the machine word size ...) Newsgroups: alt.folklore.computers Date: Tue, 03 Apr 2001 15:00:05 GMT"GRIMBLE GRUMBLE" writes:
random refs:
https://www.garlic.com/~lynn/2000c.html#36
https://www.garlic.com/~lynn/2000c.html#37
https://www.garlic.com/~lynn/96.html#29
https://www.garlic.com/~lynn/96.html#30
https://www.garlic.com/~lynn/99.html#12
Interdata was one of the early non-PDP ports of unix.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Imitation... Newsgroups: alt.folklore.computers Date: Tue, 03 Apr 2001 15:15:06 GMTCharles Richmond writes:
random ref:
https://www.garlic.com/~lynn/96.html#30
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: solicit advice on purchase of digital certificate Newsgroups: comp.security.unix Date: Tue, 03 Apr 2001 15:35:41 GMTChrister Palm writes:
the problem is that when somebody goes to one of the certification authorities to get a domain name certificate ... the certification authorities have to contact some authoritative organization as to the validity of the owner of the domain name ... which is the same domain name infrastructure that has everybody worried about getting certificates to compensate for.
in part, for the benefit of the certification authorities, there are some integrity proposals for the domain name infrastructure which involve a domain name owner registering a public key at the same time they register their domain name.
The issue for the certification authorities, is if the domain name infrastructure is strengthen for their purposes ... it actually gets strengthen for everybody's purposes (i.e. less chance that when you want to go to www.xyz.com that you ever go any place else). A trusted domain name infrastructure for the use of certification authorities also pretty much negates the reasons that domain name certificates exist.
The other issue is that if the domain name owner registers their public key at the same time they register their domain name ... it is now possible for the domain name infrastructure to serve up the public key effectively using the same mechanism that is in place today for serving up ip-addresses (real time serving both trusted ip-address as well as trusted public keys ... w/o having to resort to certificates).
Also, an SSL/TLS implementation based on domain name infrastructure serving up trusted public keys would be a lot more efficient that the current certificate-based mechanism for serving up public keys.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Economic Factors on Automation Newsgroups: comp.robotics.misc,comp.ai.philosophy,sci.econ,alt.folklore.computers Date: Tue, 03 Apr 2001 18:36:58 GMTIan Stirling writes:
while both points argue that world population isn't likely to exceed available resource limits ... they differ significantly with regard to whether there are practical, relatively near term, resource limits that could significantly affect avg. standard of living of the world wide population.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Flash and Content address memory Newsgroups: comp.arch Date: Tue, 03 Apr 2001 18:58:42 GMTegor writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Economic Factors on Automation Newsgroups: comp.robotics.misc,comp.ai.philosophy,sci.econ,alt.folklore.computers Date: Wed, 04 Apr 2001 11:37:43 GMTGrinch writes:
--
Anne & Lynn Wheeler | lynn@garlic.com, https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Flash and Content address memory Newsgroups: comp.arch Date: Thu, 05 Apr 2001 11:32:05 GMTegor writes:
+content +addressable +memory
5900 pages found
--
Anne & Lynn Wheeler | lynn@garlic.com, https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: solicit advice on purchase of digital certificate Newsgroups: comp.security.unix Date: Wed, 04 Apr 2001 12:08:33 GMTChrister Palm writes:
Since the domain name infrastructure ... back up into the registration authority ... is the ultimate authoritative reference for domain name ownership ... it is possible to check with as many places as you want ... and they still all have to refer back to the authoritative agency.
random refs
https://www.garlic.com/~lynn/aepay4.htm#dnsinteg1
https://www.garlic.com/~lynn/aepay4.htm#dnsinteg2
https://www.garlic.com/~lynn/2000e.html#38
https://www.garlic.com/~lynn/aadsmore.htm#seecurevid
> I guess you are talking about DNSSEC?
> Yes that is a very interesting initiative.
>
> True, although most certificates used by e-business websites are not
> simple domain-name certificates, but also has the organization identity
> and address verified and filed.
however, there is no "protocol" that cross-checks any of the other
information, given a domain name hijack, anything could be put in the
rest of the fields (as far as requesting a certificate ... and all of
it could be perfectly valid and also useless).
> Right. This, however, effectively makes the DNS operators into "CA's"
> that needs to be credable enough to be generally trusted if the purpose
> would be served.
> Many DNS operators may not be ready to mantle such a responsibility.
then merchants could choose to register with ones that are ... for at
least the problem of domain name hijacking
> Yes, given that they will also store and make available verified
> information about the domain owners together with the keys.
>
> Unfortunately, I guess this will not happen overnight.
> Here in Sweden, as well in some other countries, the government are
> currently funding investigations on how they could implement a national
> DNSSEC infrastructure to meet these goals.
the basic problem is that the top of the domain name system hierarchy
is the domain name registration ... which is the ultimate
authoratative agency for domain name ownership ... if the domain name
is hijacked there, a CA could check with thousands of other agencies
... but they would still all have to rely on the domain name
authoritative agency as to the owner of the domain name.
however, fixing even the domain name hijacking problem with registering public keys with the domain name ... puts the public key in real time database with the domain name ... enabling it to be served along with any of the other real time information supported by DNS ... including ip-address.
the current merchant certificate stuff didn't happen overnight either ... see first two references below
random urls
https://www.garlic.com/~lynn/aadsm5.htm#asrn2 Assurance, e-commerce, and some x9.59 ... fyi
https://www.garlic.com/~lynn/aadsm5.htm#asrn3 Assurance, e-commerce, and some x9.59 ... fyi
https://www.garlic.com/~lynn/2001c.html#8 Server authentication
https://www.garlic.com/~lynn/2001c.html#9 Server authentication
https://www.garlic.com/~lynn/2000c.html#32 Request for review of "secure" storage scheme
https://www.garlic.com/~lynn/2000e.html#50 Why trust root CAs ?
https://www.garlic.com/~lynn/2001c.html#34 PKI and Non-repudiation practicalities
https://www.garlic.com/~lynn/2001c.html#62 SSL weaknesses
https://www.garlic.com/~lynn/2001d.html#8 Invalid certificate on 'security' site.
https://www.garlic.com/~lynn/aadsm3.htm#kiss5 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))
https://www.garlic.com/~lynn/aadsm3.htm#kiss7 KISS for PKIX. (Was: RE: ASN.1 vs XML (used to be RE: I-D ACTION :draft-ietf-pkix-scvp- 00.txt))
https://www.garlic.com/~lynn/aadsm4.htm#2 Public Key Infrastructure: An Artifact...
https://www.garlic.com/~lynn/aadsm4.htm#3 Public Key Infrastructure: An Artifact...
https://www.garlic.com/~lynn/aadsm4.htm#4 Public Key Infrastructure: An Artifact...
https://www.garlic.com/~lynn/aadsm4.htm#8 Public Key Infrastructure: An Artifact...
https://www.garlic.com/~lynn/aepay3.htm#openclose open CADS and closed AADS
https://www.garlic.com/~lynn/aepay3.htm#votec (my) long winded observations regarding X9.59 & XML, encryption and certificates
https://www.garlic.com/~lynn/aepay6.htm#gaopki4 GAO: Government faces obstacles in PKI security adoption
--
Anne & Lynn Wheeler | lynn@garlic.com, https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: IBM was/is: Imitation... Newsgroups: alt.folklore.computers Date: Sun, 08 Apr 2001 15:36:55 GMTeugene@cse.ucsc.edu (Eugene Miya) writes:
A trivial example was some situation involving trade secrets and something about the amount of security needed to be proportional to the perceived value ... something valued at >$10b had to have significantly more security than something valued at $10m (otherwise it fell in some category about swimming pools being attractive nuisance). However most times you couldn't really predict which would be $10m and which would be >$10b .... so the $10b+ security had to be applied to everything from the start.
The idea was born of IBU (independent business unit) that was suppose to be free from all the normal business processes. One downside was IBUs being hosted on existing plant facilities. I remember some argument between some IBU with a plant manager asserting that all the members of the IBU had to observe a whole lot of business processes & practices. The counter claim was that this was an IBU and was free of all the standard business processes & practices. The plant manager's reply was an IBU might be free of a lot of other business processes & practices but not his (and it was difficult to find some business process owner that believed it was their processes that an IBU didn't have to follow).
There was also a case of a product using a different component from another plant. As part of getting interoperability, there was a desire to make that component available to outside companies. There was a rule of thumb about price markup (whether an external sale or internal transfer). In order to deliver this specific component to outside corporations, it had to pass through several business units, each one expecting to apply the markup guideline. Final component delivery was going to have over a 1000% markup.
There was the joke about the NSF evaluation of the backbone Anne & I was running ... where there was something about what we had was at least five years ahead of bid proposals to build something new for NSFNET .... that it takes at least five years (going to effectively infinity for some things) for new technology to make it through all the processes and out the door.
random ref:
https://www.garlic.com/~lynn/internet.htm#0
some thread-drift ... is it imitation or offspring
a pc networking company in provo
https://www.garlic.com/~lynn/2000g.html#40
.... the 229-3174 360/67 "blue card" that I found in boxes ... has the name "Edward J. Mosher" stamped across the top of the front (maybe someday i'll get a scanner and put it up on garlic).
cambridge had a habit of trying to have acronyms that were people's initials. I've mentioned before that compare and swap was Charlie's initials. I've also mentioned that GML were initials of people at cambridge ... where GML begate SGML which begate HTML which begate XML, ECML, FSML, ... and some number of other MLs. Well Mosher is the "M" in all of these MLs. To tie it back to the thread ... are all these MLs imitations of the original (or offspring)?
random ref:
https://www.garlic.com/~lynn/94.html#43 Bloat, elegance, simplicity and other irrelevant concepts
https://www.garlic.com/~lynn/94.html#55 How Do the Old Mainframes Compare to Today's Micros?
https://www.garlic.com/~lynn/96.html#24 old manuals
https://www.garlic.com/~lynn/97.html#9 HELP! Chronology of word-processing
https://www.garlic.com/~lynn/97.html#26 IA64 Self Virtualizable?
https://www.garlic.com/~lynn/98.html#16 S/360 operating systems geneaology
https://www.garlic.com/~lynn/98.html#21 Reviving the OS/360 thread (Questions about OS/360)
https://www.garlic.com/~lynn/99.html#42 Enter fonts (was Re: Unix case-sensitivity: how did it originate?
https://www.garlic.com/~lynn/99.html#43 Enter fonts (was Re: Unix case-sensitivity: how did it originate?
https://www.garlic.com/~lynn/99.html#91 Documentation query
https://www.garlic.com/~lynn/99.html#197 Computing As She Really Is. Was: Re: Life-Advancing Work of Timothy Berners-Lee
https://www.garlic.com/~lynn/2000.html#8 Computer of the century
https://www.garlic.com/~lynn/2000.html#34 IBM 360 Manuals on line ?
https://www.garlic.com/~lynn/2000e.html#23 Is Tim Berners-Lee the inventor of the web?
https://www.garlic.com/~lynn/2001c.html#15 OS/360 (was LINUS for S/390)
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Economic Factors on Automation Newsgroups: comp.robotics.misc,comp.ai.philosophy,sci.econ,alt.folklore.computers Date: Sun, 08 Apr 2001 16:43:52 GMTCarlos Antunes writes:
there is the whole thread of the US automobile industry and foriegn competition.
interesting side effect that was written up (I believe i saw it in washington post) where quotas was established for inexpensive foriegn imports. the foriegn companies then apparently realized that given the quotas they would max. the quota almost regardless of the price of the car ... so they quickly changed their product offering to be something like three times more expensive (and significantly more profit).
One point of the article was that w/o the downward price pressure (of lots of cheap imports) that it allowed american industry to significantly raise their prices w/o having to actually change their product ... and it raised the issue if the gov. shouldn't impose an 100% "unearned" profit tax on the american industry.
Another side-effect was that the (then) current industry standard was it took seven years elapsed time to produce a new automobile. Effectively as part of the product re-organization, foreign competition invented new procedures where they could produce a new offering in three years elapsed time. This innovation resulted in foreign competition being able to adapt to changing consumer demands better than twice as fast as domestic industry. In effect, the us industry was on its way to obsoleting themselves ... by the time it had come out with a new offering ... it might be already obsolete and market had gone through two new generations.
this isn't simply a question of automation but also innovation.
something strictly based on commodity hourly labor ... if a new procedure cut the time in half to produce something, then a theory of commodity hourly labor would result in them only getting half as much.
Applying the theory of commodity hourly labor at the organization level would imply that the organization would only receive half as much for doing something in half the time.
the issue of innovation (in conjunction with automation) is having significant effect on labor. Lots of labor has been in association with capital intensive manufacturing plants. Many of the manufacturing plants have had 20-100 year lifetimes ... resulting in little labor disruption over long periods of time.
Innovation is not only making specific products (and associated labor training) obsolete but has also started making the associated manufacturing plants obsolete. This is possibly more readily seen in chip fabrication plants, where capital costs are in the multi-billion dollar range and life-expectancy can be 2-3 years (initial plant capital costs have to be amortized over the chips produced in the life-time of the plant ... and these costs can dominate all other factors).
In more traditional manufacturing there has been move focus on automation ... but the issue of innovation can be as or more significant. Much of cutting 7years to 3years elapsed time for new product was associated with business process innovation (as it was anything to do with plant automation) The 3year elapsed time for new product is as much labor as any final assembly manufacturing process.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: IBM was/is: Imitation... Newsgroups: alt.folklore.computers Date: Sun, 08 Apr 2001 16:10:42 GMTAnne & Lynn Wheeler writes:
random refs:
https://www.garlic.com/~lynn/2000.html#9 Computer of the century
https://www.garlic.com/~lynn/2000b.html#55 Multics dual-page-size scheme
https://www.garlic.com/~lynn/2000e.html#49 How did Oracle get started?
https://www.garlic.com/~lynn/2000f.html#16 [OT] FS - IBM Future System
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: A beautiful morning in AFM. Newsgroups: alt.folklore.military Date: Sun, 08 Apr 2001 17:27:50 GMTBobMac writes:
at least by the mid-80s the individuals that had received their indoctrination into organizational management during WWII were starting to dominate executive positions (in both commerical and non-commercial worlds); and their organizational style reflected the rigidly controlled, top-down style needed to handle huge numbers of individuals with scant training and no experience (regardless of the actual composition of the organization).
& of course, random ref:
http://www.belisarius.com/
https://web.archive.org/web/20010722050327/http://www.belisarius.com/
https://www.garlic.com/~lynn/94.html#8
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: anyone have digital certificates sample code Newsgroups: sci.crypt Date: Sun, 08 Apr 2001 20:51:06 GMT"normang" writes:
aka the registration authority part of registering public key w/o having to do the certification authority piece (i.e. since they are internal they presumably don't need 3rd party certification) ... and/or w/o having to implement offline trust propagation (which is the fundamental purpose of issuing a certificate .... i.e. trust propagation that has been certified into offline environments).
random refs:
https://www.garlic.com/~lynn/aadsm2.htm#pkikrb PKI/KRB
https://www.garlic.com/~lynn/aadsm3.htm#kiss7 KISS for PKIX. (Was: RE: ASN.1 vs XML (used to be RE: I-D ACTION :draft-ietf-pkix-scvp- 00.txt))
https://www.garlic.com/~lynn/aadsm4.htm#7 Public Key Infrastructure: An Artifact...
https://www.garlic.com/~lynn/aadsm4.htm#9 Thin PKI won - You lost
https://www.garlic.com/~lynn/aadsm4.htm#10 Thin PKI won - You lost
https://www.garlic.com/~lynn/aadsm5.htm#shock2 revised Shocking Truth about Digital Signatures
https://www.garlic.com/~lynn/aadsmail.htm#complex AADS/CADS complexity issue
https://www.garlic.com/~lynn/aepay2.htm#cadis disaster recovery cross-posting
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Just a guick remembrance of where we all came from Newsgroups: comp.arch Date: Mon, 09 Apr 2001 01:30:14 GMTJim Purcell writes:
I did similar operation later ... but possibly with only five tubes (instead of 10-15 tubes).
I don't know the service/cycle time for the tubes ... but when i got to school they still had a 709 with thousands of tubes. TVs might only have service time of hr or two a day ... the 709 tended to be powered on constantly and there were at least a couple tubes a week that went
one 709 might have the equivalent number of tubes of 1000 or more audio amplifiers, a 709 problem was the equivalent of any one tube in any one of 1000 or more amplifiers having a problem.
a 709 with maybe 20,000? tubes and for argument sake, each tube had a life-time of five years. If it was straight MTBF with uniform distribution, then five years has about 44,000hrs and you might expect some tube failure every two hrs. However, the distribution should be skewed towards higher failure rates later in life cycle ... so a 709 that had been operating for more than five years would be expected to experience even a higher failure rate (some tube failing every hr or so).
Some tube (out of 20,000?) after more than five years of nearly continuous operation ... failing every day or so seems to be very reliable tubes (i.e. less than 1/10th the failure rate calculated so maybe more like MTBF of 50+ years ... with uniform distribution)
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: VTOC position Newsgroups: bit.listserv.ibm-main Date: Tue, 10 Apr 2001 15:04:43 GMTrush-main@21CN.COM (Rush Yan) writes:
I presented some results at SHARE, that for sample job stream the elapsed time was reduced by 60%-70% compared to a normal sysgen. The problem was that normal PTF activity replacing PDS members could degrade system performed by a factor of 2 over a period of six months.
IBM introduced VTOC placement with MVT15/16 that provided some additional optimization for ordering arm seek distances.
random refs:
https://www.garlic.com/~lynn/2000d.html#50
https://www.garlic.com/~lynn/2001.html#26
--
Anne & Lynn Wheeler | lynn@garlic.com, https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: VTOC position Newsgroups: bit.listserv.ibm-main Date: Tue, 10 Apr 2001 16:17:29 GMTAnne & Lynn Wheeler writes:
note that the original published numbers for the 3880-13 cache hit ratios was somewhat biased. they showed a 90% hit rate for certain types of activity. this activity was sequential access with 10 records per track ... and of course, the first reference to a record on the track would be a miss and bring in the whole track. the subsequent 9 sequential record reads were all "hits" ... resulting in 9 hits out of 10 or 90% cache hit ratio. however, the same effect could have been obtained with 10 record buffering and chained i/o w/o even needing a cache.
--
Anne & Lynn Wheeler | lynn@garlic.com, https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: SSL certificate question... Newsgroups: comp.security.misc Date: Mon, 09 Apr 2001 22:07:07 GMT"The§eidh" writes:
--
Anne & Lynn Wheeler | lynn@garlic.com, https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: OT Re: A beautiful morning in AFM. Newsgroups: alt.folklore.military Date: Fri, 13 Apr 2001 22:52:25 GMTjimlillie@aol.com (JimLillie) writes:
what it actually said was that each person had to go to the site security officer to obtain the one & only valid password that met all the restrictions and conditions.
random ref:
https://www.garlic.com/~lynn/99.html#52
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: OT Re: A beautiful morning in AFM. Newsgroups: alt.folklore.military Date: Sat, 14 Apr 2001 01:43:12 GMTthe original ....
CORPORATE DIRECTIVE NUMBER 84-570471 April 1, 1984
In order to increase the security of all IBM computing facilities, and to avoid
the possibility of unauthorized use of these facilities, new rules are being put
into effect concerning the selection of passwords. All users of IBM computing
facilities are instructed to change their passwords to conform to these rules
immediately.
RULES FOR THE SELECTION OF PASSWORDS:
1. A password must be at least six characters long, and must not contain two
occurrences of a character in a row, or a sequence of two or more characters
from the alphabet in forward or reverse order.
Example: HGQQXP is an invalid password.
GFEDCB is an invalid password.
2. A password may not contain two or more letters in the same position as any
previous password.
Example: If a previous password was GKPWTZ, then NRPWHS would be invalid
because PW occurs in the same position in both passwords.
3. A password may not contain the name of a month or an abbreviation for a
month.
Example: MARCHBC is an invalid password.
VWMARBC is an invalid password.
4. A password may not contain the numeric representation of a month.
Therefore, a password containing any number except zero is invalid.
Example: WKBH3LG is invalid because it contains the numeric representation
for the month of March.
5. A password may not contain any words from any language. Thus, a password
may not contain the letters A, or I, or sequences such as AT, ME, or TO
because these are all words.
6. A password may not contain sequences of two or more characters which are
adjacent to each other on a keyboard in a horizontal, vertical or diagonal
direction.
Example: QWERTY is an invalid password.
GHNLWT is an invalid password because G and H are horizontally
adjacent to each other.
HUKWVM is an invalid password because H and U are diagonally
adjacent to each other.
7. A password may not contain the name of a person, place or thing.
Example: JOHNBOY is an invalid password.
Because of the complexity of the password selection rules, there is actually only
one password which passes all the tests. To make the selection of this password
simpler for the user, it will be distributed to all managers. All users are
instructed to obtain this password from his or her manager and begin using it
immediately.
--
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: April Fools Day Newsgroups: alt.folklore.computers Date: Sat, 14 Apr 2001 02:07:24 GMT"Donald Tees" writes:
april 1st was sunday ... somebody printed this on corporate letterhead and posted it on all the bulletin boards over the weekend. many people reading it on monday didn't catch on. later all corporate letterhead paper was locked in cabinets.
CORPORATE DIRECTIVE NUMBER 84-570471 April 1, 1984
In order to increase the security of all IBM computing facilities, and to avoid
the possibility of unauthorized use of these facilities, new rules are being put
into effect concerning the selection of passwords. All users of IBM computing
facilities are instructed to change their passwords to conform to these rules
immediately.
RULES FOR THE SELECTION OF PASSWORDS:
1. A password must be at least six characters long, and must not contain two
occurrences of a character in a row, or a sequence of two or more characters
from the alphabet in forward or reverse order.
Example: HGQQXP is an invalid password.
GFEDCB is an invalid password.
2. A password may not contain two or more letters in the same position as any
previous password.
Example: If a previous password was GKPWTZ, then NRPWHS would be invalid
because PW occurs in the same position in both passwords.
3. A password may not contain the name of a month or an abbreviation for a
month.
Example: MARCHBC is an invalid password.
VWMARBC is an invalid password.
4. A password may not contain the numeric representation of a month.
Therefore, a password containing any number except zero is invalid.
Example: WKBH3LG is invalid because it contains the numeric representation
for the month of March.
5. A password may not contain any words from any language. Thus, a password
may not contain the letters A, or I, or sequences such as AT, ME, or TO
because these are all words.
6. A password may not contain sequences of two or more characters which are
adjacent to each other on a keyboard in a horizontal, vertical or diagonal
direction.
Example: QWERTY is an invalid password.
GHNLWT is an invalid password because G and H are horizontally
adjacent to each other.
HUKWVM is an invalid password because H and U are diagonally
adjacent to each other.
7. A password may not contain the name of a person, place or thing.
Example: JOHNBOY is an invalid password.
Because of the complexity of the password selection rules, there is actually only
one password which passes all the tests. To make the selection of this password
simpler for the user, it will be distributed to all managers. All users are
instructed to obtain this password from his or her manager and begin using it
immediately.
--
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: VM & VSE news Newsgroups: bit.listserv.vmesa-l Date: Fri, 13 Apr 2001 21:52:26 -0600"Tom Duebusch" writes:
https://www.garlic.com/~lynn/94.html#21 370 ECPS VM microcode assist
https://www.garlic.com/~lynn/94.html#27 370 ECPS VM microcode assist
https://www.garlic.com/~lynn/94.html#28 370 ECPS VM microcode assist
https://www.garlic.com/~lynn/94.html#51 Rethinking Virtual Memory
https://www.garlic.com/~lynn/95.html#3 What is an IBM 137/148 ???
https://www.garlic.com/~lynn/97.html#20 Why Mainframes?
https://www.garlic.com/~lynn/98.html#26 Merced & compilers (was Re: Effect of speed ... )
https://www.garlic.com/~lynn/99.html#90 CPU's directly executing HLL's (was Which programming languages)
https://www.garlic.com/~lynn/99.html#116 IBM S/360 microcode (was Re: CPU taxonomy (misunderstood RISC))
https://www.garlic.com/~lynn/99.html#187 Merced Processor Support at it again . . .
https://www.garlic.com/~lynn/99.html#204 Core (word usage) was anti-equipment etc.
https://www.garlic.com/~lynn/99.html#209 Core (word usage) was anti-equipment etc.
https://www.garlic.com/~lynn/2000.html#8 Computer of the century
https://www.garlic.com/~lynn/2000.html#12 I'm overwhelmed
https://www.garlic.com/~lynn/2000.html#63 Mainframe operating systems
https://www.garlic.com/~lynn/2000.html#70 APL on PalmOS ???
https://www.garlic.com/~lynn/2000.html#78 Mainframe operating systems
https://www.garlic.com/~lynn/2000.html#86 Ux's good points.
https://www.garlic.com/~lynn/2000b.html#50 VM (not VMS or Virtual Machine, the IBM sort)
https://www.garlic.com/~lynn/2000b.html#51 VM (not VMS or Virtual Machine, the IBM sort)
https://www.garlic.com/~lynn/2000c.html#19 Hard disks, one year ago today
https://www.garlic.com/~lynn/2000c.html#50 Does the word "mainframe" still have a meaning?
https://www.garlic.com/~lynn/2000c.html#68 Does the word "mainframe" still have a meaning?
https://www.garlic.com/~lynn/2000c.html#75 Does the word "mainframe" still have a meaning?
https://www.garlic.com/~lynn/2000c.html#76 Is a VAX a mainframe?
https://www.garlic.com/~lynn/2000c.html#83 Is a VAX a mainframe?
https://www.garlic.com/~lynn/2000d.html#12 4341 was "Is a VAX a mainframe?"
https://www.garlic.com/~lynn/2000d.html#20 S/360 development burnout?
https://www.garlic.com/~lynn/2000d.html#60 "all-out" vs less aggressive designs (was: Re: 36 to 32 bit transition)
https://www.garlic.com/~lynn/2000d.html#82 "all-out" vs less aggressive designs (was: Re: 36 to 32 bit transition)
https://www.garlic.com/~lynn/2000e.html#6 Ridiculous
https://www.garlic.com/~lynn/2000e.html#54 VLIW at IBM Research
https://www.garlic.com/~lynn/2000e.html#56 Why not an IBM zSeries workstation?
https://www.garlic.com/~lynn/2000f.html#37 OT?
https://www.garlic.com/~lynn/2000f.html#55 X86 ultimate CISC? No. (was: Re: "all-out" vs less aggressive designs)
https://www.garlic.com/~lynn/2000f.html#57 X86 ultimate CISC? No. (was: Re: "all-out" vs less aggressive designs)
https://www.garlic.com/~lynn/2000f.html#59 360 Architecture, Multics, ... was (Re: X86 ultimate CISC? No.)
https://www.garlic.com/~lynn/2000f.html#66 360 Architecture, Multics, ... was (Re: X86 ultimate CISC? No.)
https://www.garlic.com/~lynn/2000f.html#78 TSS ancient history, was X86 ultimate CISC? designs)
https://www.garlic.com/~lynn/2000g.html#7 360/370 instruction cycle time
https://www.garlic.com/~lynn/2000g.html#8 360/370 instruction cycle time
https://www.garlic.com/~lynn/2000g.html#11 360/370 instruction cycle time
https://www.garlic.com/~lynn/2000g.html#21 360/370 instruction cycle time
https://www.garlic.com/~lynn/2001.html#38 Competitors to SABRE?
https://www.garlic.com/~lynn/2001b.html#29 z900 and Virtual Machine Theory
https://www.garlic.com/~lynn/2001b.html#40 John Mashey's greatest hits
https://www.garlic.com/~lynn/2001b.html#42 John Mashey's greatest hits
https://www.garlic.com/~lynn/2001b.html#49 PC Keyboard Relics
https://www.garlic.com/~lynn/2001b.html#83 Z/90, S/390, 370/ESA (slightly off topic)
https://www.garlic.com/~lynn/2001c.html#1 Z/90, S/390, 370/ESA (slightly off topic)
https://www.garlic.com/~lynn/2001c.html#2 Z/90, S/390, 370/ESA (slightly off topic)
https://www.garlic.com/~lynn/2001c.html#3 Z/90, S/390, 370/ESA (slightly off topic)
https://www.garlic.com/~lynn/2001c.html#87 "Bootstrap"
https://www.garlic.com/~lynn/2001d.html#22 why the machine word size is in radix 8??
https://www.garlic.com/~lynn/2001d.html#26 why the machine word size is in radix 8??
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: VM & VSE news Newsgroups: bit.listserv.vmesa-l Date: Fri, 13 Apr 2001 21:57:21 -0600"Tom Duebusch" writes:
https://www.garlic.com/~lynn/2001d.html#35
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Pentium 4 Prefetch engine? Newsgroups: comp.arch Date: Sat, 14 Apr 2001 15:49:52 GMTnmm1@cus.cam.ac.uk (Nick Maclaren) writes:
"supervisor services" then wrappered a bunch of library stuff around EXCP. This was supervisor I/O library services that would be dynamically loaded/specified at file open time. supervisor services was complex ... not so much that any one service was complicated but because there were so many different flavors.
one of the simplest was "move mode" get/put where the supervisor library services handled all synchronizing issues and moving data from/to program data buffer and internal i/o buffers. Then there was "locate mode" where pointers were passed back and forth between application program and internal i/o buffers.
then you could get into read/write where application program had control of WAIT/POST ECB synchronization services.
disk I/O could have a lot of additional flavors where the library services supported sequential and non-sequential access along with various forms of indexes.
In addition, library services supported both fixed-length and variable-length records. Instead of having implicit lengths (aka the existing C language services that are the root of very large percentage of security/integrity exploits over the years), variable-length records had explicit lengths.
random refs:
https://www.garlic.com/~lynn/aadsm5.htm#asrn4
https://www.garlic.com/~lynn/aadsm5.htm#asrn1
in part because there was so much overhead at file-open time, a number of subsystem monitors sprung up ... which provided a restricted subset of services against files that had effectively been pre-opened. This predated the DBMS implementations which effectively were a follow-on that added justifications like integrity and transaction semeantics for implementing subsystem monitors.
A significant amount of business critical commercial data processing continue to be deployed on some of these subsystem montiors that appeared in the late '60s or early '70s (like CICS and IMS).
random refs:
https://www.garlic.com/~lynn/99.html#71
https://www.garlic.com/~lynn/2001d.html#5
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Impact of Internet Newsgroups: comp.arch,comp.lang.java.advocacy,comp.object,comp.os.linux.advocacy,comp.os.ms-windows.nt.advocacy,comp.theory,misc.invest.stocks Date: Sat, 14 Apr 2001 15:56:54 GMT"2 + 2" <2-2@web.com> writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Very CISC Instuctions (Was: why the machine word size ...) Newsgroups: alt.folklore.computers Date: Mon, 16 Apr 2001 15:04:24 GMTStan Sieler writes:
when doing analysis of unix & C language in the '80s for high availability product, C language convention of implicit lengths was identified as possibly increasing buffer problems (& exploits) by a couple orders of magnitude (at least to what we were familiar with).
reference to assurance panel discussion i was on at Intel Developer's conference:
https://www.garlic.com/~lynn/aadsm5.htm#asrn4
random refs:
https://www.garlic.com/~lynn/ansiepay.htm#theory Security breach raises questions about Internet shopping
https://www.garlic.com/~lynn/99.html#44 Internet and/or ARPANET?
https://www.garlic.com/~lynn/99.html#219 Study says buffer overflow is most common security bug
https://www.garlic.com/~lynn/2000.html#25 Computer of the century
https://www.garlic.com/~lynn/2000.html#30 Computer of the century
https://www.garlic.com/~lynn/2000b.html#17 ooh, a real flamewar :)
https://www.garlic.com/~lynn/2001b.html#58 Checkpoint better than PIX or vice versa???
https://www.garlic.com/~lynn/2001c.html#32 How Commercial-Off-The-Shelf Systems make society vulnerable
https://www.garlic.com/~lynn/2001c.html#38 How Commercial-Off-The-Shelf Systems make society vulnerable
https://www.garlic.com/~lynn/2001c.html#66 KI-10 vs. IBM at Rutgers
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Pentium 4 Prefetch engine? Newsgroups: comp.arch Date: Mon, 16 Apr 2001 15:26:02 GMTnmm1@cus.cam.ac.uk (Nick Maclaren) writes:
For small buffer sizes, buffer copies can be lost in the rest of the protocol pathlength. For 8k byte or larger sized buffer copies the processor time for the data movement can start to dominate the pathlength. Some protocol stacks have been tuned to approach hardware thruput at expense of dedicating the processor.
a simple check for high i/o efficiencies with large amounts of data is 1) near 100 percent hardware transfer rates and 2) near zero processor utilization (i.e. which would leave most of the processor available for actually executing some application code that might deal with the data) and 3) application space code (either in application or libraries) utilizes some serialization primitives.
somewhat at issue is w/o some sort of buffer copy, there is either no concurrent application execution or there needs to be some application space synchronization code (i.e. application space code is either blocked during buffer transfers or application space code has to utilize some sort of serialization primitives with multiple buffering logic).
there are some hacks that can be done in this area manipulating virtual memory constructs .... application space still needs some amount of multiple buffering logic ... but there are games that can be played with implicit buffer serialization by manipulating virtual memory (w/o needing explicit the application space code to explicitly execute serialization operations).
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: VTOC/VTOC INDEX/VVDS and performance (expansion of VTOC position) Newsgroups: bit.listserv.ibm-main Date: Mon, 16 Apr 2001 15:57:50 GMTedgould@WORLDNET.ATT.NET (Edward Gould) writes:
I got to shoot a problem at at large retail chain in the early '80s .... all data processing for all regions, branches, stores, were done at hdqtrs with multiple machines sharing common library on 3330 drive.
they were experiencing random slow downs across some or all the machines.
I came into a class room that had foot high printed output of MVS performance data completely covering half dozen or so class room tables.
cpu went up, cpu went down, some drive activity went up, some drive activity went down. After a couple hrs, I noticed a slight correlation between periods as identified as "slow" with a consistent utilization on a particular 3330 (out of maybe 50-60 drives) at 6 I/Os per second.
Turns out that it was the common library drive, the library PDS had a three cylinder directory; the "consistent" drive I/O rate at 6/sec was peak saturation ... 19 tracks, multi-track search, 3600RPM, 60 rotations per second; about 1/3 of second I/O for search, plus a member read or two.
Nobody was looking for totally saturated device with long queues when peak i/o rate for the drive was 6.5/sec (aggregate, across all processors in the complex).
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: VTOC/VTOC INDEX/VVDS and performance (expansion of VTOC position) Newsgroups: bit.listserv.ibm-main Date: Mon, 16 Apr 2001 16:36:17 GMTAnne & Lynn Wheeler writes:
.... and nobody informed me beforehand about the common library until i started asking questions about the particular drive and why did it seeem to have a consistent uniform 6 i/os per second correlating with periods of "slow-down" (i.e. first couple passes thru the data didn't turn up anything .... so i had to ask for them to specify what periods were they "subjectively" experiencing slow-down) ... while the rest of the time it had i/o rates in the 1-5 per second range.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: OT Re: A beautiful morning in AFM. Newsgroups: alt.folklore.military Date: Mon, 16 Apr 2001 16:50:05 GMTjimlillie@aol.com (JimLillie) writes:
there was also a write up done on frequency of changing passwords resulting in the postit note scenerios .... more complex, less frquently changed passwords were more secure because of various human factors.
the rest of the write-up correlated password changing with changing combinations for combination locks and keys for keyed locks; i.e. security officers were required to change combinations in all combination locks for the site at least twice an hour ... and that keyed locks at the site had to be rekeyed and new keys issued twice a minute (desks, doors, cabinets, etc).
individuals had to always be present to receive the twice a minute new keying material and also had to later be able to account for all keying material received.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Pentium 4 Prefetch engine? Newsgroups: comp.arch Date: Mon, 16 Apr 2001 17:12:32 GMTAnne & Lynn Wheeler writes:
i thot it was pretty good for the 4341 since it was only about a 1mip processor.
random refs:
https://www.garlic.com/~lynn/2000.html#90
https://www.garlic.com/~lynn/2000d.html#0
so scale the hardware transport by a factor of 100 (say something like HIPPI or FCS) and the processor speed by a factor of a couple hundred; current CPU utilization would then be expected to be a couple percent for trivial loop transmitting/receiving data.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: VTOC/VTOC INDEX/VVDS and performance (expansion of VTOC position) Newsgroups: bit.listserv.ibm-main Date: Mon, 16 Apr 2001 19:33:46 GMTAnne & Lynn Wheeler writes:
i got to work on a non-CKD solution for MVS ... but STL quoted something like cost of $26m to deploy ... it represented a significant system thruput improvement even if CKD drives were being used (but would also work on fba-like devices). now, at least there are indexed vtocs and pdse.
random refs:
https://www.garlic.com/~lynn/97.html#16 Why Mainframes?
https://www.garlic.com/~lynn/97.html#22 Pre S/360 IBM Operating Systems?
https://www.garlic.com/~lynn/97.html#28 IA64 Self Virtualizable?
https://www.garlic.com/~lynn/97.html#29 IA64 Self Virtualizable?
https://www.garlic.com/~lynn/98.html#21 Reviving the OS/360 thread (Questions about OS/360)
https://www.garlic.com/~lynn/99.html#74 Read if over 40 and have Mainframe background
https://www.garlic.com/~lynn/99.html#75 Read if over 40 and have Mainframe background
https://www.garlic.com/~lynn/2000.html#86 Ux's good points.
https://www.garlic.com/~lynn/2000b.html#71 "Database" term ok for plain files?
https://www.garlic.com/~lynn/2000d.html#42 360 CPU meters (was Re: Early IBM-PC sales proj..
https://www.garlic.com/~lynn/2000d.html#50 Navy orders supercomputer
https://www.garlic.com/~lynn/2000e.html#19 Is Al Gore The Father of the Internet?^
https://www.garlic.com/~lynn/2000e.html#22 Is a VAX a mainframe?
https://www.garlic.com/~lynn/2000f.html#18 OT?
https://www.garlic.com/~lynn/2000f.html#19 OT?
https://www.garlic.com/~lynn/2000g.html#51 > 512 byte disk blocks (was: 4M pages are a bad idea)
https://www.garlic.com/~lynn/2000g.html#52 > 512 byte disk blocks (was: 4M pages are a bad idea)
https://www.garlic.com/~lynn/2001.html#12 Small IBM shops
https://www.garlic.com/~lynn/2001.html#22 Disk caching and file systems. Disk history...people forget
https://www.garlic.com/~lynn/2001.html#54 FBA History Question (was: RE: What's the meaning of track overfl ow?)
https://www.garlic.com/~lynn/2001.html#55 FBA History Question (was: RE: What's the meaning of track overfl ow?)
https://www.garlic.com/~lynn/2001b.html#23 Linux IA-64 interrupts [was Re: Itanium benchmarks ...]
https://www.garlic.com/~lynn/2001c.html#17 database (or b-tree) page sizes
https://www.garlic.com/~lynn/2001d.html#5 Unix hard links
https://www.garlic.com/~lynn/2001d.html#48 VTOC position
https://www.garlic.com/~lynn/2001d.html#49 VTOC position
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Pentium 4 Prefetch engine? Newsgroups: comp.arch Date: Wed, 18 Apr 2001 02:47:48 GMTAnne & Lynn Wheeler writes:
so a benchmark on 1ghz pentium, 1gbyte memory, redhat7/linux2.4, with 36gbyte, 10k RPM scis disk (160mb scsi, disk 41mbyte-62mbyte internal spead).
i performed dd of a 1.3gbyte file to /dev/null took took 64secs elapsed and total 10secs cpu
or about 21mbytes/sec elapsed (about 50% of the 41mbyte/sec internal drive transfer speed).
just for comparison dd of the same file to another file took over 4mins elapsed (to be expected since it was the same drive) and about 25secs cpu (not a whole lot of overhead in writing to /dev/null).
now back to the 4341/rfc1044 implementation .... dd on 1ghz pentium is getting about 40times as much mbytes per cpu second as the 4341/rfc1044 implementation. Given what numbers you believe the 1ghz pentium is somewhere between 1500-2000 mip processor (compared to the 1mip 4341).
taking the @2000mip rating, linux/dd is then executing 50 times as many instructions per mbyte transferred as the 4341/rfc1044 implementation; not 100 percent, not ten times, but fifty times as many instructions per mbyte transferred.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Pentium 4 Prefetch engine? Newsgroups: comp.arch Date: Wed, 18 Apr 2001 03:52:56 GMTAnne & Lynn Wheeler writes:
following is from something in the very early '80s, 20 years ago comparing "mainframes" from 20 years ago to "mainframes" about 30+ years ago .... early posting
https://www.garlic.com/~lynn/93.html#31
system 3.1L HPO change machine 360/67 3081 47* (mips) pageable pages 105 7000 66* users 80 320 4* channels 6 24 4* drums 12meg 72meg 6* page I/O 150 600 4* user I/O 100 300 3* # disk arms 45 32 4*?perform. bytes/arm 29meg 630meg 23* avg. arm access 60mill 16mill 3.7* transfer rate .3meg 3meg 10* total data 1.2gig 20.1gig 18*so how would my little linux system compare to the "mainframe" of 30+ years ago
system 3.1L Linux change machine 360/67 1ghz(dual) 8000* pageable pages 105 1gbyte 2000* users 80 1 channels 6 1 drums 12meg 0 page I/O 150/sec - user I/O 100/sec - # disk arms 45 1 bytes/arm 29meg 36gbyte 1500* avg. arm access 60mill 4.5mill 13* transfer rate .3meg 40-60mbyte 133-200* total data 1.2gig 36gbyte 30*the '67 might substain 100 "user" i/os per second for much of first shift, someplace between .5mbytes to 1mbyte per second aggregate (reads and writes). In terms of random operations, the fast scsi disk is only about 13 times faster ... for it to achieve 130 times faster it has to do an awful large number of contiguous block transfers.
At the best case, assuming that the Linux system is keeping both processors 100 percent busy, the configuration is only capable of moving about 1/60th as many disk mbytes per mip executed, optimal case with contiguous transfer; which might drop to 1/600th as many disk mbytes moved per mip executed if there is much arm movement
aka, assuming same number of bytes moved per arm motion, if the arm is 13 times faster, and the processor is 8000 times faster, the relative speed of the disk subsystem (compared to the processor speed) has decreased by a factor of 600 times. however, note that the '67 configuration with 45 disk arms ... even being 13 times slower ... could still do an aggregate of three times as many arm movements as a single current arm. Taking the disk subsystem as a whole (1 arm versus 45 arms that are 13 times slower), the actual relative disk subsystem speed (compared to the processor speed) has decreased by a factor of nearly 1800 times.
In theory then, if both pentium processors are operating at 100% utilization ... and the single arm is operating at 100% utilization ... compared to the '67 system operating at 100% cpu utilization and all 45 arms operating at 100% utilization, the current number of disk operations per mip executed has decreased by a factor of 1800 times.
So if you take aggregate number of mips when executing at 100% utilization (for both sysems) and divide it by the total number of disk operations when the respective disk subsystem are operating at 100% utilization ... then the mips/disk-ops will have increased by 1800 times (comparing the linux/dual 1ghz system to the '67 system).
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Pentium 4 Prefetch engine? Newsgroups: comp.arch Date: Wed, 18 Apr 2001 15:50:23 GMTdsiebert@excisethis.khamsin.net (Douglas Siebert) writes:
https://www.garlic.com/~lynn/2000d.html#0
I did find dhrystones for pentium pro 200 that rated it at 453mips. I have some numbers on one of my own (non-FP) application that has twice the thruput on pii-400 as p-pro (900mips?) and has 2.5 times the thruput on 1ghz processor as on my pii-400. that puts the 1ghz processr at 5 times the thruput of p-pro for a specific application that I have used over the past six years. 5*450mips = 2250 mips (for whatever reason, this particular application thruput has scaled with the pentium clock rate).
The specific application is complex indexing, bit manipulation, pointer & storage management (and I keep detailed history of operations performed and cpu used, p-pro to 1ghz isn't direct comparison since the p-pro has bad scsi disk at the moment and the implementation has changed between the time i last ran it on p-pro and the current time). I use it for the rfc standard process and generates the rfc ietf index (as well as various glossaries)
https://www.garlic.com/~lynn/rfcietff.htm
https://www.garlic.com/~lynn/
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: I/O contention Newsgroups: bit.listserv.ibm-main Date: Wed, 18 Apr 2001 17:13:41 GMTsmetz@NSF.GOV (Metz, Seymour) writes:
i had once tried to get multiple exposure support for fixed head area on 3350s ... but it didn't make it out the door.
random refs:
https://www.garlic.com/~lynn/93.html#31 Big I/O or Kicking the Mainframe out the Door
https://www.garlic.com/~lynn/95.html#8 3330 Disk Drives
https://www.garlic.com/~lynn/95.html#12 slot chaining
https://www.garlic.com/~lynn/99.html#6 3330 Disk Drives
https://www.garlic.com/~lynn/99.html#8 IBM S/360
https://www.garlic.com/~lynn/99.html#104 Fixed Head Drive (Was: Re:Power distribution (Was: Re: A primeval C compiler)
https://www.garlic.com/~lynn/2000d.html#7 4341 was "Is a VAX a mainframe?"
https://www.garlic.com/~lynn/2000d.html#13 4341 was "Is a VAX a mainframe?"
https://www.garlic.com/~lynn/2000d.html#52 IBM 650 (was: Re: IBM--old computer manuals)
https://www.garlic.com/~lynn/2000d.html#53 IBM 650 (was: Re: IBM--old computer manuals)
https://www.garlic.com/~lynn/2000g.html#42 4M pages are a bad idea (was Re: AMD 64bit Hammer CPU and VM)
https://www.garlic.com/~lynn/2000g.html#45 4M pages are a bad idea (was Re: AMD 64bit Hammer CPU and VM)
https://www.garlic.com/~lynn/2001.html#18 Disk caching and file systems. Disk history...people forget
https://www.garlic.com/~lynn/2001b.html#61 Disks size growing while disk count shrinking = bad performance
https://www.garlic.com/~lynn/2001c.html#17 database (or b-tree) page sizes
https://www.garlic.com/~lynn/2001d.html#24 April Fools Day
https://www.garlic.com/~lynn/2001d.html#49 VTOC position
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Block oriented I/O over IP Newsgroups: comp.arch Date: Wed, 18 Apr 2001 18:12:56 GMT"Stephen Fuld" writes:
Various people working TCP have worried about window size issues to help mask end-to-end latency issues (akin to multiple request queueing).
buffer copies have alwas been somewhat of an issue .... but as relative descrepency between cache performance and memory performance has increased ... the impact of multiple large buffer copies can dominate processor utilization. Of course poor coding implementations can also aggravate system thruput.
airline res systems can have serialization and latency thruput issues at several levels. several years ago, i had the opportunity to redesign and rewrite "routes" in one of the res systems (represented about 25% of total overall activity). one of the things i got to do was collapse three separate human interactions into a single transaction. The elapsed time for the resulting transaction was about the same as the most trivial of the original three, but with the agent only having to do a single transaction rather than three separate transactions resulted in much more than three times improvement.
random refs:
https://www.garlic.com/~lynn/93.html#28 Log Structured filesystems -- think twice
https://www.garlic.com/~lynn/94.html#22 CP spooling & programming technology
https://www.garlic.com/~lynn/94.html#50 Rethinking Virtual Memory
https://www.garlic.com/~lynn/95.html#13 SSA
https://www.garlic.com/~lynn/96.html#14 mainframe tcp/ip
https://www.garlic.com/~lynn/96.html#15 tcp/ip
https://www.garlic.com/~lynn/96.html#16 middle layer
https://www.garlic.com/~lynn/96.html#17 middle layer
https://www.garlic.com/~lynn/96.html#29 Mainframes & Unix
https://www.garlic.com/~lynn/96.html#31 Mainframes & Unix
https://www.garlic.com/~lynn/98.html#34 ... cics ... from posting from another list
https://www.garlic.com/~lynn/98.html#49 Edsger Dijkstra: the blackest week of his professional life
https://www.garlic.com/~lynn/98.html#50 Edsger Dijkstra: the blackest week of his professional life
https://www.garlic.com/~lynn/98.html#59 Ok Computer
https://www.garlic.com/~lynn/99.html#1 Early tcp development?
https://www.garlic.com/~lynn/99.html#36 why is there an "@" key?
https://www.garlic.com/~lynn/99.html#40 [netz] History and vision for the future of Internet - Public Question
https://www.garlic.com/~lynn/99.html#70 Series/1 as NCP (was: Re: System/1 ?)
https://www.garlic.com/~lynn/99.html#123 Speaking of USB ( was Re: ASR 33 Typing Element)
https://www.garlic.com/~lynn/99.html#136a checks (was S/390 on PowerPC?)
https://www.garlic.com/~lynn/99.html#153 Uptime (was Re: Q: S/390 on PowerPC?)
https://www.garlic.com/~lynn/99.html#164 Uptime (was Re: Q: S/390 on PowerPC?)
https://www.garlic.com/~lynn/99.html#214 Ask about Certification-less Public Key
https://www.garlic.com/~lynn/2000.html#61 64 bit X86 ugliness (Re: Williamette trace cache (Re: First view of Willamette))
https://www.garlic.com/~lynn/2000.html#90 Ux's good points.
https://www.garlic.com/~lynn/2000.html#93 Predictions and reality: the I/O Bottleneck
https://www.garlic.com/~lynn/2000b.html#11 "Mainframe" Usage
https://www.garlic.com/~lynn/2000c.html#13 Gif images: Database or filesystem?
https://www.garlic.com/~lynn/2000c.html#23 optimal cpu : mem <-> 9:2 ?
https://www.garlic.com/~lynn/2000c.html#56 Does the word "mainframe" still have a meaning?
https://www.garlic.com/~lynn/2000c.html#59 Does the word "mainframe" still have a meaning?
https://www.garlic.com/~lynn/2000d.html#80 When the Internet went private
https://www.garlic.com/~lynn/2000e.html#17 X.25 lost out to the Internet - Why?
https://www.garlic.com/~lynn/2000e.html#19 Is Al Gore The Father of the Internet?^
https://www.garlic.com/~lynn/2000e.html#39 I'll Be! Al Gore DID Invent the Internet After All ! NOT
https://www.garlic.com/~lynn/2000e.html#45 IBM's Workplace OS (Was: .. Pink)
https://www.garlic.com/~lynn/2000f.html#10 Optimal replacement Algorithm
https://www.garlic.com/~lynn/2000f.html#18 OT?
https://www.garlic.com/~lynn/2000f.html#20 Competitors to SABRE?
https://www.garlic.com/~lynn/2000f.html#23 Why trust root CAs ?
https://www.garlic.com/~lynn/2000f.html#30 OT?
https://www.garlic.com/~lynn/2000f.html#50 Al Gore and the Internet (Part 2 of 2)
https://www.garlic.com/~lynn/2000f.html#51 Al Gore and the Internet (Part 2 of 2)
https://www.garlic.com/~lynn/2001.html#12 Small IBM shops
https://www.garlic.com/~lynn/2001.html#18 Disk caching and file systems. Disk history...people forget
https://www.garlic.com/~lynn/2001.html#46 Small IBM shops
https://www.garlic.com/~lynn/2001.html#73 how old are you guys
https://www.garlic.com/~lynn/2001b.html#14 IBM's announcement on RVAs
https://www.garlic.com/~lynn/2001b.html#36 [OT] Currency controls (was: First OS?)
https://www.garlic.com/~lynn/2001b.html#38 Why SMP at all anymore?
https://www.garlic.com/~lynn/2001b.html#61 Disks size growing while disk count shrinking = bad performance
https://www.garlic.com/~lynn/2001b.html#85 what makes a cpu fast
https://www.garlic.com/~lynn/2001c.html#16 database (or b-tree) page sizes
https://www.garlic.com/~lynn/2001c.html#30 PKI and Non-repudiation practicalities
https://www.garlic.com/~lynn/2001c.html#74 database (or b-tree) page sizes
https://www.garlic.com/~lynn/2001c.html#79 Q: ANSI X9.68 certificate format standard
https://www.garlic.com/~lynn/2001d.html#63 Pentium 4 Prefetch engine?
https://www.garlic.com/~lynn/2001d.html#65 Pentium 4 Prefetch engine?
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Pentium 4 Prefetch engine? Newsgroups: comp.arch Date: Wed, 18 Apr 2001 23:22:11 GMT"Bill Todd" writes:
while these may not have been popular platforms from a end-user standpoint (paradigm that operating system interacts with an application rather than a paradigm that an operating system interacts with a human) ... they are very popular for industrial strength applications like payroll.
A couple years ago, One of the big financial infrastructures commented
that two of the things they attribute to having 100% availability for
the preceeding six years was
• ims hot-standby (aka clustering)
• automated operator
batch systems tend to still have (relatively) small number of
interactions involving an (human) operator ... who could still make
mistakes (opportunity for mistakes are possibly orders of magnitude
less than a operating system evovling from a user interaction
paradigm, but still non-zero). automated operator was methodology for
trapping any remaining interactions that would involve humans and
implementing programmatic solutions.
random refs:
https://www.garlic.com/~lynn/94.html#2 Schedulers
https://www.garlic.com/~lynn/98.html#18 Reviving the OS/360 thread (Questions about OS/360)
https://www.garlic.com/~lynn/98.html#35a Drive letters
https://www.garlic.com/~lynn/98.html#37 What is MVS/ESA?
https://www.garlic.com/~lynn/98.html#40 Comparison Cluster vs SMP?
https://www.garlic.com/~lynn/98.html#51 Mainframes suck? (was Re: Possibly OT: Disney Computing)
https://www.garlic.com/~lynn/99.html#71 High Availabilty on S/390
https://www.garlic.com/~lynn/99.html#128 Examples of non-relational databases
https://www.garlic.com/~lynn/99.html#136a checks (was S/390 on PowerPC?)
https://www.garlic.com/~lynn/2000.html#13 Computer of the century
https://www.garlic.com/~lynn/2000c.html#45 Does the word "mainframe" still have a meaning?
https://www.garlic.com/~lynn/2000c.html#47 Does the word "mainframe" still have a meaning?
https://www.garlic.com/~lynn/2000f.html#12 Amdahl Exits Mainframe Market
https://www.garlic.com/~lynn/2000f.html#30 OT?
https://www.garlic.com/~lynn/2000f.html#54 360 Architecture, Multics, ... was (Re: X86 ultimate CISC? No.)
https://www.garlic.com/~lynn/2000f.html#58 360 Architecture, Multics, ... was (Re: X86 ultimate CISC? No.)
https://www.garlic.com/~lynn/2001.html#43 Life as a programmer--1960, 1965?
https://www.garlic.com/~lynn/2001c.html#13 LINUS for S/390
https://www.garlic.com/~lynn/2001c.html#69 Wheeler and Wheeler
Cluster, High Availability and/or Loosely-Coupled posts
https://www.garlic.com/~lynn/subtopic.html#hacmp
Disk Engineering posts
https://www.garlic.com/~lynn/subtopic.html#disk
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Pentium 4 Prefetch engine? Newsgroups: comp.arch Date: Thu, 19 Apr 2001 15:41:04 GMT"Bill Todd" writes:
random refs:
https://www.garlic.com/~lynn/99.html#71
my wife having done a spell in pok in charge of loosely-coupled architecture and originated Peer-Coupled Shared Data ... which was the basis of a number of things, inlucding ims hot standby (although i kid her that while she was writing documents, I was helping deploy what was considered the largest single system imfrastructure anywhere up until that time) as well as doing some "bullet-proof" i/o subsystem for the guys over in the disk engineering lab.
random ref:
https://www.garlic.com/~lynn/97.html#14
https://www.garlic.com/~lynn/99.html#31
in the late '80s when we were running skunk works responsible for ha/cmp we got a lot of push back from pok, rochester, vms crowd and some number of others (even some very prominant in current "open" cluster genre) that it was not practical to improve reliability and availability for "open" platform systems.
random refs
https://www.garlic.com/~lynn/95.html#13
https://www.garlic.com/~lynn/2001c.html#69
although we did identify some issues .... like some C language library conventions and the vast differences between operating systems designed for interactive/end-users and operating systems designed for batch/applications (n part having worked on automated operator applications in the early to mid-70s).
can even claim the simplicity & ease of use of some of the C language library conventions (namely implicit lengths) has been one of its great difficiencies.
random refs
https://www.garlic.com/~lynn/aadsm5.htm#asrn4
https://www.garlic.com/~lynn/aadsm5.htm#asrn1
One of the things we did in the mid-90s working on various infrastructure deployments was noting that while up-front costs for deploying a web-server in closet was relatively low ... that the scale-up costs increased much faster than some of the industrial strength platforms .... and total costs definately crossed over for the top-tier servers that represented possibly 70-80% of web traffic i.e. that server and client platforms don't have to be symmetrical/homogeneous, and that the human element requirement of many of the platforms that originated out of an "interactive" orientation also had significant human element care & feeding scaling issues (not just reliability and availability but also significant cost issues trying to scale up).
random ref:
https://www.garlic.com/~lynn/aadsm5.htm#asrn3
long ago and far away ... I claimed that the significant market penetration of unix was its relatively low costs for manufactures entering the processor market. At least by 1980, the cost of computer hardware development had come down so significantly that it was starting to allow a number of hardware vendors to enter the mini & workstation market. However, the cost of developing a proprietary operating system remained prohibitatively expensive. The demonstrated portability ease of moving UNIX to a new platform became an attractive cost alternative to such enterprises (compared to developing a proprietary operating system from scratch) i.e. delivering an operating system for the platform didn't cost more than the whole rest of the platform delivery effort combined.
random ref:
https://www.garlic.com/~lynn/99.html#222
moved to
http://vm.marist.edu/~piper/party/jph-12.html#wheeler
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Pentium 4 Prefetch engine? Newsgroups: comp.arch Date: Thu, 19 Apr 2001 15:57:43 GMTdsiebert@excisethis.khamsin.net (Douglas Siebert) writes:
i claimed that I had an application that scaled fairly linearly from p-pro 200 to 1ghz. It doesn't completely reside in cache, but it does have relatively high cache hit ratio and there is no floating point ... which is representative of large amount of data processing, file activity.
so for the hypothetical 1ghz 2000 mips number ... divide all the numbers by some value ... 2?, 4?, 5? 10? we may actually be in violent agreement ... in part because the processor thruput has increased so much faster than the i/o thruput has increased (a trend that has been going on since at least the late '60s) ... that the nature of what is done on the processors has had to change (human nature that attempts to fill a vacuum?)
aka ... if running an appication that had mips/mbyte-io ratios of the '60s ... the processors would only have trivial cpu utilization ... depending on the mip rate valute used that might be 5 percent or .05 percent (three orders of magnitude difference but all still trivial).
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Rational basis for password policy? Newsgroups: comp.security.misc Date: Thu, 19 Apr 2001 16:05:31 GMTGunther Schadow writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Pentium 4 Prefetch engine? Newsgroups: comp.arch Date: Thu, 19 Apr 2001 16:22:24 GMTAnne & Lynn Wheeler writes:
in the description of the following "routes" for res system recently posted to this ng on different thread
https://www.garlic.com/~lynn/2001d.html#69
i used a fairly large in-memory data structure ... and I got a factor of 3 times difference in total cpu utilization by changing the data structure from an extremely straight-foward design to one that was tuned for storage/cache access patterns (things were still larger than cache ... but cache miss dropped significantly).
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: April Fools Day Newsgroups: alt.folklore.computers Date: Thu, 19 Apr 2001 17:18:15 GMTjchausler writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Changing IP addresses, was: Carrying authentication information between Web applications Newsgroups: comp.security.misc Date: Thu, 19 Apr 2001 17:27:25 GMTLassi Hippeläinen writes:
https://www.garlic.com/~lynn/2001c.html
everything is relative ... if an ISP kicks people off after being on a couple hrs and/or drops the line if inactive for more than 10 minutes ... then the avg connect time would likely be shorter than the IP address time-out interval.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Pentium 4 Prefetch engine? Newsgroups: comp.arch Date: Fri, 20 Apr 2001 16:03:21 GMTKonrad Schwarz writes:
The issue with TSS having all memory-mapped was the relative large size of data compared to real storage sizes ... and its poor handling of sequential access patterns ... i.e. TSS would trivially page thrash with sequential access to memory-mapped locations ... the CMS implementation could do full memory mapping with somewhat better page thrashing control ... but also do large buffer page-mapped sequences with a lot of performance advantage over traditioanl I/O but the trade-off with explicit read/write paradigm in the application was the better explicit hints regarding things like sequential and/or "weak" access patterns (i.e. when read/write referred to previously used virtual address it was easily understood that application moved out of the "previous" data and into the "new" data).
I got to install on possibly several hundred "internal" production machines (much larger than the total Multics install base) but didn't actually ship to customers except on something called XT/AT//370 platform.
random refs to some of that internal install base:
https://www.garlic.com/~lynn/99.html#112
https://www.garlic.com/~lynn/99.html#126
The general TSS install base (non-internal & non-AT&T) approached the size of total Multics install base ... but details are much less well known, in part because the other operating systems on the platforms so dominated the total industry. However, AT&T did do a "unix" port to TSS (i.e. unix running on top of TSS) and just the AT&T install base was probably larger than the total Multics install base.
random refs:
https://www.garlic.com/~lynn/2000.html#1
https://www.garlic.com/~lynn/2000.html#64
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/