Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a command prompt that I like and edited .bashrc to get it to happen on every terminal instance. However as soon as I do a SU command the prompt changes back to the original. Where is the file to configure the root users prompt?
Also if you happen to know, when in terminal mode if you do an "info" or "help" screen how do you get back to the command prompt without closing the window and starting over?
I've still had no luck getting my Apache server to work.
Where is the file to configure the root users prompt?
/root/.bashrc
Quote:
Also if you happen to know, when in terminal mode if you do an "info" or "help" screen how do you get back to the command prompt without closing the window and starting over?
In some systems, you can create root/.bashrc for superuser so that /home/user/.bashrc is for the user. It could be different in some other distros. You may want to google about .bash_profile as well. Do a "source /etc/profile" to see if it works.
I think, if I get you right to escape from a "manual" page like from "man emacs" you can simply type a "q" to drop back to the command prompt.
Sorry, I am not able to comment about the Apache server.
Perhaps you can open a new thread, and give more info
distribution, problem, errormessages.....
Editing the root->.bashrc got me the prompt I wanted. Thanks.
Q: A further question is, why I cant see the .bashrc file in the root using Terminal with the "ls" command even though I'm logged on as SuperUser? When I couldn't see it I tried to create it with gedit. Gedit said the file existed already. Then I did "gedit .bashrc" which worked even though the "ls" command doesn't see the file. How many other interesting files are invisible.
Q: Do you know how to get the Gnome "File Browser" to work under a SU permission set? Can you start FileBrowser from a SU terminal to get there?
My Apache Server says on boot: "Can not bind to 192.168.1.100 creating log file failed" 192.168.1.100 is my static IP address for the Fedora box. I can ping that ip address do problems locally and on other machines in the house. There are some other screwy symptoms. Is there a log file that has a record of the Apache output on boot? I'll post a new thread on my Apache problem soon.
Q: Why does gedit give me this error even though it loads and worksgedit:2925): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
Last edited by scotthill; 01-02-2009 at 11:32 AM.
Reason: I'm always less than perfect the first time. Edit->Compile->Test
Editing the root->.bashrc got me the prompt I wanted. Thanks.
Q: A further question is, why I cant see the .bashrc file in the root using Terminal with the "ls" command even though I'm logged on as SuperUser? When I couldn't see it I tried to create it with gedit. Gedit said the file existed already. Then I did "gedit .bashrc" which worked even though the "ls" command doesn't see the file. How many other interesting files ar invisible.
These are dot files, or hidden files. ls -a will reveal them to you.
Quote:
My Apache Server says on boot: "Can not bind to 192.168.1.100 creating log file failed" 192.168.1.100 is my static IP address for the Fedora box. I can ping that ip address do problems locally and on other machines in the house. There are some other screwy symptoms. Is there a log file that has a record of the Apache output on boot? I'll post a new thread on my Apache problem soon.
You might want to start a new thread on this, it's really unrelated to your topic and it won't get much exposure to the right people.
Q: A further question is, why I cant see that file in Terminal with the "ls" command even though I'm logged on as SuperUser? When I couldn't see it I tried to create it with gedit. Gedit said the file existed already. Then I did "gedit .bashrc" which worked even though the "ls" command doesn't see the file.
because it is a hidden file (mark the "." before the filename)
To see it type
ls -a
Quote:
Q: Do you know how to get the Gnome "File Browser" to work under a SU permission set? Can you start FileBrowser from a SU terminal to get there?
in a terminal type sudo nautilius
Quote:
Q: Why does gedit give me this error even though it loads and worksgedit:2925): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
Q: Do you know how to get the Gnome "File Browser" to work under a SU permission set? Can you start FileBrowser from a SU terminal to get there?
The root user by default is not given authority to connect to a running x-server started by another user (just like all other users). This has been covered multiple times here, so I suggest searching the forums for it if you want to set it up.
But you can also run any gui program with root permissions from a normal user's terminal by using gksu or gksudo: e.g. "gksudo nautilus".
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.