X-Spam-Check-By: sourceware.org Message-ID: <43C851B8.3000307@equate.dyndns.org> Date: Sat, 14 Jan 2006 01:19:52 +0000 From: Chris Taylor Reply-To: cygwin AT cygwin DOT com User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) MIME-Version: 1.0 To: Brett Serkez CC: cygwin AT cygwin DOT com Subject: Re: Installing cygwin by manually copying c:\cygwin to another machine References: <1137149072 DOT 2980 DOT 251770934 AT webmail DOT messagingengine DOT com> <43C789D2 DOT 8020505 AT equate DOT dyndns DOT org> <1137201240 DOT 1365 DOT 251826199 AT webmail DOT messagingengine DOT com> In-Reply-To: <1137201240.1365.251826199@webmail.messagingengine.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Brett Serkez wrote: > [snip] > >>>Is it just the mount points that are the issue? The path? The >>>desktop icon? It is possible to run setup against such an >>>'installation' to update it? >> >>It's primarily just the mount points. See Corinna's message in this >>thread for recreating them. >> >>The desktop & start menu icons are obviously not going to be present >>with this method, but that's not really an issue. It should be noted >>that cygwin.bat has a full path in it, so this would need editing. >> >>Yes, you could run setup with this - it is, for all intents and >>purposes, the installation you made with setup on the other machine. >>Setup doesn't care that it's now on a different machine. None of what >>it does is machine-specific. > > > What about chere and services such as sshd and the like? > > Seems to me there is a short list, having a documented method or even a > script to settle in a moved cygwin directory on a new system may be > useful. I would presume this would be significantly faster than > reinstalling on multiple systems. > Not particularly, assuming you use the same local package cache on each machine, especially if you use the trick for pulling in all the packages you want automatically. I don't know about chere, but once the mount points are created, as per Corinna's message, cygwin is in the same state it would be in if you had installed it on that system directly. That means that setup, services like sshd, cron, inetd, etcetera will be available for installation. Permissions will be set accordingly by the service installation scripts, where appropriate. You could /potentially/ have a permissions problem if you copy the folder as a user and for whatever reason permissions are not inherited that allow other users to utilise cygwin, but if this is the case then you're already running a non-standard setup, and should know enough about it to avoid this problem. Chris -- Spinning complacently in the darkness, covered and blinded by a blanket of little lives, false security has lulled the madness of this world into a slumber. Wake up! An eye is upon you, staring straight down and keenly through, seeing all that you are and everything that you will never be. Yes, an eye is upon you, an eye ready to blink. So face forward, with arms wide open and mind reeling. Your future has arrived... Are you ready to go? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/