Subject: Re: Mass deployment
From: "Michael A. Chase" <[email-masked]>
To: "Cygwin Users" <[email-masked]>, <[email-masked]>
Cc: "\"Earnie Boyd\"" <[email-masked]>
Date: Tue, 17 Apr 2001 12:43:36 -0700

The new option in mount won't be ready in time for 1.3.0.  I haven't yet
found out who can sign the disclaimer for my company.

For now youre probably better off dumping the appropriate registry areas
using regedit.exe and then using it to load them in the other machines.

--
Mac :})
** I normally forward private database questions to the DBI mail lists. **
Give a hobbit a fish and he'll eat fish for a day.
Give a hobbit a ring and he'll eat fish for an age.
----- Original Message -----
From: "Earnie Boyd" <[email-masked]>
To: <[email-masked]>
Cc: "Cygwin Users" <[email-masked]>
Sent: Tuesday, April 17, 2001 5:23 AM
Subject: Re: Mass deployment

> Optionally you could install on the server and just set the cygwin
> directory as a share and have all the others map to it.  This will have
> speed impact so if you're actually depending on timely results it might
> not be what you want to do.  If you do decide on this you'll need to map
> the mount points in the registry.  The yet to be released 1.3.0 has a
> new option in mount to allow it to output the mount point registry
> entries in a file so that you can move that file to another client and
> use that file to do the mounts.  You could grab a current snapshot and
> use the binary for the new mount process it you decide to use this
> option.

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple