[cobalt-users] Re: Qube2 BIND Updates (Mike Vanecek)

["Larry M. McConnell" <mcconnelllm@xxxxxxxxxxx>]

:>At 4/10/01 10:29 AM -0500, you wrote:
:>>So, which version of bind should be currently installed??
:>
:>"Should" is a big question for me right now. 4.9.8 "is" installed courtesy
:>of Security-4.0.2, after 8.2.2P5 "was" installed by OS Update 4.0. I'm
:>hoping that they finally decide that 8.2.3 "should be" and make it so.

>Uhm, ...  It would be nice if the web page containing 4.0.2 did not say it
was
>installing bind 8.2.3. I looked through the archives and did not see
anything
>bout Cobalt responding to a question about this. Do you know if Cobalt has
>acknowledged what has happened with regard to bind for the Qube 2?  I'd
send
>them an email, but my warranty is down the tubes ...

I offer the following as more info regarding the order to install updates
from the Cobalt site.  Months ago Cobalt tech support told me the correct
order is start at the bottom of the list and work up. Hope that helps.

I also offer the following which is somewhat related and was posted last
week but had no response.  From our experience with installing the updates
it appears to me the updates breaks the GUI.

Went to update our Qube 2 with the latest OS/software updates off the cobalt
site.  I found two issues:  1.)  The OS 4.0 update will change the smb.conf
file so "oplocks = yes" and 2.) The "Disk Usage Summary"  on the user
interface gives a false reading and also gives an amber light, even when it
shows a total of 727 MB's for the "Operating System and Programs"!  The
oplocks problem is easy to fix, just edit the file.  The amber light problem
appears to be a "glitch" with the UI.  Called Tech Support and they said
they were aware of the problem starting with the OS 4.0 update (dated Feb
14, 2001) some valentines day present.  I would like to see if anybody knows
how to correct the problem.  When we load the Qube back up with files the
"Operating System and programs" seems to grow larger as well according to
the GUI.  When you do a df in a telnet session, /dev/hda1 never grows larger
than 232 MB's.  So it seems to be just a problem with the UI.  Anybody have
any suggestions, or insights on how to fix the GUI?

Feel free to respond to the list and <mailto:McConnellLM@xxxxxxxxxxx>

Larry M. McConnell