On Mon, Feb 04, 2013 at 10:40:51AM -0000, Cédric Dufour wrote:
> Note that this issue also presents itself when not using plymouth
> (though the passphrase prompt would "hide" the mountall "boredom" until
> the 'return' key is pressed).
There is no case in which plymouth is not used.
> However, I think that hard-coding a 3-second timeout in the source code
> is not a good idea. Timeouts should be configureable.
This is an unsubstantiated "should". This is merely the timeout until
which the user is given the opportunity to skip a disk's mounting at boot;
allowing configurability of such a timeout really doesn't add much value.
On Mon, Feb 04, 2013 at 10:40:51AM -0000, Cédric Dufour wrote:
> Note that this issue also presents itself when not using plymouth
> (though the passphrase prompt would "hide" the mountall "boredom" until
> the 'return' key is pressed).
There is no case in which plymouth is not used.
> However, I think that hard-coding a 3-second timeout in the source code
> is not a good idea. Timeouts should be configureable.
This is an unsubstantiated "should". This is merely the timeout until
which the user is given the opportunity to skip a disk's mounting at boot;
allowing configurability of such a timeout really doesn't add much value.