David Woodhouse:
>
> smurf@noris.de said:
> > NB: It'd be nice if knfsd would be a drop-in replacement for unfsd
> > (meaning that I wouldn't have to change all the clients), but that's
> > not likely to happen in the 2.2 timeframe. :-(
>
> Why do you need to change the clients? I needed to restart them - the NFS
> filehandles were different with knfsd - but nothing else needed to change.
>
knfsd will not let me access mounted subvolumes.
Suppose that you have a server which has disks mounted on /archive,
/archive/.2, and /archive/.3 and so on. Mounting /archive will let the
client access /archive/.2 when the server uses the unfs daemon, but with
knfsd I _must_ mount /archive/.2 separately, on every client.
Since the client configuration cannot be changed (and IMHO it's not the
clients' business how the server has its disks laid out in the first
place), I'm stuck with unfsd until somebody does something about this.
Allegedly, it's not just a "change a few lines of code here" job. :-/
-- Matthias Urlichs | noris network GmbH | smurf@noris.de | ICQ: 20193661- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/