Differences between version 12 and predecessor to the previous major change of AFSNotes.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 12 | Last edited on Monday, September 1, 2003 11:28:24 pm | by AristotlePagaltzis | Revert |
| Older page: | version 7 | Last edited on Wednesday, June 18, 2003 11:58:35 pm | by NathanWard | Revert |
@@ -1,98 +1,89 @@
!!!Setting up an [AFS] server under Debian
-A lot of this will
translate to other distributions as well, however I cannot guarantee it will work as it reads
.
-
+A lot of this should
translate to other distributions as well, but [YMMV]
.
!! Before you start
This section is almost definately OS/Distro independant.
! [Kerberos]
-[AFS] needs
[Kerberos] installed
. See
[KerberosNotes] for notes this
.
+[AFS] depends on a working
[Kerberos] installation
. Refer to
[KerberosNotes].
! Filesystems and Partitions
-[AFS] seems to be
fairly filesystem independant, so you can basically use any filesystem you like on the server. It
really prefers having a seperate partition for your AFS cell, and some notes I've read hint at
it requiring
a different fsck for magical reasons, so its probably best to follow this. Put your first partition on /vicepa, and your second on /vicepb, and so on.
-<br><small>
You can also use the namei backend which is slow, but is FS/OS independant, provided you can do normal filesystem stuff - NathanWard</small>
-
+Though
[AFS] seems fairly filesystem independant, it
really prefers having a seperate partition for your AFS cell. Apparently
it requires
a different fsck(8)
for magical reasons too
, so its probably best to follow this. Put your first partition on __
/vicepa__
, and your second on __
/vicepb__
, and so on. You can also use the namei backend which is slow, but is FS/OS independant, provided you can do normal filesystem stuff.
! Hostname
-[AFS] requires that the hostname of your
server resolve via DNS correctly. Make sure this is the case before you get too far down the line
, or else you
'll hit
weird problems that occur
for no apparent reason.
-<br><small>I've never had this problem... I have used clients
and servers with no DNS server. Perhaps this is a
[Kerberos] issue? - NathanWard</small>
+Some people report
[AFS] required their
server's hostname to
resolve properly
via [
DNS]
, or they
'd get
weird problems for no apparent reason. This does not seem to be consistent
and might be
[Kerberos] issue.
! Kernel
-[AFS] seems to really dislike linux 2.4.20. I've not tried it on a more recent kernel (not even a pre21 kernel). It does seem to work ok with 2.4.18 however. Make sure you have a
kernel that works
before continuing, or else things will
fail for no good reason!
-<br><small>I'm running 2
.4.20 in production now. Works fine
. YMMV - NathanWard</small>
+Make sure
[AFS] likes your
kernel before continuing, or else things may
fail for no good reason. Some people report problems with [AFS] on kernel versions others have no trouble with, so check your own setup
.
!! Installing [AFS]
! Installing the packages:
-In debian, install the following:
openafs-dbserver openafs-krb5 openafs-client
-
-Your cellname should be your lower-case DNS name, eg element.tla
-Your DBServer for AFS should be the dns name of the machine you are installing on currently!
+The pertinent [Debian] packages are
+*
openafs-dbserver
+*
openafs-krb5
+*
openafs-client
+Your cellname should be your lower-case DNS name, eg __element.tla__. Your DBServer for [AFS] should be the [DNS] name of the machine you are installing on currently.
! Setting up Kerberos
-<verbatim>
-
+Run the following commands (but see below first)
:
+
kadmin.local -e des-cbc-crc:v4
addprinc -randkey afs
ktadd -k /tmp/afs.keytab afs
quit
kadmin.local
addprinc root
- (enter passowrds
)
+ (enter passwords
)
quit
asetkey add 3 /tmp/afs.keytab afs
-</verbatim>
-<small>I don't think adding
a princ for root is a good
idea. The "[Kerberos] Way" is to have user/instance. In my case
, nward
/admin, which in AFS is
known as nward
.admin - NathanWard</small>
+Adding
a __
princ__
for __
root__
is probaby
a bad
idea. The "[Kerberos] Way" is to have user/instance, eg __joeshmoe
/admin__
, known to [AFS]
as __joeshmoe
.admin__.
! Partitions
-Make sure you have a partition created and mounted at /vicepa. If you cant do this with a real partition, make a loopback one as follows:
+Make sure you have a partition created and mounted at __
/vicepa__
. If you cant do this with a real partition, make a loopback one as follows:
-<verbatim>
dd if=/dev/zero of=/var/lib/openafs/vicepa bs=1024k count=32
mke2fs /var/lib/openafs/vicepa
- mount -oloop /var/lib/openafs /vicepa
-<
/verbatim>
+ mkdir /vicepa &&
mount -oloop /var/lib/openafs/vicepa /vicepa
-<small>Never fear!
later on you can
add /vicepb, /vicepc and so on
.. - NathanWard</small>
+You can
later add __
/vicepb__
, __
/vicepc__ etc
.
! Set up the cell
-In
/etc/openafs, edit the following files and make sure they look
something like these
+Make sure __
/etc/openafs/!ThisCell__ looks
something like
-<verbatim>
-/etc/openafs/ThisCell
element.tla
-/etc/openafs/CellServDb
+
+and __
/etc/openafs/!
CellServDb__ resembles
+
>element.tla # cell
10.66.1.101 # afs.element.tla
-</verbatim>
-At this point, make sure you have compiled the openafs
modules for your kernel. If you build a new kernel at the same time, reboot now so you can get these modules installed properly.
+At this point, make sure you have compiled the OpenAFS
modules for your kernel. If you build a new kernel at the same time, reboot now so you can get these modules installed properly.
+
+You can do this under [Debian] with [make-kpkg(1)]:
-You can do this under [Debian] with [make-kpkg]:
-<verbatim>
-
-# cd /usr/src
-# tar xzf openafs.tar.gz
-# cd /path/to/kernel/source
-# make-kpkg modules_image
-# dpkg -i ../openafs-modules*deb
-</verbatim>
+
# apt-get source openafs-modules-source
+ # cd /usr/src
+ # tar xzf openafs.tar.gz
+ # cd /path/to/kernel/source
+ # make-kpkg modules_image
+ # dpkg -i ../openafs-modules*deb
-The DebianPackages
, at least, come with a script to do all this for you:
+The [Debian] [Packages|Package]
, at least, come with a script to do all this for you:
afs-newcell
! Set up the root volume:
There is also a script to to this:
afs-rootvol
