Activity log for bug #30241

Date Who What changed Old value New value Message
2006-02-01 17:09:49 Crispin Flowerday bug added bug
2006-04-03 23:26:21 Matt Zimmerman netbase: status Unconfirmed Confirmed
2006-04-03 23:26:21 Matt Zimmerman netbase: assignee keybuk
2006-04-03 23:26:21 Matt Zimmerman netbase: statusexplanation
2006-04-06 05:42:23 Scott James Remnant (Canonical) None: priority Low
2006-04-27 08:38:09 Fabio Massimo Di Nitto sysvinit: severity Normal Major
2006-04-27 08:38:09 Fabio Massimo Di Nitto sysvinit: statusexplanation I have the same problem here but i noticed that it happens only when booting into newly installed kernels (for example on ABI bumps). If i run depmod -a with the new running kernel and i reboot, the problem goes away forever. I *think* that with all the attempts to improve the boot speed we managed to endup in never running depmod -a at least once on a kernel boot to refresh everything. Another side effect of this is that things like alsa index= options are not respected at the first boot without depmod -a. Probably the best solution would be to make sure that we run depmod -a at least once. on boot, into a new installed kernel, before everything else happen. Fabio
2006-05-09 15:44:22 Scott James Remnant (Canonical) sysvinit: status Confirmed Fix Released
2006-05-09 15:44:22 Scott James Remnant (Canonical) sysvinit: statusexplanation I have the same problem here but i noticed that it happens only when booting into newly installed kernels (for example on ABI bumps). If i run depmod -a with the new running kernel and i reboot, the problem goes away forever. I *think* that with all the attempts to improve the boot speed we managed to endup in never running depmod -a at least once on a kernel boot to refresh everything. Another side effect of this is that things like alsa index= options are not respected at the first boot without depmod -a. Probably the best solution would be to make sure that we run depmod -a at least once. on boot, into a new installed kernel, before everything else happen. Fabio sysvinit (2.86.ds1-6ubuntu27) dapper; urgency=low . * Move the mountnfs.sh init script to a network if-up.d script, and clean up a little now it's not being run in the main boot sequence. * Place a simple waitnfs.sh init script in its place that waits for /usr to be mounted if necessary.