[OpenAFS-devel] Call for consensus: configure defaulting behavior change

Jeffrey Hutzelman jhutz@cmu.edu
Tue, 28 Aug 2001 18:34:56 -0400 (EDT)


On Tue, 28 Aug 2001, Derrick J Brashear wrote:

> On Mon, 27 Aug 2001, Sam Hartman wrote:
> 
> > Now that AFS supports configure, people probably expect to be able to
> > use the --prefix argument and other path control switches to  change
> > where AFS puts files and  where it expects to find them at runtime.
> > Clearly we will want to support the current paths now.  Most existing
> > users will continue to  use the Transarc style paths or whatever
> > site-specific modifications they have been using.  
> 
> The next question is, what will the new defaults be, and how granular will
> you be able to configure, e.g. a place for servers, a place for logs, a
> place for database files.

Conveniently, I have the answers to those questions.  The following is
taken from a working document describing what Sam and I have in mind...

  There are two modes: "Transarc mode" and "GCS mode":
  - In Transarc mode, we retain compatibility with Transarc/IBM AFS tools
    by putting client configuaration files in /usr/vice/etc, and server
    files in /usr/afs under the traditional directory layout.
  - In GCS mode, files are located in standardized locations, usually
    under $(prefix).
  - Client programs, libraries, and related files always go in standard
    directories under $(prefix).  This rule covers things that would go
    into $(bindir), $(includedir), $(libdir), $(mandir), and $(sbindir).
  - Other files get located in the following places:

    Directory     Transarc Mode              GCS Mode
    ============  =========================  ==============================
    viceetcdir    /usr/vice/etc              $(sysconfdir)/openafs
    afssrvdir     /usr/afs/bin (servers)     $(libexecdir)/openafs
    afsconfdir    /usr/afs/etc               $(sysconfdir)/openafs/server
    afslocaldir   /usr/afs/local             $(localstatedir)/openafs
    afsdbdir      /usr/afs/db                $(localstatedir)/openafs/db
    afslogdir     /usr/afs/logs              $(localstatedir)/openafs/logs

    afsbosconfig  $(afslocaldir)/BosConfig   $(afsconfdir)/BosConfig
    afsbosserver  $(afsbindir)/bosserver     $(sbindir)/bosserver


The idea is that any of the directories listed above can be overridden
with an appropriate configure option.

-- Jeffrey T. Hutzelman (N3NHS) <jhutz+@cmu.edu>
   Sr. Research Systems Programmer
   School of Computer Science - Research Computing Facility
   Carnegie Mellon University - Pittsburgh, PA