Your message dated Fri, 26 Aug 2005 10:32:07 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#322638: fixed in openafs 1.4rc1-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 12 Aug 2005 01:00:55 +0000
>From [EMAIL PROTECTED] Thu Aug 11 18:00:55 2005
Return-path: <[EMAIL PROTECTED]>
Received: from eddings.acpub.duke.edu [152.3.233.76]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E3Nup-0006sh-00; Thu, 11 Aug 2005 18:00:55 -0700
Received: from riverside.dulci.biostat.duke.edu
(riverside.dulci.biostat.duke.edu [152.3.172.51])
by eddings.acpub.duke.edu (8.12.10/8.12.10/Duke-5.0.0) with ESMTP id
j7C10oeh015262;
Thu, 11 Aug 2005 21:00:50 -0400 (EDT)
Received: from faheem by riverside.dulci.biostat.duke.edu with local (Exim 4.50)
id 1E3Nul-0007uH-HQ
for [EMAIL PROTECTED]; Thu, 11 Aug 2005 21:00:51 -0400
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="ISO-8859-1"
From: Faheem Mitha <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: debugging openafs server config
X-Mailer: reportbug 3.8
Date: Thu, 11 Aug 2005 21:00:51 -0400
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: openafs
Severity: normal
Hi,
This reports follows the config session described in
/usr/share/doc/openafs-*/configuration-transcript.txt.gz
Comments will be enclosed by *'s.
General comment before starting: the /configuration-transcript.txt.gz is
good and all, but it would be even better to have a more manual approach,
and have people test the configuration as they go along. See, for example,
the Gentoo equivalent (http://www.gentoo.org/doc/en/openafs.xml), which is
rather manual, but has a ton of verification, which I think is good.
The log was made using screen, initializing with 'screen -L', and setting
debconf to readline mode. The screen logs have lots of ^M's at the end, and
produces other garbage, which I've mostly removed. If you can suggest better
ways of logging a terminal session, let me know.
I'll start off my with /etc/hosts file.
/etc/hosts begins*****************************************
127.0.0.1 localhost
152.3.172.51 riverside.dulci.biostat.duke.edu riverside
# The following lines are desirable for IPv6 capable hosts
# (added automatically by netbase upgrade)
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
/etc/hosts ends******************************************
Ok, now the configuration transcript.
comment ends**************************************************************
configuration transcript begins*******************************************
riverside:/home/faheem# apt-get -q install openafs-dbserver openafs-krb5
krb5-admin-server
Reading Package Lists...
Building Dependency Tree...
The following extra packages will be installed:
krb5-config krb5-kdc krb5-user openafs-client openafs-fileserver
The following NEW packages will be installed:
krb5-admin-server krb5-config krb5-kdc krb5-user openafs-client
openafs-dbserver openafs-fileserver openafs-krb5
0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded.
Need to get 3275kB of archives.
After unpacking 7786kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://ftp.us.debian.org sarge/main krb5-config 1.6 [10.2kB]
Get:2 http://ftp.us.debian.org sarge/main openafs-client 1.3.81-3sarge1 [1547kB]
Get:3 http://security.debian.org stable/updates/main krb5-user 1.3.6-2sarge2
[127kB]
Get:4 http://security.debian.org stable/updates/main krb5-kdc 1.3.6-2sarge2
[115kB]
Get:5 http://security.debian.org stable/updates/main krb5-admin-server
1.3.6-2sarge2 [94.8kB]
Get:6 http://ftp.us.debian.org sarge/main openafs-fileserver 1.3.81-3sarge1
[783kB]
Get:7 http://ftp.us.debian.org sarge/main openafs-dbserver 1.3.81-3sarge1
[467kB]
Get:8 http://ftp.us.debian.org sarge/main openafs-krb5 1.3-10.1 [129kB]
Fetched 3275kB in 5s (550kB/s)
[snip]
Configuring krb5-config
-----------------------
When users attempt to use Kerberos and specify a principal or user
name without specifying what administrative Kerberos realm that
principal belongs to, the system appends the default realm.
Normally default realm is the upper case version of the local DNS
domain.
What is the default Kerberos version 5 realm? DULCI.BIOSTAT.DUKE.EDU
Configuring krb5-kdc
--------------------
By default, Kerberos4 requests are allowed from principals that do not require
preauthentication. This allows Kerberos4 services
to exist while requiring most users to use Kerberos5 clients to get their
initial tickets. These tickets can then be converted to
Kerberos4 tickets. Alternatively, the mode can be set to full, allowing
Kerberos4 to get initial tickets even when
preauthentication would normally be required, or to disable, which will disable
all Kerberos4 support.
1. disable 2. full 3. nopreauth 4. none
Kerberos4 compatibility mode to use: 3
Configuring krb5-admin-server
-----------------------------
Setting up a Kerberos Realm
This package contains the administrative tools necessary to run on the Kerberos
master server. However, installing this package
does not automatically set up a Kerberos realm. Doing so requires entering
passwords and as such is not well-suited for package
installation. To create the realm, run the krb5_newrealm command. You may also
wish to read /usr/share/doc/krb5-kdc/README.KDC and the administration guide
found in the krb5-doc package.
Don't forget to set up DNS information so your clients can find your KDC and
admin servers. Doing so is documented in the
administration guide.
Configuring openafs-client
--------------------------
AFS filespace is organized into cells or administrative domains. Each
workstation belongs to one cell. Usually the cell is the DNS
domain name of the site.
[4m What AFS cell does this workstation belong to? dulci.biostat.duke.edu
AFS uses an area of the disk to cache remote files for faster access. This
cache will be mounted on /var/cache/openafs. It is
important that the cache not overfill the partition it is located on. Often,
people find it useful to dedicate a partition to
their AFS cache.
How large is your AFS cache (kB)? 50000
/afs generally contains an entry for each cell that a client can talk to.
Traditionally, these entries were generated by servers in
the client's home cell. However, OpenAFS clients can generate the contents of
/afs dynamically based on the contents of
/etc/openafs/CellServDB and DNS.
If you generate /afs dynamically, you may need to create /etc/openafs/CellAlias
to include aliases for common cells. DO NOT SELECT
THIS OPTION IF THIS MACHINE IS THE FIRST DATABASE SERVER IN A NEW CELL .
Dynamically generate the contents of /afs? no
Selecting previously deselected package krb5-config.
(Reading database ... 79883 files and directories currently installed.)
Unpacking krb5-config (from .../krb5-config_1.6_all.deb) ...
Selecting previously deselected package krb5-user.
Unpacking krb5-user (from .../krb5-user_1.3.6-2sarge2_i386.deb) ...
Selecting previously deselected package krb5-kdc.
Unpacking krb5-kdc (from .../krb5-kdc_1.3.6-2sarge2_i386.deb) ...
Selecting previously deselected package krb5-admin-server.
Unpacking krb5-admin-server (from .../krb5-admin-server_1.3.6-2sarge2_i386.deb)
...
Selecting previously deselected package openafs-client.
Unpacking openafs-client (from .../openafs-client_1.3.81-3sarge1_i386.deb) ...
Selecting previously deselected package openafs-fileserver.
Unpacking openafs-fileserver (from
.../openafs-fileserver_1.3.81-3sarge1_i386.deb) ...
Selecting previously deselected package openafs-dbserver.
Unpacking openafs-dbserver (from .../openafs-dbserver_1.3.81-3sarge1_i386.deb)
...
Selecting previously deselected package openafs-krb5.
Unpacking openafs-krb5 (from .../openafs-krb5_1.3-10.1_i386.deb) ...
Setting up krb5-config (1.6) ...
Configuring krb5-config
-----------------------
Enter the hostnames of Kerberos servers in the DULCI.BIOSTAT.DUKE.EDU Kerberos
realm separated by spaces.
What are the Kerberos servers for your realm?
[24mriverside.dulci.biostat.duke.edu
Enter the hostname of the administrative (password changing) server for the
DULCI.BIOSTAT.DUKE.EDU Kerberos realm.
What is the administrative server for your Kerberos realm?
[24mriverside.dulci.biostat.duke.edu
Setting up krb5-user (1.3.6-2sarge2) ...
Setting up krb5-kdc (1.3.6-2sarge2) ...
Setting up krb5-admin-server (1.3.6-2sarge2) ...
Starting Kerberos Administration Servers: kadmind: No such file or directory
while initializing, aborting
kadmind.
Setting up openafs-client (1.3.81-3sarge1) ...
Configuring openafs-client
--------------------------
AFS uses the file /etc/openafs/CellServDB to hold the list of servers that
should be contacted to find parts of a cell. The cell
you claim this workstation belongs to is not in that file. Enter the host
names of the database servers separated by spaces.
IMPORTANT: If you are creating a new cell and this machine is to be a database
server in that cell, only enter this machine's name;
add the other servers later after they are functioning. Also, do not enable the
AFS client to start at boot on this server until
the cell is configured. When you are ready you can edit
/etc/openafs/afs.conf.client to enable the client.
What hosts are DB servers for your home cell? riverside.dulci.biostat.duke.edu
Should the Openafs filesystem be started and mounted at boot? Normally, most
users who install the openafs-client package expect to
run it at boot. However, if you are planning on setting up a new cell or are
on a laptop, you may not want it started at boot
time. If you choose not to start AFS at boot , run /etc/init.d/openafs-client
force-start to start the client when you wish to run
it.
Run Openafs client now and at boot? no
Setting up openafs-fileserver (1.3.81-3sarge1) ...
Starting AFS Server: bosserver.
Setting up openafs-dbserver (1.3.81-3sarge1) ...
Setting up openafs-krb5 (1.3-10.1) ...
riverside:/home/faheem# krb5_newrealm
This script should be run on the master KDC/admin server to initialize
a Kerberos realm. It will ask you to type in a master key password.
This password will be used to generate a key that is stored in
/etc/krb5kdc/stash. You should try to remember this password, but it
is much more important that it be a strong password than that it be
remembered. However, if you lose the password and /etc/krb5kdc/stash,
you cannot decrypt your Kerberos database.
Loading random data
Initializing database '/var/lib/krb5kdc/principal' for realm
'DULCI.BIOSTAT.DUKE.EDU',
master key name 'K/[EMAIL PROTECTED]'
You will be prompted for the database Master Password.
It is important that you NOT FORGET this password.
Enter KDC database master key:
Re-enter KDC database master key to verify:
Starting Kerberos KDC: krb5kdc krb524d.
Starting Kerberos Administration Servers: kadmind.
Now that your realm is set up you may wish to create an administrative
principal using the addprinc subcommand of the kadmin.local program.
Then, this principal can be added to /etc/krb5kdc/kadm5.acl so that
you can use the kadmin program on other computers. Kerberos admin
principals usually belong to a single user and end in /admin. For
example, if jruser is a Kerberos administrator, then in addition to
the normal jruser principal, a jruser/admin principal should be
created.
Don't forget to set up DNS information so your clients can find your
KDC and admin servers. Doing so is documented in the administration
guide.
comment begins********************************************************
I've only the sketchiest idea what the purpose of these principals is. The
original transcript compounds confusion by using a preexisting account, eg.
"Re-enter KDC database master key to verify:foo
Authenticating as principal hartmans/[EMAIL PROTECTED] with password."
Do I need to create two principals, namely faheem and faheem/admin. If so,
what purposes do they serve?
Is there some way I can authenticate that I have set this up correctly?
comment ends***********************************************************
riverside:/home/faheem# kadmin.local -e des-cbc-crc:v4
Authenticating as principal faheem/[EMAIL PROTECTED] with password.
comment begins*********************************************************
When I did this before, I was getting root/[EMAIL PROTECTED]
As far as I know I cleared out all the configuration, so I am not sure what
has changed.
comment ends***********************************************************
kadmin.local: addprinc -randkey afs
WARNING: no policy specified for [EMAIL PROTECTED]; defaulting to no policy
Principal "[EMAIL PROTECTED]" created.
kadmin.local: ktadd -k /tmp/riverside.keytab afs
Entry for principal afs with kvno 3, encryption type DES cbc mode with CRC-32
added to keytab WRFILE:/tmp/riverside.keytab.
kadmin.local: quit
riverside:/home/faheem# kadmin.local
Authenticating as principal faheem/[EMAIL PROTECTED] with password.
kadmin.local: addprinc faheem
WARNING: no policy specified for [EMAIL PROTECTED]; defaulting to no policy
Enter password for principal "[EMAIL PROTECTED]":
Re-enter password for principal "[EMAIL PROTECTED]":
Principal "[EMAIL PROTECTED]" created.
kadmin.local: quit
riverside:/home/faheem# asetkey add 3 /tmp/riverside.keytab afs
riverside:/home/faheem# dd if=/dev/zero of=/var/lib/openafs/vicepa bs=1024k
count=32
32+0 records in
32+0 records out
33554432 bytes transferred in 0.090969 seconds (368855314 bytes/sec)
riverside:/home/faheem# mke2fs -j /var/lib/openafs/vicepa
comment begins***********************************************************
I see no reason not to use 'mke2fs -j' instead of 'mke2fs'.
comment ends ************************************************************
mke2fs 1.37 (21-Mar-2005)
/var/lib/openafs/vicepa is not a block special device.
Proceed anyway? (y,n) y
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
8192 inodes, 32768 blocks
1638 blocks (5.00%) reserved for the super user
First data block=1
4 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Superblock backups stored on blocks:
8193, 24577
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 22 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
riverside:/home/faheem# mount -oloop /var/lib/openafs/vicepa /vicepa
comment begins************************************************************
This seems a good time to stop and look at files that have been
created in /etc/openafs, since we'll soon run into trouble in that
context.
So, here is
*******/etc/openafs/ThisCell begins********
dulci.biostat.duke.edu
*******/etc/openafs/ThisCell endss*********
/etc/openafs/CellServDB begins***********************************
>dulci.biostat.duke.edu
152.3.172.51 # riverside.dulci.biostat.duke.edu
>grand.central.org #GCO Public CellServDB 27 Jan 2005
18.7.14.88 #grand-opening.mit.edu
128.2.191.224 #penn.central.org
130.237.48.87 #andrew.e.kth.se
[snip]
/etc/openafs/CellServDB ends**************************************
/etc/openafs/server/CellServDB begins******************************
>dulci.biostat.duke.edu
/etc/openafs/server/CellServDB ends******************************
Note /etc/openafs/ThisCell and /etc/openafs/server/ThisCell are the same.
/etc/openafs/server/CellServDB looks dodgy to me.
Ok, now we go with afs-newcell.
comment ends******************************************************************
riverside:/home/faheem# afs-newcell
Prerequisites
In order to set up a new AFS cell, you must meet the following:
1) You need a working Kerberos realm with Kerberos4 support. You
should install Heimdal with Kth-kerberos compatibility or MIT
Kerberos5.
2) You need to create the single-DES AFS key and load it into
/etc/openafs/server/KeyFile. If your cell's name is the same as
your Kerberos realm then create a principal called afs. Otherwise,
create a principal called afs/cellname in your realm. The cell
name should be all lower case, unlike Kerberos realms which are all
upper case. You can use asetkey from the openafs-krb5 package, or
if you used AFS3 salt to create the key, the bos addkey command.
3) This machine should have a filesystem mounted on /vicepa. If you
do not have a free partition, then create a large file by using dd
to extract bytes from /dev/zero. Create a filesystem on this file
and mount it using -oloop.
4) You will need an administrative principal created in a Kerberos
realm. This principal will be added to susers and
system:administrators and thus will be able to run administrative
commands. Generally the user is a root instance of some administravie
user. For example if jruser is an administrator then it would be
reasonable to create jruser/root and specify jruser/root as the user
to be added in this script.
5) The AFS client must not be running on this workstation. It will be
at the end of this script.
Do you meet these requirements? [y/n] y
If the fileserver is not running, this may hang for 30 seconds.
/etc/init.d/openafs-fileserver stop
Stopping AFS Server: bos: could not find entry (can't find cell '<default>' in
cell database)
bosserver.
What administrative principal should be used? faheem
comment begins************************************************************
Why isn't this faheem/admin? What is the difference?
comment ends**************************************************************
echo \>dulci.biostat.duke.edu >/etc/openafs/server/CellServDB
/etc/init.d/openafs-fileserver start
Starting AFS Server: bosserver.
bos addhost riverside riverside -localauth ||true
bos: could not find entry (can't find cell '<default>' in cell database)
bos adduser riverside faheem -localauth
bos: could not find entry (can't find cell '<default>' in cell database)
Failed: 256
bos: could not find entry (can't find cell '<default>' in cell database)
riverside:/home/faheem# exit
exit
configuration transcript ends*******************************************
comment begins************************************************************
The files in /etc/openafs are unchanged after this script runs.
The above error goes away, and the script seemingly gets a bit further
before exiting with another error, if /etc/openafs/server/CellServDB is
replaced by
>dulci.biostat.duke.edu
152.3.172.51 # riverside.dulci.biostat.duke.edu
Note that one also needs to comment out the following line in
/usr/sbin/afs-newcell
run( "echo \\>$cell >/etc/openafs/server/CellServDB");
otherwise the change gets overwritten when afs-newcell runs.
I can do this and report again if desired.
comment ends**************************************************************
Regards, Faheem.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
---------------------------------------
Received: (at 322638-close) by bugs.debian.org; 26 Aug 2005 17:39:54 +0000
>From [EMAIL PROTECTED] Fri Aug 26 10:39:54 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
id 1E8i3j-00060g-00; Fri, 26 Aug 2005 10:32:07 -0700
From: Russ Allbery <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#322638: fixed in openafs 1.4rc1-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 26 Aug 2005 10:32:07 -0700
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 2
Source: openafs
Source-Version: 1.4rc1-1
We believe that the bug you reported is fixed in the latest version of
openafs, which is due to be installed in the Debian FTP archive:
libopenafs-dev_1.4rc1-1_i386.deb
to pool/main/o/openafs/libopenafs-dev_1.4rc1-1_i386.deb
libpam-openafs-kaserver_1.4rc1-1_i386.deb
to pool/main/o/openafs/libpam-openafs-kaserver_1.4rc1-1_i386.deb
openafs-client_1.4rc1-1_i386.deb
to pool/main/o/openafs/openafs-client_1.4rc1-1_i386.deb
openafs-dbserver_1.4rc1-1_i386.deb
to pool/main/o/openafs/openafs-dbserver_1.4rc1-1_i386.deb
openafs-fileserver_1.4rc1-1_i386.deb
to pool/main/o/openafs/openafs-fileserver_1.4rc1-1_i386.deb
openafs-kpasswd_1.4rc1-1_i386.deb
to pool/main/o/openafs/openafs-kpasswd_1.4rc1-1_i386.deb
openafs-modules-source_1.4rc1-1_all.deb
to pool/main/o/openafs/openafs-modules-source_1.4rc1-1_all.deb
openafs_1.4rc1-1.diff.gz
to pool/main/o/openafs/openafs_1.4rc1-1.diff.gz
openafs_1.4rc1-1.dsc
to pool/main/o/openafs/openafs_1.4rc1-1.dsc
openafs_1.4rc1.orig.tar.gz
to pool/main/o/openafs/openafs_1.4rc1.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Russ Allbery <[EMAIL PROTECTED]> (supplier of updated openafs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Fri, 26 Aug 2005 01:30:21 -0700
Source: openafs
Binary: openafs-client libopenafs-dev openafs-dbserver openafs-modules-source
openafs-fileserver openafs-kpasswd libpam-openafs-kaserver
Architecture: source i386 all
Version: 1.4rc1-1
Distribution: unstable
Urgency: low
Maintainer: Sam Hartman <[EMAIL PROTECTED]>
Changed-By: Russ Allbery <[EMAIL PROTECTED]>
Description:
libopenafs-dev - The AFS distributed filesystem- development libraries
libpam-openafs-kaserver - The AFS distributed filesystem- kaserver PAM module
openafs-client - The AFS distributed filesystem- client support
openafs-dbserver - The AFS distributed filesystem- database server
openafs-fileserver - The AFS distributed filesystem- file server
openafs-kpasswd - The AFS distributed filesystem- old password changing
openafs-modules-source - The AFS distributed filesystem- Module Sources
Closes: 120097 249315 322638 323582 324694
Changes:
openafs (1.4rc1-1) unstable; urgency=low
.
* New upstream version.
* Install pam_afs.krb.so on hppa. I believe the new PAM module build
process fixes the issue that was being worked around before.
* Improve the documentation and scripts for setting up new servers or a
new cell. afs-rootvol can now be run from a client configured to use
dynroot. afs-newcell generates the server CellServDB directly to work
around oddities with bos addhost. There are many other, more minor
improvements as well. Thanks to Faheem Mitha and Sergio Gelato for
analysis and patches. (Closes: #322638)
* Update the configuration transcript to reflect the current packages,
messages, and instructions. Thanks, Faheem Mitha.
* Fill in the server CellServDB with information about the local cell,
if available in the client CellServDB, rather than always initializing
it to contain just the name of the cell.
* Detect AFS caches on non-ext2/ext3 file systems and abort AFS client
initialization. (Closes: #249315)
* Provide a way of setting sysname in afs.conf. (Closes: #324694)
* Don't create the unused /etc/openafs/AFSLog file. (Closes: #120097)
* Redo how library object files are found for the PAM module build to
avoid assuming C locale character set behavior. (Closes: #323582)
* Remove the openafs-client warning against dynroot for the first system
in a cell now that afs-rootvol can cope. Provide some basic
documentation of the CellAlias syntax in that message until we have a
real man page.
* Suggest openafs-doc.
* Update standards version to 3.6.2 for the kernel module packages (no
changes required).
* Translation updates.
- Czech, thanks Martin Sin.
- Vietnamese, thanks Clytie Siddall.
- French, thanks Christian Perrier.
Files:
6f73aebf36a64ab4cccf90267de52cf4 1108 net optional openafs_1.4rc1-1.dsc
8cac45d3fc3c0d63d68092fd9638ee69 4355767 net optional
openafs_1.4rc1.orig.tar.gz
1bc1c0820a608446f009053d5ac86189 115168 net optional openafs_1.4rc1-1.diff.gz
077ea2b10ad48b29261eeca1ce1ef45a 4469272 net extra
openafs-modules-source_1.4rc1-1_all.deb
948acee67bd91462ef4b2cbf13b06b08 1491022 net optional
openafs-client_1.4rc1-1_i386.deb
8eb36ac3b740ea0025369ec91eec6263 193674 net extra
openafs-kpasswd_1.4rc1-1_i386.deb
f3c14db41c5f0d81110fd4b9d29130ac 774976 net optional
openafs-fileserver_1.4rc1-1_i386.deb
4c457b6371e9813752f004bec3b01108 449610 net optional
openafs-dbserver_1.4rc1-1_i386.deb
d6a13c5639e29fc5e3fec8b9db3aa5bc 1128886 libdevel extra
libopenafs-dev_1.4rc1-1_i386.deb
d2488d4711afe347a71c13b666746901 396030 net extra
libpam-openafs-kaserver_1.4rc1-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iQEVAwUBQw9Qb7f2jhx5fmQdAQKBZQgAt1z5p6so2JuXwZnAwScUqnZXfvENSJB2
e8E4LTKAIUNOwlKiyaSLhQPR17jxBV6fvVBI0RZoQxe8R4OG1QoVNAJ6rLE9pWfD
LnA2fSSEFJNh4tea0444fLx7wG9Z0b37JawZp1FCZoy4llzbAJqfToHvwWHot/0c
DWlpGaww0NIJXuU0LgUP+BCBCyaAE7Zd7oJ0hb141xvwg/GCsMAOZHRo5rCRoKkL
OTdcw0EcG0Efe1z+IP9MgytWuGUyn6zDHhdkLSubp+MXp2oa2AsaJUFWIXhQRmXB
otnDFFWjgJ5IUI102ubWyuJWdDQTO7F4SeYyY4j8sKdPdjG1mqThrg==
=igG2
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
