Comment 48 for bug 427356

On Wed, Sep 16, 2009 at 12:05 PM, Scott James Remnant wrote:
> On Wed, 2009-09-16 at 06:59 +0000, Kamilion wrote:
>
>> The new networking scripts failed to find my br0 defined in /etc/network/interfaces.
>> (Fortunately this motherboard has IPMI2 KVM-over-dedicated-IP, otherwise I would have been up a creek)
>>
> You should file a separate bug for this.

Never mind, it was my fault. Missed a package. Haven't had the problem since the initial reboot.
After a package update this morning and a reboot, it works fine.

>> couldn't find out how to disable upstart services, so I ended up moving /etc/init/gdm.conf to /etc/init-disabled/gdm.conf,
>> Any better ways?
> Rename them to .conf-disabled is another.
So it's looking in any directory under /etc/init for ".conf" files, correct?

What's the best trigger to get upstart to log all events as early as possible?
I'd like to figure out the path the new setup follows.

> I tend to just comment out the "start on" line.
yeah, I ended up doing the same, to keep 'start gdm' working,

> Better methods are planned in future Upstart releases which will find
> their way into future Ubuntu releases.

Where's the discussion for this type of stuff currently centered?

>> Some simple upstart jobs I'd like to see quickly:
>> opensshd, postfix, bootlogd, kvm/libvirt

> I think we'll largely stick with the current set for karmic; though
> don't be surprised if karmic+1 work appears in the ubuntu-boot PPA
> sooner rather than later.

I've got some time to kill, and I'd like to see at least opensshd make the jump before karmic+1, mainly because it's one of the single most important dependencies on a remote system to have properly tied to network events being emitted. Better to debug this now and have it solid and reliable before ubuntu-server goes out.
How can I help? (Just send me an email)