mountall needs a timeout in addition to the skip option
Bug #595904 reported by
jwm
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| mountall (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: mountall
The 'skip' mounting action is a big improvement over karmic's behaviour, but a timeout is still needed for cases where input is unavailable.
In my case, I use a bluetooth keyboard, and the bluetooth stack is still starting under the usual SysV system. No doubt there are plenty of other good cases for a timeout.
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in mountall (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package mountall - 2.24
---------------
mountall (2.24) natty; urgency=low
[ Colin Watson ]
* Update mountall's version number; it was last updated at 2.15.
[ Surbhi Palande ]
* Added a command line option dev-wait-time which specifies the time that
mountall needs to wait for a device to get ready. The default value for the
wait is 30 seconds.
(LP: #595904)
-- Bryce Harrington <email address hidden> Mon, 07 Mar 2011 16:50:04 -0800