summaryrefslogtreecommitdiffstats
path: root/bin/rm/rm.1
Commit message (Collapse)AuthorAgeFilesLines
* Protecting against rm -rf / is now POSIXLY_CORRECT per posix 1003.1bapt2015-11-071-2/+2
| | | | | | | | | edition 2013. No need anymore to disable the protection if one set the POXILY_CORRECT environment variable. Reviewed by: imp MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D4092
* mdoc: remove superfluous paragraph macros.joel2014-06-151-1/+0
|
* Add -x option to avoid crossing mount points when removing a hierarchy.eadler2013-04-261-2/+4
| | | | | | Discussed on: -hackers Inspired by: DragonflyBSD MFC After: 1 week
* Add a few examples.joel2013-03-151-1/+14
| | | | Obtained from: OpenBSD
* Fix typo and grammar nituqs2010-10-311-2/+2
| | | | | Submitted by: arundel MFC after: 7 days (or when the bikeshed has abated)
* Elaborate some more on the non-security implications of using -Puqs2010-10-311-6/+15
| | | | | Submitted by: delphij Discussion at: svn-src-all
* Language cleanup.des2010-10-271-3/+3
|
* rm(1): clarify that -P works only when blocks are updated in-placeuqs2010-10-081-4/+4
| | | | Suggested by: pjd, ivoras, arundel
* Clarify the combination effect of -P and -f to make it clear.delphij2010-10-041-3/+7
| | | | | Submitted by: arundel MFC after: 2 weeks
* Give a hint to the reader as to what the "whiteout" actually means.ru2006-12-261-2/+3
|
* Fix markup, add the EXIT STATUS section.ru2006-12-261-7/+12
|
* Correct a security issue introduced in previous commit:delphij2006-10-311-1/+9
| | | | | | | | | | | | | | | | | | | | 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
* Be more reasonable when overwrite mode is specified while theredelphij2006-10-301-1/+3
| | | | | | | | | 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
* -mdoc sweep.ru2005-11-171-1/+1
|
* Give .Dd a tummy rub, forgotten on my last commit.dougb2005-09-301-1/+1
|
* Handle the case where the -P flag is specified for a read-only filedougb2005-09-291-0/+4
| | | | | | | | | | | | | | 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@
* Sync program's usage() with manpage's SYNOPSIS.ru2005-02-091-1/+2
|
* Add the new standard EXIT STATUS section where appropriate.ru2005-01-161-16/+16
| | | | Sort standard sections in the (documented) preferred order.
* /*- or .\"- or #- to begin license clauses.imp2005-01-101-0/+1
|
* Correct a typo and make the documentation more mdoc(7) complaint.delphij2004-11-011-3/+3
| | | | | Pointed out by: dd Approved by: murray (mentor)
* Add -I, an option that asks for confirmation once if recursivelydelphij2004-10-281-2/+8
| | | | | | | | | | | | | | | | | | | | | 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
* Markup fixes.des2004-10-041-4/+4
| | | | Pointed out by: ru
* Find out how flame-proof my underwear really is.des2004-10-041-1/+2
|
* Mechanically kill hard sentence breaks.ru2004-07-021-2/+4
|
* Remove clause 3 from the UCB licenses.markm2004-04-061-4/+0
| | | | OK'ed by: imp, core
* Cross ref chflags(1).trhodes2003-02-041-0/+1
| | | | Suggested by: Craig Carey <research@ijs.co.nz) on -doc.
* s/filesystem/file system/ as discussed on -developerstrhodes2002-08-211-2/+2
|
* Consistancy check s/file system/filesystem/trhodes2002-05-161-2/+2
| | | | Reviewed by: brian
* Update STANDARDS section on rm(1) to reflect current conformance.dwhite2002-03-021-16/+2
| | | | PR: 35471
* Remove whitespace at EOL.dd2001-07-151-5/+5
|
* mdoc(7) police: use the default ``file ...'' feature of the .Ar macro.ru2001-02-131-1/+1
|
* Prepare for mdoc(7)NG.ru2000-12-151-1/+1
|
* mdoc(7) police: use the new features of the Nm macro.ru2000-11-201-2/+2
|
* Fix cut'n'paste niggles in previous commit.sheldonh1999-12-211-6/+7
|
* Add link(1) and unlink(1) as special cases of ln(1) and rm(1)sheldonh1999-12-201-1/+18
| | | | | | | | | | | | 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>
* brucify, `v' before `W', mention -v is non-standard in manpage andmharo1999-09-041-3/+6
| | | | | | make code slightly easier to read Reviewed by: obrien
* add verbose flagmharo1999-08-291-1/+3
| | | | | | exit(1) --> exit(EX_USAGE) Reviewed by: obrien
* $Id$ -> $FreeBSD$peter1999-08-271-1/+1
|
* Use .Dq instead of ``'' in manpagekris1999-05-281-2/+5
| | | | | | | Use optimal blocksize for rm -P, instead of always using 8192-byte blocks to overwrite the file. Obtained from: OpenBSD
* Fix synopsis to match 1003.2. Add text describing the way in whichwollman1999-01-281-10/+19
| | | | | our implementation does not meet 1003.2 (rather than the now outdated ``is expected to comply' language).
* .Nm rm -> .Nm.charnier1998-05-181-8/+8
|
* Remove remaining Lite1 stuff from the man page and uphold thesteve1997-08-071-7/+1
| | | | | | | 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>
* Enable whiteout code since we now have the lite2 support for them.dfr1997-04-291-2/+2
|
* Provide examples of how to remove file names that begin withmpp1997-04-091-1/+8
| | | | | | | | a dash in non-getopt implementations. E.g.: rm /home/mpp/-filename rm ./-filename Requested by: bde
* Improve the wording in the NOTES section. Closes PR# 3223.mpp1997-04-081-13/+12
|
* Revert $FreeBSD$ to $Id$peter1997-02-221-1/+1
|
* Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-141-1/+1
| | | | | | | | 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.
* Merge Lite2 mods, and -Wall cleaning. Unimplemented undelete(2)steve1996-12-141-4/+15
| | | | | cruft is protected by a #ifdef (BSD4_4_LITE) that should be removed when this is supported by the kernel.
* [HISTORY] command appeared in Version 1 AT&T UNIXwosch1996-08-291-1/+6
| | | | Obtained from: A Quarter Century of UNIX, Peter H. Salus, page 41
* fix usage stringwosch1996-03-071-1/+17
| | | | | | respond `Y' is equal to `y' Add a note how to delete file name with beginning `-'
OpenPOWER on IntegriCloud