| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Submitted by: arundel
MFC after: 7 days (or when the bikeshed has abated)
|
|
|
|
|
| |
Submitted by: delphij
Discussion at: svn-src-all
|
| |
|
|
|
|
| |
Suggested by: pjd, ivoras, arundel
|
|
|
|
|
| |
Submitted by: arundel
MFC after: 2 weeks
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
instead of removing the file and issue a warning about
the removal, do not do any operation at all in case -P
is specified when the dinode has hard links.
With -f and -P specified together, we assume that the
user wants rm to overwrite the contents of the file
and remove it (destroy the contents of file but leave
its hard links as is).
The reason of doing it this way is that, in case where
a hard link is created by a malicious user (currently
this is permitted even if the user has no access to the
file). Losing the link can potentially mean that the
actual owner would lose control completely to the user
who wants to obtain access in a future day.
Discussed with: Peter Jermey
|
|
|
|
|
|
|
|
|
| |
is hard links. Overwritting when links > 1 would cause data
loss, which is usually undesired.
Inspired by: discussion on -hackers@
Suggested by: elessar at bsdforen de
Obtained from: OpenBSD
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
earlier, and more gracefully. Previously, this combination would be
ignored early in the code where permissions are tested and fail later
with a very unhelpful "permission denied" error.
Instead, test for this flag in the same block that generates the
"override?" messages for read-only files, but instead of trying
to guess what the user has in mind, generate an error and exit.
Update the man page to reflect this new behavior.
Not objected to by: freebsd-hackers@
|
| |
|
|
|
|
| |
Sort standard sections in the (documented) preferred order.
|
| |
|
|
|
|
|
| |
Pointed out by: dd
Approved by: murray (mentor)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
removing directories or if more than 3 files are listed in the
command line.
This feature is intended to provide a safe net but not being too
annoying like having "rm -i" for every deleting operations, and
is generally good for both newbies and power users, preventing
them from being so easily run into ``rm -rf /'', ``rm -rf *''
and so forth.
Originally implemented by Matthew Dillon for DragonFly, plus
some improvements done by various DragonFly contributors.
Approved by: murray (mentor; the original dillon's version)
Discussed with: des
Obtained from: DragonFly's bin/rm/
rm.c rev. 1.4 - 1.8
rm.1 rev. 1.3 - 1.4
MFC After: 1 month
|
|
|
|
| |
Pointed out by: ru
|
| |
|
| |
|
|
|
|
| |
OK'ed by: imp, core
|
|
|
|
| |
Suggested by: Craig Carey <research@ijs.co.nz) on -doc.
|
| |
|
|
|
|
| |
Reviewed by: brian
|
|
|
|
| |
PR: 35471
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
respectively, in accordance with SUSv2.
This differs from the approach taken in NetBSD, but provides
less obscure error messages in at least the EISDIR case and
does not take up additional disk space for new binaries.
PR: 13071
PR: 13074
Requested by: James Howard <howardjp@wam.umd.edu>
|
|
|
|
|
|
| |
make code slightly easier to read
Reviewed by: obrien
|
|
|
|
|
|
| |
exit(1) --> exit(EX_USAGE)
Reviewed by: obrien
|
| |
|
|
|
|
|
|
|
| |
Use optimal blocksize for rm -P, instead of always using 8192-byte blocks
to overwrite the file.
Obtained from: OpenBSD
|
|
|
|
|
| |
our implementation does not meet 1003.2 (rather than the now outdated
``is expected to comply' language).
|
| |
|
|
|
|
|
|
|
| |
precedence in changing sccsid to rcsid as set by Phillippe
Charnier in his previous 100 or so commits.
pointed out by: Bruce Evans <bde@zeta.org.au>
|
| |
|
|
|
|
|
|
|
|
| |
a dash in non-getopt implementations. E.g.:
rm /home/mpp/-filename
rm ./-filename
Requested by: bde
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
cruft is protected by a #ifdef (BSD4_4_LITE) that should be
removed when this is supported by the kernel.
|
|
|
|
| |
Obtained from: A Quarter Century of UNIX, Peter H. Salus, page 41
|
|
|
|
|
|
| |
respond `Y' is equal to `y'
Add a note how to delete file name with beginning `-'
|
| |
|
|
|