For the 2 comics (page 1) who feeled allowed to treat people as "crazy", "insane" or even more people using "sudo su", instead of 'sudo -i", to switch from user to root in a terminal, they should definitely share their experience with FreeBSD and CentOS users.
How to Use Sudo on Debian, CentOS, and FreeBSD
https://www.vultr.com/docs/how-to-use-s ... nd-freebsd
Any of the below commands will allow the sudo user to become root.
sudo su -
sudo -i
sudo -S
If Debian considered that "sudo su" was so "crazy/insane" compared to "sudo -i", "sudo su" would have been forbidden by default in
visudo (managing sudoers permissions).
I've started using Linux with a Netinstall of Morphix I think it was in 2002/3, and never seen people treating people "crazy/insane" without any valid argumentation. Even not sure this is compliant with forum rules.
Well, to not frustrate some people and avoid pointless discussions, let's say "sudo -i" here. This will calm them down.
Now, as I said before, I see a real confusion between starting a root session from a user terminal, then, to execute some administration tasks, and trying to launch graphical applications as root.
This is the point.
dblake2 wrote:based on shep's post i tried entering the command manually from a normal terminal as reg user (gksu /usr/bin/x-terminal-emulator).
You still have some
Stretch packages in your Buster.
I think what you do is wrong simply because "gksu/gksudo,kdesu,kdesudo" commands
do not exist in Buster, and what you try is not clean.
The only administrative graphical application I use is Gparted.
The Gparted launcher command is simply..... "
/usr/sbin/gparted", but when launching the program, a password will be requested because permissions are managed by
policykit-1 which content is:
/usr/share/polkit-1/actions/org.gnome.gparted.policy
Code: Select all
<defaults>
<allow_any>auth_admin</allow_any>
<allow_inactive>auth_admin</allow_inactive>
<allow_active>auth_admin</allow_active>
</defaults>
Then, if you have old application launchers which Exec command contain "gksu", you should progressively forget them, to avoid coming difficulties with Buster.
I do not have any problem in KDE opening Konsole (terminal) as user, and open a new Tab, with a profile defined to open a root session, even with a "RED Tab icon" to clearly identify this special session.
I must say I practically never need to open a root session (mainly to manage deboostrap installations, and chroot).
Then some practices need to be changed from Stretch to Buster.