Your message dated Wed, 13 Nov 2013 09:44:33 -0500 with message-id <[email protected]> and subject line umount: discrepancy between manpage and program has caused the Debian Bug report #533188, regarding umount: discrepancy between manpage and program to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 533188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533188 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: mount Version: 2.15.1~rc1-1 Severity: normal Hi! The umount-manpage states: NOTES The syntax of external umount helpers is: /sbin/umount.<suffix> [-nlfvr] dir | device where the <suffix> is filesystem type or a value from "uhelper=" mtab option. The uhelper (unprivileged umount helper) is possible to used when non-root user wants to umount a mountpoint which is not defined in the /etc/fstab file (e.g devices mounted by HAL). But the uhelper is only called when the uhelper= option is present and not based on filesystem type. A feature which would be really great because I could umount usermounted filesytems like ltspfs (www.ltsp.org, fuse based) with umount. I tried a quick hack (works for me), but I'm not sure about the correctness :-) --- umount.c.orig 2009-05-27 15:37:52.000000000 +0200 +++ umount.c 2009-06-15 15:33:07.000000000 +0200 @@ -492,6 +492,8 @@ if (mc->m.mnt_opts) uhelper = get_value(mc->m.mnt_opts, "uhelper="); + if (!uhelper) + uhelper = mc->m.mnt_type; if (uhelper) { int status = 0; if (check_special_umountprog(arg, arg, -- Jörg Friedrich There are only 10 types of people: Those who understand binary and those who don't.
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message --------BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Version: 2.20.1-5 Looks like this was fixed a while ago. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSg5BRAAoJEJrBOlT6nu754xgIAL9PJkC1Syl8L2sC2smecU45 NwYkK+H2ngL7XpEvltv587XtU6IXuVaZZFCCe3leHtT1XsEgRKFPVbkAGVoTiKEp DEykm5jIUtGTehpViVrqiSQvWn1oGoM0pFStho/bkmoXD7LD6wnGtSzvm/pJ/qyB sFT4e5I6x9sUlSMhR0o+oLdVwFK/dqzIVl2ht2fQyobiHW/O6eZn10wpLhgF1A8j y5GYkckSoUEb3EiWGKF10WPYARjzk/45YvG/3XugmPebYA4lMQ++tvOZKDXBY5Fa 8/rBO6Q3QAx0Z7B3UEg4YU/V9GWG10wEusc6oIP8RFb0BiyaR7S54K5pdHYD2ZU= =7R/b -----END PGP SIGNATURE-----
--- End Message ---
