[opensuse] doubts
Hi, I have the open suse 10.3 installed in my notebook. How can I upgrade for open suse 11?? Thanks, Rods -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rods Listas wrote:
Hi,
Hi,
I have the open suse 10.3 installed in my notebook. How can I upgrade for open suse 11??
Well... you can download the openSUSE 11.0 DVD and, right after you start the installation setup, you can choose upgrade.
Thanks,
Rods
-- Rui Santos http://www.ruisantos.com/ Veni, vidi, Linux! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
If your laptop uses intel wireless (4965) then don't do it. Wait for a while as this wireless only stays up a few hours a a time. (my experience is with an 'N' network). wcn Rui Santos wrote:
Rods Listas wrote:
Hi,
Hi,
I have the open suse 10.3 installed in my notebook. How can I upgrade for open suse 11??
Well... you can download the openSUSE 11.0 DVD and, right after you start the installation setup, you can choose upgrade.
Thanks,
Rods
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-09-22 at 13:51 +0100, Rui Santos wrote:
Hi,
I have the open suse 10.3 installed in my notebook. How can I upgrade for open suse 11??
Well... you can download the openSUSE 11.0 DVD and, right after you start the installation setup, you can choose upgrade.
He could download a live version first, to see if it works on his machine before upgrading. Plus, I always recomend doing a full backup first. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjX7gUACgkQtTMYHG2NR9XrEgCfdJjvzQTpCnDXT3BCzyRX0eRK p8MAoJMox/L9Cjyy3jjDVgTjSXcCUk7m =w+7H -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rods Listas wrote:
Hi,
I have the open suse 10.3 installed in my notebook. How can I upgrade for open suse 11??
Thanks,
Rods
Rods, Before considering an 'upgrade' of 10.3 -> 11.0, I would consider a quick backup of your 10.3 ~/home directory and the needed config files from /etc, mail from /var/spool, any additions to /usr/local and the rest of your data to a separate machine. After backup, I wouldn't do an 'upgrade', but rather do a fresh 'install' of 11.0 on the laptop and then simply restore the backups of ~/home, /etc, /usr/local, /var/spool and your data to the fresh 11.0 install. I, personally, would feel much more confident newly installed base compared to the 'upgraded' base and I have experienced little or no problems in moving between releases this way. Yes, in theory, the 'upgrade' should work just as well as the install, but since there is little time or effort difference required between a 'backup/install' compared to an 'upgrade', I see no reason not to do a fresh install and eliminate any possibility of lingering upgrade issues that might bite you later. You could do your backup with a simple script run from the _backup_ machine as root such as (hack it to meet your needs): #!/bin/bash # ## RUN FROM BACKUP COMPUTER AS ROOT TO AVOID PERMISSION PROBLEMS # mkdir -p /home/backup && chown your_user_name:users /home/backup LOGFILE=/home/backup/BACKUP_LOG # ## note no trailing '/' after your_user_name below # if rsync -av your_user_name@laptop_name:/home/your_user_name \ /home/backup | tee -a $LOGFILE; then echo -e "\n\tBackup of /home/your_user_name -- Succeeded\n" | tee -a $LOGFILE else echo -e "\n\tBackup of /home/your_user_name -- FAILED\n" | tee -a $LOGFILE fi # ## You will need read permission of your config files # if rsync -av your_user_name@laptop_name:/etc/needed_files \ /home/backup | tee -a $LOGFILE; then echo -e "\n\tBackup of /etc/needed_files -- Succeeded\n" | tee -a $LOGFILE else echo -e "\n\tBackup of /etc/needed_files -- FAILED\n" | tee -a $LOGFILE fi # ## You will need read permission of your files in var # if rsync -av your_user_name@laptop_name:/var/needed_files \ /home/backup | tee -a $LOGFILE; then echo -e "\n\tBackup of /var/needed_files -- Succeeded\n" | tee -a $LOGFILE else echo -e "\n\tBackup of /var/needed_files -- FAILED\n" | tee -a $LOGFILE fi # ## quick check # grep Succeeded $LOGFILE grep FAILED $LOGFILE exit 0 You could also consider using the '-r --files-from <textfilename>' options to rsync and do all the operations in a single while loop utilizing a separate text file '<textfilename>' that contained a list of the files you wanted to backup. The point being, a simple backup/restore will allow you to do a fresh install and eliminate any and all lingering 'upgrade' issues. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, Sep 23, 2008 at 12:27 PM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote: <snip>
The point being, a simple backup/restore will allow you to do a fresh install and eliminate any and all lingering 'upgrade' issues.
David ... that is a handy looking little script, and I am quite sure I will avail myself of it to test an "upgrade" process myself. I've been told before that this is a "better" upgrade procedure, and have done it once going from Sled 10 to SLED 10 sp1 and all seemed to go well ... but a nagging doubt lingers: Is the RPM database for the original machine preserved in anyway? Or, is that just munged and un-recoverable from the stand-point of what software had previously been installed, with what versions, and also being able to uninstall using RPM commands? Also, while I know that KDE/GNOME config files from one version to the next generally will stay generally the same, is it not likely that the new versions of things will have SOME new options and new defaults, etc? Therefore, when I overwrite the newly installed stuff, do I not lose that -- possibly at the risk of either sub-optimal performance, if not even some sorts of instability? Just wondering ... Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Peter Van Lone wrote:
Is the RPM database for the original machine preserved in anyway? Or, is that just munged and un-recoverable from the stand-point of what software had previously been installed, with what versions, and also being able to uninstall using RPM commands?
Also, while I know that KDE/GNOME config files from one version to the next generally will stay generally the same, is it not likely that the new versions of things will have SOME new options and new defaults, etc? Therefore, when I overwrite the newly installed stuff, do I not lose that -- possibly at the risk of either sub-optimal performance, if not even some sorts of instability?
Just wondering ...
Peter
Peter, Sorry for the delay in the response. You are correct, the rpm database is not preserved, but then, it need not be. Yast provides an solution for taking your package list with you. Just have yast export the rpm package list and then you can use the list to install your packages in 11.0. (note, I just reinstall and reselect) To create the list, go to yast -> software management -> file -> export. Yast will create an xml listing of all your packages in the default name of 'user-packages.xml'. Each line of the file contains the name and version of your packages. Example: <entry kind="package" name="imlib2" epoch="0" ver="1.4.0" rel="46.3" arch="x86_64"/> <entry kind="package" name="imlib" epoch="0" ver="1.9.14" rel="365.1" arch="x86_64"/> <entry kind="package" name="img2eps" epoch="0" ver="0.2" rel="110.1" arch="x86_64"/> Looking at the list, it is just a package list without any repository information so there is nothing to prevent it from being used when moving from 10.3 to 11.0. After your fresh install, select all of your normal community repositories (packman, openoffice, etc..) Presumably, you can then use the software management -> file -> import function to re-import your complete package list into your new install. I presume that yast will automatically handle the version changes by locating the current version of each package. Somebody else will have to add additional details, but this is my understanding of how it works. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2008-09-23 at 19:07 -0500, Peter Van Lone wrote:
On Tue, Sep 23, 2008 at 12:27 PM, David C. Rankin <> wrote: <snip>
The point being, a simple backup/restore will allow you to do a fresh install and eliminate any and all lingering 'upgrade' issues.
David ...
that is a handy looking little script, and I am quite sure I will avail myself of it to test an "upgrade" process myself.
I've been told before that this is a "better" upgrade procedure, and have done it once going from Sled 10 to SLED 10 sp1 and all seemed to go well ... but a nagging doubt lingers:
I personally prefer doing an upgrade by, er... doing an upgrade :-) This system I'm using has been upgraded several times, in steps, from 8.1 to 11.0, without major hurdles. It can't be so bad. In any case, a full backup is always a good thing. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjdckoACgkQtTMYHG2NR9WdZwCdH4Hlvz16iGhC2ySIZ5G0fIpw YuYAoJfy3xeihckHz0+lmMsLEcF8paH7 =ykPd -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos E. R. wrote:
The Tuesday 2008-09-23 at 19:07 -0500, Peter Van Lone wrote:
On Tue, Sep 23, 2008 at 12:27 PM, David C. Rankin <> wrote: <snip>
The point being, a simple backup/restore will allow you to do a fresh install and eliminate any and all lingering 'upgrade' issues.
David ...
that is a handy looking little script, and I am quite sure I will avail myself of it to test an "upgrade" process myself.
I've been told before that this is a "better" upgrade procedure, and have done it once going from Sled 10 to SLED 10 sp1 and all seemed to go well ... but a nagging doubt lingers:
I personally prefer doing an upgrade by, er... doing an upgrade :-)
This system I'm using has been upgraded several times, in steps, from 8.1 to 11.0, without major hurdles. It can't be so bad.
In any case, a full backup is always a good thing.
-- Cheers, Carlos E. R.
I would second the upgrade root, the backup is essential in either case, and it is occasionally useful to have partioning, /etc/fstab and GRUB info to hand on paper if upgrading. Though if you have an absolutely SuSE vanilla install there is probably not much difference in the options... so YMMV. I dont have such a setup and a clean install would be for me a royal pain. Fixing the things which did not make the upgrade is usually a lot easier than rebuilding all of the non standard stuff from scratch. I would regard a clean install and restore as an act of last resort (things are so SNAFU'd from an upgrade to the extent there is no easy way back), and in recent time only had to resort to it due to hardware problems and in one case a power cut during the install process that left machines concerned in a bit of mess. - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkjeC+MACgkQasN0sSnLmgKcNQCdH4QA0OWIToYYukle9otqH6RO OyUAn3klLEwN9RQXkVPSrDJAK+CktULb =xehO -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2008-09-27 at 11:33 +0100, G T Smith wrote:
I would second the upgrade root, the backup is essential in either case,
You mean 'route', surely? :-)
and it is occasionally useful to have partioning, /etc/fstab and GRUB info to hand on paper if upgrading.
Of course, I forgot to mention that. For any system install/upgrade it is better to have that pritned info.
Though if you have an absolutely SuSE vanilla install there is probably not much difference in the options... so YMMV.
I dont have such a setup and a clean install would be for me a royal pain. Fixing the things which did not make the upgrade is usually a lot easier than rebuilding all of the non standard stuff from scratch.
Just my case.
I would regard a clean install and restore as an act of last resort (things are so SNAFU'd from an upgrade to the extent there is no easy way back), and in recent time only had to resort to it due to hardware problems and in one case a power cut during the install process that left machines concerned in a bit of mess.
Yep. The upgrade broke for me when I tried 7.3->8.1, at the time the switch from yast to yast2 was being made. Yast failed to mount all the needed partitions, and too many packages went to the filesystem root instead of /usr or /opt, filling it up and crashing the upgrade. To compose the damage, instead of a full backup I had made a yast backup, which only saves modified system files. So I had to install fresh and then configure everything again from scratch. Now I always make sure the partitions are mounted, and if not, I mount them manually. So the first recomendation is make a full backup, in all cases, because: - If you do a fresh install, you can retrieve any of the old configuration files. - If the fresh install doesn't work, you can go back to the old version exactly as it was. - If you do an upgrade and it fails, you can restore the backup and try again, knowing what the problem was. Or you can abandon the upgrade and install fresh, having all the configuration files saved. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjeKDkACgkQtTMYHG2NR9VAPQCggkWeoTkZHYc4y8YZ7/4medww XEEAoISASTksFwjlrM+j1D5QqJn6UDro =PfpO -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
Carlos E. R. -
David C. Rankin -
G T Smith -
Peter Van Lone -
Rods Listas -
Rui Santos -
Wendell Nichols