From: Amin Azez <azez@ufomechanic.net>
To: Roberto Nibali <ratz@tac.ch>
Cc: Netfilter Developers <netfilter-devel@lists.netfilter.org>
Subject: Re: Fixed Re: iptables 1.3.1 crashes on iptables-restore
Date: Mon, 08 Aug 2005 17:03:18 +0100 [thread overview]
Message-ID: <42F78246.3030302@ufomechanic.net> (raw)
In-Reply-To: <42F780B3.3030102@tac.ch>
Roberto Nibali wrote:
>>Yes, I need the latest and greatest conntrack stuff, naturally ;-)
>>
>>
>
>So you run a 2.6.14 kernel :)
>
>
I'm waiting for all the fancy goods to get merged before I take that one.
>
>Invoke /lib/libc.so.6 like a command. It won't destroy your system but
>it will display how your libc was crafted.
>
>
GNU C Library stable release version 2.3.2, by Roland McGrath et al.
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 3.2.2 20030222 (Red Hat Linux 3.2.2-5).
Compiled on a Linux 2.4.20 system on 2003-03-13.
Available extensions:
GNU libio by Per Bothner
crypt add-on version 2.1 by Michael Glad and others
linuxthreads-0.10 by Xavier Leroy
BIND-8.2.3-T5B
libthread_db work sponsored by Alpha Processor Inc
NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
Thread-local storage support included.
Report bugs using the `glibcbug' script to <bugs@gnu.org>.
Sam
next prev parent reply other threads:[~2005-08-08 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 3:46 iptables 1.3.1 crashes on iptables-restore Alexander Samad
2005-03-31 8:18 ` Roberto Nibali
2005-08-04 16:24 ` Amin Azez
2005-08-05 10:08 ` Amin Azez
2005-08-05 12:57 ` Fixed " Amin Azez
2005-08-05 13:22 ` Roberto Nibali
2005-08-08 15:45 ` Amin Azez
2005-08-08 15:56 ` Roberto Nibali
2005-08-08 16:03 ` Amin Azez [this message]
2005-08-08 16:19 ` Roberto Nibali
2005-08-08 16:28 ` Amin Azez
2005-08-08 16:46 ` Roberto Nibali
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=42F78246.3030302@ufomechanic.net \
--to=azez@ufomechanic.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=ratz@tac.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.