Migration problems going from 9.2 to 9.3
Hi, Last night I migrated to 9.3 from 9.2. Due to the XServer crashing while trying to do the upgrade from the booting DVD, I had to use yast on the 9.2 system and choose the option "upgrade". During this I had no obvious problems. However afterwards /etc/issue nor was /etc/opt/kde..../kdmrc did not have the "9.2 string updated to "9.3". This by itself is not a big problem, but when I run online update the system still thinks that it is 9.2!! What do I need to change to tell the system that it is really 9.3 for YOU ? Thanks CPH
con wrote:
Hi, Last night I migrated to 9.3 from 9.2. Due to the XServer crashing while trying to do the upgrade from the booting DVD, I had to use yast on the 9.2 system and choose the option "upgrade". During this I had no obvious problems. However afterwards /etc/issue nor was /etc/opt/kde..../kdmrc did not have the "9.2 string updated to "9.3". This by itself is not a big problem, but when I run online update the system still thinks that it is 9.2!! What do I need to change to tell the system that it is really 9.3 for YOU ?
Thanks CPH
Check and change if necessary, then try YOU again. # less /etc/SuSE-release SuSE Linux 9.3 (i586) VERSION = 9.3 Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
Sid Boyce wrote:
Check and change if necessary, then try YOU again. # less /etc/SuSE-release SuSE Linux 9.3 (i586) VERSION = 9.3
i also get YOU looking for 9.2 after my upgrade, but my SuSE-release file says 9.3 -- Raoul Snyman Saturn Laboratories Cell: 082 550 3754 E-mail: raoul.snyman@saturnlaboratories.co.za Web: http://www.saturnlaboratories.co.za/ Blog: http://blog.saturnlaboratories.co.za/ Registered Linux User #333298 (http://counter.li.org)
On Wed, 1 Jun 2005, Raoul Snyman wrote:
Sid Boyce wrote:
Check and change if necessary, then try YOU again. # less /etc/SuSE-release SuSE Linux 9.3 (i586) VERSION = 9.3
i also get YOU looking for 9.2 after my upgrade, but my SuSE-release file says 9.3
Here is another 'me too'. -- Carpe diem - Seize the day. Carp in denim - There's a fish in my pants! Jon Nelson <jnelson-suse@jamponi.net>
On Wednesday 01 June 2005 13:46, Jon Nelson wrote:
On Wed, 1 Jun 2005, Raoul Snyman wrote:
Sid Boyce wrote:
Check and change if necessary, then try YOU again. # less /etc/SuSE-release SuSE Linux 9.3 (i586) VERSION = 9.3
i also get YOU looking for 9.2 after my upgrade, but my SuSE-release file says 9.3
Here is another 'me too'.
Sounds very much like http://portal.suse.com/sdb/en/2003/10/thallma_you_oldpatches.html Greetings from Stuhr hartmut
On Wed, 1 Jun 2005, Hartmut Meyer wrote:
On Wednesday 01 June 2005 13:46, Jon Nelson wrote:
On Wed, 1 Jun 2005, Raoul Snyman wrote:
Sid Boyce wrote:
Check and change if necessary, then try YOU again. # less /etc/SuSE-release SuSE Linux 9.3 (i586) VERSION = 9.3
i also get YOU looking for 9.2 after my upgrade, but my SuSE-release file says 9.3
Here is another 'me too'.
Sounds very much like
http://portal.suse.com/sdb/en/2003/10/thallma_you_oldpatches.html
Yeah, that sounds like it, but here are some points: 1. if you can't upgrade a running system (Debian can, most others can) without BOOTING FROM THE CD or DVD, then why does YaST have the option available? 2. Half of my machines don't have CD drives, much less CDROMS, and none of them have floppy drives. A Network Install is basically the only way to upgrade them. -- Carpe diem - Seize the day. Carp in denim - There's a fish in my pants! Jon Nelson <jnelson-suse@jamponi.net>
Hi, On Wednesday 01 June 2005 14:06, Jon Nelson wrote:
On Wed, 1 Jun 2005, Hartmut Meyer wrote:
http://portal.suse.com/sdb/en/2003/10/thallma_you_oldpatches.html
Yeah, that sounds like it, but here are some points:
1. if you can't upgrade a running system (Debian can, most others can) without BOOTING FROM THE CD or DVD, then why does YaST have the option available?
You can add other installation sources that provide newer (but non-core) packages like ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.3/yast-source And than use this YaST2 module to update all available packages.
2. Half of my machines don't have CD drives, much less CDROMS, and none of them have floppy drives. A Network Install is basically the only way to upgrade them.
Tough ... Greetings from Stuhr hartmut
On Wed, 1 Jun 2005, Hartmut Meyer wrote:
Hi,
On Wednesday 01 June 2005 14:06, Jon Nelson wrote:
On Wed, 1 Jun 2005, Hartmut Meyer wrote:
http://portal.suse.com/sdb/en/2003/10/thallma_you_oldpatches.html
Yeah, that sounds like it, but here are some points:
1. if you can't upgrade a running system (Debian can, most others can) without BOOTING FROM THE CD or DVD, then why does YaST have the option available?
You can add other installation sources that provide newer (but non-core) packages like
ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.3/yast-source
And than use this YaST2 module to update all available packages.
That's not what I'm talking about. I'm talking about the "System Upgrade" option/component of YaST. It's sole purpose is to upgrade the entire system (say, from 9.2 to 9.3), and despite no warnings or problems encountered along the way, apparently, it doesn't /quite/ work. That's fun! -- Carpe diem - Seize the day. Carp in denim - There's a fish in my pants! Jon Nelson <jnelson-suse@jamponi.net>
Hi, On Wednesday 01 June 2005 14:51, Jon Nelson wrote:
On Wed, 1 Jun 2005, Hartmut Meyer wrote:
On Wednesday 01 June 2005 14:06, Jon Nelson wrote:
On Wed, 1 Jun 2005, Hartmut Meyer wrote:
http://portal.suse.com/sdb/en/2003/10/thallma_you_oldpatches.html
Yeah, that sounds like it, but here are some points:
1. if you can't upgrade a running system (Debian can, most others can) without BOOTING FROM THE CD or DVD, then why does YaST have the option available?
You can add other installation sources that provide newer (but non-core) packages like
ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.3/yast-source
And than use this YaST2 module to update all available packages.
That's not what I'm talking about. I'm talking about the "System Upgrade" option/component of YaST. It's sole purpose is to upgrade the entire system (say, from 9.2 to 9.3), and despite no warnings or problems encountered along the way, apparently, it doesn't /quite/ work.
That's the one I meant. I know it is confusing and many people belive that this module is meant to do an update of the running system from one release to the next, but it is not. Did you read the manual? It's chapter 2.3.4 "System Update" (SUSE Linux 9.2) in the big Admin manual. Greetings from Stuhr hartmut
On Wed, 1 Jun 2005, Hartmut Meyer wrote:
Hi,
On Wednesday 01 June 2005 14:51, Jon Nelson wrote:
On Wed, 1 Jun 2005, Hartmut Meyer wrote:
On Wednesday 01 June 2005 14:06, Jon Nelson wrote:
On Wed, 1 Jun 2005, Hartmut Meyer wrote:
http://portal.suse.com/sdb/en/2003/10/thallma_you_oldpatches.html
Yeah, that sounds like it, but here are some points:
1. if you can't upgrade a running system (Debian can, most others can) without BOOTING FROM THE CD or DVD, then why does YaST have the option available?
You can add other installation sources that provide newer (but non-core) packages like
ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.3/yast-source
And than use this YaST2 module to update all available packages.
That's not what I'm talking about. I'm talking about the "System Upgrade" option/component of YaST. It's sole purpose is to upgrade the entire system (say, from 9.2 to 9.3), and despite no warnings or problems encountered along the way, apparently, it doesn't /quite/ work.
That's the one I meant.
I know it is confusing and many people belive that this module is meant to do an update of the running system from one release to the next, but it is not.
Did you read the manual? It's chapter 2.3.4 "System Update" (SUSE Linux 9.2) in the big Admin manual.
What /is/ it there for, then, anyway? I don't have any manuals handy, and I sure as hell don't carry them around with me. Saying "Read the Manual" is, quite frankly, about the lamest response I've heard in a long time. It's not relevant whether I've read the manual or not. That's like saying a button in your car labeled "Heat" doesn't really produce heat but just redirects exhaust into the cabin. Yeah, you might get warm, but there are unintended side effects. Is it a labeling issue? Should the option even /be/ there? SuSE's inability to upgrade a running system is a very serious shortcoming, and apparently one dictated not by technical feasability. Honestly I'm rather disappointed with that aspect of SuSE. They cannot and will not gain meaningful market share if they can't improve installation and upgrades, an issue which has been a problem for SuSE for as long as I can remember! IMO Debian has, far and away, the best upgrade mechanism available - at one point I had upgraded seemlessly (all while "online" I might add) an installation whose initial install dated back 3 major versions! Furthermore, the fact that I'm not the only one that has hit upon this problem suggests that it /is/ a problem. Saying "did you read the manual" is a total cop-out. -- Carpe diem - Seize the day. Carp in denim - There's a fish in my pants! Jon Nelson <jnelson-suse@jamponi.net>
* Jon Nelson <jnelson-suse@jamponi.net> [06-01-05 08:27]:
On Wed, 1 Jun 2005, Hartmut Meyer wrote: ....
I know it is confusing and many people belive that this module is meant to do an update of the running system from one release to the next, but it is not.
Did you read the manual? It's chapter 2.3.4 "System Update" (SUSE Linux 9.2) in the big Admin manual.
What /is/ it there for, then, anyway? I don't have any manuals handy, and I sure as hell don't carry them around with me. Saying "Read the Manual" is, quite frankly, about the lamest response I've heard in a long time.
/more ranting removed/ Fine discorse. You are to be congratulated. You are slamming one of the few SuSE employes active on the list. note: Never read the instructions, that's not what they are for. When you do not know how to accomplish something or for some reason cannot accomplish something, *immediately* go ask for *free* answers from *unpaid* list participants. Under *no* circumstances make an effort to research your problems and, perhaps learn something that you *might* contribute. ps: To participating SuSE employes: Thanks for your efforts. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery
On Wed, 1 Jun 2005, Patrick Shanahan wrote:
* Jon Nelson <jnelson-suse@jamponi.net> [06-01-05 08:27]:
On Wed, 1 Jun 2005, Hartmut Meyer wrote: ....
I know it is confusing and many people belive that this module is meant to do an update of the running system from one release to the next, but it is not.
Did you read the manual? It's chapter 2.3.4 "System Update" (SUSE Linux 9.2) in the big Admin manual.
What /is/ it there for, then, anyway? I don't have any manuals handy, and I sure as hell don't carry them around with me. Saying "Read the Manual" is, quite frankly, about the lamest response I've heard in a long time.
/more ranting removed/
Fine discorse. You are to be congratulated. You are slamming one of the few SuSE employes active on the list.
OK, I deserved that. I didn't read closely enough. Blame it on lack of sleep, mea culpa. CLEARLY he described what it's for, and I'm to blame for misreading his response. I certainly didn't intend to "slam" anybody, there is a huge difference between a difference of opinion and a personal attack. That issue aside, I think I've raised some questions that got lost in the noise, specifically the item about SuSE's inability to be upgraded while running. Additionally, Hartmut seems to agree that it's confusing to have an item "System Update" that doesn't appear to function as "many people" believe it does, and I feel that it's a problem. Fundamentally, it's not as big of a problem as the inability to upgrade while running, however. -- Carpe diem - Seize the day. Carp in denim - There's a fish in my pants! Jon Nelson <jnelson-suse@jamponi.net>
On Wed, 2005-06-01 at 10:27 -0500, Jon Nelson wrote:
On Wed, 1 Jun 2005, Patrick Shanahan wrote:
Fine discorse. You are to be congratulated. You are slamming one of the few SuSE employes active on the list.
OK, I deserved that. I didn't read closely enough. Blame it on lack of sleep, mea culpa. CLEARLY he described what it's for, and I'm to blame for misreading his response. I certainly didn't intend to "slam" anybody, there is a huge difference between a difference of opinion and a personal attack.
That issue aside, I think I've raised some questions that got lost in the noise, specifically the item about SuSE's inability to be upgraded while running. Additionally, Hartmut seems to agree that it's confusing to have an item "System Update" that doesn't appear to function as "many people" believe it does, and I feel that it's a problem. Fundamentally, it's not as big of a problem as the inability to upgrade while running, however.
What is so important that you -have- to upgrade while the system is running? It is always better to upgrade a non-running system. Update is different. There are far more things changing under the hood than you think which is why you should boot to the install media do upgrade. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Wed, 1 Jun 2005, Ken Schneider wrote:
On Wed, 2005-06-01 at 10:27 -0500, Jon Nelson wrote:
On Wed, 1 Jun 2005, Patrick Shanahan wrote:
Fine discorse. You are to be congratulated. You are slamming one of the few SuSE employes active on the list.
OK, I deserved that. I didn't read closely enough. Blame it on lack of sleep, mea culpa. CLEARLY he described what it's for, and I'm to blame for misreading his response. I certainly didn't intend to "slam" anybody, there is a huge difference between a difference of opinion and a personal attack.
That issue aside, I think I've raised some questions that got lost in the noise, specifically the item about SuSE's inability to be upgraded while running. Additionally, Hartmut seems to agree that it's confusing to have an item "System Update" that doesn't appear to function as "many people" believe it does, and I feel that it's a problem. Fundamentally, it's not as big of a problem as the inability to upgrade while running, however.
What is so important that you -have- to upgrade while the system is running? It is always better to upgrade a non-running system. Update is different. There are far more things changing under the hood than you think which is why you should boot to the install media do upgrade.
I don't have to upgrade a running system. If I could do a diskless (no CD,DVD, or floppy) upgrade that would really be ideal. There are many machines that don't have any of those items. As for "It is /always/ better to upgrade a non-running system." (emphasis mine) that's an absolute and I'm quite sure isn't always true - there may be many times when upgrading while running (even in runlevel 1 or 2) may be preferable to attempting to do an upgrade of a non-booted system. -- Carpe diem - Seize the day. Carp in denim - There's a fish in my pants! Jon Nelson <jnelson-suse@jamponi.net>
On Wednesday 01 June 2005 12:34 pm, Jon Nelson wrote:
I don't have to upgrade a running system. If I could do a diskless (no CD,DVD, or floppy) upgrade that would really be ideal. There are many machines that don't have any of those items. As for "It is /always/ better to upgrade a non-running system." (emphasis mine) that's an absolute and I'm quite sure isn't always true - there may be many times when upgrading while running (even in runlevel 1 or 2) may be preferable to attempting to do an upgrade of a non-booted system.
I have a small sony Viao laptop (PCG-505G) that doesn't have floppy, cdrom, or bootable usb, network. It has a very small HD (about 4 gig I think) and my only option to install on this is pulling the HD out and copying the CD's to it. I tried installing with HD in a different machine and ran into trouble when the hardware changed. SuSEPluger (or whatever) didn't catch all the changes. I then ran into this problem mentioned here thinking that using the Upgrade link pointing to a nfs share would install the newer 9.3 and let the hardware be re-detected. That didn't happen the first time. I re-ran again, and it seemed to work (mostly). I would agree that it would be nice to be able to do a clean install from nfs. Something to the effect of wiping out HD, and installing just what is needed to access the nfs share and install from scratch that way.... my 2 cents FWIW B-)
On Wed, 2005-06-01 at 08:19 -0500, Jon Nelson wrote:
On Wed, 1 Jun 2005, Hartmut Meyer wrote:
Hi,
On Wednesday 01 June 2005 14:51, Jon Nelson wrote:
That's the one I meant.
I know it is confusing and many people belive that this module is meant to do an update of the running system from one release to the next, but it is not.
Did you read the manual? It's chapter 2.3.4 "System Update" (SUSE Linux 9.2) in the big Admin manual.
What /is/ it there for, then, anyway? I don't have any manuals handy, and I sure as hell don't carry them around with me.
There should be a copy installed on the PC.
Saying "Read the Manual" is, quite frankly, about the lamest response I've heard in a long time.
It's not relevant whether I've read the manual or not. That's like saying a button in your car labeled "Heat" doesn't really produce heat but just redirects exhaust into the cabin. Yeah, you might get warm, but there are unintended side effects. Is it a labeling issue? Should the option even /be/ there? SuSE's inability to upgrade a running system is a very serious shortcoming, and apparently one dictated not by technical feasability. Honestly I'm rather disappointed with that aspect of SuSE. They cannot and will not gain meaningful market share if they can't improve installation and upgrades, an issue which has been a problem for SuSE for as long as I can remember! IMO Debian has, far and away, the best upgrade mechanism available - at one point I had upgraded seemlessly (all while "online" I might add) an installation whose initial install dated back 3 major versions!
Then why don't you stop using SuSE and use Debian and stop ranting here about some function you haven't read about? Or is that how you run all of your systems, let me click on this and see what happens.
Furthermore, the fact that I'm not the only one that has hit upon this problem suggests that it /is/ a problem. Saying "did you read the manual" is a total cop-out.
If manuals were nothing more than "a total cop-out" and unnecessary as you say why do all software companies supply docs in some form or another? They are there for when something does not work as "expected" so you can see what the actual use is. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
What /is/ it there for, then, anyway? He answered that one already. You can add sources of newer packages,
Jon Nelson wrote: like supplementary and packman, and use System Update to update to the newer packages.
I don't have any manuals handy, and I sure as hell don't carry them around with me. Don't you have the electronic ones installed? If not, why not? Saying "Read the Manual" is, quite frankly, about the lamest response I've heard in a long time.
You are entitled to your opinion, but to say that reveals much.
It's not relevant whether I've read the manual or not. Are you kidding? If you ask a question answered in the manual that comes with your software, it is relevant. That's like saying a button in your car labeled "Heat" doesn't really produce heat but just redirects exhaust into the cabin. Yeah, you might get warm, but there are unintended side effects. Is it a labeling issue? No, you are misreading. Should the option even /be/ there? Yes SuSE's inability to upgrade a running system is a very serious shortcoming, and apparently one dictated not by technical feasability. There, you do know the difference between update and upgrade. They are not the same, and you are trying to make out like System Update means System Upgrade. It doesn't. Furthermore, the fact that I'm not the only one that has hit upon this problem suggests that it /is/ a problem. Saying "did you read the manual" is a total cop-out.
Your original problem was answered in the suse knowledge base, was that written just for you? If you mean your mistaking System Update for an upgrade, hopefully you ARE the only one that has made that mistake. For sure, though, attacking Hartmut is hardly a smart thing to do, especially when he has provided the answers to your problems. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
Op woensdag 1 juni 2005 15:19, schreef Jon Nelson:
IMO Debian has, far and away, the best upgrade mechanism available - at one point I had upgraded seemlessly (all while "online" I might add) an installation whose initial install dated back 3 major versions!
In this case point your sources.list file to suse 93 and perform an 'apt dist-upgrade'. More about it at http://linux01.gwdg.de/apt4rpm, but be warned you will be one of 1st to perform the upgrade to 93 this way. -- Richard Bos Without a home the journey is endless
On Wed, 1 Jun 2005, Richard Bos wrote:
Op woensdag 1 juni 2005 15:19, schreef Jon Nelson:
IMO Debian has, far and away, the best upgrade mechanism available - at one point I had upgraded seemlessly (all while "online" I might add) an installation whose initial install dated back 3 major versions!
In this case point your sources.list file to suse 93 and perform an 'apt dist-upgrade'. More about it at http://linux01.gwdg.de/apt4rpm, but be warned you will be one of 1st to perform the upgrade to 93 this way.
I've done upgrades like that - they work great, except for the YOU problem still thinking it's 9.2 (different machine). If that could be solved, I think upgrades via apt would ROCK. I don't understand what can't be taken care of at rpm installation time that /is/ taken care of by installing from the media. If I knew what it was, I could take care of it myself. Honestly, I'd really like to know, even if it's not a technically feasible thing to accomplish, I'd like to know what, exactly, is done at install time /other/ than installing RPMs. -- Carpe diem - Seize the day. Carp in denim - There's a fish in my pants! Jon Nelson <jnelson-suse@jamponi.net>
Op woensdag 1 juni 2005 22:07, schreef Jon Nelson:
If that could be solved, I think upgrades via apt would ROCK. I don't understand what can't be taken care of at rpm installation time that /is/ taken care of by installing from the media. If I knew what it was, I could take care of it myself. Honestly, I'd really like to know, even if it's not a technically feasible thing to accomplish, I'd like to know what, exactly, is done at install time /other/ than installing RPMs.
Perhaps it is the /etc/SuSE-release file or is it /var/adm/YaST/InstSrcManager/IS_CACHE_0x00000002/DESCRIPTION/description? IS_CACHE_0x00000002 may have different names.... -- Richard Bos Without a home the journey is endless
On Wednesday 01 June 2005 22:10, Richard Bos wrote:
Op woensdag 1 juni 2005 22:07, schreef Jon Nelson:
If that could be solved, I think upgrades via apt would ROCK. I don't understand what can't be taken care of at rpm installation time that /is/ taken care of by installing from the media. If I knew what it was, I could take care of it myself. Honestly, I'd really like to know, even if it's not a technically feasible thing to accomplish, I'd like to know what, exactly, is done at install time /other/ than installing RPMs.
Perhaps it is the /etc/SuSE-release file or is it /var/adm/YaST/InstSrcManager/IS_CACHE_0x00000002/DESCRIPTION/description?
IS_CACHE_0x00000002 may have different names....
No, it's /var/adm/YaST/ProdDB/prod_00000001 Just replace all instances of the old version number with the new
On Wed, 1 Jun 2005, Anders Johansson wrote:
On Wednesday 01 June 2005 22:10, Richard Bos wrote:
Op woensdag 1 juni 2005 22:07, schreef Jon Nelson:
If that could be solved, I think upgrades via apt would ROCK. I don't understand what can't be taken care of at rpm installation time that /is/ taken care of by installing from the media. If I knew what it was, I could take care of it myself. Honestly, I'd really like to know, even if it's not a technically feasible thing to accomplish, I'd like to know what, exactly, is done at install time /other/ than installing RPMs.
Perhaps it is the /etc/SuSE-release file or is it /var/adm/YaST/InstSrcManager/IS_CACHE_0x00000002/DESCRIPTION/description?
IS_CACHE_0x00000002 may have different names....
No, it's /var/adm/YaST/ProdDB/prod_00000001
Just replace all instances of the old version number with the new
If that's true, then I was able to do that approx. May 7th, although mine is prod_00000002. Hmm. I wonder what /that/ means. I did upgrade the box from 9.1 (had to install a CDROM temporarily). I'll note that the grub stuff didn't get updated, either, although that's just a detail. Still, there must a some place this stuff is listed (update grub menu, fiddle with /var/adm/YaST/...., etc....) -- Carpe diem - Seize the day. Carp in denim - There's a fish in my pants! Jon Nelson <jnelson-suse@jamponi.net>
On Wednesday 01 June 2005 15:07, Hartmut Meyer wrote:
I know it is confusing and many people belive that this module is meant to do an update of the running system from one release to the next, but it is not.
Having said that though, it does most of the work for you and comes very close to giving you a running update (with the exception of the ProdDB file and the few cases where an update changes syntax in the YaST config files). The manual labour to make the update complete is relatively minor But yes, an upgrade is a large enough operation that it shouldn't be undertaken lightly on a production machine
On Wednesday 01 June 2005 14:07, Hartmut Meyer wrote:
Hi,
On Wednesday 01 June 2005 14:51, Jon Nelson wrote:
On Wed, 1 Jun 2005, Hartmut Meyer wrote:
On Wednesday 01 June 2005 14:06, Jon Nelson wrote:
On Wed, 1 Jun 2005, Hartmut Meyer wrote:
http://portal.suse.com/sdb/en/2003/10/thallma_you_oldpatches.html
Yeah, that sounds like it, but here are some points:
1. if you can't upgrade a running system (Debian can, most others can) without BOOTING FROM THE CD or DVD, then why does YaST have the option available?
You can add other installation sources that provide newer (but non-core) packages like
ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.3/yast- source
And than use this YaST2 module to update all available packages.
That's not what I'm talking about. I'm talking about the "System Upgrade" option/component of YaST. It's sole purpose is to upgrade the entire system (say, from 9.2 to 9.3), and despite no warnings or problems encountered along the way, apparently, it doesn't /quite/ work.
That's the one I meant.
I know it is confusing and many people belive that this module is meant to do an update of the running system from one release to the next, but it is not.
Did you read the manual? It's chapter 2.3.4 "System Update" (SUSE Linux 9.2) in the big Admin manual.
Thanks everyone. By booting with the SuSE dvd and doing an install I solved by problem - strange tho that it did not seen to recognise that I had installed almost all 9.3 packages already. Also it did not reinstall the nvidia drivers :( Also I've used Yast for quite a few years and there is no way I would have thought to check in the printed manual to see if the tool labelled "System Update" did something other than update the system!! Please either rename this tool to "partial system update - read manual first" or add a new warning message when that app is started ! Please. Thanks CPH
participants (11)
-
Anders Johansson -
Brad Bourn -
con -
Hartmut Meyer -
Joe Morris (NTM) -
Jon Nelson -
Ken Schneider -
Patrick Shanahan -
Raoul Snyman -
Richard Bos -
Sid Boyce