public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: Rituparna ghosh <ghosh.rituparna@gmail.com>,
	linux-man@vger.kernel.org, shadow <~hallyn/shadow@lists.sr.ht>,
	Iker Pedrosa <ipedrosa@redhat.com>
Subject: Re: man7 - useradd query
Date: Tue, 17 Oct 2023 16:17:42 +0200	[thread overview]
Message-ID: <ZS6XjjJO59pVMU8_@debian> (raw)
In-Reply-To: <20231017134408.GA181875@mail.hallyn.com>

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

Hi Iker,

On Tue, Oct 17, 2023 at 08:44:08AM -0500, Serge E. Hallyn wrote:
[...]

> > > The useradd command here is showing an option   -F which is shown as
> > > invalid in RH 8.8 or RH 9.
> > > Is this correct?
> > 
> > From what I see in the source code of useradd.c in shadow, the feature
> > is compiled conditionally, #ifdef ENABLE_SUBIDS.  It may be that RHEL,
> > or your version, doesn't build with that option; I ignore it, I'm a
> > Debian user.
> 
> Yeah - but the manpage should likewise should not show the option if
> it is not compiled in, I guess.

This sounds reasonable.

>  At the moment it looks like we
> conditionally complie some manpages, like newuidmap.1, but I don't
> see any sections compiled out in the man/*.xml files.

You mean that currently it's either the entire page or nothing at all,
right?  I don't see anything that compiles part of a page either.

I imagine that you could do something like that by wrapping the
conditional part in something like <ifdef id="ENABLE_SUBIDS">...</ifdef>,
and write some script to handle it.

Cheers,
Alex

-- 
<https://www.alejandro-colomar.es/>

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

  reply	other threads:[~2023-10-17 14:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABP5-fx2YvLup4GFXicJapue=qpyZ61oHuRuBB82ne1Ka7uctw@mail.gmail.com>
2023-10-12 16:43 ` man7 - useradd query Alejandro Colomar
2023-10-17 13:44   ` Serge E. Hallyn
2023-10-17 14:17     ` Alejandro Colomar [this message]
2023-10-17 15:16       ` Serge E. Hallyn

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=ZS6XjjJO59pVMU8_@debian \
    --to=alx@kernel.org \
    --cc=ghosh.rituparna@gmail.com \
    --cc=ipedrosa@redhat.com \
    --cc=linux-man@vger.kernel.org \
    --cc=serge@hallyn.com \
    --cc=~hallyn/shadow@lists.sr.ht \
    /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