From: G. Branden Robinson <g.branden.robinson@gmail.com>
Date: Thu, 9 Feb 2023 18:09:50 +0000 (-0600)
Subject: man*/: srcfix (^ -> \[ha])
X-Git-Tag: man-pages-6.03~18
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=e4b0116296e40a82a2cdd5208310ab3f6254b208;p=thirdparty%2Fman-pages.git

man*/: srcfix (^ -> \[ha])

Use correct *roff special character for hat/caret/circumflex accent.

Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
---

diff --git a/man2/adjtimex.2 b/man2/adjtimex.2
index 9f278674a1..d76ec04a9e 100644
--- a/man2/adjtimex.2
+++ b/man2/adjtimex.2
@@ -571,7 +571,7 @@ and
 .I stabil
 are ppm (parts per million) with a 16-bit fractional part,
 which means that a value of 1 in one of those fields
-actually means 2^-16 ppm, and 2^16=65536 is 1 ppm.
+actually means 2\[ha]-16 ppm, and 2\[ha]16=65536 is 1 ppm.
 This is the case for both input values (in the case of
 .IR freq )
 and output values.
diff --git a/man2/eventfd.2 b/man2/eventfd.2
index c1cb408947..5f25ca82b0 100644
--- a/man2/eventfd.2
+++ b/man2/eventfd.2
@@ -183,7 +183,7 @@ event.
 As noted above,
 .BR write (2)
 can never overflow the counter.
-However an overflow can occur if 2^64
+However an overflow can occur if 2\[ha]64
 eventfd "signal posts" were performed by the KAIO
 subsystem (theoretically possible, but practically unlikely).
 If an overflow has occurred, then
diff --git a/man2/mmap2.2 b/man2/mmap2.2
index 1c541d55be..1fd5732ad4 100644
--- a/man2/mmap2.2
+++ b/man2/mmap2.2
@@ -36,7 +36,7 @@ file in 4096-byte units (instead of bytes, as is done by
 .BR mmap (2)).
 This enables applications that use a 32-bit
 .I off_t
-to map large files (up to 2^44 bytes).
+to map large files (up to 2\[ha]44 bytes).
 .SH RETURN VALUE
 On success,
 .BR mmap2 ()
diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
index dd90ab0078..68f68fe31d 100644
--- a/man2/perf_event_open.2
+++ b/man2/perf_event_open.2
@@ -1681,7 +1681,7 @@ are logged into a ring-buffer.
 This ring-buffer is created and accessed through
 .BR mmap (2).
 .PP
-The mmap size should be 1+2^n pages, where the first page is a
+The mmap size should be 1+2\[ha]n pages, where the first page is a
 metadata page
 .RI ( "struct perf_event_mmap_page" )
 that contains various
diff --git a/man2/quotactl.2 b/man2/quotactl.2
index 47655d516f..30e93966f3 100644
--- a/man2/quotactl.2
+++ b/man2/quotactl.2
@@ -88,11 +88,11 @@ The original quota format.
 .TP
 .B QFMT_VFS_V0
 The standard VFS v0 quota format, which can handle 32-bit UIDs and GIDs
-and quota limits up to 2^42 bytes and 2^32 inodes.
+and quota limits up to 2\[ha]42 bytes and 2\[ha]32 inodes.
 .TP
 .B QFMT_VFS_V1
 A quota format that can handle 32-bit UIDs and GIDs
-and quota limits of 2^63 - 1 bytes and 2^63 - 1 inodes.
+and quota limits of 2\[ha]63 - 1 bytes and 2\[ha]63 - 1 inodes.
 .RE
 .IP
 The
diff --git a/man2/shmget.2 b/man2/shmget.2
index 856fd6024f..c4d8df8ed6 100644
--- a/man2/shmget.2
+++ b/man2/shmget.2
@@ -297,7 +297,7 @@ the default value for this limit is:
 .IP
 .in +4n
 .EX
-ULONG_MAX - 2^24
+ULONG_MAX - 2\[ha]24
 .EE
 .in
 .IP
@@ -340,7 +340,7 @@ the default value for this limit is:
 .IP
 .in +4n
 .EX
-ULONG_MAX - 2^24
+ULONG_MAX - 2\[ha]24
 .EE
 .in
 .IP
diff --git a/man2/times.2 b/man2/times.2
index 4f6aac5784..745867e8ec 100644
--- a/man2/times.2
+++ b/man2/times.2
@@ -155,7 +155,7 @@ On Linux, the "arbitrary point in the past" from which the return value of
 .BR times ()
 is measured has varied across kernel versions.
 On Linux 2.4 and earlier, this point is the moment the system was booted.
-Since Linux 2.6, this point is \fI(2^32/HZ) \- 300\fP
+Since Linux 2.6, this point is \fI(2\[ha]32/HZ) \- 300\fP
 seconds before system boot time.
 This variability across kernel versions (and across UNIX implementations),
 combined with the fact that the returned value may overflow the range of
