Enable the nfs backend
Bug #1637988 reported by
Rui Salvaterra
This bug affects 26 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned | ||
Bionic |
Won't Fix
|
Wishlist
|
Unassigned | ||
Cosmic |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
* Impact
The gio/nautilus nfs:// locations handling is missing
* Test case
Try to connect to/browse a nfs server from nautilus by using a nfs:// location
* Regression potential
It's a new backend being enabled, it shouldn't have an impact on the existing ones
Note that the backend relies on libnfs which got promoted in disco and would need to be promoted in cosmic/bionic as well then
Changed in gvfs (Ubuntu): | |
importance: | Undecided → Wishlist |
tags: | added: sts |
summary: |
- gvfsd-nfs not present in gvfs-backends, why? + Enable the nfs backend |
description: | updated |
To post a comment you must log in.
Just got here when trying to migrate a user from Solaris to Ubuntu (16.04).
It would be nice to get at least some statement why it isn't included/when it might be included.
From what I can see 16.04.1 has gvfs 1.28.2 (e.g. >1.23.90) and libnfs 1.9.8 (e.g. >1.9.7). /mail.gnome. org/archives/ gvfs-list/ 2015-March/ msg00000. html .
That suggests that all prerequisites are covered based on the nfs support announcment post https:/