From owner-freebsd-current Sat Jan 29 16: 6:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id 8627F14E79 for ; Sat, 29 Jan 2000 16:06:35 -0800 (PST) (envelope-from kuriyama@sky.rim.or.jp) Received: from mail1.rim.or.jp by serio.al.rim.or.jp (8.8.8/3.7W/HMX-12) with ESMTP id IAA03062 for ; Sun, 30 Jan 2000 08:28:13 +0900 (JST) Received: from rhea.sky.rim.or.jp (ppp382.kt.rim.or.jp [202.247.140.82]) by mail1.rim.or.jp (3.7W/) id JAA13223 for ; Sun, 30 Jan 2000 09:06:33 +0900 (JST) Received: from localhost.sky.rim.or.jp (localhost [127.0.0.1]) by rhea.sky.rim.or.jp (8.9.3/3.7W/rhea-1.2) with ESMTP id JAA54062 for ; Sun, 30 Jan 2000 09:06:33 +0900 (JST) Date: Sun, 30 Jan 2000 09:06:33 +0900 Message-ID: <86aeloo22e.wl@localhost.sky.rim.or.jp> From: Jun Kuriyama To: current@FreeBSD.org Subject: "rm -rf" behavior on readonly nfs User-Agent: Wanderlust/2.2.16 (No Son Of Mine) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found difference between "rm -rf" for non-exist file on readonly nfs and usual non-writable directory. In this example, /usr/src is readonly nfs mounted and /usr/bin is normal filesystem but not writable. And file "a" is not exist. ----- % rm /usr/bin/a rm: /usr/bin/a: No such file or directory % rm -f /usr/bin/a % rm -rf /usr/bin/a % rm /usr/src/a rm: /usr/src/a: No such file or directory % rm -f /usr/src/a % rm -rf /usr/src/a rm: /usr/src/a: Read-only file system % ----- For "-f" option, last behavior is expected one, or not? Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message