Many thanks, all -
Tobias's suggestion brought my world back too.
It's a bit scary just how far we still are from having a system suitable
for normal users :-(
--
udevadm trigger is not permitted while udev is unconfigured
https://bugs.launchpad.net/bugs/358654
You received this bug notificatio
*** This bug is a duplicate of bug 103177 ***
https://bugs.launchpad.net/bugs/103177
Matt - thanks - we were having the same problem and it certainly solved
it for us.
--
boot on md raid drives fails
https://bugs.launchpad.net/bugs/79204
You received this bug notification because you are a m
Upgrading to Feisty is still a problem, though, at least for me.
Paul Williams' "dirty fix" got me going again - thanks Paul.
--
Latest python2.5-minimal update in Feisty fails
https://bugs.launchpad.net/bugs/80200
You received this bug notification because you are a member of Ubuntu
Bugs, which
*** This bug is a duplicate of bug 103177 ***
https://bugs.launchpad.net/bugs/103177
Mmm. Actually - re my previous comment - there still seems to be about
a 30% failure rate.
--
boot on md raid drives fails
https://bugs.launchpad.net/bugs/79204
You received this bug notification because yo
This affects us as well, because our clients have monitoring tools that
check on the kernel version running, and send notifications if it isn't
updated pretty promptly.
I'm going to try an extra kernel postinst script along the lines of the
one here to recover the original behaviour:
https://asku
