From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: gentoo iptables problem
Date: Fri, 17 Nov 2006 18:33:43 -0700 [thread overview]
Message-ID: <20061118013343.GA1202@localhost.localdomain> (raw)
In-Reply-To: <Pine.BSF.4.64.0611171846230.12922@server2.shellworld.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
No, you don't understand. There's a binary called iptables, and there
is a kernel module also called iptables, (though if you want to be
specific, that's actually called iptables.co), that you load via
modprobe. If the kernel module isn't loaded, or is not built into the
kernel, or can't be automagically loaded when needed, you can do with
the iptables binary whatever you want, and it still won't work without
that module.
Greg
On Fri, Nov 17, 2006 at 06:48:34PM -0500, Jude DaShiell wrote:
> John, that's right when the emerge happened iptables was built as a
> program not a module. It's probably some useflag that needs setting
> correctly for this to build as a module.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFXmL37s9z/XlyUyARAmrhAKCceRKkw3p2WWBynsxvm4s0idRFjQCfZ/co
ttzYoZj3S6KNCM3gJ/7wyds=
=iZZI
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Jude DaShiell
` Gregory Nowak [this message]
` John Heim
-- strict thread matches above, loose matches on Subject: below --
Jude DaShiell
Jude DaShiell
` John Heim
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=20061118013343.GA1202@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).