I found a (lengthy) guide to doing this but it is for gksu which is gone. I have to imagine there’s an easy way. I am running Ubuntu.
I found a (lengthy) guide to doing this but it is for gksu which is gone. I have to imagine there’s an easy way. I am running Ubuntu.
It’s a relatively simple question, but it’s a loaded question, it’s like someone asking you how you run “apt-get upgrade” on Windows, the question implies that this is possible and necessary, the correct answer to any such question is “what is it that you’re trying to accomplish? Why do you think you need this?”. 99% of the times the answer is that the person is trying to do something else entirely, this is known as the XY problem, the person has problem X and is asking how to solve problem Y that he’s having because he thinks that’s the only way to solve X.
In OP’s case he caused the issue by running one program as root, and then everything that program touched needs root now, so he needs to run things as root because he’s running things as root, it’s a cyclical problem, if he had never ran things with sudo he wouldn’t need to run things with sudo. Everyone was asking him why he feels he needs that and he wasn’t answering, in one answer he let it slip his original mistake that caused all of this headache.
Yes, the community can be a bit toxic sometimes, but if everyone is asking you “why you think you need this?” There’s a good chance you don’t, and if you refuse to answer the questions of people who are trying to help you, you make it real hard to be helped.
Sometimes people want to be generally helped, and sometimes people just want an answer to their question. If the answer is “it’s impossible” then that’s a valid answer, but if the answer is “I’m not going to tell you, instead I’m going to assume that what you actually want is me to teach you why you were wrong to ask the question in the first place” then theres a good chance that actually they just wanted an answer, and you deciding for them what they need comes across as patronising.