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