fsfacca@AVELON.LERC.NASA.GOV (Tony Facca) (02/04/91)
> >The init.ps file for the window manager startup and the inetd for the >communication are automatically modified (changed to the new version) >without notification. This should be removed in future releases, because there >is some work in these files. There should be a .O or similar extension. I second! I understand why /usr/etc/inetd.conf must be replaced so that new features of the network software are properly handled by inetd (have you ever run an OLD inetd.conf with NEW software -- it's kinda strange.. :-) /usr/NeWS/lib/user.ps and /usr/NeWS/lib/startup.ps on the other hand are simply replaced. No .O, nothing. But then, there probably won't be a user.ps or startup.ps in the next major release, right? -- ----------------------------------------------------------------------------- Tony Facca | fsfacca@avelon.lerc.nasa.gov | phone: 216-433-8318 ----------------------------------------------------------------------------- You are at Witt's end. Passages lead off in *all* directions.
vjs@rhyolite.wpd.sgi.com (Vernon Schryver) (02/05/91)
In article <1991Jan31.130801.1349@urz.unibas.ch>, doelz@urz.unibas.ch writes: > > Yesterday, I installed 3.3.2 (option AUTOMATIC in INST). > > The init.ps file for the window manager startup and the inetd for the > communication are automatically modified (changed to the new version) >without notification. This should be removed in future releases, because there > is some work in these files. There should be a .O or similar extension. All "configuration files" are handled by some simple rules. Each configuration file is labelled in our source as "noupdate", "update", or "suggest". When installing new software, inst notes whether the existing, old copy of a configurat file has been changed from the SGI-shipped contents of the previous release. From these 6 states, inst does: "noupdate", changed or not: leave the existing file alone, discard new version from the tape. "update", changed: move old version to foo.O, and install new version. "update", unchanged: install new version on top of old version. "suggest", changed: install new version as foo.N "suggest", unchanged: install new version on top of old version. Inetd.conf was marked as "update" in 3.3.2. There is a mechanism that seems to have been broken in 3.3.2 that is supposed to complain to the console as the system is booted if there are any unresolved configuration file changes. The mechanism just ran `versions changed`. Are you saying that you had changed inetd.conf, but that inst installed wrote a new inetd.conf on top of your changes without saving them in inetd.conf.O? What does `versions changed` report? vjs