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. -D _______________________________________________ OpenAFS-devel mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-devel
- [OpenAFS-devel] Call for consensus: configure defaultin... Sam Hartman
- Re: [OpenAFS-devel] Call for consensus: configure ... Nathan Neulinger
- Re: [OpenAFS-devel] Call for consensus: configure ... Jeffrey Hutzelman
- Re: [OpenAFS-devel] Call for consensus: config... Nathan Neulinger
- Re: [OpenAFS-devel] Call for consensus: configure ... Derrick J Brashear
- Re: [OpenAFS-devel] Call for consensus: configure ... Jeffrey Hutzelman
- Re: [OpenAFS-devel] Call for consensus: configure ... Derrick J Brashear
- Re: [OpenAFS-devel] Call for consensus: configure ... Jeffrey Hutzelman
- Re: [OpenAFS-devel] Call for consensus: configure ... Derrick J Brashear
- Re: [OpenAFS-devel] Call for consensus: config... Jeffrey Hutzelman
- Re: [OpenAFS-devel] Call for consensus: configure ... Sam Hartman
- Re: [OpenAFS-devel] Call for consensus: config... Derrick J Brashear
- Re: [OpenAFS-devel] Call for consensus: configure ... Jim Rees
- Re: [OpenAFS-devel] Call for consensus: configure ... Derrick J Brashear
