#
fcda3c86 |
| 27-Oct-1997 |
Steve Price <steve@FreeBSD.org> |
Offending statement removed from STANDARDS section. From what I can gather from the Posix spec that I have (which is very old) all one character options are extensions to Posix.
PR: docs/4701
|
Revision tags: release/2.2.5_cvs |
|
#
3f5223f8 |
| 13-Oct-1997 |
Wolfram Schneider <wosch@FreeBSD.org> |
Add the primaries -mmin, -amin, -cmin to find, similar to the GNU find.
|
#
127d7563 |
| 30-Aug-1997 |
Warner Losh <imp@FreeBSD.org> |
Add -execdir which will execute the exec command in the dir of the file in question. This change and the fts changes should be merged into 2.2-stable as soon as they are vetted in -current. This sh
Add -execdir which will execute the exec command in the dir of the file in question. This change and the fts changes should be merged into 2.2-stable as soon as they are vetted in -current. This should allow cleaning of files in /tmp to be reneabled. Obtained from: OpenBSD
show more ...
|
#
3d9a9402 |
| 19-May-1997 |
John Polstra <jdp@FreeBSD.org> |
Mention that "-P" is the default.
|
#
6ad98044 |
| 19-May-1997 |
Eivind Eklund <eivind@FreeBSD.org> |
`it's'' -> `its'' where appropriate and typo fixes in time2posix.3.
Closes PR docs/3612.
Submitted by: Josh Gilliam <soil@quick.net>
|
Revision tags: release/2.2.2_cvs |
|
#
fbe0d04a |
| 03-May-1997 |
Masafumi Max NAKANE <max@FreeBSD.org> |
Minor typo. PR: 3472 Submitted by: Josh Gilliam <soil@quick.net>
|
Revision tags: release/2.2.1_cvs, release/2.2.0 |
|
#
841484cd |
| 11-Mar-1997 |
Peter Wemm <peter@FreeBSD.org> |
Merge from Lite2 - use new getvfsbyname() and related changes. understand whiteouts (FTS_W from fts()).
|
#
0da30e9a |
| 11-Mar-1997 |
Peter Wemm <peter@FreeBSD.org> |
Import some parts of CSRG 4.4BSD-Lite2 usr.bin sources to fix tree build.
|
Revision tags: release/2.1.7_cvs |
|
#
c115df18 |
| 22-Feb-1997 |
Peter Wemm <peter@FreeBSD.org> |
Revert $FreeBSD$ to $Id$
|
Revision tags: release/2.1.6_cvs, release/2.1.6.1 |
|
#
1130b656 |
| 14-Jan-1997 |
Jordan K. Hubbard <jkh@FreeBSD.org> |
Make the long-awaited change from $Id$ to $FreeBSD$
This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so
Make the long-awaited change from $Id$ to $FreeBSD$
This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
show more ...
|
Revision tags: release/2.1.5_cvs |
|
#
abacbbbf |
| 04-Oct-1996 |
Peter Wemm <peter@FreeBSD.org> |
Implement a -delete option to find. The code is extremely paranoid and goes to a fair degree of trouble to enable something like this to be safe: cd /tmp && find . -mtime +7 -delete
It removes bot
Implement a -delete option to find. The code is extremely paranoid and goes to a fair degree of trouble to enable something like this to be safe: cd /tmp && find . -mtime +7 -delete
It removes both files and directories. It does not attempt to remove immutable files (an earlier version I showed to a few people did a chflags and tried to blow away even immutable files. Too risky..)
It is thought to be safe because it forces the fts(3) driven descent to only do "minimal risk" stuff. specifically, -follow is disabled, it does checking to see that it chdir'ed to the directory it thought it was going to, it will *not* pass a pathname with a '/' character in it to unlink(), so it should be totally immune to symlink tree races. If it runs into something "fishy", it bails out rather than blunder ahead.. It's better to do that if somebody is trying to compromise security rather than risk giving them an opportunity. Since the unlink()/rmdir() is being called from within the current working directory during the tree descent, there are no fork/exec overheads or races.
As a side effect of this paranoia, you cannot do a "find /somewhere/dir -delete", as the last argument to rmdir() is "/somewhere/dir", and the checking won't allow it. Besides, one would use rm -rf for that case anyway. :-)
Reviewed by: pst (some time ago, but I've removed the immutable file deletion code that he complained about since he last saw it)
show more ...
|
#
b8923d4c |
| 29-Aug-1996 |
Wolfram Schneider <wosch@FreeBSD.org> |
[HISTORY] command appeared in Version 1 AT&T UNIX Obtained from: A Quarter Century of UNIX, Peter H. Salus, page 41
|
Revision tags: release/2.1.0_cvs, release/2.0.5_cvs |
|
#
7cd23434 |
| 09-May-1995 |
Garrett Wollman <wollman@FreeBSD.org> |
Add GNU-style `-print0' primary. This exists so that one can safely do `find some-nasty-expression -print0 | perl -n0e unlink' and have all the files actuallly get deleted. (Using `xargs' and `rm'
Add GNU-style `-print0' primary. This exists so that one can safely do `find some-nasty-expression -print0 | perl -n0e unlink' and have all the files actuallly get deleted. (Using `xargs' and `rm' is not safe.)
show more ...
|
Revision tags: release/2.0, release/1.1.5.1_cvs |
|
#
9b50d902 |
| 27-May-1994 |
Rodney W. Grimes <rgrimes@FreeBSD.org> |
BSD 4.4 Lite Usr.bin Sources
|
Revision tags: release/7.3.0_cvs, release/7.3.0 |
|
#
d740b7c7 |
| 17-Mar-2010 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Better way to find out available file system types is to use lsvfs(1). Using 'sysctl vfs' is not only ugly, but is also not reliable - not all file system types create entries in vfs sysctl tree.
Re
Better way to find out available file system types is to use lsvfs(1). Using 'sysctl vfs' is not only ugly, but is also not reliable - not all file system types create entries in vfs sysctl tree.
Reviewed by: imp MFC after: 1 week
show more ...
|
#
1ee774f6 |
| 02-Oct-2009 |
Oleksandr Tymoshenko <gonzo@FreeBSD.org> |
- MFC
|
#
a05cb852 |
| 20-Sep-2009 |
Jilles Tjoelker <jilles@FreeBSD.org> |
Update find(1) man page for -L/-delete interaction.
It is a bit unfortunate that the example to delete broken symlinks now uses rm(1), but allowing this with -delete would require fixing fts(3) to n
Update find(1) man page for -L/-delete interaction.
It is a bit unfortunate that the example to delete broken symlinks now uses rm(1), but allowing this with -delete would require fixing fts(3) to not imply FTS_NOCHDIR if FTS_LOGICAL is given (or hacks in the -delete option).
PR: bin/90687 MFC after: 2 weeks
show more ...
|
Revision tags: release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0 |
|
#
dfab7fb1 |
| 03-Mar-2008 |
Ruslan Ermilov <ru@FreeBSD.org> |
Fix SYNOPSIS and usage().
|
#
b390c311 |
| 24-Feb-2008 |
Ceri Davies <ceri@FreeBSD.org> |
Bump .Dd for revisions 1.83 and 1.84.
|
#
a66a6a2a |
| 24-Feb-2008 |
Warner Losh <imp@FreeBSD.org> |
Tag -ilname and -lname as GNU extensions. Correct their descriptions to indicate that it is the contents of the symbolic link that are matched.
|
Revision tags: release/7.0.0_cvs, release/7.0.0 |
|
#
46b993ff |
| 23-Feb-2008 |
Warner Losh <imp@FreeBSD.org> |
Implement a number of primaries present in GNU find, but not present in our find.
The following are nops because they aren't relevant to our find: -ignore_readdir_race -noignore_readdir_race -nol
Implement a number of primaries present in GNU find, but not present in our find.
The following are nops because they aren't relevant to our find: -ignore_readdir_race -noignore_readdir_race -noleaf The following aliaes were created: -gid -> -group [2] -uid -> -user [2] -wholename -> -path -iwholename -> ipath -mount -> -xdev -d -> -depth [1] The following new primaries were created: -lname like -name, but matches symbolic links only) -ilname like -lname but case insensitive -quit exit(0) -samefile returns true for hard links to the specified file -true Always true I changed one primary to match GNU find since I think our use of it violates POLA -false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above. This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the normal range thing that. GNU find -user and -uid also take a numberic arg, but don't do the range processing. find(1) does both for -user and -group, so making -uid and -gid aliases is compatible for all non-error cases used in GNU find. While not perfect emulation, this seems a reasonable thing for us.
show more ...
|
Revision tags: release/6.3.0_cvs, release/6.3.0 |
|
#
fbccd9db |
| 28-Feb-2007 |
Ruslan Ermilov <ru@FreeBSD.org> |
Check in some insignificant fixes obtained as a result of the translation work.
|
Revision tags: release/6.2.0_cvs, release/6.2.0 |
|
#
3b0fbd31 |
| 13-Dec-2006 |
Ruslan Ermilov <ru@FreeBSD.org> |
Fix the description of the -Btime primary.
Noticed by: Vadim Goncharov <vadimnuclight tpu.ru>
|
#
659a728e |
| 08-Oct-2006 |
Ceri Davies <ceri@FreeBSD.org> |
Update the list of POSIX extensions.
PR: docs/103859 Submitted by: shaun MFC after: 1 week
|
#
cb29445a |
| 29-Sep-2006 |
Ruslan Ermilov <ru@FreeBSD.org> |
Markup fixes.
|