[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [cobalt-users] Patching A RaQ4r



> -----Original Message-----
> From: wcstaff [mailto:wcstaff@xxxxxxxxxxxx] 
> Sent: Wednesday, June 11, 2003 12:46 PM
> To: cobalt-users@xxxxxxxxxxxxxxx
> Subject: Re: [cobalt-users] Patching A RaQ4r
> 
> 
> > Yes...I did take a look at that page, but I am new to Cobalt's and 
> > curious how to compare versions, etc.  Is everything listed 
> on the Sun 
> > page stable and current right now, or will I most likely 
> run into huge 
> > problems and downtime while patching them?
> >
> > I do not have physical access to the servers, so I need to 
> be careful 
> > to avoid any reboot charges...
> >
> > Restoring from scratch is not an option I want to use 
> because of some 
> > added-value features that are on the servers that I don't want to 
> > lose.
> >
> If you do not have access to the boxes, I suggest not doing 
> anything. If you don't reboot (it is a possibility), you will 
> be doing a system restore/initial configuration.
We have had a Raq4 and remotely controlled it for years. We've kept it patched up and haven't had much trouble with any patches. You can also reboot your box all day long even though it is remote. Make sure you apply the patches in the correct order.
The only thing to watch out for is patches that would interfere with your custom installed software. Read the patch description before you install them.
I would suggest you enable SSH and make sure you can access it using puTTY (Windows Client) or SSH (linux client).
Not patching your box is not a good option, you would be easy prey securitywise.

Vidar

> 
> _____________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To subscribe/unsubscribe, or to SEARCH THE ARCHIVES, go to: 
> http://list.cobalt.com/mailman/listinfo/cobalt> -users
>