[OpenAFS] openafs on alpha linux
Nathan Davis
davi0709@tc.umn.edu
Tue, 7 May 2002 21:40:10 -0500
This is a multi-part message in MIME format.
------=_NextPart_000_000F_01C1F60F.C35BCC00
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
I'm trying to setup afs on my alpha box running the stock Redhat 7.1 =
(kernel version 2.4.3-12). I got the latest source rpm, and did an rpm =
--rebuild on it.
1) src/config/Makefile.alpha_linux24.in is =
src/config/Makefile.alpha_linux_24.in instead. This causes the build to =
bail out. My first question, therefore, is if this is intentional. Is =
afs on alpha-linux not currently working, so the file is renamed so as =
to make sure you really want to do it? Or is this just something that =
was overlooked? Also, Makefile.alpha_linux_24.in only makes references =
to 2.2 kernels (although only in comments). It has nothing relating to =
2.4 kernels (either commented or uncommented). I suspect that is just =
because noone has bothered to change it yet.
2) Okay, so the quick fix in the short term was to hack the spec file so =
that the alpha Makefile.in would be accessed (in other words, change how =
the sysname variable was generated). This, of course, would cause =
builds to fail on other architectures where the Makefile.in file is =
"properly" named, but now the software builds on alpha-linux. A quick =
question here is whether this might cause different pre-processor =
variables/macros to be defined (thus causing code to be generated =
differently than it should).
3) I got the binary RPMs built, and started to install -- fundamentally =
following Quick Start Guide (specifically, the "Installing the First AFS =
Machine" chapter), but obviously making adaptions (mostly skipping =
parts) due to using RPM. Everything appears to go fine until I get to =
the section "Initializing Cell Security." The problem is, after =
creating "afs" in kas and executing the bos addkey commands, when I =
compare the checksum they are different. Any ideas as to what is wrong? =
I tried multiple times, even trying less than trivial passwords (to =
make sure there was no mistake in typing), and they were different every =
time.
4) Are there any "gotchas" when you want to start over? I.e., is there =
anything special you need to do (files that need to be deleted that =
aren't in /usr/afs or /usr/vice and aren't uninstalled automatically =
when the rpm is uninstalled, etc.)? Could it help the problem?
5) What (if any) tools are available for installing and/or =
administrating afs, beyond what is distributed with openafs? I just =
want to know, so I can write them if they aren't available ;-).
Thanks for bearing with me,
--Nathan G. Davis
------=_NextPart_000_000F_01C1F60F.C35BCC00
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>Hi,</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>I'm trying to setup afs on my alpha =
box running=20
the stock Redhat 7.1 (kernel version 2.4.3-12). I got the latest =
source=20
rpm, and did an rpm --rebuild on it.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>1) =
src/config/Makefile.alpha_linux24.in is=20
src/config/Makefile.alpha_linux_24.in instead. This causes the =
build to=20
bail out. My first question, therefore, is if this is =
intentional. =20
Is afs on alpha-linux not currently working, so the file is renamed so =
as to=20
make sure you really want to do it? Or is this just something that =
was=20
overlooked? Also, Makefile.alpha_linux_24.in only makes references =
to 2.2=20
kernels (although only in comments). It has nothing relating to =
2.4=20
kernels (either commented or uncommented). I suspect that is just =
because=20
noone has bothered to change it yet.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>2) Okay, so the quick fix in the =
short term was=20
to hack the spec file so that the alpha Makefile.in would be accessed =
(in other=20
words, change how the sysname variable was generated). This, of =
course,=20
would cause builds to fail on other architectures where the Makefile.in =
file is=20
"properly" named, but now the software builds on =
alpha-linux. A=20
quick question here is whether this might cause different pre-processor=20
variables/macros to be defined (thus causing code to be generated =
differently=20
than it should).</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>3) I got the binary RPMs built, and =
started to=20
install -- fundamentally following Quick Start Guide (specifically, the=20
"Installing the First AFS Machine" chapter), but obviously =
making=20
adaptions (mostly skipping parts) due to using RPM. Everything =
appears to=20
go fine until I get to the section "Initializing Cell =
Security." =20
The problem is, after creating "afs" in kas and executing the =
bos=20
addkey commands, when I compare the checksum they are different. =
Any ideas=20
as to what is wrong? I tried multiple times, even trying less than =
trivial=20
passwords (to make sure there was no mistake in typing), and they were =
different=20
every time.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>4) Are there any "gotchas" =
when you=20
want to start over? I.e., is there anything special you need to do =
(files=20
that need to be deleted that aren't in /usr/afs or /usr/vice and aren't=20
uninstalled automatically when the rpm is uninstalled, etc.)? =
Could it=20
help the problem?</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>5) What (if any) tools are available =
for=20
installing and/or administrating afs, beyond what is distributed with=20
openafs? I just want to know, so I can write them if they aren't =
available=20
;-).</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>Thanks for bearing with =
me,</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>--Nathan G. =
Davis</FONT></DIV></BODY></HTML>
------=_NextPart_000_000F_01C1F60F.C35BCC00--