The board for frustrated newbies would be this one. The biggest thing to remember when learning Linux is patience. I know a lot of people who have given up after a few days of things not working like they're used to....it's just a matter of learning the ropes. Just learn a few tips and tricks and you'll be able to set up a system in no time flat.
Root booting directly to YaST doesn't surprise me. In Windows, logging in as the Administrator is allowed and usually what's done. Linux has a bit of a tighter security policy in that logging in as root from the initial login screen is supposed to be ONLY for system maintenance. Normal usage should be done under a user account. Whenever you need administrator access to files, you can use the "su" command in a terminal to become root user ("exit" will drop you back down to the user account you came from). Alternatively, if you have "sudo" installed, you can add your username and relevant parameters to /etc/sudoers, and then use sudo to mimick root user. Just use "sudo <commandname> <flags>".
So if this gives you a no-permission error:
You can use this instead
And that will run that command as root (btw, "Esc" followed by ":q" will exit vim if you try this and find you can't get out ).
sudo vim /var/log/messages
Anyway I run all my boxes with my username in the /etc/sudoers file with the NOPASSWD option so I never have to type in a password. Works pretty seamlessly, and I never have to log in as root. In fact, there are distributions out there that don't have a root account at all and rely completely on sudo in order to get root stuff done.
So the point of this little foray into Linux philosophy has been to say that logging in as root should be used for system maintenance only (ie, when things break horribly) and is generally discouraged. I'm thinking that SUSE sends you to YaST by default since YaST is SUSE's system config tool. You should be logging in as a user and then performing administrative actions by either typing "su" in a terminal or setting up your /etc/sudoers file so you can use "sudo" instead.