summaryrefslogtreecommitdiffstats
path: root/usr.bin/find
Commit message (Collapse)AuthorAgeFilesLines
...
* More consistancy. file system > filesystemtrhodes2002-05-162-4/+4
|
* Use `The .Nm utility'charnier2002-04-201-2/+3
|
* Fix to WARNS=2 level.obrien2002-04-153-25/+8
| | | | Tested by: AXP gcc 3.1
* Clean up the 1/2 a** committing from Thu, 3 May 2001 11:05:39 -0700 (PDT).obrien2002-04-142-4/+1010
| | | | | | | | | | | | | | Since then we have living with a GPL'ed find(1) due to grabbing getdate.y from src/contrib/cvs and its user of the GPL'ed xtime.h. I don't even want to think about how this could have affected people using our source base. Would it have been too much trouble to do then what I did now? Copied getdate.y (public domain) to usr.bin/find and change to use standard system headers. find(1) now compiles simply with out having to go to extra effort to do so. Pointed hat to: phk Build fixed on: gcc 3.1 using platforms
* Replace err() with errx(), errno is garbage in this context.charnier2002-04-121-1/+1
|
* find.1 does not encourage users to DTRT when piping to xargs(1)trhodes2002-04-101-0/+7
| | | | | | | PR: 36602 Submitted by: Joshua Goodall <joshua@roughtrade.net> No objections from: ru MFC after: 2 days
* There is breakage in parsedate, so revert to get_date until this can bemarkm2002-04-023-3/+8
| | | | | | resolved. Reported by: paul
* Fix find -exec with no command specified (i.e.: find . -exec ';')jmallett2002-04-021-0/+3
| | | | | | | PR: bin/36521 Submitted by: Simon 'corecode' Schubert <corecode@corecode.ath.cx> Reviewed by: mike MFC after: 3 days
* Fix SCM IDs.obrien2002-04-017-18/+14
|
* Allow to compile a YACC produced file with GCC 3.1 (which has differentobrien2002-04-011-0/+1
| | | | header searching rules for generated files with #line).
* Run find.1 through ispell.keramida2002-04-011-1/+1
| | | | | | PR: docs/36601 Submitted by: Joshua Goodall <joshua@roughtrade.net> MFC after: 3 days
* Change a "/*" within a comment to a "**".dwmalone2002-03-301-1/+2
| | | | Add a missing include spotted by gcc30.
* spellingcharnier2002-03-262-4/+4
|
* Restructure for own parsedate (replacement for get_date from CVS).markm2002-03-214-48/+54
| | | | | | Fix up parsedate.y for WARNS=4. Reviewd by: bde (except for parsedate.y diffs)
* Add a replacement for get_date which is currently being dug out ofmarkm2002-03-211-0/+880
| | | | | | | CVS's sources. This is a "public domain" implementation stolen from INN, and is added unmodified.
* For the sake of consistency, remove an include that is included inmarkm2002-03-201-1/+0
| | | | a previous include. All other files in this app do this.
* Remove __P().markm2002-03-208-23/+23
|
* 1) Remove -Wall from Makefile.dwmalone2002-02-279-71/+80
| | | | | | 2) WARNs fixes (rename option to lookup_option to avoid shadowing, rename argv to argv1 to avoid shadowing, const stuff, prototypes, __unused). 3) Remove "register"s.
* Fixed divots that I created when I moved prototypes of group_from_gidimp2002-02-191-1/+7
| | | | | | | and user_from_uid to grp.h and pwd.h. Update the man pages. Submitted by: David Malone Pointy hat to: imp
* Add a missing comma.ru2001-11-201-1/+1
|
* Document -depthobrien2001-10-061-0/+13
|
* Simplify f_Xtime().ru2001-09-141-24/+11
|
* Bloat find(1) even more, and introduce the conceptru2001-09-143-18/+166
| | | | | | | | of time units to be used with -[acm]time primaries. Based on patch from Nils M Holm <nmh@t3x.org>. PR: bin/29165, bin/30309
* The implementation of -flags was broken and did not match the (poorly)ru2001-09-043-31/+79
| | | | | | | | | | | | | | | | | | | | | | | | | | | | documented behavior. Only a certain set of file flags were recognized, and "no" flags did not match files that have corresponding flags bits turned off. Fix and extend the -flags functionality as follows: : -flags [-|+]<flags>,<notflags> : The flags are specified using symbolic names (see chflags(1)). : Those with the "no" prefix (except "nodump") are said to be : <notflags>. Flags in <flags> are checked to be set, and flags in : <notflags> are checked to be not set. Note that this is different : from -perm, which only allows the user to specify mode bits that : are set. : : If flags are preceded by a dash (``-''), this primary evaluates : to true if at least all of the bits in <flags> and none of the bits : in <notflags> are set in the file's flags bits. If flags are pre- : ceded by a plus (``+''), this primary evaluates to true if any of : the bits in <flags> is set in the file's flags bits, or any of the : bits in <notflags> is not set in the file's flags bits. Otherwise, : this primary evaluates to true if the bits in <flags> exactly match : the file's flags bits, and none of the <flags> bits match those of : <notflags>. MFC after: 2 weeks
* Sort predicates.ru2001-08-311-70/+70
| | | | PR: docs/30237
* Restore the `-perm +mode' feature.ru2001-08-301-2/+2
| | | | | Broken in the "close a PR" race, in revision 1.30. Note that the patch in the PR did not have this bug!
* Remove emalloc and expand to the malloc + error checking it was, where used.obrien2001-07-243-20/+9
|
* Quiet a [useless] compiler warning.obrien2001-07-231-1/+1
|
* Clarify the feature that -exec parameters won't getyar2001-06-291-0/+5
| | | | | | shell-expanded when the specified utility is run. MFC after: 5 days
* mdoc(7) police: fix markup.ru2001-05-161-198/+255
|
* They add the following commands:phk2001-05-039-927/+793
| | | | | | | | | | | | | | | | | | | | | -anewer -cnewer -mnewer -okdir -newer[acm][acmt] With it, you can form queries like find . -newerct '1 minute ago' -print As an extra bonus, the program is ANSI-fied - the original version relies on some obscure features of K&R C. (This PR was submitted in 1999, and the submittor has kept the patch updated ever since, hats off for him guys, and how about you close a PR ??) PR: 9374 Submitted by: Martin Birgmeier <Martin.Birgmeier@aon.at>
* Don't attempt to parse %c, use nl_langinfo insteadache2001-03-211-13/+16
|
* MAXPATHLEN already accounts for the trailing NUL, so no need to add one in.imp2001-03-011-1/+1
| | | | | In addition, since we pass readlink MAXPATHLEN - 1, we would have never have used that extra byte anyway.
* mdoc(7) police: restore correct order of references in the SEE ALSO.ru2001-02-241-1/+1
|
* Implement the following options and primaries:knu2001-02-237-7/+219
| | | | | | | | | | | | | | | | | | | | | | | | | | | -E Interpret regular expressions followed by -regex and -iregex op- tions as extended (modern) regular expressions rather than basic regular expressions (BRE's). The re_format(7) manual page fully describes both formats. -iname pattern Like -name, but the match is case insensitive. -ipath pattern Like -path, but the match is case insensitive. -regex pattern True if the whole path of the file matches pattern using regular expression. To match a file named ``./foo/xyzzy'', you can use the regular expression ``.*/[xyz]*'' or ``.*/foo/.*'', but not ``xyzzy'' or ``/foo/''. -iregex pattern Like -regex, but the match is case insensitive. These are meant to be compatible with other find(1) implementations such as GNU's or NetBSD's except regexp library differences. Reviewed by: sobomax, dcs, and some other people on -current
* mdoc(7) police: split punctuation characters + misc fixes.ru2001-02-011-2/+1
|
* Add the -empty flag, from OpenBSD. It returns true if the directorypeter2001-01-235-2/+49
| | | | | | | | | | | is empty. There doesn't appear to be another easy way to do this. mobile# mkdir foo mobile# mkdir foo/bar mobile# mkdir bar mobile# find . -empty ./foo/bar ./bar
* Prepare for mdoc(7)NG.ru2001-01-161-1/+1
|
* Prepare for mdoc(7)NG.ru2000-12-191-4/+11
|
* mdoc(7) police: use the new features of the Nm macro.ru2000-11-201-20/+20
|
* "minute(s) period(s)" --> "minute(s)"mph2000-11-171-6/+6
|
* Make passing unknown fstypes to -fstype result in a warning instead ofeivind2000-07-281-2/+16
| | | | | | an error. As it was, which find command lines that would work (be accepted at all) was dependent on the presently running kernel, making script writing and porting hard.
* Switch over to using the new fflagstostr and strtofflags library calls.joe2000-06-172-5/+2
|
* Make find -Wall -Wredundant-decls clean.roberto2000-06-141-4/+0
| | | | Submitted by: nrahlstr
* This patch adds the -mindepth and -maxdepth options to find(1), whichroberto2000-06-1211-6/+115
| | | | | | | | | | | | behave as in GNU find (and of course as described in the manual page diff included). I think these options would be useful for some people. Some missing $FreeBSD$ tags are also added. The patch was slightly modified (send-pr mangling of TABS). PR: bin/18941 Submitted by: Ben Smithurst <ben@scientia.demon.co.uk>
* The find -perm option currently supports an exact match,roberto2000-06-123-1/+9
| | | | | | | | | | or if the mode is preceded by a '-', it checks for a match in at least the bits specified on the command line. It is often desirable to find things with any execute or setuid or setgid bits set. PR: bin/10169 Submitted by: Monte Mitzelfelt <monte@gonefishing.org>
* Fix errors in .Xr usage.nik2000-03-011-3/+3
| | | | | PR: docs/17057 Submitted by: Submitted by: Udo Erdelhoff <ue@nathan.ruhr.de>
* Revert part of the last commit, remove {g|s}etflags from the libcjoe2000-02-052-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | interface, and statically link them to the programs using them. These functions, upon reflection and discussion, are too generically named for a library interface with such specific functionality. Also the api that they use, whilst ok for private use, isn't good enough for a libc function. Additionally there were complications with the build/install-world process. It depends heavily upon xinstall, which got broken by the change in api, and caused bootstrap problems and general mayhem. There is work in progress to address future problems that may be caused by changes in install-chain tools, and better names for {g|s}etflags can be derived when some future program requires them. For now the code has been left in src/lib/libc/gen (it started off in src/bin/ls). It's important to provide library functions for manipulating file flag strings if we ever want this interface to be adopted outside of the source tree, but now isn't necessarily the right moment with 4.0-release just around the corner. Approved: jkh
* Historically file flags (schg, uschg, etc) have been converted fromjoe2000-01-272-5/+1
| | | | | | | | | | | | | | | | | string to u_long and back using two functions, flags_to_string and string_to_flags, which co-existed with 'ls'. As time has progressed more and more other tools have used these private functions to manipulate the file flags. Recently I moved these functions from /usr/src/bin/ls to libutil, but after some discussion with bde it's been decided that they really ought to go in libc. There are two already existing libc functions for manipulating file modes: setmode and getmode. In keeping with these flags_to_string has been renamed getflags and string_to_flags to setflags. The manual page could probably be improved upon ;)
* Added missing DPADD's. Removed unrequired SRCS's.joe2000-01-011-0/+1
| | | | Obtained from: bde
OpenPOWER on IntegriCloud