On Wednesday 14 March 2007 08:57, Abstract wrote:

Adding to that, can smart or any other package manager be used instead? I know in the past I heard you could not upgrade suse major revision upgrades, just minor.

-rami

On 3/14/07, riccardo35@gmail.com wrote:

...

- can yast be used to upgrade Distribution ?

for example. upgrade from SuSE 10.2 to 13.0 ?

Welllllll....Don't know about now, but way back when, I upgraded 8.0 to 8.1 with apt-get. Just changed my source files from 8.0 to 8.1 and let it go. Worked pretty well but there were things that had to be fixed.

Would be interesting to know if it can still be done. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2007-03-14 at 08:57 -0400, Abstract wrote:

I know in the past I heard you could not upgrade suse major revision upgrades, just minor.

Rubish! I upgraded from 9.3 to 10.2, via the install dvd. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFF+Sn0tTMYHG2NR9URApo+AJ9wV5h2f6IBJo7hGD3HjqwFL0O3mgCdHZ3t gLNGAjDNDKVqnQz613e4Ytk= =KXf4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Richard Bos wrote:

On Thu, Mar 15, 2007 at 12:11:46PM +0100, Carlos E. R. wrote:

...

The Wednesday 2007-03-14 at 08:57 -0400, Abstract wrote:

I upgraded from 9.3 to 10.2, via the install dvd.

And me too :)

I'm planning to do just that "real soon now" on several boxen (laptop, desktop, servers, 32bit, 64bit), some of them "mission critical" (like my laptop ;-) ). Any snag I have to watch for ? Any recommendation (outside of the usual "make a backup/mondoarchive first") ? TIA Cheers. Bye. Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan@iba-group.com http://www.iba-worldwide.com The contents of this e-mail message and any attachments are intended solely for the recipient (s) named above. This communication is intended to be and to remain confidential and may be protected by intellectual property rights. Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipient(s) is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. Ion Beam Applications does not accept liability for any such errors. Thank you for your cooperation.

S Glasoe wrote:

Watch out for the kernel 2.6.18.8-0.1 update either during or post update/upgrade. Known issue is that /boot/grub/menu.lst is being changed in ways that are not always user friendly. I advise making backups of /boot/grub/menu.lst to /etc/or /home/some-user before doing the kernel 2.6.18.8-0.1 update. Soooo, it wasn't just me, then ;-)

Already noticed that on a server at home (fresh install). Thanks for the tip, I'll keep it in mind. Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan@iba-group.com http://www.iba-worldwide.com The contents of this e-mail message and any attachments are intended solely for the recipient (s) named above. This communication is intended to be and to remain confidential and may be protected by intellectual property rights. Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipient(s) is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. Ion Beam Applications does not accept liability for any such errors. Thank you for your cooperation.

On Thursday 15 March 2007 09:01:05 am Joe Morris (NTM) wrote:

S Glasoe wrote:

...

Watch out for the kernel 2.6.18.8-0.1 update either during or post update/upgrade. Known issue is that /boot/grub/menu.lst is being changed in ways that are not always user friendly. I advise making backups of /boot/grub/menu.lst to /etc/or /home/some-user before doing the kernel 2.6.18.8-0.1 update.

Make sure you follow the advice in the release notes, i.e. Booting Multiple Instances of openSUSE on One System If multiple instances of openSUSE 10.2 are installed on one machine and the instance in partition 2 is booted from the GRUB in partition 1, the entry in menu.lst in partition 1 for partition 2 should contain the entry: kernel /boot/vmlinuz initrd /boot/initrd instead of kernel /boot/vmlinuz-2.6.18.2-23-default initrd /boot/initrd-2.6.18.2-23-default With this change, it is safe to update the kernel in partition 2 and the system can still be booted from partition 1.

I suspect that is the problem you had Stan. The update worked flawlessly here.

-- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64

Nope. Single instance of a single 9.3 install upgraded to 10.2 totally trashed /boot/grub/menu.lst. I've checked/updated several 10.2 machines and this happened on all of those. Where I may see a clue is in using the generic vmlinuz and initrd links to the kernel versus appending the kernel version. I do believe that 10.2 has been using the appended version number style. I thought that strange but didn't go change it to vmlinuz and initrd assuming it wouldn't matter! Hmmm.... Stan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org