Re: CIFS symlinks on network share break Cygwin

"Dave Korn" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > On 07 February 2008 00:22, Matt Seitz wrote: > >> "Dave Korn" wrote in message >> news:[EMAIL PROTECTED] > > I did?! It was email when *I* last saw it! > Sorry for any confusion. I'm using the GMane mail to nntp gateway

RE: CIFS symlinks on network share break Cygwin

On 07 February 2008 00:22, Matt Seitz wrote: > "Dave Korn" wrote in message > news:[EMAIL PROTECTED] I did?! It was email when *I* last saw it! >> My win32 "T:" drive is a netapp share (CIFS with NFS perms) > I'm assuming you mean "T: maps to a CIFS share that points to a volume or > QTre

Re: CIFS symlinks on network share break Cygwin

"Dave Korn" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > Oops, pardon. I thought I had posted this yesterday but now I see it's just > lying around my drafts folder. My win32 "T:" drive is a netapp share (CIFS > with NFS perms) > and /win/t is a mountpoint to it (system, bin

Re: CIFS symlinks on network share break Cygwin

On Feb 6 11:13, Corinna Vinschen wrote: > On Feb 5 12:08, Jonathan Lanier wrote: > > And that > > gives me a totally crazy idea - wouldn't it be nice if there were a > > standardized, open set of extensions to allow Windows applications to > > access native symlinks, attributes, and permissions

Re: CIFS symlinks on network share break Cygwin

On Feb 5 20:24, Dave Korn wrote: > On 05 February 2008 14:27, Corinna Vinschen wrote: > > you didn't answer my first question. What exactly happens with the perms? > > To what values are they set when creating a file? > > Oops, pardon. I thought I had posted this yesterday but now I see it's

Re: CIFS symlinks on network share break Cygwin

On Feb 5 12:08, Jonathan Lanier wrote: > And that > gives me a totally crazy idea - wouldn't it be nice if there were a > standardized, open set of extensions to allow Windows applications to > access native symlinks, attributes, and permissions over remote network > shares? If there were such

RE: CIFS symlinks on network share break Cygwin

On 05 February 2008 14:27, Corinna Vinschen wrote: > On Feb 5 13:48, Dave Korn wrote: >> On 05 February 2008 13:35, Corinna Vinschen wrote: >> >>> What exactly happens with the perms? Are you using CYGWIN=smbntsec? > > you didn't answer my first question. What exactly happens with the perms?

RE: CIFS symlinks on network share break Cygwin

>> Yep, and it doesn't help. It's solely down to the secureshare >> stuff not presenting through the standard NT api; it's only visible >> by using the shell extension dll. >> >> (... which makes me wonder, could we possibly leverage that to do >> some useful work for us in these situations.

Re: CIFS symlinks on network share break Cygwin

On Feb 5 13:48, Dave Korn wrote: > On 05 February 2008 13:35, Corinna Vinschen wrote: > > > What exactly happens with the perms? Are you using CYGWIN=smbntsec? you didn't answer my first question. What exactly happens with the perms? To what values are they set when creating a file? > > Ye

RE: CIFS symlinks on network share break Cygwin

On 05 February 2008 13:35, Corinna Vinschen wrote: > What exactly happens with the perms? Are you using CYGWIN=smbntsec? Yep, and it doesn't help. It's solely down to the secureshare stuff not presenting through the standard NT api; it's only visible by using the shell extension dll. (...

Re: CIFS symlinks on network share break Cygwin

On Feb 5 01:22, Dave Korn wrote: > On 05 February 2008 00:32, Jonathan Lanier wrote: > > > OK, so in addition to commenting out the SE_BACKUP_PRIV line in > > sec_helper.cc, I also had to comment out the SE_RESTORE_PRIV line. The > > former broke calls to GetFileAttributes(), and the latter brok

Re: CIFS symlinks on network share break Cygwin

On Feb 4 18:34, Jonathan Lanier wrote: > > We use netapp here too, and we have a mixed NTFS/NT ACLS + > > NFS/Unix perms domain. None of it works well for me from the > > cygwin side, I always find myself having to use the win > > explorer shell extension to change the perms. If I can help > >

RE: CIFS symlinks on network share break Cygwin

