X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 16 May 2008 20:52:29 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: links broken during a backup (not restore), need more info on how they work to fix & file bug with vendor Message-ID: <20080517005229.GA5088@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20080516230238 DOT 49311BE4078 AT ws1-9 DOT us4 DOT outblaze DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080516230238.49311BE4078@ws1-9.us4.outblaze.com> User-Agent: Mutt/1.5.16 (2007-06-09) 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 On Fri, May 16, 2008 at 06:02:38PM -0500, vapid vapid wrote: >> >Just tell them that a backup program has no business clearing "read-only" >> >and "system" attributes on any files. >> >> I would actually expect that they probably are just reading the .lnk >> information and ignoring the cygwin bits. Even if they preserve the >> read-onlyness of the .lnk file, unless they preserve the file in its >> entirety it won't be recognized. > >My issue was that they messed up my disk __during the backup__. I would >be more understanding if it was during the restore. There's no reason >for a backup program to modify my harddisk (unless it's keeping status >in its config/log directory). It should treat my disk as a read >only device. That's for sure. That really seems like a bug. cgf -- 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/