Re: [suse-kde] Latest KDE disables graphical login as root?
Hi Shriramana, ... since this is a group discussion, I took the freedom to redirect it back from private mail to the group.
So if according to the geeks here I would be bonkers to login as root graphically, then I need to know how to go to pure text session, right?
... yes and no. What you refer to as "pure text session" is one of the consoles which you can reach via the ctrl-alt-f1..ctrl-alt-f6 keys just as much as is a terminal window. The thing with the ctrl- alt-fn keys has already been pointed out by others. There's nothing special about a terminal window compared to a console screen other than that it does not eat up all screen space and stuff like that. The only specialty is that you should be very careful doing X11 configuration in a terminal window (ie., with X running, that is!) unless you know what you're doing. Also, the "pure text session", which I assume you mean the text consoles with (grey text on black background, nothing else visible) can't start GUI programs. So, beside doing actual X11 config stuff, you never need one of the consoles.
And a "normal terminal window" will have to be opened after logging into root via gfx, right? And I am not able to do that, okay? So I gotta login as a user via gfx and then log out to a pure text session, where I can login as root.
... the first question and/or it's implied answer is wrong. You can log in to the GUI as _any_ user, open a terminal window, and do the "su", "sux" or "sudo" stuff there to become root. That will do perfectly well and you can happily avoid being logged into the GUI as root. So you do _not_ need to log "into root via gfx". This is the last time I say it! It has been repeated more than once here on the list.
Come on man, I donno the commands at the terminal, okay?
... then why did you say you're a text command guy? When someone points you to your statement claiming you're a command line guy then you say you're a click-guy. When someone points you to your statement of being a click-guy then you say you're a command line guy. I tell you something: We continue helping you as soon as you make up your mind _definitely_ which party you belong to. How's that for a start? Your initial question was not about text commands which everyone including me would have happily told you in the first place but you insisted on being logged into the GUI as root. Would you have asked a question like "How do I edit file /etc/some-system.conf?" then it would have made sense. But instead you asked "How can I log into the GUI as root?" which is to some people, well, kinda controversial issue, a sensitive one for others (both of which you couldn't possibly know, ok), thus telling nobody here what you wanted to do in the first place. If you would have asked for what you actually wanted to achieve and not some mysterious path to get there with leaving anyone here in the dark about your goal, then, and only then, help would have mysteriously emerged. So, one thing is to get upset about answers one gets but another thing is to think about what one actually asked for. -- cul8er Paul paul.foerster@gmx.net
Paul Foerster wrote:
... yes and no. What you refer to as "pure text session" is one of the consoles which you can reach via the ctrl-alt-f1..ctrl-alt-f6 keys just as much as is a terminal window. The thing with the ctrl-alt-fn keys has already been pointed out by others.
(Please note that I'm as of now accessing my mail from Windoze. I am yet to configure my ASDL USB modem on Linux. So I can't immediately check out whatever you say.) So take this situation here: I have a Fedora Core 4 installed by the side of my SuSE 9.3. It goes to KDM (I *think* it's KDM) and it allows me to enter my user name and password and login. But it doesn't allow me to enter as root. Now how do I go into root, even via a text terminal?
There's nothing special about a terminal window compared to a console screen other than that it does not eat up all screen space and stuff like that.
I don't understand. By terminal window, you refer to something like Konsole, which opens *inside* an X-Session? By console screen you refer to a state of affairs where the X-Server itself is not running? Analogies from Windows would be: command prompt window accessed by running cmd at Start>Run and DOS (Windows text shell) screen accessed by rebooting in MSDOS mode (or booting from a floppy). Which one corresponds to which in Linux terminology? (Again, you see the effects of my Linux-ignorance - but it's up to you, if you choose, to rid me of my Linux-ignorance rather than berate me for it.)
unless you know what you're doing. Also, the "pure text session", which I assume you mean the text consoles with (grey text on black background, nothing else visible) can't start GUI programs. So, beside doing actual X11 config stuff, you never need one of the consoles.
So you have been telling me to login to root (if at all) only using text. (All right, I understand that in the first place you are telling me NEVER to login as root, but supposing I have such a situation, how do I manage it?) Apart from X11 config stuff, I may need to do partition/bootloader stuff on a root pure text session. Does your statement "besides doing actual X11 config stuff, you never need one of the consoles" still hold true?
Come on man, I donno the commands at the terminal, okay?
... then why did you say you're a text command guy? When someone points you to your statement claiming you're a command line guy then you say you're a click-guy. When someone points you to your statement of being a click-guy then you say you're a command line guy. I tell you something: We continue helping you as soon as you make up your mind _definitely_ which party you belong to. How's that for a start?
OK look - in Windows I can handle the console. I'm a newbie to Linux, okay? So what I mean is: I have the potentiality to be a console guy in Linux since I'm already a console guy in Windows. Hey, if I were already a console guy in Linux, why would I be asking you all these questions and start this thread on how to login (all right all right I won't say it) - come on - you can well understand where I stand. So long as I've not become a console guy on Linux, I still need to do at least *some* things via graphics on Linux too. I've successfully logged in many times in the way that you condemn, to edit my /etc/fstab and /boot/grub/menu.lst files. I was ignorant, okay? So you understand this?: so long as I don't know how to do it via console on Linux and I NEED to do it, I find some other way of doing it, which is via graphics on Linux. Now have I made myself clear?
Your initial question was not about text commands which everyone including me would have happily told you in the first place but you insisted on being logged into the GUI as root.
Certainly my initial question was not about text commands. I wanted to know why that-which-must-not-be-named-so-let-me-call-it-Lord-Voldemort has been disabled in the latest version of KDE (which was what I was informed by a posting on the net).
root?" which is to some people, well, kinda controversial issue, a sensitive one for others (both of which you couldn't possibly know, ok),
At last, you evince a certain amount of *acceptance* for my situation. It's like going to England and using the name Randy. Go there and say "Hi I'm Randy" and see how they react. Any person with culturedness will *understand* that the other guy doesn't know that his name in British slang has a "different" meaning, and not laugh at him.
you would have asked for what you actually wanted to achieve and not some mysterious path to get there with leaving anyone here in the dark about your goal, then, and only then, help would have mysteriously emerged. So, one thing is to get upset about answers one gets but another thing is to think about what one actually asked for.
I think about what I actually asked for and I find: I wanted to know for what purpose Lord Voldemort (see above for explanation) was disabled. This is like asking why the sky is blue. I want to know the *reason* the sky is blue. I do not want to *achieve* anything by asking that question, unless you will accept that knowledge in itself is an achievement in which case I *achieved* the knowledge of why Lord Voldemort was disabled in the latest version of KDE. For me, that's an end in itself. -- Shriramana Sharma http://samvit.org
participants (2)
-
Paul Foerster
-
Shriramana Sharma