Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Wed, 22 Sep 2004 18:30:45 +1000 (EST) From: luke DOT kendall AT cisra DOT canon DOT com DOT au Subject: Re: Request for change to /etc/profile To: cygwin AT cygwin DOT com In-Reply-To: <4150F06C.9070001@comcast.net> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Message-Id: <20040922083046.252F084CB1@pessard.research.canon.com.au> On 21 Sep, CyberZombie wrote: > Or 'mkdir -p "$HOME"'... No, that would do entirely the wrong thing! If the place where /home is supposed to be mounted hasn't been mounted, the last thing you want to do is create an alternate /home. I can imagine the weird problems and reports ("all my files disappeared!"), that doing mkdir -p would cause! My change means that if you can't make the user directory, you just don't try to create the skeleton files in it for them. > >$ diff /etc/profile /etc/profile.orig > >38,39c38 > >< if [ ! -d "$HOME" ] && mkdir "$HOME" > >< then > >--- > > > > > >>if [ ! -d "$HOME" ]; then luke -- 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/