Preserving version numbers in NFS

[Barry Margolin <barmar@Think.COM>]

    Date: Thu, 1 Oct 1992 09:09 EDT
    From: sjameson@hannibal.atl.ge.com (Stephen M Jameson)

    Is there any way to copy a file from a LMFS to an NFS file system and preserve
    version numbers.  If you copy a file "foo.lisp.7" from one lmfs directory to
    another, it seems in general to do so, so you get "foo.lisp.7" in the other
    directory.  If you copy the same file to an NFS directory (which has a "*.sct"
    somewhere in its pathname), it creates "foo.lisp.~<n+1>~", where n is the
    number of previously existing versions of foo.lisp in the directory.  Is there
    any way to force it to create foo.lisp.~7~.  

    This is important for being able to copy an SCT system over to an NFS file
    server, while preserving the ability to load all previously compiled versions
    of the system.

I've never seen this problem when copying into a something.sct directory
on an NFS server.  I have a Unix directory where I periodically back up
the latest versions of my namespace files, and they always copy the
version numbers properly.

I can believe that this would happen when copying to a non-sct directory
on the NFS server.  But since you say you're doing this with SCT
systems, I assume you're putting them into a directory with a ".sct"
suffix.

                                                barmar