I have recently installed Mandrake 9.1 on my Windows box. Dual-boot works fine. A lot of extra entries in LILO, but I think I can figure that out. What I am having issues with is when I get to the graphical log-in screen, all that's listed is my user account. There's no way/option for me to log in as root. In order to log in as root, I have to go to a virtual console, which, of course, is command-line only and means I can't follow a lot of the instructions I recieve from the helpful people on several forums I browse.

I read on one post (somewhere) about how I could use any login "client" I desired - and how to set this up. But I still can only log in as a user, regardless of which login manager I choose. Any help???

Hi!
The only thing you have to do when you are in the graphical log-in screen is typing 'root'; in fact when I press 'r' I pre-select the root user (even if this user is previously hidden) then select it (with the mouse, for instance) and you will be able to loggin as root
Regards

No, No I was wrong:
You can see which users are hidden and change this with 'kde control center', in the system section you'll find something like 'acces administrator', then choose 'administrator mode'...
I'm sorry about the last post
Regards

Which graphical login are you using? GDM, KDM or XDM? I seem to recall an option somewhere in KDM disallowing root logins. I can't remember where this is, though. Try man kdm. You shouldn't really need to login in as root. Just log in as a regular user and type su and then give the root password when you want to do something only root can do.

Be warned the downside of login as root . If you make a mistake as root . Many a good installation has been ruined by trying to learn while logged as root. Been there done that.
Regards
SHARKEE

Here's how, but I do not recommend that you login as root in windows. DO NOT connect to the net if you are on broadband, shouldn't on dial-up either.

This is for KDE. Start thingy then Configuration then KDE then System then Login Manager. Click the tab users. Then click 'Selected only' then put a x next to the ones you want to appear.

I can't stress this enough. You should not login to x as root. I can not think of any reason for you to do so either. One mistake and your done.

Later

run "init 3" as root and then startx

I want to thank everyone for their advice on how to fix this - I have several options to go through in my attempts to get this straightened out. Very nice.

Also, I want to express my gratitude for the concern about me logging in as 'root'. It's really not an issue, tho'. This is a test/learning installation - if I blow it - I reinstall. Done that nearly half-a-dozen times this weekend already. The reason I need to log in as 'root' is that my network config is out of whack and the only fix suggested that I haven't tried requires that I have 'root' privileges to configure the network interface and how it's accessed. So, I'm not going willy-nilly as 'root', I am attempting to do something that REQUIRES that I be logged in as 'root'. It says so in the dialogue box that pops up - doesn't ask for the password, just pops up and reads something like 'Stop. You must be logged in as "root" to do this' or close.

Good day and thanks again. I'll post whether anything works (and which it was) when I get it done.

I know you've heard this before, but you can do what you are trying to do without logging is to the graphical interface as root. All of the graphical windows that you can launch from the menus can also be launched - as root - while logged in as a normal user. Of course, all of the command line things can be done as well - and without the risk of being root in a full blown graphical shell.

Just log is as a normal user, open a terminal session (Konsole in KDE), type su (for super user) and hit enter - followed by your root password. Once you are "root", you can then type the command for whatever graphical tool you want to launch and you will be able to do the things only root can do in it. For example, if you want to edit your modules.conf file, make yourself super user root, type kwrite at the # prompt in the Konsole and press enter. Now you are using a nice graphical editor, but you have all the priviledges of root.

If you don't know what command launches the graphical tools, just find them on your "K" menu, right click them and look at the properties. The command that launches that tool will be listed right there. If it isn't in a folder that is in your path, you may have to preceed the name of the tool with the path to it (e.g. /usr/sbin/kwrite).

Thanks FallGuy. You're right, I've heard all of that before. But never with such detail in explanation. I've been told "login as 'su' and then do it" but never the whole "open a Konsole window..." step-by-step. I'd love to have you write the tech docs I need to read. To state it more simplistically, "Muchas gracias."

Now, to what actually worked!!! I had previously gone into the Start thingy>Configuration>Login menu/app and modified my login to start with GDM instead of KDM, but it wouldn't come up that way when I logged out. After I left this forum, I went to the Mdk box and rebooted (from virtual console) rather than logout (from GUI). When the login screen came up it was Gnome (as I'd configured) AND required that I type in my username and password. Then I went ahead as 'root' and changed the configurations as needed. (BTW, the network config changes didn't help.) So, the big issue was that I needed to make the changes suggested AND reboot. So, in addition to all of the other useful/helpful info here, that's the solution that worked for me.

One thing you might find helpful is, once you're in X Window environment, open a terminal, su to root, and issue

linuxconf

At least on Mandrake, this provides an interface for configuring just about anything--as well as examining dozens of logs, etc. One of the first choices you'll see is "networking" and I wouldn't be surprised if you could do all the configuring you needed to do, right there. Maybe!

thanks for the advice on logging into the konsole as 'root', but I get errors trying to run linuxconfig from the konsole. don't know why, but I do. i found a work-around, anyway.

No thank you needed - but appreciated. I think most people that are seasoned enough to give useful advice often forget just how little they knew when they first started out. As a result they take too much for granted and end up leaving helpful tips that only the other seasoned pros can follow.

Oh yeah ... and I used to teach (not Linux).

I have experienced the "you're too dumb to understand the answer" phenomenon (sp?) a LOT since coming to the Linux world. As a matter of fact, I stayed away from Linux for a long time for that very reason - I'd ask questions and the standard answer was "read the docs". Not inaccurate. Not rude or arrogant. But definitely burdensome until you learn the jargon to understand the docs. One hell of a learning curve for the "green-as-a-gourd" bunch.

And you have my respect. I used to think I could teach. I knew the material. Forwards and backwards. But why couldn't these lunkheads get it??? Found out that most of teaching was figuring out how they LEARNED. (Red) Hats off to you. (had to do it)