X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: "Michael Kairys" Subject: Re: Intermittent perl crash Date: Mon, 17 Dec 2007 21:26:39 -0500 Lines: 21 Message-ID: References: <6910a60712171332t3e8db66fn4cf1a64fe611011@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit In-Reply-To: <6910a60712171332t3e8db66fn4cf1a64fe611011@mail.gmail.com> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 "Reini Urban" wrote in message news:6910a60712171332t3e8db66fn4cf1a64fe611011@mail.gmail.com... > Known problem and easy to fix. > Download the rebase package, read the readme, stop all cygwin services and > run rebaseall in ash. Thank you for the timely reply! However I am stuck on what should be a simple step: rebaseall tells me /tmp is not writable. I have tried a variety of directories (all of which are actually writable of course) and a variety of ways of geting there, including mount point, env. var, etc. Further experimentation leads me to believe the shell will return false for -w of any directory. This is consistent with the apparent mode of 555 I see on all of them. And of course they don't respond to chmod. (I believe this is a windows thing that I have even read about somewhere in the cygwin docs...) So I am left with the question: how would this ever work? -- 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/