Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Message-ID: <018b01c1c546$421db3f0$d700a8c0@mchasecompaq>
From: "Michael A Chase" <mchase@ix.netcom.com>
To: <cygwin@cygwin.com>
References: <17B78BDF120BD411B70100500422FC6309E4B7@IIS000> <20020306175108.GA15442@redhat.com>
Subject: Re: Suggestion for setup
Date: Wed, 6 Mar 2002 11:25:30 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

----- Original Message -----
From: "Christopher Faylor" <cgf@redhat.com>
To: <cygwin@cygwin.com>
Sent: Wednesday, March 06, 2002 09:51
Subject: Re: Suggestion for setup


> 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.

Not necessarily.  The existance of /etc/password is already being checked in
setup.exe.  So if it exists, the default should be 4; if it doesn't, the
default should be 1 to avoid delays in large domains.
--
Mac :})
** I normally forward private questions to the appropriate mail list. **
Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.


--
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/