Hello,
I'm trying to build openafs 1.4.0 or 1.4.2 on my machine (x86) running
opensuse 10.2 (kernel 2.6.18.2-34-default).
I get the following error:
/home/cerminar/io/installazione/openafs-1.4.0/src/afs/LINUX/osi_machdep.h:55:2:
error: #error Not sure what to do about rlim (should be in
* Gianluca Cerminara [2006-12-27 16:20:49 +0100]:
Hello,
I'm trying to build openafs 1.4.0 or 1.4.2 on my machine (x86) running
opensuse 10.2 (kernel 2.6.18.2-34-default).
I get the following error:
/home/cerminar/io/installazione/openafs-1.4.0/src/afs/LINUX/osi_machdep.h:55:2:
On Dec 25, 2006, at 6:49 PM, Derrick J Brashear wrote:
On Mon, 25 Dec 2006, Adam Megacz wrote:
Marcus Watts [EMAIL PROTECTED] writes:
#1 - what is the process to get a real linux filesystem type
number
assigned?
Ask the Linux Standards Committee.
(No such entity)
Actually I
Steve Simmons wrote:
*chuckle* So as a reducto ad absurdum argument, I can assume this
means there are no actual linux filesystem type numbers because it's
impossible to get agreement. As Descarte didn't say, I think not.
/*chuckle
Since it clearly is possible and there's a minor shitload
Folks,
I recently upgraded my OpenAFS systems from the 1.4.1 release to
the 1.4.2 release using the image provided at www.openafs.org. I
have since had problems with afsd on the machine that also acts as my
server. When attempting to start afsd, I get the following crash
report. My
I just got it to build by changing the configure for the command for the
libafs build to use /usr/src/linux instead of /usr/src/linux-obj for the
--with-linux-kernel-headers value. But the spec file that I'm using at
the moment is very messy. I also removed the kernel-syms dependency and
Adam Megacz [EMAIL PROTECTED] writes:
Are you referring to this?
http://www.pdc.kth.se/kth-krb/
The code in lib/kafs/afssys.c appears to catch the SIGSYS signal while
doing some scary syscall()-guessing.
This is the closest thing to an answer so far. But that's a pretty
huge amount of
Sergio Gelato [EMAIL PROTECTED] writes:
OpenAFS 1.4.2, on the other hand, ought to work (it did for me in a
recent upgrade to Debian etch, which also has a 2.6.18 kernel).
Do you get the same error with 1.4.2? (The message you showed us says
1.4.0.)
Yes, 1.4.2 will build with 2.6.18 and
