[iPAQ] 'Stale NFS handles' with chrooted, NFS-mounted Intimate

I'm trying to set up an environment where I can actually compile some
stuff for Familiar. Since I have no big luck with the skiffcluster,
since cross-compiling looks a real big task and since the 128MB of my CF
looked a little bit small for compiling Python ;-), I had the idea to
set up an Intimate system on a NFS-mounted partition on my workstation.

I was lazy, so I didn't bother setting up a really dual-boot environment
for this NFS solution. Instead, I'm booting Familiar, and then chrooting
into the NFS mount. Setting up Intimate on the NFS partition worked like
a charm (just untar base.tar.gz). Most things seem to work as expected
on any Debian system--even the network setup is working fine, so I can
just go ahead and "apt-get upgrade" my chrooted Intimate.

But, when I "apt-get source" some stuff, I'm constantly running into
problems with stale NFS file handle: Even dpkg-source fails, appearently
when trying to apply the diff to the source tree.

Is somebody else experiencing the same (I haven't found any references
to stale NFS handle in the list archives) ? Am I the only one who had
this obvious idea ? ;-) Any clue how this could be resolved ???

If this NFS setup would work reliable, it could be a very low-profile
way to setup developement environments for nearly anyone.

Thanks in advance,

    Gregor
Received on Tue May 07 22:09:22 2002