diff --git a/man3/drand48.3 b/man3/drand48.3
index f9425a91ea..a93b8655e0 100644
--- a/man3/drand48.3
+++ b/man3/drand48.3
@@ -70,14 +70,14 @@ The
 and
 .BR nrand48 ()
 functions return nonnegative
-long integers uniformly distributed over the interval [0,\ 2^31).
+long integers uniformly distributed over the interval [0,\ 2\[ha]31).
 .PP
 The
 .BR mrand48 ()
 and
 .BR jrand48 ()
 functions return signed long
-integers uniformly distributed over the interval [\-2^31,\ 2^31).
+integers uniformly distributed over the interval [\-2\[ha]31,\ 2\[ha]31).
 .PP
 The
 .BR srand48 (),
@@ -110,7 +110,7 @@ according to the linear congruential formula:
 .PP
 The parameter
 .I m
-= 2^48, hence 48-bit integer arithmetic is performed.
+= 2\[ha]48, hence 48-bit integer arithmetic is performed.
 Unless
 .BR lcong48 ()
 is called,
diff --git a/man3/ldexp.3 b/man3/ldexp.3
index 6ee0f5495e..fc944b7290 100644
--- a/man3/ldexp.3
+++ b/man3/ldexp.3
@@ -46,7 +46,7 @@ by 2 raised to the power
 .IR exp .
 .SH RETURN VALUE
 On success, these functions return
-.IR "x * (2^exp)" .
+.IR "x * (2\[ha]exp)" .
 .PP
 If
 .I exp
diff --git a/man3/random.3 b/man3/random.3
index 5ad72d8781..7bc300d7ba 100644
--- a/man3/random.3
+++ b/man3/random.3
@@ -49,9 +49,9 @@ The
 function uses a nonlinear additive feedback random
 number generator employing a default table of size 31 long integers to
 return successive pseudo-random numbers in
-the range from 0 to 2^31\ \-\ 1.
+the range from 0 to 2\[ha]31\ \-\ 1.
 The period of this random number generator is very large, approximately
-.IR "16\ *\ ((2^31)\ \-\ 1)" .
+.IR "16\ *\ ((2\[ha]31)\ \-\ 1)" .
 .PP
 The
 .BR srandom ()
@@ -105,7 +105,7 @@ or be the result of a previous call of
 The
 .BR random ()
 function returns a value between 0 and
-.IR "(2^31)\ \-\ 1" .
+.IR "(2\[ha]31)\ \-\ 1" .
 The
 .BR srandom ()
 function returns no value.
diff --git a/man3/tgamma.3 b/man3/tgamma.3
index d7318c2cb7..1ed27bf66b 100644
--- a/man3/tgamma.3
+++ b/man3/tgamma.3
@@ -42,7 +42,7 @@ These functions calculate the Gamma function of
 The Gamma function is defined by
 .PP
 .RS
-Gamma(x) = integral from 0 to infinity of t^(x\-1) e^\-t dt
+Gamma(x) = integral from 0 to infinity of t\[ha](x\-1) e\[ha]\-t dt
 .RE
 .PP
 It is defined for every real number except for nonpositive integers.
diff --git a/man5/proc.5 b/man5/proc.5
index 7d09da6bb0..b253e42f5b 100644
--- a/man5/proc.5
+++ b/man5/proc.5
@@ -3073,7 +3073,7 @@ The size in bytes of a certain order is given by the formula:
 .IP
 .in +4n
 .EX
-(2^order)\ *\ PAGE_SIZE
+(2\[ha]order)\ *\ PAGE_SIZE
 .EE
 .in
 .IP
@@ -5195,7 +5195,7 @@ On 32-bit platforms, 32768 is the maximum value for
 .IR pid_max .
 On 64-bit systems,
 .I pid_max
-can be set to any value up to 2^22
+can be set to any value up to 2\[ha]22
 .RB ( PID_MAX_LIMIT ,
 approximately 4 million).
 .\" Prior to Linux 2.6.10, pid_max could also be raised above 32768 on 32-bit
diff --git a/man7/mount_namespaces.7 b/man7/mount_namespaces.7
index cfd639c52c..c40aae96b1 100644
--- a/man7/mount_namespaces.7
+++ b/man7/mount_namespaces.7
@@ -1129,7 +1129,7 @@ in the following step:
                \fBstrace \-o /tmp/log \e\fP
                \fBumount /mnt/dir\fP
 umount: /etc/shadow: not mounted.
-# \fBgrep \[aq]^umount\[aq] /tmp/log\fP
+# \fBgrep \[aq]\[ha]umount\[aq] /tmp/log\fP
 umount2("/etc/shadow", 0)     = \-1 EINVAL (Invalid argument)
 .EE
 .in
