Re: Bug: Setup tool doesn't respect managed mountpoints/filesystems

Jason Pyeron wrote: > could you forward the link for th IFS SDK? > > I would like to have the license reviewed, etc. It's the first hit on a google for "ifs ddk microsoft": . Brian -- Unsubscribe info: http://cygwin.com/ml/#unsub

Re: Bug: Setup tool doesn't respect managed mountpoints/filesystems

Igor Pechtchanski wrote: > If either everything or nothing is encoded, that's only 2 possibilities. > I originally thought that it would be enough to encode the differing > characters, but therein lies madness, as you observed. Right, I think that's what I was incorrectly thinking of. > Not "nea

Re: Bug: Setup tool doesn't respect managed mountpoints/filesystems

could you forward the link for th IFS SDK? I would like to have the license reviewed, etc. On Mon, 19 Sep 2005, Brian Dessent wrote: Mark Paulus wrote: Has anyone explored the option of an IFS that would implement the cygwin managed filesystem semantics, but it would be transparent to all cy

Re: Bug: Setup tool doesn't respect managed mountpoints/filesystems

On Mon, 19 Sep 2005, Brian Dessent wrote: > Igor Pechtchanski wrote: > > > Which was what I said in the part you snipped. > > My skimming skills are not great today. :( No problem... > > > Repeat for "readme" vs. "Readme" and every other of billions of > > > permutation of case. I see no way t

Re: Bug: Setup tool doesn't respect managed mountpoints/filesystems

Mark Paulus wrote: > Has anyone explored the option of an IFS that would implement the cygwin > managed filesystem semantics, but it would be transparent to all > cygwin apps. From the brief investigation I have done, it appears there would > need to be 2 flavors, 9x/ME & NT/2K/XP, but that would

Re: Bug: Setup tool doesn't respect managed mountpoints/filesystems

Igor Pechtchanski wrote: > Which was what I said in the part you snipped. My skimming skills are not great today. :( > > Repeat for "readme" vs. "Readme" and every other of billions of > > permutation of case. I see no way this wouldn't turn into a nightmare. > > Huh? Why would you need to t

Re: Bug: Setup tool doesn't respect managed mountpoints/filesystems

On Mon, 19 Sep 2005 15:48:01 -0400 (EDT), Igor Pechtchanski wrote: >On Mon, 19 Sep 2005, Brian Dessent wrote: >> Igor Pechtchanski wrote: >> >> > Yes, there are issues to work out here, but they are not very different >> > from, say, those arising when two programs try creating a file with the >>

Re: Bug: Setup tool doesn't respect managed mountpoints/filesystems

On Mon, 19 Sep 2005, Brian Dessent wrote: > Igor Pechtchanski wrote: > > > Yes, there are issues to work out here, but they are not very different > > from, say, those arising when two programs try creating a file with the > > same name simultaneously... In fact, the case-insensitivity of both NT

Re: Bug: Setup tool doesn't respect managed mountpoints/filesystems

On Mon, Sep 19, 2005 at 03:10:52PM -0400, Igor Pechtchanski wrote: >On Mon, 19 Sep 2005, Brian Dessent wrote: > >> Igor Pechtchanski wrote: >> >> > OTOH, one of the changes that would be worth making in the managed mount >> > code is to leave the filename alone unless there's a clash, in which case

Re: Bug: Setup tool doesn't respect managed mountpoints/filesystems

Igor Pechtchanski wrote: > Yes, there are issues to work out here, but they are not very different > from, say, those arising when two programs try creating a file with the > same name simultaneously... In fact, the case-insensitivity of both NTFS > and VFAT plays into our hands here, as you say

Re: Bug: Setup tool doesn't respect managed mountpoints/filesystems

On Mon, 19 Sep 2005, Brian Dessent wrote: > Igor Pechtchanski wrote: > > > OTOH, one of the changes that would be worth making in the managed mount > > code is to leave the filename alone unless there's a clash, in which case > > the clashing filename becomes encoded. > > But then any file creatio

Re: Bug: Setup tool doesn't respect managed mountpoints/filesystems

Igor Pechtchanski wrote: > OTOH, one of the changes that would be worth making in the managed mount > code is to leave the filename alone unless there's a clash, in which case > the clashing filename becomes encoded. But then any file creation/renaming operation would have to check and see if the

Re: Bug: Setup tool doesn't respect managed mountpoints/filesystems

On Mon, 19 Sep 2005, Mark Paulus wrote: > My company just replaced my desktop with a laptop, and in the > migration process, I am getting my cygwin install set back up. > Two changes I had made before was to mount /usr/src and /usr/share > as managed filesystems (I have a directory c:\cygmanaged w

Re: Bug: Setup tool doesn't respect managed mountpoints/filesystems

Mark Paulus wrote: > So, it appears that the installer is respecting the mount point, but > it isn't respecting the managed attribute of the filesystem/mountpoint. setup.exe itself is not a Cygwin program (does not use cygwin1.dll) and has no idea what a managed mount is. You will have to limit

Bug: Setup tool doesn't respect managed mountpoints/filesystems

My company just replaced my desktop with a laptop, and in the migration process, I am getting my cygwin install set back up. Two changes I had made before was to mount /usr/src and /usr/share as managed filesystems (I have a directory c:\cygmanaged where share and src live). While doing some cl