X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=debian%2Fpatches%2F04-umount-exit-status.patch;fp=debian%2Fpatches%2F04-umount-exit-status.patch;h=0000000000000000000000000000000000000000;hb=3971bcb9b1a9b0c78916d35836c56119fa92db56;hp=bba5bfd8936bd5596ce1ff01f48da7c42a56b10c;hpb=55d68ec9d81637f142db3320937f8a2a83716044;p=nfs-utils.git

diff --git a/debian/patches/04-umount-exit-status.patch b/debian/patches/04-umount-exit-status.patch
deleted file mode 100644
index bba5bfd..0000000
--- a/debian/patches/04-umount-exit-status.patch
+++ /dev/null
@@ -1,20 +0,0 @@
-mount.c seems to assume that nfsumount() uses standard C true/false
-return values, and inverts them for the exit status (where 0 is
-traditionally considered success). However, nfsumount() consistently
-seems to use 0 for success, and thus a success gets returned as exit
-status 1 and a failure as exit status 0. This confuses at least
-the GNOME drive manager applet, and probably others as well.
-
-Index: nfs-utils-1.1.0/utils/mount/mount.c
-===================================================================
---- nfs-utils-1.1.0.orig/utils/mount/mount.c
-+++ nfs-utils-1.1.0/utils/mount/mount.c
-@@ -371,7 +371,7 @@ int main(int argc, char *argv[])
- 			umount_usage();
- 			exit(1);
- 		}
--		exit(nfsumount(argc, argv) ? 0 : 1);
-+		exit(nfsumount(argc, argv));
- 	}
- 
- 	if(argv[1] && argv[1][0] == '-') {