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
Message-ID:	<014401c1c564$06147510$0200a8c0@lifelesswks>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Bernard Dautrevaux" <Dautrevaux AT microprocess DOT com>,
	"'Rick Rankin'" <rick_rankin AT yahoo DOT com>,
	"Stephano Mariani" <sk DOT mail AT btinternet DOT com>, <cygwin AT cygwin DOT com>
References:	<17B78BDF120BD411B70100500422FC6309E4B7 AT IIS000>
Subject:	Re: Suggestion for setup
Date:	Thu, 7 Mar 2002 10:09:51 +1100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000
X-OriginalArrivalTime:	06 Mar 2002 23:08:28.0695 (UTC) FILETIME=[D3AE8A70:01C1C563]

----- Original Message -----
From: "Bernard Dautrevaux" <Dautrevaux AT microprocess DOT com>

> > Depends on how you define "harmless". We have a *huge*
> > domain, and "mkpasswd
> > -d" can take a very long time (20 - 30 minutes) to complete,
> > so I definitely
> > wouldn't want to run blindly run it with the -d option here.
> > If it were
> > implemented, it should be an option, at least.
>
> Oh, I didn't think at that ;-( Obviously a way to avoid running
"mkpasswd
> -d" in such a case would be useful.

Seems to me that a regex mapping for the users & groups to pickup would
be ideal. Then if it's a plain string (ie Robert) mkpasswd behaves
like -u was passed, and if it's empty like -d, if it's an actual regex
expression, it filters the -d content.

The the setup script can ask for the input when it runs, or have it on
the comamnd line from setup.exe (I"m not convinced that this is
something that belongs in the GUI at all..)

...
> Of course the right solution would be to avoid the need for
/etc/passwd and
> /etc/group and automatically serach the NT domain controller, but I'm
afraid
> this would be a *huge* job to create these files as virtual files that
just
> talk to the domain controller if any. Plus if one blindly and dumbly
just
> search through the /etc/passwd file you will get the 20min run time
anyway.

Actually what you're talking about is making cygwin behave as though the
NT domain where a yp server. Look into yp on BSD or Linux and you'll see
what that involves. I'm pretty confident that a yp implementation for
Cygwin would be cool... and a NT->yp mapper would also go down well :}.

Rob


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