public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Kreutzmann <debian@helgefjell.de>
To: Alejandro Colomar <alx@kernel.org>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page mknod.2
Date: Thu, 25 Dec 2025 06:06:40 +0000	[thread overview]
Message-ID: <aUzUcM0dIDgNHx18@meinfjell.helgefjelltest.de> (raw)
In-Reply-To: <aUwHa051I7BDgWb4@devuan>

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

Hello Alex,
Am Wed, Dec 24, 2025 at 04:32:26PM +0100 schrieb Alejandro Colomar:
> Hi Helge,
> 
> On Wed, Dec 24, 2025 at 02:38:21PM +0000, Helge Kreutzmann wrote:
> > Without further ado, the following was found:
> > 
> > Issue:    This is the man page of B<mknod>, what is "like B<mknod>()" supposed to refer to? Itself?
> 
> The text is in the subsection mknodat(), so it says that mknodat() is
> like mknod().
> 
> 
> Cheers,
> Alex
> 
> > 
> > "If I<path> is relative and I<dirfd> is the special value B<AT_FDCWD>, then "
> > "I<path> is interpreted relative to the current working directory of the "
> > "calling process (like B<mknod>())."

Ok, I see, thanks!

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	other threads:[~2025-12-25  6:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-24 14:38 Issue in man page mknod.2 Helge Kreutzmann
2025-12-24 15:32 ` Alejandro Colomar
2025-12-25  6:06   ` Helge Kreutzmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-24 14:48 Helge Kreutzmann

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=aUzUcM0dIDgNHx18@meinfjell.helgefjelltest.de \
    --to=debian@helgefjell.de \
    --cc=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox