Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Sun, 8 Feb 2004 22:12:32 -0500 (EST) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Chown bug, attn fileutils maintainer (Was Re: RE : How can i really uninstall completly cygwin from Windows XP Pro ???) In-Reply-To: Message-ID: References: <000001c3ee30$4561e3f0$be00a8c0 AT florent> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.39 On Sun, 8 Feb 2004, Igor Pechtchanski wrote: > The first is a bug in the Cygwin version of chown. A temporary workaround > would be to use "chown -R Flo /*; chown Flo /". > [snip] > On Sun, 8 Feb 2004, Flo wrote: > > > Hello Thx for your help but i get and error : > >[snip] > > The error : > > $ chown -R Flo / > > chown: getting attributes of `//bin': No such file or directory > > chown: getting attributes of `//cvsroot': No such file or directory > > chown: getting attributes of `//cygwin.bat': No such file or directory > > chown: getting attributes of `//cygwin.ico': No such file or directory > > chown: getting attributes of `//etc': No such file or directory > > chown: getting attributes of `//ftp': No such file or directory > > chown: getting attributes of `//home': No such file or directory > > chown: getting attributes of `//lib': No such file or directory > > chown: getting attributes of `//opt': No such file or directory > > chown: getting attributes of `//temp': No such file or directory > > chown: getting attributes of `//tmp': No such file or directory > > chown: getting attributes of `//usr': No such file or directory > > chown: getting attributes of `//var': No such file or directory BTW, I have a procedural question regarding this. I have a 1-line patch to fix this in the current fileutils source. However, fileutils is not maintained, and the problem (generating filenames with the '//' prefix) affects only Cygwin, so it's unlikely to be accepted upstream, and will have to be part of a Cygwin-specific patch. There was some talk about replacing fileutils et al with coreutils (there was even a test version out there, but it never got past the first problem report on cygwin-apps, and the download link is dead). AFAICT, coreutils 5.0 also has this bug, and I could try to send the fix upstream once Cygwin has a coreutils package. The question is, should I wait for coreutils to be out, or should I send in a fix for fileutils? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/