Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 6 Mar 2002 12:51:08 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Suggestion for setup Message-ID: <20020306175108.GA15442@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <17B78BDF120BD411B70100500422FC6309E4B7@IIS000> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17B78BDF120BD411B70100500422FC6309E4B7@IIS000> User-Agent: Mutt/1.3.23.1i On Wed, Mar 06, 2002 at 06:31:04PM +0100, Bernard Dautrevaux wrote: >Oh, I didn't think at that ;-( Obviously a way to avoid running "mkpasswd >-d" in such a case would be useful. This is just an issue for first time installations, right? AFAICT, /etc/passwd should not be produced if there is already a /etc/passwd. Ditto /etc/group. I guess the best solution is to present the user with several options 1) Create /etc/passwd using local accounts? 2) Create /etc/passwd using domain accounts? 3) Create /etc/passwd using local and domain accounts? 4) Don't create /etc/passwd Then we have to remember what the user wanted. cgf -- 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/