Bug#470308: findutils: fixes for the info file

Package: findutils
Version: 4.2.33-1
Severity: minor
Tags: patch upstream
File: /usr/share/info/find.info.gz
X-Debbugs-Cc: bug-findutilsgnu.org

--- /usr/share/info/find.info.gz
+++ /tmp/findinfo.gz.14865	2008-03-10 12:03:29.000000000
-0400
 -578,7
+578,7 
 ensures that any symbolic links listed on the command line
are
 dereferenced, but other symbolic links are not.
 
-   Symbolic links are different to "hard links"
in the sense that you
+   Symbolic links are different than "hard links"
in the sense that you
 need permissions upon the linked-to file in order to be
able to
 dereference the link.  This can mean that even if you
specify the `-L'
 option, `find' may not be able to determine the properties
of the file
 -841,7
+841,7 
 
      The `b' suffix always considers blocks to be 512
bytes.  This is
      not affected by the setting (or non-setting) of the
POSIXLY_CORRECT
-     environment variable.  This behaviour is different to
the
+     environment variable.  This behaviour is different
than the
      behaviour of the `-ls' action).  If you want to use
1024-byte
      units, use the `k' suffix instead.
 
 -1128,8
+1128,8 
 
  -- Action: -quit
      Exit immediately (with return value zero if no errors
have
-     occurred).  This is different to `-prune' because
`-prune' only
-     applies to the contents of pruned directories, whilt
`-quit'
+     occurred).  This is different than `-prune' because
`-prune' only
+     applies to the contents of pruned directories, while
`-quit'
      simply makes `find' stop immediately.  No child
processes will be
      left running, but no more files specified on the
command line will
      be processed.  For example, `find /tmp/foo /tmp/bar
-print -quit'
 -2176,7
+2176,7 
 
    Here, the first invocation of `xargs' has no input line
length limit
 because it doesn't use the `-I' option. The second
invocation of
-`xargs' does have such a limit, but we have ensured that
the it never
+`xargs' does have such a limit, but we have ensured that it
never
 encounters a line which is longer than it can handle.
 
    This is not an ideal solution.  Instead, the `-I' option
should not
 -3181,14
+3181,14 
 `--null'
 `-0'
      Results are separated with the ASCII NUL character
rather than the
-     newline character.  To get the full benefit of the use
of this
+     newline character.  To get the full benefit of this
      option, use the new `locate' database format (that is
the default
      anyway).
 
 `--print'
 `-p'
-     Print search results when they normally would not,
because of the
-     presence of `--statistics' (`-S') or `--count'
(`-c').
+     Print search results when they normally wouldn't be
due to
+     use of `--statistics' (`-S') or `--count' (`-c').
 
 `--wholename'
 `-w'
 -5248,7
+5248,7 
 ..................
 
 If your system supports the O_NOFOLLOW flag (1) to the
`open(2)' system
-call, `find' uses it when safely changing directory.  The
target
+call, `find' uses it to safely change directories.  The
target
 directory is first opened and then `find' changes working
directory
 with the `fchdir()' system call.  This ensures that
symbolic links are
 not followed, preventing the sort of race condition attack
in which use
 -5472,7
+5472,7 
    If remote users can choose the names of files stored on
your system,
 and these files are indexed by `updatedb', this may be a
remote
 security vulnerability.  Findutils version 4.2.31 fixes
this problem.
-The `updatedb', `bigram' and `code' programs do no appear
to be
+The `updatedb', `bigram' and `code' programs do not appear
to be
 affected.
 
    If you are also using GNU coreutils, you can use the
following
 -5558,7
+5558,7 
 `Warning: filesystem /path/foo has recently been mounted'
 `Warning: filesystem /path/foo has recently been
unmounted'
      These messages might appear when `find' moves into a
directory and
-     finds that the device number and inode are different
to what it
+     finds that the device number and inode are different
than what it
      expected them to be.  If the directory `find' has
moved into is on
      an network filesystem (NFS), it will not issue this
message,
      because `automount' frequently mounts new filesystems
on
 -5597,7
+5597,7 
      somebody has moved one of the parent directories to
another
      location in the same filesystem.  This may or may not
have been
      done maliciously.  In any case, `find' stops at this
point to
-     avoid traversing parts of the filesystem that it
wasn't intended.
+     avoid traversing parts of the filesystem that it
wasn't intended to.
      You can use `ls -li' or `find /path -inum 12345 -o
-inum 67893' to
      find out more about what has happened.
 

On Mon, Mar 10, 2008 at 7:47 PM, Justin Pryzby
<justinpryzbyusers.sourceforge.net> wrote:

>  > Likewise (and some other changes).
>  What else?

No, by likewise I meant "thanks for spotting this
also" and by "and
some other changes" I meant "thanks for the other
changes you sent,
but I won't quote them".   Sorry for the confusion.

>  I include a patch against 4.2.33-1 (Debian).  A few
changes weren't
>  necessary in that (more recent) version:

