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 October 28, 2004 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. 91.It Fl R 92Attempt to remove the file hierarchy rooted in each file argument. 93The 94.Fl R 95option implies the 96.Fl d 97option. 98If the 99.Fl i 100option is specified, the user is prompted for confirmation before 101each directory's contents are processed (as well as before the attempt 102is made to remove the directory). 103If the user does not respond affirmatively, the file hierarchy rooted in 104that directory is skipped. 105.Pp 106.It Fl r 107Equivalent to 108.Fl R . 109.It Fl v 110Be verbose when deleting files, showing them as they are removed. 111.It Fl W 112Attempt to undelete the named files. 113Currently, this option can only be used to recover 114files covered by whiteouts. 115.El 116.Pp 117The 118.Nm 119utility removes symbolic links, not the files referenced by the links. 120.Pp 121It is an error to attempt to remove the files 122.Pa / , 123.Pa .\& 124or 125.Pa .. . 126.Pp 127When the utility is called as 128.Nm unlink , 129only one argument, 130which must not be a directory, 131may be supplied. 132No options may be supplied in this simple mode of operation, 133which performs an 134.Xr unlink 2 135operation on the passed argument. 136.Pp 137The 138.Nm 139utility exits 0 if all of the named files or file hierarchies were removed, 140or if the 141.Fl f 142option was specified and all of the existing files or file hierarchies were 143removed. 144If an error occurs, 145.Nm 146exits with a value >0. 147.Sh NOTE 148The 149.Nm 150command uses 151.Xr getopt 3 152to parse its arguments, which allows it to accept 153the 154.Sq Li -- 155option which will cause it to stop processing flag options at that 156point. 157This will allow the removal of file names that begin 158with a dash 159.Pq Sq - . 160For example: 161.Dl rm -- -filename 162The same behavior can be obtained by using an absolute or relative 163path reference. 164For example: 165.Dl rm /home/user/-filename 166.Dl rm ./-filename 167.Sh COMPATIBILITY 168The 169.Nm 170utility differs from historical implementations in that the 171.Fl f 172option only masks attempts to remove non-existent files instead of 173masking a large variety of errors. 174The 175.Fl v 176option is non-standard and its use in scripts is not recommended. 177.Pp 178Also, historical 179.Bx 180implementations prompted on the standard output, 181not the standard error output. 182.Sh SEE ALSO 183.Xr chflags 1 , 184.Xr rmdir 1 , 185.Xr undelete 2 , 186.Xr unlink 2 , 187.Xr fts 3 , 188.Xr getopt 3 , 189.Xr symlink 7 190.Sh STANDARDS 191The 192.Nm 193command conforms to 194.St -p1003.2 . 195.Pp 196The simplified 197.Nm unlink 198command conforms to 199.St -susv2 . 200.Sh HISTORY 201A 202.Nm 203command appeared in 204.At v1 . 205.Sh BUGS 206The 207.Fl P 208option assumes that the underlying file system is a fixed-block file 209system. 210UFS is a fixed-block file system, LFS is not. 211In addition, only regular files are overwritten, other types of files 212are not. 213