From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: master fails to build on FreeBSD when ACL support is on Date: Sun, 21 Jan 2018 22:42:36 -0800 Organization: UCLA Computer Science Department Message-ID: <4bdd53c4-5a79-e4e5-0a8d-d1d0d65aee25@cs.ucla.edu> References: <86o9lua0yx.fsf@phe.ftfl.ca> <834lnly8ht.fsf@gnu.org> <86vafy20sj.fsf@phe.ftfl.ca> <83o9lpuct5.fsf@gnu.org> <83lggtu1qn.fsf@gnu.org> <9dd64b10-78ce-c561-8c51-9e15b11e102c@cs.ucla.edu> <83bmhpt12i.fsf@gnu.org> <867escw93p.fsf@phe.ftfl.ca> <86vafwumqp.fsf@phe.ftfl.ca> <025ce2fd-a69a-12da-ce5b-c894d5636789@cs.ucla.edu> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1516603286 21387 195.159.176.226 (22 Jan 2018 06:41:26 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 22 Jan 2018 06:41:26 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 Cc: Joseph Mingrone , Eli Zaretskii , ashish@FreeBSD.org, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 22 07:41:21 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1edVnD-00055B-Af for ged-emacs-devel@m.gmane.org; Mon, 22 Jan 2018 07:41:19 +0100 Original-Received: from localhost ([::1]:50192 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1edVpD-00027K-JJ for ged-emacs-devel@m.gmane.org; Mon, 22 Jan 2018 01:43:23 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57932) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1edVoa-000277-Tl for emacs-devel@gnu.org; Mon, 22 Jan 2018 01:42:45 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1edVoa-0001kD-0d for emacs-devel@gnu.org; Mon, 22 Jan 2018 01:42:44 -0500 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:48110) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1edVoW-0001Zz-4G; Mon, 22 Jan 2018 01:42:40 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 9C26D160E52; Sun, 21 Jan 2018 22:42:37 -0800 (PST) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id S94Xoc86Lkeu; Sun, 21 Jan 2018 22:42:36 -0800 (PST) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id DF6CA160E97; Sun, 21 Jan 2018 22:42:36 -0800 (PST) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id c1AOhdWtkCCB; Sun, 21 Jan 2018 22:42:36 -0800 (PST) Original-Received: from [192.168.1.9] (unknown [47.154.30.119]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 9A633160E52; Sun, 21 Jan 2018 22:42:36 -0800 (PST) In-Reply-To: Content-Language: en-US X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 131.179.128.68 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:222131 Archived-At: Stefan Monnier wrote: > Talking about what happens when rename-file uses copy-file: shouldn't i= t > first copy-file to a temporary file near the destination and then > rename-file that temp file? Otherwise the destination will temporarily > be in a "partially written" state, which is usually not what > `rename-file` callers want, right? I suspect rename-file is trying to mimic 'mv' here. With GNU 'mv', the=20 destination can temporarily be in a partially-written state when file sys= tem=20 boundaries are being crossed. This behavior is allowed by POSIX. Although= the=20 behavior you describe does have advantages, it is not allowed by POSIX fo= r 'mv'=20 and it can exhaust the destination file system even when there's room for= the=20 final result.