https://bugs.kde.org/show_bug.cgi?id=505234
TraceyC <kde...@tlcnet.info> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[Feature Request] Add GUI |[Feature Request] Add GUI
|in Dolphin to permanently |in Dolphin to permanently
|mount network shares with |mount network shares,
|fstab/systemd integration |manage them, and provide
| |better integration with
| |applications
Resolution|--- |WAITINGFORINFO
Status|REPORTED |NEEDSINFO
CC| |kde...@tlcnet.info
--- Comment #1 from TraceyC <kde...@tlcnet.info> ---
Thanks for sharing this design proposal for Dolphin. There are definitely a
pain points regarding access to Samba shares, and them not appearing as a local
folder. I've personally been frustrated by this. One use case for me is with
music players accessing a music share on a home NAS. Certainly this is not the
only use case, just one example.
With that said, I'm going to change the summary of this request, and provide a
little perspective. I think the goal, as I understand it, is worthy. The
suggested implementation details may not be the best way to achieve it. There
are existing design choices and constraints that may not be immediately
obvious. I'll forward this to the Dolphin developers to consider.
One serious limitation is that Dolphin, and indeed the system, can hang when a
mount in /etc/fstab becomes unavailable. For instance see bug 423187 and bug
423187. Mounts in /etc/fstab that aren't available at boot time cause issues as
well.
As a note, the ability to store credentials for a remote share already exists.
For instance, I've saved credentials for a couple of samba shares in KWallet
(at the auto prompt when I first accessed them).
Finally, I'd like to ask you for more detail about one thing. Can you expand on
what you mean by "mount shares permanently"?. What exactly would that allow a
user to do that is not possible with the current functionality of Dolphin? I
don't mean "create an fstab / systemd entry", I'm asking what that enables for
the user? The better we understand the desired behavior, the better we can
address this. Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
