Marco d'Itri pe v So 29. 10. 2005 v 01:41 +0200:
On Oct 29, Dominik Sauer [EMAIL PROTECTED] wrote:
(You may want to try the package at http://www.bofh.it/~md/debian/
which is faster but only lightly tested. If it breaks you keep both
pieces.)
I tried, it timeouts either (with default
Package: udev
Version: 0.071-1
Severity: critical
Justification: breaks the whole system
when installed, the timeout (udevd_timeout variable from
/etc/init.d/udev) is not set big enough to wait for creation of certain
devices (in particular /dev/hd* and ethernet card). This makes the
severity 336189 normal
thanks
On Oct 28, Dominik Sauer [EMAIL PROTECTED] wrote:
when I change the timeout to higher value (26 on my machine, but your
Which POS hardware are you using? This is a bit uncommon...
--
ciao,
Marco
signature.asc
Description: Digital signature
On Fri, Oct 28, 2005 at 03:07:15PM +0200, Marco d'Itri wrote:
severity 336189 normal
thanks
On Oct 28, Dominik Sauer [EMAIL PROTECTED] wrote:
when I change the timeout to higher value (26 on my machine, but your
Which POS hardware are you using? This is a bit uncommon...
... so race
On Oct 28, Steve Langasek [EMAIL PROTECTED] wrote:
On Oct 28, Dominik Sauer [EMAIL PROTECTED] wrote:
when I change the timeout to higher value (26 on my machine, but your
Which POS hardware are you using? This is a bit uncommon...
... so race conditions are ok if they're only known to
On Oct 29, Dominik Sauer [EMAIL PROTECTED] wrote:
well, i don't think it's a matter of paralelized init scripts. this
It is, because if everything happens as a consequence of hotplug events
then you do not need to wait for them.
meanwhile, would'nt be nice to split the devices into two?
Marco d'Itri pe v So 29. 10. 2005 v 00:04 +0200:
On Oct 28, Steve Langasek [EMAIL PROTECTED] wrote:
On Oct 28, Dominik Sauer [EMAIL PROTECTED] wrote:
when I change the timeout to higher value (26 on my machine, but your
Which POS hardware are you using? This is a bit uncommon...
7 matches
Mail list logo
