dear All, does it possible to upgrade my 8.1 professional to 8.2? i have only remote access to the host. No graphical env., just ssh connection and unable to get the box physically (cannot insert the installation dvd into the tray). is this possible? any hints before start? thx in advance, z
The 03.08.14 at 00:08, Zoltan Levardy wrote:
does it possible to upgrade my 8.1 professional to 8.2? i have only remote access to the host. No graphical env., just ssh connection and unable to get the box physically (cannot insert the installation dvd into the tray). is this possible? any hints before start?
I don't think so... But I think it will try to connect to a console on the serial port, however. Alternatively, you could fill up manually a partition with an update you prepare manually elsewhere, and make sure it can boot from there when you finally tell it to boot. -- Cheers, Carlos Robinson
Op donderdag 14 augustus 2003 00:08, schreef Zoltan Levardy:
does it possible to upgrade my 8.1 professional to 8.2? i have only remote access to the host. No graphical env., just ssh connection and unable to get the box physically (cannot insert the installation dvd into the tray). is this possible? any hints before start?
Zoltan, You can try it with apt; http://linux01.gwdg.de/apt4rpm http://linux01.gwdg.de/apt4rpm/upgrade-81to82.html It worked for me :) -- Richard Bos Without a home the journey is endless
On Wednesday 13 August 2003 17:08, Zoltan Levardy wrote:
dear All,
does it possible to upgrade my 8.1 professional to 8.2? i have only remote access to the host. No graphical env., just ssh connection and unable to get the box physically (cannot insert the installation dvd into the tray). is this possible? any hints before start?
thx in advance, z
I did it once with using YaST System Update. you need to copy the CDs or ftp tree to some location, then set up the installation sources and go ahead, BUT! In SuSE 8.2 there is an updated version of GLIBC from 2.2.4 (as far as i remember) to 2.3.2 -- if you just start update -- it will fail and leave you with the broken system, and rpm will not work any more. So, first you need to update somehow both GLIBC and RPM, do ldconfig, and after that proceed with normal update. In my case, i understood that too late, so when my update interrupted in the middle of the update, and RPM stopped working, i had to extract the package contents into the root file system (using mc), and then i restarted update and it continued. but again -- doing it remotely you risk to leave your system unbootable, so you should rather be close !
participants (4)
-
Carlos E. R.
-
Richard Bos
-
Vitaly Shishakov
-
Zoltan Levardy