From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
When mounting a NFS share from a tru64 Box (5.1) we get
different behaviour if we mount with the option noac or without.

Version-Release number of selected component (if applicable):
kernel-bigmem-2.4.18-27.7.x

How reproducible:
Always

Steps to Reproduce:
1. mount <IP>:/system /mnt
2. mount -onoac <IP>:/system /mnt1
3. stat /mnt/file /mnt1/file
    

Actual Results:  stat /mnt1/file /mnt/file
 File: "/mnt1/file"
 Size: 7760            Blocks: 16         IO Block: -4611697082263134208 Regular
File
Device: eh/14d  Inode: 1163557     Links: 1
Access: (0664/-rw-rw-r--)  Uid: (   -2/ UNKNOWN)   Gid: (   -2/ UNKNOWN)
Access: Mon Feb 17 21:45:12 2003
Modify: Wed Apr  2 21:38:21 2003
Change: Wed Apr  2 21:38:21 2003

 File: "/mnt/file"
 Size: 7760            Blocks: 16         IO Block: -4611697082263138304 Regular
File
Device: 16h/22d Inode: 1163557     Links: 1
Access: (0664/-rw-rw-r--)  Uid: (65534/nfsnobody)   Gid: (65534/nfsnobody)
Access: Mon Feb 17 21:45:12 2003
Modify: Wed Apr  2 21:38:21 2003
Change: Wed Apr  2 21:38:21 2003


Expected Results:  
See the differences in the UID: once: -2 and the other time 65534. /mnt is
normally mounted, /mnt1/ is mounted with noac.

By comparison this does not happen with UID 65533 or lower!