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.
I was running Guarddog from the command prompt just noticed that it actually installed shortcuts in the kde menu.The shortcut brings up a root password prompt.
Perhaps you know it, but guarddog writes his rc.firewall in /etc/, which is not the right place in Slackware. So, when you reboot, there's no more firewall. You have to move this script in /etc/rc.d/ in order to have a permanently walled system.
I just did that and started up Guarddog and it created a new rc.firewall in /etc, It doesnt look like its using the one in /etc/rc.d. Is there a way to fix that?
Originally posted by Tinkster Several ways, actually ...
ln -s
Edit the source
manually copy the file
...
Cheers,
Tink
I manually copied the file from /etc to /etc/rc.d and when i started up guarddog I received a message saying that This is the first time I have started it and so on, So I think guarddog is looking at /etc for rc.firewall instead of /etc/rc.d.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.