Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Message-ID: <019f01c1c564$bae55e00$0200a8c0@lifelesswks>
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Andrew DeFaria" <Andrew@DeFaria.com>
Cc: <cygwin@cygwin.com>
References: <20020306162159.57702.qmail@web10508.mail.yahoo.com> <3C866767.7050709@DeFaria.com>
Subject: Re: Suggestion for setup
Date: Thu, 7 Mar 2002 10:14:54 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


--
===
"Andrew DeFaria" <Andrew@DeFaria.com> wrote in message
news:3C866767.7050709@DeFaria.com...
> Rick Rankin wrote:
>
> > 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.
> >
> > When I run mkpasswd here, I generally run it twice, once to get
local machine
> > accounts, and once with the -d *and* -u options to get a specific
user's info
> > from the domain. It might be useful with those options. Hmm, maybe
I'll take a
> > look at that. It would require some fields in the GUI though...
>
> That's why I lobbied (briefly) for setup to allow the user to specify
> their own setup script - a script to be run automatically after Cygwin
> setup is done. This way the various administrators could determine and
> code their own local customizations as it were.

And the setup in beta at the moment sortof-has this capability. Simply
add a new mirror site, with a single package in base called "Andrew's
master script". It's postinstall script will get run.

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/