[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: kfm symlink-bug
From:       Dawit Alemayehu <adawit () earthlink ! net>
Date:       1999-02-01 17:32:14
[Download RAW message or body]

David Faure wrote:

> On Sun, Jan 31, 1999 at 03:05:04AM -0500, Dawit Alemayehu wrote:
> >
> > Stefan Siegel wrote:
> >
> > > Hi,
> > >
> > > i just tried to log on "ftp://ftp.uni-kl.de/pub/", using kfm. The
> > > problem i found:
> > > All the Files shown by kfm are "unknown symlinks" but they should be
> > > symlinks to folders.
> This is a known problem, due to the fact that stat() doesn't exist for ftp,
> (of course!), so how could kfm know what the symlink is pointing to ?
> Only by going the the directory where the target is, and then listing its
> contents to get whether it's file or a directory. (Remember, the link can
> point to a file or dir in another directory...)
> Such a complicated algorithm isn't implemented in the current kfm, and
> obviously won't be - Torben, looks like another feature request for kfm III.
>
> (How does such a site behave in another graphical ftp client (llnl*, wsftp) ?
> I'd be surprised if the correct icons appeared...)

Works okay in Netscape 4.07 ...


> > > When clicking on the icons (e.g. informatik) kfm shows an alert-box,
> > > saying that the file does
> > > not exist, i have to add a slash in the location line manually, to
> > > navigate on.
> > > I think this is a bug which should be solved before 1.1.
> > >
> > > Greetings,
> > >                   Stefan
> >
> > Aye! I was able to reproduce this problem too.  The links in the ftp
> > site you mentioned are missing a trailing "/".  This causes kfm to
> > interpret these links as "unknown file symlinks" instead of "directory
> > symlinks".   This is a tricky one.
>
> Ah. Who is guilty then ? The site or kfm ? :)))
> (kidding).  Well, the problem is the same, in fact.
> Sorry, I see no way of fixing it easily, especially before 1.1.

The site of course!! But you already knew that :-)  After spending sometime on
it, I did not it can be fixed for 1.1 either.

[prev in list] [next in list] [prev in thread] [next in thread]