I was using the latest sarge nfs-kernel-server and was then forced to change kernels.
What do you mean, "forced"? Someone stood over you with a bat? :-)
Curious remark. Unfortunately, atmel drivers didn't respond to our SP907BB usb wlan adapter when compiled for a 2.4.x kernel (we used 2.4.27-k6-1). Fortunately, it did respond to the same cvs release when compiled for 2.6.8 kernel. Unfortunately, my boss REALLY wanted his winlaptop to do wireless directly with our linux server. Unfortunately, the server has no PCI slots left for a PCI card, fortunately, I managed to make the usb wlan thingy to do the trick, unfortunately, the nfs server stops serving after the upgrade if you start mozilla-firefox on a remote machine (the one that gets its /home from the server witch is the router).
Not that it matters.
I tried upgradeing nfs-common (nfs-common reported "mount version older than kernel" during bootup but no newer mount version is availible).
That message is unfortunate, but it is beyond my control, and means nothing important.
I'm not worried about the message, but about the nfs-kernel-server stoping responding to client requests after upgrade. :-/ I'll try woody when I get back.
If we suppose the kernel is OK, then the problem lies within nfs-kernel-server? Can you help there or at least establish that the nfs-kernel-server isn't the guilty party and send the report to kernel people?
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
