diff options
author | Alejandro Colomar <alx@kernel.org> | 2022-12-04 20:38:06 +0100 |
---|---|---|
committer | Alejandro Colomar <alx@kernel.org> | 2022-12-04 20:39:41 +0100 |
commit | b324e17d3208c940622ab192609b836928d5aa8d (patch) | |
tree | de6403ed6aaad3b403607aeb1624f2b193e50590 /man4 | |
parent | 0137c7f49c178c14c230a0b89e2979732a52e6df (diff) |
Many pages: wfix
Refer consistently to software versions. In most cases, it is done as
<software> <version>. In the case of Linux and glibc, use the project
name, instead of other terms such as 'kernel' or 'library'.
I found the uses of inconsistent language with the following:
$ find man* -type f \
| xargs grep -i '\(since\|before\|after\|until\|to\|from\|in\|between\|version\|with\) \(kernel\|version\|2\.\|3\.\|4\.\|5\.\)' \
| sort
However, I might have missed some cases. Anyway, 99% consistency is
pretty good consistency. We'll fix the remaining cases as we see them.
Signed-off-by: Alejandro Colomar <alx@kernel.org>
Diffstat (limited to 'man4')
-rw-r--r-- | man4/cciss.4 | 2 | ||||
-rw-r--r-- | man4/console_codes.4 | 4 | ||||
-rw-r--r-- | man4/lirc.4 | 4 | ||||
-rw-r--r-- | man4/random.4 | 4 | ||||
-rw-r--r-- | man4/sk98lin.4 | 2 | ||||
-rw-r--r-- | man4/st.4 | 28 | ||||
-rw-r--r-- | man4/vcs.4 | 2 | ||||
-rw-r--r-- | man4/wavelan.4 | 2 |
8 files changed, 24 insertions, 24 deletions
diff --git a/man4/cciss.4 b/man4/cciss.4 index cfc57efc0..a0ee99c1a 100644 --- a/man4/cciss.4 +++ b/man4/cciss.4 @@ -15,7 +15,7 @@ modprobe cciss [ cciss_allow_hpsa=1 ] .SH DESCRIPTION .\" commit 253d2464df446456c0bba5ed4137a7be0b278aa8 .BR Note : -This obsolete driver was removed from the kernel in version 4.14, +This obsolete driver was removed in Linux 4.14, as it is superseded by the .BR hpsa (4) driver in newer kernels. diff --git a/man4/console_codes.4 b/man4/console_codes.4 index 72e978757..880df050b 100644 --- a/man4/console_codes.4 +++ b/man4/console_codes.4 @@ -774,10 +774,10 @@ scripts which exercise other features. ESC 8 (DECRC) is not able to restore the character set changed with ESC %. .SH BUGS -In 2.0.23, CSI is broken, and NUL is not ignored inside +In Linux 2.0.23, CSI is broken, and NUL is not ignored inside escape sequences. .PP -Some older kernel versions (after 2.0) interpret 8-bit control +Some older kernel versions (after Linux 2.0) interpret 8-bit control sequences. These "C1 controls" use codes between 128 and 159 to replace ESC [, ESC ] and similar two-byte control sequence initiators. diff --git a/man4/lirc.4 b/man4/lirc.4 index 30797a679..68f665fc7 100644 --- a/man4/lirc.4 +++ b/man4/lirc.4 @@ -369,7 +369,7 @@ The driver supports setting the receive carrier frequency using .BR LIRC_SET_REC_CARRIER . Any .B lirc -device since the drivers were merged in kernel release 2.6.36 +device since the drivers were merged in Linux 2.6.36 must have .B LIRC_CAN_SET_REC_CARRIER_RANGE set if @@ -410,7 +410,7 @@ or .SH BUGS Using these devices requires the kernel source header file .IR lirc.h . -This file is not available before kernel release 4.6. +This file is not available before Linux 4.6. Users of older kernels could use the file bundled in .UR http://www.lirc.org .UE . diff --git a/man4/random.4 b/man4/random.4 index 12c859248..38396b667 100644 --- a/man4/random.4 +++ b/man4/random.4 @@ -118,7 +118,7 @@ from .I /dev/random will return at most 512 bytes .\" SEC_XFER_SIZE in drivers/char/random.c -(340 bytes on Linux kernels before version 2.6.12). +(340 bytes before Linux 2.6.12). .PP Writing to \fI/dev/random\fP or \fI/dev/urandom\fP will update the entropy pool with the data written, but this will not result in a @@ -218,7 +218,7 @@ returns the size of the entropy pool in bits (see below). .SS /proc interfaces The files in the directory .I /proc/sys/kernel/random -(present since 2.3.16) provide additional information about the +(present since Linux 2.3.16) provide additional information about the .I /dev/random device: .TP diff --git a/man4/sk98lin.4 b/man4/sk98lin.4 index 6801b9ea1..481ff6956 100644 --- a/man4/sk98lin.4 +++ b/man4/sk98lin.4 @@ -44,7 +44,7 @@ sk98lin \- Marvell/SysKonnect Gigabit Ethernet driver v6.21 .ad l .hy 0 .BR Note : -This obsolete driver was removed from the kernel in version 2.6.26. +This obsolete driver was removed in Linux 2.6.26. .PP .B sk98lin is the Gigabit Ethernet driver for @@ -77,7 +77,7 @@ There is no corresponding block device. .PP The driver uses an internal buffer that has to be large enough to hold at least one tape block. -In kernels before 2.1.121, the buffer is +Before Linux 2.1.121, the buffer is allocated as one contiguous block. This limits the block size to the largest contiguous block of memory the kernel allocator can provide. @@ -96,7 +96,7 @@ In addition to this, the driver tries to allocate a larger temporary buffer at run time if necessary. However, run-time allocation of large contiguous blocks of memory may fail and it is advisable not to rely -too much on dynamic buffer allocation with kernels older than 2.1.121 +too much on dynamic buffer allocation before Linux 2.1.121 (this applies also to demand-loading the driver with kerneld or kmod). .PP The driver does not specifically support any tape drive brand or @@ -149,7 +149,7 @@ Device is usually created as a hard or soft link to the default tape device on the system. .PP -Starting from kernel 2.6.2, the driver exports in the sysfs directory +Starting from Linux 2.6.2, the driver exports in the sysfs directory .I /sys/class/scsi_tape the attached devices and some parameters assigned to the devices. .SS Data transfer @@ -177,13 +177,13 @@ byte count, an error is returned. In fixed-block mode the read byte counts can be arbitrary if buffering is enabled, or a multiple of the tape block size if buffering is disabled. -Kernels before 2.1.121 allow writes with +Before Linux 2.1.121 allow writes with arbitrary byte count if buffering is enabled. In all other cases -(kernel before 2.1.121 with buffering disabled or newer kernel) the +(before Linux 2.1.121 with buffering disabled or newer kernel) the write byte count must be a multiple of the tape block size. .PP -In the 2.6 kernel, the driver tries to use direct transfers between the user +In Linux 2.6, the driver tries to use direct transfers between the user buffer and the device. If this is not possible, the driver's internal buffer is used. @@ -271,7 +271,7 @@ Go to the end of the recorded media (for appending files). .TP .B MTERASE Erase tape. -With 2.6 kernel, short erase (mark tape empty) is performed if the +With Linux 2.6, short erase (mark tape empty) is performed if the argument is zero. Otherwise, long erase (erase all) is done. .TP @@ -319,7 +319,7 @@ is positive, it gives the size of partition 1 and partition If .I mt_count is zero, the tape is formatted into one partition. -From kernel version 4.6, +From Linux 4.6, .\" commit 8038e6456a3e6f5c4759e0d73c4f9165b90c93e7 a negative .I mt_count @@ -403,7 +403,7 @@ Set various drive and driver options according to bits encoded in .IR mt_count . These consist of the drive's buffering mode, a set of Boolean driver options, the buffer write threshold, defaults for the block size and -density, and timeouts (only in kernels 2.1 and later). +density, and timeouts (only since Linux 2.1). A single operation can affect only one item in the list below (the Booleans counted as one item.) .IP @@ -563,7 +563,7 @@ to instruct the driver not to use the command. The end result is that, with read-ahead and fixed-block mode, the tape may not be correctly positioned within a file when the device is closed. -With 2.6 kernel, the +With Linux 2.6, the default is true for drives supporting SCSI-3. .TP .BR MT_ST_NO_BLKLIMS " (Default: false)" @@ -629,7 +629,7 @@ and the default density code can be set with The values for the parameters are or'ed with the operation code. .PP -With kernels 2.1.x and later, the timeout values can be set with the +With Linux 2.1.x and later, the timeout values can be set with the subcommand .B MT_ST_SET_TIMEOUT ORed with the timeout in seconds. @@ -646,7 +646,7 @@ practical values for a specific drive. The timeouts set for one device apply for all devices linked to the same drive. .PP -Starting from kernels 2.4.19 and 2.5.43, the driver supports a status +Starting from Linux 2.4.19 and Linux 2.5.43, the driver supports a status bit which indicates whether the drive requests cleaning. The method used by the drive to return cleaning information is set using the @@ -771,7 +771,7 @@ the drive is set not to buffer data. .TP \fBGMT_CLN\fP(\fIx\fP) The drive has requested cleaning. -Implemented in kernels since 2.4.19 and 2.5.43. +Implemented since Linux 2.4.19 and Linux 2.5.43. .RE .TP \fImt_erreg\fP @@ -848,7 +848,7 @@ The requested operation could not be completed. The byte count in .BR read (2) is smaller than the next physical block on the tape. -(Before 2.2.18 and 2.4.0 the extra bytes have been +(Before Linux 2.2.18 and Linux 2.4.0 the extra bytes have been .\" Precisely: Linux 2.6.0-test6 silently ignored.) .TP diff --git a/man4/vcs.4 b/man4/vcs.4 index 9bda05d74..12ad4b500 100644 --- a/man4/vcs.4 +++ b/man4/vcs.4 @@ -80,7 +80,7 @@ requests are supported. .\" .SH AUTHOR .\" Andries Brouwer <aeb@cwi.nl> .SH VERSIONS -Introduced with version 1.1.92 of the Linux kernel. +Introduced with Linux 1.1.92. .SH EXAMPLES You may do a screendump on vt3 by switching to vt1 and typing .PP diff --git a/man4/wavelan.4 b/man4/wavelan.4 index 45ac95f46..e5c5c7d9c 100644 --- a/man4/wavelan.4 +++ b/man4/wavelan.4 @@ -17,7 +17,7 @@ wavelan \- AT&T GIS WaveLAN ISA device driver .fi .SH DESCRIPTION .I This driver is obsolete: -it was removed from the kernel in version 2.6.35. +it was removed in Linux 2.6.35. .PP .B wavelan is the low-level device driver for the NCR / AT&T / Lucent |