From owner-freebsd-bugs  Thu Jul 19  6:26:17 2001
Delivered-To: freebsd-bugs@freebsd.org
Received: from yertle.kciLink.com (yertle.kcilink.com [216.194.193.105])
	by hub.freebsd.org (Postfix) with ESMTP
	id D7C2937B403; Thu, 19 Jul 2001 06:26:14 -0700 (PDT)
	(envelope-from khera@kciLink.com)
Received: from onceler.kciLink.com (onceler.kciLink.com [216.194.193.106])
	by yertle.kciLink.com (Postfix) with ESMTP
	id 6AFA02E45F; Thu, 19 Jul 2001 09:26:13 -0400 (EDT)
Received: (from khera@localhost)
	by onceler.kciLink.com (8.11.4/8.11.4) id f6JDQDK96815;
	Thu, 19 Jul 2001 09:26:13 -0400 (EDT)
	(envelope-from khera)
From: Vivek Khera <khera@kcilink.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15190.57333.290133.65965@onceler.kciLink.com>
Date: Thu, 19 Jul 2001 09:26:13 -0400
To: <mike@FreeBSD.org>
Cc: freebsd-bugs@FreeBSD.org
Subject: Re: kern/16040: Read-only files under NFS are not seen as read-only by FreeBSD 3.4-RELEASE
In-Reply-To: <200107190426.f6J4Q5V05784@freefall.freebsd.org>
References: <200107190426.f6J4Q5V05784@freefall.freebsd.org>
X-Mailer: VM 6.92 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

>>>>> "m" == mike  <mike@FreeBSD.org> writes:

m> Synopsis: Read-only files under NFS are not seen as read-only by FreeBSD 3.4-RELEASE
m> State-Changed-From-To: open->feedback
m> State-Changed-By: mike
m> State-Changed-When: Wed Jul 18 21:24:30 PDT 2001
m> State-Changed-Why: 

m> Does this problem still occur in newer versions of FreeBSD,
m> such as 4.3-RELEASE or 4.3-STABLE?

m> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=16040

Gosh... this was such a long time ago.  I think the error turned out
to be a bug in the BSD/OS NFS server code.  When I switched to FreeBSD
servers, the problems went away.  I thought this issue was closed, but
maybe that was just the mailing list discussion conclusion.

Anyhow, I believe it is a BSD/OS bug, not FreeBSD.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message