Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 21 Jul 2004 10:09:17 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: chown -R expanding / to //bin etc. Message-ID: <20040721080917.GB21800@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20040721073930.C5D6084CA3@pessard.research.canon.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040721073930.C5D6084CA3@pessard.research.canon.com.au> User-Agent: Mutt/1.4.2i On Jul 21 17:39, luke.kendall@cisra.canon.com.au wrote: > I've noticed that if I do (*) a > > chown -R administrator.SYSTEM / > > then chown goes out onto the network and tries to access shares called > //bin, //var, //usr etc., and can block for long periods, too. > > Now, I do understand that really I should be doing (**) > > chown -R administrator.SYSTEM `cygpath -w / | sed 's|\\|/|g'` > > to restrict the chown to only affect Cygwin files anyway, but I'm still > interested in how the spurious //bin etc. names are generated. (I.e. > whether that's actually a bug?) It's a bug in the current chown implementation in that it doesn't know that leading double slashes has a special meaning on some operating systems. I don't know if that's fixed in newer versions of chown. Since chown is part of coreutils today, it would be nice if we could find a volunteer to maintain coreutils. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/