I am literally shocked by Yast in SuSE 11.0

[Robert_SK]

I have been using SuSE for many years and it is my favorite distribution. Now I am trying to upgrade from fairly old SuSE 9.3 to SuSE 11.0.

I can hardly believe that I have been unable to set up such a trivial thing as the network. I can't locate neither DNS settings nor the routing table. In SuSE 9.3 it is under Network Devices -> Network Settings, but in SuSE 11.0 I can just assign IP addresses to network cards and that's it. However, when I start the module, it says "Initializing network configuration" and later on "Read routing configuration".

This is for the first time in my life I am asking such a question on the forum.

[Robert_SK]

I have finally figured it out by accident.
If I maximize my terminal window to the whole screen and start yast, I can see:

Network Settings
[Global Options] [ => ...

If I start yast in a standard 80x25 window, I do not see the second line.

It's hard to believe...

[gogalthorp]

Why are you running Yast from the command line???

If you look in the menu you will find a fully GUI version.

[Robert_SK]

I have just one monitor. I did not feel like disconnecting it, so I used ssh to log into the machine and change the settings.

Yast seem to have other serios flaws as well. I tried to put my boot partition onto a SW RAID1 and use LILO to boot from it. However LILO complained about some inconsistency. A quick research on the Internet showed that LILO required a RAID with a version 0.9 superblock. So I prepared my RAID in advance using an older version of mdadm to make it 0.9. Yast detected the RAID1, but it declared it to be RAID0. Fortunately, it did not want to do anything about the "omitted" partition (format it or delete it), so I could successfully install the system on the RAID1. Certainly this should not happen. I should be able to stick with my current partitioning (prepared in advance) during an install.

[Natures_End]

it did not want to do anything about the "omitted" partition (format it or delete it), so I could successfully install the system on the RAID1. Certainly this should not happen. I should be able to stick with my current partitioning (prepared in advance) during an install.

I ran into this same thing. I "-guessed-" it was because I didn't remove the older versioon of suse. So, FDISK ftw. Did a fresh install and never thought about it again till you just mentioned it . lol I dont know if this was the problem or if it really is even a problem, just thought i would toss that little chestnut out here. lol

[gogalthorp]

Yes, doing an upgrade across that many versions is not a good idea. There are just too many changes and old config files may not work

1) Do a full install but tell the installer NOT to format the home partition. If you don't have a separate partition for home back up home some place to preserve your personal files.

2) rename the desktop Directories (.kde / .gnome) in the users home so that new ones are created.