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.
Using a line editor like vim, nano, etc. isn't always advised when you CCP text.
Kwrite/Kate, Gedit, mousepad, leafpad, etc. are text editors, not line editors. If you want to CCP large blocks of text, like rc.firewall, use a text editor.
What?
I'm not a huge vi/vim fan, but you certainly can insert multiple lines of text with vi without it adding automatic line wrap and what not.
I'm not a huge vi/vim fan, but you certainly can insert multiple lines of text with vi without it adding automatic line wrap and what not.
ed is what I consider a line editor.
I've never had favorable multiline with editors using a terminal. Mostly why I group them in with line editors like ed. Just my experience and point of view, but it's just that only.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 928
Rep:
Quote:
Originally Posted by astrogeek
...
Code:
bash-4.2# cd /etc/rc.d/rc.firewall
bash: cd: /etc/rc.d/rc.firewall: Not a directory
(twice)
You must try to understand what you expect each step to do, and you must read, and understand the messages returned by each command. Otherwise your result is just gibberish.
...
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 928
Rep:
Quote:
Originally Posted by Belikewater
Alright I get it. I need to study. Thanks for the input.
Yes, as I'm studying and learning every day too.
Quote:
Slackware is a tough crowd indeed.
No, they are really friendly, what happens is Slackware is not a 'hold your hand' type of distro,
so some hours of read, search and experiment is expected.
Break your Slackware install as many times you need. You will learn a lot trying to fix it (as I do )
Alright I get it. I need to study. Thanks for the input. Slackware is a tough crowd indeed.
Your intention to study more, read more and learn more, expressed more than once in this thread, is a noble one.
But it does nothing - absolutely nothing - to solve the problem which is the subject of this thread, namely the problem of setting up a firewall on Slackware. A thread started by none other than yourself.
There's no need for high drama or gnashing of teeth regarding this problem. Just show us the content that was generated when you visited Eric's Easy Firewall Generator page; then tell us how you tried to save it to /etc/rc.d/; and, finally, tell us how you made that file executable and what errors, if any, came up when you restarted the computer.
Answering just those very simple questions will get you a lot farther, a lot faster, than all those solemn posts of yours about how you intend to study more widely and more deeply some time in the never-never. Try to focus systematically on just the problem at hand, namely, the firewall problem, and the specific steps you have taken or are about to take to resolve this one problem in your effort to learn Slackware. List the specific steps you have taken and post the content of any files you have created or edited along the way, and your firewall problem will be solved before evening.
Thanks Gezley. I will look into it when I get out of work. I'll figure it out on my own. Ill just read the instructions more carefully which I plan to do during my break here shortly. We can close this thread.
Using a line editor like vim, nano, etc. isn't always advised when you CCP text.
Kwrite/Kate, Gedit, mousepad, leafpad, etc. are text editors, not line editors. If you want to CCP large blocks of text, like rc.firewall, use a text editor.
Thank you Reaper and notKlaatu. I used a text editor and it worked
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.