Linux-man Archive on lore.kernel.org
 help / color / Atom feed
From: Helge Kreutzmann <debian@helgefjell.de>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: Errors in man pages, here: rename(2): Content
Date: Sun, 26 Apr 2020 18:17:04 +0200
Message-ID: <20200426161704.GA23062@Debian-50-lenny-64-minimal> (raw)
In-Reply-To: <CAKgNAkiRBUkOgu47JqEML=hhV=Ra4zh9WRJjWxWVG+LHZGgC4A@mail.gmail.com>


[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]

Hello Michael,
On Sun, Apr 26, 2020 at 04:24:14PM +0200, Michael Kerrisk (man-pages) wrote:
> On Sun, 26 Apr 2020 at 13:12, Helge Kreutzmann <debian@helgefjell.de> wrote:
> > On Mon, Apr 20, 2020 at 11:40:26AM +0200, Michael Kerrisk (man-pages) wrote:
> > > On 4/19/20 8:48 AM, Helge Kreutzmann wrote:
> > > > **
> > > >
> > > > If newpath exists, this is already the reason for the failure?
> > > >
> > > > "If I<newpath> exists but the operation fails for some reason, B<rename>()  "
> > > > "guarantees to leave an instance of I<newpath> in place."
> > >
> > > I do not understand this report. Please elaborate.
> >
> > Trying to 2nd guess what the original translator, who unfortunately is
> > no longer active, might have thought:
> >
> > If you want to rename but the new path already exists, how can there
> > be other reasons for failure at all?
> 
> Because renaming onto an existing 'newpath' is permitted! Earlier, the
> man page says:
> 
>        If newpath already exists, it will be atomically replaced, so that
>        there is no point at which another process  attempting  to  access
>        newpath  will  find it missing.
> 
> I think the translator must not have understood this.
> 
> > If this still does not make sense, please close this report without
> > changes, of course.
> 
> Please close.

Thanks & Done

Greetings

           Helge
-- 
      Dr. Helge Kreutzmann                     debian@helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-19  6:48 Helge Kreutzmann
2020-04-20  9:40 ` Michael Kerrisk (man-pages)
2020-04-26 11:12   ` Helge Kreutzmann
2020-04-26 14:24     ` Michael Kerrisk (man-pages)
2020-04-26 16:17       ` Helge Kreutzmann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200426161704.GA23062@Debian-50-lenny-64-minimal \
    --to=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-man Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-man/0 linux-man/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-man linux-man/ https://lore.kernel.org/linux-man \
		linux-man@vger.kernel.org
	public-inbox-index linux-man

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-man


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git