1.\"- 2.\" Copyright (c) 1990, 1993, 1994 3.\" The Regents of the University of California. All rights reserved. 4.\" 5.\" This code is derived from software contributed to Berkeley by 6.\" the Institute of Electrical and Electronics Engineers, Inc. 7.\" 8.\" Redistribution and use in source and binary forms, with or without 9.\" modification, are permitted provided that the following conditions 10.\" are met: 11.\" 1. Redistributions of source code must retain the above copyright 12.\" notice, this list of conditions and the following disclaimer. 13.\" 2. Redistributions in binary form must reproduce the above copyright 14.\" notice, this list of conditions and the following disclaimer in the 15.\" documentation and/or other materials provided with the distribution. 16.\" 4. Neither the name of the University nor the names of its contributors 17.\" may be used to endorse or promote products derived from this software 18.\" without specific prior written permission. 19.\" 20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 23.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" @(#)rm.1 8.5 (Berkeley) 12/5/94 33.\" $FreeBSD$ 34.\" 35.Dd September 29, 2005 36.Dt RM 1 37.Os 38.Sh NAME 39.Nm rm , 40.Nm unlink 41.Nd remove directory entries 42.Sh SYNOPSIS 43.Nm 44.Op Fl f | i 45.Op Fl dIPRrvW 46.Ar 47.Nm unlink 48.Ar file 49.Sh DESCRIPTION 50The 51.Nm 52utility attempts to remove the non-directory type files specified on the 53command line. 54If the permissions of the file do not permit writing, and the standard 55input device is a terminal, the user is prompted (on the standard error 56output) for confirmation. 57.Pp 58The options are as follows: 59.Bl -tag -width Fl 60.It Fl d 61Attempt to remove directories as well as other types of files. 62.It Fl f 63Attempt to remove the files without prompting for confirmation, 64regardless of the file's permissions. 65If the file does not exist, do not display a diagnostic message or modify 66the exit status to reflect an error. 67The 68.Fl f 69option overrides any previous 70.Fl i 71options. 72.It Fl i 73Request confirmation before attempting to remove each file, regardless of 74the file's permissions, or whether or not the standard input device is a 75terminal. 76The 77.Fl i 78option overrides any previous 79.Fl f 80options. 81.It Fl I 82Request confirmation once if more than three files are being removed or if a 83directory is being recursively removed. 84This is a far less intrusive option than 85.Fl i 86yet provides almost the same level of protection against mistakes. 87.It Fl P 88Overwrite regular files before deleting them. 89Files are overwritten three times, first with the byte pattern 0xff, 90then 0x00, and then 0xff again, before they are deleted. 91Specifying this flag for a read only file will cause 92.Nm 93to generate an error message and exit. 94The file will not be removed or overwritten. 95.It Fl R 96Attempt to remove the file hierarchy rooted in each file argument. 97The 98.Fl R 99option implies the 100.Fl d 101option. 102If the 103.Fl i 104option is specified, the user is prompted for confirmation before 105each directory's contents are processed (as well as before the attempt 106is made to remove the directory). 107If the user does not respond affirmatively, the file hierarchy rooted in 108that directory is skipped. 109.Pp 110.It Fl r 111Equivalent to 112.Fl R . 113.It Fl v 114Be verbose when deleting files, showing them as they are removed. 115.It Fl W 116Attempt to undelete the named files. 117Currently, this option can only be used to recover 118files covered by whiteouts. 119.El 120.Pp 121The 122.Nm 123utility removes symbolic links, not the files referenced by the links. 124.Pp 125It is an error to attempt to remove the files 126.Pa / , 127.Pa .\& 128or 129.Pa .. . 130.Pp 131When the utility is called as 132.Nm unlink , 133only one argument, 134which must not be a directory, 135may be supplied. 136No options may be supplied in this simple mode of operation, 137which performs an 138.Xr unlink 2 139operation on the passed argument. 140.Pp 141The 142.Nm 143utility exits 0 if all of the named files or file hierarchies were removed, 144or if the 145.Fl f 146option was specified and all of the existing files or file hierarchies were 147removed. 148If an error occurs, 149.Nm 150exits with a value >0. 151.Sh NOTE 152The 153.Nm 154command uses 155.Xr getopt 3 156to parse its arguments, which allows it to accept 157the 158.Sq Li -- 159option which will cause it to stop processing flag options at that 160point. 161This will allow the removal of file names that begin 162with a dash 163.Pq Sq - . 164For example: 165.Dl rm -- -filename 166The same behavior can be obtained by using an absolute or relative 167path reference. 168For example: 169.Dl rm /home/user/-filename 170.Dl rm ./-filename 171.Sh COMPATIBILITY 172The 173.Nm 174utility differs from historical implementations in that the 175.Fl f 176option only masks attempts to remove non-existent files instead of 177masking a large variety of errors. 178The 179.Fl v 180option is non-standard and its use in scripts is not recommended. 181.Pp 182Also, historical 183.Bx 184implementations prompted on the standard output, 185not the standard error output. 186.Sh SEE ALSO 187.Xr chflags 1 , 188.Xr rmdir 1 , 189.Xr undelete 2 , 190.Xr unlink 2 , 191.Xr fts 3 , 192.Xr getopt 3 , 193.Xr symlink 7 194.Sh STANDARDS 195The 196.Nm 197command conforms to 198.St -p1003.2 . 199.Pp 200The simplified 201.Nm unlink 202command conforms to 203.St -susv2 . 204.Sh HISTORY 205A 206.Nm 207command appeared in 208.At v1 . 209.Sh BUGS 210The 211.Fl P 212option assumes that the underlying file system is a fixed-block file 213system. 214UFS is a fixed-block file system, LFS is not. 215In addition, only regular files are overwritten, other types of files 216are not. 217