* README.Debian: Document that the client cache partition must be ext2

    or ext3 and that XFS and ReiserFS will not work.  upserver and
    upclient are now provided.  Provide some information about why
    kaserver is not provided.  (Closes: #249315)

diff --git a/debian/README.Debian b/debian/README.Debian
index 2a5f83c16db14a077b27842341ad013fb20d10b2..a07eb492f1e6fcfa1beeb0f6857368007975daf7 100644 (file)
--- a/debian/README.Debian
+++ b/debian/README.Debian
@@ -1,29 +1,30 @@
-openafs for Debian
-----------------------
+OpenAFS for Debian
+------------------
+
+* AFS users may be confused by the directory layout.  The files that
+  normally go in /usr/vice/etc go in /etc/openafs.  The cache should be
+  mounted on /var/cache/openafs.
+
+* The AFS client cache must be on an ext2 or ext3 partition.  Other file
+  systems often do not support the semantics required by the AFS kernel
+  module and will cause kernel faults.  In particular, XFS and ReiserFS
+  will NOT work.
 
 * No manual pages are included.  I need to find out if versions exist
   that are OK for copyright reasons.
 
 * Documentation can be found at http://www.openafs.org.  If want to
-set up a new cell, read the docs there and then look at the example
-session in configuration-transcript.txt.gz in this directory.  You
-should also read README.servers.  The procedure outlined in these two
-files is much simpler and more secure than the one in the Openafs
-documentation, but the Openafs documentation provides useful
-background.
-
-*  AFS users may be confused by the directory layout.  The files that
-   normally go in /usr/vice/etc go in /etc/openafs.  The cache should
-   be mounted on /var/cache/openafs.
+  set up a new cell, read the docs there and then look at the example
+  session in configuration-transcript.txt.gz in this directory.  You
+  should also read README.servers.  The procedure outlined in these two
+  files is much simpler and more secure than the one in the Openafs
+  documentation, but the Openafs documentation provides useful background.
 
 * The libopenafs-dev package only includes static libraries because
-the shared libraries built by AFS are not compatible with Debian
-policy.  They include non-PIC code and do not have a stable ABI.
-
-* The upserver, upclient and kaserver are not included.
-
-
-
+  the shared libraries built by AFS are not compatible with Debian policy.
+  They include non-PIC code and do not have a stable ABI.
 
+* kaserver is not included.  New AFS cells should use Kerberos v5 rather
+  than the old K4-based kaserver KDC.
 
- -- Sam Hartman <hartmans@mit.edu>, Tue Aug  5 16:09:13 2003
+ -- Russ Allbery <rra@stanford.edu>, Sat Apr 30 11:15:25 2005

diff --git a/debian/changelog b/debian/changelog
index 871f24ebce81d199a175dcec591c6d05f0107e03..0fc8657ed92f2895e61820a33700497483a86ca8 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -4,6 +4,10 @@ openafs (1.3.81-3sarge1) unstable; urgency=low
     missing symbols and therefore unusable.  (Closes: #308844)
   * In the init script, handle modules named either with or without the
     .mp extension on SMP hosts.  (Closes: #305389, #307280, #307797)
+  * README.Debian: Document that the client cache partition must be ext2
+    or ext3 and that XFS and ReiserFS will not work.  upserver and
+    upclient are now provided.  Provide some information about why
+    kaserver is not provided.  (Closes: #249315)
 
  --