I can confirm this on my jaunty to karmic upgrade as well. I did a
network upgrade of a clean jaunty base (ssh only) installation. I'm
getting the same error booting from a valid mirror set via the chainload
option recommended here:
Hi Chuck,
Actually I put that project on hold because I couldn't get it working.
Life has a way of readjusting your priorities. :) I've just recently
wiped the system and loaded a 9.04 version to attempt the process again,
although I'm not sure I'm using the same combinations this time
Hi Chuck,
Actually I put that project on hold because I couldn't get it working.
Life has a way of readjusting your priorities. :) I've just recently
wiped the system and loaded a 9.04 version to attempt the process again,
although I'm not sure I'm using the same combinations this time
Thanks Brian,
I think that's probably the right classification but since it seems to
be an interaction problem I wasn't sure. I also questioned whether it
could be indirectly security related since the only possible fix I've
run across is someone who appears to have run postfix without
Thanks Brian,
I think that's probably the right classification but since it seems to
be an interaction problem I wasn't sure. I also questioned whether it
could be indirectly security related since the only possible fix I've
run across is someone who appears to have run postfix without
Public bug reported:
This may be related to 244568, 138931. The details don't appear to be
the same, but the underlying cause could in fact be the same. I'm
attempting to setup an 8.04 server install with Postfix, mysql, and
postfixadmin. I'm using courier for imap and pop services, but that's
