Date:  Sat, 2 Sep 2006 18:33:56 +0200
From:  Michael Stauber <bq (at mark) solarspeed.net>
Subject:  [coba-e:06692] Re: E-mail broke afer massive updaes v3.5
To:  coba-e (at mark) bluequartz.org
Message-Id:  <200609021833.56283.bq (at mark) solarspeed.net>
In-Reply-To:  <20060902160246.M52803 (at mark) mediapie.nl>
References:  <20060831180840.M21588 (at mark) ds3.net> <20060831215523.M55216 (at mark) ds3.net> <20060902160246.M52803 (at mark) mediapie.nl>
X-Mail-Count: 06692

Hi F de Vries mediaPie,

> Anyone but Yada has had problems with updating older versions of BQ (before
> 3)?

Yes. I had a client with an unknown version of BQ, where after updating PAM 
was broken. Only admin/root logins were possible, but anything PAM based was 
not.

After lots of experimenting (like reinstalling PAM manually from the RPMs) I 
downloaded the BQ tarball install and did an "upgrade" from the tarball. Had 
to comment out the "exit 1" line in the section where it checks for the 
version of CentOS4, otherwise it would say "Your version of CentOS is not 
supported" (or similar). That's right at the top of the upgrade.sh script.

Afterwards authentication worked again and another manual run of "yum update" 
brought the box fully back in line with the current patchlevel. 

-- 

With best regards,

Michael Stauber