> We use netapp here too, and we have a mixed NTFS/NT ACLS + > NFS/Unix perms domain. None of it works well for me from the > cygwin side, I always find myself having to use the win > explorer shell extension to change the perms. If I can help > with some testing or diagnosis or anything, pleas

RE: CIFS symlinks on network share break Cygwin

On 05 February 2008 00:32, Jonathan Lanier wrote: > OK, so in addition to commenting out the SE_BACKUP_PRIV line in > sec_helper.cc, I also had to comment out the SE_RESTORE_PRIV line. The > former broke calls to GetFileAttributes(), and the latter broke calls to > FindFirstFile(). Commenting ou

RE: CIFS symlinks on network share break Cygwin

OK, so in addition to commenting out the SE_BACKUP_PRIV line in sec_helper.cc, I also had to comment out the SE_RESTORE_PRIV line. The former broke calls to GetFileAttributes(), and the latter broke calls to FindFirstFile(). Commenting out both of them seems to fix everything in Cygwin. NetApp m

RE: CIFS symlinks on network share break Cygwin

> On Mon, Feb 04, 2008 at 11:05:18AM -0800, Jonathan Lanier wrote: >> Any comments from NetApp? Doesn't, like, Christopher Faylor work for >> them, or something? :) I've been told that they troll here... > > I work for them but I'm neither a troll nor am I involved > Netapp technical support.

Re: CIFS symlinks on network share break Cygwin

On Mon, Feb 04, 2008 at 11:05:18AM -0800, Jonathan Lanier wrote: >Any comments from NetApp? Doesn't, like, Christopher Faylor work for >them, or something? :) I've been told that they troll here... I work for them but I'm neither a troll nor am I involved Netapp technical support. The only oth

RE: CIFS symlinks on network share break Cygwin

> On Feb 1 18:06, Jonathan Lanier wrote: >> Newer versions of Cygwin appear to be incompatible with Windows >> network shares on CIFS servers. This incompatibility arises due to >> the fact that the Windows OS seems to return unexpected values for >> file/directory information if the file/directo

Re: CIFS symlinks on network share break Cygwin

On Feb 1 18:06, Jonathan Lanier wrote: > Newer versions of Cygwin appear to be incompatible with Windows network > shares on CIFS servers. This incompatibility arises due to the fact > that the Windows OS seems to return unexpected values for file/directory > information if the file/directory is

CIFS symlinks on network share break Cygwin

OK, so, to resurrect this issue from... oh, about 1.5 years ago (see my post on Oct 22 2006)... :P Sorry for not getting back with more on this earlier, but I have been busy. Since it was going to be difficult to track down I ended up reverting to the older, working Cygwin. To quickly (re)summa

Re: 1.5.21-1: CIFS symlinks on network share break Cygwin

On Wed, 25 Oct 2006, DePriest, Jason R. wrote: > On 10/24/06, Larry Hall (Cygwin) <> wrote: > > I'm not sure everyone is paying full attention here. > > again. Reformatted. > > The entry just defines TOFU: > Text Over, Full-quote Under (or, in the original Germa

Re: Problem reporting (was 1.5.21-1: CIFS symlinks on network share break Cygwin)

On Wed, Oct 25, 2006 at 06:28:37PM -0400, Larry Hall (Cygwin) wrote: >Christopher Faylor wrote: >>On Wed, Oct 25, 2006 at 03:07:19PM -0500, DePriest, Jason R. wrote: >>>On 10/25/06, DePriest, Jason R. <> wrote: On 10/25/06, Larry Hall (Cygwin) <> wrote: >Certainly this and quoting raw email

Re: Problem reporting (was 1.5.21-1: CIFS symlinks on network share break Cygwin)

Christopher Faylor wrote: On Wed, Oct 25, 2006 at 03:07:19PM -0500, DePriest, Jason R. wrote: On 10/25/06, DePriest, Jason R. <> wrote: On 10/25/06, Larry Hall (Cygwin) <> wrote: Certainly this and quoting raw email addresses could be offered as guidelines in .

Re: 1.5.21-1: CIFS symlinks on network share break Cygwin

DePriest, Jason R. wrote: On 10/25/06, Larry Hall (Cygwin) <> wrote: Certainly this and quoting raw email addresses could be offered as guidelines in . Care to offer a patch? The "submitting a patch" guidelines seem to refer to program patches... since this is

