1 .\" $NetBSD: rm.1,v 1.9 1997/10/20 08:53:14 enami Exp $
3 .\" Copyright (c) 1990, 1993, 1994
4 .\" The Regents of the University of California. All rights reserved.
6 .\" This code is derived from software contributed to Berkeley by
7 .\" the Institute of Electrical and Electronics Engineers, Inc.
9 .\" Redistribution and use in source and binary forms, with or without
10 .\" modification, are permitted provided that the following conditions
12 .\" 1. Redistributions of source code must retain the above copyright
13 .\" notice, this list of conditions and the following disclaimer.
14 .\" 2. Redistributions in binary form must reproduce the above copyright
15 .\" notice, this list of conditions and the following disclaimer in the
16 .\" documentation and/or other materials provided with the distribution.
17 .\" 3. All advertising materials mentioning features or use of this software
18 .\" must display the following acknowledgement:
19 .\" This product includes software developed by the University of
20 .\" California, Berkeley and its contributors.
21 .\" 4. Neither the name of the University nor the names of its contributors
22 .\" may be used to endorse or promote products derived from this software
23 .\" without specific prior written permission.
25 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
26 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
27 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
28 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
29 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
30 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
31 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
32 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
33 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
34 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
37 .\" @(#)rm.1 8.5 (Berkeley) 12/5/94
44 .Nd remove directory entries
53 utility attempts to remove the non-directory type files specified on the
55 If the permissions of the file do not permit writing, and the standard
56 input device is a terminal, the user is prompted (on the standard error
57 output) for confirmation.
59 The options are as follows:
62 Attempt to remove directories as well as other types of files.
64 Attempt to remove the files without prompting for confirmation,
65 regardless of the file's permissions.
66 If the file does not exist, do not display a diagnostic message or modify
67 the exit status to reflect an error.
70 option overrides any previous
74 Request confirmation before attempting to remove each file, regardless of
75 the file's permissions, or whether or not the standard input device is a
79 option overrides any previous
83 Overwrite regular files before deleting them.
84 Files are overwritten three times, first with the byte pattern 0xff,
85 then 0x00, and then 0xff again, before they are deleted.
87 Attempt to remove the file hierarchy rooted in each file argument.
95 option is specified, the user is prompted for confirmation before
96 each directory's contents are processed (as well as before the attempt
97 is made to remove the directory).
98 If the user does not respond affirmatively, the file hierarchy rooted in
99 that directory is skipped.
105 Attempts to undelete the named files.
106 Currently, this option can only be used to recover
107 files covered by whiteouts.
112 utility removes symbolic links, not the files referenced by the links.
114 It is an error to attempt to remove the files ``.'' and ``..''.
118 utility exits 0 if all of the named files or file hierarchies were removed,
121 option was specified and all of the existing files or file hierarchies were
125 exits with a value >0.
135 option assumes that the underlying file system is a fixed-block file
137 UFS is a fixed-block file system, LFS is not.
138 In addition, only regular files are overwritten, other types of files
143 utility differs from historical implementations in that the
145 option only masks attempts to remove non-existent files instead of
146 masking a large variety of errors.
150 implementations prompted on the standard output,
151 not the standard error output.
155 utility is expected to be