|
From: Szakacsits S. <sz...@si...> - 2003-04-23 12:09:40
|
On Tue, 22 Apr 2003, Anton Altaparmakov wrote:
> Nobody ever expressed interessed in it which is why noone ever bothered
> working on it... Now that someone is interested I will consider working
> on this in the near-ish future. But note that we may well only do it for
> 2.5.x kernels as 2.4.x kernels handle nfs completely differently (unless
I've looked 2.4.20 _quickly_ at that time. nfsd/export.c states
/* There are two requirements on a filesystem to be exportable.
* 1: We must be able to identify the filesystem from a number.
* either a device number (so FS_REQUIRES_DEV needed)
* or an FSID number (so NFSEXP_FSID needed).
* 2: We must be able to find an inode from a filehandle.
* either using fh_to_dentry (prefered)
* or using read_inode (the hack).
*/
The new ntfs driver satisfies both, still it's not exportable. However I
didn't look it further why.
> To implement properly pretty much impossible as there just isn't enough
You mean for a read-write ntfs driver? IMHO that's a bit far ... For the
read-only one it's much-much more simpler.
Szaka
|
