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 From: "John Morrison" To: "Cygwin" Cc: "Cygwin Apps" Subject: Skel files Date: Tue, 30 Jul 2002 10:09:32 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Corinna or whom it may concern ;) If/when the 'profile' (name may change) package gets the green light it will have support for a /etc/skel directory. This directory (in case you don't already know) holds so called skeleton files which get copied to a new user's directory. The copy operation is usually done as part of adduser, however, since cygwin doesn't actually add users to the system the home directory creation is done in /etc/profile. As part of this operation I'm going to get it to cp /etc/skel/. $HOME These files are for users to modify to suit themselves. However, I believe that it would be of benifit for shells (and anything else with similar functionality (eg XFree86?)) to add some .default files to help newbies (I can add functionality to filter the package .defaults out of the copy). There. Quite long and slightly rambly. However, what do people think; aye or nay? The copy _will_ be done as part of $HOME creation, default files would be a bonus I believe. Some of the files I have on my system which I believe could have defaults... .bashrc .bash_profile .login .logout .xinit .pinerc .inputrc .vimrc .xserverrc J. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/