https://RustRocket.rs -- Cloud Monk Losang Jinpa, Ph.D., MCSE / MCT, https://Rustaceans.rs, Full Stack Cloud Native Rust DevOps Engineer - Rocket Framework Rust Microservices on Kubernetes-AWS-Azure-GCP

• author = Ken Thompson, Dennis Ritchie (AT&T Bell Laboratories)
• developer = Various open-source and commercial developers
• released = 1971 November 3]]
• operating system = Unix, Unix-like, V, Plan 9, Inferno, KolibriOS, IBM i
• platform = Cross-platform
• genre = Command
• license = coreutils: GPLv3+

In computing,

rm

(short for remove) is a basic command on Unix and Unix-like operating systems used to remove objects such as computer files, directories and symbolic links from file systems and also special files such as device nodes, pipes and sockets, similar to the

[[Del (command)|del]]

command in MS-DOS, OS/2, and Microsoft Windows. The command is also available in the EFI shell.<ref name=“EFI-Shells-and-Scripting”>

</ref>

The

rm

command removes references to objects from the filesystem using the unlink system call, where those objects might have had multiple references (for example, a file with two different names), and the objects themselves are discarded only when all references have been removed and no programs still have open handles to the objects.

This allows for scenarios where a program can open a file, immediately remove it from the filesystem, and then use it for temporary space, knowing that the file's space will be reclaimed after the program exits, even if it exits by crashing.

The command generally does not destroy file data, since its purpose is really merely to 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.

rm

is generally only seen on UNIX-derived operating systems, which typically do not provide for recovery of deleted files through a mechanism like the recycle bin,¹⁾ hence the tendency for users to enclose

rm

in some kind of wrapper to limit accidental file deletion.

There are undelete utilities that will attempt to reconstruct the index and can bring the file back if the parts were not reused.

On some old versions of Unix, the

rm

command would delete directories if they were empty.<ref>

</ref> This behaviour can still be obtained in some versions of

rm

with the

-d

flag, e.g., the BSDs (such as FreeBSD,<ref>

</ref> NetBSD,<ref>

</ref> OpenBSD<ref>

</ref> 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.<ref>

</ref> This version also provides

-d

option, to help with compatibility.<ref>

</ref> 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”.<ref name=“reader”>

</ref>

KolibriOS includes an implementation of the

command.<ref>

</ref>

The

command has also been ported to the IBM i operating system.<ref>

</ref>

rm

deletes the file specified after options are added. Users can use a full path or a relative file path to specify the files to delete.

rm

doesn't delete a directory by default.<ref>

</ref>

<syntaxhighlight lang=“csh”> % rm foo </syntaxhighlight>deletes the file “foo” in the directory the user is currently in.

rm

, like other commands, uses options to specify how it will behave:

• -r

  , “recursive,” which removes directories, removing the contents recursively beforehand (so as not to leave files without a directory to reside in).

• -i

  , “interactive” which asks for every deletion to be confirmed.

• -f

  , “force,” which ignores non-existent files and overrides any confirmation prompts (effectively canceling

  -i

  ), although it will not remove files from a directory if the directory is write-protected.

• -v

  , “verbose,” which prints what

  rm

  is doing onto the terminal

• -d

  , “directory,” which deletes an empty directory, and only works if the specified directory is empty.

• --one-file-system

  , only removes files on the same file system as the argument, and will 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.<ref name=“Linux/UNIX: Delete a file”>

</ref> 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:

<syntaxhighlight lang=“bash”>

xargs rm < filelist

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

<syntaxhighlight lang=“bash”>

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

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.)<ref>

</ref>

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.<ref>

</ref>

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.

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.<ref>

</ref> Shortly after, the same functionality was introduced into FreeBSD version of

rm

utility.<ref>

</ref> GNU

rm

refuses to execute

rm -rf /

if the

--preserve-root

option is given,<ref>

</ref> 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.

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:

<syntaxhighlight lang=“bash”> alias rm=“rm -i” rm () { /bin/rm -i “$@” ; } </syntaxhighlight>

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.

Users have even been seen going as far as “

yes | rm ''files''

”, which automatically inserts “y” for each file.

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:

<syntaxhighlight lang=“bash”> 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
 }

It's 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”<ref>

</ref> or “trash”.<ref>

</ref>

GNU Core Utilities implementation used in multiple Linux distributions will be limited in command line arguments bytes number of pages that are allocated within the kernel for command-line arguments before kernel 2.6.23 Released on 9 October 2007<ref>

</ref> <ref>

</ref>were defined at kernel compile time at variable

MAX_ARG_PAGES

in

include/linux/binfmts.h

file but new kernels limits the maximum argument length to 25% of the maximum stack limit (ulimit -s). Error:

/bin/rm: Argument list too long.

will prompt if command-line argument limit is exceed<ref>

</ref>

• srm (Unix): secure remove file in Unix
• unlink(): the underlying system call called by this user space program for its main functionality
• del (command)
• deltree
• dsw (command) - an obsolete Unix command for deleting difficult files

File deletion Standard Unix programs Unix SUS2008 utilities Plan 9 commands Inferno (operating system) commands