Commercial support for fixing bugs

[Alvin]

On Tuesday 05 January 2010 18:12:39 Ante Karamatić wrote:
> On 05.01.2010 16:50, Alvin wrote:
> > 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.
> 
> <rant and solution>
> 
> I, and rest of the server people, were hit by this or some other
> upstart/mountall/whatever bug that renders Karmic unusable in NFS
> environment.
> 
> [...]
> 
> </rant and solution>

Let's call that a workaround. There are other possibilities to work around 
this, but I don't like doing a lot of stuff in rc.local that SHOULD be done by 
the boot mechanism. Currently there are 3 things that need to be done after 
boot.

- mount NFS shares (bug 470776)
- restart samba (bug 462169)
- restart libvirtd (bug 491273)

Only the samba bug is fixed in karmic proposed. This bug is mentioned in the 
release notes. Shouldn't there be a warning in those release notes about NFS 
too?

I don't care for booting under 10 seconds on a server, but I do care for 
consistent booting. Right now, there are so many things going wrong that I 
don't know where to begin reporting. Even error messages are wrong (504224), 
and without boot logging (328881) they are the only thing we got to know what 
is going wrong.

I've had a talk about all this with my colleague, and we will probably try a 
support contract and see how it turns out.