(Illustration by Gaich Muramatsu)
On Wed, May 26, 2004 at 04:41:52AM +0100, Nuno Tavares wrote: > Problem #1: > # rpm -ivh RPMS/coda-client-6.0.5-1.i386.rpm > Preparing... ########################################### [100%] > 1:coda-client ########################################### [100%] > venus-setupCreating /usr/coda/spool, mode 755 /usr/sbin/venus-setup: line > 156: syntax error near unexpected token `else' /usr/sbin/venus-setup: line > 156: ` else' > > Solution: miswritten line 153 missed "; then" in the "if" statement Why did you build 6.0.5 when 6.0.6 that has this fixed was released a couple of weeks ago? Oh right, the package name is coda-debug-6.0.6-1.src.rpm, the -debug- part of the name simply indicates that we don't strip the binaries before packaging them up in the hope that the symbols will be useful when a client or server crashes for unknown reasons. > Problem 2: after venus-setup: > Date: Wed 05/26/2004 ... > 04:38:47 WorkerInit: Version Skew with kernel! Get a newer kernel! > 04:38:47 WorkerInit: Kernel version is 2 There are 2 solutions, - Either build a coda.o module for your 2.4 kernel from the linux-coda-6.0.0.tgz package (which Niraj mentioned) - OR, use a Linux-2.6.x kernel. Build instructions for 2.4 modules are in the README file in the linux-coda package, but here is a quick summary. make config This checks your kernel version and tries to figure out with what options your kernel was build, SMP/module versions/etc. We need to know these things otherwise the module will refuse to load (or worse crash the kernel). make coda.o If the configuration was successful, this should build a coda.o module in the linux-2.4 subdirectory. make install This _tries_ to copy the coda.o module to the right place in /lib/modules. Then you probably want to run 'depmod -a', which updates the module loader dependency files, and if you previously tried to run the Coda client it is quite likely that you need to remove the old kernel module with 'rmmod coda'. If after all this venus still doesn't run, try to load the module by hand, because that way we see any errors that might be preventing the new module. rmmod coda insmod [path to linux-coda-6.0.0]/linux-2.4/coda.o Ofcourse in some cases upgrading to a 2.6 kernel is easier, because the Coda 5.0->6.0 realms related changes are already merged. JanReceived on 2004-05-26 10:25:15