01-07-2015, 10:52 PM
(This post was last modified: 01-07-2015, 10:56 PM by greenisland.)
Thank you Dave. The reason for my issue is that I use a couple of programs that seem to work well when a network drive is "mounted" but do not work so well (or at all) when the connection is just a smb share such as gigolo sets up. I don't know enough to understand the difference but maybe I can find a link from another forum. At any rate, thank you for your efforts so far.
Here is something I read some time ago that gave a stab and explaining the difference:
Here is something I read some time ago that gave a stab and explaining the difference:
"Is there any difference technically in the resulting connection between (1) adding the entry in fstab, and (2) using Dolphin in KDE to navigate over to the share?
I realize that the fstab entry is "permanent" but I don't know if I should worry about getting it right in fstab if going through Dolphin creates the same technical result.
Yes, there is.
Using fstab will mount the network into the local filesystem, making it available to any other process like any other file. It is completely application agnostic, and more in-line with the original Unix/Linux filesystem ideology.
Accessing it though Dolphin uses "kioslaves" (or, whatever their current KDE4 equivalent may be), without making the files "locally accessible". Only (probably KDE/QT) aware applications will be able to properly access them, in even in those case, they may actually copy the file to "tmp" before accessing it. This is most noticeable, for example, if you try to use LibreOffice in this way...opening the file will probably fail.
Personally, I would recommend the fstab approach, or manually (either at the command line, or through a batch file) mounting the resource into the local filesystem.
One thing I've noticed, that may be worth note, when I've manually mounted SMB shares: on occasions where I've failed to un-mount them prior to shutting down or rebooting, the process would hang and require a hard boot. I'm not 100% certain, but if it is in fstab, then un-mounting all mounted drives is part of the shut down process.
I realize that the fstab entry is "permanent" but I don't know if I should worry about getting it right in fstab if going through Dolphin creates the same technical result.
Yes, there is.
Using fstab will mount the network into the local filesystem, making it available to any other process like any other file. It is completely application agnostic, and more in-line with the original Unix/Linux filesystem ideology.
Accessing it though Dolphin uses "kioslaves" (or, whatever their current KDE4 equivalent may be), without making the files "locally accessible". Only (probably KDE/QT) aware applications will be able to properly access them, in even in those case, they may actually copy the file to "tmp" before accessing it. This is most noticeable, for example, if you try to use LibreOffice in this way...opening the file will probably fail.
Personally, I would recommend the fstab approach, or manually (either at the command line, or through a batch file) mounting the resource into the local filesystem.
One thing I've noticed, that may be worth note, when I've manually mounted SMB shares: on occasions where I've failed to un-mount them prior to shutting down or rebooting, the process would hang and require a hard boot. I'm not 100% certain, but if it is in fstab, then un-mounting all mounted drives is part of the shut down process.