|RM(1)||General Commands Manual||RM(1)|
rmutility attempts to remove the non-directory type files specified on the command line. If the permissions of the file do not permit writing, and the standard input device is a terminal, the user is prompted (on the standard error output) for confirmation.
The options are as follows:
-foption overrides any previous
-ioption overrides any previous
-Roption implies the
-doption. If the
-ioption is specified, the user is prompted for confirmation before each directory (and its contents) are processed. If the user does not respond affirmatively, the file hierarchy rooted in that directory is skipped.
rm utility removes symbolic links, not
the files referenced by the links.
It is an error to attempt to remove the root directory or the
files “.” or “..”. It is forbidden to remove the
file “..” merely to avoid the antisocial consequences of
inadvertently doing something like “
rmutility exits 0 if all of the named files or file hierarchies were removed, or if the
-foption was specified and all of the existing files or file hierarchies were removed. If an error occurs,
rmexits with a value >0.
$ rm -rf foobar
Either of these commands will remove the file -f:
$ rm -- -f $ rm ./-f
rmutility is compliant with the IEEE Std 1003.1-2008 (“POSIX.1”) specification.
The flags [
-dPv] are extensions to that
rmcommand appeared in Version 1 AT&T UNIX.
rm utility differs from historical
implementations in that the
-f option only masks
attempts to remove non-existent files instead of masking a large variety of
Also, historical BSD implementations prompted on the standard output, not the standard error output.
The interactive mode used to be a
command, a carryover from the ancient past with an amusing etymology.
-Poption assumes that both the underlying file system and storage medium write in place. This is true for the FFS and MS-DOS file systems and magnetic hard disks, but not true for most flash storage. In addition, only regular files are overwritten; other types of files are not.
|March 31, 2018||OpenBSD-current|