Re: [RFC] /proc/fs/nfsd/exports

Riley Williams (rhw@bigfoot.com)
Thu, 29 Oct 1998 21:56:54 +0000 (GMT)


Hi Allen.

> I am adding a proc file to kernel nfsd to display the exports and
> would like opions on what its output should look like.

> The basic layout is

> path client flags IPs

> This is simular to the /etc/exports file, with the addition of the
> IP numbers that client refers to.

> if myhost = 1.0.0.1 and 2.0.0.1 and if the etc/export file
> contained:

> /home myhost(async, ro, root_squash)
> /home 2.0.0.1(async, rw, no_root_quash)

> /proc/fs/nfsd/exports would have:

> /home myhost 15 01000001,-02000001
> /home 2.0.0.1 10 02000001

> or

> /home localhost(async,ro,root_squash) # 1.0.0.1,(2.0.0.1)
> /home 2.0.0.1(async) # 2.0.0.1

> The `myhost' export has its 2.0.0.1 IP _masked_ by the `2.0.0.1'
> export. This is what the `-' or `()'s are trying to signify.

> I prefer the first, as it is much easier to implement, and easier
> to parse, but the second one is easier to read and would be
> compatible with exports(5).

> Or there might be something better.

Personally, I'd go for the second - there's enough arguments already
about the existing /proc files that show IP addresses as numbers, and
whether they should be displayed in big-endian format (as your example
above does) or little-endian format (as /proc/net/route does).

Also, I seem to remember Linux stating that all things like that
should be displayed in the way one expects to see them in, such that
any question of endian-ness becomes irrelevant. Linus, am I right
here, or did I misunderstand you ???

Best wishes from Riley.

-
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/