Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <5C838890A2EDD411AFB2009027CC67091A2B76@cupex3.rational.com> From: "Masterson, Dave" To: "'Earnie Boyd'" Subject: RE: Questions about Cygwin's setup... Date: Wed, 24 Jan 2001 18:35:40 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Hmmm. The cygwin mailer does some strange things with Reply-to. Your message has a Reply-to of "Earnie Boyd ". Is this intentional? With respect to my message, it should be obvious that I'm trying to setup a "minimum" install of Cygwin. My thought was that, since only I in my group pay attention to what goes on with Cygwin, I could maintain a central area where Cygwin is. I suppose I could send out occassional messages that say something like "rerun \\my\setup.exe to update your Cygwin", but it would be much better if it just happened automatically. Thus the idea of a pre-setup central share that I (the Cygwin admin) maintain. Also, if the speed of the central share, it probably wouldn't be hard to make a batch script to mirror it to a local drive (which I might write). With respect to your answers: * Why not make setup a package (say "cygwinsetup") like all the rest so that it could potentially update itself? * The cygwinsetup package could include a batch script that calls a copy of setup.exe from some well-known location in the local directory tree. It could first install setup.exe and then copy it to the well-known location to ensure there are no update conflicts. * The cygwinsetup script could also include a separate shell/bat/exe that could be called by (say) cygwin.bat to check to see if the mount tables in the registry have been setup and, if not, set them up before starting bash. (This could probably be hacked out of setup.exe.) With this, I only have to tell users (once) to setup a shortcut icon that points to cygwin.bat. Also, since this area is pre-setup by me, I can include things that are not installed by setup.exe (like many Elisp extensions to Emacs or many toys in /usr/local) and users would "just get it". -----Original Message----- From: Earnie Boyd [mailto:earnie_boyd AT yahoo DOT com] Sent: Wednesday, January 24, 2001 5:53 PM To: Masterson, Dave Cc: 'cygwin AT cygwin DOT com' Subject: Re: Questions about Cygwin's setup... "Masterson, Dave" wrote: > > I have a few questions about the setup of Cygwin: > > * If you use the Setup.exe program to install Cygwin, does that update > the Windows-NT registry in any meaningful way? Yes. > * Could I use the Setup program to install Cygwin on a Windows-NT > share and would that be immediately useable by others (assuming they update > their PATH variables)? No. The mount tables from the registry wouldn't be on the local client. > * If I use Setup to update this share (assuming its quiet), would > users need to do something (like fix their registry)? Yes. The other option is to execute Setup in an empty directory and choose the install from local disk option. It wouldn't install anything but the setup process would create the registry entries. > * Does Setup remove old files during update? Yes. > * Can Setup update itself? No. > * What is the latest version of Setup (I have 2.6)? Just always execute the one from http://cygwin.com/setup.exe and don't worry about the most current version. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple