From khera@kciLink.com  Mon Jan 10 12:06:50 2000
Return-Path: <khera@kciLink.com>
Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1])
	by hub.freebsd.org (Postfix) with ESMTP id DD64C1537F
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 10 Jan 2000 12:06:49 -0800 (PST)
	(envelope-from khera@kciLink.com)
Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2])
	by kci.kciLink.com (Postfix) with ESMTP id 9BE79E8AD
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 10 Jan 2000 15:06:48 -0500 (EST)
Received: (from khera@localhost)
	by onceler.kcilink.com (8.9.3/8.9.3) id PAA16051;
	Mon, 10 Jan 2000 15:06:48 -0500 (EST)
	(envelope-from khera@kci.kcilink.com)
Message-Id: <200001102006.PAA16051@onceler.kcilink.com>
Date: Mon, 10 Jan 2000 15:06:48 -0500 (EST)
From: <khera@kciLink.com>
Reply-To: khera@kciLink.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: NFS files don't show up as read-only under FreeBSD 3.4-STABLE
X-Send-Pr-Version: 3.2

>Number:         16040
>Category:       kern
>Synopsis:       Read-only files under NFS are not seen as read-only by FreeBSD 3.4-RELEASE
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jan 10 12:10:00 PST 2000
>Closed-Date:    Thu Jul 19 08:55:51 PDT 2001
>Last-Modified:  Thu Jul 19 09:00:44 PDT 2001
>Originator:     Vivek Khera
>Release:        FreeBSD 3.4-STABLE i386
>Organization:
>Environment:

XEmacs 21.1.8 compiled (from ports collection) on FreeBSD 3.4-STABLE
on December 9, 1999; Jove from 3.3-RELEASE package collection.

The NFS servers in question are BSD/OS 4.0.1 and BSD/OS 3.1; the NFS
implementation in BSD/OS 4.0.1 is certified as properly interoperable
with other NFS implementations.

>Description:

XEmacs doesn't notice that files are read-only if the file system in
question is NFS.  Read-only files are properly noticed for local FFS
and MFS file systems.

Using FreeBSD 3.4 as the server and BSD/OS 4.0.1 as the client
operates as expected: the read-only attribute is honored.

>How-To-Repeat:

In an NFS mounted directory:

cat >foo
chmod a-w foo
xemacs foo

xemacs will not mark the file as a read-only buffer, nor will it warn
you when you are about to overwrite the file when saving it.

Similarly, jove will not consider the file read-only either.

>Fix:
	
don't know.



>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: gnats-admin->freebsd-bugs 
Responsible-Changed-By: asmodai 
Responsible-Changed-When: Tue Jan 11 02:22:51 PST 2000 
Responsible-Changed-Why:  
This belongs to the kernel group IMHO. 
Mayhaps dillon want to look at this? 

From: Vivek Khera <vivek@khera.org>
To: freebsd-gnats-submit@FreeBSD.org, khera@kciLink.com
Cc:  
Subject: Re: kern/16040: Read-only files under NFS are not seen as read-only by 
 FreeBSD 3.4-RELEASE
Date: Fri, 17 Nov 2000 17:12:07 -0500

 This is a multi-part message in MIME format.
 --------------01C53509AE54FA078C244B30
 Content-Type: text/plain; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 
 same as kern/20842, which is non-issue because it is BSD/OS NFS server
 problem.
 --------------01C53509AE54FA078C244B30
 Content-Type: text/x-vcard; charset=us-ascii;
  name="vivek.vcf"
 Content-Transfer-Encoding: 7bit
 Content-Description: Card for Vivek Khera
 Content-Disposition: attachment;
  filename="vivek.vcf"
 
 begin:vcard 
 n:Khera;Vivek
 tel;fax:301-545-6899
 tel;work:301-545-6996
 x-mozilla-html:TRUE
 url:http://www.khera.org/~vivek/
 org:Khera Communications, Inc.
 version:2.1
 email;internet:vivek@khera.org
 adr;quoted-printable:;;1445 Research Blvd=0D=0A5th Floor;Rockville;MD;20850;USA
 x-mozilla-cpt:;0
 fn:Vivek Khera
 end:vcard
 
 --------------01C53509AE54FA078C244B30--
 
 
State-Changed-From-To: open->feedback 
State-Changed-By: mike 
State-Changed-When: Wed Jul 18 21:24:30 PDT 2001 
State-Changed-Why:  

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

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=16040 
State-Changed-From-To: feedback->closed 
State-Changed-By: mike 
State-Changed-When: Thu Jul 19 08:55:51 PDT 2001 
State-Changed-Why:  

Originator indicated to me, in a private e-mail, that the problem 
appeared to be with BSD/OS.  The originator's solution was to use 
FreeBSD for both server and client. 

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