summaryrefslogtreecommitdiffstats
path: root/usr.bin/find
Commit message (Collapse)AuthorAgeFilesLines
* Use rpmatch() instead of checking for responses that begin with 'y'tjr2005-04-022-18/+24
| | | | | in queryuser(). This allows users to respond to -ok and -okdir prompts with any affirmative reply defined by their current locale.
* - Make find(1) WARNS?= 6 cleanssouhlal2005-01-252-3/+3
| | | | | | - Bump to WARNS?= 6 Approved by: stefanf, grehan (mentor)
* Scheduled mdoc(7) sweep.ru2005-01-111-1/+1
|
* Change the 'no terminating ";"' error message to 'no terminating ";" or "+"'tjr2004-07-291-1/+1
| | | | since + is also a valid way to terminate -exec.
* Remove partial support for building this on NetBSD.tjr2004-07-293-10/+0
|
* Now that fnmatch() supports multibyte characters, find does too; removetjr2004-07-291-5/+1
| | | | entry from BUGS section that said otherwise.
* Start new sentence on new line.cperciva2004-07-271-1/+2
| | | | Pointed out by: simon
* Add a BUGS entry pointing out that -mindepth and -maxdepth are globalcperciva2004-07-271-0/+7
| | | | | | options even though they look like primaries. (This is already documented in the options themselves, but is sufficiently astonishing that I think it deserves a BUGS entry as well.)
* Merge the "multibyte not supported" BUG into the pre-existing BUGScperciva2004-07-271-6/+6
| | | | | | | | | section. Move the HISTORY section to place it before BUGS rather than after BUGS, in order to minimize the chance of this error being reproduced in the future. (Both mdoc(7) and 63% of manual pages have these sections listed in this order.)
* mdoc(7) fixes.ru2004-07-071-2/+2
|
* Document missing multibyte character support in utilities specifiedtjr2004-07-031-1/+5
| | | | by POSIX.
* Re-add half of UCB copyright notice that went missing in 1.20.tjr2004-07-031-0/+1
|
* - introduce a new primary `-depth n', which tests whethereik2004-05-286-28/+91
| | | | | | | | | | | | | | | | | | | | | the depth of the current file relative to the starting point of the traversal is n. The usual +/- modifiers to the argument apply. - while I'm here, fix -maxdepth in the case of a depth-first traversal Print the top ten maintainers of python module ports (works with p5-* too): find /usr/ports -depth 2 \! -name 'py-*' -prune -o \ -depth 3 -name Makefile -execdir make -VMAINTAINER \; \ | sort | uniq -c | sort -nr | head PR: 66667 Reviewed by: ru, joerg Approved by: joerg MFC after: 2 weeks
* Bumped document date.ru2004-05-191-16/+16
| | | | | Fixed a bunch of hyphen misspellings. Fixed one warning.
* snafu, exchanged the descriptions of -maxdepth and -mindepth.eik2004-05-161-5/+5
| | | | Noticed by: ru
* -maxdepth and -mindepth are global variableseik2004-05-141-3/+16
| | | | | | PR: 66613 Approved by: ru MFC after: 3 days
* Clarify and correct some compatibility notes.des2004-04-211-9/+22
| | | | PR: 65822
* Add -acl and a small blurb about it to the options list.trhodes2004-04-071-1/+8
| | | | Update date.
* Give find(1) the option -acl to locate files with extendedbmilekic2004-04-033-0/+54
| | | | | | | | | | | ACLs. This is similar to what ls(1) can do. It is handy to have it so that it can be used in conjunction with "-exec setfacl {} \;" (to find(1)), among others. This is the submitter's patch, but slightly modified. PR: bin/65016 Submitted by: Christian S.J. Peron <maneo@bsdpro.com>
* Update the find manual page:trhodes2004-02-271-1/+14
| | | | | | | | | | 1: Document -follow under COMPATIBILITY. 2: Update an example to be a little more 'safe'. 3: Use '/' in place of '.' for an example; similar to other manual pages. PR: 40196 (1), 39532 (2, 3) Submitted by: Marc Silver <marcs@draenor.org> (2 and 3) Discussed with: des (1)
* Typo.des2004-02-231-1/+1
|
* Use a larger field for the size in blocks; the current width (4 digits)des2004-01-201-1/+1
| | | | is only good for 5 MB.
* State that in -exec ... ; the semicolon should be quoted if invoked fromschweikh2003-07-251-0/+4
| | | | | | | | a shell. PR: docs/54667 Submitted by: Patrick Alken <pa59@cornell.edu> MFC after: 3 days
* Fix all WARNS. Checked with "make WARNS=9". Remove unused file.markm2003-06-1410-1184/+133
|
* Correctly alphabetize options[] so we don't stop at -nouser when searchingdes2003-02-181-1/+1
| | | | | | | | for -not. PR: bin/48423 Submitted by: Matsumura Naoki <matsu@jp.FreeBSD.org> MFC after: 3 days
* Uniformly refer to a file system as "file system".ru2002-12-121-5/+5
| | | | Approved by: re
* 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).
OpenPOWER on IntegriCloud