summaryrefslogtreecommitdiffstats
path: root/usr.bin/find
Commit message (Collapse)AuthorAgeFilesLines
* mdoc(7) police: markup polishing.ru2002-11-261-17/+5
| | | | Approved by: re
* Make the threatened fts(3) ABI fix. FTSENT now avoids the use of the structwollman2002-09-211-2/+2
| | | | | | | | | | | | | | | | hack, thereby allowing future extensions to the structure (e.g., for extended attributes) without rebreaking the ABI. FTSENT now contains a pointer to the parent stream, which fts_compar() can then take advantage of, avoiding the undefined behavior previously warned about. As a consequence of this change, the prototype of the comparison function passed to fts_open() has changed to reflect the required amount of constness for its use. All callers in the tree are updated to use the correct prototype. Comparison functions can now make use of the new parent pointer to access the new stream-specific private data pointer, which is intended to assist creation of reentrant library routines which use fts(3) internally. Not objected to in spirit by: -arch
* Do not repeat the name of the flag in its descriptioncharnier2002-08-271-24/+8
|
* Add a unary -not operator ala -false and !, for sake of completeness.jmallett2002-08-192-0/+2
| | | | | Obtained from: OpenDarwin MFC after: 1 week
* Oops, add -false to the operators list in the manual page for find(1), as addedjmallett2002-08-151-0/+1
| | | | | | in revision 1.17 of option.c. MFC after: 1 week
* Add support for -false instead of '!' cause it can be hard to use that injmallett2002-08-151-0/+1
| | | | | | | some shells, etc., and also for GNU compatability (lack of this broke the Mono CVS build for me). MFC after: 1 week
* - Introduce a new struct xvfsconf, the userland version of struct vfsconf.mux2002-08-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | - Make getvfsbyname() take a struct xvfsconf *. - Convert several consumers of getvfsbyname() to use struct xvfsconf. - Correct the getvfsbyname.3 manpage. - Create a new vfs.conflist sysctl to dump all the struct xvfsconf in the kernel, and rewrite getvfsbyname() to use this instead of the weird existing API. - Convert some {set,get,end}vfsent() consumers to use the new vfs.conflist sysctl. - Convert a vfsload() call in nfsiod.c to kldload() and remove the useless vfsisloadable() and endvfsent() calls. - Add a warning printf() in vfs_sysctl() to tell people they are using an old userland. After these changes, it's possible to modify struct vfsconf without breaking the binary compatibility. Please note that these changes don't break this compatibility either. When bp will have updated mount_smbfs(8) with the patch I sent him, there will be no more consumers of the {set,get,end}vfsent(), vfsisloadable() and vfsload() API, and I will promptly delete it.
* - Use MAXLOGNAME - 1 rather than UT_NAMESIZE.robert2002-07-221-3/+2
| | | | - Remove the inclusion of <utmp.h>.
* Account for space used by environment variables in a similar way totjr2002-07-131-8/+12
| | | | xargs(1) when handling -exec ... {} + constructions.
* Indicate that the semicolon that terminates argument lists should be intjr2002-06-261-2/+8
| | | | its own argument for -ok and -okdir.
* Make it more obvious that the semicolon that terminates -exec and -execdirtjr2002-06-261-2/+8
| | | | | argument lists must be in an argument by itself, not on the end of the previous one.
* Support the SysV-style -exec utility args.. {} + function, required bytjr2002-06-024-8/+95
| | | | SUSv3. This is similar to find foo -print0 | xargs -0 utility args.
* mdoc(7) police: markup nits.ru2002-05-291-1/+1
|
* Clean up malloc(3)'s argument. Remove casts which do nothing when we'rejmallett2002-05-171-9/+9
| | | | | | | using sizeof() anyway. Use slightly more consistent (per-file) error reporting for malloc(3) returning NULL. If "malloc failed" was being printed, don't use err(3). If a NULL format is being used, use err(3). In one case errx(3) was being used with strerror(3), so just use err(3).
* 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
|
OpenPOWER on IntegriCloud