links broken during a backup (not restore), need more info on how they work to fix file bug with vendor

2008-05-16 Thread vapid vapid
Hi, I believe my backup program (CMS ABS Bounceback) is mucking with the links in my cygwin and work directories when it is creating a backup. It doesn't appear to affect links created by windows, only those created by cygwin. I don't fully understand the cygwin links: there are some that

Re: links broken during a backup (not restore), need more info on how they work to fix file bug with vendor

2008-05-16 Thread Igor Peshansky
On Fri, 16 May 2008, vapid vapid wrote: Hi, I believe my backup program (CMS ABS Bounceback) is mucking with the links in my cygwin and work directories when it is creating a backup. It doesn't appear to affect links created by windows, only those created by cygwin. I don't fully

Re: links broken during a backup (not restore), need more info on how they work to fix file bug with vendor

2008-05-16 Thread Christopher Faylor
On Fri, May 16, 2008 at 04:30:40PM -0400, Igor Peshansky wrote: On Fri, 16 May 2008, vapid vapid wrote: Hi, I believe my backup program (CMS ABS Bounceback) is mucking with the links in my cygwin and work directories when it is creating a backup. It doesn't appear to affect links created by

Re: links broken during a backup (not restore), need more info on how they work to fix file bug with vendor

2008-05-16 Thread vapid
Thank you for the quick response Igor. You need to use attrib +R on .lnk files and attrib +S on the plain-text links. I swear I tried attrib +R on both types of links earlier, but I must have only tried the plain-text ones. It does fix the .lnk's as you said. I'm using these two [slow]

Re: links broken during a backup (not restore), need more info on how they work to fix file bug with vendor

2008-05-16 Thread vapid vapid
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

Re: links broken during a backup (not restore), need more info on how they work to fix file bug with vendor

2008-05-16 Thread Brian Dessent
[EMAIL PROTECTED] wrote: Maybe someone can come up with a fancier find. I had to spawn a bash to use the and delay the evaluation of the `cygpath {}`. There's a lot of quoting to deal with spaces in filenames. You can speed things up a lot by only running cygpath once, e.g.: (echo @echo

Re: links broken during a backup (not restore), need more info on how they work to fix file bug with vendor

2008-05-16 Thread Christopher Faylor
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

Re: links broken during a backup (not restore), need more info on how they work to fix file bug with vendor

2008-05-16 Thread Igor Peshansky
On Fri, 16 May 2008, vapid wrote: Thank you for the quick response Igor. You need to use attrib +R on .lnk files and attrib +S on the plain-text links. I swear I tried attrib +R on both types of links earlier, but I must have only tried the plain-text ones. It does fix the .lnk's as you