| rm.1 (139969) | rm.1 (140353) |
|---|---|
| 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 --- 16 unchanged lines hidden (view full) --- 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 | 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 --- 16 unchanged lines hidden (view full) --- 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: head/bin/rm/rm.1 139969 2005-01-10 08:39:26Z imp $ | 33.\" $FreeBSD: head/bin/rm/rm.1 140353 2005-01-16 16:41:59Z ru $ |
| 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 --- 116 unchanged lines hidden (view full) --- 158.Pq Sq - . 159For example: 160.Dl rm -- -filename 161The same behavior can be obtained by using an absolute or relative 162path reference. 163For example: 164.Dl rm /home/user/-filename 165.Dl rm ./-filename | 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 --- 116 unchanged lines hidden (view full) --- 158.Pq Sq - . 159For example: 160.Dl rm -- -filename 161The same behavior can be obtained by using an absolute or relative 162path reference. 163For example: 164.Dl rm /home/user/-filename 165.Dl rm ./-filename |
| 166.Sh SEE ALSO 167.Xr chflags 1 , 168.Xr rmdir 1 , 169.Xr undelete 2 , 170.Xr unlink 2 , 171.Xr fts 3 , 172.Xr getopt 3 , 173.Xr symlink 7 174.Sh BUGS 175The 176.Fl P 177option assumes that the underlying file system is a fixed-block file 178system. 179UFS is a fixed-block file system, LFS is not. 180In addition, only regular files are overwritten, other types of files 181are not. | |
| 182.Sh COMPATIBILITY 183The 184.Nm 185utility differs from historical implementations in that the 186.Fl f 187option only masks attempts to remove non-existent files instead of 188masking a large variety of errors. 189The 190.Fl v 191option is non-standard and its use in scripts is not recommended. 192.Pp 193Also, historical 194.Bx 195implementations prompted on the standard output, 196not the standard error output. | 166.Sh COMPATIBILITY 167The 168.Nm 169utility differs from historical implementations in that the 170.Fl f 171option only masks attempts to remove non-existent files instead of 172masking a large variety of errors. 173The 174.Fl v 175option is non-standard and its use in scripts is not recommended. 176.Pp 177Also, historical 178.Bx 179implementations prompted on the standard output, 180not the standard error output. |
| 181.Sh SEE ALSO 182.Xr chflags 1 , 183.Xr rmdir 1 , 184.Xr undelete 2 , 185.Xr unlink 2 , 186.Xr fts 3 , 187.Xr getopt 3 , 188.Xr symlink 7 |
|
| 197.Sh STANDARDS 198The 199.Nm 200command conforms to 201.St -p1003.2 . 202.Pp 203The simplified 204.Nm unlink 205command conforms to 206.St -susv2 . 207.Sh HISTORY 208A 209.Nm 210command appeared in 211.At v1 . | 189.Sh STANDARDS 190The 191.Nm 192command conforms to 193.St -p1003.2 . 194.Pp 195The simplified 196.Nm unlink 197command conforms to 198.St -susv2 . 199.Sh HISTORY 200A 201.Nm 202command appeared in 203.At v1 . |
| 204.Sh BUGS 205The 206.Fl P 207option assumes that the underlying file system is a fixed-block file 208system. 209UFS is a fixed-block file system, LFS is not. 210In addition, only regular files are overwritten, other types of files 211are not. |
|