altair4 wrote: ⤴Sat Apr 21, 2018 10:12 am
We don't need no stinkin' gksu.
We Linux desktop users have an understandable feeling of superiority over those poor Windows and macOS users. You can't feel superior if you are part of the majority. Removing gksu and making all of those HowTo's out there that specify it's use useless is just a way to remove the wheat from the chaff.
What are you on? I'm having hard time believing you're not a troll. Next phase, remove
sudo and
su?
Sudo is a highly configurable system - it's different from pkexec, as I understand that with
pkexec the program will not run as root, unlike with
sudo or
su which execute as
root, or as another defined user. I have a very complex
/etc/sudoers, with many users, user groups, commands that ask no password, ask the users password and those that ask for
root password - I also have complicated command definitions, where for example running a command with certain parameters (using GLOB's for filename parameters) asks users password, but the same command with different parameters is asking for
root's password (and the timeout is considerably shorter), etc.
It's a super tool - and if you're against
gksudo,
lxsudo and other graphical wrappers, then you're against
sudo itself too. Heck, maybe you're even against
su - which is crazy.
In your face Windows.
Linux and Unix has always had a gazillion ways to achieve one thing. Well, Perl has even more, but then again how many use it outside *nix-like systems? Some, sure, just like there are Python programs with installer that installs the runtime, so the user doesn't have to install Python separately, so have there been several Perl applications doing the same. In fact, for Windows, there is a product called ActivePerl, which let's you package your Perl-application in Windows installer (.MSI I think, though it might be an .EXE as well - but why?
The fact that we have
su and
sudo, and GUI wrappers for them, like
lxsudo, after the distro defaulted to
pkexec is a richness - and I can't understand why they didn't ship
gksu-package pre-installed with the distro, what I can't fathom is why on earth did they have to remove the package from repositories? And yet there are many other
su/
sudo wrappers available, like said
lxsudo. So WHAT'S THE POINT!?
It broke many of my scripts and made me search for a solution for some time, without no benefit (and one thing you expect with Linux is that such change won't break a huge load of scripts and even applications) - until I first found
pkexec, but I had no luck with couple scripts that called
sudo or
gksudo (depending if it was ran from terminal) several times - because normally it would ask the password after the first
(gk)sudo, then execute the rest without problem. Now replacing them with
pkexec made it ask at every line where a command was run with
pkexec - now how good progress was that?
My problem finally was solved when I installed
lxsudo - I was going to replace
pkexec with that in my script(s), but the I realized that I just copied the old script back (the rest I hadn't modified yet) and made a symlink like this (in
/usr/bin):
Code: Select all
robsku@dragon:/usr/bin$ sudo ln -s gksudo lxsudo
What this removal of
gksu-package is, it's what Windows does. They replace a working solution with another, even if they would work fine together - it's a wonder that they didn't kill
cmd.exe when they introduced PowerShell - Not Linux. Besides Linux has always had several different subsystems, like SVGAlib, FB, DirectFB and X11/X.org and now Wayland (which still has X support). Like when they switched from OSS (Open Sound System 3) to ALSA (Advanced Linux Sound Architecture), did they ditch OSS support? Nope, though first you had to configure virtual OSS device by hand and direct it's output to primary ALSA output. Funny thing, I created also virtual ALSA output, directed the v-OSS to that and directed that ALSA output to Jack Audio Daemon (I was building a system for creating music) and selected the second, real hardware output of ALSA as output for JACK.
I hope one day someone will include OSS4 (used by BSD, has better driver support and features, plus it's easier to program than the damn ALSA, which is pain in butt unless you're using a library with abstraction or PulseAudio) as alternative to ALSA. Like ALSA had OSS3 emulation so does OSS4 have ALSA virtual emulation, or so I've heard. Of course one should be able to choose either one, or even both if one has more than one sound cards - there are some drivers for ALSA that aren't available for OSS4 - then again, why not port them then?
What does it bother you to have both? Have you ever done serious work with sudo, or is it just something that pop's out now and then to ask your password?
EDIT: Some moderator keeps changing the last sentence of my post. I keep restoring it. Rather than this deteriorate into a I know what you are but what am I kind of thing they deleted it entirely. That was probably best since the modification by the moderator wasn't the least bit funny.
I'm interested, but judging from your attitude (except for
In your face Windows, which it deserves, no matter how ill placed it was.
P.S. You are not majority, neither are MacOS users, but it's really sad if you thin you're feeling "superior" because of that. I feel superior because I know my way around computers, which is the reason I use Linux (and some other systems, but never Windows, unless I have to at work or it's running in a Virtual Machine and I got the license for free). See, I use Linux because that's what HC computer freaks do - and not necessarily Linux. Some use BSD, some other systems, some even what's ready on GNU. Now, BSD is a minority if anything - are they superior to you? Are Gentoo users? Because according to you they should.
