--O3RTKUHj+75w1tg5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Nov 16, 2007 at 08:31:04PM -0500, Adam McDougall wrote:
> I am beginning to dabble with NFSv4 client functionality. I noticed
> idmapd is not built in -stable but it has been in -current since src/sbin=

/Makefile
> v. 1.163 (13 months ago). Should it be hooked up to the build? Thanks


At the time I was looking at it in -current, idmapd worked fine but the
client had serious issues (nothing on an NFSv4 mount could be executed,
for instance) which I couldn't track down, so I stopped working with it.

I think that hooking up idmapd could be a good thing to do in order to
expose those problems, but I'm concerned that it may give the impression
that our NFSv4 client is any use, which it appears not to be (at least
13 months ago; apologies if this is not longer the case).

Ceri
--=20
That must be wonderful! I don't understand it at all.
-- Moliere

--O3RTKUHj+75w1tg5
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)

iD8DBQFHP0SeocfcwTS3JF8RAsJpAKCN2ir3wqQt9J+d/T5NhpBFAo0gvwCgsApj
yojm36uGL8DfaCdpQ6zHUts=
=1+Z8
-----END PGP SIGNATURE-----

--O3RTKUHj+75w1tg5--