X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <20259653 DOT post AT talk DOT nabble DOT com> <297343D29C14AA4D822142893ABEAEF30597D0CE AT srv1163ex1 DOT flightsafety DOT com> <490B1E7D DOT 10305 AT bmts DOT com> Subject: RE: Cygwin setup.exe via the cygwin shell Date: Fri, 31 Oct 2008 15:55:42 -0000 Message-ID: <02cb01c93b71$224acb00$9601a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <490B1E7D.10305@bmts.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Ralph Hempel wrote on 31 October 2008 15:04: > One thing nagging in the background is whether or not you can/should > update your cygwin installation while any Cygwin processes are running. Well, there's obviously going to be a bash process running if you do things that way, but hopefully that will just cause the replace-on-reboot mechanism to come into play. You will, however, have to /expect/ to reboot every time if you insist on launching setup from bash. (It should be possible to launch it from cmd.exe or from a .bat file without this inconvenience.) It is, in general, very much for the best if you /don't/ do things this way. Replace-on-reboot can help, but I think it's quite possible that postinstall scripts might fail if you have a half-updated installation waiting for a reboot to become valid again. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/