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.
Sorry if this is too noobie of a question but I have been searching for hours and can't find the answer. I'm still pretty lost in Slackware.
In Mandrake, if I wanted to find out what services are running and turn services off so they wont start on boot, I used the Mandrake Control Center. In Slack I can't even figure out how to list the running services, much less turn them off. I thought "ps -aux" listed everything that's running but it doesn't show running services like: arts, shorewall, nfs... etc.
Could someone please take a minute and point me in the right direction?
Thank you for the reply. Slack is kind of different. In Mandrake you had rc3.d, rc4.d and so on. You just comment out the services you don't want running at whatever run-level the service ran. I tried using the instructions for stopping services in my Linux administration book but the instruction won't work for Slack. I'll keep studying though.
another way of doing the same thing that contra explained is to do the following:
1) if you want to see what services are listening on given ports, use "$socklist" or "$netstat -l"
2) to get rid of these services, i just go through the various scripts in /etc/rc.d/ that start and stop the respective services; if you want to not have httpd (or any of the other daemons) run on startup, then go through the scripts rc.0, rc.K, rc.M, rc.S, and rc.inet2 and comment out the lines where those services are mentioned; also remember to go through /etc/inetd.conf to shutdown services like finger, auth, etc.
3) check that no services are listening by using commands in 1)
Originally posted by mooreted I have gone back to Mandrake. Tired of trying to fix Slackware.
Thanks for all the help,
Ted.
Trying to fix Slackware? There is nothing broke in it.
What your are doing under the 'Mandrake Control Center' is using a GUI interface to manipulate scripts and configuration files. Since you have no idea where these files are and how they interact with each other you require a GUI.
Some do not wish to use a GUI or have a greater desire to understand how their OS works.
Ok, since I'm a hardcore Slacker, I have to call a foul. Mere MENTION of Mandrake requires a quick disembowelment! Keep in mind, the true power of linux is still yielded at the command line. I tried Mandrake when I first started with linux way back when. Even at first glance I hated it. GUI configs were buggy and no real control over your own environment unless you went to the command line which is where Slackware comes in. To truly understand linux, I honestly believe you need to put yourself in the shoes of the creator. It's really not that hard to comprehend once you start to recognize certain patterns in the obvious logic that is Slackware. I really must say - the more I use Slackware, the more I appreciate it over the other distributions, truly.
Originally posted by mooreted I have gone back to Mandrake. Tired of trying to fix Slackware.
Thanks for all the help,
Ted.
There are those who like to do things for themselves and those who like to have things done for them. If you prefer the latter then you are better off in Mandrake. Don't get me wrong, I think Mandrake is a fine distro and does it's job well. It just has a different philosophy. Slackware is very low level for administration, if this does not suit you then you probably will never like it. But Slackware does not need "fixing" it needs administration.
hi.....don't worry, it just a normal process of learning linux. Ppl will go forth and back again to various distro until they stop and think. Which distro teach them someting. For me, itys Slackware. Once you know how Slackware works, it will become easier everyday.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.