diff --git a/man7/random.7 b/man7/random.7
index 280e798c69..69e6c24035 100644
--- a/man7/random.7
+++ b/man7/random.7
@@ -191,7 +191,7 @@ The amount of seed material required to generate a cryptographic key
 equals the effective key size of the key.
 For example, a 3072-bit RSA
 or Diffie-Hellman private key has an effective key size of 128 bits
-(it requires about 2^128 operations to break) so a key generator
+(it requires about 2\[ha]128 operations to break) so a key generator
 needs only 128 bits (16 bytes) of seed material from
 .IR /dev/random .
 .PP
diff --git a/man7/sched.7 b/man7/sched.7
index ba9196ac8d..4da3ea3314 100644
--- a/man7/sched.7
+++ b/man7/sched.7
@@ -318,7 +318,7 @@ sched_runtime <= sched_deadline <= sched_period
 In addition, under the current implementation,
 all of the parameter values must be at least 1024
 (i.e., just over one microsecond,
-which is the resolution of the implementation), and less than 2^63.
+which is the resolution of the implementation), and less than 2\[ha]63.
 If any of these checks fails,
 .BR sched_setattr (2)
 fails with the error
diff --git a/man7/tcp.7 b/man7/tcp.7
index 2daea58aff..c0c4a838bd 100644
--- a/man7/tcp.7
+++ b/man7/tcp.7
@@ -300,11 +300,11 @@ Enabling this option can harm the clients of your server.
 .IR tcp_adv_win_scale " (integer; default: 2; since Linux 2.4)"
 .\" Since Linux 2.4.0-test7
 Count buffering overhead as
-.IR "bytes/2^tcp_adv_win_scale" ,
+.IR "bytes/2\[ha]tcp_adv_win_scale" ,
 if
 .I tcp_adv_win_scale
 is greater than 0; or
-.IR "bytes\-bytes/2^(\-tcp_adv_win_scale)" ,
+.IR "bytes\-bytes/2\[ha](\-tcp_adv_win_scale)" ,
 if
 .I tcp_adv_win_scale
 is less than or equal to zero.
@@ -368,7 +368,7 @@ but not loaded.
 This variable defines how many
 bytes of the TCP window are reserved for buffering overhead.
 .IP
-A maximum of (\fIwindow/2^tcp_app_win\fP, mss) bytes in the window
+A maximum of (\fIwindow/2\[ha]tcp_app_win\fP, mss) bytes in the window
 are reserved for the application buffer.
 A value of 0 implies that no amount is reserved.
 .\"
diff --git a/man7/udplite.7 b/man7/udplite.7
index 6e23303405..509b3060ca 100644
--- a/man7/udplite.7
+++ b/man7/udplite.7
@@ -64,15 +64,15 @@ The following two options are specific to UDP-Lite.
 .B UDPLITE_SEND_CSCOV
 This option sets the sender checksum coverage and takes an
 .I int
-as argument, with a checksum coverage value in the range 0..2^16-1.
+as argument, with a checksum coverage value in the range 0..2\[ha]16-1.
 .IP
 A value of 0 means that the entire datagram is always covered.
 Values from 1\-7 are illegal (RFC\ 3828, 3.1) and are rounded up to
 the minimum coverage of 8.
 .IP
 With regard to IPv6 jumbograms (RFC\ 2675), the UDP-Litev6 checksum
-coverage is limited to the first 2^16-1 octets, as per RFC\ 3828, 3.5.
-Higher values are therefore silently truncated to 2^16-1.
+coverage is limited to the first 2\[ha]16-1 octets, as per RFC\ 3828, 3.5.
+Higher values are therefore silently truncated to 2\[ha]16-1.
 If in doubt, the current coverage value can always be queried using
 .BR getsockopt (2).
 .TP
diff --git a/man7/units.7 b/man7/units.7
index e089c23590..4618727ae7 100644
--- a/man7/units.7
+++ b/man7/units.7
@@ -15,30 +15,30 @@ Below the standard prefixes.
 .TS
 l l l.
 Prefix	Name	Value
