fox2mike 05/11/09 20:58:08 Modified: xml/htdocs/doc/en openafs.xml Log: #110883 - Huge update to OpenAFS guide, thanks to stefaan. This is a Gentoo Doc Overnight Express Delivery on the request of seemant.
Revision Changes Path 1.23 +626 -78 xml/htdocs/doc/en/openafs.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/openafs.xml?rev=1.23&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/openafs.xml?rev=1.23&content-type=text/plain&cvsroot=gentoo diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/openafs.xml.diff?r1=1.22&r2=1.23&cvsroot=gentoo Index: openafs.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v retrieving revision 1.22 retrieving revision 1.23 diff -u -r1.22 -r1.23 --- openafs.xml 29 Oct 2005 21:10:15 -0000 1.22 +++ openafs.xml 9 Nov 2005 20:58:07 -0000 1.23 @@ -1,5 +1,5 @@ <?xml version='1.0' encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.22 2005/10/29 21:10:15 so Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.23 2005/11/09 20:58:07 fox2mike Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> @@ -18,6 +18,12 @@ <author title="Editor"> <mail link="[EMAIL PROTECTED]">Steven McCoy</mail> </author> +<author title="Editor"> + <mail link="[EMAIL PROTECTED]">Stefaan De Roeck</mail> +</author> +<author title="Editor"> + <mail link="[EMAIL PROTECTED]">Shyam Mani</mail> +</author> <abstract> This guide shows you how to install an OpenAFS server and client on Gentoo @@ -28,8 +34,8 @@ <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> -<version>1.0</version> -<date>2005-10-29</date> +<version>1.1</version> +<date>2005-11-10</date> <chapter> <title>Overview</title> @@ -86,7 +92,7 @@ file which they are accessing, is located. They even won't notice if a server will be located to another room, since every volume can be replicated and moved to another server without any user noticing. The files are always -accessable. Well, it's like NFS on steroids :) +accessible. Well, it's like NFS on steroids :) </p> </body> @@ -145,6 +151,470 @@ </chapter> <chapter> +<title>Upgrading from previous versions</title> +<section> +<title>Introduction</title> +<body> + +<p> +This section aims to help you through the process of upgrading an existing +OpenAFS installation to OpenAFS version 1.4.0 or higher (or 1.2.x starting from +1.2.13. The latter will not be handled specifically, as most people will want +1.4 for a.o.linux-2.6 support, large file support and bug fixes). +</p> + +<p> +If you're dealing with a clean install of a 1.4 version of OpenAFS, then you can +safely skip this chapter. However, if you're upgrading from a previous version, +we strongly urge you to follow the guidelines in the next sections. The +transition script in the ebuild is designed to assist you in quickly upgrading +and restarting. Please not that it will (for safety reasons) not delete +configuration files and startup scripts in old places, not automatically change +your boot configuration to use the new scripts, etc. If you need further +convincing, using an old OpenAFS kernel module together with the updated system +binaries, may very well cause your kernel to freak out. So, let's read on for a +clean and easy transition, shall we? +</p> + +<note> +This chapter has been written bearing many different system configurations in +mind. Still, it is possible that due to peculiar tweaks a user has made, his or +her specific situation may not be described here. A user with enough +self-confidence to tweak his system should be experienced enough to apply the +given remarks where appropriate. Vice versa, a user that has done little +to his system but install the previous ebuild, can skip most of the warnings +further on. +</note> + +</body> +</section> +<section> +<title>Differences to previous versions</title> +<body> + +<p> +Traditionally, OpenAFS has used the same path-conventions that IBM TransArc labs +had used, before the code was forked. Understandably, old AFS setups continue +using these legacy path conventions. More recent setups conform with FHS by +using standard locations (as seen in many Linux distributions). The following +table is a compilation of the configure-script and the README accompanying the +OpenAFS distribution tarballs: +</p> + +<table> +<tr> + <th>Directory</th> + <th>Purpose</th> + <th>Transarc Mode</th> + <th>Default Mode</th> + <th>translation to Gentoo</th> +</tr> +<tr> + <ti>viceetcdir</ti> + <ti>Client configuration</ti> + <ti>/usr/vice/etc</ti> + <ti>$(sysconfdir)/openafs</ti> + <ti>/etc/openafs</ti> +</tr> +<tr> + <ti>unnamed</ti> + <ti>Client binaries</ti> + <ti>unspecified</ti> + <ti>$(bindir)</ti> + <ti>/usr/bin</ti> +</tr> +<tr> + <ti>afsconfdir</ti> + <ti>Server configuration</ti> + <ti>/usr/afs/etc</ti> + <ti>$(sysconfdir)/openafs/server</ti> + <ti>/etc/openafs/server</ti> +</tr> +<tr> + <ti>afssrvdir</ti> + <ti>Internal server binaries</ti> + <ti>/usr/afs/bin (servers)</ti> + <ti>$(libexecdir)/openafs</ti> + <ti>/usr/libexec/openafs</ti> +</tr> +<tr> + <ti>afslocaldir</ti> + <ti>Server state</ti> + <ti>/usr/afs/local</ti> + <ti>$(localstatedir)/openafs</ti> + <ti>/var/lib/openafs</ti> +</tr> +<tr> + <ti>afsdbdir</ti> + <ti>Auth/serverlist/... databases</ti> + <ti>/usr/afs/db</ti> + <ti>$(localstatedir)/openafs/db</ti> + <ti>/var/lib/openafs/db</ti> +</tr> +<tr> + <ti>afslogdir</ti> + <ti>Log files</ti> + <ti>/usr/afs/logs</ti> + <ti>$(localstatedir)/openafs/logs</ti> + <ti>/var/lib/openafs/logs</ti> +</tr> +<tr> + <ti>afsbosconfig</ti> + <ti>Overseer config</ti> + <ti>$(afslocaldir)/BosConfig</ti> + <ti>$(afsconfdir)/BosConfig</ti> + <ti>/etc/openafs/BosConfig</ti> +</tr> +</table> + +<p> +There are some other oddities, like binaries being put in +<path>/usr/vice/etc</path> in Transarc mode, but this list is not intended +to be comprehensive. It is rather meant to serve as a reference to those +troubleshooting config file transition. +</p> + +<p> +Also as a result of the path changes, the default disk cache location has +been changed from <path>/usr/vice/cache</path> to +<path>/var/cache/openafs</path>. +</p> + +<p> +Furthermore, the init-script has been split into a client and a server part. +You used to have <path>/etc/init.d/afs</path>, but now you'll end up with both +<path>/etc/init.d/openafs-client</path> and +<path>/etc/init.d/openafs-server</path>. +Consequently, the configuration file <path>/etc/conf.d/afs</path> has been split +into <path>/etc/conf.d/openafs-client</path> and +<path>/etc/conf.d/openafs-server</path>. Also, options in +<path>/etc/conf.d/afs</path> to turn either client or server on or off have +been obsoleted. +</p> + +<p> +Another change to the init script is that it doesn't check your disk cache +setup anymore. The old code required that a separate ext2 partition be +mounted at <path>/usr/vice/cache</path>. There were some problems with that: +</p> + -- [email protected] mailing list
