X-Spam-Check-By: sourceware.org Date: Tue, 27 Feb 2007 19:03:47 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Strange message from updatedb Message-ID: <20070228000347.GB1687@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <82c42b950702261435t4acc4fbctdd2042aee0f609d4 AT mail DOT gmail DOT com> <81BDE334890B7C429EDBA5857465C7565F165F AT mcaosx6 DOT ca DOT mcao DOT maricopa DOT gov> <82c42b950702271050w2e807388t6009e795f4041d82 AT mail DOT gmail DOT com> <82c42b950702271238v7ce39db0i86ca282168df222e AT mail DOT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Tue, Feb 27, 2007 at 04:17:54PM -0700, Cary Jamison wrote: >Phil Edwards wrote: >> I'm aware of the restrictions, and I will bet long odds that spaces >> show up in filenames far more often than colons (or any other >> punctuation commonly used as a separator in pathname lists) are used. >> I've not changed my opinion that updatedb is behind the times and is >> needlessly complicating things for admins, but I also don't expect >> that opinion to change anybody else's mind -- this bug has been >> reported before, against other distros, and gets rejected because "you >> shouldn't use spaces in filenames under Linux," how quaint. > >This opinion by Linux users has to change if they want Linux to become a >more mainstream os. Everyday users are going to use spaces in filenames >through the Linux desktop, just as it has become more common on the Windows >desktop. > ><$.02 Personally,Idon'treallyunderstandwhatthebigdealishere. cgf -- 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/