Re: Problem reporting (was 1.5.21-1: CIFS symlinks on network share break Cygwin)

On Wed, Oct 25, 2006 at 03:07:19PM -0500, DePriest, Jason R. wrote: >On 10/25/06, DePriest, Jason R. <> wrote: >>On 10/25/06, Larry Hall (Cygwin) <> wrote: >>> Certainly this and quoting raw email addresses could be offered as >>> guidelines in . Care to offer a >>

Problem reporting (was 1.5.21-1: CIFS symlinks on network share break Cygwin)

On 10/25/06, DePriest, Jason R. <> wrote: On 10/25/06, Larry Hall (Cygwin) <> wrote: > Certainly this and quoting raw email addresses could be offered as > guidelines in . Care to offer a > patch The "submitting a patch" guidelines seem to refer to program patch

Re: 1.5.21-1: CIFS symlinks on network share break Cygwin

On 10/25/06, Larry Hall (Cygwin) <> wrote: Certainly this and quoting raw email addresses could be offered as guidelines in . Care to offer a patch The "submitting a patch" guidelines seem to refer to program patches... since this is only an HTML update, here i

Re: 1.5.21-1: CIFS symlinks on network share break Cygwin

Jonathan Lanier wrote: If anyone could direct me to an ftp or http archive of the older Cygwin distributions, it would be much appreciated. Thanks! See: http://www.google.com/search?hl=en&lr=&q=%22cygwin+time+machine%22&btnG=Search Particularly: http://www.fruitbat.org/Cygwin/index.html#cygwi

Re: TOFU (was: 1.5.21-1: CIFS symlinks on network share break Cygwin)

DePriest, Jason R. wrote: On 10/24/06, Larry Hall (Cygwin) <> wrote: I'm not sure everyone is paying full attention here. again. Reformatted. The entry just defines TOFU: Text Over, Full-quote Under (or, in the original German, "Text Oben, Fullquote Unten").

RE: 1.5.21-1: CIFS symlinks on network share break Cygwin

