mirror of https://github.com/mkerrisk/man-pages
lseek.2, inet_pton.3, tzfile.5: tfix
Please find attach a consistency fix: there were only five "zeroes" but twenty four "zeros" in those manual pages. (Make all instances "zeros".) Signed-off-by: David Prévot <taffit@debian.org>
This commit is contained in:
parent
f7cac3c341
commit
fb30b09644
|
@ -126,12 +126,12 @@ This can be useful for applications such as file backup tools,
|
||||||
which can save space when creating backups and preserve holes,
|
which can save space when creating backups and preserve holes,
|
||||||
if they have a mechanism for discovering holes.
|
if they have a mechanism for discovering holes.
|
||||||
|
|
||||||
For the purposes of these operations, a hole is a sequence of zeroes that
|
For the purposes of these operations, a hole is a sequence of zeros that
|
||||||
(normally) has not been allocated in the underlying file storage.
|
(normally) has not been allocated in the underlying file storage.
|
||||||
However, a file system is not obliged to report holes,
|
However, a file system is not obliged to report holes,
|
||||||
so these operations are not a guaranteed mechanism for
|
so these operations are not a guaranteed mechanism for
|
||||||
mapping the storage space actually allocated to a file.
|
mapping the storage space actually allocated to a file.
|
||||||
(Furthermore, a sequence of zeroes that actually has been written
|
(Furthermore, a sequence of zeros that actually has been written
|
||||||
to the underlying storage may not be reported as a hole.)
|
to the underlying storage may not be reported as a hole.)
|
||||||
In the simplest implementation,
|
In the simplest implementation,
|
||||||
a file system can support the operations by making
|
a file system can support the operations by making
|
||||||
|
@ -145,7 +145,7 @@ return
|
||||||
(i.e., even if the location referred to by
|
(i.e., even if the location referred to by
|
||||||
.I offset
|
.I offset
|
||||||
is a hole,
|
is a hole,
|
||||||
it can be considered to consist of data that is a sequence of zeroes).
|
it can be considered to consist of data that is a sequence of zeros).
|
||||||
.\" https://lkml.org/lkml/2011/4/22/79
|
.\" https://lkml.org/lkml/2011/4/22/79
|
||||||
.\" http://lwn.net/Articles/440255/
|
.\" http://lwn.net/Articles/440255/
|
||||||
.\" http://blogs.oracle.com/bonwick/entry/seek_hole_and_seek_data
|
.\" http://blogs.oracle.com/bonwick/entry/seek_hole_and_seek_data
|
||||||
|
|
|
@ -93,7 +93,7 @@ For example, the loopback address
|
||||||
.I 0:0:0:0:0:0:0:1
|
.I 0:0:0:0:0:0:0:1
|
||||||
can be abbreviated as
|
can be abbreviated as
|
||||||
.IR ::1 .
|
.IR ::1 .
|
||||||
The wildcard address, consisting of all zeroes, can be written as
|
The wildcard address, consisting of all zeros, can be written as
|
||||||
.IR :: .
|
.IR :: .
|
||||||
.IP 3.
|
.IP 3.
|
||||||
An alternate format is useful for expressing IPv4-mapped IPv6 addresses.
|
An alternate format is useful for expressing IPv4-mapped IPv6 addresses.
|
||||||
|
|
|
@ -13,7 +13,7 @@ begin with the magic characters "TZif" to identify then as
|
||||||
timezone information files,
|
timezone information files,
|
||||||
followed by a character identifying the version of the file's format
|
followed by a character identifying the version of the file's format
|
||||||
(as of 2005, either an ASCII NUL ('\\0') or a '2')
|
(as of 2005, either an ASCII NUL ('\\0') or a '2')
|
||||||
followed by fifteen bytes containing zeroes reserved for future use,
|
followed by fifteen bytes containing zeros reserved for future use,
|
||||||
followed by six four-byte values of type
|
followed by six four-byte values of type
|
||||||
.IR long ,
|
.IR long ,
|
||||||
written in a "standard" byte order
|
written in a "standard" byte order
|
||||||
|
|
Loading…
Reference in New Issue