[Info-vax] SOLVED : Re: Process quota problem after upgrade to 8.4-2L1

[Phillip Helbig undress to reply]

In article <rrtpi5$nb3$1 at dont-email.me>, Dave Froble
<davef at tsoft-inc.com> writes: 

> On 12/22/2020 4:29 PM, Phillip Helbig (undress to reply) wrote:
> > In article <rrt30e$aua$1 at dont-email.me>, Stephen Hoffman
> > <seaohveh at hoffmanlabs.invalid> writes:
> >
> >> Cluster satellite workstations are also not configurations I'd expect
> >> to see a whole lot of usage or testing, generally. I'd expect little
> >> usage of these configurations outside of hobbyist environments.
> >
> > Probably true today.  On the other hand, they tend to be rebooted once a
> > day rather than once a decade, so non-dynamic parameters can be tested.
> >
> >> We'd
> >> see yet fewer of these cases too, if OpenVMS were better about its
> >> installation and re-installation and provisioning and which would ease
> >> cloning
> >
> > I would really like the ability to do an upgrade to the OS without
> > affecting any customized settings.
> 
> Ummm ...  how can I say this?
> 
> You should really avoid customization of an OS, unless you're the OS 
> developer.  I consider doing so is just asking for problems, both while 
> using the OS, and most definitely when upgrading.

I'm talking about things like mounting disks, my TCPIP configuration, 
and so on.

> My practice is to insert required startup tasks in SYSTARTUP_VMS.COM, 
> which is preserved during an upgrade.  Any more would require convincing 
> needs.

Yes, they are preserved.  But, say, you have cluster-common stuff on 
another disk, which has to be mounted earlier.  Yes, there is the 
.TEMPLATE and .COM.  But on the other hand if one never touches the 
user-modified files, one would never use any new functionality in the 
templates.