Some advice needed after having installed Slackware 14.2
SlackwareThis 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.
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.
Some advice needed after having installed Slackware 14.2
Edit: sorry for somewhat off topic, but this is the second time this week that this has come up. I would like to know the proper way to use sudo on Slackware if I am wrong.
You can use sudo as long as you execute each command in a login shell. However, not all commands can be launched in a login shell with sudo using the -i option. As an example a limited user can run slackpkg or sbopkg like so:
At least this is how I understand sudo for Slackware. I use sudo like this all the time. However, as another example, Slackbuilds should always be ran from a login shell as root. I am interested to know if this is accurate.
Re-P.S. You're right, same here with drei-sat, looks like it needs Flash. I'm not using Flash at all, mainly due to its security issues, and I'm not versed with it, but you could try what AlienBoB prepared: http://www.slackware.com/~alien/slac...player-plugin/
@gregors & @mralk3
- check this recent discussion about sudo (don't mind my mistake with sudo (corrected by bassmadrigal), haven't used it for ages and also don't plan to in the near future - thus, my brain just dropped all the useless knowledge about it )
@gregors & @mralk3
- check this recent discussion about sudo (don't mind my mistake with sudo (corrected by bassmadrigal), haven't used it for ages and also don't plan to in the near future - thus, my brain just dropped all the useless knowledge about it )
Thanks! I usually set my path in .bashrc which I guess accomplishes the same thing as setting it in /etc/sudoers via visudo. I will modify my settings appropriately.
Interesting. Is systemd mandatory in Debian? I seem to recall reading something about it not being mandatory, and that you could still choose to install SysVinit.
Unfortunately it's not that simple. The way Debian's package management system works, as soon as it needs to install a package which depends on systemd (and it might be a package unintentionally installed as a dependency of another package), it pulls in systemd and converts the system over to using it.
This makes using Debian without systemd prohibitively difficult.
The better alternatives are to use Devuan (which is Debian with package dependencies redone to avoid systemd) or another of the seventy or so distributions which don't use it.
1. This LQ forum is the best one to stay in touch with the Slack community, only use English, otherwise you'll maybe get banned
You could also visit this forum in German. Salix being a derivative of Slackware some questions can be answered here. Bear in mind though that Salix does not ship all Slackware packages, and only one desktop.
Quote:
6. As you come from Debian, I'd like to point out that under Slackware you always need to be root ( su - ) if you're performing administrative tasks, never use sudo.
I recently installed Debian Buster in a VM. I was given the choice of setting a password for root or using sudo during installation. I chose the former and use su -.
Last edited by Didier Spaier; 11-04-2018 at 03:22 AM.
I recently installed Debian Buster in a VM. I was given the choice of setting a password for root or using sudo during installation. I chose the former and use su -.
For my entire first week of learning Debian I was root, I didn't even have a user account. This was due to my lack of knowledge, but I didn't screw anything up. In retrospect, it would have been entirely possible, and advisable, just to use su - on my user account.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.