-q	quecto	10^\-30 = 0.000000000000000000000000000001
-r	ronto	10^\-27 = 0.000000000000000000000000001
-y	yocto	10^\-24 = 0.000000000000000000000001
-z	zepto	10^\-21 = 0.000000000000000000001
-a	atto	10^\-18 = 0.000000000000000001
-f	femto	10^\-15 = 0.000000000000001
-p	pico	10^\-12 = 0.000000000001
-n	nano	10^\-9  = 0.000000001
-\[mc]	micro	10^\-6  = 0.000001
-m	milli	10^\-3  = 0.001
-c	centi	10^\-2  = 0.01
-d	deci	10^\-1  = 0.1
-da	deka	10^ 1  = 10
-h	hecto	10^ 2  = 100
-k	kilo	10^ 3  = 1000
-M	mega	10^ 6  = 1000000
-G	giga	10^ 9  = 1000000000
-T	tera	10^12  = 1000000000000
-P	peta	10^15  = 1000000000000000
-E	exa	10^18  = 1000000000000000000
-Z	zetta	10^21  = 1000000000000000000000
-Y	yotta	10^24  = 1000000000000000000000000
-R	ronna	10^27  = 1000000000000000000000000000
-Q	quetta	10^30  = 1000000000000000000000000000000
+q	quecto	10\[ha]\-30 = 0.000000000000000000000000000001
+r	ronto	10\[ha]\-27 = 0.000000000000000000000000001
+y	yocto	10\[ha]\-24 = 0.000000000000000000000001
+z	zepto	10\[ha]\-21 = 0.000000000000000000001
+a	atto	10\[ha]\-18 = 0.000000000000000001
+f	femto	10\[ha]\-15 = 0.000000000000001
+p	pico	10\[ha]\-12 = 0.000000000001
+n	nano	10\[ha]\-9  = 0.000000001
+\(mc	micro	10\[ha]\-6  = 0.000001
+m	milli	10\[ha]\-3  = 0.001
+c	centi	10\[ha]\-2  = 0.01
+d	deci	10\[ha]\-1  = 0.1
+da	deka	10\[ha] 1  = 10
+h	hecto	10\[ha] 2  = 100
+k	kilo	10\[ha] 3  = 1000
+M	mega	10\[ha] 6  = 1000000
+G	giga	10\[ha] 9  = 1000000000
+T	tera	10\[ha]12  = 1000000000000
+P	peta	10\[ha]15  = 1000000000000000
+E	exa	10\[ha]18  = 1000000000000000000
+Z	zetta	10\[ha]21  = 1000000000000000000000
+Y	yotta	10\[ha]24  = 1000000000000000000000000
+R	ronna	10\[ha]27  = 1000000000000000000000000000
+Q	quetta	10\[ha]30  = 1000000000000000000000000000000
 .TE
 .RE
 .PP
@@ -55,14 +55,14 @@ size, followed by "bi" for "binary".
 .TS
 l l l.
 Prefix	Name	Value
-Ki	kibi	2^10 = 1024
-Mi	mebi	2^20 = 1048576
-Gi	gibi	2^30 = 1073741824
-Ti	tebi	2^40 = 1099511627776
-Pi	pebi	2^50 = 1125899906842624
-Ei	exbi	2^60 = 1152921504606846976
-Zi	zebi	2^70 = 1180591620717411303424
-Yi	yobi	2^80 = 1208925819614629174706176
+Ki	kibi	2\[ha]10 = 1024
+Mi	mebi	2\[ha]20 = 1048576
+Gi	gibi	2\[ha]30 = 1073741824
+Ti	tebi	2\[ha]40 = 1099511627776
+Pi	pebi	2\[ha]50 = 1125899906842624
+Ei	exbi	2\[ha]60 = 1152921504606846976
+Zi	zebi	2\[ha]70 = 1180591620717411303424
+Yi	yobi	2\[ha]80 = 1208925819614629174706176
 .TE
 .RE
 .SS Discussion
diff --git a/man7/unix.7 b/man7/unix.7
index 7c987fbd01..e9fe40c9bb 100644
--- a/man7/unix.7
+++ b/man7/unix.7
@@ -416,9 +416,9 @@ then the socket is autobound to an abstract address.
 The address consists of a null byte
 followed by 5 bytes in the character set
 .IR [0\-9a\-f] .
-Thus, there is a limit of 2^20 autobind addresses.
+Thus, there is a limit of 2\[ha]20 autobind addresses.
 (From Linux 2.1.15, when the autobind feature was added,
-8 bytes were used, and the limit was thus 2^32 autobind addresses.
+8 bytes were used, and the limit was thus 2\[ha]32 autobind addresses.
 The change to 5 bytes came in Linux 2.3.15.)
 .SS Sockets API
 The following paragraphs describe domain-specific details and
diff --git a/man7/utf-8.7 b/man7/utf-8.7
index abdf6244ce..5ff6343068 100644
--- a/man7/utf-8.7
+++ b/man7/utf-8.7
@@ -55,7 +55,7 @@ problems with, for example,  \[aq]\e0\[aq] or \[aq]/\[aq].
 The lexicographic sorting order of UCS-4 strings is preserved.
 .TP
 *
-All possible 2^31 UCS codes can be encoded using UTF-8.
+All possible 2\[ha]31 UCS codes can be encoded using UTF-8.
 .TP
 *
 The bytes 0xc0, 0xc1, 0xfe, and 0xff are never used in the UTF-8 encoding.