Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Les Mikesell <les@futuresource.com>
To: "R. DuFresne" <dufresne@sysinfo.com>
Cc: Netfilter users list <netfilter@lists.netfilter.org>,
	"John A. Sullivan III" <jsullivan@opensourcedevelopmentcorp.com>
Subject: Re: Saving IPTable rules..oops
Date: Wed, 29 Dec 2004 14:30:39 -0600	[thread overview]
Message-ID: <1104352238.2940.29.camel@moola.futuresource.com> (raw)
In-Reply-To: <Pine.LNX.4.05.10412291453001.27815-100000@darkstar.sysinfo.com>

On Wed, 2004-12-29 at 14:15, R. DuFresne wrote:

> > The way I've typically seen it work is that the init.d/iptables script
> > calls iptables-restore and passes it the /etc/sysconfig/iptables file. 
> > This file is written when you do init.d/iptables save.
> 
> 
> perhaps on redhat and debian, and maybe suse systems that have moved away
> from the standard upon which linux was formed, namely bsd.

Linux is a kernel and it leans more in the sysV direction.  As I
recall, the early versions supported termio.h, not sgtty.h before things
converged to the posix termios.h

> Those dists
> that retain their bsd layouts have no /etc/init.d directory, everything
> lies under /etc/rc.d/. 

Retain?  Perhaps you mean 'were built separately', omitting the sysv
init functionality?

> And it's a shame things are seperating out in
> the linux world like this as many of the tools and toys bewing created
> either conform to the new redhat layouts or follow older established
> standards.  

SysV and bsd styles separated before Linux was invented. It's a shame
they never converged and that bsd style distributions still don't have
a decent way to start and stop services.

---
  Les Mikesell
   les@futuresource.com




  parent reply	other threads:[~2004-12-29 20:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-29 18:03 Saving IPTable rules..oops Jason Williams
2004-12-29 18:23 ` Deepak Seshadri
2004-12-30 20:39   ` Jason Williams
2004-12-30 20:52     ` Deepak Seshadri
2004-12-30 21:38       ` Jason Williams
2004-12-30 22:09         ` John A. Sullivan III
2004-12-29 18:32 ` John A. Sullivan III
2004-12-29 20:15   ` R. DuFresne
2004-12-29 20:29     ` Jason Opperisano
2004-12-30  6:33       ` R. DuFresne
2004-12-29 20:30     ` Les Mikesell [this message]
2004-12-29 22:29     ` John A. Sullivan III
2004-12-30  0:08       ` Alistair Tonner
2004-12-30  6:45       ` R. DuFresne
2004-12-29 18:35 ` John A. Sullivan III

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=1104352238.2940.29.camel@moola.futuresource.com \
    --to=les@futuresource.com \
    --cc=dufresne@sysinfo.com \
    --cc=jsullivan@opensourcedevelopmentcorp.com \
    --cc=netfilter@lists.netfilter.org \
    /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