1 GNU findutils NEWS - User visible changes. -*- outline -*- (allout)
3 * Major changes in release 4.3.14-CVS
7 #15472: Error messages that print ino_t values are no longer truncated
8 on platforms with 64-bit ino_t.
10 ** Documentation Fixes
12 #20873: Indicate that * matches / and leading dot in filenames for
15 * Major changes in release 4.3.13, 2008-02-14
19 #22057: Actually rename the old locate database to the new one
20 atomically, instead of just claiming the rename is atomic in a
23 #22056: -Xtime tests are off by one second (e.g. rm -f x; touch x;
24 find x -mtime 0 should print x).
26 #21960: xargs should collect the exit status of child processes even if
27 the total count of unreaped children has not yet reached the maximum
30 ** Documentation Fixes
32 Documented various useful techniques with invoking "sh -c" from
33 xargs in the Texinfo documentation.
37 Updated the German, Irish, Dutch, Polish and Vietnamese translations.
40 * Major changes in release 4.3.12, 2007-12-19
44 #15384: Find misbehaves when parent directory is not readable.
46 ** Documentation Fixes
48 More examples in the xargs manual page, including a portable analogue
53 Updated translations: Polish, Dutch, Portuguese, Swedish, Vietnamese.
56 * Major changes in release 4.3.11, 2007-12-02
60 When the POSIXLY_CORRECT environment variable is set, "find -perm
61 +a+w" is rejected as invalid. Some other similar mode strings
62 starting with '+' which are not valid in POSIX are also rejected.
64 The -prune action now always evaluates as true (this is also a
70 #21568: Switch to checking the gnulib code out with native git, not
71 CVS. This affects mainly those who check findutils code out of CVS.
72 This is not the first time this bug has been fixed (the previous fix
73 used "cvs update -D", which git-cvspserver silently does not
76 #21039: Setting the POSIXLY_CORRECT environment variable now turns off
77 warnings by default, because POSIX requires that only diagnostic
78 messages (and -ok prompts) are printed on STDERR, and diagnostic
79 messages must also result in a nonzero exit status.
81 #20970: Trailing slash on directory arguments breaks -name. "find
82 foo/ -name foo" now correctly matches foo and printf foo/. See POSIX
83 interp http://www.opengroup.org/austin/interps/uploads/40/14959/AI-186.txt
85 #20865: Using both -delete and -prune without explicitly using -depth
86 is now an error. Traditionally, -delete has always turned -depth on
87 anyway, so this is not a functional change. However, using -depth
88 (implicitly or explicitly) makes -prune a no-op. This change is
89 intended to avoid nasty surprises for people who test with
90 "-print" and then change it to "-delete" when they are happy.
92 #20803: POSIX requires that -prune always returns true. Previously it
93 returned false when -depth was in effect and true otherwise.
95 #20802: If -delete fails, find's exit status will now be non-zero.
96 However, find still skips trying to delete ".".
98 ** Documentation Fixes
99 #21635: Some of the documentation files had missing copying
100 conditions. The missing files now have copying headers, and these
101 are compatible with each other (GNU FDL 1.2).
103 #21634: No copy of FDL 1.2 included with the source code
105 #21633: Missing copyright/license header in some documentation.
107 #21628: find -perm /000 matches all files rather than none, since
108 findutils-4.3.3. The Texinfo documentation is now consistent with the
109 manual page on this point.
111 #21270: Formatting fixes to the xargs.1 manual page, including making
112 options bold instead of italic and making OPTIONS a section header
113 rather than a subsection.
115 * Major changes in release 4.3.10, 2007-11-13
119 #21568: findutils gnulib code does not match the date in
120 import-gnulib.config. We now check out the gnulib code via
123 * Major changes in release 4.3.9, 2007-11-11
127 Findutils version 4.3.9 is released under version 3 of the GNU General
132 #20834: Avoid segmentation violation for -execdir when $PATH is
133 unset. Assume that the PATH is safe in this situation.
135 #20310: configure uses hosts's support status for "sort -z" when
136 generating the updatedb script for use on the target. This is
137 inappropriate when cross-compiling, so avoid doing that.
139 #20263: Compilation fix for DEC Alpha OSF/1 cc, which forbids the
140 ordering comparison of function pointers.
142 #20139: find -[acm]time -N (wrongly) includes files from N days ago,
143 as well as (correctly) from less than N days ago.
145 #20273: When xargs is successful without consuming all of stdin (for
146 example, with the -E option), and stdin is seekable, xargs now
147 correctly restores the file position, even on platforms where exit()
148 does not follow the POSIX rules of doing likewise. Likewise for find
149 (for example, with the -ok action).
151 #20547: The version information printed by find, xargs, locate,
152 updatedb, frcode and code now complies with the GNU Project's coding
155 #20662: Avoid memory leak in find -name and other places affected by
156 gnulib dirname module. The leak had been present since 4.3.1.
158 #20751: Avoid memory corruption in find -ls that has been present
161 #20871: Assertion failure introduced in 4.3.3, when oldfind is invoked
162 in a directory where the parent directory lacks search permission.
166 #20594: Allow fine-tuning of the default argument size used by xargs
167 and find at ./configure time.
169 #20688: The warning printed by -name or -iname when the pattern to
170 match contains a slash can now be silenced by -nowarn. This warning
171 was originally introduced unconditionally in 4.2.21.
173 Translation of locate --limit problems is improved.
175 POSIX will standardise -path, so the documentation no longer claims
176 that -wholename is the 'canonical' test, and -ipath no longer
179 ** Documentation Fixes
181 Point out more explicitly that the subsecond timestamp support
182 introduced by findutils-4.3.3 introduces a change in the format of
185 Also explain that when reporting a bug, you should check the most
186 recent findutils release first.
188 Introduced doc/find-maint.texi, a maintenance manual for findutils.
190 Added an extra worked example for find (copying a subset of files).
192 The locate command's manual page now has a HISTORY section.
194 #20951: Very bad/unclear/confusing documentation of security checks in
197 #20865: Better documentation on the fact that -delete implies -depth
198 and that -delete interacts badly with -prune.
200 #20552: Fixed typos, formatting and section ordering issues in the
203 #20529: removed spurious 'o' in description of "xargs -a" in
206 #20232: The --max-database-age option of locate was added in release
207 4.3.3, but this file (NEWS) did not previously mention this fact.
211 Updated Dutch translation.
214 * Major changes in release 4.3.8, 2007-06-12
218 #20157: Avoid segfault in locate when run as root. This is caused by
219 a buffer overrun, but at this time no exploit mechanism is known.
221 * Major changes in release 4.3.7, 2007-06-09
223 ** Functional changes
225 Locate can now read old-format locate databases generated on machines
226 with a different byte order. It does this by guessing the byte order,
227 so the result is not completely reliable. If you need to share
228 databases between machines of different architectures, you should use
229 the LOCATE02 format (which has other advantages, as explained in the
234 #20014: Findutils-4.3.7 includes a patch for a potential security
235 problem in locate. When locate read an old-format database, it read
236 file names into a fixed-length buffer allocated on the heap without
237 checking for overflow. Although overflowing a heap buffer is often
238 somewhat safer than overflowing a buffer on the stack, this bug still
239 has potential security implications.
241 This bug also affected the following previous findutils releases:
243 - All releases prior to 4.2.31
244 - Findutils 4.3.0 to 4.3.6.
246 This bug has been assigned CVE number CVE-2007-2452.
250 #20128: Fix compilation error of find/tree.c on AIX with GCC.
252 #20005: Tests -mtime -n and -mtime +n incorrectly treated like -mtime n.
254 #19983: include_next causes compilation failure in findutils 4.3.6 on
257 #19981: Don't call setgroups if the function isn't available. This
258 fixes Savannah bug# 19981.
260 #19980: Don't use the functions putw() or getw() since these are not
261 in current POSIX. Use the gnulib version of wcwidth() where the
262 system does not provide it.
264 #19979: Compilation errors on BeOS
266 #19970: Cannot cast from pointer to bool using gnulib's <stdbool.h>
268 #19967: Use of __attribute((__noreturn__)) makes compilation fail with
269 some non-GCC compilers
271 #19966: find should link against -lm for modf() and fabs()
273 #19965: Compilation failure on OSF/1 4.0; non-declaration of uintmax_t
275 #19948: Assertion failure O_NOFOLLOW != 0 on IRIX 6.5
277 #19871: Typos in find.1
279 #19596: Fixed this bug again, this time in the Texinfo manual (the
280 discussion should compare %b with %s/512, not %s/1024).
282 #19416: _FORTIFY_SOURCE warn_unused_result warnings
284 * Major changes in release 4.3.6, 2007-05-21
288 #19948: Fixed an assertion failure on IRIX 6.5 (O_NOFOLLOW is defined
291 #19923: Fixed an array overrun in groups[] array of 'locate' when run by
292 or as root. This bug appears not to be exploitable. If locate is not
293 installed setuid, the bug is not exploitable. For setuid
294 installations, it is concievable that there could be an information
295 leak if the user uses the -d option or the -e option, though the
296 maintainer has been unable to provoke this on an x86 system.
298 #19871: Spurious .R directives in manpage produced error messages from
299 GNU troff. This is now fixed (they are corrected to .B).
301 #19416: The result of I/O operations in print-related actions is now
302 checked, and failures are reported. Any failure will cause find's
303 exit status to be nonzero. The predicate itself will continue to
308 A variety of changes were made to allow compilation to succeed on
311 #19983: Now compiles on DEC C V5.9-005 on Digital UNIX V4.0 (or at
314 #19970: Compile correctly on C89 systems where the "_Bool" type is not
315 provided, taking into account the limitations of the gnulib
316 replacement for stdbool.h.
318 #19967: Build successfully with C compilers that don't support the GCC
319 construct __attribute__((__noreturn__)).
321 #19966: Findutils should now build on systems which have the modf()
322 and fabs() functions in the maths library, -lm. This includes some
323 versions of HP-UX and Solaris.
325 #19965: Fixed a compilation failure on OSF/1 4.0 (no definition of the
329 * Major changes in release 4.3.5, 2007-05-05
331 ** Functional changes
333 Updatedb can now support he generation of file name databases which
334 are compatible with slocate. For some time, GNU locate has been able
337 The /proc filesystem is excluded from the locate database (by
338 default; change PRUNEPATHS to modify this behaviour).
342 #19806: The -samefile predicate might get fooled by inode reuse. We
343 now hold open a file descriptor on the reference file to prevent this.
345 #19768: Better detection of corrupted old-style locate databases
346 (e.g. if the database is too short to include a complete bigram
349 #19766: The frcode and code programs now detect write errors more
352 #19371: Fix compilation failure on systems which #define open to
353 open64 (and similarly with the close system call). This fixes
354 Savannah bug #19371, affecting AIX 5.3.
356 #19658: When cross-compiling, "make clean" no longer deletes the
357 generated file doc/regexprops.texi, because there is no way to
360 #19391: When xargs knows that the system's actual exec limit is larger
361 than the compiled-in ARG_MAX, use the system's limit without
362 generating an assertion failure.
364 #18203: A duplicate report of bug #17478.
366 #17478: Error messages from find can garble the console.
368 #16378: Assertion failure if stat() returns 00000 as the mode
369 of a file. This apparently can happen occasionally with broken NFS
372 #11668: FreeBSD extensions for time specification are now
373 implemented. In fact, these were included in findutils-4.3.3. The
374 change was listed as a functional change (whcih it is) and this bug
375 report was not mentioned.
377 ** Documentation Fixes
379 The locatedb.5 manpage now documents the (default) LOCATE02 format
380 more clearly, and also documents the slocate database format.
382 The maximum and default values applying to the -s option of xargs are
383 now documented more clearly in the manual page.
385 * Major changes in release 4.3.4, 2007-04-21
389 #19634: Test suite now passes (again) if "." is on your $PATH.
391 #19619: Findutils builds once again on Cygwin.
393 #19617: Nonexistent start points are (once again) diagnosed in
394 ftsfind. This bug affected only findutils-4.3.3.
396 #19616: Fix leaf optimisation and loop detection (which were
397 unreliable in findutils 4.3.3). This bug affected only
400 #19615: find --version no longer claims to be using FTS_CWDFD when it
401 isn't. This bug affected only findutils-4.3.3.
403 #19613: "find -L . -type f" no longer causes an assertion failure when
404 it encounters a symbolic link loop. This bug affected only
407 #19605: Issue an error message (and later return nonzero exit status)
408 if a symbolic link loop was encountered during directory traversal.
410 #19484: bigram.c and code.c fail if the first pathname recorded begins
413 #19483: Inconsistent option highlighting in updatedb manpage
415 #18414: Tests for "find -readable" are skipped for the superuser, as
416 on some systems (e.g. Cygwin with an Administrative user) users can
421 Findutils 4.3.4 includes a translation for the Ukranian language.
424 * Major changes in release 4.3.3, 2007-04-15
426 Fiundutils-4.3.3 was released on 2007-04-15.
430 #19596: Correct the comparison in the find manpage between %b and %s
431 (the divisor is 512 not 1024).
433 #18714: In the POSIX locale, vertical tabs and form feeds are not
436 #18713: Quoted but empty arguments which occur last on an xargs input
437 line are no longer ignored, but instead produce an empty argument.
439 #18554: Documented the construct -exec sh -c 'foo "$@" bar' {} +
441 #18466: we now avoid this bug by limiting "-execdir ...+"
442 to just one argument for the time being. There is a performance
443 penalty for doing this. We hope to make a better fix in a later
446 #18384: excess bracket in xargs --help
448 #18320: Zero bytes in input should give warning
450 #17437: Corrected the handling of X in symbolic permissions (such
451 as-u+w,a+X). This change actually occurred in findutils-4.3.2, but
452 the NEWS file for that release didn't mention it.
454 #17396: find -mtime -atime -ctime does not support fractional part
455 (see "Functional changes" below)
457 #14748: find -perm /zzz gives wrong result when zzz evaluates to an
460 #14535: correctly support case-folding in locate (that is, "locate
461 -i") for multibyte character environments such as UTF-8. Previously,
462 if your search string contained a character which was outside the
463 single-byte-encoding range for UTF-8 for example, then the
464 case-folding behaviour failed to work and only exact matches would be
469 ** Functional changes
471 The -printf action (and similar related actions) now support %S,
472 which is a measurement of the sparseness of a file.
474 The test "-perm /000" now matches all files instead of no files. For
475 over a year find has been issuing warning messages indicating that
476 this change will happen. We now issue a warning indicating that the
477 change has already happened (in 4.3.x only, there is no plan to make
478 this change in the 4.2.x series).
480 The tests -newer, -anewer, -cnewer, -mtime, -atime, -ctime, -amin,
481 -cmin, -mmin and -used now support sub-second timestamps, including
482 the ability to specify times with non-integer arguments.
484 The -printf format specifiers also support sub-second timestamps:
493 The new test -newerXY supports comparison between status times for
494 files. One of the status times for a file being considered (denoted
495 X) is checked against a reference time (denoted Y) for the file whose
496 name id the argument. X and Y can be:
499 B Birth time (st_birthtime, currently unsupported)
502 t Valid only for the reference time; instead of comparison
503 against a file status time, the argument is a time string.
506 For example, -newermm is equivalent to -newer, and -neweram is true if
507 the file being considered was accessed more recently than the
508 reference file was modified. The -newerXY test supports subsecond
509 timestamps where these are available. The X=B variant is not yet
512 If you configure the source code and then run the tests with "make
513 check", the test suite fails rather than defaulting to testing the
516 A new option, --max-database-age, has been added to locate.
519 * Major changes in release 4.3.2, 2006-11-25
523 #18222: find -printf '%H %P' once again prints the right result if
524 more than one start point was given on the command line.
526 #17782: find -execdir now correctly puts the prefix "./" before the
527 expansion of "{}" rather than at the start of the argument it appears
528 in. Please note that if you use the -exec or -execdir actions with a
529 shell, then you may be vulnerable to shell code injection attacks, so
530 don't do that. It's not a security defect in find - you should not be
531 passing untrusted data (such as file names chosen by other people) to
534 #17490: find -regex generated a segfault in findutils-4.3.1, but this
535 is fixed in findutils-4.3.2.
537 #17477: find -printf '%' (that is, where the format has a trailing %)
538 now generates an error message.
540 #17372: The fts-based find executable (the default configuration uses
541 fts) is now much faster when -maxdepth is used on filesystems with
544 #15531: The -prune action now behaves correctly when applied to a file.
546 ** Functional changes
548 The slocate database format is now supported. Preliminary changes
549 intended to eventually allow setuid operation of locate have also been
550 made. For the moment, please don't install GNU locate as a
551 set-user-ID program (except for testing purposes; if you do so, please
552 make sure that untrusted users cannot execute the set-user-ID locate
555 Use of an slocate database which was built with a nonzero security
556 mode (at the moment, GNU updatedb will not do this) forces locate's
557 "-e" option to be turned on, which has an effect on the "-S" option
558 which is probably surprising for most users.
561 ** Documentation Fixes
563 The global effect of options (other than -daystart and -follow) is now
564 explained more clearly in the manual page. Savannah bug #15360.
567 * Major changes in release 4.3.1, 2006-08-06
571 Find now follows POSIX rules for determining where directories end and
572 expressions start. This means that "find \(1 \!2 \, \)" now searches
573 in the four named directories, rather than trying to parse an
574 expression. (Savannah bug #15235).
576 You now get a more helpful error message when you use command lines
577 which have missing expressions, such as
584 Savannah bug #15800: If find finds more subdirectories within a parent
585 directory than it previously expected to based on the link count of
586 the parent, the resulting error message now gives the correct
587 directory name (previously an error message was issued but it
588 specified the wrong directory).
590 Savannah bug #16738: "find .... -exec ... {} +" now works if you have
591 a large environment and many files must be passed to the -exec
592 action. The same problem affected the -execdir action, though since
593 the number of files in a given directory will normally be smaller, the
594 problem was worse for -exec.
596 Savannah bug #16579: Updatedb now works if it is running as a user
597 whose login shell is not actually a shell.
599 There have also been a number of documentation improvements (includng
600 Savannah bug #16269).
602 ** Functional changes
604 For find, debug output can now be enabled at runtime with the -D
605 option. This causes the printing of various sorts of information
606 about find's internal state and progress.
608 The find option -nowarn cannot itself produce a warning (this used to
609 happen with commands like "find . -name quux -nowarn -print").
611 ** Performance Enhancements
613 Find now has a rudimentary cost-based optimiser. It has an idea of
614 the basic cost of each test (i.e. that -name is very cheap while -size
615 is more expensive). It re-orders tests bearing in mind the cost of
616 each test and its likely success. Predicates with side effects (for
617 example -delete or -exec) are not reordered. The optimiser is not
618 yet enabled by default, but the new option -O controls the query
619 optimisation level. To see this in action, try
620 find -D opt -O3 . -type f -o -type c -o -size 555 -name Z
621 and compare the optimised query with:
622 find -D opt -O3 . -size 555 -o -type c -o -type f -name Z
624 find -D opt . -size 555 -o -type c -o -type f -name Z
626 Over time, as optimisations are proven to be robust and correct, they
627 will be moved to lower optimisation levels. Some optimisations have
628 always been performed by find (for example -name is always done early
633 Findutils 4.3.1 includes updated translations for the following
635 Vietnamese, Belarusian, Catalan, Danish, German, Greek, Esperanto,
636 Spanish, Estonian, Finnish, French, Irish, Galician, Croatian, Hungarian,
637 Indonesian, Italian, Japanese, Korean, Luganda, Malay, Dutch, Polish,
638 Portuguese, Brazilian Portuguese, Romanian, Russian, Kinyarwanda,
639 Slovak, Slovenian, Serbian, Swedish, Turkish, Chinese (simplified),
640 Chinese (traditional), Bulgarian
642 * Major changes in release 4.3.0, 2005-12-12
644 The 4.3.x release series are currently 'development' releases. Please
645 test it, but think carefully before installing it in a production
646 system. New features in findutils-4.3.x are under development; they
647 may change or go away.
649 All changes up to and including findutils-4.2.27 are included in this
650 release. In addition the following changes are new in this release:
652 ** Functional Changes
654 By default, find now uses the fts() function to search the file
655 system. The use of fts greatly increases find's ability to search
656 extremely deep directory hierarchites.
658 You can tell that the version of find you are using uses FTS, because
659 the output of "find --version" will include the word "FTS".
661 Currently two binaries for 'find' are built. The configure option
662 --without-fts can be used to select whether 'find' uses fts:
665 default configuration find oldfind
666 configure --with-fts find oldfind
667 configure --without-fts ftsfind find
669 New tests, -readable, -writable, -executable. These check that a file
670 can be read, written or executed respectively.
672 * Major changes in release 4.2.27, 2005-12-06
674 ** Warnings of Future Changes
676 The test -perm /000 currently matches no files, but for greater
677 consistency with -perm -000, this will be changed to match all files;
678 this change will probably be made in early 2006. Meanwhile, a warning
679 message is given if you do this.
683 If xargs is invoked with many short arguments on PPC systems running
684 the Linux kernel, we no longer get an "argument list too long" error
685 from the operating system.
687 Fixed a bug in the test suite which caused it to spuriously fail on
688 systems where ARG_MAX is different to the value used by the Linux
689 kernel on 32-bit x86-architecture systems.
691 On systems running the Linux kernel, "find -printf %F" no longer
692 produces the wrong answer for files on filesystems that have been
693 remounted elsewhere using "mount --bind". (Savannah bug #14921).
695 ** Documentation Changes
697 Following some extensive and detailed review comments from Aaron
698 Hawley, the material in the manual pages and the Texinfo manual are
701 The %M format specifier of "find -printf" is now documented, although
702 it has existed since release 4.2.5.
704 The 'find' manual page now correctly documents the fact that -regex
705 defaults to using Emacs-style regular expressions (though this can be
708 * Major changes in release 4.2.26, 2005-11-19
710 ** Public Service Announcements
712 I'd like to point out a second time that the interpretation of '-perm
713 +mode' has changed to be more POSIX-compliant. If you want the old
714 behaviour of the GNU extension you should use '-perm /mode'. See the
715 NEWS entry for findutils version 4.2.21 for details.
717 ** Functional Changes
719 The xargs command now supports a new option (--delimiter) which allows
720 input items to be separated by characters other than null and
721 whitespace. This resolves Savannah support request sr #102914.
723 Sometimes find needs to read the /etc/mtab file (or perform the
724 equivalent operation on systems not using /etc/mtab). If this
725 information is needed but not available, find now exits with an error
726 message non-zero status. If the information is not needed, find will
729 A new xargs option --delimiter allows the input delimiter to be
730 changed (previously \0 was the only choice unless you use the -L
731 option, which changes other semantics too).
735 If the environment size is too large to allow xargs to operate
736 normally, 'xargs --help' still works (now).
738 If the input to xargs is a large number of very short options (for
739 example, one character each), earlier versions of xargs would fail
740 with 'Argument list too long'. However, since this is precisely the
741 problem that xargs was invented to solve, this is a bug. Hence on
742 those systems we now correctly use a shorter command line. This
743 problem particularly affected 64-bit Linux systems because of the
744 larger size of pointers, although 32-bit Linux systems were also
745 affected (albeit for longer command lines). In theory the same
746 problem could affect 'find -exec {} +', but that's much less likely
747 (even so, the bug is fixed there too).
749 Bugfix for an unusual failure mode (Savannah bug #14842) where an
750 attempt to allocate more space for directory contents succeeds but is
751 incorrectly diagnosed as a failure. The likelihood of you
752 experiencing this depends on your architecture, operating system and
753 resource limits. This failure has been observed in a directory
754 containing 35396 entries.
756 ** Documentation Changes
758 The EXAMPLES section of the find manual page now correctly describes
759 the symbolic and octal modes for the -perm test.
761 The documentation and "--help" usage information for the -L, -l, -I
762 and -i options have been clarified (but the behaviour has not changed).
764 The documentation now explains more clearly what happens when you use
767 * Major changes in release 4.2.25, 2005-09-03
771 find -perm /440 (which should succeed if a file is readable by its
772 owner or group) now works. Previously there was a bug which caused
773 this to be treated as "find -perm 440".
775 Some files in the xargs test suite have been renamed to avoid problems
776 on operating systems whoch cannot distinguish filenames on the basis
777 of upper/lower case distinctions.
779 The software now builds on Cygwin, including the generated file
782 Findutils should now build once again on systems supporting AFS, but
783 this support has not recently been fully tested. Findutils should
784 also (once again) build on Cygwin.
788 The test suite for find is now much more extensive.
790 * Major changes in release 4.2.24, 2005-07-29
792 ** Documentation Changes
794 The manual now includes a "Worked Examples" section which talks about
795 the various ways in which findutils can be used to perform common
796 tasks, and why some of these alternatives are better than others.
798 The -I option of xargs (which is required by the POSIX standard) is
801 We now document the fact that find ensures that commands run by -ok
802 and -okdir don't steal find's input. Find does this by redirecting
803 the command's standard input from stdin.
805 Many documentation readability enhancements and proofreading fixes
806 were contributed by Aaron Hawley.
808 ** Functional Changes
810 *** Functional changes in locate
812 The "--regex" option of locate now assumes the regular expression to
813 be in the same syntax as is used in GNU Emacs, though this can be
814 changed with the new option --regextype. This is a change from the
815 existing behaviour (which was to use POSIX Basic Regular Expressions).
816 Since this feature is releatively new anyway, I though it was more
817 useful to have compatibility between regular expression handling in
818 find and locate than to maintain the short-lived previous behaviour of
821 The locate program now also supports a "--regextype" long option which
822 controls which regular expression syntax is understood by locate.
823 This is a long option and has no single-letter 'short option'
826 *** Functional changes in find
828 The regular expression syntax understood by "find" can be changed with
829 the -regextype option; this option is positional, meaning that you can
830 have several tests, each using a distinct syntax (this is not
831 recommended practice however).
833 The default regular expression syntax is substantially the same as
834 that recognised by GNU Emacs, except for the fact that "." will match
837 The leaf optimisation can be disabled with the configure option
838 "--disable-leaf-optimisation", which is equivalent to specifying
839 "-noleaf" on all find command lines. This is useful for systems
840 having filesystems which do not provide traditional Unix behaviour for
841 the link count on directories (for example Cygwin and the Solaris 9
842 HSFS implementation).
846 *** Bug Fixes for find
848 The -iregex test now works once again on systems that lack
849 re_search() (that is, systems on which findutils needs to use the
850 gnulib version of this function).
852 find -regex now once again uses GNU Emacs-compatible regular
855 If invoked with stderr closed, the -fprint and -fprintf actions now no
856 longer cause error messages to be sent into the output file.
858 If the link count of a directory is less that two, the leaf
859 optimisation is now disabled for that directory. This should allow
860 searching of non-Unix filesystems to be more reliable on systems that
861 don't take the trouble to make their filesystems look like traditional
862 Unix filesystems. Some filesystems don't even take the trouble to
863 have a link count of less than two and for these, -noleaf is still
864 required unless --disable-leaf-optimisation was used at configure time.
866 The "%Y" directive for the -printf action now no longer changes find's
867 idea of the mode of the file, so this means among other things that
868 "-printf %Y %y" now works properly. This is Savannah bug #13973.
870 * Major changes in release 4.2.23, 2005-06-19
872 ** Documentation Changes
874 The -L and -I options of xargs are currently incompatible (but should
877 Improved the documentation for -execdir and -okdir.
879 ** Functional Changes to updatedb
881 File names ending in "/" which are specified as an argument to
882 --prunepaths (or in $PRUNEPATHS) don't work, so we now issue an error
883 message if the user tries to do that. The obvious exception of course
884 is "/" which does work and is not rejected.
887 * Major changes in release 4.2.22, 2005-06-12
891 If a directory entry searched with "find -L" is a symbolic link to
892 ".", we no longer loop indefinitely. This problem affected find
893 versions 4.2.19, 4.2.20 and 4.2.21. This problem allows users to make
894 "find" loop indefinitely. This is in effect a denial of service and
895 could be used to prevent updates to the locate database or to defeat
896 file security checks based on find. However, it should be noted that
897 you should not use "find -L" in security-sensitive scenarios.
901 None in this release.
903 ** Functional Changes to locate
905 A locate database can now be supplied on stdin, using '-' as a element
906 of the database-path. If more than one database-path element is '-',
907 later instances are ignored.
909 A new option to locate, '--all' ('-A') causes matches to be limited to
910 entries which match all given patterns, not entries which match
911 one or more patterns.
913 ** Documentation Changes
915 Some typos in the manual pages have been fixed. Various parts of the
916 manual now point out that it is good practice to quote the argument of
917 "-name". The manpage now has a "NON-BUGS" section which explains some
918 symptoms that look like bugs but aren't. The explanations of the "%k"
919 and "%b" directives to "find -printf" have been imrpoved.
922 * Major changes in release 4.2.21, 2005-06-07
923 ** Functional Changes to find
925 The GNU extension "find ... -perm +MODE" has been withdrawn because it
926 is incompatible with POSIX in obscure cases like "find ... -perm ++r".
927 Use the new syntax "find ... -perm /MODE" instead. Old usages will
928 still continue to work, so long as they don't conflict with POSIX.
930 If the output is going to a terminal, the -print, -fprint, -printf and
931 -fprintf actions now quote "unusual" characters to prevent unwanted
932 effects on the terminal. See "Unusual Characters in File Names" for
933 further details. There is no change to the behaviour when the output
934 is not going to a terminal. The locate program does the same thing,
935 unless the -0 option is in effect (in which case the filenames are
938 ** Functional Changes to locate
940 The locate command will now read each locate database at most once.
941 This means that if you are using multiple databases and are searching
942 for more than one name, the results will now be printed in a different
943 order (and if you specified a small limit with --limit, you may get a
944 different set of results).
946 A new option '--print' for locate causes it to print the matching
947 results even if the '--count' or '--statistics' option is in effect.
950 find /blah/blah/blah -depth -empty now works once again.
952 The -regex and -iregex tests of find now correctly accept POSIX Basic
953 Regular Expressions. (Savannah bug #12999)
955 The updatedb program now works on systems where "su" does not support
956 the "-s" option, for example Solaris.
958 * Major changes in release 4.2.20, 2005-03-17
959 ** Internationalization and Localization
960 Updated Vietnamese and Dutch translations.
963 Minor bugfix affecting only those who compile from the CVS repository,
964 as opposed to those who compile from the source releases.
966 * Major changes in release 4.2.19, 2005-03-07
969 find should now no longer hang on systems which lack the O_NOFOLLOW
970 flag to open(2) and which are clients of an unresponsive NFS server
971 (Savannah bug #12044).
973 We now avoid inappropriately failing for "find -L foo" or "find -H
974 foo" if foo is a symbolic link (Savannah bug #12181). Previously we
975 used to fail with the error message "Too many levels of symbolic
978 "find . -false -exec foo {} +" no longer runs an extra instance of foo
979 when find exits (Savannah bug #12230).
981 If the chdir() safety check fails but we can no longer get back to
982 where we started, exit with an explanatory (fatal) error message.
983 This does not happen on GNU/Linux and FreeBSD because the safety check
984 is not needed (the security problem the safety check protects against
985 is prevented in a cleaner way on those systems).
987 "make distclean" no longer deletes regex.c (which "make all" needs).
989 ** Functionality Changes
990 "find -printf "%h\n" will now print "." for files in the current directory.
991 Previously it printed nothing (but there was a bug in the %h
992 implementation anyway). This fixes Savannah bug #12085.
994 Should now build (again) on non-C99-compliant systems.
996 ** Documentation enhancements
997 Fixed some typos and clarified wording in "Working with automounters".
999 ** Internationalization and Localization
1000 New Vietnamese message translation.
1002 * Major changes in release 4.2.18, 2005-02-16
1004 *** "find -depth" was missing out non-leaf directories when they contain
1005 non-directories. This affected findutils releases 4.2.15,
1006 4.2.16 and 4.2.17, but the bug is now fixed.
1007 *** Find no longer hangs on systems which are clients of unresponsive
1009 ** Documentation improvements
1010 *** Improvements and corrections to the find.1 manpage, including corrections to the descriptions of -H and -L.
1012 * Major changes in release 4.2.17, 2005-02-08
1014 *** bug #11861 undefined symbol "basename" on IRIX 5.3
1015 *** bug #11865 xargs -i regression (as compared to findutils-4.2.12)
1016 *** bug #11866 Typo in pred_okdir renders it useless (affecting 4.2.16 only)
1017 *** patch #3723 fix recent process_top_path change (for -execdir on /)
1018 *** Fixing bug #11866 and applying patch #3723 made -execdir work much better.
1019 *** find bar/baz/ugh now works again if baz is a symbolic link (broken
1022 * Major changes in release 4.2.16, 2005-02-05
1023 ** Functionality Changes
1024 *** Updated the message catalogues for the translated messages.
1025 *** The subfs filesystem is now treated the same as the autofs
1027 *** New translations: Belarusian, Catalan, Greek, Esperanto,
1028 Finnish, Irish, Croatian, Hungarian, Japanese, Luganda,
1029 Malay, Romanian, Slovenian, Serbian, Chinese (simplified).
1032 *** The -execdir action now works correctly for files named on the
1035 * Major changes in release 4.2.15, 2005-01-29
1036 ** Functionality Changes
1037 *** locate now supports matching regular expression (--regex).
1038 *** --enable-d_type-optimization (introduced in findutils 4.2.13) is now turned on by default.
1040 * Major changes in release 4.2.14, 2005-01-25
1041 ** Functionality Changes
1042 *** New options -L, -P, -H for locate. The work in the same was as the same options for find.
1044 *** Don't include the "findutils/find/testsuite/find.gnu" subdirectory in the
1045 distributed tar file more than once.
1046 *** Should now build on Solaris once again.
1047 *** -xtype and -printf %Y now work correctly for symbolic links once again
1048 ** Documentation improvements
1049 *** All options for "locate" are now documented
1051 * Major changes in release 4.2.13, 2005-01-23
1052 ** Performance Enhancements
1053 *** On Linux and some other systems, a large performance improvement,
1054 because we can eliminate many of the calls to lstat() (in extreme
1055 cases, 99% of them). Limited testing shows a 2x speedup on NFS
1056 filesystems. Other systems which can make use of this enhancement
1057 include Mac OS X and *BSD.
1059 * Major changes in release 4.2.12, 2005-01-22
1060 ** Functionality Changes
1061 *** find is now POSIX-compliant, as far as I know.
1062 *** -exec ... {} + now works.
1063 *** New actions -execdir and -okdir which are like -exec and -ok but more secure.
1064 *** "locate -w" is now a synonym for "locate --wholepath".
1065 *** An empty path entry in the locate database path (for example "::" in
1066 $LOCATE_PATH or in the argument to "locate -d") is taken to mean
1067 the default database, whose name is hard-coded in locate.
1069 *** If find or xargs cannot write to stdout, for example because
1070 output is redirected to a file and the disk is full, the
1071 relevant program will return a non-zero exit status.
1073 * Major changes in release 4.2.11, 2004-12-12
1075 *** Compilation fix for systems without EOVERFLOW.
1076 *** More helpful error message if you make a mistake with (, ), -o or -a.
1077 ** Functionality Changes
1078 *** If you have unclosed parentheses on the find command line,
1079 or any of a number of similar problems, find will now produce
1080 a more helpful error message.
1081 *** locate -b is now a synonym for locate --basename
1082 *** locate now supports a --statistics (or -S) option, which prints some
1083 statistics about the locate databases.
1084 *** Implemented the -samefile option.
1085 ** Documentation improvements
1086 *** New chapter in the manual, "Security Considerations".
1087 *** Better documentation for -prune (Mainly thanks to Stepan Kasal)
1089 *** locate's options -i and -w now work with the -e option (previously a bug
1092 * Major changes in release 4.2.10, 2004-12-06
1094 *** Portability fix for fstype.c: should now compile on UNICOS, and possibly
1095 also produce useful results on BeOS and Dolphin, perhaps other
1098 * Major changes in release 4.2.9, 2004-12-05
1099 ** Functionality Changes
1100 *** xargs no longer treats a line containing only an underscore as a logical end-of-file. To obtain the behaviour that was previously the default, use "-E_".
1101 *** xargs now supports the POSIX options -E, -I and -L. These are synonyms
1102 for the existing options -e, -i and -l, but the latter three are
1105 *** xargs -n NUM now invokes a command as soon as it has NUM arguments.
1106 Previously, it waited until NUM+1 items had been read, and then
1107 invoked the command with NUM arguments, saving the remaining one
1109 *** If "find -L" discovers a symbolic link loop, an error message is issued.
1110 *** If you specify a directory on the find command line, but -prune
1111 is applied to it, find will no longer chdir() into it anyway.
1112 ** Documentation improvements
1113 *** The precise interpretation of the arguments to the -atime, -ctime
1114 and similar tests in find has been documented more clearly.
1116 * Major changes in release 4.2.8, 2004-11-24
1117 *** Bugfix to the findutils 4.2.7 automount handling on Solaris. This
1118 worked to some extent in findutils-4.2.7, but is much improved in
1121 * Major changes in release 4.2.7, 2004-11-21
1122 ** Functionality Changes
1123 *** xargs can now read a list of arguments from a named file, allowing
1124 the invoked program to use the same stdin as xargs started with
1125 (for example ``xargs --arg-file=todo emacs'').
1126 ** Documentation improvements
1127 *** The Texinfo manual now has an extra chapter, "Error Messages". Most
1128 error messages are self-explanatory, but some of the ones which
1129 are not are explained in this chapter.
1131 *** Avoid trying to link against -lsun on UNICOS, which doesn't need it or
1133 *** Bugfix to the findutils 4.2.6 automount handling (which hadn't been enabled
1135 *** Reenabled internationalisation support (which had been accidentally
1136 disabled in findutils-4.2.5).
1138 * Major changes in release 4.2.6, 2004-11-21
1140 *** find now copes rather better when a directory appears to change just as
1141 it is about to start examining it, which happens with automount.
1142 This is because automount mounts filesystems as you change
1143 directory into them. This should resolve Savannah bugs #3998,
1146 * Major changes in release 4.2.5, 2004-11-11
1147 ** Functionality Changes
1148 *** The POSIX options -H and -L are supported. These control whether or not
1149 find will follow symbolic links.
1150 *** The BSD option -P is also now supported (though in any case
1152 ** Documentation improvements
1153 *** Better documentation for "xargs -i".
1155 *** "make install" now respects DESTDIR when generating localstatedir.
1156 (this is only relevant if you are installing to some location
1157 other than the one that you indictaed when you ran "configure").
1158 *** Compatible with automake versions 1.8 and 1.9.
1159 *** Build problems on UNICOS now fixed, though the linker will still generate
1160 warnings because we try to link with the nonexistent library
1161 "-lsun". Edit $(LIBS) to work around this problem.
1163 * Major changes in release 4.2.4, 2004-11-08
1164 ** Functionality Changes
1165 *** If your system sort command has a working "-z" option, updatedb will
1166 now correctly handle newline characters in filenames (as will
1168 *** xargs now uses 128Kb of command line by default (less if the system
1169 doesn't support that much).
1170 *** If you specify a 'find' option after non-option, a warning message
1171 is now issued. Options should be specified immediately after the
1172 list of paths to search. These warnings are enabled if you
1173 specify the -warn option, or if stdin is a tty. They are diabled
1174 by the use of the -nowarn option.
1175 *** Like find, the locate program now supports an option --null (short form -0)
1176 which changes the result separator from newline to NULL.
1177 *** Locate supports the option -c (long form --count) which suppresses normal
1178 output but prints on stdout the number of results produced (like
1180 *** Locate supports the option -l (long form --limit) which limits the
1181 number of results. This is useful if you only want to find out if
1182 there are copies of a certain file on the system, but don't want
1183 to wait for the entire locate database to be searched.
1184 *** Locate now has an option --basename which forces the specified pattern to
1185 be matched against the basename of the entries in the locate
1186 database, rather than the whole name. The default behaviour
1187 (matching against the whole name of the file including all the
1188 parent directory names) corresponds to the option --wholename.
1189 *** updatedb has a new option, --findoptions, that can be used to
1190 pass extra options through to the find command that it uses.
1192 *** "find -printf '%H\n'" now works (rather than segfaulting) on
1193 systems that have non-writable string constants.
1194 *** Better POSIX compliance for the -s option to xargs (out of range
1195 values should just result in bounding to the correct range, not an
1196 error, so now we just print a warning message and adjust the
1198 *** Corrected section numbers of manual page cross-references
1200 * Major changes in release 4.2.3, 2004-10-30
1201 ** Functionality Changes
1202 *** Added new action -delete which deletes things that find matches.
1203 *** Added new action -quit which causes find to exit immediately.
1204 *** A new format directive '%D' for "find -printf" prints the device number.
1205 *** The -ls predicate no longer truncates user or group names.
1206 *** Added new option "-d" which is a synonym for "-depth" for compatibility
1207 with Mac OS, OpenBSD and FreeBSD. This option is already
1208 deprecated since the POSIX standard specifies "-depth".
1209 *** Added two new format specifiers to the -printf action; these are
1210 %y and %Y. They indicate the type of the file as a single letter;
1211 these are the same latters as are used by the "-type" test.
1212 *** If a parent directory changes during the execution of find,
1213 the error message we issue identifies the nature of the change
1214 (for example the previous and current inode numbers of the
1215 directory we've just returned out of).
1217 *** Non-functional code changes to silence compiler warnings.
1219 * Major changes in release 4.2.2, 2004-10-24
1220 ** Documentation improvements
1221 *** "find ... -exec {}+" is not yet supported.
1223 *** Fixed compilation problems on Solaris, RedHat EL AS 2.1, Irix, AIX
1224 *** Work around possible compiler bug on HP-UX 11.23 for ia64
1225 *** The built-in internationalisation support now works again.
1227 *** We now import the gnulib source in the way it is intended to be used,
1228 which means among other things that we only have one config.h file
1230 *** Functions which findutils requires but which are not present in
1231 gnulib are now defined in "libfind.a". This is in the lib
1232 directory, while gnulib is in the gnulib subdirectory.
1233 *** Fixed a typo in the address of the FSF in many of the file headers.
1235 * Major changes in release 4.2.1, 2004-10-17
1237 *** 'find -name \*bar now matches .foobar, because the POSIX standard
1238 requires it, as explained at
1239 http://standards.ieee.org/reading/ieee/interp/1003-2-92_int/pasc-1003.2-126.html
1241 * Major changes in release 4.2.1, 2004-10-17
1243 *** find -iname now works correctly on systems that have an fnmatch() function
1244 that does not support FNM_CASEFOLD
1245 *** updatedb now uses signal names for "trap" instead of numbers,
1246 as per bug #9465 (see http://www.opengroup.org/onlinepubs/009695399/utilities/trap.html)
1247 *** Better support for systems lacking intmax_t
1249 **** findutils now uses a newer version of gnulib (dated 2004-10-17).
1251 * Major changes in release 4.2.0, 2003-06-14
1252 ** Functionality Changes
1253 *** xargs now works better when the environment variables are very extensive.
1254 The xargs command used to run into difficulties if the environment
1255 data contained more than 20480 bytes.
1256 *** New options -wholename and -iwholename
1257 As per the GNU Projecvt coding standard, These are preferred over
1258 the -path and -ipath options. Using -ipath now generates a warning,
1259 though -path does not (since HPUX also offers -path).
1260 *** The environment variable FIND_BLOCK_SIZE is now ignored.
1261 *** New option "-ignore_readdir_race"
1262 silences an error messages which would otherwise occur if a file is removed
1263 after find has read it from the directory using readdir(), but before
1264 find stats the file. There is also an option
1265 -noignore_readdir_race which has the opposite effect.
1266 ** Documentation improvements
1267 *** The -size option of find is now documented in more detail
1268 *** POSIX compliance and GNU extensions
1269 The find manual page also now includes a section
1270 which describes the relationship between the features of GNU
1271 find and the POSIX standard. Some other small improvements
1272 to the find and xargs manual pages have been made.
1273 *** The argument to the -fprintf directive is now better documented.
1274 The escape code '\0' for the `-printf' predicate of find is now
1275 documented, and the documentation for the %k and %b specifiers
1277 *** xargs -i is now more clearly documented.
1279 *** locate 'pa*d' will now find /etc/passwd (if it exists, of course)
1280 *** xargs standard input is not inherited by child processes
1281 If the command invoked by xargs reads from its standard input,
1282 it now gets nothing, as opposed to stealing data from the
1283 list of files that xargs is trying to read.
1284 *** Better support for 64-bit systems.
1285 *** The command "xargs -i -n1" now works as one might expect,
1286 I think this is a strange thing to want to do.
1287 *** Arguments to find -mtime that are too large are now diagnosed
1288 Previously, this just used to cause find just to do the wrong thing.
1289 *** updatedb is now somewhat more robust
1290 The updatedb shell script now does not generate an empty
1291 database if it fails.
1292 *** Sanity-check on some data read from locatedb
1293 Locate now detects some types of file corruption in the
1295 *** The %k format specifier for -fprintf now works
1296 This was broken in 4.1.20.
1298 * Major changes in release 4.1.20, 2003-06-14:
1299 ** New maintainer, James Youngman <jay@gnu.org>
1300 ** As far as I know, this is the first release after 4.1.7, but I've left
1302 ** We now use an "imported" version of gnulib, rather than including
1303 a copy of the gnulib code in our CVS repository. There are no
1304 differences in the build instructions, though (unless you are
1305 building directly from CVS, in which case please read the file
1307 ** There are no (deliberate) functional changes in version 4.1.20.
1309 * Major changes in release 4.1.7, 2001-05-20:
1310 fix problem so that default "-print" is added when "-prune" is used.
1311 security fixes related to directories changing while find is executing.
1313 * Major changes in release 4.1.6, 2000-10-10:
1314 correct bug in prune.
1315 added --ignore-case option for locate
1317 * Major changes in release 4.1.5, 2000-04-12:
1318 Add support for large files
1320 * Major changes in release 4.1.4, 2000-02-26:
1321 bug fixes, more up-to-date languages.
1323 * Major changes in release 4.1.3, 2000-01-27:
1324 added internationalization and localization.
1326 * Major changes in release 4.1.2, 2000-01-18:
1329 * Major changes in release 4.1.1, 1999-08-8:
1330 attempt at successful compilation on many platforms after years of neglect
1331 "--existing" option added to locate "--prunefs" option added to updatedb
1333 * Major changes in release 4.1, 1994-11-3:
1335 ** Distribution renamed to findutils.
1336 ** updatedb is now a user command, installed in $exec_prefix/bin
1337 instead of $exec_prefix/libexec.
1338 ** A few problems in Makefiles and testsuite corrected.
1340 * Major changes in release 4.0, 1994-11-2:
1344 *** Man page for updatedb.
1345 *** Man page for the locate database formats.
1348 *** Takes less CPU time on long paths, because it uses chdir to descend
1349 trees, so it does fewer inode lookups.
1350 *** Does not get trapped in symbolic link loops when -follow is given.
1351 *** Supports "-fstype afs" if you have /afs and /usr/afsws/include
1352 and you configure using the --with-afs option.
1353 *** New action -fls FILE; like -ls but writes to FILE.
1356 *** Supports a new database format, which is 8-bit clean and
1357 allows machines with different byte orderings and integer sizes to
1358 share the databases. The new locate can also detect and read the
1359 old database format automatically. The new databases are typically
1360 30% or more larger than the old ones (due to allowing all 8 bits in
1361 file names). Search times are approximately the same, or faster on
1363 *** Warns if a file name database is more than 8 days old.
1366 *** Takes command-line options.
1369 *** Performance improved 10-20%.
1370 *** The EOF string is not used when -0 is given.
1371 *** Now has a test suite. Some minor bugs fixed as a result.
1373 * Major changes in release 3.8, 1993-03-29:
1375 ** case insensitive versions of -lname, -name, -path, -regex:
1376 -ilname, -iname, -ipath, -iregex
1377 ** %F directive for -printf, -fprintf to print file system type
1379 * Major changes in release 3.7:
1381 ** locate can search multiple databases
1382 ** locate has an option to specify the database path
1383 ** updatedb no longer goes into an infinite loop with some versions of tail
1385 * No NEWS was kept for earlier releases. Known release dates include:
1386 ** release 3.2, 1991-08-28
1387 ** release 3.1, 1991-08-21
1388 ** release 3.0, 1991-08-21
1389 ** release 2.2, 1991-04-05
1390 ** release 2.1, 1991-01-01
1391 ** release 2.0, 1990-11-20
1392 ** release 1.2, 1990-07-03
1393 ** release 1.1, 1990-06-24
1394 ** release 1.0, 1990-06-22
1395 ** beginning of findutils history, 1987-02-21
1398 This is used by Emacs' spell checker ispell.el:
1400 LocalWords: ansi knr strftime xargs updatedb sh fnmatch hin strcpy
1401 LocalWords: lib getstr getline frcode bigram texi depcomp automake
1402 LocalWords: strncasecmp strcasecmp LIBOBJS FUNC prunefs allout libexec
1403 LocalWords: testsuite Texinfo chdir inode fstype afs fls ls EOF lname
1404 LocalWords: regex ilname iname ipath iregex printf fprintf
1406 Copyright (C) 1996, 1999, 2000, 2001, 2003, 2004, 2005, 2006, 2007,
1407 2008 Free Software Foundation, Inc.
1409 Permission is granted to copy, distribute and/or modify this document
1410 under the terms of the GNU Free Documentation License, Version 1.2 or
1411 any later version published by the Free Software Foundation; with no
1412 Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
1413 Texts. A copy of the license is included in the ``GNU Free
1414 Documentation License'' file as part of this distribution.