X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org X-OB-Received: from unknown (208.36.123.73) by wfilter.us4.outblaze.com; 16 May 2008 23:02:38 -0000 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 From: "vapid vapid" To: cygwin AT cygwin DOT com Date: Fri, 16 May 2008 18:02:38 -0500 Subject: Re: links broken during a backup (not restore), need more info on how they work to fix & file bug with vendor Message-Id: <20080516230238.49311BE4078@ws1-9.us4.outblaze.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id m4GN3Ahx020241 > >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. -- See Exclusive Video: 10th Annual Young Hollywood Awards http://www.hollywoodlife.net/younghollywoodawards2008/ -- 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/