Rm (Unix)

rm, short for remove, is a shell command on Unix and Unix-like operating systems used to remove files (which includes special files such as directories) from the file system.

rm

The rm command
Original author(s)	Ken Thompson, Dennis Ritchie (AT&T Bell Laboratories)
Developer(s)	Various open-source and commercial developers
Initial release	November 3, 1971; 53 years ago (1971-11-03)
Written in	C
Operating system	Unix, Unix-like, V, Plan 9, Inferno, KolibriOS, IBM i
Platform	Cross-platform
Type	Command
License	coreutils: GPLv3+ Plan 9: MIT License

The rm command may not actually delete a file since it only removes a reference to a file via the unlink() system call. A file can have multiple references (for example, a file with two names). The file will remain on the file system if there are other references to it after the specified links are removed.

The command generally does not destroy (overwrite/clear) file data, since its purpose to merely unlink() references, and the filesystem space freed may still contain leftover data from the removed file. This can be a security concern in some cases, and hardened versions sometimes provide for wiping out the data as the last link is being cut, and programs such as shred and srm are available which specifically provide data wiping capability.

Since rm does not provide a fallback to recover a file such as a recycle bin, its use involves the risk of accidentally losing information.^[1] Users tend to wrap calls to rm in safety mechanisms to limit accidental deletion. There are undelete utilities that attempts to reconstruct the index and can bring the file back if its storage was not reused.

The command is available in Windows via UnxUtils,^[2] KolibriOS,^[3] IBM i,^[4] and EFI shell.^[5]

The unlink command provides a similar function. The del command provides a similar capability in MS-DOS, OS/2, and Windows.

History

On some old versions of Unix, the rm command would delete directories if they were empty.^[6] This behaviour can still be obtained in some versions of rm with the -d flag, e.g., the BSDs (such as FreeBSD,^[7] NetBSD,^[8] OpenBSD^[9] and macOS) derived from 4.4BSD-Lite2.

The version of rm bundled in GNU coreutils was written by Paul Rubin, David MacKenzie, Richard Stallman, and Jim Meyering.^[10] This version also provides -d option, to help with compatibility.^[11] The same functionality is provided by the standard rmdir command.

The -i option in Version 7 replaced dsw, or "delete from switches", which debuted in Version 1. Doug McIlroy wrote that dsw "was a desperation tool designed to clean up files with unutterable names".^[12]

Use

rm deletes specified files, but does not delete a directory by default.^[13]rm foo deletes the file "foo" in the directory the user is currently in.

Commonly provided options:

• -r, recursive; remove directories and their content recursively
• -i, interactive; ask user to confirm deleting each file
• -f, force; ignore non-existent files and override any confirmation prompts (effectively canceling -i), does not allow removing files from a write-protected directory
• -v, verbose; log status
• -d, directory; delete any empty directories
• --one-file-system, only remove files on the same file system as the argument; ignore mounted file systems

rm can be overlain by a shell alias (C shell alias, Bourne shell or Bash) function of "rm -i" so as to avoid accidental deletion of files. If a user still wishes to delete a large number of files without confirmation, they can manually cancel out the -i argument by adding the -f option (as the option specified later on the expanded command line "rm -i -f" takes precedence). Unfortunately this approach generates dangerous habits towards the use of wildcarding, leading to its own version of accidental removals.

rm -rf (variously, rm -rf /, rm -rf *, and others) is frequently used in jokes and anecdotes about Unix disasters,^[14] such as the loss of many files during the production of film Toy Story 2 at Pixar.^[15] The rm -rf / variant of the command, if run by a superuser, would cause every file accessible from the present file system to be deleted from the machine.

rm is often used in conjunction with xargs to supply a list of files to delete:

 xargs rm < filelist

Or, to remove all PNG images in all directories below the current one:

 find . -name '*.png' -exec rm {} +

Permissions

Usually, on most filesystems, deleting a file requires write permission on the parent directory (and execute permission, in order to enter the directory in the first place). (Note that, confusingly for beginners, permissions on the file itself are irrelevant. However, GNU rm asks for confirmation if a write-protected file is to be deleted, unless the -f option is used.)^[16]

To delete a directory (with rm -r), one must delete all of its contents recursively. This requires that one must have read and write and execute permission to that directory (if it's not empty) and all non-empty subdirectories recursively (if there are any). The read permissions are needed to list the contents of the directory in order to delete them. This sometimes leads to an odd situation where a non-empty directory cannot be deleted because one doesn't have write permission to it and so cannot delete its contents; but if the same directory were empty, one would be able to delete it.^[17]

If a file resides in a directory with the sticky bit set, then deleting the file requires one to be the owner of the file.

Protection of the filesystem root

Sun Microsystems introduced "rm -rf /" protection in Solaris 10, first released in 2005. Upon executing the command, the system now reports that the removal of / is not allowed.^[18] Shortly after, the same functionality was introduced into FreeBSD version of rm utility.^[19] GNU rm refuses to execute rm -rf / if the --preserve-root option is given,^[20] which has been the default since version 6.4 of GNU Core Utilities was released in 2006. In newer systems, this failsafe is always active, even without the option. To run the command, user must bypass the failsafe by adding the option --no-preserve-root, even if they are the superuser.

User-proofing

Systems administrators, designers, and even users often attempt to defend themselves against accidentally deleting files by creating an alias or function along the lines of:

alias rm="rm -i"
rm () { /bin/rm -i "$@" ; }

This results in rm asking the user to confirm on a file-by-file basis whether it should be deleted, by pressing the Y or N key. Unfortunately, this tends to train users to be careless about the wildcards they hand into their rm commands, as well as encouraging a tendency to alternately pound y and the return key to affirm removes - until just past the one file they needed to keep.^{[citation needed]} Users have even been seen going as far as "yes | rm files", which automatically inserts "y" for each file. ^{[citation needed]}

A compromise that allows users to confirm just once, encourages proper wildcarding, and makes verification of the list easier can be achieved with something like:

if [ -n "$PS1" ] ; then
  rm () 
  { 
      ls -FCsd "$@"
      echo 'remove[ny]? ' | tr -d '\012' ; read
      if [ "_$REPLY" = "_y" ]; then
          /bin/rm -rf "$@"
      else
          echo '(cancelled)'
      fi
  }
fi

It is important to note that this function should not be made into a shell script, which would run a risk of it being found ahead of the system rm in the search path, nor should it be allowed in non-interactive shells where it could break batch jobs. Enclosing the definition in the if [ -n "$PS1" ] ; then ....  ; fi construct protects against the latter.

There exist third-party alternatives which prevent accidental deletion of important files, such as "safe-rm"^[21] or "trash".^[22]

Maximum command line argument limitation

GNU Core Utilities implementation used in multiple Linux distributions have limits on command line arguments. Arguments are nominally limited to 32 times the kernel's allocated page size. Systems with 4KB page size would thus have a argument size limit of 128KB.^[23]

For command-line arguments before kernel 2.6.23, (released on 9 October 2007,) the limits were defined at kernel compile time and can be modified by changing the variable MAX_ARG_PAGES in include/linux/binfmts.h file.^[24][25]

Newer kernels^[which?] limit the maximum argument length to 25% of the maximum stack limit (ulimit -s). Exceeding the limit would prompt the display of the error message /bin/rm: Argument list too long.^{[26][clarification needed]}

See also

• del (command)
• deltree
• dsw (command) – an obsolete Unix command for deleting difficult files
• srm (Unix) – command line utility for secure file deletionPages displaying wikidata descriptions as a fallback