(PCYMTNQREAIYR, TOFU, grokked; apologies - haven't been on this list for about 9 years...) >> One completely wild guess would be that there is some attribute >> associated with the process that might expose the native symlinks, >> possibly for improved compatibility with SFU/Posix and CIFS; > > C

Re: 1.5.21-1: CIFS symlinks on network share break Cygwin

DePriest, Jason R. wrote: On 10/24/06, Larry Hall (Cygwin) <> wrote: I'm not sure everyone is paying full attention here. again. Reformatted. The entry just defines TOFU: Text Over, Full-quote Under (or, in the original German, "Text Oben, Fullquote Unten").

Re: 1.5.21-1: CIFS symlinks on network share break Cygwin

On 10/24/06, Larry Hall (Cygwin) <> wrote: I'm not sure everyone is paying full attention here. again. Reformatted. The entry just defines TOFU: Text Over, Full-quote Under (or, in the original German, "Text Oben, Fullquote Unten"). A combination of top posti

Re: 1.5.21-1: CIFS symlinks on network share break Cygwin

On Oct 24 11:08, Jonathan Lanier wrote: > One completely wild guess would be that there is some attribute > associated with the process that might expose the native symlinks, > possibly for improved compatibility with SFU/Posix and CIFS; Cygwin processes are ordinary Win32 processes, just linked a

Re: 1.5.21-1: CIFS symlinks on network share break Cygwin

nd, more importantly, <http://cygwin.com/acronyms/#PCYMTNQREAIYR> again. Let's not make life any easier for spammers, eh? Sent: Wednesday, October 25, 2006 12:58 PM Subject: Re: 1.5.21-1: CIFS symlinks on network share break Cygwin You too. <http://cygwin.com/acronyms/#TOFU>. Reforma

Re: 1.5.21-1: CIFS symlinks on network share break Cygwin

Message - From: "Larry Hall (Cygwin)" <[EMAIL PROTECTED]> To: Sent: Wednesday, October 25, 2006 12:58 PM Subject: Re: 1.5.21-1: CIFS symlinks on network share break Cygwin You too. <http://cygwin.com/acronyms/#TOFU>. Reformatted. Jonathan Lanier wrote: -Orig

Re: 1.5.21-1: CIFS symlinks on network share break Cygwin

n com Yikes! Ditto - <http://cygwin.com/acronyms/#PCYMTNQREAIYR>. Thanks. Subject: Re: 1.5.21-1: CIFS symlinks on network share break Cygwin <http://cygwin.com/acronyms/#TOFU>. Reformatted. Champ Mendis wrote: - Original Message - From: &

RE: 1.5.21-1: CIFS symlinks on network share break Cygwin

/#PCYMTNQREAIYR>. Thanks. > Sent: Wednesday, October 25, 2006 8:47 AM > Subject: Re: 1.5.21-1: CIFS symlinks on network share break Cygwin > > >> Jonathan Lanier wrote: >>> Well, I thought of that - first rule of debugging, calculatus >>> eliminatus. I tried it

Re: 1.5.21-1: CIFS symlinks on network share break Cygwin

Sent: Wednesday, October 25, 2006 8:47 AM Subject: Re: 1.5.21-1: CIFS symlinks on network share break Cygwin Jonathan Lanier wrote: Well, I thought of that - first rule of debugging, calculatus eliminatus. I tried it; but, attempts to use the older DLLs with newer apps (or vice-versa) resul

Re: 1.5.21-1: CIFS symlinks on network share break Cygwin

run in DOS mode but it failed. I will also try the same thing as Jonathan says. Thanks, Champ - Original Message - From: "Larry Hall (Cygwin)" <[EMAIL PROTECTED]> To: Sent: Wednesday, October 25, 2006 8:47 AM Subject: Re: 1.5.21-1: CIFS symlinks on network sh

Re: 1.5.21-1: CIFS symlinks on network share break Cygwin

Jonathan Lanier wrote: Well, I thought of that - first rule of debugging, calculatus eliminatus. I tried it; but, attempts to use the older DLLs with newer apps (or vice-versa) result in corrupted shared memory, and force me to reboot my WinXP box. I've been under the impression that cygwin1.dl

RE: Re: 1.5.21-1: CIFS symlinks on network share break Cygwin

rom: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Woehlke Sent: Tuesday, October 24, 2006 12:53 PM To: cygwin@cygwin.com Subject: Re: 1.5.21-1: CIFS symlinks on network share break Cygwin Jonathan Lanier wrote: > Also, because (I know the FAQ > says not to say this, but I t

Re: 1.5.21-1: CIFS symlinks on network share break Cygwin

Jonathan Lanier wrote: Also, because (I know the FAQ says not to say this, but I think it's useful information in this case) we have a much older version of Cygwin (cygcheck reports v1.5.14) that works flawlessly with CIFS and does not suffer the same problems. So, at the very least, it appears

RE: 1.5.21-1: CIFS symlinks on network share break Cygwin

> I can't help to think this is a bug in the CIFS server, rather than a bug in Cygwin. That is a tempting conclusion to reach; unfortunately I don't think it's the right one, nor do I think this bug has to blamed on just one or the other. Notice that I ran these tests 3 times, each compiled in a

Re: 1.5.21-1: CIFS symlinks on network share break Cygwin

On Oct 22 22:56, Jonathan Lanier wrote: > Brief summary, before I get into details: Cygwin 1.5.21-1 on WinXP SP2 > was working perfectly, until a new CIFS server was installed on our LAN. > [...] > The common factor to > all failures: they are all symbolic links on the CIFS server. Typical > fa

RE: 1.5.21-1: CIFS symlinks on network share break Cygwin

Sorry for the duplicate post; my mail filter indicated that it had blocked my outgoing message due to the attachment. Apparently, it didn't. :) - Jonathan Lanier -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentati

1.5.21-1: CIFS symlinks on network share break Cygwin

Brief summary, before I get into details: Cygwin 1.5.21-1 on WinXP SP2 was working perfectly, until a new CIFS server was installed on our LAN. Since then, some apps won't run, directories won't list, and many Cygwin-compiled applications are failing to recognize the correct file size, including c

1.5.21-1: CIFS symlinks on network share break Cygwin

Brief summary, before I get into details: Cygwin 1.5.21-1 on WinXP SP2 was working perfectly, until a new CIFS server was installed on our LAN. Since then, some apps won't run, directories won't list, and many Cygwin-compiled applications are failing to recognize the correct file size, including c