I have applied your patch with this ChangeLog entry.   The
"(tiny
change)" simply means that the change is small enough
not to require
you to provide a copyright assignment to the FSF before I
apply the
patch.

2008-03-10  Justin Pryzby  <justinpryzbyusers.sourceforge.net> (tiny change)

	* doc/find.texi: Various typo corrections.

Thanks for your help!

James.

On Mon, Mar 10, 2008 at 04:59:15PM +0000, James Youngman
wrote:
> On Mon, Mar 10, 2008 at 4:05 PM, Justin Pryzby
> <justinpryzbyusers.sourceforge.net> wrote:
> >  -   Symbolic links are different to "hard
links" in the sense that you
> >  +   Symbolic links are different than "hard
links" in the sense that you
> 
> No.   The phrase "different to" is correct,
but it you prefer to be
> pedantic, then "different from" would
probably be the ideal phrasing.
On reflection, I agree.

> >  -     Print search results when they normally
would not, because of the
> >  -     presence of `--statistics' (`-S') or
`--count' (`-c').
> >  +     Print search results when they normally
wouldn't be due to
> >  +     use of `--statistics' (`-S') or `--count'
(`-c').
> 
> Likewise (and some other changes).
What else?

> However, "find.info" is not the source file;
it is generated from find.texi.
Doh.

> You can get the current upstream source from
> http://
savannah.gnu.org/cvs/?group=findutils.    Please send
your
> patch to bug-findutilsgnu.org or to
findutils-patchesgnu.org.
I include a patch against 4.2.33-1 (Debian).  A few changes
weren't
necessary in that (more recent) version:

-This behaviour is different to

-This is different to `-prune'
(2 lines)

-do no appear

Justin


--- findutils-4.2.28.orig/doc/find.texi
+++ findutils-4.2.28/doc/find.texi
 -615,7
+615,7 
 links listed on the command line are dereferenced, but
other symbolic
 links are not.
 
-Symbolic links are different to ``hard links'' in the sense
that you
+Symbolic links are different from ``hard links'' in the
sense that you
 need permissions upon the linked-to file in order to be
able to
 dereference the link.  This can mean that even if you
specify the
 samp option, code may not be able
to determine the
 -893,7
+893,7 
 
 The `b' suffix always considers blocks to be 512 bytes. 
This is not
 affected by the setting (or non-setting) of the
POSIXLY_CORRECT
-environment variable.  This behaviour is different to the
behaviour of
+environment variable.  This behaviour is different from the
behaviour of
 the samp action).  If you want to use 1024-byte
units, use the
 `k' suffix instead.
 
 -2222,7
+2222,7 
 Here, the first invocation of code has no input
line length
 limit because it doesn't use the samp option. The
second
 invocation of code does have such a limit, but we
have ensured
-that the it never encounters a line which is longer than it
can
+that it never encounters a line which is longer than it
can
 handle.  
 
 This is not an ideal solution.  Instead, the samp
option should
 -2801,14
+2801,14 
 item --null
 itemx -0
 Results are separated with the ASCII NUL character rather
than the
-newline character.  To get the full benefit of the use of
this option,
+newline character.  To get the full benefit of this
option,
 use the new code database format (that is the
default
 anyway).
 
 item --print
 itemx -p
-Print search results when they normally would not, because
of the
-presence of samp (samp) or samp
+Print search results when they normally would not be due
to
+use of samp (samp) or samp
 (samp).
 
 item --wholename
 -4131,7
+4131,7 
 If your system supports the O_NOFOLLOW flag footnote{GNU/Linux
 (kernel version 2.1.126 and later) and FreeBSD (3.0-CURRENT
and later)
 support this} to the code{open(2)} system call, code uses it
-when safely changing directory.  The target directory is
first opened
+to safely change directories.  The target directory is
first opened
 and then code changes working directory with the
 code{fchdir()} system call.  This ensures that
symbolic links are not
 followed, preventing the sort of race condition attack in
which use
 -4405,7
+4405,7 
 item Warning: filesystem /path/foo has recently been
mounted
 itemx Warning: filesystem /path/foo has recently been
unmounted
 These messages might appear when code moves into a
directory
-and finds that the device number and inode are different to
what it
+and finds that the device number and inode are different
from what it
 expected them to be.  If the directory code has moved into is
 on an network filesystem (NFS), it will not issue this
message, because
 code frequently mounts new filesystems on
directories as
 -4445,7
+4445,7 
 another location in the same filesystem.  This may or may
not have been done
 maliciously.  In any case, code stops at this
point
 to avoid traversing parts of the filesystem that it wasn't
-intended.  You can use code{ls -li} or code{find
/path -inum
+intended to.  You can use code{ls -li} or code{find
/path -inum
 12345 -o -inum 67893} to find out more about what has
happened.
 
 item sanity check of the fnmatch() library function
failed.