Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Wed, 6 Mar 2002 12:51:08 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Suggestion for setup
Message-ID:	<20020306175108.GA15442@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<17B78BDF120BD411B70100500422FC6309E4B7 AT IIS000>
Mime-Version:	1.0
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/

- Raw text -