What other distros' apps are compatible with PCLOS?

[inseine]

6) Omitting sudo did not allow the program to install

Run the installation command as root user, instead. In other words, if the instuctions are:

$ sudo run-this-installation-program

do this, instead:

$ su
# run-this-installation-program
# exit
$

A question..

The install code - XXXX - has two instances of XXXX in it. How is that handled using su?

[Archie]

It's not about not using sudo. It's about responsible use. Even if you are the only user on your machine and you use sudo, setting it up correctly will help you understand that it's purpose is not to conveniently give root privileges to users.

Some helpful reading:
http://www.gratisoft.us/sudo/sudoers.man.html
https://wiki.archlinux.org/index.php/Sudo

Allowing a user complete root privileges defeats the whole idea of having a user session. Might as well logon as root. It's knowing the restrictions - which executables would be allowed to use, which machine the commands are restricted to, password timeouts, etc. all constitute to responsible, hence secure use.

No more sudo lest we risk the wrath of the admins. There really just those who listen, hear and understand ... and those who stick with the little they know because it's easier for them. Sometimes I prefer to think I'm with the latter.

6) Omitting sudo did not allow the program to install

Run the installation command as root user, instead. In other words, if the instuctions are:

$ sudo run-this-installation-program

do this, instead:

$ su
# run-this-installation-program
# exit
$

A question..

The install code - XXXX - has two instances of XXXX in it. How is that handled using su?

Just remove the sudo part. The && takes care of the other parts.

Code: [Select]

[user@localhost ~] $ su
[root@localhost ~] # mkdir -p /opt/odesk && tar -C /opt/odesk -jxf odeskteam_bundle-3.2.43.tar.bz2 && /opt/odesk/bin/odeskteam/installer.sh
[root@localhost ~] # exit
[user@localhost ~] $

[Tony]

While it's being talked about; 'su', then root password, gets us root privileges.

I've read on the Forum to not use sudo, so I don't, and have no need to.

From the link: https://wiki.archlinux.org/index.php/Sudo
Rationale

Sudo is an alternative to su for running commands as root. Unlike su, which launches a root shell that allows all further commands root access, sudo instead grants temporary privilege escalation to a single command. By enabling root privileges only when needed, sudo usage reduces the likelyhood that a typo or a bug in an invoked command will ruin the system. Sudo can also be used to run commands as other users; additionally, sudo logs all commands and failed access attempts for security auditing.

      The link goes into a lot of detail of how to use 'sudo'      

I'm really not a command line type guy, unless I have to be, which is generally a lot of fun.
I have installed Avast!4linux workstations, a .rpm package from a totally obtuse source; an Windows Anti-Virus Company,  -- only using su.
I don't really understand the danger of sudo usage, but I'll look online for a clear answer out of interest. Or maybe best I don't know what the danger is.   Actually that's not good is it, best to know the danger.

It's not about not using sudo. It's about responsible use. Even if you are the only user on your machine and you use sudo, setting it up correctly will help you understand that it's purpose is not to conveniently give root privileges to users.

OK, that's enough info actually. I get it, takes a bit of time for the penny to drop sometimes.  

EDIT: Old-Polack has a sticky clearly explaining the issue here:
http://www.pclinuxos.com/forum/index.php/topic,90479.0.html

[Archie]

Hi Abraxas.

One fundamental concern is the passwordless sudo. This IMHO is a really, really bad way to set up the tool. It basically gives the user the same rights as a user without needing even a password. Then there's a setup that even with a user's password, the user have access to ALL root commands. This is a bad setup as well.

One difference I can think of between sudo and su is the password timeout. In su, as long as you are in root mode, you have root privileges. I very seldom use su.

Where as in sudo, I have set my password to expire in a minute. If I have to issue a privilege command, like for example a mkdir on /var/www/html (which only apache has privileges to) as my user ... every timeout, I have to supply my user password. It's not elegant, it's not easy ... but you'd be surprise at how much CLI stuff one can do in a minute.

sudo is very dangerous when used in an irresponsible way ... the buntu way of sudo is irresponsible... very similar to a single-user in Windows where the user is also the administrator.

[Tony]

Thanks for the explanation Archie.