Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!uunet!gatech!rpi!batcomputer!cornell!cs.cornell.edu!cchase From: cchase@cs.cornell.edu (Craig Chase) Subject: Re: Help: 386bsd NFS Filename Truncation Message-ID: <1992Sep8.171415.19489@cs.cornell.edu> Sender: news@cs.cornell.edu (USENET news user) Nntp-Posting-Host: bullwinkle.cs.cornell.edu Organization: Electrical Engineering, Cornell University, Ithaca NY References: <92252.103621AI4CPHYW@MIAMIU.BITNET> Date: Tue, 8 Sep 1992 17:14:15 GMT Lines: 29 In article <92252.103621AI4CPHYW@MIAMIU.BITNET>, <AI4CPHYW@MIAMIU.BITNET> writes: |> [..] After some thought I realized |> that I could do an NFS mount of another Unix machine (an Intergraph |> CAD server running Clix, I-graph's flavor of Unix) and use that disk |> space to hold the source distribution. |> [...] |> I found differences. First, the ownership was different (the files on |> the local disk were owned by root and the copies were owned by 32767 |> (not a problem for chown, but still :) Second, and more important, |> the long filenames were truncated. First: The uid 32767 is *nobody* in NFS land. When you NFS mount something without the -root option (in /etc/exports on the server machine), root on the client machine is translated into nobody on the server machine. This is for security (i.e. it's supposed to work that way). Solution: chown, and consider changing /etc/expors on the Clix machine. Second: SYSV (pre release 4) only allowed 14 (or there abouts) characters in the filenames. Since you're writing the files onto a SYSV variant of unix, all filenames are truncated to this length. Solution: don't use SYSV :-) Craig -- ------------------------------------------------------------------------ | Craig Chase | This space for rent | | cchase@ee.cornell.edu | 555-8968 | ------------------------------------------------------------------------