Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!mit-eddie!apollo!bares From: bares@apollo.uucp (Vittorio Bares) Newsgroups: comp.sys.apollo Subject: Re: Updating Large Rings Message-ID: <379c3ee1.487d@apollo.uucp> Date: Thu, 1-Oct-87 14:01:00 EDT Article-I.D.: apollo.379c3ee1.487d Posted: Thu Oct 1 14:01:00 1987 Date-Received: Mon, 5-Oct-87 05:00:06 EDT Distribution: world Organization: Apollo Computer, Chelmsford, Mass. Lines: 32 [referring to Leonard Zubkoff's installation scheme...] This installation scheme is fine but only under certain controlled conditions. For instance, presently, the only way to preserve a subsystem manager stamp on an object from magnetic tape using RBAK is to include the -SACL option for each restore. If you are restoring a network which is 'open' (i.e. does not use registries or does not protect its files using acl's.) then this would not be a problem. Otherwise, the node being restored would inherit all the acl's presently on the tape. If your network is one in which each developer or group has their own protections for their disks then you would surely receive complaints from people having to re-acl their nodes each time a restore was done. With CPT you are safe in this respect, because CPT carries subsystem stamps over to the new destination automatically by default. Secondly, what happens if there are links on the node you are restoring that point to another volume ? RBAK and CPT will both copy through the link, possibly causing another node to now contain inconsistent software, which could result in crashing that node. Thirdly, what happens to template files which have been customized by the node owner ? Do you have a scheme that assists the user in protecting their customized files from getting overwritten by the standard template files ? As stated earlier, the scheme outlined by Leonard Zubkoff, is undoubtedly quicker than the standard Apollo scripts but, there is no such thing as a free lunch :-), this scheme may not be applicable to all Apollo networks. Cheers, Vittorio Bares bares@apollo.UUCP