util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: mtk.manpages@gmail.com, Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: [PATCH 11/12] Manual pages: agetty.8: Minor formatting and wording fixes
Date: Fri, 24 Jul 2020 12:06:17 +0200	[thread overview]
Message-ID: <20200724100618.584918-11-mtk.manpages@gmail.com> (raw)
In-Reply-To: <20200724100618.584918-1-mtk.manpages@gmail.com>

Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
---
 term-utils/agetty.8 | 24 +++++++++++++++++-------
 1 file changed, 17 insertions(+), 7 deletions(-)

diff --git a/term-utils/agetty.8 b/term-utils/agetty.8
index 902914197..6c748a365 100644
--- a/term-utils/agetty.8
+++ b/term-utils/agetty.8
@@ -74,7 +74,9 @@ The default for \fBserial terminals\fP is keep the current baud rate
 .TP
 .I term
 The value to be used for the TERM environment variable.  This overrides
-whatever init(8) may have set, and is inherited by login and the shell.
+whatever
+.BR init (1)
+may have set, and is inherited by login and the shell.
 .sp
 The default is 'vt100', or 'linux' for Linux on a virtual terminal,
 or 'hurd' for GNU Hurd on a virtual terminal.
@@ -93,8 +95,12 @@ Using this option causes an \fB\-f \fIusername\fR option and argument to be
 added to the \fB/bin/login\fP command line.  See \fB\-\-login\-options\fR, which
 can be used to modify this option's behavior.
 
-Note that \fB\-\-autologin\fP may affect the way how agetty initializes the
-serial line, because on auto-login agetty does not read from the line and it
+Note that \fB\-\-autologin\fP may affect the way in which 
+.B getty
+initializes the
+serial line, because on auto-login
+.B agetty
+does not read from the line and it
 has no opportunity optimize the line setting.
 .TP
 \-c, \-\-noreset
@@ -353,16 +359,20 @@ not be interpreted as options.  Use this feature if available by passing "\-\-"
 before the username gets passed by \\u.
 
 .SH ISSUE FILES
-The default issue file is \fI/etc/issue\fP. If the file exists then agetty also
+The default issue file is \fI/etc/issue\fP. If the file exists, then
+.B agetty
+also
 checks for \fI/etc/issue.d\fP directory. The directory is optional extension to
 the default issue file and content of the directory is printed after
-\fI/etc/issue\fP content. If the \fI/etc/issue\fP does not exist than the
+\fI/etc/issue\fP content. If the \fI/etc/issue\fP does not exist, then the
 directory is ignored. All files \fBwith .issue extension\fP from the directory are
 printed in version-sort order. The directory can be used to maintain 3rd-party
 messages independently on the primary system \fI/etc/issue\fP file.
 
 Since version 2.35 additional locations for issue file and directory are
-supported. If the default \fI/etc/issue\fP does not exist than agetty checks
+supported. If the default \fI/etc/issue\fP does not exist, then
+.B agetty
+checks
 for \fI/run/issue\fP and \fI/run/issue.d\fP, thereafter for
 \fI/usr/lib/issue\fP and \fI/usr/lib/issue.d\fP.  The directory /etc is
 expected for host specific configuration, /run is expected for generated stuff
@@ -372,7 +382,7 @@ The default path maybe overridden by \fB\-\-issue\-file\fP option. In this case
 specified path has to be file or directory and all the default issue file and
 directory locations are ignored.
 
-The issue file feature is possible to completely disable by \fB\-\-noissue\fP option.
+The issue file feature can be completely disabled by \fB\-\-noissue\fP option.
 
 It is possible to review the current issue file by \fBagetty \-\-show\-issue\fP
 on the current terminal.
-- 
2.26.2


  parent reply	other threads:[~2020-07-24 10:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24 10:06 [PATCH 01/12] Manual pages: blockdev.8: Minor wording and formatting fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 02/12] Manual pages: fsck.cramfs.8: Wording fix Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 03/12] Manual pages: raw.8: Minor formatting and wording fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 04/12] Manual pages: sfdisk.8: Minor wording and formatting fixes Michael Kerrisk (man-pages)
2020-07-24 16:32   ` Nuno Silva
2020-08-27 15:16     ` Michael Kerrisk
2020-08-28 11:09       ` Nuno Silva
2020-07-24 10:06 ` [PATCH 05/12] Manual pages: sfdisk.8: Use less aggressive indenting Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 06/12] Manual pages: lslogins.1: Minor wording and formatting fixres Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 07/12] Manual pages: nologin.8: formatting fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 08/12] Manual pages: logger.1: minor formatting and typo fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 09/12] Manual pages: lsblk.8: Minor " Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 10/12] Manual pages: wdctl.8: typo fix Michael Kerrisk (man-pages)
2020-07-24 10:06 ` Michael Kerrisk (man-pages) [this message]
2020-07-24 10:06 ` [PATCH 12/12] Manual pages: wipefs.8: Formatting fixes Michael Kerrisk (man-pages)
2020-07-24 12:43 ` [PATCH 01/12] Manual pages: blockdev.8: Minor wording and formatting fixes Karel Zak
2020-07-24 16:07 ` Nuno Silva

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=20200724100618.584918-11-mtk.manpages@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).