Re: Linux 2.6.11

From: Neil Brown
Date: Sun Mar 06 2005 - 01:05:32 EST


On Sunday March 6, trond.myklebust@xxxxxxxxxx wrote:
> su den 06.03.2005 Klokka 00:19 (+0000) skreiv J.A. Magallon:
>
> > static int __init init_nfsd(void)
> > {
> > ...
> > if (proc_mkdir("fs/nfs", NULL)) {
> > struct proc_dir_entry *entry;
> > entry = create_proc_entry("fs/nfs/exports", 0, NULL);
> > if (entry)
> > entry->proc_fops = &exports_operations;
> > }
> > ...
> >
> > But nfs-utils 1.0.7 say that you can mount nfsd at /proc/fs/nfsd.
> > What 'exports' would kernel use ? Just duplicate info or a bug ?
>
> Not sure why /proc/fs/nfs was originally chosen (perhaps Neil
> knows?),

No, before my time.
/proc/fs/nfs/exports has "always" been a file listing the kernels
current understanding of the exports table.
The same information is provided by the "/exports" file in the nfsd
filesystem which (obviously) can be mounted anywhere you like, but
nfs-utils will only work with it if it is mounted on /proc/fs/nfsd
(the preferred location) or /proc/fs/nfs (because for a little while
/proc/fs/nfsd didn't exist).

> but the above code has nothing to do with where you mount the "nfsd"
> filesystem. It is rather part of the legacy support for older versions
> of nfs-utils.
>
> We should aim to deprecate it at some point soon.

I would like to deprecate the nfssvc system call and /proc/fs/nfs, and
I was planning to do it when 2.7 came out .....
Maybe June 2005 would be a good time to mark it 'deprecated' and June
2006 would be a good time to remove it.

NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/