Rajko wrote:
On Sun, 24 Mar 2013 16:13:12 -0300 Claudio Freire <klaussfreire@gmail.com> wrote:
TBH I've always considered "sudo su" rather common and standard.
That could be the case in some other distro, but within openSUSE you will find often recommendations to use 'su' and 'su -' and not 'sudo'.
But sudo doesn't change my environment. su does. That was the point of this discussion. Also sudo -- if you go back to when it first entered suse, DIDN'T reset the environment by default --- it didn't have a BUNCH of options it now has. SuSE took sudo, configured it for their purposes, and left the user with nothing but to go off and use some private copy. Same with perl and vim among others. The problem is that these system utilities are there ***FOR THE USER***, not for the private use of the distro. I use a distro to get precompiled binaries of utils I use, not to have all of my standard utilities taken away and modified to be non-standard and have arbitrary/non-standard functionality. Suse needs to realize -- if the OS NEEDS a non-standard version, it needs to NOT take over the /usr/bin or /bin copies -- but maintain it's own set of "internal-use only"... As it stands, Suse feels free to take over all of /{,usr}/}{s,}bin,lib64}/ and tell users how to use standard programs or not to use them at all. If users want to use those programs, they need to go find a distro that compiles them and load it into /usr/local, in addition to letting suse have all of /usr. That's ridiculous -- that's not serving the users -- that's serving SuSE and telling the users they are on their own if they mess with any of their own system's programs, just like you just did among several others.
A sole purpose of such answers is to point out to readers of our mail list archives that it is not problem with openSUSE setup, but with your customization.
NOT at all -- It's suse that is customizing standard utils not to work in standard ways. My "customizations", as you call them, are to try to get back to standard functionality. So far, the entire venture into systemd and moving all the boot utils to /usr has been pointless and disaster for systems compatibility. No one has come up with any good reason to move all the boot utils to /usr -- No one wants to answer that question. There is no reason why the file systems systemd needs to run can't be mounted by scripts on DISK or initrd, and then started -- or at least no reason that anyone has admitted to -- like "we can't allow user scripts to have control during boot or it will defeat the purpose of secure boot -- which is to kill the personal computer as a general computing device -- which most users do not want! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org