[cobalt-users] RE: OS 3.0 Update Nightmare

["David Hall" <dhall@xxxxxxxxxxxxxx>]

>Actually, reading your post and the corresponding error message makes me
think
>more of faulty network hardware and/or corrupted memory in the RaQ,
resulting in
>corrupted commands in shell scripts.
> if there really *is* the string "echp" in a shell script inside the
>kernel-source RPM. Kernel OOPS messages should never occur during an update
>IMHO.

Cobalt took a look at it and put in a temporary fix and here was what they
had to say:
"This fix will work until we get a new kernel rolled out. This does not
affect
the usability of the server in anyway"

>Since you commented on the RaQ philosophy itself, I took the freedom to
comment
>on a few aspects of your post.

Well, I still believe the Raq3i was not ready for prime time, the over
abundance of patches
 that have been sent out, I think attests to that. How they could have
possibly let it out the door
with the way it generates the log stats in the GUI is beyond me. After all
log stat reporting
is a fairly basic function.
I do commend their tech support they have always been responsive for me.