From: Chuck Gelm <nc8q@gelm.net>
To: pa3gcu@zeelandnet.nl
Cc: "Eckhardt, Rodolpho H. O." <reckhardt@mandic.com.br>,
paul@mnwebhost.net, linux-newbie@vger.kernel.org
Subject: Re: iptables & a dhcpd question
Date: Sat, 01 Mar 2003 11:57:05 -0500 [thread overview]
Message-ID: <3E60E661.AF8913CF@gelm.net> (raw)
In-Reply-To: 03022720562401.00903@unix.pa3gcu
> > /etc/(PATH TO rc.firewall)/rc.firewall
^^^^^^^^^^^^^^^^^^^^^
/etc/rc.d/rc.firewall
Hmmm, it is plain to see that Richard gave you good advice.
:-|
locate rc.
Yes, IIRC, Slackware is BSD'ish, rather than SYSV'ish.
HTH, Chuck
> >
> > and when they say dhcpd stop, you have to add the path to it in the front:
> >
> > /etc/init.d/dhcpd stop (if /etc/init.d is the path)
> >
> > I hope this works,
>
> Huum, its plain to see you have never seen slackware, slackware does not even
> have a directory called /etc/init.d.
> Slackware is not of the sysv catagory sorry.
>
> >
> > Rodolpho
>
> --
> Regards Richard
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2003-03-01 16:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 19:53 iptables & a dhcpd question Paul
2003-02-27 20:00 ` Eckhardt, Rodolpho H. O.
2003-02-27 20:56 ` pa3gcu
2003-03-01 16:57 ` Chuck Gelm [this message]
2003-03-01 1:28 ` animated gif creation Peter Howell
2003-02-27 20:16 ` iptables & a dhcpd question Ray Olszewski
2003-02-27 20:41 ` Paul
2003-02-27 21:02 ` Brian P. Bilbrey
2003-02-27 21:09 ` Jos Lemmerling
-- strict thread matches above, loose matches on Subject: below --
2003-02-27 22:22 Weigand, Benjamin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E60E661.AF8913CF@gelm.net \
--to=nc8q@gelm.net \
--cc=linux-newbie@vger.kernel.org \
--cc=pa3gcu@zeelandnet.nl \
--cc=paul@mnwebhost.net \
--cc=reckhardt@mandic.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox