Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
View Poll Results: Should Slackware remove "sudo" package?
|
Yes! Kill it!
|
  
|
6 |
12.00% |
No! OMG, Its my BFF!
|
  
|
34 |
68.00% |
Move the sudo package to /extra
|
  
|
9 |
18.00% |
Move the sudo package to Slackbuilds.org
|
  
|
1 |
2.00% |
 |
|
07-13-2014, 04:33 AM
|
#16
|
Senior Member
Registered: Sep 2012
Posts: 1,385
|
Quote:
Originally Posted by dugan
Sudo is included with Slackware and not enabled by default. I think that's perfect.
|
I agree!
|
|
|
07-13-2014, 06:02 AM
|
#17
|
Senior Member
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,559
|
The wording of this poll is exceptionally biased in its wording. I refuse to vote as nothing applies to me.
Leave it where it is. Granted Ubuntu, MacOS and others overuse sudo but that doesn't mean it has no value at all. As others have stated, granularity is the key.
|
|
|
07-13-2014, 08:22 AM
|
#18
|
Slackware Contributor
Registered: Apr 2008
Distribution: Slackware
Posts: 1,707
|
Quote:
Originally Posted by kingbeowulf
Egad! Only root should be allowed to do certain tasks. The horror! Not just some random user, even if that random user is just you.
|
There are some good explanations in this thread about what sudo is _actually_ for, and its intended use cases.
For example, for some of the systems I used to administer, I wrote a script to provide some insight into a particular batch queue. This involved running certain commands as root, so I set up /etc/sudoers to permit a small set of commands to be run as root. Nobody could do 'sudo su -' and get a root shell.
Probably in 2006 or there abouts I started seeing Red Hat adopt this 'sudo this' 'sudo that' approach.
Having worked as a sysadmin at Red Hat during that period, all I could ascertain from the devs that it was stupid to open a root shell with 'su -' (which was what all the sysadmins did, who are careful with a root shell).
The developers couldn't appreciate that it was indeed possible for someone whose profession and sleep was related to being careful, went about abusing 'sudo', putting it in blogs, documents. Quickly the mind virus spread.
You only have to look at the other crazy ideas such as aliasing 'rm' to 'rm -i'. On Red Hat, you can't even issue ' rm -rf ' without being prompted; you either have to unalias rm or call '/bin/rm -rf'.
Red Hat and Canonical (Ubuntu) are commercial companies who operate support departments. The idea (one of them) is to reduce the amount of support calls they get from people who opened a root shell, forgot it was root and did stupid things. It makes sense from this point of view.
I can see about 10 root shells open on my desktop at the moment, but they're mostly to Slack ARM build machines where I always need to use root. Other systems I only su - when necessary, to minimise accidentally pasting something from the clipboard into that shell.
There are plenty of people who use Linux who are sensible and careful, and find it irritating if their chosen distribution tries to treat them like they're less than so.
Last edited by drmozes; 07-13-2014 at 08:23 AM.
|
|
4 members found this post helpful.
|
07-13-2014, 08:49 AM
|
#19
|
Moderator
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,989
|
Member Response
Hi,
Slackware is unique and I wish it to remain such. Just because *buntu are jumping off the barn doesn't mean Slackware needs too follow. Absurd to try and walk the 'hold your hand' distro way. Let them to continue jumping off the barn. Leave Slackware alone!
As a Slackware user you have the means to secure the install! Just be aware of howto or ask here. 'sudo' is useful when you need others to have controlled access for utilities on the system. Trusted!
|
|
|
07-13-2014, 09:10 AM
|
#20
|
Senior Member
Registered: Oct 2008
Distribution: Debian sid
Posts: 2,683
|
Quote:
Originally Posted by drmozes
You only have to look at the other crazy ideas such as aliasing 'rm' to 'rm -i'. On Red Hat, you can't even issue ' rm -rf ' without being prompted; you either have to unalias rm or call '/bin/rm -rf'.
|
Try 'escaping' it
|
|
|
07-13-2014, 09:48 AM
|
#21
|
Senior Member
Registered: Apr 2005
Posts: 2,727
|
buntu can do what they like with sudo for all I care, doesn't necessarily make sudo a bad thing. Anything can be abused and someone can equally run everything as root or by abusing su.
The manual is clear:
Code:
sudo allows a permitted user to execute a command as the superuser or
another user, as specified by the sudoers file. The real and effective
uid and gid are set to match those of the target user, as specified in
the password database, and the group vector is initialized based on the
group database (unless the -P option was specified). See the Command
Environment section below for more details.
|
|
|
07-13-2014, 10:46 AM
|
#22
|
LQ 5k Club
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,311
Rep: 
|
I've abstained from voting, because I'm the sole user of my computers, I've never used sudo on Slackware, it's no hardship entering root's password, and don't care where it is.
|
|
|
07-13-2014, 11:08 AM
|
#23
|
Member
Registered: Nov 2009
Location: Kansas, USA
Distribution: Slackware64-15.0
Posts: 865
|
I have likewise abstained from voting, as this question assumes that Slackware users are as prone to stupidity as *buntu and RedHat users to abuse the 'sudo' command. Slackware and its ilk are suited for mature users who know how to use root's powers judiciously and are well aware of its potentially destructive abilities.
kingbeowulf, I would strongly suggest that you take a closer look at this forum, and the discussion between veteran users and newbies to get a sense of how often 'sudo' is abused/overused. Rarely (if ever) have I come across a case where root's powers were used carelessly, and if they were, the users learned their lesson and abstained from similar behavior thereafter.
Summary: Leave sudo as is.
|
|
|
07-13-2014, 11:17 AM
|
#24
|
LQ 5k Club
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,311
Rep: 
|
I wouldn't call RedHat and *buntu users stupid, I'd say they have poor taste in distros. 
|
|
1 members found this post helpful.
|
07-13-2014, 11:31 AM
|
#25
|
Member
Registered: Nov 2009
Location: Kansas, USA
Distribution: Slackware64-15.0
Posts: 865
|
Quote:
Originally Posted by brianL
I wouldn't call RedHat and *buntu users stupid, I'd say they have poor taste in distros. 
|
I do agree with you about their taste in distros, but I didn't say that *buntu and RedHat users were stupid in general, just in their tendency to overuse the 'sudo' command, although my statement might have been worded as to leave that impression on the mind of a casual reader.
|
|
1 members found this post helpful.
|
07-13-2014, 11:38 AM
|
#26
|
Moderator
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,989
|
Member Response
Hi,
I too think that *buntu users are not stupid but just misguided or just drinking too much of the *buntu cool aid. 
|
|
|
07-13-2014, 11:57 AM
|
#27
|
Member
Registered: Nov 2009
Location: Kansas, USA
Distribution: Slackware64-15.0
Posts: 865
|
Quote:
Originally Posted by onebuck
Hi,
I too think that *buntu users are not stupid but just misguided or just drinking too much of the *buntu cool aid. 
|
I apologize for inadvertently leaving the impression that I was calling *buntu/RedHat users stupid in general. In the context of the abuse of the 'sudo' command are *buntu/RedHat users stupid, leaving aside the wisdom of their choice of distros. Alas, however,too many people equate 'Linux' with 'Ubuntu' because a lot of sites are giving that impression. A curious paradox, given the fact that Ubuntu itself avoids using the word 'Linux' in its labeling. As I see it, there are two possibilities which would adequately explain this state of affairs. Either a) *buntu wants to focus attention solely on itself, thereby garnering mindshare in users looking for an alternative to Windows or b) *buntu wants to help users overcome the instinctive fear of new users when hearing 'Linux' (because *nix has the reputation of having a steep learning curve), much as the word 'computer' was avoided by DEC in the 50's & 60's in an attempt to circumvent fears of big, hulking machines when trying to sell their minicomputers.
I think that the first possibility is the most likely, although that might well be prejudice on my part, given statements made by Mark Shuttleworth in the past regarding the direction he wants *buntu to take.
Last edited by 1337_powerslacker; 07-13-2014 at 12:07 PM.
|
|
|
07-13-2014, 12:18 PM
|
#28
|
Member
Registered: Jul 2014
Posts: 57
Rep: 
|
I find it convenient to use sudo (with no password even) for mounting/unmounting removable media like cdroms, usb storage and the like. Other than that I'd just as soon use su to run privileged commands. I see no reason to move/get rid of the sudo package.
|
|
|
07-13-2014, 12:27 PM
|
#29
|
Member
Registered: Nov 2009
Location: Kansas, USA
Distribution: Slackware64-15.0
Posts: 865
|
Quote:
Originally Posted by BobKay
I find it convenient to use sudo (with no password even) for mounting/unmounting removable media like cdroms, usb storage and the like. Other than that I'd just as soon use su to run privileged commands. I see no reason to move/get rid of the sudo package.
|
Agreed.
|
|
|
07-13-2014, 12:41 PM
|
#30
|
Senior Member
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,559
|
Quote:
Originally Posted by BobKay
I find it convenient to use sudo (with no password even) for mounting/unmounting removable media like cdroms, usb storage and the like. Other than that I'd just as soon use su to run privileged commands. I see no reason to move/get rid of the sudo package.
|
You could also use pmount instead.
EDIT
Hmm .. I only just realised that I could just use udisks or udisks2 for this and still avoid escalating to root.
udisks:
Code:
udisks --mount /dev/sdc1
udisks --unmount /dev/sdc1
udisks will mount disks to /media/ label.
udisks2:
Code:
udisksctl mount -b /dev/sdc1
udisksctl unmount -b /dev/sdc1
udisks2 will mount disks to /run/media/ username/ label.
Note: Adjust the device name to match the device you wish to mount/unmount.
Last edited by ruario; 07-13-2014 at 01:28 PM.
|
|
2 members found this post helpful.
|
All times are GMT -5. The time now is 08:27 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|