* [gentoo-doc-cvs] cvs commit: openafs.xml
@ 2005-07-18 10:44 Sven Vermeulen
0 siblings, 0 replies; 7+ messages in thread
From: Sven Vermeulen @ 2005-07-18 10:44 UTC (permalink / raw
To: gentoo-doc-cvs
swift 05/07/18 10:44:57
Modified: xml/htdocs/doc/en openafs.xml
Log:
#97481 - Add information on -syslog argument
Revision Changes Path
1.20 +18 -3 xml/htdocs/doc/en/openafs.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/openafs.xml?rev=1.20&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.20&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/openafs.xml.diff?r1=1.19&r2=1.20&cvsroot=gentoo
Index: openafs.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- openafs.xml 2 Jul 2005 09:50:30 -0000 1.19
+++ openafs.xml 18 Jul 2005 10:44:57 -0000 1.20
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.19 2005/07/02 09:50:30 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.20 2005/07/18 10:44:57 swift Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -23,10 +23,12 @@
This guide shows you how to install a openafs server and client on gentoo linux
</abstract>
+<!-- The content of this document is licensed under the CC-BY-SA license -->
+<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>0.8</version>
-<date>2005-07-02</date>
+<version>0.9</version>
+<date>2005-07-18</date>
<chapter>
<title>Overview</title>
@@ -126,6 +128,19 @@
</body>
</section>
+<section>
+<title>How Can I Debug Problems?</title>
+<body>
+
+<p>
+OpenAFS has great logging facilities. However, by default it logs straight into
+its own logs instead of through the system logging facilities you have on your
+system. To have the servers log through your system logger, use the
+<c>-syslog</c> option for all <c>bos</c> commands.
+</p>
+
+</body>
+</section>
</chapter>
<chapter>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-doc-cvs] cvs commit: openafs.xml
@ 2005-10-29 20:20 Stefano Rossi
0 siblings, 0 replies; 7+ messages in thread
From: Stefano Rossi @ 2005-10-29 20:20 UTC (permalink / raw
To: gentoo-doc-cvs
so 05/10/29 20:20:57
Modified: xml/htdocs/doc/en openafs.xml
Log:
#108338 OpenAFS updated
Revision Changes Path
1.21 +133 -131 xml/htdocs/doc/en/openafs.xml
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
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/openafs.xml?rev=1.21&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/openafs.xml.diff?r1=1.20&r2=1.21&cvsroot=gentoo
Index: openafs.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- openafs.xml 18 Jul 2005 10:44:57 -0000 1.20
+++ openafs.xml 29 Oct 2005 20:20:57 -0000 1.21
@@ -1,9 +1,9 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.20 2005/07/18 10:44:57 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.21 2005/10/29 20:20:57 so Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<guide link = "/doc/en/openafs.xml">
+<guide link="/doc/en/openafs.xml">
<title>Gentoo Linux OpenAFS Guide</title>
<author title="Editor">
@@ -20,7 +20,8 @@
</author>
<abstract>
-This guide shows you how to install a openafs server and client on gentoo linux
+This guide shows you how to install an OpenAFS server and client on Gentoo
+Linux.
</abstract>
<!-- The content of this document is licensed under the CC-BY-SA license -->
@@ -37,21 +38,21 @@
<body>
<p>
-This document provides you with all neccessary steps to install an openafs
-server on Gentoo Linux. Parts of this document are taken from the AFS FAQ and
-IBM's Quick Beginnings guide on AFS. Well, never reinvent the wheel :)
+This document provides you with all neccessary steps to install an OpenAFS
+server on Gentoo Linux. Parts of this document are taken from the AFS FAQ and
+IBM's Quick Beginnings guide on AFS. Well, never reinvent the wheel. :)
</p>
</body>
</section>
<section>
-<title>What is AFS ?</title>
+<title>What is AFS?</title>
<body>
<p>
AFS is a distributed filesystem that enables co-operating hosts
(clients and servers) to efficiently share filesystem resources
-across both local area and wide area networks. Clients hold a
+across both local area and wide area networks. Clients hold a
cache for often used objects (files), to get quicker
access to them.
</p>
@@ -59,70 +60,70 @@
<p>
AFS is based on a distributed file system originally developed
at the Information Technology Center at Carnegie-Mellon University
-that was called the "Andrew File System". "Andrew" was the name of the
-research project at CMU - honouring the founders of the University. Once
-Transarc was formed and AFS became a product, the "Andrew" was dropped to
+that was called the "Andrew File System". "Andrew" was the name of the
+research project at CMU - honouring the founders of the University. Once
+Transarc was formed and AFS became a product, the "Andrew" was dropped to
indicate that AFS had gone beyond the Andrew research project and had become
-a supported, product quality filesystem. However, there were a number of
-existing cells that rooted their filesystem as /afs. At the time, changing
-the root of the filesystem was a non-trivial undertaking. So, to save the
-early AFS sites from having to rename their filesystem, AFS remained as the
+a supported, product quality filesystem. However, there were a number of
+existing cells that rooted their filesystem as /afs. At the time, changing
+the root of the filesystem was a non-trivial undertaking. So, to save the
+early AFS sites from having to rename their filesystem, AFS remained as the
name and filesystem root.
</p>
</body>
</section>
<section>
-<title>What is an AFS cell ?</title>
+<title>What is an AFS cell?</title>
<body>
<p>
-An AFS cell is a collection of servers grouped together administratively
-and presenting a single, cohesive filesystem. Typically, an AFS cell is a set
-of hosts that use the same Internet domain name (like for example gentoo.org)
-Users log into AFS client workstations which request information and files
-from the cell's servers on behalf of the users. Users won't know on which server
-a 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 :)
+An AFS cell is a collection of servers grouped together administratively and
+presenting a single, cohesive filesystem. Typically, an AFS cell is a set of
+hosts that use the same Internet domain name (for example, gentoo.org) Users
+log into AFS client workstations which request information and files from the
+cell's servers on behalf of the users. Users won't know on which server a
+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 :)
</p>
</body>
</section>
<section>
-<title>What are the benefits of using AFS ?</title>
+<title>What are the benefits of using AFS?</title>
<body>
<p>
-The main strengths of AFS are its:
+The main strengths of AFS are its:
caching facility (on client side, typically 100M to 1GB),
security features (Kerberos 4 based, access control lists),
simplicity of addressing (you just have one filesystem),
scalability (add further servers to your cell as needed),
-communications protocol.
+communications protocol.
</p>
</body>
</section>
<section>
-<title>Where can i get more information ?</title>
+<title>Where can I get more information?</title>
<body>
<p>
-Read the <uri link="http://www.angelfire.com/hi/plutonic/afs-faq.html">AFS
+Read the <uri link="http://www.angelfire.com/hi/plutonic/afs-faq.html">AFS
FAQ</uri>.
</p>
<p>
-Openafs main page is at <uri
+OpenAFS main page is at <uri
link="http://www.openafs.org">www.openafs.org</uri>.
</p>
<p>
AFS was originally developed by Transarc which is now owned by IBM.
You can find some information about AFS on
-<uri link="http://www.transarc.ibm.com/Product/EFS/AFS/index.html">Transarcs
+<uri link="http://www.transarc.ibm.com/Product/EFS/AFS/index.html">Transarc's
Webpage</uri>.
</p>
@@ -135,7 +136,7 @@
<p>
OpenAFS has great logging facilities. However, by default it logs straight into
its own logs instead of through the system logging facilities you have on your
-system. To have the servers log through your system logger, use the
+system. To have the servers log through your system logger, use the
<c>-syslog</c> option for all <c>bos</c> commands.
</p>
@@ -150,7 +151,7 @@
<body>
<p>
-You can get the original IBM AFS Documentation. It is very well written and you
+You can get the original IBM AFS Documentation. It is very well written and you
really want read it if it is up to you to administer a AFS Server.
</p>
@@ -169,20 +170,20 @@
<body>
<note>
-All commands should be written in one line !! In this document they are
+All commands should be written in one line!! In this document they are
sometimes wrapped to two lines to make them easier to read.
</note>
<note>
-Unfortunately the AFS Client needs a ext2 partiton for it's cache to run
-correctly, because there are some locking issues with reiserfs. You need to
-create a ext2 partition of approx. 200MB (more won't hurt) and mount it to
+Unfortunately the AFS Client needs a ext2 partiton for its cache to run
+correctly, because there are some locking issues with reiserfs. You need to
+create a ext2 partition of approx. 200MB (more won't hurt) and mount it to
<path>/usr/vice/cache</path>
</note>
<p>
-You should adjust the two files CellServDB and ThisCell before you build the
-afs client. (These files are in <path>/usr/portage/net-fs/openafs/files</path>)
+You should adjust the two files CellServDB and ThisCell before you build the
+AFS client. (These files are in <path>/usr/portage/net-fs/openafs/files</path>)
</p>
<pre caption="Adjusting CellServDB and ThisCell">
@@ -200,10 +201,10 @@
</warn>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-doc-cvs] cvs commit: openafs.xml
@ 2005-10-29 21:10 Stefano Rossi
0 siblings, 0 replies; 7+ messages in thread
From: Stefano Rossi @ 2005-10-29 21:10 UTC (permalink / raw
To: gentoo-doc-cvs
so 05/10/29 21:10:15
Modified: xml/htdocs/doc/en openafs.xml
Log:
bumped version
Revision Changes Path
1.22 +3 -3 xml/htdocs/doc/en/openafs.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/openafs.xml?rev=1.22&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.22&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/openafs.xml.diff?r1=1.21&r2=1.22&cvsroot=gentoo
Index: openafs.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- openafs.xml 29 Oct 2005 20:20:57 -0000 1.21
+++ openafs.xml 29 Oct 2005 21:10:15 -0000 1.22
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.21 2005/10/29 20:20:57 so Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.22 2005/10/29 21:10:15 so Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -28,8 +28,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>0.9</version>
-<date>2005-07-18</date>
+<version>1.0</version>
+<date>2005-10-29</date>
<chapter>
<title>Overview</title>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-doc-cvs] cvs commit: openafs.xml
@ 2005-11-09 20:58 Shyam Mani
0 siblings, 0 replies; 7+ messages in thread
From: Shyam Mani @ 2005-11-09 20:58 UTC (permalink / raw
To: gentoo-doc-cvs
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="fnjordy@gmail.com">Steven McCoy</mail>
</author>
+<author title="Editor">
+ <mail link="stefaan@gentoo.org">Stefaan De Roeck</mail>
+</author>
+<author title="Editor">
+ <mail link="fox2mike@gentoo.org">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>
+
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-doc-cvs] cvs commit: openafs.xml
@ 2007-06-29 8:33 Xavier Neys
0 siblings, 0 replies; 7+ messages in thread
From: Xavier Neys @ 2007-06-29 8:33 UTC (permalink / raw
To: gentoo-doc-cvs
neysx 07/06/29 08:33:12
Modified: openafs.xml
Log:
Update from #176407
Revision Changes Path
1.24 xml/htdocs/doc/en/openafs.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/openafs.xml?rev=1.24&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/openafs.xml?rev=1.24&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/openafs.xml?r1=1.23&r2=1.24
Index: openafs.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- openafs.xml 9 Nov 2005 20:58:07 -0000 1.23
+++ openafs.xml 29 Jun 2007 08:33:12 -0000 1.24
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.23 2005/11/09 20:58:07 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.24 2007/06/29 08:33:12 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -7,6 +7,9 @@
<title>Gentoo Linux OpenAFS Guide</title>
<author title="Editor">
+ <mail link="stefaan@gentoo.org">Stefaan De Roeck</mail>
+</author>
+<author title="Editor">
<mail link="darks@gentoo.org">Holger Brueckner</mail>
</author>
<author title="Editor">
@@ -19,9 +22,6 @@
<mail link="fnjordy@gmail.com">Steven McCoy</mail>
</author>
<author title="Editor">
- <mail link="stefaan@gentoo.org">Stefaan De Roeck</mail>
-</author>
-<author title="Editor">
<mail link="fox2mike@gentoo.org">Shyam Mani</mail>
</author>
@@ -34,8 +34,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.1</version>
-<date>2005-11-10</date>
+<version>1.2</version>
+<date>2007-06-29</date>
<chapter>
<title>Overview</title>
@@ -44,7 +44,7 @@
<body>
<p>
-This document provides you with all neccessary steps to install an OpenAFS
+This document provides you with all necessary steps to install an OpenAFS
server on Gentoo Linux. Parts of this document are taken from the AFS FAQ and
IBM's Quick Beginnings guide on AFS. Well, never reinvent the wheel. :)
</p>
@@ -78,7 +78,7 @@
</p>
</body>
-</section>
+</section>
<section>
<title>What is an AFS cell?</title>
<body>
@@ -92,11 +92,11 @@
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
-accessible. Well, it's like NFS on steroids :)
+accessible. Well, it's like NFS on steroids :)
</p>
</body>
-</section>
+</section>
<section>
<title>What are the benefits of using AFS?</title>
<body>
@@ -111,7 +111,7 @@
</p>
</body>
-</section>
+</section>
<section>
<title>Where can I get more information?</title>
<body>
@@ -134,7 +134,7 @@
</p>
</body>
-</section>
+</section>
<section>
<title>How Can I Debug Problems?</title>
<body>
@@ -160,7 +160,7 @@
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).
+1.4 for a.o. linux-2.6 support, large file support and bug fixes).
</p>
<p>
@@ -168,7 +168,7 @@
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
+and restarting. Please note 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
@@ -289,7 +289,7 @@
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.
+been obsoleted.
</p>
<p>
@@ -309,7 +309,7 @@
<li>
Some people use soft-links to point to the real disk cache location.
The init script didn't like this, because then this cache location
- didn't turn up in <path>/proc/mounts</path>.
+ didn't turn up in <path>/proc/mounts</path>.
</li>
<li>
Many prefer ext3 over ext2 nowadays. Both filesystems are valid for
@@ -342,7 +342,7 @@
</p>
<pre caption="Checking your CONFIG_PROTECT_MASK">
-# <i>emerge info | grep "CONFIG_PROTECT_MASK</i>
+# <i>emerge info | grep "CONFIG_PROTECT_MASK"</i>
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d"
</pre>
@@ -367,7 +367,7 @@
<ul>
<li>
- <path>/usr/afs/etc</path> is copied to<path>/etc/openafs/server</path>
+ <path>/usr/afs/etc</path> is copied to <path>/etc/openafs/server</path>
</li>
<li>
<path>/usr/vice/etc</path> is copied to <path>/etc/openafs</path>
@@ -378,7 +378,7 @@
<li>
<path>/usr/afs/local/BosConfig</path> is copied to
<path>/etc/openafs/BosConfig</path>, while replacing occurrences of
- <path>/usr/afs/bin/</path> with <path>/usr/libexec/openafs</path>,
+ <path>/usr/afs/bin/</path> with <path>/usr/libexec/openafs</path>,
<path>/usr/afs/etc</path> with <path>/etc/openafs/server</path>
and <path>/usr/afs/bin</path> (without the / as previously) with
<path>/usr/bin</path>
@@ -459,7 +459,7 @@
<p>
Before starting the OpenAFS client again, please take time to check your
-cache settings. They are determined by <path>/etc/openafs/cacheinfo</path>.
+cache settings. They are determined by <path>/etc/openafs/cacheinfo</path>.
To restart your OpenAFS client installation, please type the following:
</p>
@@ -533,7 +533,7 @@
the OpenAFS client and server on startup. Those who don't can safely skip
this section. If you had your system configured to start them automatically,
you will need to re-enable this, because the names of the init scripts have
-changed.
+changed.
</p>
<pre caption="Re-enabling OpenAFS startup at boot time">
@@ -555,10 +555,10 @@
<body>
<p>
-Don't panic. You shouldn't have lost any data or configuration files. So
-let's analyze the situation. Please file a bug at
-<uri link="http://bugs.gentoo.org">bugs.gentoo.org</uri> in any case,
-preferably with as much information as possible.
+Don't panic. You shouldn't have lost any data or configuration files. So let's
+analyze the situation. Please file a bug at <uri
+link="http://bugs.gentoo.org">bugs.gentoo.org</uri> in any case, preferably
+with as much information as possible.
</p>
<p>
@@ -572,7 +572,7 @@
</li>
<li>
Check <path>/etc/openafs/cacheinfo</path>. It should be of the form:
- /afs:{path to disk cache}:{number of blocks for disk cache}.
+ /afs:{path to disk cache}:{number of blocks for disk cache}.
Normally, your disk cache will be located at
<path>/var/cache/openafs</path>.
</li>
@@ -638,7 +638,7 @@
Documentation.
</p>
-</body>
+</body>
</section>
</chapter>
@@ -648,11 +648,6 @@
<title>Building the Client</title>
<body>
-<note>
-All commands should be written in one line!! In this document they are
-sometimes wrapped to two lines to make them easier to read.
-</note>
-
<pre caption="Installing openafs">
# <i>emerge net-fs/openafs</i>
</pre>
@@ -702,7 +697,7 @@
10.0.0.1 #storage
ThisCell:
-netlabs
+netlabs
</pre>
<warn>
@@ -711,7 +706,14 @@
</warn>
<p>
-For a quick start, you can now start <path>/etc/init.d/openafs/client</path> and
+CellServDB tells your client which server(s) it needs to contact for a
+specific cell. ThisCell should be quite obvious. Normally you use a name
+which is unique for your organisation. Your (official) domain might be a
+good choice.
+</p>
+
+<p>
+For a quick start, you can now start <path>/etc/init.d/openafs-client</path> and
use <c>klog</c> to authenticate yourself and start using your access to the
cell. For automatic logons to you cell, you want to consult the appropriate
section below.
@@ -725,12 +727,13 @@
<note>
Unfortunately the AFS Client needs a ext2/3 filesystem for its cache to run
-correctly, because there are some issues with reiserfs.
+correctly. There are some issues when using other filesystems (using e.g.
+reiserfs is not a good idea).
</note>
<p>
-You can house your cache on an existing filesystem (if it's ext2/3), but some
-may want to create a separate partition for that. The default location of the
+You can house your cache on an existing filesystem (if it's ext2/3), or you
+may want to have a separate partition for that. The default location of the
cache is <path>/var/cache/openafs</path>, but you can change that by editing
<path>/etc/openafs/cacheinfo</path>. A standard size for your cache is
200MB, but more won't hurt.
@@ -739,39 +742,6 @@
</body>
</section>
<section>
-<title>Adjusting the cell access configuration</title>
-<body>
-
-<p>
-In case you want to do more than just read-only browsing of globally available
-AFS cells, you need to adjust the two files CellServDB and ThisCell. These
-are located in <path>/etc/openafs</path>.
-</p>
-
-<pre caption="Adjusting CellServDB and ThisCell">
-CellServDB:
->netlabs #Cell name
-10.0.0.1 #storage
-
-ThisCell:
-netlabs
-</pre>
-
-<warn>
-Only use spaces inside the <path>CellServDB</path> file. The client will most
-likely fail if you use TABs.
-</warn>
-
-<p>
-CellServDB tells your client which server(s) it needs to contact for a
-specific cell. ThisCell should be quite obvious. Normally you use a name
-which is unique for your organisation. Your (official) domain might be a
-good choice.
-</p>
-
-</body>
-</section>
-<section>
<title>Starting AFS on startup</title>
<body>
@@ -786,8 +756,8 @@
if your AFS server is down. (And this is quite a long long time)
</warn>
-<pre caption="Adding AFS server to the default runlevel">
-# <i>rc-update add openafs-server default</i>
+<pre caption="Adding AFS client to the default runlevel">
+# <i>rc-update add openafs-client default</i>
</pre>
</body>
@@ -800,9 +770,14 @@
<title>Building the Server</title>
<body>
+<note>
+All commands should be written in one line!! In this document they are
+sometimes wrapped to two lines to make them easier to read.
+</note>
+
<p>
-The following command will install all necessary binaries for setting up an AFS
-Server <e>and</e> Client.
+If you haven't already done so, the following command will install all
+necessary binaries for setting up an AFS Server <e>and</e> Client.
</p>
<pre caption="Installing openafs">
@@ -812,20 +787,11 @@
</body>
</section>
<section>
-<title>Starting AFS Server</title>
+<title>Starting AFS Server</title>
<body>
<p>
-You need to remove the sample CellServDB and ThisCell file first.
-</p>
-
-<pre caption="Remove sample files">
-# <i>rm /usr/vice/etc/ThisCell</i>
-# <i>rm /usr/vice/etc/CellServDB</i>
-</pre>
-
-<p>
-Next you will run the <c>bosserver</c> command to initialize the Basic OverSeer
+You need to run the <c>bosserver</c> command to initialize the Basic OverSeer
(BOS) Server, which monitors and controls other AFS server processes on its
server machine. Think of it as init for the system. Include the <c>-noauth</c>
flag to disable authorization checking, since you haven't added the admin user
@@ -844,17 +810,17 @@
</pre>
<p>
-Verify that the BOS Server created <path>/usr/vice/etc/CellServDB</path>
-and <path>/usr/vice/etc/ThisCell</path>
+Verify that the BOS Server created <path>/etc/openafs/server/CellServDB</path>
+and <path>/etc/openafs/server/ThisCell</path>
</p>
<pre caption="Check if CellServDB and ThisCell are created">
-# <i>ls -al /usr/vice/etc/</i>
+# <i>ls -al /etc/openafs/server/</i>
-rw-r--r-- 1 root root 41 Jun 4 22:21 CellServDB
-rw-r--r-- 1 root root 7 Jun 4 22:21 ThisCell
</pre>
-</body>
+</body>
</section>
<section>
<title>Defining Cell Name and Membership for Server Process</title>
@@ -894,8 +860,8 @@
<body>
<p>
-Next use the <c>bos create</c> command to create entries for the four database
-server processes in the <path>/etc/openafs/BosConfig</path> file. The four
+Next use the <c>bos create</c> command to create entries for the four database
+server processes in the <path>/etc/openafs/BosConfig</path> file. The four
processes run on database server machines only.
</p>
@@ -923,13 +889,21 @@
Very important :)
</ti>
</tr>
-</table>
+</table>
<pre caption="Create entries for the database processes">
-# <i>bos create <server name> kaserver simple /usr/libexec/openafs/kaserver -cell <cell name> -noauth</i>
-# <i>bos create <server name> buserver simple /usr/libexec/openafs/buserver -cell <cell name> -noauth</i>
-# <i>bos create <server name> ptserver simple /usr/libexec/openafs/ptserver -cell <cell name> -noauth</i>
-# <i>bos create <server name> vlserver simple /usr/libexec/openafs/vlserver -cell <cell name> -noauth</i>
+# <i>bos create <server name> kaserver \
+simple /usr/libexec/openafs/kaserver \
+-cell <cell name> -noauth</i>
+# <i>bos create <server name> buserver \
+simple /usr/libexec/openafs/buserver \
+-cell <cell name> -noauth</i>
+# <i>bos create <server name> ptserver \
+simple /usr/libexec/openafs/ptserver \
+-cell <cell name> -noauth</i>
+# <i>bos create <server name> \
+vlserver simple /usr/libexec/openafs/vlserver \
+-cell <cell name> -noauth</i>
</pre>
<p>
@@ -995,7 +969,7 @@
</pre>
<p>
-Run the <c>bos adduser</c> command, to add the <b>admin</b> user to
+Run the <c>bos adduser</c> command, to add the <b>admin</b> user to
the <path>/etc/openafs/server/UserList</path>.
</p>
@@ -1004,7 +978,7 @@
</pre>
<p>
-Issue the <c>bos addkey</c> command to define the AFS Server
+Issue the <c>bos addkey</c> command to define the AFS Server
encryption key in <path>/etc/openafs/server/KeyFile</path>
</p>
@@ -1049,13 +1023,50 @@
system:administrators
</pre>
+</body>
+</section>
+<section>
+<title>Properly (re-)starting the AFS server</title>
+<body>
+
+<p>
+At this moment, proper authentication is possible, and the OpenAFS server can
+be started in a normal fashion. Note that authentication also requires a
+running OpenAFS client (set it up is described in the previous chapter).
+<!-- Left out because deemed confusing>
+Continuing without this step is possible, but in that case a quick restart of
+the server is required, as demonstrated at the end of this section.
+<-->
+</p>
+
+<pre caption="Shutdown bosserver">
+# <i>bos shutdown <server name> -wait -noauth</i>
+# <i>killall bosserver</i>
+</pre>
+
+<pre caption="Normal OpenAFS server (and client) startup">
+# <i>/etc/init.d/openafs-server start</i>
+# <i>/etc/init.d/openafs-client start</i>
+</pre>
+
+<pre caption="Adding AFS server to the default runlevel">
+# <i>rc-update add openafs-server default</i>
+</pre>
+
+<pre caption="Getting a token as the admin user">
+# <i>klog admin</i>
+</pre>
+
+<!-- Left out because deemed confusing>
<p>
-Restart all AFS Server processes
+If you chose not to restart OpenAFS without the -noauth flag, you can simply
+perform the following procedure instead:
</p>
<pre caption="Restart all AFS server processes">
# <i>bos restart <server name> -all -cell <cell name> -noauth</i>
</pre>
+<-->
</body>
</section>
@@ -1064,18 +1075,18 @@
<body>
<p>
-Start the <c>fs</c> process, which consists of the
-File Server,
-Volume Server and Salvager (fileserver,
-volserver and salvager processes).
+Start the <c>fs</c> process, which consists of the File Server, Volume Server
+and Salvager (fileserver, volserver and salvager processes).
</p>
<pre caption="Start the fs process">
-# <i>bos create <server name> fs fs /usr/libexec/openafs/fileserver /usr/libexec/openafs/volserver /usr/libexec/openafs/salvager -cell <cell name> -noauth</i>
+# <i>bos create <server name> fs \
+fs /usr/libexec/openafs/fileserver /usr/libexec/openafs/volserver /usr/libexec/openafs/salvager \
+-cell <cell name> -noauth</i>
</pre>
<p>
-Verify that all processes are running
+Verify that all processes are running:
</p>
<pre caption="Check if all processes are running">
@@ -1114,14 +1125,19 @@
</p>
<p>
-If you are installing the first AFS Server ever in the cell create the
-first AFS volume, <b>root.afs</b>
+If you are installing the first AFS Server ever in the cell, create the first
+AFS volume, <b>root.afs</b>
</p>
<note>
For the partition name argument, substitute the name of one of the machine's
-AFS Server partitions. By convention
-these partitions are named <path>/vicepx</path>, where x is in the range of a-z.
+AFS Server partitions. Any filesystem mounted under a directory called
+<path>/vicepx</path>, where x is in the range of a-z, will be considered and
+used as an AFS Server partition. Any unix filesystem will do (as opposed to the
+client's cache, which can only be ext2/3). Tip: the server checks for each
+<path>/vicepx</path> mount point whether a filesystem is mounted there. If not,
+the server will not attempt to use it. This behaviour can be overridden by
+putting a file named <path>AlwaysAttach</path> in this directory.
</note>
<pre caption="Create the root.afs volume">
@@ -1145,7 +1161,7 @@
<pre caption="Synchronise the VLDB">
# <i>vos syncvldb <server name> -cell <cell name> -verbose -noauth</i>
-# <i>vos syncserv <server name> -cell <cell name> -verbose -noauth</i>
+# <i>vos syncserv <server name> -cell <cell name> -verbose -noauth</i>
</pre>
</body>
@@ -1155,9 +1171,9 @@
<body>
<pre caption="Start the update server">
-# <i>bos create <server name>
-upserver simple "/usr/libexec/openafs/upserver
--crypt /etc/openafs/server -clear /usr/libexec/openafs"
+# <i>bos create <server name> \
+upserver simple "/usr/libexec/openafs/upserver \
+-crypt /etc/openafs/server -clear /usr/libexec/openafs" \
-cell <cell name> -noauth</i>
</pre>
@@ -1172,6 +1188,16 @@
<path>/afs</path>.
</p>
+<note>
+The default OpenAFS client configuration has <b>dynroot</b> enabled.
+This option turns <path>/afs</path> into a virtual directory composed of the
+contents of your <path>/etc/openafs/CellServDB</path> file. As such, the
+following command will not work, because it requires a real AFS directory.
+You can temporarily switch dynroot off by setting <b>ENABLE_DYNROOT</b> to
+<b>no</b> in <path>/etc/conf.d/openafs-client</path>. Don't forget to issue
+a client after changing parameters.
+</note>
+
<pre caption="Set access control lists">
# <i>fs setacl /afs system:anyuser rl</i>
</pre>
@@ -1183,12 +1209,19 @@
</p>
<pre caption="Prepare the root volume">
-# <i>vos create <server name><partition name> root.cell</i>
-# <i>fs mkmount /afs/<cell name> root.cell </i>
+# <i>vos create <server name> <partition name> root.cell</i>
+# <i>fs mkmount /afs/<cell name> root.cell</i>
# <i>fs setacl /afs/<cell name> system:anyuser rl</i>
# <i>fs mkmount /afs/.<cell name> root.cell -rw</i>
</pre>
+<pre caption="Adding volumes underneath">
+# <i>vos create <server name> <partition name> <myvolume></i>
+# <i>fs mkmount /afs/<cell name>/<mymountpoint> <myvolume></i>
+# <i>fs mkmount /afs/<cell name>/.<mymountpoint> <myvolume> -rw</i>
+# <i>fs setquota /afs/<cell name>/.<mymountpoint> -max <quotum></i>
+</pre>
+
<p>
Finally you're done!!! You should now have a working AFS file server
on your local network. Time to get a big
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-doc-cvs] cvs commit: openafs.xml
@ 2007-06-29 12:11 Xavier Neys
0 siblings, 0 replies; 7+ messages in thread
From: Xavier Neys @ 2007-06-29 12:11 UTC (permalink / raw
To: gentoo-doc-cvs
neysx 07/06/29 12:11:05
Modified: openafs.xml
Log:
Fixed typo, tx ewoud
Revision Changes Path
1.25 xml/htdocs/doc/en/openafs.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/openafs.xml?rev=1.25&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/openafs.xml?rev=1.25&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/openafs.xml?r1=1.24&r2=1.25
Index: openafs.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- openafs.xml 29 Jun 2007 08:33:12 -0000 1.24
+++ openafs.xml 29 Jun 2007 12:11:05 -0000 1.25
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.24 2007/06/29 08:33:12 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.25 2007/06/29 12:11:05 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -751,9 +751,9 @@
</p>
<warn>
-You should always have a running afs server in your domain when trying to
-start the afs client. You're system won't boot until it gets some timeout
-if your AFS server is down. (And this is quite a long long time)
+You should always have a running afs server in your domain when trying to start
+the afs client. Your system won't boot until it gets some timeout if your AFS
+server is down (and this is quite a long long time.)
</warn>
<pre caption="Adding AFS client to the default runlevel">
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-doc-cvs] cvs commit: openafs.xml
@ 2007-07-01 18:58 Josh Saddler
0 siblings, 0 replies; 7+ messages in thread
From: Josh Saddler @ 2007-07-01 18:58 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 07/07/01 18:58:48
Modified: openafs.xml
Log:
final touchup from bug 176407, thanks stefaan
Revision Changes Path
1.26 xml/htdocs/doc/en/openafs.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/openafs.xml?rev=1.26&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/openafs.xml?rev=1.26&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/openafs.xml?r1=1.25&r2=1.26
Index: openafs.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- openafs.xml 29 Jun 2007 12:11:05 -0000 1.25
+++ openafs.xml 1 Jul 2007 18:58:48 -0000 1.26
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.25 2007/06/29 12:11:05 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/openafs.xml,v 1.26 2007/07/01 18:58:48 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -1032,7 +1032,7 @@
<p>
At this moment, proper authentication is possible, and the OpenAFS server can
be started in a normal fashion. Note that authentication also requires a
-running OpenAFS client (set it up is described in the previous chapter).
+running OpenAFS client (setting it up is described in the previous chapter).
<!-- Left out because deemed confusing>
Continuing without this step is possible, but in that case a quick restart of
the server is required, as demonstrated at the end of this section.
@@ -1195,7 +1195,7 @@
following command will not work, because it requires a real AFS directory.
You can temporarily switch dynroot off by setting <b>ENABLE_DYNROOT</b> to
<b>no</b> in <path>/etc/conf.d/openafs-client</path>. Don't forget to issue
-a client after changing parameters.
+a client restart after changing parameters.
</note>
<pre caption="Set access control lists">
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2007-07-01 18:59 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-10-29 21:10 [gentoo-doc-cvs] cvs commit: openafs.xml Stefano Rossi
-- strict thread matches above, loose matches on Subject: below --
2007-07-01 18:58 Josh Saddler
2007-06-29 12:11 Xavier Neys
2007-06-29 8:33 Xavier Neys
2005-11-09 20:58 Shyam Mani
2005-10-29 20:20 Stefano Rossi
2005-07-18 10:44 Sven Vermeulen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox