Russ Allbery wrote:
> "chas williams <- CONTRACTOR" <[EMAIL PROTECTED]>> writes:
>> In message <[EMAIL PROTECTED]>,FB writes:
>
>>> * OpenAFS 1.4.2rc2 (it's the latest debian package available)
>
>> while its the latest debian package, 1.4.2rc2 has several known bugs that
>> have been fixed in
Chaskiel M Grundman wrote:
--On Friday, March 24, 2006 15:02:10 +0100 Miroslav Ruda
<[EMAIL PROTECTED]> wrote:
Is it know problem on 2.6.16 kernel or should I suspect Xen patches?
It's a 2.6.16 problem. See if you can build your linux kernel with
CONFIG_DEBUG_RODATA off.
if
Hello,
I'm trying to use development Xen, which comes with 2.6.16-rc6 kernel and
openafs on amd64 machine. I can compile openafs-1.4.1-rc10 or 1.4.0 (with
patches mentioned in this list), but module loading fails:
libafs: no version for "struct_module" found: kernel tainted.
libafs: module l
Hello,
I have tried 1.3.78 on my Suse 9.2 x86_64, with default kernel 2.6.8-24.11.
Openafs compiles fine, with sysname amd64_linux26, and I'm able to start afsd.
However, my first ls on our cell (not /afs) gives oops of bash:
Pid: 5202, comm: bash Tainted: PF U (2.6.8-24.11-default
SL92_BRANCH
chas williams (contractor) wrote:
In message <[EMAIL PROTECTED]>,Miroslav Ruda writes:
checking if kernel uses MODVERSIONS... no
checking which kernel modules to build... MP SP
configure: WARNING: Cannot determine sys_call_table status. assuming it isn'
t exported
configure is makin
Matthew Miller wrote:
On Tue, Jun 08, 2004 at 03:40:02PM +0200, Horst Birthelmer wrote:
Actually the EXPORT_SYMBOL(sys_call_table) was right.
AFAIK every older kernel does this in ksyms.c. So try to place it there.
But my understanding is that you don't need to do this with the 2.6 code
anymore.
N
Horst Birthelmer wrote:
That's your problem!!
You have no exported sys_call_table. Just export it, recompile the
kernel and hopefully it works...
Could you suggest how to export sys_call_table? I have tried
EXPORT_SYMBOL(sys_call_table);
in arch/x86_64/kernel/syscall.c but nothing has changed.
T
Derrick J Brashear wrote:
> Why? Heimdal includes:
> -support for copying a real kaserver database to heimdal (use hprop and
> hpropd assuming you configure --enable-kaserver-db)
> -a krb5 aklog equivalent (afslog. actually it's not quite the same but
> it's close)
> -support for a kaserver for au
