After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 354249 - invalid entries in /etc/fstab should be filtered out
invalid entries in /etc/fstab should be filtered out
Status: RESOLVED WONTFIX
Product: gnome-vfs
Classification: Deprecated
Component: Volume and drive handling
2.16.x
Other Linux
: Normal enhancement
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
Depends on:
Blocks:
 
 
Reported: 2006-09-04 10:33 UTC by Sebastien Bacher
Modified: 2008-09-06 18:55 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Sebastien Bacher 2006-09-04 10:33:31 UTC
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/gnome-vfs2/+bug/42810

"Hello, I was wondering if it were possible to have gnome-vfs filter out all those /etc/fstab entries which refer to devices being no longer valid. The /etc/fstab is created at install time and entries are populated according to the block devices found on the system during setup, a typical example in this respect is the cd-rom drive. Problem is, if the user later on moves the cd-drive to a different IDE channel, the corresponding /etc/fstab entry is invalidated. Actually this is not a serious issue, because gnome-vfs would get the new device node through HAL, problem is we will end with a "bogus" cd-rom drive showing up in nautilus. Actually, an easy workaround would be removing any reference to cd-rom drives from /etc/fstab altogether, since most desktop apps seem to rely on HAL nowadays: pmount is a valid example in this respect, it will still work even if no fstab entry is provided for the device which is being mounted. On the other hand, some don't: gnomebaker is one of these. Regards, andre"
Comment 1 Christof Krüger 2007-01-26 13:53:11 UTC
Could some dev explain the semantics of a drive being marked as user_visible? Because i had such a dead entry in my fstab and the corresponding gnome-vfs drive had this flag set. The same happens to entries that are not valid at boot time (e.g. for usb mass storage devices). Such devices can't be mounted at the moment as they are not available. So why are they flagged as user_visible?

This is related to bug #354249.
Comment 2 Christof Krüger 2007-01-26 13:55:50 UTC
Sorry for the bugspam. The bug number above should have been #332906.
Comment 3 André Klapper 2008-09-06 18:55:04 UTC
gnome-vfs has been deprecated and superseded by gio/gvfs since GNOME 2.22, hence mass-closing many of the gnome-vfs requests/bug reports. This means that gnome-vfs is NOT actively maintained anymore, however patches are still welcome.

If your reported issue is still valid for gio/gvfs, please feel free to file a bug report against glib/gio or gvfs.

@Bugzilla mail recipients: query for
      gnome-vfs-mass-close
to get rid of this notification noise all together.


General further information: http://en.wikipedia.org/wiki/GVFS 
Reasons behind this decision are listed at http://www.mail-archive.com/gnome-vfs-list@gnome.org/msg00899.html