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: Mon, 19 Jun 2000 11:02:26 -0400 To: cygwin at sourceware dot cygnus dot com Subject: Re: all commands start up sloooooow...... Message-ID: <20000619110226.B14829@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cygwin at sourceware dot cygnus dot com References: <82E0F488CB97D31188CD009027B117C149B275@pdc-ehy-atl.ehatchery.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <82E0F488CB97D31188CD009027B117C149B275@pdc-ehy-atl.ehatchery.net>; from FMerenda@vetexchange.com on Mon, Jun 19, 2000 at 10:52:02AM -0400 On Mon, Jun 19, 2000 at 10:52:02AM -0400, Frank Merenda wrote: >one thing I was told from Larry Hall was to make sure that your HOME >environment variable was set, and it wasn't set to "/". >Also check to make sure that you don't have any mounts starting with "\\" or >environment variables that start with "\\". If setting HOME to / is still a problem then we'll fix that. The last I heard, if you are running a recent version of bash, this is not a problem. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com