SlackwareThis Forum is for the discussion of Slackware Linux.
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.
If possible I think it is best to avoid running your unit as root. It is better to run your unit as a regular user and give that regular user root privileges as needed.
Just my .
hitest, how to give that regular user root privileges? I normally skip this part, in terms of my slackware reading, as I thought I would use root forever.
hitest, how to give that regular user root privileges? I normally skip this part, in terms of my slackware reading, as I thought I would use root forever.
As previously mentioned you would first create a new user with the adduser command. Then at a shell prompt when root privileges are needed type su then your root password.
Slightly off topic but I thought I would test this just to see if they really did stop you running as root. Yes it is a really bad idea but at the same time I don't really agree with software preventing you doing these types of things. Anyway, I could run Chrome (version 10.0.648.205) as root without issues. So if it wouldn't start perhaps it is another issue rather than Chrome actively trying to stop you running as root.
P.S. All that said, I agree with the others. Don't run as root!
Thanks ruario,
Exactly, Chrome shouldn't prevent me running as root, I chose linux, hoping to have more freedom.
Don't want to start a fight, just my 2 cents.
Thanks ruario,
Exactly, Chrome shouldn't prevent me running as root, I chose linux, hoping to have more freedom.
Don't want to start a fight, just my 2 cents.
This is just Google acting stupid.
"What a brilliant idea: Users are all stupid so let's prevent them from having options. We (Google) know better."
Well, we users do have options, we can choose another browser.
@h3lder: Even though I Opera employee (and hence I have a vested interest to get you to try our browser ) to be fair to Google, in my own tests (as I mentioned above), I saw no evidence that they do this. I was able to run Chrome as root no problem. Have you seen differently?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.