Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!hao!husc6!bbn!rochester!ritcv!cci632!ccicpg!felix!zemon
From: matt@oddjob.UUCP (Godfather to putty-tats)
Newsgroups: comp.unix.ultrix
Subject: Re: Bug in 2.0 NFS
Message-ID: <16925@felix.UUCP>
Date: 24 Dec 87 18:06:23 GMT
References: <16842@felix.UUCP>
Sender: zemon@felix.UUCP
Reply-To: matt@oddjob.UUCP (Godfather to putty-tats)
Organization: Audible Boy Birdwatcher Society
Lines: 24
Approved: zemon@felix.UUCP
Reply-Path:


John P. Nelson writes:
) The bug is that the "utimes" system call returns an error if applied
) over NFS to a read-only file that resides on an ULTRIX 2.0 machine.
) ... if the same operation is done
) on the same file, but LOCALLY (i.e. not through NFS), then it succeeds.

Are you saying that utimes() can change the timestamps on a file on a
local read-only file system?  If so, then THAT is the bug, and a
serious one.  If instead you are talking about a f.s. that is R/W on
its local system, but which has been mounted by another host as R/O,
then everything is behaving just as it should.  On a R/O file system
it's not just the file contents that are unwritable, but everything
about the file system, including the inodes.

) We have notified DEC of the bug, but we are told that there is no
) chance of obtaining a fix before Ultrix 2.2 is released, and maybe
) not even then.

If DEC agreed that this was a bug, then either they did not
understand you or you talked to someone who didn't know much.
________________________________________________________
Matt	     University		matt@oddjob.uchicago.edu
Crawford     of Chicago     {astrovax,ihnp4}!oddjob!matt