No easy way to make Samba shares permanent
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ayatana Design |
New
|
Undecided
|
Unassigned | ||
| One Hundred Papercuts |
Invalid
|
Undecided
|
Unassigned | ||
| gvfs (Ubuntu) |
New
|
Wishlist
|
Unassigned | ||
| samba (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
NAS are becoming a popular add-on to people networks, used for every purpose from backing up data to let it be available to multiple PCs on the same (W)LAN. Usually network attached drives are available through a Samba share and the only way to browse them in Ubuntu is going through the Network window.
This makes no easy task to save files on daily basis since there's no easy way to browse the drive from many windows (i.e. save or open windows) except going inside .gvfs folder which is not user friendly. Also, these drives will not be mounted on boot, so in order to use them users must go through the Network window every time (or edit by themselves fstab).
Every time a user browse a Samba share it should be prompted with the option to save them with a panel inside the Nautilus window (like it happens when Ubuntu recognize a Camera when it's browsed with Nautilus) in order to make that samba share automount on every boot.
| Changed in hundredpapercuts: | |
| status: | New → Confirmed |
| Chris Wilson (notgary-deactivatedaccount) wrote | #1 |
| Changed in hundredpapercuts: | |
| status: | Confirmed → Invalid |
| Chuck Short (zulcss) wrote | #2 |
| Changed in samba (Ubuntu): | |
| status: | New → Won't Fix |
| Launchpad Janitor (janitor) wrote | #3 |
| Steve Langasek (vorlon) wrote | #4 |
| affects: | mountall (Ubuntu) → gvfs (Ubuntu) |
| Changed in gvfs (Ubuntu): | |
| importance: | Undecided → Wishlist |
| Changed in gvfs (Ubuntu): | |
| status: | New → Confirmed |
I think a solution to this would be for there to be a permanent entry created in the fstab that would remember the network share each time it was connected. This should happen automatically so that the user does not need to worry about it.
That said, this is not a trivial feature to implement, so I am invalidating it as a paper cut.