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 Message-ID: <26169.193.133.13.145.1095689906.squirrel@193.133.13.145> In-Reply-To: References: <20040920081046 DOT E810484CCE AT pessard DOT research DOT canon DOT com DOT au> <20040920091729 DOT GU17670 AT cygbert DOT vinschen DOT de> Date: Mon, 20 Sep 2004 15:18:26 +0100 (BST) Subject: Re: Login behaviour oddities: won't run .profile From: "John Morrison" To: cygwin AT cygwin DOT com User-Agent: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-15 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes > One solution is to remove /etc/skel/.bash_profile after the installs > (maybe even in your own site-specific postinstall script). I don't know > if the base-files postinstall script will re-create that file, though -- > if it does, it needs to be fixed. The base-files postinstall script will attempt to recreate its files if they don't exist, it can't differentiate between deleted and clean install (do any?). If you want to use a ~/.profile instead change /etc/skel/.bash_profile to be something along the lines of source ~/.profile Base-files *will not* (now) overwrite a user modified file. Would this be sufficient? I don't know how to improve this... make a note during preremove of any of the manifest files missing and don't create them upon installation? Possible I suppose... J. -- 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/