.BR access ()
returns 0 for such files.
.\" This behavior appears to have been an implementation accident.
-Early 2.6 kernels (up to and including 2.6.3)
-also behaved in the same way as kernel 2.4.
+Early Linux 2.6 (up to and including Linux 2.6.3)
+also behaved in the same way as Linux 2.4.
.PP
Before Linux 2.6.20,
these calls ignored the effect of the
.I buf
does not point to writable memory.
.TP
-.BR EINVAL " (kernels before Linux 2.6.26)"
+.BR EINVAL " (before Linux 2.6.26)"
An attempt was made to set
.I buf.freq
to a value outside the range (\-33554432, +33554432).
.\" From a quick glance, it appears there was no clamping or range check
.\" for buf.freq before Linux 2.0
.TP
-.BR EINVAL " (kernels before Linux 2.6.26)"
+.BR EINVAL " (before Linux 2.6.26)"
An attempt was made to set
.I buf.offset
to a value outside the permitted range.
It occupies a space that was previously a zero-filled padding byte in the
.I linux_dirent
structure.
-Thus, on kernels up to and including 2.6.3,
+Thus, on kernels up to and including Linux 2.6.3,
attempting to access this field always provides the value 0
.RB ( DT_UNKNOWN ).
.PP
For each vt in use, the corresponding bit in the
.I v_state
member is set.
-(Kernels 1.0 through 1.1.92.)
+(Linux 1.0 through Linux 1.1.92.)
.TP
.B VT_RELDISP
Release a display.
.BR TIOCLINUX ", " subcode = 8
Dump screen width and height, cursor position, and all the
character-attribute pairs.
-(Kernels 1.1.67 through 1.1.91 only.
+(Linux 1.1.67 through Linux 1.1.91 only.
With Linux 1.1.92 or later, read from
.I /dev/vcsa*
instead.)
.BR TIOCLINUX ", " subcode = 9
Restore screen width and height, cursor position, and all the
character-attribute pairs.
-(Kernels 1.1.67 through 1.1.91 only.
+(Linux 1.1.67 through Linux 1.1.91 only.
With Linux 1.1.92 or later, write to
.I /dev/vcsa*
instead.)
.\" commit 0cf2f6f6dc605e587d2c1120f295934c77e810e8
in Linux 4.9.
.PP
-In the 2.4 series Linux kernels up to and including 2.4.17,
+In Linux 2.4 series of kernels up to and including Linux 2.4.17,
a bug caused the
.BR mlockall ()
.B MCL_FUTURE
capability and a kernel configured with the
.B CONFIG_MANDATORY_FILE_LOCKING
option.
-Mandatory locking has been fully deprecated in v5.15 kernels, so
+Mandatory locking has been fully deprecated in Linux 5.15, so
this flag should be considered deprecated.
.TP
.B MS_NOATIME
This ensures that applications compiled against
new headers get at least
.B O_DSYNC
-semantics on pre-2.6.33 kernels.
+semantics before Linux 2.6.33.
.\"
.SS C library/kernel differences
Since glibc 2.26,
.IP
On Linux, this limit can be read and modified via
.IR /proc/sys/kernel/shmmni .
-.\" Kernels between 2.4.x and 2.6.8 had an off-by-one error that meant
-.\" that we could create one more segment than SHMMNI -- MTK
+.\" Kernels between Linux 2.4.x and Linux 2.6.8 had an off-by-one error
+.\" that meant that we could create one more segment than SHMMNI -- MTK
.\" This /proc file is not available in Linux 2.2 and earlier -- MTK
.PP
The implementation has no specific limits for the per-process maximum
and before glibc 2.17,
.\" glibc commit 93a78ac437ba44f493333d7e2a4b0249839ce460
the implementation falls back to this technique on systems
-running pre-2.6 Linux kernels.
+running kernels older than Linux 2.6.
.SH EXAMPLES
The program below takes two arguments: a sleep period in seconds,
and a timer frequency in nanoseconds.
.BR ioctl (2)
.B VT_GETHIFONTMASK
operation
-(available in Linux kernels 2.6.18 and above)
+(available since Linux 2.6.18)
on
.IR /dev/tty[1\-63] ;
the value is returned in the
.I msg_name
by
.BR recvmsg (2)
-does not work in some 2.2 kernels.
+does not work in some Linux 2.2 kernels.
.\" .SH AUTHORS
.\" This man page was written by Andi Kleen.
.SH SEE ALSO
.I HZ
varies across kernel versions and hardware platforms.
On i386 the situation is as follows:
-on kernels up to and including 2.4.x, HZ was 100,
+on kernels up to and including Linux 2.4.x,
+HZ was 100,
giving a jiffy value of 0.01 seconds;
-starting with 2.6.0, HZ was raised to 1000, giving a jiffy of
-0.001 seconds.
+starting with Linux 2.6.0,
+HZ was raised to 1000,
+giving a jiffy of 0.001 seconds.
Since Linux 2.6.13, the HZ value is a kernel
configuration parameter and can be 100, 250 (the default) or 1000,
yielding a jiffies value of, respectively, 0.01, 0.004, or 0.001 seconds.
Since Linux 2.6.20, a further frequency is available:
-300, a number that divides evenly for the common video
-frame rates (PAL, 25 Hz; NTSC, 30 Hz).
+300, a number that divides evenly for the common video frame rates
+(PAL, 25 Hz; NTSC, 30 Hz).
.PP
The
.BR times (2)