home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!linac!att!ucbvax!WAIKATO.AC.NZ!SLANG
- From: SLANG@WAIKATO.AC.NZ (Steve Lang)
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Subject: RE: PC-NFS 4.0 and IBM TCP/IP 1.2.1 for OS/2 problems
- Message-ID: <9211081939.aa03753@louie.udel.edu>
- Date: 9 Nov 92 00:38:00 GMT
- Sender: daemon@ucbvax.BERKELEY.EDU
- Distribution: world
- Organization: The Internet
- Lines: 74
-
- >I am trying to access an OS/2 2.0 NFS server (IBM TCP/IP 1.2.1 for OS/2)
- >from a DOS 5.0 PC running Sun PC-NFS 4.0. I can mount drives from the
- >OS/2 server, but when I do a dir I get names that look like...
-
- > WINWO~7A <DIR> 04-14-92 9:06a
-
- >when they should look like...
-
- > WINWORD DSK <DIR> 04-14-92 2:06a
-
- >(notice the time stamp is wrong also)
-
- >In fact the only file or directory that has a extenstion is a WINA20.386
- >but even it is displayed as WINA2~HA.386.
-
- >You can cd to a directory if you know the name (not the dir displayed
- >mangled version).
-
- >You cannot execute .exe files but you can type autoexec.bat, for example.
- >You can copy files from DOS to NFS server, but you cannot copy from the
- >NFS server to DOS (says file not found).
-
- >Can anyone shed some light on this problem. When I called Sun, all I got
- >was a "we didn't test with that software" answer.
-
- What you are seeing is the PC-NFS name translation thingy. Most filenames on
- Unix/NFS servers are in lowercase. These translate o.k. to DOS. Not a problem
- here.
-
- Where you have a mixture of case or all uppercase, PC-NFS translates the
- filename. This is because on a Unix server the files 'Autoexec.bat' and
- 'autoexec.bat' are different, but on DOS they are the same. So, the PC-NFS
- client is preserving the fact that they are different files, by changing the
- filename of one.
-
- If a server has all of it's files in UPPERCASE, PC-NFS will quite happily
- translate all of the filenames to something pretty much unrecognisable. This is
- the case where you have a FAT partition under OS/2. All of the filenames are
- uppercase in FAT partitions. So, serving a FAT partition to a FAT client creates
- a problem!
-
- NB:: FAT filesystems are NOT case sensitive or case preserving.
- HPFS filesystems are NOT case sensitive, but ARE case preserving.
- Most Unix filesytems ARE case sensitive and case preserving.
- (Please, no flames.)
-
- Solutions:
-
- 1) Wait for a 'future' release of PC-NFS that will have an option to disable
- name translations on a mount by mount basis. (Don't ask me when.)
-
- 2) Change all of the filenames to lowercase. This is only valid if your OS/2
- disk is an HPFS disk.
-
- 3) Convince the OS/2 NFS server to convert FAT Filenames to lowercase.
-
-
- Number 2 will work now, number 3 may or may not be possible, number 1 will have
- to wait untill the code gets written, and that's up to SUN.
-
- Hope this helps -
-
- Drink is the curse Steve Lang
- of the working class man Systems Programmer Analyst
- Work is the curse of the University of Waikato
- Drinking class man Hamilton
- NEW ZEALAND
- <slang@waikato.ac.nz>
- Ph +64-7-856 2889 Ext 8341
- Fax +64-7-838 4066
-
- I am not responsible for my employers opinion (thank heavens,) and neither are
- they for mine.
-
-