From: Alejandro Colomar <alx.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org,
"G. Branden Robinson" <g.branden.robinson@gmail.com>
Subject: Re: Issue in man page boot.7
Date: Sun, 22 Jan 2023 22:22:02 +0100 [thread overview]
Message-ID: <623dc3a0-e6d1-e8cf-9e69-06721c4fcbcd@gmail.com> (raw)
In-Reply-To: <20230122193132.GA29262@Debian-50-lenny-64-minimal>
[-- Attachment #1.1: Type: text/plain, Size: 962 bytes --]
Hi Helge,
On 1/22/23 20:31, Helge Kreutzmann wrote:
> Without further ado, the following was found:
>
> Issue 1: runlevel 2 → run-level 2
> Issue 2: sendmail → B<sendmail>(8)
>
> "To define the starting or stopping order within the same run-level, the name"
> "of a link contains an B<order-number>. Also, for clarity, the name of a"
> "link usually ends with the name of the service to which it refers. For"
> "example, the link I</etc/rc2.d/S80sendmail> starts the sendmail service on"
> "runlevel 2. This happens after I</etc/rc2.d/S12syslog> is run but before I</"
> "etc/rc2.d/S90xfs> is run."
I believe the fix would be to use runlevel everywhere. run-level is not correct
under any point of view, if I'm correct. It should be runlevel for a new term
formed specifically for programming purposes, or run level for normal English.
Branden, can you confirm?
Cheers,
Alex
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-22 21:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 19:31 Issue in man page boot.7 Helge Kreutzmann
2023-01-22 21:22 ` Alejandro Colomar [this message]
2023-01-23 6:54 ` G. Branden Robinson
2023-01-23 17:47 ` Helge Kreutzmann
2023-01-23 19:11 ` G. Branden Robinson
-- strict thread matches above, loose matches on Subject: below --
2023-03-11 17:13 Helge Kreutzmann
2023-03-11 23:41 ` Alejandro Colomar
2023-03-11 17:13 Helge Kreutzmann
2023-03-11 23:31 ` Alejandro Colomar
2023-03-12 5:31 ` Helge Kreutzmann
2023-06-17 11:11 ` Helge Kreutzmann
2023-06-18 20:05 ` Oskari Pirhonen
2023-07-08 15:42 ` Alejandro Colomar
2023-01-22 19:31 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=623dc3a0-e6d1-e8cf-9e69-06721c4fcbcd@gmail.com \
--to=alx.manpages@gmail.com \
--cc=debian@helgefjell.de \
--cc=g.branden.robinson@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.