The current DOS path handling in the FTP server is kind of broken - it 
works for some clients, but not for others.  Ironically, the smarter the 
FTP client the less likely it is to work.

The problem has to do with exposing drive letters in the path.  
Filezilla in particular detects the drive letter and assumes DOS style 
paths, with backslashes as the directory delimiter.  If I use a drive 
letter but use forward slashes in the FTP server Filezilla gets confused 
but then the Unix clients are happy.  There is no winning unless I start 
putting some non-standard mode selection commands in.

The universal solution is to make everything look like a Unix 
fileystem.  To handle drive letters I'm thinking of using something like 
/drive_x/ as the first part of the path.  For example, if your current 
working directory is "/" then you are at the "root" with no logged 
drive.  All you can do is see a list of available drives with each being 
shown in /drive_x/ format.  If you wanted to traverse the C: drive you 
would go to "/drive_c/" and work from there.

A side effect of this is that the root directory ('/') is virtual, and 
really doesn't exist.  When you are in the root directory you have to CD 
to a drive letter or do a file list; there are no other file-type 
commands you can use there.

This is kind of a big change so I'd like to see if anybody can spot any 
flaws in it ahead of time.  Users "in a sandbox" are not affected, as 
they have always seen a Unix style path and have not been exposed to 
drive letters.


All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
Freedos-user mailing list

Reply via email to