thanks Jeffrey,
I changed the afs.rc script to
KERNEL_VERSION=`uname -r | sed 's/smp//g'`
and it now tries to load the right module that was created
I'll move to 1.4.0-rc8 now. ;) Thanks for the clarification
Pucky
On 19-Oct-05, at 1:49 PM, Jeffrey Altman wrote:
OpenAFS currently uses the Linux numbering scheme in which odd minor
releases are unstable and even minor releases are stable. Therefore,
1.4.0 is the new stable branch and after 1.4.0 is announced a 1.5.0
unstable series will begin.
I can't answer your linux question but I can point out that 1.4.0-rc8
supercedes 1.3.87 by nine releases. You should be using 1.4.0-rc8
and
not 1.3.87 for any work you are currently doing.
Jeffrey Altman
Pucky Loucks wrote:
I'm having an issue with openafs-1.3.87. I've compiled it on the
following type of system:
$ Linux H2STBiznode02 2.4.21-32.0.1.ELsmp #1 SMP Thu Jun 30 10:52:34
CDT 2005 i686 i686 i386 GNU/Linux
when I try to start openafs (during a client install) I get the
following:
AFS module /usr/vice/etc/modload/libafs-2.4.21-32.0.1.ELsmp.mp.o does
not exist. Not starting AFS.
My question is... how do I tell ./configure to build me a smp version
of the openafs module? I've done this:
$ ./configure --enable-transarc-paths --enable-smp
but I'm not sure if that is anywhere close to being correct.
also when 1.40 is final and out will it be the current stable release
or will it be unstable release. the reason I ask is I'm going to be
going production with openafs in the next 3 weeks and I'm
wondering if
I should do openafs-1.2.13 or openafs-1.3.87 or openafs-1.4.
thanks,
Pucky
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel
