From owner-freebsd-questions@FreeBSD.ORG Sat Nov 24 20:32:23 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 15FFB3EB for ; Sat, 24 Nov 2012 20:32:23 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) by mx1.freebsd.org (Postfix) with ESMTP id C5A238FC13 for ; Sat, 24 Nov 2012 20:32:22 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.5/8.14.5) with ESMTP id qAOKWAhu003031 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Sat, 24 Nov 2012 14:32:10 -0600 (CST) (envelope-from tundra@tundraware.com) Message-ID: <50B12EC7.6060705@tundraware.com> Date: Sat, 24 Nov 2012 14:32:07 -0600 From: Tim Daneliuk User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2 MIME-Version: 1.0 To: FreeBSD Mailing List Subject: I Guess I Don't Understand NFS As Well As I Thought Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (ozzie.tundraware.com [192.168.0.1]); Sat, 24 Nov 2012 14:32:10 -0600 (CST) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: qAOKWAhu003031 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2012 20:32:23 -0000 Can someone kindly explain what is going on here: Machine A: FreeBSD - was running 8, just upgraded to 9.1-PRE (I don't recall seeing the behavior described below in V8, but then, I don't think I ever tried it). Machine B: Linux Mint Desktop - Machine A acts as an NFS server for Machine B. - Machine A exports a particular directory like this: /usr/foo -maproot=myid -network ... - /usr/foo/bar is owned by root on Machine A and has files therein owned as root:root with permissions of 600. - If I access /usr/foo/bar/file1 from Machine B, I cannot read it but - and this is the part I don't get - I CAN *rename* it. What's going on? Since /foo/bar/ is owned by root and everything in it is 600 root:root, I would not expect a remote access to allow things like renaming. Clearly I am missing something here, but I don't get it. -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/