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 didn't forget my root password, I just want to change it after using the same password for years.
What is the proper protocol? Should I change my root password in single user mode by booting into single user mode or change my root password in the current runlevel my system is booted at?
I guess my question is too advance for the LQ community here to answer.
I will use single user mode
It's quite common not to get answers to questions that are also so simple anyone could find the answer with a 5 second google search. Threads like that go days without a reply and usually never get replies. People here value effort instead of the quick fix. Speaking from personal experience of looking for a quick fix instead of doing my own research.
Also insulting the community by calling your question to hard is wrong as well. The people here are volunteers with lives to live. They do this in their spare time, they don't sit there all day refreshing the browser to answer questions immediately. Generally give it 24 hours before anything else.
Last edited by jmgibson1981; 05-08-2017 at 06:20 PM.
It's quite common not to get answers to questions that are also so simple anyone could find the answer with a 5 second google search.
I did not ask how to change my password. I know how to do that. I was asking if I need to be in single user mode to change the root password or if it's ok to do it at the current runlevel I'm in.
You will need the old password, and need to have root privs, so there is no additional safety to be gained.
jmgibson1981's point was valid. Everyone here volunteers their time of course, and each individual decides how to apply it, which posts to answer and which to skip in their time available. There is always the expectation that we have done our own searches before asking others for help. Please do not think that to be unfriendly or unwelcoming!
Also, jenkins123, your first post was made at 17:39 and your second one was not quite an hour later.
As my own general rule, when I post a Linux Question, I usually wait 24 hours before I check for an answer, because I know it takes a while for a willing volunteer to stumble over it and choose to answer it.
I did not ask how to change my password. I know how to do that. I was asking if I need to be in single user mode to change the root password or if it's ok to do it at the current runlevel I'm in.
Hi jenkins123 and welcome to LQ.
There's no harm in trying that, and it would work fine, allowing you to change your root password. To be clear, I have the opinion that at a command prompt if not root, you could type "su" and the existing root password at the next prompt, to become root and then issue the "passwd" command to change your password.
Sorry you feel there was indifference, what others are saying, which is that not everyone is on call here, waiting with catlike readiness to answer questions. Sometimes there may be a surprisingly fast response, and sometimes there may be a delay, and I feel that it is reasonable to wait about a day to see if anyone has any recommendations. Meanwhile you may self-resolve, and that is fine, we're all hoping that people who post questions are not simply asking for quick, simple answers, but instead working to learn continually. Myself I have started some questions and then never posted them because in my efforts to write a clear question and describe my situation, I had a moment where I realized the solution.
Best of luck and looking forward to any future questions or posts you may have.
If you feel that this problem is solved, then please mark the thread as solved (using the Thread Tools in the page) and it likely will help a future searcher of this very same question.
Myself I have started some questions and then never posted them because in my efforts to write a clear question and describe my situation, I had a moment where I realized the solution.
So true, so true - been there done that (as it were) more than once
I usually end up writing the question, posting it, then at times almost immediately after posting it. I end up figuring out the answer in post posting, afterwords.
Also, be very mindful of the fact that the root user is not the only way to gain "rootly privileges." (In fact, on many systems, that user-id is simply disabled.)
On most Linux systems, if you are a member of the wheel group (as in: "s/he's a 'big wheel' around here ..."), you can become root simply by entering sudo su and entering your own(!) login password.
This, of course, is why you should never use any user-id which is a member of this group, unless you are performing system maintenance. "Your every-day userid" should not be Billy Batson. Thus, if someone tricks you into saying, "Shazam!" ... and they very-easily could ... absolutely nothing should happen.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.