Re: RFC: remove dovecot-postfix from lucid

2010-04-15 Thread Scott Kitterman


"Mathias Gug"  wrote:

>Hi,
>
>During the Jaunty release cycle the dovecot-postfix package was created in
>order to make it easier to integrate dovecot and postfix. The solution chosen
>was to not modify the default dovecot configuration file and instead generate a
>dovecot-postfix.conf with the correct options. The init script was also
>modified to use the new dovecot-postfix.conf file (if available) instead of the
>default configuration file.
>
>While the goal is worthwhile the implementation seems to not be the best
>option. Using an alternate configuration file breaks a lot of common knowledge
>to the point that an upstream developer filed a bug [1] with a patch to dovecot
>to provide additional checks specific to Ubuntu.
>
>[1]: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/511295
>
>Given the LTS status of Lucid I'd suggest to drop the dovecot-postfix package
>in order to avoid carrying a non-default/Ubuntu-specific configuration file
>around for 5 years.
>
>What needs to be done is to update dovecot init script to not look for
>dovecot-postfix.conf and migrate an existing dovecot-postfix.conf to
>dovecot.conf in the maintainer scripts.
>.
>I still think the objective is worthwhile and we should spend some time at the
>next UDS to come up with a better implementation.
> 
This is a complete over reaction. 

There is a relatively minor bug with a fix provided.  Let's fix the bug and 
move on.  This approach has a year of good user experience behind it. I'm 
completely against removal with no replacement. 

I think having a better way for Maverick is great, but not losing this 
capability in the mean time. 

Scott K-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

RFC: remove dovecot-postfix from lucid

2010-04-15 Thread Mathias Gug
Hi,

During the Jaunty release cycle the dovecot-postfix package was created in
order to make it easier to integrate dovecot and postfix. The solution chosen
was to not modify the default dovecot configuration file and instead generate a
dovecot-postfix.conf with the correct options. The init script was also
modified to use the new dovecot-postfix.conf file (if available) instead of the
default configuration file.

While the goal is worthwhile the implementation seems to not be the best
option. Using an alternate configuration file breaks a lot of common knowledge
to the point that an upstream developer filed a bug [1] with a patch to dovecot
to provide additional checks specific to Ubuntu.

[1]: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/511295

Given the LTS status of Lucid I'd suggest to drop the dovecot-postfix package
in order to avoid carrying a non-default/Ubuntu-specific configuration file
around for 5 years.

What needs to be done is to update dovecot init script to not look for
dovecot-postfix.conf and migrate an existing dovecot-postfix.conf to
dovecot.conf in the maintainer scripts.

I still think the objective is worthwhile and we should spend some time at the
next UDS to come up with a better implementation.
 
-- 
Mathias Gug
Ubuntu Developer  http://www.ubuntu.com

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam


Bug or hardware failure

2010-04-15 Thread Alvin
A week ago, a server of mine suddenly started to halt on random moments. Blank 
screen, no input. Drives and memory where fine. I needed frequent reboots to 
be able to finally start the machine (always that blank screen)
Nothing in the logs hours before a sudden crash, nothing in /var/crash.

After a BIOS upgrade, the only message I got after a flash of grub was:
PANIC: early exception 08 rip 246:10 error 810356e6 cr2 0
(Older kernel gives same message.)

A replacement board showed the same error on boot, so unless both boards are 
faulty, a software error is more likely.

I had more success getting the system to boot with 'Intel Trusted Execution' 
disabled.

So, how would you debug a situation like this?

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam