Re: One last try...
On Sat, 2003-04-26 at 15:29, Kent West wrote:
> Z wrote:
>
> >What do I have to do to get this thing (X) installed so I can log in as
> >root? Frankly, I couldn't do it in the other distributions either, but
> >they at least allowed me to offer the password and do most changes.
> >
> >When the graphical log in comes up on boot, how do you get around it so
> >you can log in as root? Or is there a way to log in as root when you
> >are already logged in as a routine user from a counsel or terminal?
> >
>
> As others have mentioned, you really don't want to run X as root as a
> general rule. You're better off using sudo.
>
> Or if you want, you can log into X as a normal user, open a terminal
> (xterm, Eterm, Aterm, Gnome Terminal, KTerminal, etc), and then use "su
> -" which will ask for the root password. That'll make you root in that
> terminal window, and it may (or may not - I think it's changed from
> version to version) automagically set up your authorization to run
> graphics apps as root in the X session in which you're logged in as a
> normal user. If you do this, change the background of this terminal
> window to reverse video, or change the color, or tweak your prompt to
> scream something like "WARNING: YOU ARE RUNNING AS ROOT> " in flashing
> neon colors, so you'll always know, hopefully, that you're not a normal
> user when you run
> "RunMeToWinTenThousandDollars-anderaseyoursystemandspamyourexwifeslawyer.bin".
>
> If you really want to log into X as root, there are a couple of
> different ways. One is to edit the configuration files for your session
> manager (KDM, GDM, etc). You'd probably want to search the archives or
> google for the specifics on doing this.
>
> The other way is to shell out to a virtual terminal (Ctrl-Alt-F2 fer
> instance), log in as root there, and then start up a second instance of
> X with a command like "startx -- :1" (the first instance would be :0).
> If you don't want two instances of X running (the first as a normal user
> and the second as root - switch between them with Ctrl-Alt-F7/F8), or if
> your graphics card doesn't like that and hangs your system, you'll have
> to first shut down your session manager, with a command like
> "/etc/init.d/kdm stop", and then just start X with the normal "startx"
> command. Now you're all set, with a loaded gun and a rousing
> finger-tapping tune playing in the background. Have fun!
>
> --
> Kent
Thanks for the loaded gun and pretty new bullets Kent! LOL
I really do need to know these things if I'm going to change these
networks over and tweak these things. I suppose in the long run, after I
screw things up good a few times, I'll appreciate the precautions.
But being old enough to have gained a micron of wisdom I am able to
learn from the mistakes of others. Perhaps some other more specific
questions and answers will get me what I really want.
For example: Unfortunately the computers I've installed Linux on have
all had Winmodems. Ugh. Fortunately, I have Windows running on a box
that has a Windmodem, and it's hooked up to do what I need to do.
Great! I'll just copy the article I wrote to the Winbox over the local
network so I can fax it to the editor. Oops. That's not ok with
Linux. Fine by Windows. I know that. It'll stupidly take anything on
the local network that any box wants to do (within limits for the shared
folders). So, even though I can mount the shared folder in the Linux
box, look at the contents, even copy the content on the Winbox to the
Linux box, I can not copy a couple files to the Winbox.
I'm creative. I'll just save it to the zip disk and carry the I
suspect just because I can do just about anything with that other
operating system to make folks happy they think I should know about
Linux as well... damn file over there and put it where I want it so I
can fax it. Ooops... That's not ok with Linux. It doesn't want me to
write to the Zip drive. "Writing to device is not supported". With
people if they can read they can usually write too. It's a local drive
for crying out loud! What next? I can't write to the hard drive? LOL
The way the computer acts when it accesses the zip drive gives me the
impression Linux has an ongoing feud with Iomega. Let me guess...
apt-get install jazip?
So, what gyrations are required to copy a file from
file:/home/Z/Documents/Articles to file:/mnt/SharedDocs (Which I believe
is the Winbox shared files folder) What I get is "Access denied" Could
not write to etc... [cancel] [skip] [auto skip]
It will actually write to file:/home/Z/mnt/DS1WINXP/SharedDocs but that
is a local file and doesn't write to the other computer, even though it
looks like it should.
Well, I've been around long enough to know about permissions and such
so I managed to change the user account to belong to everything in the
Linux universe (or so I believe, though I'm probably mistaken). Ooops,
sorry, that's not good enough. LOL
If the deadline for that article was today, I'd used the Linux CDs for
target practice. LOL The deadline isn't today though, so I can wait
until someone throws me life line.
I am certain that once I understand some of these things they will be
incredibly simple, but I'm wandering in the wilderness still. I do read
the man pages when I can find them or make them work, and I do look
around and read a bit before I ask questions here. Hell, I even have a
whole training course on CD. Oddly, it only runs on Windows, LMAO. I
think my real trouble is I haven't learned the jargon, or have the
references yet to understand everything I'm told. Y.E.T.
Thanks again.
Z
Your Eligible Too. YET.
PS... how did you know I formatted the hard drive after I spammed my
ex-wife's lawyer? <eg>
Reply to: