Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
************************************************************************ * :title.CSD UN37900 for NFS on TCP/IP 1.2.1 "REFRESH" for OS/2 * :version.1.2.1 :date.93/04/16 :CSD. UN37900 :support. * :abs.Fixes for the NFS feature for TCP/IP 1.2.1 "REFRESH". ************************************************************************ ***** Apply to TCP/IP 1.2.1 only - do NOT apply to release 1.2.0 ****** ************************************************************************ NFSCSD PACKAGE contains fixes for OS/2 TCP/IP Version '1.2.1 REFRESH' Run the NFSCSD.CMD file to have the files replaced. You must varify that the files that are being replaced are not "LOCKED" by the operating system, locked files cannot be repaced while they are locked. The diskette inages are packed by PKZIP and are in SELF-EXTRACTING ZIP file format. To unpack the disk image enter: NFSCSD (path) Example enter "NFSCSD A:" To install the CSD form the unpacked diskette enter "INSTALL" APAR #s ------PN21834 cmd Files and directories --------------------\tcpip\syslevel.nfs Update Syslevel file for syslevel PN22239 newly \tcpip\bin\nfsctl.exe Msg SYS005 after display of created directory =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= +=+=+=+ ADD FOR UN32132 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= +=+=+=+ PN25664 \tcpip\bin\nfsctl.exe NFS MOUNT AIX to make a build NFS Stop:sys3175 PN26093 does \tcpip\bin\nfsctl.exe NFSCTL started with -c and/or -z option \tcpip\bin\nfsd.exe process case sensitivity properly. PN27557 \tcpip\bin\ln.exe directory Using LN to create a LINK caused a to be deleted on the mounted drive =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= +=+=+=+ ADD FOR UN37900 4/15/93 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= +=+=+=+ PN35354 drive \tcpip\bin\nfsctl.exe SYS3175 error on commands to a Mounted \tcpip\bin\nfsc.exe ---------------------------------------------------------------Notes on the OS/2 NFS client and case handling By default the OS/2 NFS client creates files and directories in all lowercase. You can use the -z flag when you need to create files or directories in uppercase or mixed case, but this allows applications to create uppercase or mixed case names as well. Many OS/2 applications and all DOS applications create names in uppercase. In OS/2, case is preserved when creating files and directories on HPFS drives, but it is not significant on lookup. Thus, you can create a file as foo, FOO or Foo and the case will be maintained when you display the directory. However, you can access the file by using the name foo, FOO, Foo, fOo, FoO... The NFS protocol, however, is case sensitive. The files foo, FOO and Foo are all distinct files and an NFS client needs to specify the correct case when sending requests to an NFS server. When the OS/2 NFS client sends a request to an OS/2 NFS server, everything works as expected. For example, if an OS/2 NFS server has the file FOO and an OS/2 NFS client sends the request to delete foo, the OS/2 NFS server deletes FOO as an OS/2 user would expect. This is because the OS/2 file system on the NFS server is case insensitive on lookup so foo matches FOO. The situation is different if the NFS server is case sensitive as are UNIX NFS servers. The same example would work as follows: a UNIX NFS server has the file FOO and an OS/2 NFS client sends the request to delete foo. The UNIX NFS server will not delete FOO since the UNIX file system is case sensitive on lookup; foo does not match FOO. A choice was made to have the OS/2 NFS client emulate OS/2's case insensitivity on lookup. Thus the OS/2 NFS client does the following when requesting a name lookup on an NFS server: first the OS/2 NFS client sends the name in the case as it received it. If the lookup fails the client uppercases the name and sends the request again. If this lookup fails the client lowercases the name and sends the request a final time. Because of this method, there should be no problems accessing files if the following restrictions are followed: 1. Do not use names which differ by case only. 2. Do not use mixed case names. The second restriction is needed because many programs which run on OS/2 indiscriminately uppercase file names. This is because they were written for FAT file systems which only allow uppercase names. If you use tools that maintain case, you should be able to use mixed case file names as long as you type the exact case. OS/2 commands for manipulating files maintain case. It is especially important to avoid mixed case and duplicate directory names e.g. \foodir \FOODIR. When OS/2 needs to expand a name into fully qualified path name, the result is an uppercased name. For example, ..\foo may become C:\FOODIR\FOO. This is no problem if the directory and file names are all lowercase or all uppercase since the OS/2 NFS client will try both versions. However, if the directory or file is mixed case the name will not be found; the OS/2 NFS client has no way to restore the original mixed case once it is lost. =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= +=+=+=+ NEW With UN50472 October 1993 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= +=+=+=+ PN27946 P P \tcpip\bin\nfsctl.exe \tcpip\bin\nfsbiod.exe \tcpip\bin\mount.exe Numerous performance enhancements PN23956 to run \tcpip\bin\nfsd.exe NFSD needed to be started twice PN35753 \tcpip\bin\nfsd.exe SETATTR function returns error 5 PN40445 \tcpip\bin\nfsd.exe Trap D when mounter from OEM UNIX PN45613 client \tcpip\bin\nfsd.exe Fix write to NFS server from AIX PN42780 \tcpip\bin\nfsd.exe read EOF Fix return of broken packet on