1 |
so 05/10/29 20:20:57 |
2 |
|
3 |
Modified: xml/htdocs/doc/en openafs.xml |
4 |
Log: |
5 |
#108338 OpenAFS updated |
6 |
|
7 |
Revision Changes Path |
8 |
1.21 +133 -131 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.21&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.21&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.20&r2=1.21&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.20 |
18 |
retrieving revision 1.21 |
19 |
diff -u -r1.20 -r1.21 |
20 |
--- openafs.xml 18 Jul 2005 10:44:57 -0000 1.20 |
21 |
+++ openafs.xml 29 Oct 2005 20:20:57 -0000 1.21 |
22 |
@@ -1,9 +1,9 @@ |
23 |
<?xml version='1.0' encoding="UTF-8"?> |
24 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.20 2005/07/18 10:44:57 swift Exp $ --> |
25 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.21 2005/10/29 20:20:57 so Exp $ --> |
26 |
|
27 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
28 |
|
29 |
-<guide link = "/doc/en/openafs.xml"> |
30 |
+<guide link="/doc/en/openafs.xml"> |
31 |
<title>Gentoo Linux OpenAFS Guide</title> |
32 |
|
33 |
<author title="Editor"> |
34 |
@@ -20,7 +20,8 @@ |
35 |
</author> |
36 |
|
37 |
<abstract> |
38 |
-This guide shows you how to install a openafs server and client on gentoo linux |
39 |
+This guide shows you how to install an OpenAFS server and client on Gentoo |
40 |
+Linux. |
41 |
</abstract> |
42 |
|
43 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
44 |
@@ -37,21 +38,21 @@ |
45 |
<body> |
46 |
|
47 |
<p> |
48 |
-This document provides you with all neccessary steps to install an openafs |
49 |
-server on Gentoo Linux. Parts of this document are taken from the AFS FAQ and |
50 |
-IBM's Quick Beginnings guide on AFS. Well, never reinvent the wheel :) |
51 |
+This document provides you with all neccessary steps to install an OpenAFS |
52 |
+server on Gentoo Linux. Parts of this document are taken from the AFS FAQ and |
53 |
+IBM's Quick Beginnings guide on AFS. Well, never reinvent the wheel. :) |
54 |
</p> |
55 |
|
56 |
</body> |
57 |
</section> |
58 |
<section> |
59 |
-<title>What is AFS ?</title> |
60 |
+<title>What is AFS?</title> |
61 |
<body> |
62 |
|
63 |
<p> |
64 |
AFS is a distributed filesystem that enables co-operating hosts |
65 |
(clients and servers) to efficiently share filesystem resources |
66 |
-across both local area and wide area networks. Clients hold a |
67 |
+across both local area and wide area networks. Clients hold a |
68 |
cache for often used objects (files), to get quicker |
69 |
access to them. |
70 |
</p> |
71 |
@@ -59,70 +60,70 @@ |
72 |
<p> |
73 |
AFS is based on a distributed file system originally developed |
74 |
at the Information Technology Center at Carnegie-Mellon University |
75 |
-that was called the "Andrew File System". "Andrew" was the name of the |
76 |
-research project at CMU - honouring the founders of the University. Once |
77 |
-Transarc was formed and AFS became a product, the "Andrew" was dropped to |
78 |
+that was called the "Andrew File System". "Andrew" was the name of the |
79 |
+research project at CMU - honouring the founders of the University. Once |
80 |
+Transarc was formed and AFS became a product, the "Andrew" was dropped to |
81 |
indicate that AFS had gone beyond the Andrew research project and had become |
82 |
-a supported, product quality filesystem. However, there were a number of |
83 |
-existing cells that rooted their filesystem as /afs. At the time, changing |
84 |
-the root of the filesystem was a non-trivial undertaking. So, to save the |
85 |
-early AFS sites from having to rename their filesystem, AFS remained as the |
86 |
+a supported, product quality filesystem. However, there were a number of |
87 |
+existing cells that rooted their filesystem as /afs. At the time, changing |
88 |
+the root of the filesystem was a non-trivial undertaking. So, to save the |
89 |
+early AFS sites from having to rename their filesystem, AFS remained as the |
90 |
name and filesystem root. |
91 |
</p> |
92 |
|
93 |
</body> |
94 |
</section> |
95 |
<section> |
96 |
-<title>What is an AFS cell ?</title> |
97 |
+<title>What is an AFS cell?</title> |
98 |
<body> |
99 |
|
100 |
<p> |
101 |
-An AFS cell is a collection of servers grouped together administratively |
102 |
-and presenting a single, cohesive filesystem. Typically, an AFS cell is a set |
103 |
-of hosts that use the same Internet domain name (like for example gentoo.org) |
104 |
-Users log into AFS client workstations which request information and files |
105 |
-from the cell's servers on behalf of the users. Users won't know on which server |
106 |
-a file which they are accessing, is located. They even won't notice if a server |
107 |
-will be located to another room, since every volume can be replicated and moved |
108 |
-to another server without any user noticing. The files are always accessable. |
109 |
-Well it's like NFS on steroids :) |
110 |
+An AFS cell is a collection of servers grouped together administratively and |
111 |
+presenting a single, cohesive filesystem. Typically, an AFS cell is a set of |
112 |
+hosts that use the same Internet domain name (for example, gentoo.org) Users |
113 |
+log into AFS client workstations which request information and files from the |
114 |
+cell's servers on behalf of the users. Users won't know on which server a |
115 |
+file which they are accessing, is located. They even won't notice if a server |
116 |
+will be located to another room, since every volume can be replicated and |
117 |
+moved to another server without any user noticing. The files are always |
118 |
+accessable. Well, it's like NFS on steroids :) |
119 |
</p> |
120 |
|
121 |
</body> |
122 |
</section> |
123 |
<section> |
124 |
-<title>What are the benefits of using AFS ?</title> |
125 |
+<title>What are the benefits of using AFS?</title> |
126 |
<body> |
127 |
|
128 |
<p> |
129 |
-The main strengths of AFS are its: |
130 |
+The main strengths of AFS are its: |
131 |
caching facility (on client side, typically 100M to 1GB), |
132 |
security features (Kerberos 4 based, access control lists), |
133 |
simplicity of addressing (you just have one filesystem), |
134 |
scalability (add further servers to your cell as needed), |
135 |
-communications protocol. |
136 |
+communications protocol. |
137 |
</p> |
138 |
|
139 |
</body> |
140 |
</section> |
141 |
<section> |
142 |
-<title>Where can i get more information ?</title> |
143 |
+<title>Where can I get more information?</title> |
144 |
<body> |
145 |
|
146 |
<p> |
147 |
-Read the <uri link="http://www.angelfire.com/hi/plutonic/afs-faq.html">AFS |
148 |
+Read the <uri link="http://www.angelfire.com/hi/plutonic/afs-faq.html">AFS |
149 |
FAQ</uri>. |
150 |
</p> |
151 |
|
152 |
<p> |
153 |
-Openafs main page is at <uri |
154 |
+OpenAFS main page is at <uri |
155 |
link="http://www.openafs.org">www.openafs.org</uri>. |
156 |
</p> |
157 |
|
158 |
<p> |
159 |
AFS was originally developed by Transarc which is now owned by IBM. |
160 |
You can find some information about AFS on |
161 |
-<uri link="http://www.transarc.ibm.com/Product/EFS/AFS/index.html">Transarcs |
162 |
+<uri link="http://www.transarc.ibm.com/Product/EFS/AFS/index.html">Transarc's |
163 |
Webpage</uri>. |
164 |
</p> |
165 |
|
166 |
@@ -135,7 +136,7 @@ |
167 |
<p> |
168 |
OpenAFS has great logging facilities. However, by default it logs straight into |
169 |
its own logs instead of through the system logging facilities you have on your |
170 |
-system. To have the servers log through your system logger, use the |
171 |
+system. To have the servers log through your system logger, use the |
172 |
<c>-syslog</c> option for all <c>bos</c> commands. |
173 |
</p> |
174 |
|
175 |
@@ -150,7 +151,7 @@ |
176 |
<body> |
177 |
|
178 |
<p> |
179 |
-You can get the original IBM AFS Documentation. It is very well written and you |
180 |
+You can get the original IBM AFS Documentation. It is very well written and you |
181 |
really want read it if it is up to you to administer a AFS Server. |
182 |
</p> |
183 |
|
184 |
@@ -169,20 +170,20 @@ |
185 |
<body> |
186 |
|
187 |
<note> |
188 |
-All commands should be written in one line !! In this document they are |
189 |
+All commands should be written in one line!! In this document they are |
190 |
sometimes wrapped to two lines to make them easier to read. |
191 |
</note> |
192 |
|
193 |
<note> |
194 |
-Unfortunately the AFS Client needs a ext2 partiton for it's cache to run |
195 |
-correctly, because there are some locking issues with reiserfs. You need to |
196 |
-create a ext2 partition of approx. 200MB (more won't hurt) and mount it to |
197 |
+Unfortunately the AFS Client needs a ext2 partiton for its cache to run |
198 |
+correctly, because there are some locking issues with reiserfs. You need to |
199 |
+create a ext2 partition of approx. 200MB (more won't hurt) and mount it to |
200 |
<path>/usr/vice/cache</path> |
201 |
</note> |
202 |
|
203 |
<p> |
204 |
-You should adjust the two files CellServDB and ThisCell before you build the |
205 |
-afs client. (These files are in <path>/usr/portage/net-fs/openafs/files</path>) |
206 |
+You should adjust the two files CellServDB and ThisCell before you build the |
207 |
+AFS client. (These files are in <path>/usr/portage/net-fs/openafs/files</path>) |
208 |
</p> |
209 |
|
210 |
<pre caption="Adjusting CellServDB and ThisCell"> |
211 |
@@ -200,10 +201,10 @@ |
212 |
</warn> |
213 |
|
214 |
|
215 |
|
216 |
-- |
217 |
gentoo-doc-cvs@g.o mailing list |