From: "Bruce A. Locke" <blocke@shivan.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] iptables directory
Date: 23 Dec 2001 05:51:07 -0500 [thread overview]
Message-ID: <1009104669.13876.0.camel@kodiak.chronospace.org> (raw)
In-Reply-To: <20011222095650.B23774@chiba.3jane.net>
On Sat, 2001-12-22 at 10:56, Daniel Robbins wrote:
> On Thu, Dec 20, 2001 at 03:03:02PM +0200, Vitaly Kushneriuk wrote:
> > Hi.
> > As iptables can be called from /etc/init.d/ scripts and is essential for
> > system startup, it should go to /sbin and not to /usr/sbin
>
> OK; I just fixed this in iptables-1.2.4-r1. It should be showing up on
> rsync soon.
It appears broke on my system. I unmerged all previous versions of
iptables and merged the most current and now I get fun stuff like this:
--- snip ---
iptables v1.2.4: Couldn't load target
`standard':/usr/lib/iptables/libipt_standard.so: cannot open shared
object file: No such file or directory
Try `iptables -h' or 'iptables --help' for more information.
iptables v1.2.4: Couldn't load target
`MASQUERADE':/usr/lib/iptables/libipt_MASQUERADE.so: cannot open shared
object file: No such file or directory
Try `iptables -h' or 'iptables --help' for more information.
--- snip ---
Creating a symlink from /usr/lib/iptables to /lib/iptables makes it work
again but obviously its not the correct solution... is /usr/lib
hardcoded into iptables? the ebuild seems fine, etc.
--
Bruce A. Locke
blocke@shivan.org
"Those that would give up a necessary freedom for temporary
safety deserve neither freedom nor safety."
-- Ben Franklin
next prev parent reply other threads:[~2001-12-23 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 13:03 [gentoo-dev] iptables directory Vitaly Kushneriuk
2001-12-20 13:31 ` AW: " Sebastian Werner
2001-12-20 13:38 ` Juergen Ilse
2001-12-22 15:07 ` Vitaly Kushneriuk
2001-12-22 15:59 ` Daniel Robbins
2001-12-22 15:56 ` Daniel Robbins
2001-12-23 10:51 ` Bruce A. Locke [this message]
2001-12-23 13:57 ` Martin Schlemmer
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=1009104669.13876.0.camel@kodiak.chronospace.org \
--to=blocke@shivan.org \
--cc=gentoo-dev@gentoo.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