I'd like to upgrade a lot of machines under my care to karmic, because of
different reasons, but there is a bug that 'stops the show'.
retry remote devices when parent is ready after SIGUSR1
In short, NFS mounts can not be trusted. Sometimes, it is needed to go into a
recovery shell, mount manually, and continue booting (with some other errors).
This is all good if you can manage the console, but for "human beings" who
will be using some of these systems, it's just too much to ask.
(I mentioned this and other bugs in a previous post (Earth Computing), but
there were only personal reactions.)
The good news is, that this is fixed in lucid. The bad news is: karmic will
I contacted Canonical a while ago, and a support contract will give you the
right to 10 support cases per annum. I'm perfectly willing to pay for support,
if only to give some people the chance to be payed for the work they do on
The situation with bugs (I quote):
- Support customer bugs receive higher priority by Canonical developers.
- Bugs reported as support cases do not actually count against your allocation
of support tickets for that subscription.
- Bugs that require assistance from upstream projects are also managed
directly by Canonical, increasing the likelihood, and speed of successful
So, the bugs I mentioned in my previous post would receive higher priority. I
only wonder whether this specific bug would be solved in karmic, because it
needs another solution than the one that will be used for lucid. After all, is
is already fixed.
So, will taking a support contract guarantee bootable machines in the next 4
ubuntu-server mailing list
More info: https://wiki.ubuntu.com/ServerTeam