[1165] in SIPB-AFS-requests
/afs/sipb/project/foo-server, not dec-charon
daemon@ATHENA.MIT.EDU (mhpower@mit.edu)
Sun Oct 24 23:13:49 1993
From: mhpower@mit.edu
To: charon-maintainers@mit.edu, rtfm-maintainers@mit.edu
Cc: sipb-afsreq@mit.edu
In-Reply-To: "[0457] in Charon_Maintainers_Archive", "[0070] in RTFM_Maintainers_Archive"
Date: Sun, 24 Oct 93 23:13:01 EDT
In minutes.93.10.18:
> Can /afs/sipb/project/dec-charon become a link to
>picayune? Or can we split the fooserver and barserver sources into
>the appropriate dirs? No, thats not what we want to do. Mhpower
>should do something sane and send mail.
I moved the AFS copies of bloom-picayune and charon stuff to the new
volume project.foo-server mounted on /afs/sipb/project/foo-server.
/afs/sipb/project/dec-charon is no longer a mountpoint, just a symlink
to /afs/sipb.mit.edu/project/foo-server/picayune. This should allow
any script on bloom-picayune to continue working without change, e.g.,
there are some /afs/sipb.mit.edu/project/dec-charon/usenet-addresses
references in the usenet-addresses nightly jobs.
I'd consider the following volumes obsolete:
name mountpoint
---- ----------
project.charon /afs/sipb/project/charon
project.old-charon /afs/sipb/project/new-charon
project.new-charon /afs/sipb/project/dec-charon
In fact, the first two are somewhat more obsolete than the third, in
that they don't exist anymore... Currently, though, there are full vos
dumps online in the directory /afs/sipb/project/charonvosdu (which
holds the project.charonvosdu.nb volume). This directory should be
archived to tape in a week or so, unless someone thinks that isn't
enough time to retrieve files they wanted.
The charonvosdu directory also has a full dump of project.new-charon.
However, the new-charon volume still exists, although it isn't mounted
anywhere in project/. It can be vos removed in about a week, I'd
expect.
Matt
