Mail Archives: cygwin/2001/07/24/14:44:27
On Tue, Jul 24, 2001 at 12:44:08PM -0400, 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?
Patching sftp-server even if that will result in some... resistance
by the maintainers is appropriate.
Cygwin has to deal with // paths (//server/share/...) and we can't
change that.
If you're able to create a clean and neat patch I will try to
convince the maintainers of openssh.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin AT cygwin DOT com
Red Hat, Inc.
--
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 -