X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: <48C84C9E.98E23606@dessent.net> Date: Wed, 10 Sep 2008 15:39:26 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: setup.exe --quiet-mode References: <48C0316C.F9E434A9@dessent.net> <00fc01c90f39$f4006970$9601a8c0@CAM.ARTIMI.COM> <007101c9136b$a62b3e10$9601a8c0@CAM.ARTIMI.COM> <48C841D0.ED2F523F@dessent.net> <20080910221104.GA11152@ednor.casa.cgf.cx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Christopher Faylor wrote: > Dave did suggest a possible workaround - delay any postinstall scripts > until the next reboot. That's more graceful than requiring the user to re-run setup to catch the failed postinstalls. But it still results in a broken system until the next reboot since those binaries that were just installed will all fail if you try to run them. (And if they don't fail because of missing entry points, they could fail because their postinstalls were deferred.) That's what I mean by "no workaround" -- the immediate result after running setup with cygwin1.dll in use is a broken system, and there's not a lot you can do to avoid that other than "don't run setup with important DLLs in use". Brian -- 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/