Registered Member
|
Unfortunately, non-KDE apps do not handle the KIO slaves very well. Basically, all non-KDE apps qualify as such. It would therefore be great to be able to mount an SMB share to ~/smb4k or any other mountpoint directly from Dolphin / Konqueror.
Idea is to use Dolphin / Konqueror to navigate the network, open an SMB share and then allow the user to mount the share via a context menu.
XiniX, proud to be a member of KDE forums since 2008-Oct.
|
Administrator
|
The reason behind this is not implemented is likely one of the following:
Implementation would be platform specific Implementation could lead to system lockups when remote systems go down.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
I think it would be the same as mounting via smb4k, except you don't need to fire up an extra app for it.
XiniX, proud to be a member of KDE forums since 2008-Oct.
|
Registered Member
|
I'm with Xinix - just yesterday my wife borrowed my laptop, wrote a doc in OpenOffice, then wanted to save it to our server. The share was there in Places but I could not easily mount it anywhere for Openoffice to use. In the end, I had to save it locally, then copy it where I needed it. Pretty poor really.
Si |
Registered Member
|
Thanks for the program. I have been looking for a good way to get VLC to read from my network share w/o having to have VLC buffer the entire thing to a temp directory. Including this functionality into dolphin would be a big plus for me. |
Registered Member
|
but nautilus does it !!! and it is very nice feature |
Registered Member
|
The same with NFS mount-points... I have 2 NFS dir shares setup in "/etc/fstab" but there's no manner to mount it directly in Dolphin.
I just can create an "device link" in a folder and mount it, but I can't add it to "places", as usb-drive or EXT3 extra partition. Thanks for your work! |
Registered Member
|
http://wiki.kde.org/tiki-index.php?page ... se+Gateway
I think this would fix most KIO problems for non-KDE apps, but I am not sure if it is still in development. |
Administrator
|
The fact that Nautilus does it is not valid. It won't be a nice feature when a users system suffers a fileio lockup which locks their desktop completely, causing loss of all work when the server goes down.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
I am not convinced it cannot work. What is so difficult about detecting KDE runs on Linux and then using the smb4k code to mount the share? I think the first thing is to establish if this is a valid idea. And if it is, there is surely a way to make it work
XiniX, proud to be a member of KDE forums since 2008-Oct.
|
Administrator
|
The best way would be to use the FUSE solution outlined above, which will allow usage of all KIO slaves, if it was to be implemented.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Do you mean that this happens in Gnome? I have a lot of sshfs (fuse) mount to my local server. I use it over a wireless link and so far not a single application hung. Amarok even starts playing again as soon a the link goes up! Can't you guys steal/borrow gvfs2 (which nautilus uses to do its mount-magic)? It's GPL, it's free game. |
Administrator
|
bratwurst: The SSH protocol is really good at resuming broken connections. I wouldn't be surprised if sshfs implements some special handling to prevent the system from freezing, probably by saying "File Not available" or something.
There is already a FUSE plugin for KIO in playground I think.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Moderator
|
Deleted bratwurst's post instead of him.
Primoz, proud to be a member of KDE forums since 2008-Nov.
|
Registered Member
|
Since I wrote my last post in this thread I have experienced the lockups you talk about, and I agree, they're nasty. Is it an utopia to have remote systems mounted over very lossy links (without lockups)? :'( Windows seems to behave pretty well in this situation without virtual filesystems. Well, the one thing I wonder about, and it's maybe beyond the scope of this thread but I really what to know: On which level occurs the hanging problem? The kernel, the filesystem implementation, or the user level application? It guess it can't be expected that every application reads data from a "dataread" thread with a timeout, but something like that must surely be implemented in a filesystem intended to work over a network? |
Registered users: abc72656, Bing [Bot], daret, Google [Bot], Sogou [Bot], Yahoo [Bot]