On Sat, 2002-12-14 at 11:45, [EMAIL PROTECTED] wrote: > Hi everyone out there, > > today i installed the latest kernel update > RaQXTR-All-Kernel-1.0.1-2.2.16C33_V-1 on three RaQ XTR.
Where did you get this from ftp.cobalt.com? If so then in the future I recommend checking and only applying the patches listed here http://sunsolve.sun.com/patches/cobalt/raqxtr.eng.html > So i suggest everyone **NOT** to install this update until sun issued > further information or a working update. I do not seem to remember Sun issuing this one to begin with. They simply put it up on their ftp server. They did not add it to the link above, nor did they release it as part of the Blue link update system, or what ever they call it. So in the future I would only use/apply patches that go through the normal channels. I would not download all patches on their ftp servers and install them. For reasons that you have run into head on. > Monday will be a great beginning of the week - try to fix it. I think i > will look for some alternives to cobalt servers in the future as this is > not the first time they issued a buggy update. Well I am not sure I fully agree. I have only seen one update that has ever caused me problem. Which in fact was not the fault of the patch, but the fault of a hacker using a worm that exploited bind and took over my machine. This was two years ago on a collocated Raq4r. Since then, I have never had a problem with any updates that are on the main site, the link above. I have heard of others that had problems with some patches on Raq4's that Sun withdrew, but I can't seem to remember any like that for the XTR. Now in regards to Sun/Cobalt warrantying the box for you, I hope/assume they would. I would be curious to see what they say in this scenario. I would also be curious to know why they are releasing another version of the 2.2.16 kernel instead of upgrading to the current 2.2.23. It seems more and more that Sun/Cobalt has problems with keeping things current. I know a 2.4 kernel would be pushing it due to the PROM and other reasons, but a 2.2.23 should not be out of the question. In general if you know what you are doing with a *nix box, then get a LX50, not a Cobalt. That will be my next step, or dare I say, a box from Dell. Also there is something to be said for doing kernel upgrades on machines you do not have physical access to. Make sure you have tested things, and know what you are doing will work/succeed. Or you get into situations like you are in. Due to reasons like this one and others, I stopped collocating over a year ago. Nothing like being able to walk in the next room and take care of a problem yourself immediately. I had some fans in my XTR fail. I filled out a form on-line with Sun, and within a day or two my new part arrived and I replaced it myself. If I was collocating it, I would have had to inform the ISP, and wait for them to deal with it. In your case I am not sure what to tell you. If you can access the box, try to remove the current kernel, and re-install the old one. You should be able to do it manually if you can access the box. -- Sincerely, William L. Thomson Jr. Support Group Obsidian-Studios Inc. 439 Amber Way Petaluma, Ca. 94952 Phone 707.766.9509 Fax 707.766.8989 http://www.obsidian-studios.com _______________________________________________ cobalt-developers mailing list [EMAIL PROTECTED] http://list.cobalt.com/mailman/listinfo/cobalt-developers
