Consensus: don't run anything on the root account..... tfw

not on my machine

>>61019552
The only program I run as root is sudo

I only have my root account. This way no one can hack me since the root account is already logged in.

>>61019552
You're doing it wrong. Set up groups with proper access control to the things you need, and ensure you're user is in that group.

Using sudo is for people too lazy to actually do it right, or for genuine system management tasks.

Why do people even use Sudo

I just su when I command terminal in and be like bam bam bam fuck my shit up

Linuxers just tell normies this so they won't bother them about their Ubuntu installs

>>61019552
Yeah it's annoying, easy fix is to just run everything as root including your desktop. If it's good enough for older Windows it's good enough for me and you.

File: bait.png (627KB, 1597x1600px) Image search: [Google]

627KB, 1597x1600px

>>61019668
You can log in twice you realize

>>61023237
CURSE YOU MULTIUSER SYSTEMS

regress to windows 95 when

use groups properly

The consensus is don't be a retard. Since most people aren't very good at that the fallback is don't run anything as root.

>>61022247
right, because single user windows were the picture of security and stability, right?

>>61023285

I think the issue is more that, applications that claim they require root access aren't always verbose about what files they are trying to read/write/execute. Makes it kind of tough to figure out how to set permissions.

>>61019552
>Consensus: don't run anything on the root account..... tfw only half of the programs on linux don't run properly unless on root.
chroot is your friend

>>61019819

$ dpkg-query -l sudo
dpkg-query: no packages found matching sudo