buchholz@ese3.ese.ogi.edu (Don Buchholz) (03/28/91)
So I recently applied (and committed :-)) 3003 to one of our RS/6000-320's. We had been running 3001 code. A sincere "thank you" to Steve Roseman for the scripts that a lot of the mystery out of the install/update procedures. I followed your lead and came up with shell scripts that use a lot less disk than SMIT (or effort, if you select items 1-by-1 in SMIT). I couldn't help but to notice that *all* of the *.info files were at the same major.minor.update.build numbers that we were already at. I did not force the install/update with '-F', and subsequently made no changes to these images. However, I'd appreciate some reassurance that when they said select "OVERWRITE newer version"="yes" in the PTF notes, they weren't implying that they would send us an updated product with the same version number. Would they? (The X11rte.obj was also at the 3001 level.) Should I go back and force the instupdt? Don Buchholz Oregon Graduate Institute buchholz@ese3.ese.ogi.edu
marc@stingray.austin.ibm.com (Marc J. Stephenson/140000;1C-22) (03/29/91)
The *.info and the X11rte.obj are indeed new versions on 3003. Unfortunately, the modification levels which are automatically updated for updateps are not used by installp - that is why the info files appear to be the same level. -- Marc Stephenson IBM PSPA (Personal System Programming - Austin,TX) DISCLAIMER: The content of this posting is independent of official IBM position. marc@stingray.austin.ibm.com VNET: MARC at AUSVMQ IBM T/L: 793-3796
graeme@ccu1.aukuni.ac.nz (Graeme Moffat) (04/05/91)
marc@stingray.austin.ibm.com (Marc J. Stephenson/140000;1C-22) writes: >The *.info and the X11rte.obj are indeed new versions on 3003. >Unfortunately, the modification levels which are automatically >updated for updateps are not used by installp - that is why the >info files appear to be the same level. Are those of us who use CD roms for man/info ever going to get updates? File dates for most CD files are Apr 1989, although sizes are considerably greater than the disk versions. To ship updated versions with a 0000.0000 build number is bad, IMHO. Hands up anyone else who didn't realise they had been updated. When using man with CDroms, there is a 5-10 second delay before anything appears. I guess we have to accept the speed/space tradeoff here. But I would like to know why, after EOF of man is reached, there can be 20-30 seconds delay before the prompt returns (the CD is flashing its light, doing something)? In cynical moments, I have speculated that it is either rewinding or retensioning, but is man in fact being *too* smart, and continuing to search for matches? Whatever, if the prompt does not return within 2 secs of ending man, I reach for ^C. -- Graeme Moffat g.moffat@aukuni.ac.nz \ Time wastes us all, Computer Aided Design Centre, Fax: +64-9-366-0702 / our bodies & our wits School of Engineering, Ph: +64-9-737-999 x8384 / But we waste time, University of Auckland, Private Bag, Auckland, NZ \ so time & we are quits