From: "Tim Van Holder" To: Subject: Re: .files on servers are perceived as readonly Date: Sat, 9 Jun 2001 15:49:23 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-reply-to: <1438-Sat09Jun2001145339+0300-eliz@is.elta.co.il> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > In other words, the write bit in the Posix mode bits was the only way > `stat' could relate to a program that such files are special. It's > not a bad approximation, given how many years it works without > complaints. Well, I suppose you could use the sticky bit for hidden and the suid bit for system (the latter would be especially apt, as it would cause an 's' to appear in "ls -l" output). > Could you please explain what exactly is wrong with that? Why did it > annoy you that .cvsignore was shown as not writable? Because it's a writable file. Wouldn't it annoy you if emacs considered .emacs read-only, just because it somehow got its hidden bit set? > > > ls -agl v:/martin/djgpp/djgpp/src/libc/ > > total 0 > > ----d- 96 Jun 8 23:10 cvs > > > > Is it supposed to bahave like that? > > Like what? What is the problem you refer to? Only showing the directory, I presume.