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: Sat, 6 Nov 2004 14:58:12 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Windows logins with spaces Message-ID: <20041106195812.GD31141@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <418CE5CD.5000406@iinet.net.au> <20041106164805.GA339217@hpn5170> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041106164805.GA339217@hpn5170> User-Agent: Mutt/1.4.1i On Sat, Nov 06, 2004 at 11:48:05AM -0500, Pierre A. Humblet wrote: >On Sun, Nov 07, 2004 at 12:55:09AM +1000, Nick Coghlan wrote: >> Hi, >> >> My windows login name has a space in it. I was able to remove the space >> in Cygwin just by editing /etc/passwd (effectively doing 's/login >> name/loginname/') and renaming '/home/login name/' to >> '/home/loginname/'. Cygwin then appeared to find the new home directory >> quite happily and set HOME and USER to the version of the name with no >> spaces. HOMEPATH still points to the correct Windows directory. >> >> This seems much simpler and more flexible than the approach given in the >> current FAQ (which suggests hardcoding values for USER and HOME in >> /etc/profile). It should also work with other programs which access >> /etc/passwd (which *is* mentioned as a problem with the approach given >> in the FAQ). > >You are absolutely right. Substitute text has already been proposed, >see the thread >http://cygwin.com/ml/cygwin-patches/2003-q1/msg00315.html This probably came in during one of the times when our FAQ maintainer was on a break. Go ahead and update the FAQ if you are so inclined, Pierre. 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/