Package: mount Version: 2.26.2-6 Severity: normal Tags: upstream Dear Maintainer, I've found trying to mount an optical disk that turns out to be bad, (this is the case I've encountered, may possibly happen with other media) can cause the mount command to go into a noninteruptable sleep state, waiting for response from the hardware that never arrives. This latter can interfere in placing the computer in hibernate or performing a clean shutdown. My understanding is that the command could alternatively be implimented to use a "killable" state, similar to the uninteruptable sleep, except that the process can be killed. If there are reason's the noninteruptable sleep must be used most of the time, perhaps providing a switch to enforce "killable" when the media is of unproven quality would be possible. Thanks for any consideration.
Regards, Dallas E. Legan II / [email protected] / [email protected] http://isthereanotherquestion.blogspot.com ************************************************************************ "Tekeli-li! Tekeli-li!" - "At the Mountains of Madness", H.P. Lovecraft *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages mount depends on: ii libblkid1 2.25.2-6 ii libc6 2.19-17 ii libmount1 2.25.2-6 ii libselinux1 2.3-2 ii libsmartcols1 2.25.2-6 mount recommends no packages. Versions of packages mount suggests: ii nfs-common 1:1.2.2-4 -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
