Brian Behlendorf 9ac97c2a93 Print mount/umount errors ... Because we are dependent of the system mount/umount utilities to ensure correct mtab locking, we should not suppress their error output. During a successful mount/umount they will be silent, but during a failure the error message they print is the only sure way to know why a mount failed. This is because the (u)mount(8) return code does not contain the result of the system call issued. The only way to clearly idenify why thing failed is to rely on the error message printed by the tool. Longer term once libmount is available we can issue the mount/umount system calls within the tool and still be ensured correct mtab locking. Closed #107		2011-03-09 15:26:48 -08:00
..
libavl	Linux 2.6.38 compat, blkdev_get_by_path()	2011-02-23 12:29:38 -08:00
libefi	Linux 2.6.38 compat, blkdev_get_by_path()	2011-02-23 12:29:38 -08:00
libnvpair	Linux 2.6.38 compat, blkdev_get_by_path()	2011-02-23 12:29:38 -08:00
libspl	Fix mount helper	2011-03-09 15:26:48 -08:00
libunicode	Linux 2.6.38 compat, blkdev_get_by_path()	2011-02-23 12:29:38 -08:00
libuutil	Linux 2.6.38 compat, blkdev_get_by_path()	2011-02-23 12:29:38 -08:00
libzfs	Print mount/umount errors	2011-03-09 15:26:48 -08:00
libzpool	Linux 2.6.38 compat, blkdev_get_by_path()	2011-02-23 12:29:38 -08:00
Makefile.am	Add missing libspl+libzpool libs to libzfs	2011-03-03 15:48:57 -08:00
Makefile.in	Add missing libspl+libzpool libs to libzfs	2011-03-03 15:48:57 -08:00