startup files or scripts
 

Which files do I modify to start and stop services and programs starting up at boot? :scratch:
Thanks

In Slack? /etc/rc.d/foo. Like if you don't want sendmail, remove the executable bit from rc.sendmail - if you want more detailed items, comment them out in the relevant runlevel, like rc.M.

There are more in /etc/services

Just comment out the lines for the ones you don't need. (eg. ftp)

Garry

What do you mean remove the executable bit?
How do I do that, Can I just move the file to trash?
Thanks.

I wouldn't delete them, just in case you want to use them in the future - better off to chmod a-x filename them. The files are owned by root so you shouldn't even be able to move them to the trash, if you can then you shouldn't be running X as root.

I agree, don't delete them................And what Kovacs means by removing the executable bit (the x bit) is to remove the file permission that makes a file executable (ie., allowing you to run the program or script).........all those files in /etc/rc.d are scripts. Without the x bit being set, scripts or programs cannot run...............When Slackware boots up, it checks to see if those startup scripts are executable or not and acts accordingly...... :)

There's a very good mini tutorial in LQ by bulliver which should help clarify things a little about file permissions:

Quick and Dirty Guide to Linux File Permissions

Ok, cool. Thanks :)

Is foo an example or something?, I cannot find it in slack, also, do I absolutly need sendmail since I use yahoo email?
Thanks

No you do not need sendmail to startup, because with yahoo you have to access your mail through the web, not through a e-mail client such as: thunderbird, evolution, kmail. You could also use pkgtool to remove the executable bit from your startup scripts, if your not that comfortable with command line.

-tank

Cool, Thats what I thought but I was not completely sure. Thanks..

Yes, "foobar", "foo' and "bar" are often used as examples.............. :)