Gentoo Archives: gentoo-doc-cvs

From: Shyam Mani <fox2mike@×××××××××××.org>
To: gentoo-doc-cvs@l.g.o
Subject: [gentoo-doc-cvs] cvs commit: openafs.xml
Date: Wed, 09 Nov 2005 20:58:27
Message-Id: 200511092058.jA9Kw9O0008856@robin.gentoo.org
1 fox2mike 05/11/09 20:58:08
2
3 Modified: xml/htdocs/doc/en openafs.xml
4 Log:
5 #110883 - Huge update to OpenAFS guide, thanks to stefaan. This is a Gentoo Doc Overnight Express Delivery on the request of seemant.
6
7 Revision Changes Path
8 1.23 +626 -78 xml/htdocs/doc/en/openafs.xml
9
10 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
11 plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/openafs.xml?rev=1.23&content-type=text/plain&cvsroot=gentoo
12 diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/openafs.xml.diff?r1=1.22&r2=1.23&cvsroot=gentoo
13
14 Index: openafs.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v
17 retrieving revision 1.22
18 retrieving revision 1.23
19 diff -u -r1.22 -r1.23
20 --- openafs.xml 29 Oct 2005 21:10:15 -0000 1.22
21 +++ openafs.xml 9 Nov 2005 20:58:07 -0000 1.23
22 @@ -1,5 +1,5 @@
23 <?xml version='1.0' encoding="UTF-8"?>
24 -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.22 2005/10/29 21:10:15 so Exp $ -->
25 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.23 2005/11/09 20:58:07 fox2mike Exp $ -->
26
27 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
28
29 @@ -18,6 +18,12 @@
30 <author title="Editor">
31 <mail link="fnjordy@×××××.com">Steven McCoy</mail>
32 </author>
33 +<author title="Editor">
34 + <mail link="stefaan@g.o">Stefaan De Roeck</mail>
35 +</author>
36 +<author title="Editor">
37 + <mail link="fox2mike@g.o">Shyam Mani</mail>
38 +</author>
39
40 <abstract>
41 This guide shows you how to install an OpenAFS server and client on Gentoo
42 @@ -28,8 +34,8 @@
43 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
44 <license/>
45
46 -<version>1.0</version>
47 -<date>2005-10-29</date>
48 +<version>1.1</version>
49 +<date>2005-11-10</date>
50
51 <chapter>
52 <title>Overview</title>
53 @@ -86,7 +92,7 @@
54 file which they are accessing, is located. They even won't notice if a server
55 will be located to another room, since every volume can be replicated and
56 moved to another server without any user noticing. The files are always
57 -accessable. Well, it's like NFS on steroids :)
58 +accessible. Well, it's like NFS on steroids :)
59 </p>
60
61 </body>
62 @@ -145,6 +151,470 @@
63 </chapter>
64
65 <chapter>
66 +<title>Upgrading from previous versions</title>
67 +<section>
68 +<title>Introduction</title>
69 +<body>
70 +
71 +<p>
72 +This section aims to help you through the process of upgrading an existing
73 +OpenAFS installation to OpenAFS version 1.4.0 or higher (or 1.2.x starting from
74 +1.2.13. The latter will not be handled specifically, as most people will want
75 +1.4 for a.o.linux-2.6 support, large file support and bug fixes).
76 +</p>
77 +
78 +<p>
79 +If you're dealing with a clean install of a 1.4 version of OpenAFS, then you can
80 +safely skip this chapter. However, if you're upgrading from a previous version,
81 +we strongly urge you to follow the guidelines in the next sections. The
82 +transition script in the ebuild is designed to assist you in quickly upgrading
83 +and restarting. Please not that it will (for safety reasons) not delete
84 +configuration files and startup scripts in old places, not automatically change
85 +your boot configuration to use the new scripts, etc. If you need further
86 +convincing, using an old OpenAFS kernel module together with the updated system
87 +binaries, may very well cause your kernel to freak out. So, let's read on for a
88 +clean and easy transition, shall we?
89 +</p>
90 +
91 +<note>
92 +This chapter has been written bearing many different system configurations in
93 +mind. Still, it is possible that due to peculiar tweaks a user has made, his or
94 +her specific situation may not be described here. A user with enough
95 +self-confidence to tweak his system should be experienced enough to apply the
96 +given remarks where appropriate. Vice versa, a user that has done little
97 +to his system but install the previous ebuild, can skip most of the warnings
98 +further on.
99 +</note>
100 +
101 +</body>
102 +</section>
103 +<section>
104 +<title>Differences to previous versions</title>
105 +<body>
106 +
107 +<p>
108 +Traditionally, OpenAFS has used the same path-conventions that IBM TransArc labs
109 +had used, before the code was forked. Understandably, old AFS setups continue
110 +using these legacy path conventions. More recent setups conform with FHS by
111 +using standard locations (as seen in many Linux distributions). The following
112 +table is a compilation of the configure-script and the README accompanying the
113 +OpenAFS distribution tarballs:
114 +</p>
115 +
116 +<table>
117 +<tr>
118 + <th>Directory</th>
119 + <th>Purpose</th>
120 + <th>Transarc Mode</th>
121 + <th>Default Mode</th>
122 + <th>translation to Gentoo</th>
123 +</tr>
124 +<tr>
125 + <ti>viceetcdir</ti>
126 + <ti>Client configuration</ti>
127 + <ti>/usr/vice/etc</ti>
128 + <ti>$(sysconfdir)/openafs</ti>
129 + <ti>/etc/openafs</ti>
130 +</tr>
131 +<tr>
132 + <ti>unnamed</ti>
133 + <ti>Client binaries</ti>
134 + <ti>unspecified</ti>
135 + <ti>$(bindir)</ti>
136 + <ti>/usr/bin</ti>
137 +</tr>
138 +<tr>
139 + <ti>afsconfdir</ti>
140 + <ti>Server configuration</ti>
141 + <ti>/usr/afs/etc</ti>
142 + <ti>$(sysconfdir)/openafs/server</ti>
143 + <ti>/etc/openafs/server</ti>
144 +</tr>
145 +<tr>
146 + <ti>afssrvdir</ti>
147 + <ti>Internal server binaries</ti>
148 + <ti>/usr/afs/bin (servers)</ti>
149 + <ti>$(libexecdir)/openafs</ti>
150 + <ti>/usr/libexec/openafs</ti>
151 +</tr>
152 +<tr>
153 + <ti>afslocaldir</ti>
154 + <ti>Server state</ti>
155 + <ti>/usr/afs/local</ti>
156 + <ti>$(localstatedir)/openafs</ti>
157 + <ti>/var/lib/openafs</ti>
158 +</tr>
159 +<tr>
160 + <ti>afsdbdir</ti>
161 + <ti>Auth/serverlist/... databases</ti>
162 + <ti>/usr/afs/db</ti>
163 + <ti>$(localstatedir)/openafs/db</ti>
164 + <ti>/var/lib/openafs/db</ti>
165 +</tr>
166 +<tr>
167 + <ti>afslogdir</ti>
168 + <ti>Log files</ti>
169 + <ti>/usr/afs/logs</ti>
170 + <ti>$(localstatedir)/openafs/logs</ti>
171 + <ti>/var/lib/openafs/logs</ti>
172 +</tr>
173 +<tr>
174 + <ti>afsbosconfig</ti>
175 + <ti>Overseer config</ti>
176 + <ti>$(afslocaldir)/BosConfig</ti>
177 + <ti>$(afsconfdir)/BosConfig</ti>
178 + <ti>/etc/openafs/BosConfig</ti>
179 +</tr>
180 +</table>
181 +
182 +<p>
183 +There are some other oddities, like binaries being put in
184 +<path>/usr/vice/etc</path> in Transarc mode, but this list is not intended
185 +to be comprehensive. It is rather meant to serve as a reference to those
186 +troubleshooting config file transition.
187 +</p>
188 +
189 +<p>
190 +Also as a result of the path changes, the default disk cache location has
191 +been changed from <path>/usr/vice/cache</path> to
192 +<path>/var/cache/openafs</path>.
193 +</p>
194 +
195 +<p>
196 +Furthermore, the init-script has been split into a client and a server part.
197 +You used to have <path>/etc/init.d/afs</path>, but now you'll end up with both
198 +<path>/etc/init.d/openafs-client</path> and
199 +<path>/etc/init.d/openafs-server</path>.
200 +Consequently, the configuration file <path>/etc/conf.d/afs</path> has been split
201 +into <path>/etc/conf.d/openafs-client</path> and
202 +<path>/etc/conf.d/openafs-server</path>. Also, options in
203 +<path>/etc/conf.d/afs</path> to turn either client or server on or off have
204 +been obsoleted.
205 +</p>
206 +
207 +<p>
208 +Another change to the init script is that it doesn't check your disk cache
209 +setup anymore. The old code required that a separate ext2 partition be
210 +mounted at <path>/usr/vice/cache</path>. There were some problems with that:
211 +</p>
212 +
213
214
215
216 --
217 gentoo-doc-cvs@g.o mailing list