Bug 120670 - Why must set the directory in a SSH access?
Summary: Why must set the directory in a SSH access?
Status: CONFIRMED
Alias: None
Product: knetattach
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
: 176196 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-01-23 20:50 UTC by Iñaki Baz Castillo
Modified: 2013-01-16 17:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Iñaki Baz Castillo 2006-01-23 20:50:55 UTC
Version:           desconocido (using KDE 3.5.0, Debian Package 4:3.5.0-3 (testing/unstable))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.14

I want to create a SSH (FISH) access, so the only I need is to set the host and the user. No more. But KNetAttach forces me to set a "directory", why? If I don't set the directory I can't press "Next" button so I can't finish.

In console, if I want to access to a SSH server I write:
  #> ssh user@host
Just it. In this way I go to user's home in the server.

If I want to go to a different directory I write:
  #> ssh user@host:/usr/share/

But the logical access is the first one, and KNetAttach makes it not easy because I need to write "/home/user" in "directory" field.

I think KNetAttach should allow to leave "directory" in blank and then access to "fish:/user@host". Just it.

I'd like the same using SFTP, but this is another wish.   ;)

Bye.
Comment 1 Jekyll Wu 2012-01-07 23:03:02 UTC
*** Bug 176196 has been marked as a duplicate of this bug. ***