Thank you Andre - this should come in very handy in the future.

Would you feel comfortable submitting your words of wisdom to the 
port-cobalt FAQ?

List, who's maintaining that FAQ anyway? I seem to remember it has a few 
dead links etc. in it that need to be changed.


Chas

Andre Schulze as8-at-rcs.urz.tu-dresden.de |netbsd| wrote:

>Am Tue den 05 Aug 2003 um 12:20:04PM -0700 schrieb Chas Posinoff:
>  
>
>>I am much too used to always doing fresh re-installs when a new rev of 
>>an OS comes out.. but this machine will be in the co-lo and hence only 
>>manageable remotely. 
>>
>>Is there a method of managing kernel and system upgrades via ssh -- I am 
>>pretty sure I need to keep multi-user in order to maintain anything 
>>other than a serial console connection... (which I don't have..)
>>
>>    
>>
>I don't know exactly. AFAIK the deletion of opened files is committed
>after the handle is closed, i.e. it should be possible to overwrite
>the old with the new version while the process is running.
>However i did not test this, so it might be wrong as well. Be sure
>to check this before remotely rendering the box unusable ;-)
>
>As far as the kernel is concerned there should be no problem, over-
>writing the old file always worked for me.
>
>As an alternative, you could use a copy of ssh (maybe in /usr/local)
>running on a nonstandard port while updating. You can now safely
>stop the ssh service that comes with the distribution and replace
>it with the new version by extracting the tarball.
>
>Bye,
>
>	andre
>  
>