Re: Command line arguments of ftpfs

[Neal H Walfield]

> The current ftpfs command line argument interface isn't very intuitive,
> for example most people would expect that
> 
> settrans -c /ftp /hurd/hostmux /hurd/ftpfs
> 
> works (but it doesn't since you one has add an additional "/" argument
> at the end. I think it would be a good idea to have / be the default
> directory on the ftp server, and while I volunteer to make the
> modification, I would like to hear if there are any particular reasons
> for the current command line argument interface ("ftpfs [OPTION...]
> REMOTE_FS [SERVER]"). I.e. is there a reason to stay compatible with the
> current one?

The reason that we use this order is so that it works easily with
hostmux.  E.g.

        settrans -ac ftp /hurd/hostmux /hurd/ftpfs /

I think that it would, however, be reasonable to change the behavior
of ftpfs to assume that the notation will always be:

        host.domain/path

with an optional ftp:// prepended.