delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2001/07/24/15:00:05

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <911C684A29ACD311921800508B7293BA010A8AB9@cnmail>
From: Mark Bradshaw <bradshaw AT staff DOT crosswalk DOT com>
To: "'Corinna Vinschen'" <cygwin AT cygwin DOT com>
Subject: RE: SFTP server when / is c:\
Date: Tue, 24 Jul 2001 14:50:14 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)

I've done the patches.  I'll polish 'em up and send them to you.  It
comprises one patch to the client, and one patch to the server.  All-in-all,
less than I anticipated.

Mark

-----Original Message-----
From: Corinna Vinschen [mailto:cygwin AT cygwin DOT com]
Sent: Tuesday, July 24, 2001 2:27 PM
To: 'cygwin AT cygwin DOT com'
Subject: Re: SFTP server when / is c:\


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/

--
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 -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019