#
51b0534f |
| 02-Apr-2002 |
Juli Mallett <jmallett@FreeBSD.org> |
Fix find -exec with no command specified (i.e.: find . -exec ';')
PR: bin/36521 Submitted by: Simon 'corecode' Schubert <corecode@corecode.ath.cx> Reviewed by: mike MFC after: 3 days
|
#
3077469e |
| 02-Apr-2002 |
David E. O'Brien <obrien@FreeBSD.org> |
Fix SCM IDs.
|
#
9725a7b9 |
| 26-Mar-2002 |
Philippe Charnier <charnier@FreeBSD.org> |
spelling
|
#
2a66bf16 |
| 21-Mar-2002 |
Mark Murray <markm@FreeBSD.org> |
Restructure for own parsedate (replacement for get_date from CVS).
Fix up parsedate.y for WARNS=4.
Reviewd by: bde (except for parsedate.y diffs)
|
#
ecca1f1c |
| 20-Mar-2002 |
Mark Murray <markm@FreeBSD.org> |
Remove __P().
|
#
e98080b1 |
| 27-Feb-2002 |
David Malone <dwmalone@FreeBSD.org> |
1) Remove -Wall from Makefile. 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.
|
Revision tags: release/4.5.0_cvs, release/4.4.0_cvs |
|
#
631a8765 |
| 14-Sep-2001 |
Ruslan Ermilov <ru@FreeBSD.org> |
Simplify f_Xtime().
|
#
adff4fca |
| 14-Sep-2001 |
Ruslan Ermilov <ru@FreeBSD.org> |
Bloat find(1) even more, and introduce the concept 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
|
#
7fd5ee41 |
| 04-Sep-2001 |
Ruslan Ermilov <ru@FreeBSD.org> |
The implementation of -flags was broken and did not match the (poorly) documented behavior. Only a certain set of file flags were recognized, and "no" flags did not match files that have correspondi
The implementation of -flags was broken and did not match the (poorly) 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
show more ...
|
#
c0ff9709 |
| 30-Aug-2001 |
Ruslan Ermilov <ru@FreeBSD.org> |
Restore the `-perm +mode' feature.
Broken in the "close a PR" race, in revision 1.30. Note that the patch in the PR did not have this bug!
|
#
f0cb9537 |
| 24-Jul-2001 |
David E. O'Brien <obrien@FreeBSD.org> |
Remove emalloc and expand to the malloc + error checking it was, where used.
|
#
ea92232a |
| 03-May-2001 |
Poul-Henning Kamp <phk@FreeBSD.org> |
They add the following commands: -anewer -cnewer -mnewer -okdir -newer[acm][acmt]
With it, you can form queries like
find . -newerct '1 minute ago' -print
As an extra bonus,
They add the following commands: -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>
show more ...
|
Revision tags: release/4.3.0_cvs, release/4.3.0 |
|
#
7c1d4b3a |
| 23-Feb-2001 |
Akinori MUSHA <knu@FreeBSD.org> |
Implement the following options and primaries:
-E Interpret regular expressions followed by -regex and -iregex op- tions as extended (modern) regular expressions rather than b
Implement the following options and primaries:
-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
show more ...
|
#
ed1a4621 |
| 23-Jan-2001 |
Peter Wemm <peter@FreeBSD.org> |
Add the -empty flag, from OpenBSD. It returns true if the directory is empty. There doesn't appear to be another easy way to do this.
mobile# mkdir foo mobile# mkdir foo/bar mobile# mkdir bar mobi
Add the -empty flag, from OpenBSD. It returns true if the directory 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
show more ...
|
Revision tags: release/4.2.0, release/4.1.1_cvs |
|
#
1e2f8412 |
| 28-Jul-2000 |
Eivind Eklund <eivind@FreeBSD.org> |
Make passing unknown fstypes to -fstype result in a warning instead of an error. As it was, which find command lines that would work (be accepted at all) was dependent on the presently running kerne
Make passing unknown fstypes to -fstype result in a warning instead of 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.
show more ...
|
Revision tags: release/4.1.0, release/3.5.0_cvs |
|
#
141d77b8 |
| 17-Jun-2000 |
Josef Karthauser <joe@FreeBSD.org> |
Switch over to using the new fflagstostr and strtofflags library calls.
|
#
c4b8db00 |
| 14-Jun-2000 |
Ollivier Robert <roberto@FreeBSD.org> |
Make find -Wall -Wredundant-decls clean.
Submitted by: nrahlstr
|
#
c76bc8f3 |
| 12-Jun-2000 |
Ollivier Robert <roberto@FreeBSD.org> |
This patch adds the -mindepth and -maxdepth options to find(1), which behave as in GNU find (and of course as described in the manual page diff included). I think these options would be usef
This patch adds the -mindepth and -maxdepth options to find(1), which 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>
show more ...
|
#
9d2796c3 |
| 12-Jun-2000 |
Ollivier Robert <roberto@FreeBSD.org> |
The find -perm option currently supports an exact match, 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
The find -perm option currently supports an exact match, 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>
show more ...
|
Revision tags: release/4.0.0_cvs |
|
#
418d67b0 |
| 05-Feb-2000 |
Josef Karthauser <joe@FreeBSD.org> |
Revert part of the last commit, remove {g|s}etflags from the libc interface, and statically link them to the programs using them. These functions, upon reflection and discussion, are too generically
Revert part of the last commit, remove {g|s}etflags from the libc 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
show more ...
|
#
18c0eedd |
| 27-Jan-2000 |
Josef Karthauser <joe@FreeBSD.org> |
Historically file flags (schg, uschg, etc) have been converted from string to u_long and back using two functions, flags_to_string and string_to_flags, which co-existed with 'ls'. As time has progre
Historically file flags (schg, uschg, etc) have been converted from 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 ;)
show more ...
|
Revision tags: release/3.4.0_cvs |
|
#
567664c4 |
| 19-Dec-1999 |
Ollivier Robert <roberto@FreeBSD.org> |
Second part of bin/3648: add -flags to search for specific flags. I added $FreeBSD$ whicle I was here. The patch wasn't usable anymore due to its age so I adapted it.
PR: bin/3648 Submitted by: Mar
Second part of bin/3648: add -flags to search for specific flags. I added $FreeBSD$ whicle I was here. The patch wasn't usable anymore due to its age so I adapted it.
PR: bin/3648 Submitted by: Martin Birgmeier <mbirg@austria.ds.philips.com>
show more ...
|
Revision tags: release/3.3.0_cvs |
|
#
389017e5 |
| 06-Sep-1999 |
Bill Fumerola <billf@FreeBSD.org> |
-Wall: remove unused variable, initialize variable to avoid gcc stupidity.
|
Revision tags: release/3.2.0, release/3.1.0, release/3.0.0, release/2.2.8 |
|
#
83268d4d |
| 16-Dec-1998 |
Warner Losh <imp@FreeBSD.org> |
Return memory from setmode.
Obtained from: OpenBSD
|
#
1fd98d7d |
| 13-Oct-1998 |
Dag-Erling Smørgrav <des@FreeBSD.org> |
Calls one or more of malloc(), warn(), err(), syslog(), execlp() or execvp() in the child branch of a vfork(). Changed to use fork() instead.
Some of these (mv, find, apply, xargs) might benefit gre
Calls one or more of malloc(), warn(), err(), syslog(), execlp() or execvp() in the child branch of a vfork(). Changed to use fork() instead.
Some of these (mv, find, apply, xargs) might benefit greatly from being rewritten to use vfork() properly.
PR: Loosely related to bin/8252 Approved by: jkh and bde
show more ...
|