On Mon, August 18, 2008 11:10, Alexander Heinlein wrote: > On Mon, Aug 18, 2008 at 10:11:54AM +0200, David Härdeman wrote: >> the problem is that some of the changes we've committed during the last >> couple of weeks in order to support usplash/splashy/remote shells/etc >> make >> it very hard to support timeouts. I'm not sure if we'll be able to readd >> support for it... :( > > Oh, too bad :( > > Disabling timeouts per default through config and placing a hint about > occuring issues when reenabling it isn't an option?
Well, the problem is that the "issue" is most of the time that there is no timeout at all... > Would be nice if my system will boot even if there is nobody who enters > the password for auto mounted, non essential partitions. If they aren't essential, then a workaround for now would be to mark them "noauto" and use the opposite approach compared to what you're used to doing (i.e. when someone is present, he/she can manually mount the extra volumes). -- David Härdeman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]