Bug 16040

Summary: Read-only files under NFS are not seen as read-only by FreeBSD 3.4-RELEASE
Product: Base System Reporter: Vivek Khera <khera>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 3.4-STABLE   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
vivek.vcf none

Description Vivek Khera 2000-01-10 20:10:00 UTC 
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.

Fix: 

don't know.
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.
Comment 1 Jeroen Ruigrok van der Werven freebsd_committer freebsd_triage 2000-01-11 10:22:51 UTC 
Responsible Changed
From-To: gnats-admin->freebsd-bugs

This belongs to the kernel group IMHO. 
Mayhaps dillon want to look at this?
Comment 2 Vick Khera 2000-11-17 22:12:07 UTC 
same as kern/20842, which is non-issue because it is BSD/OS NFS server
problem.
Comment 3 Mike Barcroft freebsd_committer freebsd_triage 2001-07-19 05:24:30 UTC 
State Changed
From-To: open->feedback


Does this problem still occur in newer versions of FreeBSD, 
such as 4.3-RELEASE or 4.3-STABLE?
Comment 4 Mike Barcroft freebsd_committer freebsd_triage 2001-07-19 16:55:51 UTC 
State Changed
From-To: feedback->closed


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.