Mail Archives: cygwin/2001/07/24/15:57:50
On Tue, Jul 24, 2001 at 12:51:53PM -0400, Larry Hall (RFK Partners, Inc) wrote:
>At 12:44 PM 7/24/2001, Mark Bradshaw wrote:
>>SFTP server has some unfortunate logic that occurs when you try to ls, get,
>>or put things in root (/). It's got logic all over the place that creates
>>paths that start with "//". Cygwin doesn't like to deal with these kind of
>>paths. <grin> This causes ls, get, and put (at least) to not work in /.
>>
>>When you do an ls (for example) sftp server creates pathnames to pass back.
>>It does this by combining the path + "/" + filename. This works great as
>>long as the path doesn't includes a final /, which it normally doesn't.
>>However, when you switch to / the path is / (obviously). The ls would then
>>end up coming back with things like //., //.., //cygwin.bat, etc.
>>
>>Seems that unix machines deal with these double slash paths, but cygwin
>>doesn't? Am I on track here. Either way, I'm wondering which direction is
>>the best to attempt a patch with. Patch sftp-server.c in lots of spots, or
>>cygwin in (?) spots?
>
>An argument could be made either way but I would suggest that its best to
>make SFTP as portable as possible. In that context, patching SFTP is
>best.
I don't see any argument for patching cygwin. A '//' means something
special to cygwin, it is allowed to mean something special, and cygwin
is not the only system that interprets '//' as special.
I don't see how you could possibly patch cygwin to deal with this. Obviously
you can't do something like "Does //foo exist? Yes. Ok, I'll use that rather
than use the //foo share." Or, I hope it is obvious why this logic is flawed.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -