samba - Mar 2002 - look under ownership(maybe will help?)

ncpfs Quirks
PWF Linux uses a modified version of the Linux NCP file system (ncpfs) for
mounting home directories. This version of ncpfs is set up to provide something
closer to Unix file-system semantics than the standard one, but it still differs
in the following ways:

File Names 
File names are limited to 255 characters. File names are in ISO 8859-1. he
following characters are not usable in file names and will be converted to
"." (hex 2E) when an object is created:
Code (hex) Character (ISO 8859-1) Reason  
00 NUL  Unix name terminator  
2A *  Probably confuses ArcServe  
2F /  Unix directory separator  
3F ?  Confuses ArcServe  
5C \  Confuses ArcServe  
80--9F C1 controls No representation in server character set  
FF ? Confuses ArcServe  

All other characters should work correctly. 
Long file names 
File names longer than 127 characters cannot be created. System calls which
attempt to create them will return ENAMETOOLONG.
Hard Links 
Hard links are not supported. link(2) returns EPERM.
 
Ownership 

All objects appear to be owned by the logged-in user. chown(2) returns EPERM. 
Permissions 
Unix permissions set by chmod(2) appear correctly to stat(2), but only execute
permissions are honoured by the kernel. All other permission checking is handled
by NetWare. Files with none of the "write" bits set get flagged as
NetWare "read-only".
Unlinked files 
Once a file has been unlinked, read(2) and write(2) operations on it fail with
EPERM.
Device nodes 
While it's possible to create device nodes, they don't retain major and
minor number information, so they're of little use. Users can't create
them anyway.
mmap(2) 
The implementation of mmap() is incomplete. Attempting to use mmap() with
MAP_SHARED will return EINVAL.
Quotas 
Exceeding quota generates EIO rather than EDQUOT. There is no easy way to find
out a user's remaining quota.