Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Fri, 21 Apr 2000 15:18:58 -0400 To: cygwin@sourceware.cygnus.com Subject: Re: cygwin Digest 21 Apr 2000 02:33:12 -0000 Issue 475 Message-ID: <20000421151858.B9625@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cgf@cygnus.com, cygwin@sourceware.cygnus.com References: <200004211929.PAA18266@jaj.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: <200004211929.PAA18266@jaj.com>; from pedwards@jaj.com on Fri, Apr 21, 2000 at 03:29:25PM -0400 On Fri, Apr 21, 2000 at 03:29:25PM -0400, Phil Edwards wrote: >> It sounds like you probably have /bin mounted explicitly. Looks like >> this is YA change to setup. > >The documentation might oughta change from "explicit mounts will be >overwritten," to something like "explicit mounts will cause Weird Things >to happen before being overwritten." Um. No. I guess I should have phrased that as a question: Did you have /bin mounted explicitly? Another question: Did you have other cygwin processes running during the setup? Rather than add glib comments to the documentation, I think it is probably a better plan to track down what's going wrong. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com